Processing method, processing system, and processing program

The method and system enhance vehicle responsiveness to other road users by monitoring envelope violations and setting constraints on operation control, addressing detection challenges in existing technologies.

JP7586295B2Active Publication Date: 2024-11-19DENSO CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2023508790
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

Existing technologies face challenges in effectively detecting and responding to other road users when they are blocked by the host vehicle, leading to potential impacts on responsiveness.

Method used

A processing method and system that monitor for envelope violations, generate warning information, and obtain feedback to set constraints on host mobile operation control, ensuring improved responsiveness to other road users through communication with target mobile units.

Benefits of technology

Enhances the ability of vehicles to recognize and respond to envelope violations with other road users, promoting improved responsiveness and safety in dynamic driving scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007586295000001
    Figure 0007586295000001
  • Figure 0007586295000002
    Figure 0007586295000002
  • Figure 0007586295000003
    Figure 0007586295000003
Patent Text Reader

Abstract

The processing method executed by a processor in order to carry out a process pertaining to driving of a host moving body capable of communicating with a target moving body, the processing method including: monitoring for an envelope violation, which is a violation of a safety envelope in which the safety of an intended function with respect to another road user other than the target moving body has been set in the host moving body; and generating, when the envelope violation has been recognized in the host moving body, warning information for providing warning of the envelope violation so as to transmit said information to the target moving body.
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-53970 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, even if the host vehicle detects other road users other than the target vehicle, it is assumed that the other road users may be blocked by the host vehicle and difficult to detect from the target vehicle. In this case, there is a risk that the response to the other road users may be affected.

[0006] An object of the present disclosure is to provide a processing method that promotes improvement of response capabilities to other road users. Yet another object of the present disclosure is to provide a processing system that promotes improvement of response capabilities to other road users. Yet another object of the present disclosure is to provide a processing program that promotes improvement of response capabilities to other road users.

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

[0008] The present disclosure one The aspect is A processing method executed by a processor to perform processing related to driving of a host vehicle capable of communicating with a target vehicle, comprising: monitoring for envelope violations, which are violations of a safety envelope that defines the safety of the intended functionality of the host vehicle relative to other road users other than the target vehicle; 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 the target moving object; 、 Setting constraints on driving control of a host vehicle when feedback information is not obtained; Includes.

[0009] The present disclosure two 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 for envelope violations, which are violations of a safety envelope that defines the safety of the intended functionality of the host vehicle relative to other road users other than the target vehicle; 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 the target moving object; 、 Setting constraints on driving control of a host vehicle when feedback information is not obtained; The method is configured to execute the

[0010] The present disclosure threeThe 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 an envelope violation, which is a violation of a safety envelope that defines the safety of the intended function between the host mobile unit and other road users other than the target mobile unit; 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 the target moving object. 、 Setting constraints on driving control of a host vehicle when feedback information is not obtained; Includes.

[0011] These first and second three In the host mobile body of the embodiment, an envelope that is a violation of the safety envelope between the host mobile body and other road users other than the target mobile body is monitored. When an envelope violation between the host mobile body and other road users is recognized, the host mobile body generates warning information that warns of the envelope violation to be transmitted to the target mobile body. In this way, the envelope violation warned by the host mobile body regarding other road users can be commonly recognized by the target mobile body, which can promote improvement of the response capability to other road users.

[0012] The present disclosure four The aspect is A processing method executed by a processor to perform processing related to driving of a host vehicle capable of communicating with a target vehicle, comprising: Obtaining warning information from the target moving body that warns of an envelope violation, which is a violation of a safety envelope between the target moving body and other road users, the safety envelope being set in the target moving body to define the safety of intended functions between the target moving body and other road users other than the host moving body; In response to obtaining the warning information, determining whether there is an envelope violation, which is a violation of the safety envelope between the host mobile unit and another road user.

[0013] The present disclosure Five 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 Obtaining warning information from the target moving body that warns of an envelope violation, which is a violation of a safety envelope between the target moving body and other road users, the safety of intended functions between the target moving body and other road users other than the host moving body being set in the target moving body; In response to obtaining the warning information, the vehicle is configured to determine whether there is an envelope violation, which is a violation of the safety envelope between the host mobile unit and another road user.

[0014] The present disclosure Six 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, Obtaining warning information from the target moving body that warns of an envelope violation, which is a violation of a safety envelope between the target moving body and other road users, the safety of intended functions between the target moving body and other road users other than the host moving body being set in the target moving body; In response to obtaining the warning information, determining whether there is an envelope violation, which is a violation of the safety envelope between the host mobile unit and another road user.

[0015] These four ~ SixIn the host mobile of the embodiment, warning information is acquired from the target mobile, which warns of an envelope violation, which is a violation of a safety envelope that sets the safety of the intended functions between the target mobile and other road users other than the host mobile. In response to the acquisition of the warning information, the host mobile determines whether or not there is an envelope violation between the target mobile and other road users. In this way, the envelope violation warned by the target mobile with respect to other road users is commonly recognized in the host mobile and can be reflected in the determination of the existence of an envelope violation, which can promote the improvement of the response ability to other road users. [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] 1 is a schematic diagram showing an example of a lane structure and a processing method according to a first embodiment; [Figure 15] 1 is a schematic diagram showing an example of a lane structure and a processing method according to a first embodiment; [Figure 16] 4 is a flowchart showing a processing method according to the first embodiment. [Figure 17] 4 is a flowchart showing a processing method according to the first embodiment. [Figure 18] 10 is a flowchart showing a processing method according to a second embodiment. [Figure 19] 10 is a flowchart showing a processing method according to a second embodiment. [Figure 20] FIG. 13 is a block diagram showing a processing system according to a third embodiment. [Figure 21] FIG. 13 is a block diagram showing a processing system according to a fourth embodiment. [Figure 22] FIG. 13 is a block diagram showing a processing system according to a fifth embodiment. [Figure 23] FIG. 13 is a block diagram showing a processing system according to a sixth embodiment. [Figure 24] 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 shapes 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 shapes 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 15, 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] As shown in Figs. 10 to 15, the risk monitoring block 140 assumes a model envelope Em as a safety envelope based on the above-described safety model among the safety envelopes set in accordance with the SOTIF operation policy. Furthermore, the risk monitoring block 140 assumes an extended envelope Ee as a safety envelope obtained by adding a physically-based margin to the model envelope Em. Under these assumptions, the safety distance that defines the extended envelope Ee is set to be larger than the safety distance that defines the model envelope Em. That is, the extended envelope Ee is set in a wide range that includes the model envelope Em. Therefore, the margin may be set so as to add a fixed distance or a variable distance based on, for example, a safety model, to the safety distance of the model envelope Em.

[0056] 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 Figures 16 and 17, respectively. The processing method of the first embodiment is repeatedly executed in each of the vehicles 2a, 2b while the mutual distance between the first vehicle 2a and the second vehicle 2b is within a set range. Note that each "S" in the processing method in the following description refers to multiple steps executed by multiple commands included in a processing program in the processing system 1 of each of the vehicles 2a, 2b.

[0057] 16 and 17, 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 perform mutual authentication. 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.

[0058] As shown in FIG. 16, in S101 following S100 of the processing method, the risk monitoring block 140 of the first vehicle 2a determines whether or not other road users 3 other than the second vehicle 2b, whose mutual distance with the first vehicle 2a falls within the monitoring range of the safety envelope, are recognized. The presence or absence of recognition of other road users 3 other than the second vehicle 2b is determined based on detection information by the detection block 100 of the first vehicle 2a. The monitoring range of the safety envelope in the first vehicle 2a is set to a wide range that includes the model envelope Em and the extended envelope Ee shown in FIGS. 10 to 12. Therefore, if the risk monitoring block 140 of the first vehicle 2a determines in S101 that other road users 3 other than the second vehicle 2b are recognized in the monitoring range of the first vehicle 2a, the current flow in the first vehicle 2a proceeds to S102 as shown in FIG. 16.

[0059] In S102, the risk monitoring block 140 of the first vehicle 2a monitors an envelope violation regarding the safety envelope between the first vehicle 2a and other road users 3 other than the second vehicle 2b based on the safety model of the first vehicle 2a. As shown in Fig. 10, in the first vehicle 2a, if the whole of the other road users 3 other than the second vehicle 2b exists outside the range of the extended envelope Ee and outside the range of the model envelope Em, the envelope violation is not recognized. Therefore, in S102, if the risk monitoring block 140 of the first vehicle 2a makes a determination that there is no envelope violation, the current flow in the first vehicle 2a ends as shown in Fig. 16.

[0060] On the other hand, in the first vehicle 2a, when at least a part of the other road user 3 other than the second vehicle 2b is present within the range of the extended envelope Ee outside the range of the model envelope Em as shown in Fig. 11, an extended envelope violation is recognized as an envelope violation. Also, in the first vehicle 2a, when at least a part of the other road user 3 other than the second vehicle 2b is present within the range of the model envelope Em within the range of the extended envelope Ee as shown in Fig. 12, a model envelope violation is recognized as an envelope violation.

[0061] Therefore, in S102, when the risk monitoring block 140 of the first vehicle 2a makes a determination regarding either a model envelope violation or an extended model violation, the current flow in the first vehicle 2a sequentially proceeds to S103 and S104 as shown in Fig. 16. That is, S103 and S104 are executed when an envelope violation between the first vehicle 2a and another road user 3 other than the second vehicle 2b is recognized, which is detected in the first vehicle 2a.

[0062] In S103, the risk monitoring block 140 of the first vehicle 2a generates warning information Iw for warning the second vehicle 2b of an envelope violation between the first vehicle 2a and the other road user 3. The warning information Iw may include notification information In that is a push notification from the first vehicle 2a to the second vehicle 2b of the occurrence of an 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.

[0063] 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 type, 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 other road user 3 by a safety model that defines the safety envelope that is the criterion for determining an envelope violation.

[0064] 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.

[0065] The envelope information Ise may represent at least one of the detection information of the other road user 3 detected by the detection block 100 of the first vehicle 2a in the envelope violation scene, such as an estimated state including a position, a distance, a speed, an acceleration / deceleration, a relative speed, a relative acceleration, and vectors thereof, and a type. In particular, the envelope information Ise may represent at least one of the detection information detected by the detection block 100 of the first vehicle 2a, such as the speed and acceleration / deceleration of the other road user 3, as a motion physical quantity of the envelope violation that is outside 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 other road user 3 captured by a camera that is the external sensor 50 of the first vehicle 2a in the envelope violation scene.

[0066] 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.

[0067] The warning information Iw generated in S103 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.

[0068] In S104, 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 S104 is completed, the current flow at the first vehicle 2a ends.

[0069] As shown in FIG. 17, in S111 following the above-mentioned S110, the risk monitoring block 140 of the second vehicle 2b determines whether or not other road users 3 other than the first vehicle 2a, whose mutual distance from the second vehicle 2b falls within the monitoring range of the safety envelope, are recognized. The presence or absence of recognition of other road users 3 other than the first vehicle 2a is determined based on detection information by the detection block 100 of the second vehicle 2b. The monitoring range of the safety envelope in the second vehicle 2b is set to a wide range that includes the model envelope Em and the extended envelope Ee shown in FIGS. 13 to 15. Here, the monitoring range of the safety envelope in the second vehicle 2b, the range of the model envelope Em, and the range of the extended envelope Ee are set to the same or different ranges as those in the first vehicle 2a. Therefore, if the risk monitoring block 140 of the second vehicle 2b determines in S111 that no other road users 3 other than the first vehicle 2a are recognized within the monitoring range of the second vehicle 2b, the current flow for the second vehicle 2b transitions to S115, as shown in Figure 17.

[0070] In S115, 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 S115 that the warning information Iw has not been received, the current flow in the second vehicle 2b ends.

[0071] On the other hand, if the risk monitoring block 140 of the second vehicle 2b determines in S115 that the warning information Iw has been acquired, the current flow in the second vehicle 2b proceeds to S116 and S117 in sequence. That is, S116 and S117 are executed in real time in response to the acquisition of the warning information Iw when, as shown in Figs. 11 and 12, an envelope violation between the first vehicle 2a and another road user 3 other than the second vehicle 2b is recognized in the first vehicle 2a, but the other road user 3 that is the subject of the violation is outside the detection range of the second vehicle 2b.

[0072] As shown in FIG. 17, in S116, 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.

[0073] In S117, the risk monitoring block 140 of the second vehicle 2b determines whether or not there is an envelope violation with respect to the safety envelope between the second vehicle 2b and the other road user 3 not detected by the second vehicle 2b, who has been notified of the warning information Iw as a violation target in the first vehicle 2a. As shown in Fig. 11, in the second vehicle 2b, if the whole of the other road user 3 not detected is outside the range of the extended envelope Ee and outside the range of the model envelope Em, the envelope violation is not recognized. Therefore, in S117, if the risk monitoring block 140 of the second vehicle 2b determines that there is no envelope violation, the current flow in the second vehicle 2b ends.

[0074] On the other hand, as shown in FIG. 12, in the second vehicle 2b, when at least a part of the other road user 3 that is not detected exists within the range of the extended envelope Ee outside the range of the model envelope Em, an extended envelope violation is recognized as an envelope violation. Also, although not shown, in the second vehicle 2b, when at least a part of the other road user 3 that is not detected exists within the range of the model envelope Em within the range of the extended envelope Ee, a model envelope violation is recognized as an envelope violation. For these recognitions, it is preferable that information on the other road user 3 that is the violation target of the first vehicle 2a is added to the warning information Iw as the situation information Is, or particularly the envelope information Ise therein. The information on the other road user 3 that is the violation target of the first vehicle 2a may be acquired, for example, from a remote center or the like through the communication system 6 of the second vehicle 2b.

[0075] Therefore, in S117, if the risk monitoring block 140 of the second vehicle 2b makes a determination that there is either a model envelope violation or an extended model violation, the current flow in the second vehicle 2b proceeds to S118.

[0076] In S118, the risk monitoring block 140 in the second vehicle 2b sets a constraint for avoiding an unreasonable risk to the motion control of the second vehicle 2b. The constraint for risk avoidance may be a limiting command for the control block 160 of the second vehicle 2b, which provides a constraint for moving the second vehicle 2b to a minimum risk state. However, if the envelope violation recognized in S117 is at least an extended envelope violation, such a constraint may not be set in S118, and information on the other road user 3 violating the extended envelope may be commonly recognized with the first vehicle 2a as detection information by the detection block 100 in the second vehicle 2b. When the execution of S118 is completed, the current flow in the second vehicle 2b ends.

[0077] 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.

[0078] As shown in Figure 17, if the risk monitoring block 140 of the second vehicle 2b determines in S111 that another road user 3 other than the first vehicle 2a is recognized within the monitoring range of the second vehicle 2b, the current flow for the second vehicle 2b transitions to S112.

[0079] In S112, the risk monitoring block 140 of the second vehicle 2b monitors an envelope violation regarding the safety envelope between the second vehicle 2b and other road users 3 other than the first vehicle 2a based on the safety model of the second vehicle 2b. As shown in Fig. 13, in the second vehicle 2b, if the whole of the other road users 3 other than the second vehicle 2b exists outside the range of the extended envelope Ee and outside the range of the model envelope Em, the envelope violation is not recognized. Therefore, in S112, if the risk monitoring block 140 of the second vehicle 2b makes a determination that there is no envelope violation, the current flow for the second vehicle 2b ends as shown in Fig. 17.

[0080] Before the end of the current flow after the determination of no envelope violation in S112, the risk monitoring block 140 of the second vehicle 2b may achieve common recognition with the first vehicle 2a by executing the acquisition and determination process of warning information Iw in accordance with S115. Similarly, before the end of the current flow after the determination of no envelope violation in S102 described above, the risk monitoring block 140 of the first vehicle 2a may achieve common recognition with the second vehicle 2b by executing the acquisition and determination process of warning information Iw in accordance with S115.

[0081] On the other hand, in the second vehicle 2b, when at least a part of the other road user 3 other than the first vehicle 2a is present within the range of the extended envelope Ee outside the range of the model envelope Em as shown in Fig. 14, an extended envelope violation is recognized as an envelope violation. Also, in the second vehicle 2b, when at least a part of the other road user 3 other than the first vehicle 2a is present within the range of the model envelope Em within the range of the extended envelope Ee as shown in Fig. 15, a model envelope violation is recognized as an envelope violation.

[0082] Therefore, in S112, when the risk monitoring block 140 of the second vehicle 2b makes a determination of presence of either a model envelope violation or an extended model violation, the current flow in the second vehicle 2b sequentially proceeds to S113 and S114 as shown in Fig. 17. That is, S113 and S114 are executed when an envelope violation between the second vehicle 2b and another road user 3 other than the first vehicle 2a is recognized, which is detected in the second vehicle 2b.

[0083] In S113, the risk monitoring block 140 of the second vehicle 2b executes a process for generating the warning information Iw, which is the same as the process in S103, except that the first vehicle 2a and the second vehicle 2b are interpreted in reverse. In S114, the risk monitoring block 140 of the second vehicle 2b executes a process for storing the warning information Iw, which is the same as the process in S104, except that the first vehicle 2a and the second vehicle 2b are interpreted in reverse. When the execution of S114 is completed, the current flow for the second vehicle 2b ends.

[0084] Before executing S114 or before the end of the current flow after executing S114, the risk monitoring block 140 of the second vehicle 2b may execute the acquisition determination process of the warning information Iw in accordance with S115, thereby achieving common recognition with the first vehicle 2a. Similarly, before executing the above-mentioned S104 or before the end of the current flow after executing S104, the risk monitoring block 140 of the first vehicle 2a may execute the acquisition determination process of the warning information Iw in accordance with S115, thereby achieving common recognition with the second vehicle 2b.

[0085] As shown in Figure 16, if the risk monitoring block 140 of the first vehicle 2a determines in S101 that no other road users 3 other than the second vehicle 2b are recognized within the monitoring range of the first vehicle 2a, the current flow for the first vehicle 2a transitions to S105.

[0086] In S105, the risk monitoring block 140 of the first vehicle 2a executes a process for determining whether or not the warning information Iw has been acquired, in which the first vehicle 2a and the second vehicle 2b in the description of S115 are interpreted in reverse. Therefore, in S105, if the risk monitoring block 140 of the first vehicle 2a determines that the warning information Iw has not been acquired, the current flow for the first vehicle 2a ends.

[0087] On the other hand, if the risk monitoring block 140 of the first vehicle 2a determines in S105 that the warning information Iw has been acquired, the current flow in the first vehicle 2a proceeds to S106 and S107 in sequence. That is, S106 and S107 are executed in real time in response to the acquisition of the warning information Iw when, as shown in Figs. 14 and 15, an envelope violation between the second vehicle 2b and another road user 3 other than the first vehicle 2a is recognized, but the other road user 3 that is the subject of the violation is outside the detection range of the first vehicle 2a.

[0088] 16, in S106, the risk monitoring block 140 of the first vehicle 2a executes a process for storing the warning information Iw in a manner similar to that described in S116, except that the first vehicle 2a and the second vehicle 2b are interpreted in reverse. In S107, the risk monitoring block 140 of the first vehicle 2a executes a process for determining whether or not an envelope has been violated in a manner similar to that described in S117, except that the first vehicle 2a and the second vehicle 2b are interpreted in reverse.

[0089] 14, in the first vehicle 2a, if the entire undetected other road user 3 is outside the range of the extended envelope Ee and outside the range of the model envelope Em, the envelope violation is not recognized. Therefore, in S107, if the risk monitoring block 140 of the first vehicle 2a makes a determination that there is no envelope violation, the current flow for the first vehicle 2a ends.

[0090] On the other hand, as shown in FIG. 15, in the first vehicle 2a, when at least a part of the other road user 3 that is not detected exists within the range of the extended envelope Ee outside the range of the model envelope Em, an extended envelope violation is recognized as an envelope violation. In addition, although not shown, in the first vehicle 2a, when at least a part of the other road user 3 that is not detected exists within the range of the model envelope Em within the range of the extended envelope Ee, a model envelope violation is recognized as an envelope violation. For these recognitions, it is preferable that information on the other road user 3 that is the violation target of the second vehicle 2b is added to the warning information Iw as the situation information Is, or particularly the envelope information Ise therein. The information on the other road user 3 that is the violation target of the second vehicle 2b may be acquired, for example, from a remote center or the like through the communication system 6 of the first vehicle 2a.

[0091] Therefore, in S107, if the risk monitoring block 140 of the first vehicle 2a makes a determination that there is either a model envelope violation or an extended model violation, the current flow for the first vehicle 2a proceeds to S108. In the first vehicle 2a in S108, the risk monitoring block 140 executes a constraint setting process in which the first vehicle 2a and the second vehicle 2b in the description of S118 are interpreted in reverse. When the execution of S108 is completed, the current flow for the first vehicle 2a ends.

[0092] 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 with other road users 3 other than the second vehicle 2b as a target moving body. Thus, when an envelope violation with the other road user 3 is recognized, the first vehicle 2a generates warning information Iw that warns of the envelope violation to be transmitted to the second vehicle 2b. According to this, the envelope violation warned by the first vehicle 2a with respect to the other road user 3 can be commonly recognized in the second vehicle 2b as well, which makes it possible to promote improvement of response capabilities to other road users.

[0093] On the other hand, from the viewpoint of the second vehicle 2b in the first embodiment, the second vehicle 2b as a 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 has been set in the first vehicle 2a as a target moving body with other road users other than the second vehicle 2b. In response to the acquisition of the warning information Iw, the second vehicle 2b determines whether or not there is an envelope violation with the other road user 3. According to this, the envelope violation warned by the first vehicle 2a with respect to the other road user 3 can be commonly recognized in the second vehicle 2b and reflected in the determination of the presence or absence of an envelope violation, which can promote improvement of response capabilities to other road users.

[0094] 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 with other road users 3 other than the first vehicle 2a as a target moving body. Thus, when an envelope violation with the other road user 3 is recognized, the second vehicle 2b also generates warning information Iw that warns of the envelope violation to be transmitted to the first vehicle 2a. According to this, the envelope violation warned by the second vehicle 2b with respect to the other road user 3 can be commonly recognized in the first vehicle 2a, so that it is possible to promote improvement of the response ability to other road users.

[0095] 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 has been set between the second vehicle 2b as a target moving body and other road users other than the first vehicle 2a. In response to the acquisition of the warning information Iw, the first vehicle 2a also determines whether or not there is an envelope violation between the second vehicle 2b and the other road user 3. According to this, the envelope violation warned by the second vehicle 2b with respect to the other road user 3 is commonly recognized in the first vehicle 2a and can be reflected in the determination of the existence of an envelope violation, so that it is possible to promote improvement of the response capability to other road users.

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

[0097] 18 and 19 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. Accordingly, the processing method adds S2109, S2120, and S2121 for the first vehicle 2a and S2119, S2130, and S2131 for the second vehicle 2b.

[0098] 19, whether after determining that there is no envelope violation in S117 or after executing S118, in S2119, 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 sending a 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 S103, 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.

[0099] The warning information Iw generated in S2119 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 S2119 is completed, the current flow in the second vehicle 2b ends.

[0100] 18, in S2120 following S104, 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 S2120 that the feedback information If has been acquired, the current flow for the first vehicle 2a ends.

[0101] By performing S2120, the risk monitoring block 140 of the first vehicle 2a can check whether a common recognition has been achieved with the second vehicle 2b. In addition, in S2120, 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 S2120, 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 S104 in the memory 10 of the first vehicle 2a.

[0102] On the other hand, when the risk monitoring block 140 of the first vehicle 2a judges in S2120 that the feedback information If has not been acquired, the current flow in the first vehicle 2a proceeds to S2121. In S2121, the risk monitoring block 140 of the first vehicle 2a sets a constraint for the motion control of the first vehicle 2a to avoid an unreasonable risk for the possibility that the other road user 3 of the violation target is not detected by the second vehicle 2b, or the envelope violation of the other road user 3 is not recognized by the second vehicle 2b. The constraint for risk avoidance may be a restriction command for the control block 160 of the first vehicle 2a, which gives a constraint for moving the first vehicle 2a to the minimum risk state. In addition, the constraint for risk avoidance may be at least one minor constraint among a speed limit, an acceleration limit, and a first vehicle 2a moving away from the second vehicle 2b. Such a constraint setting process enables a safer risk avoidance action when the first vehicle 2a cannot 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 S2121 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 S102 of the next flow, the generation and transmission of warning information Iw is repeated in S103 of the next flow.

[0103] 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.

[0104] 18, whether after determining no envelope violation in S107 or after executing S108, in S2109, the risk monitoring block 140 of the first vehicle 2a executes a process for generating feedback information If in which the first vehicle 2a and the second vehicle 2b in the description of S2119 are interpreted in reverse. When the execution of S2109 is completed, the current flow for the first vehicle 2a ends.

[0105] 19, in S2130 following S114, 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 S2120 are interpreted in reverse. Thus, in S2130, if the risk monitoring block 140 of the second vehicle 2b determines that feedback information If has been acquired, the current flow for the second vehicle 2b ends.

[0106] By performing S2130, the risk monitoring block 140 of the second vehicle 2b can check whether a common recognition with the first vehicle 2a has been achieved. In addition, in S2130, 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 S2130, 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 S114 in the memory 10 of the second vehicle 2b.

[0107] On the other hand, if the risk monitoring block 140 of the second vehicle 2b determines in 2130 that the feedback information If has not been acquired, the current flow in the second vehicle 2b proceeds to S2131. In S2131, 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 S2121 are read in reverse as a constraint setting process for risk avoidance against the possibility that the other road user 3 who is the violation target is not detected by the first vehicle 2a, or the envelope violation of the other road user 3 is not recognized by the first vehicle 2a. Such a constraint setting process enables a safer risk avoidance action when the second vehicle 2b cannot 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 communication system 6 not being installed in the first vehicle 2a. When the execution of S2131 is completed, the current flow in the second vehicle 2b ends. In addition, in the second vehicle 2b where the current flow has ended without obtaining the feedback information If, if the envelope violation continues in S112 of the next flow, the generation and transmission of the warning information Iw will be repeated in S113 of the next flow.

[0108] In the second embodiment, the processing methods S2109, S2120, S2121 and S2119, S2130, S2131 are added to the first embodiment and are executed mainly by the risk monitoring blocks 140 of the first vehicle 2a and the second vehicle 2b. Therefore, it is possible to promote improvement of the response ability to other road users.

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

[0110] As shown in FIG. 20, 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 in accordance with 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 in accordance with 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.

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

[0112] Fourth embodiment The fourth embodiment is a modification of the third embodiment.

[0113] As shown in FIG. 21, 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.

[0114] 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 other road users. The fourth embodiment described so far may be combined with the second embodiment.

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

[0116] 22, 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.

[0117] 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. Therefore, it is possible to promote improvement of the response ability to other road users. The fifth embodiment described so far may be combined with the second embodiment. However, when the fifth embodiment is combined with the second embodiment, in S2121 and S2131, an evaluation of the driving control based on the set constraints is executed.

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

[0119] As shown in FIGS. 23 and 24, the sixth embodiment is further provided with a test block 6180 for testing 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 the processing system 1 shown in FIG. 23 executing a test program added to the processing program for constructing each of the blocks 100, 120, 140, and 160. The test block 6180 may be constructed by a test processing system 6001 different from the processing system 1, as shown in FIG. 24, executing a test processing program different from the processing program for constructing each of the blocks 100, 120, 140, and 160. Here, the test processing system 6001 may be configured by at least one dedicated computer having a memory 10 and a processor 12, which 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).

[0120] In such a sixth embodiment, a processing method equivalent to the first embodiment is executed mainly by each test block 6180 of the first vehicle 2a and the second vehicle 2b. Therefore, it is possible to promote improvement of response capability to other road users. Note that 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 S2121 and S2131, evaluation of driving control as a test is executed based on the set constraints. (Other embodiments)

[0121] 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.

[0122] 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.

[0123] In the processing method of the modified example, in S102, S107, S112, and S117, the presence or absence of an envelope violation may be determined for only one of the model envelope Em and the extended envelope Ee as the safety envelope. In this case, in the processing method of S101 and S110, a monitoring range of the safety envelope may be set to a range including the model envelope Em or the extended envelope Ee, which is the subject of the envelope violation determination.

[0124] In the processing method of the modified example, the storage process of warning information Iw in S104 and S114 may be omitted. In the processing method of the modified example, the storage process of warning information Iw in S106 and S116 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 envelope violations, which are violations of a safety envelope that defines the safety of the intended functionality of the host vehicle with respect to other road users (3) other than the target vehicle; 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.

2. 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 envelope violations, which are violations of a safety envelope that defines the safety of the intended functionality of the host vehicle with respect to other road users (3) other than the target vehicle; 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.

3. 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 an envelope violation, which is a violation of a safety envelope that defines the safety of the intended function between the host vehicle and other road users (3) other than the target vehicle; 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.

4. A processing method executed by a processor (12) to perform processing related to operation of a host vehicle (2b, 2a) capable of communicating with a target vehicle (2a, 2b), comprising: Obtaining warning information (Iw) from the target moving body, which warns of an envelope violation, which is a violation of a safety envelope between the target moving body and the other road user (3) other than the host moving body, in which the safety of intended functions between the target moving body and the other road user (3) is set; In response to obtaining the warning information, determining whether there is an envelope violation, which is a violation of a safety envelope between the host mobile body and the other road user.

5. Determining whether or not there is an envelope violation comprises: The processing method of claim 4, further comprising determining whether or not there is a violation of a model envelope (Em) between the host mobile unit and the other road user as the safety envelope between the host mobile unit and the other road user based on a safety model that models the safety of the intended function.

6. Determining whether or not there is an envelope violation comprises: The processing method described in claim 4 or 5, further comprising determining whether or not there is a violation of the safety envelope between the host mobile unit and the other road user with respect to an extended envelope (Ee) obtained by adding a physics-based margin to the safety envelope between the host mobile unit and the other road user based on a safety model that models the safety of the intended function.

7. Determining whether or not there is an envelope violation comprises: A processing method described in any one of claims 4 to 6, comprising, when the other road user is not detected by the host mobile body, determining whether or not there is an envelope violation between the host mobile body and the other road user in response to obtaining the warning information.

8. The obtaining of the warning information includes: The processing method according to any one of claims 4 to 7, further comprising obtaining the warning information from the target moving body, which pushes notifies the envelope violation between the target moving body and the other road user.

9. The obtaining of the warning information includes: The processing method according to any one of claims 4 to 8, further comprising obtaining the warning information added to envelope information (Ise) regarding the safety envelope between the target moving body and the other road user, the envelope information being set in the target moving body.

10. The processing method according to any one of claims 4 to 9, further comprising storing the acquired warning information.

11. The processing method according to any one of claims 4 to 10, further comprising: generating, for transmission, feedback information (If) for feeding back the acquisition of the warning information to the target moving body.

12. A processing system (1) including a processor (12) for performing processing related to the operation of a host vehicle (2b, 2a) capable of communicating with a target vehicle (2a, 2b), comprising: The processor, Obtaining warning information (Iw) from the target moving body, which warns of an envelope violation, which is a violation of a safety envelope between the target moving body and the other road user (3) other than the host moving body, in which the safety of intended functions between the target moving body and the other road user (3) is set; and in response to obtaining the warning information, determining whether there is an envelope violation, which is a violation of a safety envelope between the host mobile unit and the other road user.

13. 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 (2b, 2a) capable of communicating with a target moving body (2a, 2b), The instruction: Obtaining warning information (Iw) from the target moving body, the warning information warning of an envelope violation, which is a violation of a safety envelope between the target moving body and the other road user (3) other than the host moving body, the safety of the intended function between the target moving body and the other road user (3) other than the host moving body; and determining, in response to acquisition of the warning information, whether or not there is an envelope violation, which is a violation of a safety envelope between the host mobile body and the other road user.

Citation Information

Patent Citations

  • Distance alarming device for vehicle

    JP1998250510A

  • Car navigation system

    JP2002168640A

  • Operation support system

    JP2009059200A

  • Driving support device and driving support system

    JP2019109795A

  • Navigation systems with imposed liability constraints

    JP6708793B2