Remote support method and remote support system

By calculating processing loads and communication volumes, and proposing evasion routes for mobile bodies, the method and system address the burden of remote support, reducing server loads and costs, thus enabling sustainable service operation.

JP2025014513APending Publication Date: 2025-01-30TOYOTA JIDOSHA KK
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023117127
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-07-18
Publication Date
2025-01-30

AI Technical Summary

Technical Problem

The processing load and communication costs associated with providing remote support for multiple mobile bodies can overwhelm service providers, necessitating significant infrastructure investments and increased expenses, which may burden businesses and users.

Method used

A method and system that calculates processing loads and communication volumes, and proposes evasion routes for mobile bodies to avoid remote support when limits are reached, thereby reducing server load and communication costs.

Benefits of technology

This approach prevents excessive processing loads and communication costs by suggesting alternative routes, ensuring sustainable operation of remote support services without overwhelming business operators or users.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025014513000001_ABST
    Figure 2025014513000001_ABST
Patent Text Reader

Abstract

To provide technology for suppressing an excessive load on a business operator providing a remote support service and enabling the business operator to operate the service appropriately.SOLUTION: A processing load on a server that manages a remote support is calculated, or a communication volume per unit time transmitted or received between a target moving object of the remote support and the server is calculated. Positional information about a current location and a destination of the target moving object, and map information including the current location and the destination are acquired. When the processing load is equal to or greater than an upper limit load or when the communication volume per unit time is equal to or greater than an upper limit amount, a proposal for an avoidance route that avoids an occurrence of the remote support is made to the target moving object based on the positional information and the map information.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a method and system for providing remote support to a mobile object. [Background technology]

[0002] Japanese Patent Publication No. 7211490 discloses a method for managing the travel route of a moving object used in a vehicle dispatch service. In this conventional method, the moving object is configured to be able to switch between an automatic driving mode and a manual driving mode. In the conventional method, when setting the travel route of a moving object having such a configuration, history information of the position where switching from the automatic driving mode to the manual driving mode occurred is acquired. Then, based on this history information, a travel route that avoids the position where the switching occurred is set. Therefore, according to the conventional method, it is possible to set a travel route where switching from the automatic driving mode to the manual driving mode is unlikely to occur, that is, a travel route with high travel reliability only in the automatic driving mode. This makes it possible to reduce the monitoring burden of the system that manages the vehicle dispatch service.

[0003] In addition to Japanese Patent No. 7211490, examples of documents showing the technical state of the technical field related to the present disclosure include Japanese Patent Publication No. 2020-159866 and Japanese Patent Publication No. 6551127. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7211490 [Patent Document 2] JP 2020-159866 A [Patent Document 3] Patent No. 6551127 Summary of the Invention [Problem to be solved by the invention]

[0005] Consider a service that provides remote support to multiple mobile objects. When remote support is provided in a concentrated manner within a short period of time, it is expected that the processing load of the system that manages the service will become enormous. To withstand such a huge processing load, it will be necessary to make a corresponding investment in infrastructure, such as increasing the number of processing devices that make up the system to improve robustness and broadening the network lines between the system and the multiple mobile objects. However, such infrastructure investment is expected to be a burden for the service provider.

[0006] In addition, if the volume of communication traffic increases due to the concentration of remote support services, communication costs are expected to rise. However, such an increase in costs is also expected to be a burden for service providers.

[0007] It is possible to pass on some of the infrastructure investment costs and communication costs to users of the service. However, in this case, there is a possibility that users will be prevented from using the service. Therefore, it is desirable to develop technology that enables remote support service providers to operate the service appropriately while preventing the service provider from imposing an excessive burden on the service provider.

[0008] One objective of the present disclosure is to provide technology that reduces the burden on businesses that provide remote support services and enables the businesses to operate the services appropriately. [Means for solving the problem]

[0009] A first aspect of the present disclosure is a method for remotely supporting a plurality of moving objects, the method having the following features. The method includes a step of calculating a processing load of a server managing the remote support, or a communication volume per unit time transmitted or received between a target mobile object of the remote support and the server; acquiring location information of a current location and a destination of the target moving object and map information including the current location and the destination; when the processing load is equal to or greater than an upper limit load, or when the communication volume per unit time is equal to or greater than an upper limit volume, making a proposal to the target moving object regarding an avoidance route for avoiding the occurrence of remote support based on the location information and the map information; Includes.

[0010] A second aspect of the present disclosure is a system for providing remote support to a plurality of moving objects, and has the following characteristics. The system includes a server that manages the remote support. The server, A process of calculating a processing load of the server or a communication volume per unit time transmitted or received between the target mobile object of the remote support and the server; A process of acquiring location information of a current location and a destination of the target moving object and map information including the current location and the destination; a process of proposing to the target moving object, based on the location information and the map information, a route to avoid the occurrence of remote support, when the processing load is equal to or greater than an upper limit load, or when the communication volume per unit time is equal to or greater than an upper limit volume; The present invention is configured to: Effect of the Invention

[0011] According to the present disclosure, when the processing load of the server is equal to or greater than the upper limit load, a proposal regarding an avoidance route to avoid the occurrence of remote support is made to the target mobile body. Therefore, when the target mobile body accepts this proposal, it is possible to prevent the processing load of the server from becoming too large. According to the present disclosure, or when the communication volume per unit time transmitted or received between the target mobile body of remote support and the server is equal to or greater than the upper limit, a proposal regarding an avoidance route to avoid the occurrence of remote support is made. Therefore, when the target mobile body accepts this proposal, it is possible to reduce the communication volume per unit time and prevent communication costs from increasing. Therefore, according to the present disclosure, it is possible to prevent the burden on the business providing the remote support service from becoming too large, and to allow the business to operate the service appropriately. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a conceptual diagram illustrating a remote service. [Diagram 2] FIG. 11 is a diagram showing an example of an image output from a display of a terminal operated by an operator. [Diagram 3] FIG. 11 is a diagram showing another example of an image output from the display of the terminal operated by the operator. [Figure 4] FIG. 13 is a diagram for explaining an example of an image displayed on a display when a first task is assigned to a mobile object, in association with two types of states of an operator before this assignment is made. [Diagram 5] 2 is a block diagram showing an example of a functional configuration of a processor of a management server particularly related to the first embodiment. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, a remote support method and a remote support system according to an embodiment of the present disclosure will be described with reference to the drawings. The method according to the embodiment is realized by computer processing performed in the system according to the embodiment. In addition, in each drawing, the same or corresponding parts are given the same reference numerals, and the description thereof will be simplified or omitted.

[0014] 1. Remote Support Fig. 1 is a conceptual diagram for explaining remote support for a mobile entity, which illustrates a management server MS, mobile entities MB1 and MB2, and operators OP1 and OP2.

[0015] The management server MS manages a service that provides remote support (hereinafter, also referred to as a "remote service"). The management server MS is typically managed by a remote service provider. The management server MS communicates with a plurality of mobile units MB and a plurality of operators OP.

[0016] Mobile bodies MB1 and MB2 are examples of "multiple mobile bodies MB" in the present disclosure. Each of the multiple mobile bodies MB is a target for providing remote services. Some or all of the multiple mobile bodies MB may be mobile bodies owned by a remote service provider, or may be mobile bodies owned by a corporation or individual that has entered into a remote service provision contract with this provider. The total number of the multiple mobile bodies MB (hereinafter also simply referred to as "mobile bodies MB") is M (M≧2). The configuration of the mobile body MB is not particularly limited, but it is desirable for it to have a configuration capable of automatic driving.

[0017] The operators OP1 and OP2 perform a service business SB for a remote service provision target. The multiple operators OP including the operators OP1 and OP2 may be employees of a business providing the remote service, or may be employees of a corporation or individuals who have concluded a contract for outsourcing with the business. The total number of the multiple operators OP (hereinafter also simply referred to as "operators OP") is N (N≧2). Examples of the service business SB include remote monitoring, remote assistance, and remote driving.

[0018] Remote monitoring includes monitoring by the operator OP of the communication status of the remotely monitored subject, the driving environment of the remotely monitored subject, the status of the remotely monitored subject, and the status of the occupants of the remotely monitored subject. Remote assistance includes suggestions by the operator OP to facilitate the continued driving of the remotely supported subject when the remotely supported subject encounters a situation that it cannot handle. Remote driving includes the execution of a dynamic motion task of the remotely driven subject by the operator OP and / or execution of a fallback for this dynamic motion task.

[0019] 2. Management Server Configuration Example 2 is a diagram illustrating an example of the configuration of a management server MS. In the example shown in Fig. 2, the management server MS includes a map DB (database) 11, a management DB 12, a communication device 13, and an information processing device 14.

[0020] The map DB 11 is formed in a predetermined storage device (e.g., a non-volatile recording medium such as a hard disk or a flash memory). Map information MAP is stored in the map DB 11. Examples of the map information MAP include information on the location of roads, information on the shape of roads (e.g., types of curves and straight lines), and information on the locations of intersections and structures.

[0021] The map information MAP also includes information on the occurrence level RLV of remote support. The occurrence level RLV indicates the frequency of occurrence of remote support. The occurrence level RLV is set in advance for each area formed by dividing the map. The occurrence level RLV is set, for example, based on the history of providing remote support (specifically, remote assistance or remote driving). For example, the number of times remote support is performed can be calculated according to the history of the location where remote support is performed. The frequency of occurrence of remote support can be calculated by calculating the number of times it is performed per unit time. By dividing these frequencies into multiple stages, the occurrence level RLV can be set for each area. The number of times it is performed may be calculated using time elements such as the day of the week (weekdays, holidays, etc.) and the time period (morning, afternoon, night).

[0022] In another example, the occurrence level RLV is set for each area using a prediction model that uses as variables the location of the road, the shape of the road, the presence or absence of an intersection, the presence or absence of a blind spot due to a structure, etc. In another example, the occurrence level RLV may be set using the above-mentioned time element.

[0023] The management DB12 is formed in a specified storage device, similar to the map DB11. The management DB12 stores moving body information MBL. The moving body information MBL is information for identifying a moving body MB. The moving body information MBL includes various information related to the moving body MB, such as the position information of the moving body MB, movement plan information of the moving body MB, and status information of the moving body MB. The position information and movement plan information are acquired by communication with the moving body MB. The movement plan information includes information on the destination of the moving body MB and information on the current route CRT of the moving body MB. The status information includes information on the current provision status of remote services by the management server MS (remote monitoring, remote assistance, or remote driving is being provided, or not being provided).

[0024] The mobile body information MBL also includes information on the free space FSP of the storage device of the mobile body MB in which log information of remote support is stored. Examples of log information include external information (e.g., image information of the surroundings of the mobile body MB) and internal information (e.g., information on the speed, acceleration, steering angle, etc. of the mobile body MB) transmitted by the mobile body MB to the management server MS when an event occurs in which the mobile body MB receives remote support (specifically, remote assistance or remote driving). The log information also includes instruction information received by the mobile body MB from the management server MS during the event in which the mobile body MB receives remote support, and control amount information of the traveling device (drive device, braking device, and steering device) of the mobile body MB based on this instruction information.

[0025] The management DB12 also stores operator information OPR. The operator information OPR is information for identifying the operator information OPR. The operator information OPR includes various information related to the operator OP, such as the operator OP's qualification information, schedule information, and status information. The qualification information indicates the category of the operator OP's driving license (e.g., large, medium, semi-medium, and normal). The schedule information indicates the operator OP's schedule for a certain period (e.g., from the next day to one month in the future). The status information indicates the remote service (remote monitoring, remote assistance, or remote driving) currently being provided by the operator OP.

[0026] The communication device 13 connects to an external device via a communication network. The communication network is not particularly limited, and wired and wireless networks can be used. Examples of the communication network include an Internet line, a World Wide Web (WWW), a telephone line, a Local Area Network (LAN), a Storage Area Network (SAN), and a Delay Tolerant Network (DTN). Examples of wireless communication include Wireless Fidelity (WiFi) and Bluetooth (registered trademark). The wireless communication may be in a form in which the management server MS directly communicates (Ad Hoc communication), or indirect communication via an access point. The communication destinations of the communication device 13 include a terminal of a mobile unit MB and a terminal of an operator OP.

[0027] The information processing device 14 is a computer that performs various types of information processing. The information processing device 14 includes at least one processor 14a and at least one memory 14b. The processor 14a includes a CPU (Central Processing Unit). The memory 14b is a volatile memory such as a DDR memory, and expands various programs used by the processor 14a and temporarily stores various types of information.

[0028] The processor 14a executes a program stored in the memory 14b to The control unit 10 performs processes related to remote support, such as management of the mobile unit MB and management of the operator OP. The processes related to remote support include the process of setting the occurrence level RLV described above. The process of setting the occurrence level RLV includes a process of setting the occurrence level RLV_A of remote support and a process of setting the occurrence level RVL_D of remote driving. The processes related to remote support include a process of proposing a driving route ART (hereinafter also referred to as an "avoidance route") that avoids the occurrence of at least one of remote support and remote driving. This proposal process will be described later.

[0029] 3. Proposal of avoidance route As described above, in remote services, when remote support is concentrated in a short period of time, it is expected that the processing load on the processor 14a will become huge, resulting in high communication costs. Therefore, in the embodiment, the processing load on the processor 14a is calculated. Also, the amount of communication transmitted or received per unit time between the mobile unit MB and the management server MS is calculated. Then, if the processing load is equal to or exceeds the upper limit load, or if the amount of communication per unit time is equal to or exceeds the upper limit amount, an avoidance route ART is generated. The generated avoidance route ART is transmitted to the mobile unit MB.

[0030] Figures 3 and 4 are diagrams for explaining the avoidance route ART generated in the proposal process. Figures 3 and 4 show a schematic map of an area AR including points P1 and P2. Point P1 is the current location of the mobile unit MB. Point P2 is the destination of the mobile unit MB. Time T1 shown at the bottom of Figures 3 and 4 is the current time. Times T2 and T3 are the times when the mobile unit MB is scheduled to arrive at the destination P2.

[0031] Fig. 3 illustrates a current driving route (hereinafter, also referred to as "current route") CRT from point P1 to point P2. Meanwhile, Fig. 4 illustrates an avoidance route ART. The current route CRT and the avoidance route ART are roads on which the moving body MB can travel. The current route CRT and the avoidance route ART are roads for vehicles registered in the database of a general car navigation system.

[0032] In Figs. 3 and 4, the area AR is divided into a plurality of zones CD. In the example shown in Figs. 3 and 4, the area AR is divided into a mesh shape, and a generation level RLV is set for each zone CD. The generation level RVL is set in at least two stages. When two stages of the generation level RVL are set, the generation level RVL is composed of a level where the frequency of occurrence of remote support is higher than the threshold value Th, and a level where the frequency is lower than the threshold value Th. As described above, the generation level RLV includes the generation levels RLV_A and RVL_D. Therefore, at least two stages are set for each of the generation levels RLV_A and RVL_D.

[0033] The current route CRT shown in Fig. 3 is a route that passes through the areas CD(2,2), CD(3,2), CD(4,3), and CD(4,4) having a level higher than the threshold Th, and the area CD(4,2) having a level lower than the threshold Th. In contrast, the avoidance route ART shown in Fig. 4 is a route that passes through the areas CD(2,2) and CD(4,4) having a level higher than the threshold Th, and the areas CD(2,3), CD(2,4), and CD(3,4) having a level lower than the threshold Th.

[0034] In the proposal process, an avoidance route ART is generated based on information on the points P1 and P2 and information on the occurrence level RLV. The avoidance route ART is, for example, the route from point P1 to point P2 that has the longest distance or time traveled through an area CD having a level lower than the threshold Th.

[0035] Information on the current route CRT may be used when generating the avoidance route ART. The avoidance route ART is, for example, a route that has a longer distance or time traveled through the area CD having a level lower than the threshold Th compared to the current route CRT. In another example, a travel route that greatly exceeds the travel distance or travel time along the current route CRT is excluded. Among the travel routes after this exclusion, the route that has the longest distance or time traveled through the area CD having a level lower than the threshold Th is selected. Or, among the travel routes after this exclusion, the route that has the longest distance or time traveled through the area CD having a level lower than the threshold Th is selected.

[0036] The generated avoidance route ART is transmitted to the moving object MB. It goes without saying that the moving object MB to which the avoidance route ART is transmitted is a moving object MB (e.g., a moving object MB in operation) that has established communication with the management server MS. However, as described above, the moving object information MBL includes information on the current provision status of remote services. Therefore, it is desirable to select the moving object MB to which the avoidance route ART is transmitted with reference to this provision status information.

[0037] For example, from the viewpoint of increasing the acceptance probability of the avoidance route ART, it is desirable to transmit the avoidance route ART to a moving body MB for which remote monitoring is being provided. A moving body MB for which remote assistance and remote driving are being provided is a moving body MB that is currently in need of these remote support. Therefore, such a moving body MB may request remote assistance or remote driving in the near future. In this regard, a moving body MB for which remote monitoring is being provided may not request remote assistance or remote driving. Therefore, by transmitting the avoidance route ART to a moving body MB for which remote monitoring is being provided, it is expected that the acceptance probability of the avoidance route ART will increase.

[0038] The generation of the avoidance route ART and transmission to the mobile MB may be performed for a mobile MB whose free space FSP is equal to or less than the lower limit capacity. The fact that the free space FSP is equal to or less than the lower limit capacity means that the mobile MB is approaching a situation where it will not be able to store log information for future remote support in its storage device. Therefore, even if the processing load is less than the upper limit load and the communication volume per unit time is less than the upper limit amount, the generation and transmission of the avoidance route ART may be performed when the free space FSP is equal to or less than the lower limit capacity. By accepting the avoidance route ART received by the mobile MB, it is possible to avoid the above-mentioned situation before it occurs.

[0039] 4. Example of processing by the management server 5 is a flowchart showing an example of processing that is performed by the management server MS (processor 14a) and is particularly related to the embodiment. The routine shown in FIG. 5 is repeatedly executed at a predetermined control period, for example.

[0040] In the routine shown in Fig. 5, first, various information is acquired (step S11). The various information acquired in step S11 includes mobile object information MBL, information on the processing load of the processor 14a, and the amount of communication per unit time transmitted or received between the mobile object MB and the management server MS. The mobile object information MBL is acquired from the management DB 12. The processing load of the processor 14a is calculated, for example, from the utilization rate of the processor 14a. The amount of communication per unit time is the amount of upstream (transmission) communication or the amount of downstream (reception) communication based on the management server MS. Since image information is transmitted from the mobile object MB, the amount of downstream (reception) communication is usually greater than the amount of upstream (transmission) communication.

[0041] Following the process of step S11, it is determined whether or not a first condition is satisfied (step S12). The first condition includes the following conditions (i) and (ii). (i) The processing load of the processor 14a is equal to or greater than the upper limit load. (ii) The amount of communication per unit time is equal to or greater than the upper limit. Regarding condition (i), the processing load of the processor 14a may be an instantaneous value, or may be an average value of the processing load over a predetermined period going back from the present (for example, several seconds to several tens of seconds).

[0042] If at least one of the conditions (i) and (ii) is satisfied, it is determined that the first condition is satisfied. If it is determined that the first condition is satisfied, the process of step S14 (described later) is performed. If it is determined that the first condition is not satisfied, it is determined whether or not the second condition is satisfied (step S13). The second condition includes the following condition (iii). (iii) The free space FSP is below the lower limit If the condition (iii) is satisfied, it is determined that the second condition is satisfied. If it is determined that the second condition is satisfied, the process of step S14 (described later) is performed. If it is determined that the second condition is not satisfied, the current process is terminated.

[0043] In the process of step S14, an avoidance route ART is generated. An example of the generation of the avoidance route ART is as described in the explanation of Figs. 3 and 4. At least one candidate for the avoidance route ART is generated. That is, two or more candidates for the avoidance route ART may be generated. In this case, these candidates differ from each other in the distance or time traveled through the area CD having a level lower than the threshold Th. Therefore, from among these candidates, the one that has the longest distance or time traveled through the area CD having a level lower than the threshold Th can be selected as the avoidance route ART.

[0044] Following the processing of step S14, the avoidance route ART is transmitted to the moving body MB (step S15). The moving body MB to which the avoidance route ART is transmitted differs between when the avoidance route ART is generated through the processing of step S12 and when the avoidance route ART is generated through the processing of step S13. That is, in the former case, the target of transmission of the avoidance route ART is a moving body MB with which communication has been established with the management server MS. However, as described above, it is desirable that the moving body MB to which the avoidance route ART is transmitted is selected by referring to information on the current provision status of the remote service. On the other hand, in the latter case, the moving body MB for which it is determined in the processing of step S13 that the second condition is satisfied is the target of transmission of the avoidance route ART. [Explanation of symbols]

[0045] 11...map database, 12...management database, 13...communication device, 14...information processing device, 14a...processor, 14b...memory, AR...area, CD...district, MS...management server, MB, MB1, MB2...mobile object, OP, OP1, OP2...operator, P1, P2...location, ART, CRT...driving route, FSP...free space in storage device, MAP...map information, MBL...mobile object information, OPR...operator information, RLV...remote support occurrence level

Claims

1. 1. A method for providing remote support to a plurality of moving objects, comprising: Calculating a processing load of a server that manages the remote support, or a communication volume per unit time transmitted or received between the target mobile object of the remote support and the server; acquiring location information of a current location and a destination of the target moving object and map information including the current location and the destination; when the processing load is equal to or greater than an upper limit load, or when the communication volume per unit time is equal to or greater than an upper limit volume, making a proposal to the target moving object regarding an avoidance route for avoiding the occurrence of remote support based on the location information and the map information; A remote support method comprising:

2. 2. The method of claim 1 , the step of providing a suggestion regarding an avoidance route comprises: generating the avoidance route in the server; transmitting the avoidance route from the server to the target moving object; A remote support method comprising:

3. 3. The method according to claim 1 or 2, The remote support includes remote assistance and remote driving of the target moving object, The avoidance route is a route for avoiding occurrence of at least one of the remote assistance and the remote driving. A remote support method comprising:

4. 3. The method according to claim 1 or 2, acquiring information on free space of a storage device in which log information of the remote support is stored in the target mobile object; when the processing load is less than the upper limit load and the communication volume per unit time is less than the upper limit volume, and when the available capacity is equal to or less than a lower limit volume, making a proposal regarding the avoidance route to the target moving object; The remote support method further comprises:

5. A system for providing remote support to a plurality of moving objects, comprising: A server for managing the remote support is provided, The server, A process of calculating a processing load of the server or a communication volume per unit time transmitted or received between the target mobile object of the remote support and the server; A process of acquiring location information of a current location and a destination of the target moving object and map information including the current location and the destination; a process of proposing to the target moving object, based on the location information and the map information, a route to avoid the occurrence of remote support, when the processing load is equal to or greater than an upper limit load, or when the communication volume per unit time is equal to or greater than an upper limit volume; A remote support system configured to perform the above.

Citation Information

Patent Citations

  • Automatic driving system, automatic driving control method, and automatic driving control program

    JP2022174598A

  • Server and vehicle serviced by the same

    JP2020159866A

  • Update information distribution system, update information distribution method, and update information distribution program

    JP6551127B2

  • Vehicle driving route control system, vehicle driving route control device, and vehicle driving route control method

    JP7211490B2