Processing method, processing system, and processing program

The processing method and system address the discrepancy in situation recognition by monitoring envelope violations and adjusting safety envelopes, improving vehicle responsiveness to other vehicles.

JP7586294B2Active Publication Date: 2024-11-19DENSO CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023508789
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-03-26
Filing Date
2022-02-17
Publication Date
2024-11-19
Estimated Expiration
2042-02-17

AI Technical Summary

Technical Problem

There is a possibility of discrepancy in situation recognition between a host vehicle and a target vehicle, affecting the response to the behavior of the other party's moving object.

Method used

A processing method and system that monitor for envelope violations, generate warning information, and set constraints on operation control to improve responsiveness by ensuring common recognition of envelope violations between vehicles.

Benefits of technology

Enhances the ability of vehicles to respond to the behavior of other vehicles by ensuring common recognition and adjustment of safety envelopes based on warning information and feedback.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007586294000001
    Figure 0007586294000001
  • Figure 0007586294000002
    Figure 0007586294000002
  • Figure 0007586294000003
    Figure 0007586294000003
Patent Text Reader

Abstract

In order to carry out a process related to driving of a host moving body that is capable of communicating with a target moving body, this processing method, which is executed by a processor, comprises: acquiring from the target moving body warning information warning about an envelope violation which is a violation of a safety envelope defining, in the target moving body, the safety of an intended function with respect to the host moving body; and adjusting the safety envelope with respect to the target moving body in response to acquisition of the warning information.
Need to check novelty before this filing date? Find Prior Art

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on Patent Application No. 2021-53969 filed in Japan on March 26, 2021, and the contents of the original application are incorporated by reference in their entirety. [Technical field]

[0002] The present disclosure relates to a processing technique for performing processing related to driving of a mobile object. [Background technology]

[0003] The technology disclosed in Patent Document 1 plans driving control related to the navigation operation of the host vehicle according to detection information related to the internal and external environment of the host vehicle. Therefore, when it is determined that there is a potential accident liability based on the safety model according to the driving policy and the detection information, a restriction is imposed on the driving control. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6708793 Summary of the Invention

[0005] However, in the technology disclosed in Patent Document 1, there is a possibility that a discrepancy may occur in the situation recognition between the host vehicle and the target vehicle, which may affect the response to the behavior of the other moving object.

[0006] An object of the present disclosure is to provide a processing method that promotes improvement of response capability to the behavior of a partner moving object. Yet another object of the present disclosure is to provide a processing system that promotes improvement of response capability to the behavior of a partner moving object. Yet another object of the present disclosure is to provide a processing program that promotes improvement of response capability to the behavior of a partner moving object.

[0007] The technical means of the present disclosure for solving the problems will be described below.

[0012] The present disclosure one The aspect is A processing method executed by a processor to perform processing related to operation of a host vehicle capable of communicating with a target vehicle, comprising: Monitoring an envelope violation, which is a violation of a security envelope that establishes security of an intended function between the host mobile and the target mobile; When an envelope violation is recognized in the host mobile unit, warning information for warning the target mobile unit of the envelope violation is generated so as to be transmitted to the target mobile unit. 、 Obtaining feedback information for feeding back the acquisition of warning information from a target moving object; Setting constraints on driving control of a host vehicle when feedback information is not obtained; Includes. The present disclosure two The aspect is A processing method executed by a processor to perform processing related to operation of a host vehicle capable of communicating with a target vehicle, comprising: Monitoring an envelope violation, which is a violation of a security envelope that establishes security of an intended function between the host mobile and the target mobile; generating, when an envelope violation is recognized in the host mobile unit, warning information for warning the envelope violation to be transmitted to the target mobile unit; Obtaining feedback information for feeding back the acquisition of warning information from a target moving object; and setting constraints on driving control of the host vehicle if feedback information is not obtained.

[0013] The present disclosure three The aspect is A processing system including a processor and configured to perform processing related to operation of a host vehicle capable of communicating with a target vehicle, The processor Monitoring an envelope violation, which is a violation of a security envelope that establishes security of an intended function between the host mobile and the target mobile; generating, when an envelope violation is recognized in the host mobile unit, warning information for warning the envelope violation to be transmitted to the target mobile unit; Obtaining feedback information for feeding back the acquisition of warning information from a target moving object; and setting constraints on driving control of the host vehicle if feedback information is not obtained.

[0014] The present disclosure four The aspect is A processing program stored in a storage medium, the processing program including instructions to be executed by a processor to perform processing related to the operation of a host vehicle capable of communicating with a target vehicle, The command is, monitoring, at the host mobile unit, for an envelope violation that is a violation of a security envelope that establishes security of the intended functionality between the host mobile unit and the target mobile unit; generating, when an envelope violation is recognized in the host mobile unit, warning information (Iw) for warning the envelope violation to be transmitted to the target mobile unit; Obtaining feedback information for feeding back the acquisition of warning information from a target moving object; and setting constraints on driving control of the host vehicle if feedback information is not obtained.

[0015] These one ~ fourIn the host mobile unit of the present embodiment, an envelope that is a violation of a safety envelope that sets the safety of the intended functions between the host mobile unit and the target mobile unit is monitored. When an envelope violation is recognized, the host mobile unit generates warning information that warns of the envelope violation and transmits it to the target mobile unit. In this way, the envelope violation warned by the host mobile unit can be commonly recognized by the target mobile unit, which can promote the improvement of the response capability to the behavior of the other mobile unit. [Brief description of the drawings]

[0016] [Figure 1] 1 is an explanatory table showing explanations of terms used in the present disclosure. [Diagram 2] 1 is an explanatory table showing explanations of terms used in the present disclosure. [Diagram 3] 1 is an explanatory table showing explanations of terms used in the present disclosure. [Figure 4] 1 is an explanatory table showing definitions of terms used in the present disclosure. [Diagram 5] 1 is an explanatory table showing definitions of terms used in the present disclosure. [Figure 6] 1 is a block diagram showing a processing system according to a first embodiment; [Figure 7] 1 is a schematic diagram showing a driving environment of a vehicle to which a first embodiment is applied; [Figure 8] 1 is a schematic diagram showing a driving environment of a vehicle to which a first embodiment is applied; [Figure 9] 1 is a block diagram showing a processing system according to a first embodiment; [Figure 10] 1 is a schematic diagram showing an example of a lane structure and a processing method according to a first embodiment; [Figure 11] 1 is a schematic diagram showing an example of a lane structure and a processing method according to a first embodiment; [Figure 12] 1 is a schematic diagram showing an example of a lane structure and a processing method according to a first embodiment; [Figure 13] 1 is a schematic diagram showing an example of a lane structure and a processing method according to a first embodiment; [Figure 14]4 is a flowchart showing a processing method according to the first embodiment. [Figure 15] 4 is a flowchart showing a processing method according to the first embodiment. [Figure 16] 10 is a flowchart showing a processing method according to a second embodiment. [Figure 17] 10 is a flowchart showing a processing method according to a second embodiment. [Figure 18] FIG. 13 is a block diagram showing a processing system according to a third embodiment. [Figure 19] FIG. 13 is a block diagram showing a processing system according to a fourth embodiment. [Figure 20] FIG. 13 is a block diagram showing a processing system according to a fifth embodiment. [Figure 21] FIG. 13 is a block diagram showing a processing system according to a sixth embodiment. [Figure 22] FIG. 13 is a block diagram showing a processing system according to a sixth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Hereinafter, multiple embodiments according to the present disclosure will be described with reference to the drawings. In addition, by assigning the same reference numerals to corresponding components in each embodiment, duplicated descriptions may be omitted. In addition, when only a part of the configuration is described in each embodiment, the configuration of the other embodiment described above can be applied to the other parts of the configuration. Furthermore, in addition to the combination of configurations explicitly stated in the description of each embodiment, configurations of multiple embodiments can be partially combined together even if not explicitly stated, as long as there is no particular problem with the combination.

[0018] 1 to 5 show explanations of terms related to each embodiment of the present disclosure. However, the definitions of terms are not to be interpreted as being limited to the explanations shown in FIGS. 1 to 5, but are to be interpreted within the scope of the gist of the present disclosure.

[0019] First embodiment The processing system 1 of the first embodiment shown in FIG. 6 performs processing related to driving of a moving object (hereinafter, referred to as driving-related processing). The moving object that the processing system 1 targets for the driving-related processing is a vehicle 2 shown in FIGS. 7 and 8. In the first embodiment, a first vehicle 2a and a second vehicle 2b that can communicate with each other directly or indirectly via a communication infrastructure are assumed as the vehicles 2 to which the processing system 1 is applied. From the viewpoint of the first vehicle 2a shown in FIG. 7, the ego-vehicle 2a corresponds to the host moving object, while the second vehicle 2b, which is also an other road user 3 present in the traveling environment of the ego-vehicle 2a, corresponds to the target moving object. On the other hand, from the viewpoint of the second vehicle 2b shown in FIG. 8, the ego-vehicle 2b corresponds to the host moving object, while the first vehicle 2a, which is also an other road user 3 present in the traveling environment of the ego-vehicle 2b, corresponds to the target moving object.

[0020] The vehicle 2 shown in Figs. 7 and 8 is a road user, such as a car or truck, in which autonomous driving is performed. Autonomous driving is classified into levels according to the degree of manual intervention by the occupant in a dynamic driving task (hereinafter referred to as DDT). Autonomous driving may be realized by autonomous driving control, such as conditional driving automation, high driving automation, or full driving automation, in which a system executes all DDTs when activated. Autonomous driving may be realized in advanced driving assistance control, such as driving assistance or partial driving automation, in which a driver as an occupant executes some or all of the DDTs. Autonomous driving may be realized by either one of the autonomous driving control and the advanced driving assistance control, a combination of them, or a switch between them.

[0021] The vehicle 2 is equipped with a sensor system 5, a communication system 6, a map DB (Data Base) 7, and an information presentation system 4, all of which are shown in Figs. 6 and 9. The sensor system 5 acquires sensor data that can be used by the processing system 1 by detecting the external and internal worlds of the vehicle 2. To this end, the sensor system 5 is configured to include an external sensor 50 and an internal sensor 52.

[0022] The external sensor 50 may detect a target object present in the external world of the vehicle 2. The external sensor 50 of the target detection type is at least one of a camera, a LiDAR (Light Detection and Ranging / Laser Imaging Detection and Ranging), a laser radar, a millimeter wave radar, an ultrasonic sonar, etc. The external sensor 50 may detect the atmospheric condition in the external world of the vehicle 2. The external sensor 50 of the atmospheric detection type is at least one of a outside air temperature sensor, a humidity sensor, etc.

[0023] The internal sensor 52 may detect a specific physical quantity related to vehicle motion (hereinafter, referred to as motion physical quantity) in the internal world of the vehicle 2. The internal sensor 52 of the physical quantity detection type is at least one of a speed sensor, an acceleration sensor, a gyro sensor, etc. The internal sensor 52 may detect the state of an occupant in the internal world of the vehicle 2. The internal sensor 52 of the occupant detection type is at least one of an actuator sensor, a driver status monitor, a biological sensor, a seating sensor, an in-vehicle equipment sensor, etc. Here, as the actuator sensor in particular, at least one of an accelerator sensor, a brake sensor, a steering sensor, etc. that detects the operation state of the occupant related to the motion actuator of the vehicle 2 is adopted.

[0024] The communication system 6 acquires communication data that can be used by the processing system 1 through wireless communication. The communication system 6 may receive a positioning signal from a satellite of a Global Navigation Satellite System (GNSS) that exists in the outside world of the vehicle 2. The positioning type communication system 6 is, for example, a GNSS receiver. The communication system 6 may transmit and receive a communication signal between the vehicle 2 and a V2X system that exists in the outside world of the vehicle 2. The V2X type communication system 6 is, for example, at least one of a Dedicated Short Range Communications (DSRC) communication device and a Cellular V2X (C-V2X) communication device. The communication between the vehicles 2 (2a, 2b) assumed in the first embodiment can be realized through the V2X type communication system 6 in each of the vehicles 2. The communication system 6 may transmit and receive a communication signal between a terminal that exists in the inside world of the vehicle 2. The terminal communication type communication system 6 is, for example, at least one of a Bluetooth (Bluetooth: registered trademark) device, a Wi-Fi (registered trademark) device, an infrared communication device, and the like.

[0025] The map DB 7 stores map data that can be used by the processing system 1. The map DB 7 includes at least one type of non-transitory tangible storage medium, such as a semiconductor memory, a magnetic medium, or an optical medium. The map DB 7 may be a DB of a locator that estimates the self-state quantity of the vehicle 2 including the self-position. The map DB may be a DB of a navigation unit that navigates the driving route of the vehicle 2. The map DB 7 may be constructed by combining multiple types of DBs.

[0026] The map DB 7 acquires and stores the latest map data by communication with an external center via, for example, a V2X type communication system 6. The map data is digitized in two dimensions or three dimensions as data representing the driving environment of the vehicle 2. Digital data of a high-precision map may be adopted as the three-dimensional map data. The map data may include road data representing at least one of the position coordinates, shape, and road surface condition of a road structure. The map data may include marking data representing at least one of the position coordinates and shape of road signs, road indications, and dividing lines attached to a road. The marking data included in the map data may represent landmarks such as traffic signs, arrow markings, lane markings, stop lines, directional signs, landmark beacons, rectangular signs, business signs, or changes in road line patterns. The map data may include structure data representing at least one of the position coordinates and shape of buildings and traffic lights facing the road. The marking data included in the map data may represent landmarks such as street lights, road edges, reflectors, poles, or the backs of road signs.

[0027] The information presentation system 4 presents notification information to the occupants including the driver of the vehicle 2. The information presentation system 4 is configured to include a visual presentation unit, an auditory presentation unit, and a cutaneous sensation presentation unit. The visual presentation unit presents the notification information by stimulating the occupant's vision. The visual presentation unit is at least one of a head-up display (HUD), a multi-function display (MFD), a combination meter, a navigation unit, and a light-emitting unit. The auditory presentation unit presents the notification information by stimulating the occupant's hearing. The auditory presentation unit is at least one of a speaker, a buzzer, and a vibration unit. The cutaneous sensation presentation unit presents the notification information by stimulating the occupant's cutaneous sensation. The cutaneous sensation stimulated by the cutaneous sensation presentation unit includes at least one of a touch sense, a temperature sense, and a wind sense. The cutaneous sensation providing unit is at least one of a steering wheel vibration unit, a driver's seat vibration unit, a steering wheel reaction force unit, an accelerator pedal reaction force unit, a brake pedal reaction force unit, an air conditioning unit, and the like.

[0028] As shown in FIG. 6, the processing system 1 is connected to a sensor system 5, a communication system 6, a map DB 7, and an information presentation system 4 via at least one of, for example, a LAN (Local Area Network), a wire harness, an internal bus, and a wireless communication line. The processing system 1 includes at least one dedicated computer. The dedicated computer constituting the processing system 1 may be an integrated ECU (Electronic Control Unit) that integrates the driving control of the vehicle 2. The dedicated computer constituting the processing system 1 may be a determination ECU that determines the DDT in the driving control of the vehicle 2. The dedicated computer constituting the processing system 1 may be a monitoring ECU that monitors the driving control of the vehicle 2. The dedicated computer constituting the processing system 1 may be an evaluation ECU that evaluates the driving control of the vehicle 2.

[0029] The dedicated computer constituting the processing system 1 may be a navigation ECU that navigates the driving route of the vehicle 2. The dedicated computer constituting the processing system 1 may be a locator ECU that estimates the self-state quantity including the self-position of the vehicle 2. The dedicated computer constituting the processing system 1 may be an actuator ECU that controls a motion actuator of the vehicle 2. The dedicated computer constituting the processing system 1 may be an HCU (Human Machine Interface (HMI) Control Unit) that controls the presentation of information in the vehicle 2. The dedicated computer constituting the processing system 1 may be at least one external computer that constitutes an external center or a mobile terminal capable of communicating via the communication system 6, for example.

[0030] The dedicated computer constituting the processing system 1 has at least one memory 10 and one processor 12. The memory 10 is at least one type of non-transitory tangible storage medium, such as a semiconductor memory, a magnetic medium, or an optical medium, that non-temporarily stores computer-readable programs and data. The processor 12 includes at least one type of core, such as a central processing unit (CPU), a graphics processing unit (GPU), or a reduced instruction set computer (RISC)-CPU.

[0031] The processor 12 executes a plurality of instructions included in a processing program stored in the memory 10 as software. In this way, the processing system 1 constructs a plurality of functional blocks for performing driving-related processing of the vehicle 2. In this manner, in the processing system 1, the processing program stored in the memory 10 causes the processor 12 to execute a plurality of instructions to perform driving-related processing of the vehicle 2, thereby constructing a plurality of functional blocks. The plurality of functional blocks constructed by the processing system 1 include a detection block 100, a planning block 120, a risk monitoring block 140, and a control block 160, as shown in FIG. 8.

[0032] The detection block 100 acquires sensor data from the external sensor 50 and the internal sensor 52 of the sensor system 5. The detection block 100 acquires communication data from the communication system 6. The detection block 100 acquires map data from the map DB 7. The detection block 100 detects the internal and external environments of the vehicle 2 by fusing these acquired data as inputs. By detecting the internal and external environments, the detection block 100 generates detection information to be provided to the subsequent planning block 120 and risk monitoring block 140. In this way, when generating the detection information, the detection block 100 acquires data from the sensor system 5 and the communication system 6, recognizes or understands the meaning of the acquired data, and integrates the acquired data to grasp the overall situation including the external situation of the vehicle 2, the situation in which the vehicle itself is placed therein, and the internal situation of the vehicle 2. The detection block 100 may provide substantially the same detection information to the planning block 120 and the risk monitoring block 140. The sensing block 100 may provide different sensing information to the planning block 120 and the risk monitoring block 140 .

[0033] The detection information generated by the detection block 100 describes the state detected for each scene in the driving environment of the vehicle 2. The detection block 100 may generate the detection information of an object by detecting an object including other road users 3, obstacles, and structures in the outside world of the vehicle 2. The detection information of the object may represent at least one of the following: the distance to the object, the relative speed of the object, the relative acceleration of the object, and an estimated state by tracking detection of the object. The detection information of the object may further represent a type recognized or identified from the state of the detected object. The detection block 100 may generate the detection information of the road by detecting the road on which the vehicle 2 is currently and will be traveling in the future. The detection information of the road may represent at least one state of the road surface, the lane, the road edge, and the free space, for example.

[0034] The detection block 100 may generate detection information of the self-state quantity by localization that estimates the self-state quantity including the self-position of the vehicle 2. The detection block 100 may generate update information of the map data related to the route of the vehicle 2 at the same time as the detection information of the self-state quantity, and feed back the update information to the map DB 7. The detection block 100 may generate detection information of the marking by detecting a marking associated with the route of the vehicle 2. The detection information of the marking may represent at least one type of state, for example, a sign, a division line, a traffic light, and the like. The detection information of the marking may further represent a traffic rule that is recognized or specified from the state of the marking. The detection block 100 may generate detection information of the weather condition by detecting the weather condition for each scene in which the vehicle 2 runs. The detection block 100 may generate detection information of the weather condition by detecting the time for each scene in which the vehicle 2 runs.

[0035] The planning block 120 acquires detection information from the detection block 100. The planning block 120 plans driving control of the vehicle 2 according to the acquired detection information. In the planning of the driving control, control commands related to the navigation operation and the driver assistance operation of the vehicle 2 are generated. That is, the planning block 120 realizes a DDT function that generates a control command as a motion control request of the vehicle 2. The control command generated by the planning block 120 may include a control parameter for controlling a motion actuator of the vehicle 2. Examples of the motion actuator to which the control command is output include at least one of an internal combustion engine, an electric motor, and a power train, a brake device, a steering device, and the like, which are combinations of these.

[0036] The planning block 120 may generate a control command to conform to the driving policy by using a safety model described according to the driving policy and its safety. The driving policy that the safety model follows is specified, for example, based on a vehicle-level safety strategy that ensures the safety of intended functionality (hereinafter, referred to as SOTIF). In other words, the safety model is described by following the driving policy that is an implementation of the vehicle-level safety strategy and by modeling the SOTIF. The planning block 120 may train the safety model by a machine learning algorithm that back-propagates the driving control results to the safety model. As the safety model to be trained, at least one type of learning model may be used, for example, deep learning by a neural network such as a DNN (Deep Neural Network) and reinforcement learning. The safety model here may be a safety-related model itself, or a model that constitutes a part of the safety-related model.

[0037] The planning block 120 may plan a route that the vehicle 2 will travel in the future by driving control, prior to generating a control command. The route planning may be performed by, for example, a calculation such as a simulation, in order to navigate the vehicle 2 based on the detection information. That is, the planning block 120 may realize a DDT function that plans a route as a tactical action of the vehicle 2. The planning block 120 may further plan an appropriate trajectory based on the acquired detection information for the vehicle 2 that follows the planned route, prior to generating a control command. That is, the planning block 120 may realize a DDT function that plans a trajectory of the vehicle 2. The trajectory planned by the planning block 120 may specify at least one of, for example, a running position, a speed, an acceleration, and a yaw rate, in a time series, as a motion physical quantity related to the vehicle 2. The time-series trajectory planning constructs a scenario of future travel by navigating the vehicle 2. The planning block 120 may generate a trajectory by a plan using a safety model. In this case, a cost function that assigns a cost to the generated trajectory may be calculated, and the safety model may be trained by a machine learning algorithm based on the calculation results.

[0038] The planning block 120 may plan an adjustment of the autonomous driving level of the vehicle 2 according to the acquired detection information. The adjustment of the autonomous driving level may include a handover between autonomous driving and manual driving. The handover between autonomous driving and manual driving may be realized in a scenario accompanying entry or exit from the operation design domain by setting the operation design domain in which the autonomous driving is performed. In a scenario for exiting the operation design domain, that is, a scenario for handover from autonomous driving to manual driving, for example, an unreasonable situation in which it is determined that an unreasonable risk exists based on a safety model or the like is cited as a use case. In this use case, the planning block 120 may plan a DDT fallback in which a driver who is a fallback reserve user applies a minimum-risk operation to the vehicle 2 to transition the vehicle 2 to a minimum-risk state.

[0039] The adjustment of the autonomous driving level may include degenerate driving of the vehicle 2. In the scenario of degenerate driving, an irrational situation in which it is determined based on, for example, a safety model that there is an irrational risk if the vehicle is handed over to manual driving is an example of a use case. In this use case, the planning block 120 may plan a DDT fallback for transitioning the vehicle 2 to a minimum risk state by autonomous driving and autonomous stopping. The DDT fallback for transitioning the vehicle 2 to a minimum risk state may be realized not only in an adjustment to lower the autonomous driving level, but also in an adjustment to maintain the autonomous driving level and perform degenerate driving, such as an MRM (Minimum Risk Maneuver). In the DDT fallback for transitioning the vehicle 2 to a minimum risk state, the conspicuousness of the transition state may be increased by at least one of, for example, lighting, a horn sound, a signal, and a gesture.

[0040] The risk monitoring block 140 acquires detection information from the detection block 100. Based on the acquired detection information, the risk monitoring block 140 monitors the risk between the vehicle 2 and the other road users 3 for each scene. The risk monitoring block 140 performs risk monitoring based on the detection information in a time series manner so as to guarantee the SOTIF of the vehicle 2 for the other road users 3. The other road users 3 assumed in the risk monitoring include non-vulnerable road users such as cars, trucks, motorcycles, and bicycles, and vulnerable road users such as pedestrians. The other road users 3 assumed in the risk monitoring may further include animals.

[0041] The risk monitoring block 140 sets a safety envelope based on, for example, a vehicle level safety strategy that guarantees SOTIF in the vehicle 2, based on the acquired detection information for each scene. The risk monitoring block 140 may set a safety envelope between the vehicle 2 and other road users 3 using a safety model that follows the driving policy described above. The safety model used to set the safety envelope may be designed to avoid potential accident liability caused by unreasonable risks or misuse by road users in accordance with accident liability rules. In other words, the safety model may be designed so that the vehicle 2 complies with accident liability rules that follow the driving policy. Such a safety model may include, for example, a Responsibility Sensitive Safety model as disclosed in Patent Document 1.

[0042] In setting the safety envelope, a safety distance may be estimated from a profile related to at least one type of physical quantity of motion based on a safety model for the vehicle 2 and the other road user 3 assumed to follow a driving policy. The safety distance defines a boundary around the vehicle 2 that ensures a physically based margin for the predicted motion of the other road user 3. The safety distance may be estimated taking into account the reaction time until an appropriate response is executed by each of the vehicle 2 and the other road user 3. The safety distance may be estimated so as to comply with the accident liability rules. For example, in a scene where a lane structure such as a lane exists, a safety distance that avoids the risk of a rear-end collision and a head-on collision in the longitudinal direction of the vehicle 2 and a safety distance that avoids the risk of a side collision in the lateral direction of the vehicle 2 may be calculated. On the other hand, in a scene where a lane structure does not exist, a safety distance that avoids the risk of a track collision in any direction of the vehicle 2 may be calculated.

[0043] The risk monitoring block 140 may identify the situation of the relative movement between the vehicle 2 and the other road user 3 in each scene prior to setting the above-mentioned safety envelope. For example, in a scene where a lane structure such as a lane exists, a situation where a risk of a rear-end collision and a head-on collision is assumed in the longitudinal direction and a situation where a risk of a side collision is assumed in the lateral direction may be identified. In identifying the longitudinal and lateral situations, the state quantities related to the vehicle 2 and the other road user 3 may be converted into a coordinate system assuming a straight lane. On the other hand, in a scene where a lane structure does not exist, a situation where a risk of a track collision is assumed in any direction of the vehicle 2 may be identified. Note that the above situation identification function may be at least partially executed by the detection block 100, and the situation identification result may be provided to the risk monitoring block 140 as detection information.

[0044] The risk monitoring block 140 executes a safety judgment between the vehicle 2 and the other road user 3 based on the set safety envelope and the acquired detection information for each scene. That is, the risk monitoring block 140 realizes the safety judgment by testing whether or not there is an envelope violation that violates the safety envelope in a driving scene interpreted based on the detection information between the vehicle 2 and the other road user 3. When a safety distance is assumed in the setting of the safety envelope, it may be determined that there is no envelope violation because the actual distance between the vehicle 2 and the other road user 3 exceeds the safety distance. On the other hand, it may be determined that there is an envelope violation because the actual distance between the vehicle 2 and the other road user 3 is equal to or less than the safety distance.

[0045] The risk monitoring block 140 may calculate, by simulation, a rational scenario for giving the vehicle 2 an appropriate action to be taken as an appropriate response when it is determined that an envelope violation has occurred. In simulating the rational scenario, a state transition between the vehicle 2 and the other road user 3 may be estimated, and an action to be taken for each transition state may be set as a constraint (described in detail later) for the vehicle 2. In setting the action, a limit value assumed for at least one type of motion physical quantity to be given to the vehicle 2 may be calculated so as to limit the motion physical quantity as a constraint on the vehicle 2.

[0046] The risk monitoring block 140 may directly calculate a limit value for complying with the accident liability rule from a profile related to at least one type of motion physical quantity based on a safety model for the vehicle 2 and other road users 3 assumed to follow the driving policy. The direct calculation of the limit value can be said to be the setting of a safety envelope and also the setting of a constraint on driving control. Therefore, when an actual value that is safer than the limit value is detected, a determination may be made that the envelope is not violated. On the other hand, when an actual value that is outside the limit value is detected, a determination may be made that the envelope is violated.

[0047] The risk monitoring block 140 may store at least one type of evidence information in the memory 10, for example, among detection information used to set the safety envelope, judgment information showing the judgment result of the safety envelope, detection information that influenced the judgment result, and a simulated scenario. The memory 10 in which the evidence information is stored may be mounted in the vehicle 2 depending on the type of dedicated computer constituting the processing system 1, or may be installed, for example, in an external center outside the vehicle 2. The evidence information may be stored in an unencrypted state, or may be encrypted or hashed and stored. The storage of the evidence information is at least executed when it is determined that the envelope is violated. Of course, the storage of the evidence information may also be executed when it is determined that the envelope is not violated. The evidence information in the case of the determination that the envelope is not violated can be utilized as a lagging indicator at the time of storage, and can also be utilized as a leading indicator for the future.

[0048] The control block 160 obtains a control command from the planning block 120. The control block 160 obtains judgment information regarding the safety envelope from the risk monitoring block 140. The control block 160 realizes a DDT function that controls the motion of the vehicle 2. When the control block 160 obtains judgment information indicating no envelope violation, the control block 160 executes the planned driving control of the vehicle 2 in accordance with the control command.

[0049] In response to this, when the control block 160 acquires the determination information indicating that the envelope is violated, the control block 160 imposes a constraint on the planned driving control of the vehicle 2 according to the driving policy based on the determination information. The constraint on the driving control may be a functional constraint. The constraint on the driving control may be a degraded constraint. The constraint on the driving control may be a constraint different from these. The constraint on the driving control is given by a restriction on a control command. When a reasonable scenario is simulated by the risk monitoring block 140, the control block 160 may restrict the control command according to the scenario. At this time, when a limit value is set for the motion physical quantity of the vehicle 2, the control parameter of the motion actuator included in the control command may be corrected based on the limit value.

[0050] The first embodiment will be described in detail below.

[0051] 7, 8, 10 to 13, the first embodiment assumes a lane structure Ls in which lanes are divided. The lane structure Ls regulates the movement of the vehicle 2 and other road users 3 with the direction in which the lanes extend as the longitudinal direction. The lane structure Ls regulates the movement of the vehicle 2 and other road users 3 with the width direction or the line-up direction of the lanes as the lateral direction.

[0052] The driving policy in the lane structure Ls is stipulated as the following (A) to (E) between the first vehicle 2a and the second vehicle 2b, one of which is assumed to be the vehicle 2 and the other of which is the other road user 3. Note that the forward direction based on the vehicle 2 means, for example, the traveling direction on a turning circle at the current steering angle of the vehicle 2, the traveling direction of a straight line passing through the center of gravity of the vehicle perpendicular to the axle of the vehicle 2, or the traveling direction on the axis from the front camera module of the sensor system 5 of the vehicle 2 to the FOE (Focus of Expansion) of the camera. (A) Vehicle 2 does not rear-end vehicle 2 traveling in front of it. (B) Vehicle 2 does not forcibly wed between other vehicles 2. (C) Even if vehicle 2 has the right of way, it will yield to other vehicle 2 depending on the circumstances. (D) Vehicle 2 drives carefully in areas with poor visibility. (E) Vehicle 2 will take reasonable action to prevent the accident if it is in a position to do so, regardless of whether it is at fault or not.

[0053] A model that follows a driving policy, the SOTIF modeled safety model assumes that road user behavior that does not lead to an irrational situation is the appropriate rational behavior to be taken. Irrational situations between a vehicle 2 and another road user 3 in the lane structure Ls are head-on collisions, rear-end collisions, and side collisions. Rational behavior in a head-on collision includes, for example, the first vehicle 2a and the second vehicle 2b, one of which is the other road user 3, applying the brakes of the vehicle 2a or 2b traveling in the opposite direction. Rational behavior in a rear-end collision includes, for example, the first vehicle 2a and the second vehicle 2b, the vehicle 2a or 2b traveling in front does not apply the brakes more than a certain amount, and the vehicle 2b or 2a traveling behind avoids the rear-end collision on that premise. Rational behavior in a side collision includes, for example, the first vehicle 2a and the second vehicle 2b, the vehicles 2a and 2b traveling side by side steer in the direction away from each other. When assuming rational behavior, the state quantities related to the vehicle 2 and other road users 3 are transformed into a Cartesian coordinate system that defines the longitudinal and lateral directions by assuming a straight and planar lane structure Ls, regardless of whether the lane structure Ls is a curved lane or an elevated lane structure Ls.

[0054] The safety model may be designed in accordance with the accident liability rule, which holds that a moving body that does not behave rationally is responsible for the accident. Under the accident liability rule for the lane structure Ls, the safety model used to monitor the risk between the vehicle 2 and other road users 3 sets a safety envelope for the vehicle 2 so as to avoid potential accident liability by rational behavior. In the vehicle 2, the risk monitoring block 140 in a state in which the entire processing system 1 is normal determines whether or not there is an envelope violation by checking the safety distance based on the safety model for each driving scene against the actual distance between the vehicle 2 and other road users 3. If there is an envelope violation, the risk monitoring block 140 simulates a scenario for giving the vehicle 2 rational behavior. Through the simulation, the risk monitoring block 140 sets a limit value for at least one of, for example, speed and acceleration, as a constraint on the driving control in the control block 160.

[0055] In the first embodiment, in the first vehicle 2a and the second vehicle 2b assumed as paired vehicles 2 that directly or indirectly communicate with each other, a processing method for performing driving-related processing by cooperation of functional blocks constructed by each processing system 1 is executed according to the flowcharts shown in Figs. 14 and 15, respectively. The processing method of the first embodiment is repeatedly executed in each of the first vehicle 2a and the second vehicle 2b while the mutual distance between the first vehicle 2a and the second vehicle 2b is within the monitoring range of the safety envelope. Note that each "S" in the processing method in the following description means a plurality of steps executed by a plurality of commands included in a processing program in the processing system 1 of each of the vehicles 2a and 2b.

[0056] 14 and 15, the risk monitoring blocks 140 of the first vehicle 2a and the second vehicle 2b exchange user IDs including an authentication key through mutual communication to authenticate each other. This mutual authentication may simply be a confirmation of security and whether communication is possible. In addition to the security confirmation and the confirmation of whether communication is possible, this mutual authentication may also include a confirmation of whether the adopted safety model or driving policy has a function of setting a safety envelope.

[0057] As shown in FIG. 14, in S101 following S100 of the processing method, the risk monitoring block 140 of the first vehicle 2a monitors an envelope violation regarding the safety envelope set in the first vehicle 2a between the second vehicle 2b and the SOTIF according to the driving policy based on the safety model of the first vehicle 2a. As shown by a solid circle in FIG. 12, when at least a part of the second vehicle 2b is present within the range of the safety distance that defines the safety envelope based on the safety model of the first vehicle 2a, an envelope violation is recognized. Therefore, when the risk monitoring block 140 of the first vehicle 2a determines that there is an envelope violation in S101, the current flow in the first vehicle 2a sequentially proceeds to S102 and S103 as shown in FIG. 14. That is, S102 and S103 are executed when an envelope violation between the first vehicle 2a and the second vehicle 2b is recognized in the first vehicle 2a.

[0058] In S102, the risk monitoring block 140 of the first vehicle 2a generates warning information Iw for warning the second vehicle 2b of the envelope violation. The warning information Iw may include notification information In that the first vehicle 2a pushes the second vehicle 2b to notify the occurrence of the envelope violation event. The warning information Iw may be composite information in which situation information Is is added to the notification information In. The situation information Is may include envelope information Ise related to the safety envelope set in the first vehicle 2a.

[0059] The envelope information Ise may represent the range of a safety envelope including a safety distance that is the criterion for determining an envelope violation in the first vehicle 2a. The envelope information Ise may represent at least one type of risk, for example, a rear-end collision risk, a head-on collision risk, a side collision risk, an intersection risk, a blind spot risk, and detailed conditions thereof, which are assumed as a relative state between the first vehicle 2a and the second vehicle 2b by a safety model that defines the safety envelope that is the criterion for determining an envelope violation.

[0060] The envelope information Ise may represent at least one of the detection information of the first vehicle 2a detected by the detection block 100 of the first vehicle 2a in the envelope violation scene, such as a self-state quantity including a position (i.e., a localization estimate), an estimated state including a distance, a speed, an acceleration / deceleration, a relative speed, a relative acceleration, and vectors thereof, and a type, etc. In particular, the envelope information Ise may represent at least one type of detection information detected by the detection block 100 of the first vehicle 2a, such as the speed, acceleration / deceleration, etc. of the first vehicle 2a, as a motion physical quantity of an envelope violation that deviates from a limit value set by the constraint setting of the risk monitoring block 140 in the first vehicle 2a.

[0061] The envelope information Ise may represent at least one of the detection information of the second vehicle 2b detected by the detection block 100 of the first vehicle 2a in the scene of the envelope violation, for example, position, distance, speed, acceleration / deceleration, relative speed, relative acceleration, and an estimated state including vectors thereof, and a type, etc. In particular, the envelope information Ise may represent at least one type of detection information detected by the detection block 100 of the first vehicle 2a, among the speed, acceleration / deceleration, etc. of the second vehicle 2b, as a motion physical quantity of the envelope violation that deviates from the limit value set by the constraint setting of the risk monitoring block 140 in the first vehicle 2a. The envelope information Ise may include an image or video including the second vehicle 2b captured by a camera that is the external sensor 50 of the first vehicle 2a in the scene of the envelope violation.

[0062] Other than the envelope information Ise, the situation information Is may represent at least one of the planned situations of the first vehicle 2a in the planning block 120 in the scene of the envelope violation, such as a route, a trajectory, a control parameter, an automatic driving level (including a case where manual driving is level 0), etc. The situation information Is may represent at least one of the road conditions in the scene of the envelope violation, such as traffic rules, signs, road structure, location, section, road surface condition, light and dark conditions, construction conditions, traffic congestion conditions, the presence of obstacles including fallen objects, feature structures around the road, and blind spots caused by the feature structures or the type of moving object, etc. The situation information Is may represent at least one of the time, the time zone of the violation scene including the distinction between day and night, and the weather conditions (i.e., weather) of the violation scene, etc. in the scene of the envelope violation.

[0063] The warning information Iw generated in S102 can be transmitted from the first vehicle 2a to the second vehicle 2b according to the control of the communication system 6 by the risk monitoring block 140 of the first vehicle 2a. In other words, the risk monitoring block 140 of the first vehicle 2a generates the envelope violation warning information Iw so that it is transmitted in real time from the first vehicle 2a to the second vehicle 2b in response to the determination that there is an envelope violation. Here, in this embodiment, the transmission between the vehicles 2a and 2b may be realized directly between the communication systems 6 of a V2V type or the like, may be realized indirectly via a remote center such as a cloud server, or may be realized via a mesh network configured between a plurality of vehicles including the vehicles 2a and 2b.

[0064] In S103, the risk monitoring block 140 of the first vehicle 2a stores the generated warning information Iw in the memory 10 of the first vehicle 2a. The warning information Iw may be stored in association with a timestamp representing the time of generation or transmission at the first vehicle 2a, thereby accumulating warning information Iw at multiple points in time. The warning information Iw may be stored after undergoing encryption processing or hashing processing at the first vehicle 2a. The warning information Iw may be stored as evidence information. The warning information Iw may be deleted when a set period has elapsed since the time of generation or transmission at the first vehicle 2a. When execution of S103 is completed, the current flow at the first vehicle 2a ends.

[0065] As shown in FIG. 15, in S111 following the above-mentioned S110, the risk monitoring block 140 of the second vehicle 2b monitors the envelope violation regarding the safety envelope set in the second vehicle 2b between the first vehicle 2a and the SOTIF according to the driving policy based on the safety model of the second vehicle 2b. As shown by the dashed circle in FIG. 10 to FIG. 12, when the entire first vehicle 2a is outside the range of the safety distance that defines the safety envelope based on the safety model in the second vehicle 2b, the envelope violation is not recognized in the second vehicle 2b. Therefore, when the risk monitoring block 140 of the second vehicle 2b judges that there is no envelope violation in S111, the current flow in the second vehicle 2b proceeds to S114 as shown in FIG. 15.

[0066] In S114, the risk monitoring block 140 of the second vehicle 2b determines whether or not the warning information Iw from the first vehicle 2a has been received through the communication system 6 of the second vehicle 2b. If the risk monitoring block 140 of the second vehicle 2b determines in S114 that the warning information Iw has not been received, the current flow in the second vehicle 2b ends.

[0067] On the other hand, if the risk monitoring block 140 of the second vehicle 2b determines in S114 that the warning information Iw has been acquired, the current flow in the second vehicle 2b proceeds to S115 and S116 in sequence. That is, S115 and S116 are executed in real time in response to the acquisition of the warning information Iw when the envelope violation between the first vehicle 2a and the second vehicle 2b is not recognized in the second vehicle 2b, even though the envelope violation between the first vehicle 2a and the second vehicle 2b is recognized in the first vehicle 2a, as shown in Fig. 12. Here, Fig. 12 shows an example in which a difference occurs in the recognition result because the safety distance that defines the safety envelope based on the safety model in the second vehicle 2b is smaller than the safety distance that defines the safety envelope based on the safety model in the first vehicle 2a.

[0068] As shown in FIG. 15, in S115, the risk monitoring block 140 of the second vehicle 2b stores the acquired warning information Iw in the memory 10 of the second vehicle 2b. The warning information Iw may be stored in association with a timestamp representing the time of generation or transmission at the first vehicle 2a, or the time of acquisition (i.e., the time of reception) at the second vehicle 2b, thereby accumulating warning information Iw at multiple points in time. The warning information Iw may be stored after being encrypted or hashed at the second vehicle 2b. The warning information Iw may be stored as evidence information. The warning information Iw may be deleted when a set period has elapsed from the time of generation or transmission at the first vehicle 2a, or the time of acquisition at the second vehicle 2b.

[0069] In S116, the risk monitoring block 140 of the second vehicle 2b adjusts the safety envelope set in the second vehicle 2b in accordance with the driving policy of the SOTIF between the second vehicle 2b and the first vehicle 2a. The adjustment of the safety envelope may be performed by correcting the setting parameters or learning parameters in the safety model. In this case, the correction amount for updating the parameters may be determined by verification and validation of the safety model of the second vehicle 2b based on at least the envelope information Ise of the warning information Iw from the first vehicle 2a. When the execution of S116 is completed, the current flow in the second vehicle 2b ends.

[0070] So far, a case has been described in which the first vehicle 2a is the sender of the warning information Iw and the second vehicle 2b is the receiver of the warning information Iw. Next, a case will be described in which the second vehicle 2b is the sender of the warning information Iw and the first vehicle 2a is the receiver of the warning information Iw.

[0071] As shown by the dashed circle in Fig. 13, when at least a part of the first vehicle 2a is present within a range of a safety distance that defines a safety envelope based on a safety model in the second vehicle 2b, an envelope violation is recognized. Therefore, when the risk monitoring block 140 of the second vehicle 2b determines in the above-mentioned S111 that there is an envelope violation, the current flow in the second vehicle 2b proceeds to S112 and S113 in sequence, as shown in Fig. 15. That is, S112 and S113 are executed when an envelope violation between the second vehicle 2b and the first vehicle 2a is recognized in the second vehicle 2b.

[0072] In S112, the risk monitoring block 140 of the second vehicle 2b executes a process for generating warning information Iw in the same manner as in the description of S102, except that the first vehicle 2a and the second vehicle 2b are interpreted in the opposite manner. In S113, the risk monitoring block 140 of the second vehicle 2b executes a process for storing warning information Iw in the same manner as in the description of S103, except that the first vehicle 2a and the second vehicle 2b are interpreted in the opposite manner. When the execution of S113 is completed, the current flow for the second vehicle 2b ends.

[0073] Before executing S113 or before the end of the current flow after executing S113, the risk monitoring block 140 of the second vehicle 2b may execute the acquisition and determination process of warning information Iw according to S114, thereby achieving a common recognition with the first vehicle 2a for a scene in which an envelope violation has occurred. Similarly, before executing the above-mentioned S103 or before the end of the current flow after executing S103, the risk monitoring block 140 of the first vehicle 2a may execute the acquisition and determination process of warning information Iw according to S114, thereby achieving a common recognition with the second vehicle 2b for a scene in which an envelope violation has occurred.

[0074] As shown by solid-line circles in Figs. 10, 11, and 13, when the entire second vehicle 2b is outside the range of the safety distance that defines the safety envelope based on the safety model of the first vehicle 2a, the first vehicle 2a does not recognize the envelope violation. If the risk monitoring block 140 of the first vehicle 2a determines that there is no envelope violation in the above-mentioned S101, the current flow in the first vehicle 2a proceeds to S104 as shown in Fig. 14. In S104, the risk monitoring block 140 of the first vehicle 2a executes a process in which the first vehicle 2a and the second vehicle 2b in the description of S114 are read in reverse as a process for determining whether the warning information Iw has been acquired. If the risk monitoring block 140 of the first vehicle 2a determines that the warning information Iw has not been acquired in S104, the current flow in the first vehicle 2a ends.

[0075] On the other hand, if the risk monitoring block 140 of the first vehicle 2a determines in S104 that the warning information Iw has been acquired, the current flow in the first vehicle 2a proceeds to S105 and S106 in sequence. That is, S105 and S106 are executed in real time in response to the acquisition of the warning information Iw when the envelope violation between the first vehicle 2a and the second vehicle 2b is not recognized in the first vehicle 2a, even though the envelope violation between the first vehicle 2a and the second vehicle 2b is recognized in the second vehicle 2b as shown in Fig. 13. Here, Fig. 13 shows an example in which a difference occurs in the recognition result because the safety distance that defines the safety envelope based on the safety model in the first vehicle 2a is smaller than the safety distance that defines the safety envelope based on the safety model in the second vehicle 2b.

[0076] 14, in S105, the risk monitoring block 140 of the first vehicle 2a executes a process for storing the warning information Iw, which is the same as the process in S115, except that the first vehicle 2a and the second vehicle 2b are interpreted in reverse. In S106, the risk monitoring block 140 of the first vehicle 2a executes a process for adjusting the safety envelope, which is the same as the process in S116, except that the first vehicle 2a and the second vehicle 2b are interpreted in reverse. When the execution of S106 is completed, the current flow for the first vehicle 2a ends.

[0077] As described above, in the first embodiment, from the viewpoint of the first vehicle 2a, the first vehicle 2a as a host moving body monitors an envelope that is a violation of the safety envelope for which SOTIF is set between the first vehicle 2a and the second vehicle 2b as a target moving body. When an envelope violation is recognized, the first vehicle 2a generates warning information Iw that warns of the envelope violation so as to transmit it to the second vehicle 2b. This allows the envelope violation warned by the first vehicle 2a to be commonly recognized by the second vehicle 2b, thereby promoting improvement of the ability to respond to the behavior of the other vehicle.

[0078] On the other hand, from the viewpoint of the second vehicle 2b in the first embodiment, the second vehicle 2b as the host moving body acquires from the first vehicle 2a warning of an envelope violation, which is a violation of the safety envelope for which SOTIF is set between the first vehicle 2a as the target moving body and the second vehicle 2b. In response to the acquisition of the warning information Iw, the second vehicle 2b adjusts the safety envelope between the first vehicle 2a and the second vehicle 2b. This allows the envelope violation warned by the first vehicle 2a to be commonly recognized in the second vehicle 2b as well and reflected in the adjustment of the safety envelope, thereby promoting the improvement of the ability to respond to the behavior of the other vehicle.

[0079] Also, from the viewpoint of the second vehicle 2b in the first embodiment, the second vehicle 2b as a host moving body monitors an envelope that is a violation of the safety envelope for which SOTIF is set between the second vehicle 2b as a target moving body and the first vehicle 2a as a target moving body. Thus, when an envelope violation is recognized, the second vehicle 2b generates warning information Iw that warns of the envelope violation so as to transmit it to the first vehicle 2a. In this way, the envelope violation warned by the second vehicle 2b can be commonly recognized in the first vehicle 2a, so that it is possible to promote improvement of the response capability to the behavior of the other vehicle.

[0080] On the other hand, from the viewpoint of the first vehicle 2a in the first embodiment, the first vehicle 2a as a host moving body acquires from the second vehicle 2b warning of an envelope violation, which is a violation of the safety envelope for which SOTIF is set between the first vehicle 2a and the second vehicle 2b as a target moving body. In response to the acquisition of the warning information Iw, the first vehicle 2a also adjusts the safety envelope between the first vehicle 2a and the second vehicle 2b. This allows the envelope violation warned by the second vehicle 2b to be commonly recognized in the first vehicle 2a as well and reflected in the adjustment of the safety envelope, thereby promoting the improvement of the ability to respond to the behavior of the other vehicle.

[0081] Second Embodiment The second embodiment is a modification of the first embodiment.

[0082] 16 and 17 show the processing method of the second embodiment for the first vehicle 2a and the second vehicle 2b, respectively, in which the execution of S100 and S110 is omitted, and accordingly, S2107-S2109 in the first vehicle 2a and S2117-S2119 in the second vehicle 2b are added to the processing method.

[0083] 17, in S2117 following S116, the risk monitoring block 140 of the second vehicle 2b generates feedback information If for feeding back the acquisition of the warning information Iw to the first vehicle 2a. The feedback information If may include notification information In for push notification of the acquisition of the warning information Iw from the second vehicle 2b to the first vehicle 2a. The feedback information If may be composite information in which situation information Is, which is obtained by reinterpreting the first vehicle 2a and the second vehicle 2b in the description of S102, is added to the notification information In. In other words, the situation information Is may include envelope information Ise related to the safety envelope set in the second vehicle 2b.

[0084] The warning information Iw generated in S2117 can be transmitted from the second vehicle 2b to the first vehicle 2a in accordance with the control of the communication system 6 by the risk monitoring block 140 of the second vehicle 2b. In other words, the risk monitoring block 140 of the second vehicle 2b generates feedback information If for the warning information Iw so that it is transmitted in real time from the second vehicle 2b to the first vehicle 2a in response to acquisition of the warning information Iw. When the execution of S2117 is completed, the current flow in the second vehicle 2b ends.

[0085] 16, in S2108 following S103, the risk monitoring block 140 of the first vehicle 2a determines whether or not feedback information If from the second vehicle 2b has been acquired by reception through the communication system 6 of the first vehicle 2a within a set time from the transmission of the warning information Iw. If the risk monitoring block 140 of the first vehicle 2a determines in S2108 that the feedback information If has been acquired, the current flow for the first vehicle 2a ends.

[0086] By performing S2108, the risk monitoring block 140 of the first vehicle 2a can check whether a common recognition with the second vehicle 2b has been achieved for a scene involving an envelope violation. In addition, in S2108, the risk monitoring block 140 of the first vehicle 2a may delete the warning information Iw corresponding to the acquisition from the memory 10 of the first vehicle 2a in response to the acquisition of the feedback information If. Alternatively, in S2108, the risk monitoring block 140 of the first vehicle 2a may store the feedback information If acquired in response to the warning information Iw of S103 in the memory 10 of the first vehicle 2a.

[0087] On the other hand, when the risk monitoring block 140 of the first vehicle 2a determines in S2108 that the feedback information If has not been acquired, the current flow in the first vehicle 2a proceeds to S2109. In S2109, the risk monitoring block 140 of the first vehicle 2a sets a constraint for avoiding an unreasonable risk to the motion control of the first vehicle 2a. The constraint for risk avoidance may be a degenerate command for the control block 160 of the first vehicle 2a, which causes the first vehicle 2a to execute degenerate running, such as emergency evacuation action or MRM, on a best effort basis. The constraint for risk avoidance may be a restriction command for the control block 160 of the first vehicle 2a, which gives a restriction for moving the first vehicle 2a to a minimum risk state. The constraint for risk avoidance may be at least one minor constraint among a speed limit, an acceleration limit, and a limit that the first vehicle 2a moves away from the second vehicle 2b. Such a constraint setting process enables a safer risk avoidance action when the first vehicle 2a is unable to obtain feedback information If in response to the transmission of warning information Iw from itself due to factors such as the processing system 1 not being applied to the second vehicle 2b or the communication system 6 not being installed in the second vehicle 2b. When the execution of S2109 is completed, the current flow in the first vehicle 2a ends. Note that in the first vehicle 2a where the current flow ends without obtaining feedback information If in this way, if the envelope violation continues in S101 of the next flow, the generation and transmission of warning information Iw is repeated in S102 of the next flow.

[0088] So far, the case where the second vehicle 2b is the sender of the feedback information If and the first vehicle 2a is the receiver of the feedback information If has been described. Next, the case where the first vehicle 2a is the sender of the feedback information If and the second vehicle 2b is the receiver of the feedback information If will be described.

[0089] In S2107 following S106, the risk monitoring block 140 of the first vehicle 2a executes a process for generating the feedback information If in the same manner as in S2117, except that the first vehicle 2a and the second vehicle 2b are interpreted in reverse. When the execution of S2107 is completed, the current flow for the first vehicle 2a ends.

[0090] 17, in S2118 following S113, the risk monitoring block 140 of the second vehicle 2b executes a process for determining whether or not feedback information If has been acquired, in which the first vehicle 2a and the second vehicle 2b in the description of S2108 are interpreted in reverse. Thus, if the risk monitoring block 140 of the second vehicle 2b determines in S2118 that feedback information If has been acquired, the current flow for the second vehicle 2b ends.

[0091] By performing S2118, the risk monitoring block 140 of the second vehicle 2b can check whether a common recognition with the first vehicle 2a has been achieved for a scene involving an envelope violation. In addition, in S2118, the risk monitoring block 140 of the second vehicle 2b may delete the warning information Iw corresponding to the acquisition from the memory 10 of the second vehicle 2b in response to the acquisition of the feedback information If. Alternatively, in S2118, the risk monitoring block 140 of the second vehicle 2b may store the feedback information If acquired in response to the warning information Iw of S103 in the memory 10 of the second vehicle 2b.

[0092] On the other hand, if the risk monitoring block 140 of the second vehicle 2b determines in 2118 that the feedback information If has not been acquired, the current flow in the second vehicle 2b proceeds to S2119. In S2119, the risk monitoring block 140 of the second vehicle 2b executes a process in which the first vehicle 2a and the second vehicle 2b in the description of S2109 are read in reverse as a constraint setting process for risk avoidance. Such a constraint setting process enables a safer risk avoidance action when the second vehicle 2b is unable to acquire the feedback information If in response to the transmission of the warning information Iw from itself due to factors such as the processing system 1 not being applied to the first vehicle 2a or the first vehicle 2a not being equipped with the communication system 6. When the execution of S2119 is completed, the current flow in the second vehicle 2b ends. In the second vehicle 2b in which the current flow ends without acquiring the feedback information If, if the envelope violation continues in S111 of the next flow, the generation and transmission of the warning information Iw are repeated in S112 of the next flow.

[0093] In the second embodiment, the processing method in which S2107-2109 and S2117-S2119 are added to the first embodiment is executed mainly by each risk monitoring block 140 of the first vehicle 2a and the second vehicle 2b. Therefore, it is possible to promote improvement of the response ability to the behavior of the other vehicle.

[0094] Third embodiment The third embodiment is a modification of the first embodiment.

[0095] As shown in FIG. 18, in the control block 3160 of the third embodiment, the process of acquiring judgment information on the safety envelope from the risk monitoring block 140 is omitted. Therefore, the planning block 3120 of the third embodiment acquires judgment information on the safety envelope from the risk monitoring block 140. When the planning block 3120 acquires judgment information indicating that there is no envelope violation, the planning block 3120 plans the driving control of the vehicle 2 according to the planning block 120. On the other hand, when the planning block 3120 acquires judgment information indicating that there is an envelope violation, the planning block 3120 imposes a constraint based on the judgment information on the driving control in the stage of planning the driving control according to the planning block 120. That is, the planning block 3120 imposes a restriction on the planned driving control. In either case, the control block 3160 executes the driving control of the vehicle 2 planned by the planning block 3120.

[0096] In the third embodiment, the risk monitoring block 140 of each of the first and second vehicles 2a, 2b mainly executes a processing method similar to that of the first embodiment. Therefore, it is possible to promote improvement of the response capability to the behavior of the other vehicle. The third embodiment described above may be combined with the second embodiment.

[0097] (Fourth embodiment) The fourth embodiment is a modification of the third embodiment.

[0098] As shown in FIG. 19, the planning block 4120 of the fourth embodiment incorporates the function of the risk monitoring block 140 as a risk monitoring sub-block 4140. When the risk monitoring sub-block 4140 acquires the determination information that there is no envelope violation, the planning block 4120 plans the driving control of the vehicle 2 according to the planning block 120. On the other hand, when the risk monitoring sub-block 4140 acquires the determination information that there is an envelope violation, the planning block 4120 imposes a constraint based on the determination information on the driving control in the stage of planning the driving control according to the planning block 120. That is, the planning block 4120 imposes a restriction on the planned driving control. In either case, the control block 3160 executes the driving control of the vehicle 2 planned by the planning block 4120.

[0099] In the fourth embodiment, the processing method according to the first embodiment is executed mainly by each of the risk monitoring sub-blocks 4140 of the first vehicle 2a and the second vehicle 2b. Therefore, it is possible to promote improvement of the response capability to the behavior of the other vehicle. The fourth embodiment described above may be combined with the second embodiment.

[0100] Fifth embodiment The fifth embodiment is a modification of the first embodiment.

[0101] 20, in the control block 5160 of the fifth embodiment, the process of acquiring judgment information related to the safety envelope is omitted from the risk monitoring block 5140. Therefore, the risk monitoring block 5140 of the fourth embodiment acquires information representing the result of driving control executed by the control block 5160 on the vehicle 2. The risk monitoring block 5140 evaluates the driving control by executing an envelope violation judgment on the result of the driving control.

[0102] In the fifth embodiment, the processing method according to the first embodiment is executed mainly by each of the risk monitoring blocks 5140 of the first vehicle 2a and the second vehicle 2b. In particular, the safety envelope adjustment process in S106 and S116 can improve the evaluation accuracy of the driving control. Therefore, it is possible to promote the improvement of the response to the behavior of the other vehicle. The fifth embodiment described above may be combined with the second embodiment. However, when the fifth embodiment is combined with the second embodiment, the evaluation of the driving control based on the set constraints is executed in S2109 and S2119.

[0103] Sixth Embodiment The sixth embodiment is a modification of the first embodiment.

[0104] As shown in FIGS. 21 and 22, the sixth embodiment is added with a test block 6180 that tests the operation control by the control block 160, for example, for safety approval. The test block 6180 is provided with functions equivalent to those of the detection block 100 and the risk monitoring block 140. The test block 6180 may be constructed by executing a test program added to the processing program that constructs each of the blocks 100, 120, 140, and 160 by the processing system 1 shown in FIG. 21. The test block 6180 may be constructed by executing a test processing program different from the processing program that constructs each of the blocks 100, 120, 140, and 160 by a test processing system 6001 different from the processing system 1, as shown in FIG. 22. Here, the test processing system 6001 may be configured by at least one dedicated computer having a memory 10 and a processor 12 that is connected to the processing system 1 to test the operation control (illustration of the case of connection through the communication system 6 is omitted).

[0105] In the sixth embodiment, a processing method similar to that of the first embodiment is executed mainly for each test block 6180 of the first vehicle 2a and the second vehicle 2b. In particular, the adjustment process of the safety envelope by S106 and S116 can improve the evaluation accuracy of the driving control in the test. Therefore, it is possible to promote the improvement of the response ability to the behavior of the other vehicle. The sixth embodiment described so far may be combined with the second embodiment. However, when the sixth embodiment is combined with the second embodiment, in S2109 and S2119, the evaluation of the driving control as a test is executed based on the set constraints. (Other embodiments)

[0106] Although several embodiments have been described above, the present disclosure should not be construed as being limited to those embodiments, and can be applied to various embodiments and combinations within the scope not departing from the gist of the present disclosure.

[0107] In a modified example, the dedicated computer constituting the processing system 1 may include at least one of a digital circuit and an analog circuit as a processor. Here, the digital circuit is at least one of ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array), SOC (System on a Chip), PGA (Programmable Gate Array), CPLD (Complex Programmable Logic Device), etc. Furthermore, such a digital circuit may have a memory that stores a program.

[0108] In the processing method of the modified example, the storage process of warning information Iw in S103 and S113 may be omitted. In the processing method of the modified example, the storage process of warning information Iw in S105 and S115 may be omitted. In the processing method of the modified example, the mutual authentication process in S100 and S110 may be omitted in the first embodiment as well, similar to the second embodiment.

Claims

1. A processing method executed by a processor (12) to perform processing related to operation of a host vehicle (2a, 2b) capable of communicating with a target vehicle (2b, 2a), comprising: monitoring for an envelope violation, which is a violation of a security envelope that establishes security of an intended function between the host mobile and the target mobile; generating, when the envelope violation is recognized in the host mobile unit, warning information (Iw) for warning the target mobile unit of the envelope violation to be transmitted to the target mobile unit; acquiring feedback information (If) for feeding back acquisition of the warning information from the target moving object; and setting a constraint on driving control of the host mobile object if the feedback information is not obtained.

2. Monitoring for envelope violations comprises: The method of claim 1 , further comprising monitoring for violations of the envelope based on a safety model that models the safety of an intended function.

3. generating the warning information The method according to claim 1 or 2, further comprising: generating the warning information for pushing the envelope violation to the target mobile entity.

4. generating the warning information The method according to any one of claims 1 to 3, comprising generating the warning information appended with envelope information (Ise) relating to the safety envelope established in the host mobile unit.

5. The processing method according to any one of claims 1 to 4, further comprising storing the generated warning information.

6. A processing method executed by a processor (12) to perform processing related to operation of a host vehicle (2a, 2b) capable of communicating with a target vehicle (2b, 2a), comprising: monitoring for an envelope violation, which is a violation of a security envelope that establishes security of an intended function between the host mobile and the target mobile; generating, when the envelope violation is recognized in the host mobile unit, warning information (Iw) for warning the envelope violation to be transmitted to the target mobile unit; acquiring feedback information (If) for feeding back acquisition of the warning information from the target moving object; and setting a constraint on driving control of the host mobile object if the feedback information is not obtained.

7. A processing system (1) including a processor (12) for performing processing related to the operation of a host vehicle (2a, 2b) capable of communicating with a target vehicle (2b, 2a), comprising: The processor, monitoring for an envelope violation, which is a violation of a security envelope that establishes security of an intended function between the host mobile and the target mobile; generating, when the envelope violation is recognized in the host mobile unit, warning information (Iw) for warning the envelope violation to be transmitted to the target mobile unit; acquiring feedback information (If) for feeding back acquisition of the warning information from the target moving object; and setting constraints on driving control of the host vehicle if the feedback information is not obtained.

8. A processing program stored in a storage medium (10) and including instructions to be executed by a processor (12) to perform processing related to the operation of a host moving body (2a, 2b) capable of communicating with a target moving body (2b, 2a), The instruction: monitoring the host mobile for an envelope violation that is a violation of a security envelope that establishes security of the intended functionality between the host mobile and the target mobile; generating, when the host mobile unit recognizes an envelope violation, warning information (Iw) for warning the target mobile unit of the envelope violation, for transmission to the target mobile unit; acquiring feedback information (If) for feeding back acquisition of the warning information from the target moving object; and setting a constraint on driving control of the host moving object when the feedback information is not acquired.

Citation Information

Patent Citations

  • Distance alarming device for vehicle

    JP1998250510A

  • Car navigation system

    JP2002168640A

  • Operation support system

    JP2009059200A

  • Navigation systems with imposed liability constraints

    JP6708793B2