Management device
The management device addresses premature assistance requests in autonomous vehicles by waiting for a defined time after detecting an abnormality before determining the need for assistance, thereby reducing unnecessary interventions.
Patent Information
- Application Number
- JP2023216856
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-12-22
- Publication Date
- 2025-07-03
AI Technical Summary
Existing technologies lack a mechanism to determine whether an abnormality in an autonomous vehicle is temporary or not, leading to potential premature requests for assistance that may be unnecessary.
A management device that includes processors and storage devices to manage mobility states, determining if an abnormal state exists and requiring assistance only after a waiting time has elapsed since the abnormal state began.
This approach suppresses unnecessary assistance requests by waiting for a predetermined time before determining the need for assistance, allowing for potential recovery or resolution of temporary issues.
Smart Images

Figure 2025099879000001_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a technology for managing mobility.
Background Art
[0002] Patent Document 1 discloses a management device for remotely controlling an autonomous vehicle. The management device determines a processing order based on the working time and priority for remote control, and assigns the remote control work to an operator according to the determined processing order.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] According to the above-described Patent Document 1, when an abnormality occurs in an autonomous vehicle, there is no mechanism for determining whether the abnormality is temporary. As a result, there is a risk of making a premature request for assistance that is actually unnecessary. Therefore, a technology that can appropriately determine whether assistance is required for an autonomous vehicle is desired.
Means for Solving the Problems
[0005] One aspect of the present disclosure relates to a management device for managing mobility. The management device includes one or more processors and one or more storage devices that store mobility management information for managing a mobility state indicating the state of mobility. The one or more processors determine whether the mobility state is an abnormal state based on the mobility management information. When one or more processors determine that the mobility state is an abnormal state and a waiting time has elapsed since the mobility state became the abnormal state, they determine that mobility assistance is required.
Advantages of the Invention
[0006] According to the present disclosure, when it is determined that the mobility state is an abnormal state and a waiting time has elapsed since the mobility state became the abnormal state, it is determined that mobility assistance is required. Thereby, it is possible to suppress making a request for assistance that would originally be unnecessary prematurely.
Brief Description of the Drawings
[0007]
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Modes for Carrying Out the Invention
[0008] Embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0009] 1. Outline of Mobility Management System FIG. 1 is a conceptual diagram for explaining the outline of the mobility management system 1 according to the present embodiment. The mobility management system 1 is a system for managing the mobility 100. The mobility management system 1 manages the state of the mobility 100. Further, when the mobility management system 1 receives a remote support request from the mobility 100, it may perform remote support for the mobility 100. Remote support is a concept including, for example, remote monitoring, remote assistance, and remote driving.
[0010] The mobility management system 1 includes, for example, the mobility 100, the remote operator terminal 200, and the management device 300. The mobility 100, the remote operator 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 operator terminal 200 and the management device 300 via a wireless communication network. The remote operator terminal 200 and the management device 300 can communicate with each other via a wired / wireless communication network.
[0011] The mobility 100 is a movable moving body. The mobility 100 has an autonomous movement function. The mobility 100 may have a self-diagnosis function for determining the presence or absence of its own abnormality. The type of the mobility 100 to be managed is not limited to one and may be plural. For example, the mobility 100 is a vehicle traveling on a public road. As another example, the mobility 100 may be a vehicle used in a factory. As still another example, the mobility 100 may be a special small vehicle. As still another example, the mobility 100 may be a construction machine. As still another example, the mobility 100 may be a robot. As still another example, the mobility 100 may be a flying object. As still another example, the mobility 100 may be a ship. As still another example, the mobility 100 may be a ride in an amusement park.
[0012] The remote operator terminal 200 is a terminal device used when the remote operator O remotely supports the mobility 100. That is, the remote operator terminal 200 is configured to be used by the remote operator O for remote support of the mobility 100. Examples of the remote operator terminal 200 include a cockpit-type terminal, a PC, a tablet, a smartphone, etc.
[0013] The management device 300 is a computer that manages the mobility management system 1. The management device 300 manages the mobility 100. The management device 300 may be composed of a plurality of servers that perform distributed processing. For example, the management device 300 may manage a plurality of remote operators O and a plurality of remote operator terminals 200. Further, the management device 300 may allocate the remote operator O and the remote operator terminal 200 to the remote support of the mobility 100 in response to a remote support request.
[0014] The management device 300 includes one or more processors 310 (hereinafter simply referred to as the processor 310), one or more storage devices 320 (hereinafter simply referred to as the storage device 320), and a communication device 330. The communication device 330 communicates with the mobility 100 and the remote operator terminal 200.
[0015] Processor 310 executes various processes. Examples of processor 310 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 combinations thereof. Processor 310 can also be referred to as circuitry or processing circuitry. Circuitry is hardware programmed to implement the described functions or hardware that executes functions. Storage device 320 stores various information. Examples of storage device 320 include volatile memory, non-volatile memory, HDD, SSD, etc. The functions of management device 300 may be realized by the cooperation of processor 310 that executes a management program and storage device 320. The management program is stored in storage device 320. Alternatively, the management program may be recorded on a computer-readable recording medium. The management program may be provided via a network.
[0016] The various information stored in storage device 320 includes mobility management information 321. Mobility management information 321 is information that manages a mobility state indicating the state of mobility 100. The mobility state includes, for example, the self-diagnosis result (also referred to as the self-state) of mobility 100 itself and the communication state with mobility 100. That is, mobility management information 321 includes information acquired from mobility 100 and information recorded by the monitoring of management device 300. Details of the mobility state will be described later.
[0017] The processor 310 (management device 300) according to the present embodiment executes assistance determination processing. The assistance determination processing by the processor 310 is executed, for example, while the mobility 100 is running. The outline of the assistance determination processing is as follows. The processor 310 determines whether the mobility state is an abnormal state based on the mobility management information 321. Then, when the mobility state is determined to be an abnormal state and a waiting time has elapsed since the mobility state became an abnormal state, the processor 310 determines that assistance for the mobility 100 is necessary. Thereby, it is possible to suppress making a premature assistance request that would otherwise be unnecessary.
[0018] 2. Examples of Mobility States FIG. 2 is a diagram showing an example of an abnormal state of the mobility state. As described above, the mobility state includes the self-diagnosis result of the mobility 100 and the communication state with the mobility 100. The management device 300 determines whether the mobility state is an abnormal state. Hereinafter, the details of the determination example of the abnormal state will be described.
[0019] 2-1. First Example (A) in FIG. 2 shows a determination example of an abnormal state based on the self-diagnosis result of the mobility 100. The mobility management information 321 includes self-diagnosis result information 322. The self-diagnosis result information 322 is information indicating the self-diagnosis result of whether the mobility 100 itself is normal or abnormal. The self-diagnosis result information 322 is acquired from the mobility 100 via communication. The management device 300 determines whether the mobility 100 has detected an abnormality based on the self-diagnosis result information 322. When it is determined that the mobility 100 has detected an abnormality, the management device 300 determines that the mobility state is an abnormal state.
[0020] 2-2. Second Example (B) in FIG. 2 shows an example of determining the mobility state based on the communication state of the mobility 100. The mobility management information 321 includes communication state information 323. The communication state information 323 indicates the communication state with the mobility 100. Examples of the communication state include the presence or absence of communication, communication speed, communication quality, communication delay, etc. The management device 300 can obtain (detect, estimate) the communication state based on the data received from the mobility 100. For example, when the mobility 100 travels through a predetermined section CDS (e.g., tunnel) where communication interruption occurs, the communication between the mobility 100 and the management device 300 is interrupted. In this case, the communication state information 323 indicates that communication interruption has occurred. When the communication between the management device 300 and the mobility 100 is interrupted, the management device 300 determines that the mobility state is an abnormal state.
[0021] 3. Outline of Assistance Judgment Consider the assistance judgment when the mobility state becomes an abnormal state. For example, in the first example described above, as shown in (A) in FIG. 2, when the mobility 100 detects an abnormality, that is, when the self-diagnosis result information 322 obtained from the mobility 100 includes an abnormality, the mobility 100 performs its own recovery process. In this case, although there is a possibility that the mobility state will return to normal after the completion of the recovery process by the mobility 100, the management device 300 may determine that assistance for the mobility 100 is required during the execution of the recovery process. In the first example, it is preferable to determine whether assistance for the mobility 100 is required in consideration of the possibility that the recovery process may succeed if waiting for a certain period. Note that the recovery process includes, for example, a process of restarting the device where an abnormality is presumed to have occurred.
[0022] As another example, in the second example described above, it is the case where the mobility 100 travels through a predetermined section CDS where communication interruption occurs. In this case, although there is a possibility that communication will be restored if the mobility 100 passes through the predetermined section CDS, the management device 300 may determine that assistance for the mobility 100 is required. In the second example, it is preferable to determine whether assistance for the mobility 100 is required in consideration of the possibility that communication will be restored if waiting for a certain period.
[0023] Therefore, when the mobility state of the management device 300 according to the present embodiment is determined to be an abnormal state and a waiting time has elapsed since the mobility state became the abnormal state, it is determined that assistance for the mobility 100 is necessary. The waiting time may be a fixed value (default value) or may be variably set according to the situation. Hereinafter, details of an example of assistance determination will be described.
[0024] 4. Example of Assistance Determination 4-1. First Example FIG. 3 is a diagram showing a first example of a processing sequence for assistance determination. According to the first example of assistance determination, when the mobility 100 detects an abnormality, that is, when the self-diagnosis result information 322 includes an abnormality, the management device 300 does not determine that assistance for the mobility is necessary until the waiting time has elapsed.
[0025] The management device 300 may estimate the time required from when the mobility 100 detects an abnormality until the recovery process is completed (also referred to as the required time). When the self-diagnosis result information 322 includes information on the abnormality detection location indicating the location where the mobility 100 detects an abnormality, the management device 300 may estimate the required time based on list information including the required time associated with the abnormality detection location. For example, the list information includes information such as the required time is 60 seconds when the abnormality detection location is a communication device mounted on the mobility 100. After estimating the required time, the management device 300 may set the waiting time to be longer than the estimated required time. In addition, when the required time is estimated, a time longer than the time until the estimation of the required time is completed may be set as the initial value of the waiting time. As another example, the management device 300 may disable the process related to assistance determination so that assistance determination is not performed until the estimation of the required time is completed.
[0026] After setting the standby time, the management device 300 determines whether assistance for the mobility 100 is required after the standby time has elapsed. For example, as shown in (A) of FIG. 3, if the mobility state (self-state) has returned from an abnormal state to a normal state after the standby time has elapsed, that is, if the self-diagnosis result information 322 has switched from abnormal to normal, the management device 300 determines that assistance for the mobility 100 is not required.
[0027] As another example, as shown in (B) of FIG. 3, if the mobility state (self-state) remains in an abnormal state after the standby time has elapsed, that is, if the self-diagnosis result information 322 maintains the abnormality, the management device 300 determines that assistance for the mobility 100 is required.
[0028] 4-2. Second Example FIG. 4 is a diagram showing a second example of the processing sequence for assistance determination. According to the second example of assistance determination, when communication with the mobility 100 is interrupted, the management device 300 does not determine that mobility assistance is required until the standby time has elapsed.
[0029] The management device 300 may estimate whether the mobility 100 exists in a predetermined section CDS (e.g., tunnel) where communication interruption occurs. For example, the mobility management information 321 further includes the position information 324 of the mobility 100 (hereinafter simply referred to as the position information 324), and the storage device 320 further stores the map information 325. The position information 324 includes the current position information indicating the current position of the mobility 100 and the history of the position information of the mobility 100 (also referred to as the history position information). The position information 324 is obtained from the mobility 100. The position information 324 obtained by the mobility 100 is obtained, for example, by a sensor such as GPS mounted on the mobility 100. The map information 325 includes information on a predetermined section CDS (e.g., tunnel) where communication interruption occurs.
[0030] Consider the case where the mobility 100 exists in the predetermined section CDS. In this case, sensors such as GPS installed in the mobility 100 cannot obtain the current position information. Therefore, by using the historical position information in the position information 324, it is possible to estimate whether the mobility 100 has entered the predetermined section CDS, that is, whether the mobility 100 exists in the predetermined section CDS. Therefore, when the communication with the mobility 100 is interrupted, that is, when the communication status information 323 includes information regarding the communication interruption, the management device 300 estimates whether the mobility 100 exists in the predetermined section CDS based on the map information 325 and the historical position information. For example, when the position of the mobility 100 estimated from the historical position information is included in the predetermined section CDS, the management device 300 estimates that the mobility 100 exists in the predetermined section CDS.
[0031] When it is estimated that the mobility 100 exists in the predetermined section CDS, the management device 300 may estimate the time required for the mobility 100 to pass through the predetermined section CDS (also referred to as the passing time). The passing time is estimated based on, for example, the distance information of the predetermined section CDS obtained from the map information 325 and the vehicle speed information of the mobility 100. As the vehicle speed information, for example, the one last obtained from the mobility 100 is used. Alternatively, the vehicle speed of the mobility 100 may be estimated based on the historical position information. After estimating the passing time, the management device 300 may set the standby time longer than the estimated passing time. In addition, when the passing time is estimated, a time longer than the time until the estimation of the passing time is completed may be set as the initial value of the standby time. As another example, the management device 300 may invalidate the process related to the assistance determination so as not to perform the assistance determination until the estimation of the passing time is completed.
[0032] After setting the standby time, the management device 300 determines whether assistance for the mobility 100 is required after the standby time has elapsed. For example, as shown in (A) of FIG. 4, if the mobility state (communication state) has returned from an abnormal state to a normal state after the standby time has elapsed, that is, if the communication state information 323 has switched from communication interruption to information regarding reconnection, the management device 300 determines that assistance for the mobility 100 is not required.
[0033] As another example, as shown in (B) of FIG. 4, if the mobility state (communication state) remains in an abnormal state after the standby time has elapsed, that is, if the communication state information 323 maintains information regarding communication interruption, the management device 300 determines that assistance for the mobility 100 is required.
[0034] 5. Processing Example FIG. 5 is a flowchart showing an example of assistance determination processing by the management device 300 according to the present embodiment.
[0035] In step 100, the management device 300 acquires the mobility state. Thereafter, the process proceeds to step S110. Note that the mobility state is managed by the mobility management information 321.
[0036] In step S110, the management device 300 determines whether the mobility state is an abnormal state. If it is determined that the mobility state is an abnormal state (step S110; Yes), the process proceeds to step S120. Otherwise (step S110; No), the process ends.
[0037] In step S120, the management device 300 determines whether the standby time has elapsed since the mobility state became an abnormal state. If it is determined that the standby time has elapsed (step S120; Yes), the process proceeds to step S130. Otherwise (step S120; No), the process ends.
[0038] In step S130, the management device 300 determines that assistance for the mobility 100 is required.
[0039] 6. Effects According to the present embodiment, when the mobility state is determined to be an abnormal state and a waiting time has elapsed since the mobility state became abnormal, it is determined that mobility assistance is required. For example, when the mobility 100 performs a recovery process after detecting an abnormality, or when the mobility 100 exists in a predetermined section CDS (e.g., tunnel) where a temporary communication interruption occurs, there is a possibility of recovering from the abnormal state after waiting for a while. In such a case, it is possible to suppress making a premature assistance request that was originally unnecessary.
[0040] 7. Other Embodiments Other embodiments propose a response when it is determined that assistance for the mobility 100 is required.
[0041] FIG. 6 is a diagram showing an example of a processing sequence of assistance determination according to other embodiments. When it is determined that assistance for the mobility 100 is required, the management device 300 transmits assistance request information 410 to the service institution 400 via the communication device 330. The service institution 400 is an institution that provides a tow service. Examples of the service institution 400 include JAF, the police, etc. The assistance request information 410 includes the position of the mobility 100 when the mobility state becomes an abnormal state or when it is determined that assistance for the mobility 100 is required. That is, the storage device 320 according to other embodiments includes at least the position information 324. The communication device 330 is configured to be able to communicate with the service institution 400.
[0042] According to other embodiments, assistance request information 410 including the position of the mobility 100 when the mobility state becomes an abnormal state or when it is determined that mobility assistance is required is transmitted to the service institution 400. Thereby, assistance for the mobility 100 can be smoothly performed.
[0043] Furthermore, the transmission of the assistance request information 410 to the service institution 400 is not limited to the management device 300 only. For example, as shown in (A) of FIG. 6, when the mobility 100 does not return even after performing the return process, the mobility 100 may transmit the assistance request information 410 to the service institution 400.
Explanation of Signs
[0044] 1…Mobility management system, 100…Mobility, 200…Remote operator terminal, 300…Management device, 310…Processor, 320…Storage device, 321…Mobility management information, 322…Self-diagnosis result information, 323…Communication status information, 324…Location information, 325…Map information, 330…Communication device, 400…Service institution, 410…Assistance request information
Claims
1. A management device for managing mobility, comprising: one or more processors; one or more storage devices storing mobility management information for managing a mobility state indicating the state of the mobility; and is configured to: the one or more processors are configured to: determine whether the mobility state is an abnormal state based on the mobility management information; when it is determined that the mobility state is an abnormal state and a waiting time has elapsed since the mobility state became the abnormal state, determine that assistance for the mobility is required configured as a management device.
2. The management device according to claim 1, wherein the mobility state includes a communication state of the mobility, and the one or more processors are configured to determine that the mobility state is the abnormal state when communication with the mobility is interrupted. a management device.
3. The management device according to claim 2, wherein the one or more storage devices further store map information including a predetermined section where communication interruption occurs, the mobility management information includes position information of the mobility, and the one or more processors are further configured to: estimate whether the mobility exists in the predetermined section based on the map information and a history of the position information; when it is estimated that the mobility exists in the predetermined section, estimate the time required for the mobility to pass through the predetermined section; set the waiting time to be longer than the estimated time configured as a management device.
4. The management device according to claim 1, wherein the mobility management information includes self-diagnosis result information indicating a result of determining whether the mobility itself is normal or abnormal, and the one or more processors are further configured to: determine whether the mobility has detected an abnormality based on the self-diagnosis result information; estimate the time required for the mobility to complete a recovery process after detecting the abnormality; set the waiting time to be longer than the estimated time configured as a management device.
5. The management device according to any one of claims 1 to 4, comprising a communication device capable of communicating with a service institution that provides a load service, the mobility management information includes position information of the mobility, the one or more processors are When the mobility state becomes the abnormal state, or when it is determined that assistance for the mobility is necessary, assistance request information including the position of the mobility at that time is transmitted to the service organization via the communication device. configured to management device.
Citation Information
Patent Citations
Server and communication system
JP2019185426A
Control apparatus
JP2019185279A