Patent Grant
11299112
The present invention relates to an onboard system to which an onboard dedicated electronic control device and a plurality of electronic control devices are connected through an onboard network.
In recent years, according to enhancement in an automobile function, digitalizing a vehicle has progressed, the number of vehicle Electronic Control Units (ECUs), and the amount of information transmitted between the ECUs has increased. Henceforth, by realization and evolution of the autonomous driving function, it has been considered that the number of sensors such as a camera or a radar which is required to grasp a situation of the vicinity of a vehicle has increased. Therefore, a CPU processing load for processing sensing data which is output from a sensor, and a load of a network transmission path between the sensor and the ECU or between the ECUs has increased. Since a CPU performance or a network bandwidth is finite, it is important to reduce the amount of data of the above described sensing data.
PTL 1 discloses a technique in which a communication bandwidth is suppressed by reducing data exchanged between ECUs when an event (network failure) occurs. A communication system disclosed in PTL 1 connects control unit each other by CAN buses of two systems for a main use and a backup use, first data (driving use data+pleasantness improvement data) which is classified in advance is transmitted and received by the CAN bus for the main use and second data (driving use data) of which an amount of data is less than that of the first data is transmitted and received by the CAN bus for the backup use. In addition, when a breakdown of any of the CAN buses of the two systems is detected, transmission and reception are performed by using only a normal CAN bus, and thus at least the data for driving is able to be surely transmitted and received.
PTL 1: JP-A-2014-118072
The onboard system disclosed in PTL 1 uniformly reduces data transmitted from all the ECUs, but there is a desire to flexibly reduce according to a situation. For example, in an autonomous driving system, reducing data is necessary according to various situations such as the type of roads, a time slot, the climate, and the volume of traffic.
The present application includes a plurality of means for resolving the above problems, but for example, as disclosed in claims, an autonomous driving system in which an autonomous driving ECU and a plurality of data ECUs are connected with each other through a first network is configured. The autonomous driving ECU includes a first communication unit that transmits and receives autonomous driving data to and from the plurality of data ECUs, and a vehicle control unit that controls a vehicle on the basis of the autonomous driving data transmitted from the plurality of data ECUs. Each of the data ECUs includes a data construction unit that performs a construction of the autonomous driving data transmitted to the autonomous driving ECU, and a second communication unit that transmits and receives the autonomous driving data to and from the autonomous driving ECU. In a case in which a predetermined event occurs, among the plurality of data ECUs, the data construction unit of the data ECU in which the predetermined event occurs constructs the autonomous driving data so that a total amount of the autonomous driving data transmitted from the data ECU in which the predetermined event occurs is not greater than a predetermined amount of data.
It is possible to flexibly reduce an amount of data processed by an onboard electronic control device, and a communication amount of data transmitted and received between onboard electronic control devices.
Hereinafter, an example of the present invention is described with reference to drawings. In addition, the same numeral is written for the same elements and processing contents and descriptions thereof are omitted.
In Example 1, a configuration of a device, and a method for dynamically reducing information transmitted from a data ECU to the autonomous driving ECU, on the basis of a request instruction from the autonomous driving ECU to the data ECU at the time of a network failure occurrence as one of an event which becomes a trigger for reducing data, are described by using
In addition, an onboard use network uses a network which complies with a standard, such as Controller Area Network (CAN, registered trademark), a Local Interconnect Network (LIN), a FlexRay, a Media Oriented Systems Transport (MOST), and Ethernet (registered trademark) in many cases, but the present example is not limited thereto.
<Network Configuration>
(a) of
The autonomous driving ECU 1 calculates a control signal related to a driving control of a vehicle, for a high degree of support system or an autonomous driving system, by using external recognition information which specifies various objects (a sign, a landmark, a vehicle, a pedestrian, a movable body, an obstacle, and the like) around a host vehicle based on information on a sensor such as a camera or a radar, host vehicle position information with high precision calculated on the basis of Global Positioning System (GPS) information and driving related information on the host vehicle such as an acceleration and a rudder angle, map information with high precision for performing an autonomous driving such as an autonomous driving or a remote operation driving, and the like.
The data ECU 2 calculates and transmits the above described external recognition information, the host vehicle position information with high precision, or the map information with high precision, to the autonomous driving ECU 1.
The calculation processing of information (hereinafter, referred to as autonomous driving data) such as the external recognition information, the host vehicle position information with high precision, or the map information with high precision, which is required to the autonomous driving may be performed by a plurality of data ECUs 2 by assigning a part of the calculation processing to each of the plurality of data ECUs 2, and may be performed by the plurality of data ECUs 2 by cooperating the calculation processing.
In addition, a part or the entire of the calculation processing may be combined in the autonomous driving ECU 1. Further, basically, a transmission demand of the autonomous driving data from the autonomous driving ECU 1 to the data ECU 2 is not issued, and the autonomous driving data is transmitted from the data ECU 2 to the autonomous driving ECU 1 in a regular period.
The network switch 6 is a switch device for connecting the autonomous driving ECU 1 with the data ECU 2 by a star type network. An object of the present device is to perform a relay of data between a plurality of transmission paths, and the present device may be a device such as a switching hub, a router, and a gateway.
The main use network 10 is a transmission path for configuring a star type network, and for example, complies with an onboard use Ethernet.
The backup use network 20 is a transmission path for configuring a bus type network, and for example, complies with a CAN or a Controller Area Network-Flexible Data rate (CAN-FD).
(b) of
The network switch 7 is identical to the network switch 6, and is a device for relaying data. However, a corresponding communication interface may be different from that of the network switch 6.
The backup use network 30 is identical to the main use network 10, is a transmission path for configuring a star type network, and for example, complies with an onboard dedicated Ethernet (registered trademark). In addition, a configuration complying with a standard of which the highest communication rate is different from that of the main use network 10 is considered as an example.
In the configuration illustrated in
In addition, the configurations of the main use network 10 and the backup use network 20 may be replaced with each other. For example, in (a) of
In the below example, descriptions are performed by using the network configuration illustrated in (a) of
In addition, In
In addition, the configuration illustrated in
<System Configuration>
<Configuration of Autonomous Driving ECU 1>
The autonomous driving ECU 1 is configured with a high speed NW interface 100, a low speed NW interface 101, a communication control unit 102, an NW failure detection unit 103, a demand information determination unit 104, an autonomous driving situation determination unit 105, a vehicle control plan unit 106, a demand autonomous driving data construction unit 107, a vehicle control unit 108, and a control NW interface 109.
In the present example, it is assumed that the autonomous driving ECU 1 includes a CPU and a memory, which are not illustrated, and the high speed NW interface 100, the low speed NW interface 101, and the control NW interface 109 as hardware. The CPU performs an operation according to a program stored in the memory, and thus functions as the communication control unit 102, the NW failure detection unit 103, the demand information determination unit 104, the autonomous driving situation determination unit 105, the vehicle control plan unit 106, the demand autonomous driving data construction unit 107, and the vehicle control unit 108 are realized. But, the present example is not limited to such an embodiment, and loading the entirety or a part of the above described functions as hardware is possible.
The high speed NW interface 100 is an interface to be connected to the data ECU 2 through the main use network 10 and the network switch 6, and includes a connector complying with, for example, Ethernet (registered trademark), an Integrated Circuit (IC), a controller, a driver, and the like.
The low speed NW interface 101 is an interface to be connected to the data ECU 2 through the backup use network 20, and includes a connector complying with, for example, the CAN or CAN-FD, a transceiver, a controller, a driver, and the like.
The communication control unit 102 performs communication control for transmitting and receiving data through the high speed NW interface 100 and the low speed NW interface 101.
The NW failure detection unit 103 performs detection whether a failure occurs in the main use network 10. For example, the detection may be realized by a method in which a control packet for KeepAlive is transmitted and received between the autonomous driving ECU 1 and the data ECU 2 in a regular period, and an omission or a delay of the control packet is monitored.
The demand information determination unit 104 specifies a network failure range from a network failure location, and determines a reduction guideline of autonomous driving related information demanded from the autonomous driving ECU 1 to the data ECU 2, that is, autonomous driving related information transmitted from the data ECU 2 to the autonomous driving ECU 1. As the reduction guideline of the autonomous driving related information, there is, for example, a size, a classification, or the like of information. The reduction guideline of the autonomous driving related information indicates a guideline which reduces only the amount of information without changing the type of the transmitted and received information, or reduces the amount of the information by changing the type of the transmitted and received information. Specific processing contents of the demand information determination unit 104 are described later.
The autonomous driving situation determination unit 105 determines a load status of a driving speed of the host vehicle, information related to objects such as a movable body in the vicinity of the host vehicle, an obstacle, and a landmark, such as the volume of traffic of a movable body (vehicle, pedestrian, bicycle, and motorcycle) in the vicinity of the host vehicle, and a relative velocity between the host vehicle and another movable body, or the autonomous driving dedicated high precision map to the autonomous driving ECU 1. The determination information is used in information demanded from the autonomous driving ECU 1 to the data ECU 2, for reducing the autonomous driving data, in the demand autonomous driving data construction unit 107, which is described later.
The vehicle control plan unit 106 determines a vehicle driving control plan. The vehicle control plan indicates vehicle course (driving track) information which indicates how a vehicle is going to (going straight, left turn, right turn, lane change to the left, and lane change to the right) at the time of the failure occurrence, or vehicle course (driving track) information after the network failure occurrence determined on the basis of the information on the network failure range which is determined by the demand information determination unit 104. The vehicle course information after the network occurrence indicates information on a vehicle course (driving track), such as continuing the autonomous driving while maintaining the speed, continuing the autonomous driving while reducing the speed, stopping the vehicle at the shoulder of a road while gradually reducing the speed, and stopping the vehicle without stopping the vehicle at the shoulder of a road.
The demand automatic data construction unit 107 constructs contents information on the autonomous driving data demanded to the data ECU 2. The contents of the autonomous driving data demanded from the autonomous driving ECU 1 indicates coordinate information on two points for specifying a range 503 of a vehicle object, with respect to the data ECU 2 calculating vehicle recognition information by using a sensor which is described later. In addition, the contents of the autonomous driving data demanded from the autonomous driving ECU 1 indicates information for designating a range of updated map information, with respect to the data ECU 2 which provides map information with high precision.
The vehicle control unit 108 controls a driving of the vehicle by using the autonomous driving control related information transmitted from the data ECU 2.
The control NW interface 109 is an interface toward a control network of the vehicle, and the vehicle control unit 108 outputs a signal related to a vehicle driving control to a controller or an ECU such as an accelerator, a brake, and a steering, through the interface.
<Configuration of Data ECU 2>
The data ECU 2 is configured with a high speed NW interface 200, a low speed NW interface 201, an NW failure detection unit 202, a communication control unit 203, a demand autonomous driving data reception determination unit 204, and a demand autonomous driving data response construction transmission unit 205.
In the present example, it is assumed that the data ECU 2 includes a CPU and a memory, which are not illustrated, and the high speed NW interface 200, and the low speed NW interface 201 as hardware. The CPU performs an operation according to a program stored in the memory, and thus functions as the NW failure detection unit 202, the communication control unit 203, the demand autonomous driving data reception determination unit 204, and the demand autonomous driving data response construction transmission unit 205 are realized. But, the present example is not limited to such embodiment, and loading the entire or a part of the above described functions as hardware is possible.
The high speed NW interface 200 is identical to the high speed NW interface 100, and is an interface to be connected to the data ECU 2 through the main use network 10 and the network switch 6.
The low speed NW interface 201 is identical to the low speed NW interface 101, and is an interface to be connected to the data ECU 2 through the backup use network 20.
The NW failure detection unit 202 is identical to the NW failure detection unit 103, and performs detection on whether a failure occurs in the main use network 10. In addition, in a case in which the system is configured so that it is possible to detect the failure by only the autonomous driving ECU 1, the NW failure detection unit 202 may be omitted from the configuration.
The communication control unit 203 performs a communication control for data transmission and reception through the high speed NW interface 200 and the low speed NW interface 201.
The demand autonomous driving data reception determination unit 204 determines whether the demand autonomous driving data, which is transmitted from the autonomous driving ECU 1 through the backup use network 20, is received from the low speed NW interface 201 or not.
The demand autonomous driving data response construction transmission unit 205 creates, constructs, and transmits the autonomous driving data corresponding to a demand autonomous driving data request from the autonomous driving ECU 1, to the autonomous driving ECU 1 through the low speed NW interface 201.
<Operation of Demand Information Determination Unit 104>
A processing flow of the demand information determination unit 104 is illustrated in (a) of
In step S200, the determination of the failure occurrence location is performed. In a case in which the failure occurrence location is an autonomous driving ECU network, an information reduction pattern 1 is performed (step S201), in a case of the network switch 6, an information reduction pattern 2 is performed (step S202), and in a case in which the failure occurrence location is a data ECU network, an information reduction pattern 3 is performed (step S203).
In addition, the autonomous driving ECU network indicates a transmission path between the autonomous driving ECU 1 and the network switch 6, and the data ECU network indicates a transmission path between the data ECU 2 and the network switch 6. An object of the flow is to be able to change a reduction pattern of information according to the number of the data ECUs 2, from a change in the number of the data ECUs 2 using the backup use network 20, according to the failure occurrence location. Therefore, the information reduction pattern 1, pattern 2, and pattern 3 of step S201 to step S203 may be the same. In addition, the failure occurrence location of step S201 to step S203 may be further subdivided.
<Data Reduction Method 1>
An example of a method of determining information by the demand autonomous driving data construction unit 107, by using the determination information on the autonomous driving situation determination unit 105 is illustrated in
In reality, a movable body, an obstacle, a landmark, a white line, a road sign, and the like are also recognized, besides the vehicle, but, for simplification of description, it is limited to the vehicle.
The diagram is configured with a host vehicle 500, another vehicle 501, a range 502 of a vehicle object recognized from a sensor, a range 503 of the vehicle object transmitted from the data ECU 2 to the autonomous driving ECU 1, and a host vehicle driving speed 504.
(a) and (b) of
In (b) of
In addition, since the range 502 of the vehicle object and the range 503 of the vehicle object are a rectangle, in a case in which it is assumed that coordinates of right and left ends of the range 502 of the vehicle object recognized from the sensor are (0, 0)=(x coordinate, y coordinate), it is possible to perform expression by coordinates information on two location illustrated in the drawing. However, a shape of the object range may be other shapes other than the rectangular. In this case, if necessary, the coordinate information on two or more locations is used in the expression. In addition, it is considered that the shape of the object range is changeable according to the driving situation at the time of the failure occurrence.
<Data Reduction Method 2>
An example of a method of determining information by the demand autonomous driving data construction unit 107, by using the determination information on the autonomous driving situation determination unit 105 is illustrated in
(a) of
(b) and (c) of
In addition, the vehicle control plan unit 106 sets a point where the vehicle is able to reach by avoiding a turning at an intersecting point and the like that requires a complex control of the vehicle and where it is possible to assign the vehicle control authority as much secure as possible as the autonomous driving cancel release schedule point 604, in spite of the vehicle driving control plan until it is determined that the autonomous driving is not able to be continued. In addition, in a case in which it is determined that the autonomous driving is not able to be continued while the turning at the intersecting point is performed, the turning at the intersecting point is ended as it is, and then a point in which it is possible to assign the vehicle control authority by avoiding the complex control of the vehicle is set as the autonomous driving cancel release schedule point 604.
In a case of (b) of
On the other hand, even in a case in which the failure occurs in the network, in a case in which the autonomous driving is able to be continued, it is possible to reduce an amount of data by limiting an obtainment of the map information, which corresponds to the portion of 2 km at the normal time, to an obtainment corresponding to the portion of 1 km.
<Data Reduction Method 3>
An example of a method of determining information by the demand autonomous driving data construction unit 107, by using the determination information on the autonomous driving situation determination unit 105 is illustrated in
Similarly to
(a) of
Therefore, the range 503 of the vehicle object is changed according to the vehicle driving control plan, and thus it is possible to reduce the amount of the information on the vehicle object transmitted from the data ECU 2 to the autonomous driving ECU 1. In addition, in a case of an example of the load of the map with high precision of
As an example of another method of reducing data, a processing flow is conceivable in which the demanded autonomous driving data number 400 and a table of the data transmission pattern 401 corresponding to the demanded autonomous driving data number 400, shown in (b) of
Such demand autonomous driving data is transmitted through the backup use network 20 with respect to the data ECU 2 which is not able to transmit and receive data by using the main use network 10 by the network failure occurrence.
<Processing Sequence of Data Reduction Processing>
The present processing sequence is started in a case in which the NW failure detection unit 103 of the autonomous driving ECU 1 detects the network failure (S100).
In step S101, the NW failure detection unit 103 grasps a network failure range by specifying a network failure occurrence location, so as to determine a reduction pattern of information demanded to the data ECU 2 ((a) of
Then, a transition to step S102 is performed, and the autonomous driving situation determination unit 105 performs a determination of the driving situation of the host vehicle and the vehicles around the host vehicle or the load status of the map with high precision at the time of the network failure occurrence (
In addition, a transition to step S103 is performed, and the vehicle control plan unit 106 determines how the driving of the host vehicle is controlled at the time of the network failure occurrence (
Then, a transition to step S104 is performed. The demand autonomous driving data construction unit 107 determines and constructs the autonomous driving data (demand autonomous driving data request) demanded to the data ECU 2, by using the information determined by the NW failure detection unit 103, the autonomous driving situation determination unit 105, and the vehicle control plan unit 106 in S101 to S103, and transmits the autonomous driving data to the backup use network 20 (data ECU 2) through the low speed NW interface 101. In the autonomous driving ECU 1, the processes from S100 to S104 are repeated until the NW failure detection unit 103 does not detect the network failure.
In addition, in step S104, the demand autonomous driving data request, which is constructed by the demand autonomous driving data construction unit 107 and transmitted through the low speed NW interface 101 may be transmitted in a case in which the network failure does not occur as well as after the network failure occurs. At this time, the transmission may be performed through the low speed NW interface 101, and in a case in which the network failure does not occur, the high speed NW interface 100 may be used.
In a case in which the communication control unit 203 of the data ECU 2 receives the demand autonomous driving data request, a transition to step S106 is performed.
In step S106, a determination of the autonomous driving data which is demanded from the autonomous driving ECU 1 is performed, on the basis of the demand autonomous driving data request.
In addition, a transition to step S107 is performed, and the demand autonomous driving data response construction transmission unit 205 performs a construction of the autonomous driving data determined by step S106.
Then, a transition to step S108 is performed, and the communication control unit 203 performs a transmission to the autonomous driving ECU 1 through the low speed NW interface 201 and the backup use network 20.
It is possible to reduce the amount of information on the autonomous driving related data to be transmitted and received between the ECUs at the time of the network failure occurrence, by the operation described above. Therefore, it is possible to configure the backup use network 20 as a narrow bandwidth in comparison with the main use network 10, or to share a network between a plurality of ECUs like a bus type topology such as the CAN. Thus, in comparison with the CAN, it is possible to construct a network with low cost and high reliability in comparison with a case in which a communication method with high cost such as Ethernet is applied to the backup use network 20.
In Example 1, although the communication method at the time of the network failure occurrence is described, it is possible to apply the present example to a case in which another event other than the network failure occurs.
As the other event, a case in which the number of objects detected or recognized by a sensor for an external recognizing such as a camera or a radar is equal to or greater than a threshold value, and a case in which a processing load such as a CPU use rate in the autonomous driving ECU 1 is equal to or greater than a threshold value are considered. In this case, the autonomous driving ECU 1 and the data ECU 2 may perform communication through the main use network 10, or may perform communication through the backup use network 20.
In a case in which an amount of data is reduced by using the CPU use rate as a trigger, it is necessary for the autonomous driving ECU 2 to include a CPU monitor unit which monitors an amount of use of a CPU in
In a case in which the autonomous driving ECU 1 detects such an event (it is also possible to detect by information sharing with the data ECU 2), the amount of information on the autonomous driving data which is transmitted from the data ECU 2 to the autonomous driving ECU 1 is reduced, in a manner identical to the case of the network failure occurrence of Example 1. Therefore, it is possible to avoid a situation in which the autonomous driving system is not functioned completely by a reason such as stopping the continuous processing by the autonomous driving ECU 1, at the time of the event occurrence.
In addition, as an example of another event, a case in which a failure occurs in a portion of the autonomous driving ECU 1 or the data ECU 2, or an application of the present example in a case in which an arrival at a specific point or area is performed in association with information on the map with high precision or information provided from a cloud is considered.
By changing a kind of information on autonomous driving data transmitted from the data ECU 2 to the autonomous driving ECU 1 at the time of the occurrence of such an event, it is possible to avoid the situation in which the autonomous driving system is not functioned completely at the time of the event occurrence. In addition, the specific point or area indicates an area in which an external recognition object recognized by a sensor such as a camera or a radar in a town or the like becomes voluminous, an area in which a road or a landmark is newly built, an area in which a traffic rule is changed, an area in which an accident occurs due to an incorrect detection of the external recognition object, and the like.
In association with reducing the amount of information on the autonomous driving data at the time of the occurrence of the above described various events, in a case of the configuration in which the autonomous driving data is transmitted from the data ECU 2 to the autonomous driving ECU 1, when a failure does not occur in the main use network 10, the autonomous driving data may be transmitted and received by using the main use network 10.
In addition, in association with reducing the amount of information on the autonomous driving data illustrated in
In Example 2, a configuration of a device, and a method for reducing information transmitted from the data ECU 2 to the autonomous driving ECU 1 dynamically, or in a predetermined fixed pattern, without receiving a request instruction from the autonomous driving ECU 1 to the data ECU 2, at the time of a network failure occurrence, are described by using
The autonomous driving ECU 1 is configured with the high speed NW interface 100, the low speed NW interface 101, the communication control unit 102, the NW failure detection unit 103, the vehicle control unit 108, the control NW interface 109, and an NW failure information notification unit 800.
In the configuration, compared to the autonomous driving ECU 1 in Example 1, the demand information determination unit 104, the autonomous driving situation determination unit 105, the vehicle control plan unit 106, and the demand autonomous driving data construction unit 107 are removed, and the NW failure information notification unit 800 is newly added.
The NW failure information notification unit 800 notifies the data ECU 2 of the network failure information detected by the NW failure detection unit 103, through the high speed NW interface 100 or the low speed NW interface 101, so as to share failure information between each of the ECUs.
The data ECU 2 is configured with the high speed NW interface 200, the low speed NW interface 201, the NW failure detection unit 202, the communication control unit 203, an NW failure information notification unit 801, a backup NW transmission autonomous driving data determination unit 802, and a backup NW transmission autonomous driving data construction unit 803.
In the configuration, compared to the configuration of the data ECU 2 in Example 1, the demand autonomous driving data reception determination unit 204 and the demand autonomous driving data response construction transmission unit 205 are removed, and the NW failure information notification unit 801, the backup NW transmission autonomous driving data determination unit 802, and the backup NW transmission autonomous driving data construction unit 803 are added.
The NW failure information notification unit 801 notifies the autonomous driving ECU 1 of failure information on another ECU, which is detected by the NW failure detection unit 103, through the high speed NW interface 200 or the low speed NW interface 201.
The backup NW transmission autonomous driving data determination unit 802 determines contents of the autonomous driving data which is transmitted from the data ECU 2 to the autonomous driving ECU 1 through the backup use network 20 rather than the main use network 10, at the time of the main use network failure occurrence.
The backup NW transmission autonomous driving data construction unit 803 performs a construction processing of the contents of the autonomous driving data which is determined by the backup NW transmission autonomous driving data determination unit 802.
The present processing sequence is started in a case in which the NW failure detection unit 103 or the NW failure detection unit 202 detects the network failure (S400 and S402).
In step S401 and step S403, the NW failure information notification unit 800 or the NW failure information notification unit 801 notifies the autonomous driving ECU 1 or the data ECU 2 of the network failure information through the high speed NW interface 100 or the low speed NW interface 101, so as to perform information sharing of the network failure between ECUs in a system.
In addition, a transition to step S404 is performed, and the backup NW transmission autonomous driving data determination unit 802 of the data ECU 2 determines the contents of the autonomous driving data which is transmitted from the data ECU 2 to the autonomous driving ECU 1 through the backup use network 20 rather than the main use network 10, at the time of the main use network failure occurrence.
Then, in step S405, the backup NW transmission autonomous driving data construction unit 803 performs the construction processing of the contents of the autonomous driving data which is determined by the backup NW transmission autonomous driving data determination unit 802.
In addition, a transition to step S406 is performed, and the communication control unit 203 transmits the backup NW transmission autonomous driving data to the autonomous driving ECU 1 through the low speed NW interface 201.
Then, a transition to step S407 is performed, and the communication control unit 102 of the autonomous driving ECU 1 receives the autonomous driving data from the data ECU 2.
It is possible to reduce the amount of information on the autonomous driving related data to be transmitted and received between the ECUs at the time of the network failure occurrence, by the operation described above. Therefore, it is possible to configure the backup use network 20 as a narrow bandwidth in comparison with the main use network 10, or to share a network between a plurality of ECUs like a bus type topology such as the CAN. Thus, in comparison with the CAN, it is possible to construct a network with low cost and high reliability in comparison with a case in which a communication method with high cost such as Ethernet is applied to the backup use network 20.
In addition, it is possible to apply the present example in the case of the network failure occurrence to the case of another event occurrence identical to Example 1. It is possible to reduce the amount of information on the autonomous driving data which is transmitted from the data ECU 2 to the autonomous driving ECU 1, by applying the present example to the case of the other event occurrence. Therefore, it is possible to avoid a situation in which the autonomous driving system is not functioned completely by a reason such as stopping the continuous processing by the autonomous driving ECU 1, at the time of the event occurrence.
Example 3 shows a method of changing data transmitted and received between ECUs, by determining whether it is possible to perform the autonomous driving or not by the autonomous driving ECU 1 or the data ECU 2, at the time of the network failure or the occurrence of the other event shown in Example 1.
Specifically, a method is shown, in which by a determination processing whether it is possible to perform the autonomous driving or not, in a case in which it is possible to perform the autonomous driving, the transmission and reception of the autonomous driving data are performed between the ECUs by using the main use network 10 or the backup use network 20, and in a case in which it is determined that it is impossible to perform the autonomous driving, transmission and reception of the autonomous driving fallback data which is necessary to fall back the autonomous driving function and perform a partial function are performed between the ECUs by using the main use network 10 or the backup use network 20.
The autonomous driving performance possibility or impossibility determination unit 1000 performs a determination processing of whether it is possible to perform the autonomous driving from the information from the demand information determination unit 104, the autonomous driving situation determination unit 105, and the vehicle control plan unit 106, at the time of the network failure or the other event shown in Example 1 occurs. In addition, determination result information thereof is transmitted from the high speed NW interface 100 or the low speed NW interface 101 to the data ECU 2, through the communication control unit 102.
In addition, the determination result information by the autonomous driving performance possibility or impossibility determination unit 1000 may be transmitted from the autonomous driving ECU 1 to the data ECU 2 also in a case in which the network failure or the other event shown in Example 1 does not occur as well as a timing other than the time of the network failure or the other event shown in Example 1 occurs.
A network used at this time uses the high speed NW interface 100 or the low speed NW interface 101. For example, the low speed NW interface 101 may be used, in a case in which the network failure or the other event shown in Example 1 does not occur, the high speed NW interface 100 may be used, and in a case in which the network failure or the other event shown in Example 1 occurs, the low speed NW interface 101 may be used.
The autonomous driving performance possibility or impossibility information reception determination unit 1001 determines whether or not it is possible to receive the determination result information which is transmitted from the autonomous driving ECU 1 and indicates whether it is possible to perform the autonomous driving or not, at the time of the event occurrence.
The autonomous driving data construction transmission unit 1002 constructs the autonomous driving data according to the determination result information which indicates whether it is possible to perform the autonomous driving or not, and transmits the autonomous driving data to the autonomous driving ECU 1 by the high speed NW interface 200 or the low speed NW interface 201 through the communication control unit 203. The autonomous driving data mentioned here indicates the external recognition object data in the vicinity of the host vehicle, the position information with high precision, or the map information with high precision, which is necessary for the autonomous driving, in a case in which it is possible to perform the autonomous driving. In a case in which it is impossible to perform the autonomous driving, the autonomous driving data indicates information which is necessary to fall back the autonomous driving function and perform the partial autonomous driving function. The partial autonomous driving function indicates a function of any of an Automatic Emergency Breaking (AEB), a Lane Departure Warning (LDW), a Forward Collision Warning (FCW), and an Adaptive Cruise Control (ACC), or a combination of several functions.
The configuration of
The autonomous driving performance possibility or impossibility determination unit 1100 determines whether it is possible to perform the autonomous driving, at the time of the network failure occurrence or the other event shown in Example 1 occurs.
The autonomous driving data construction transmission unit 1101 constructs the autonomous driving data on the basis of a determination processing result by the autonomous driving performance possibility or impossibility determination unit 1100, and transmits the autonomous driving data to the autonomous driving ECU 1 by the high speed NW interface 200 or the low speed NW interface 201 through the communication control unit 203. The autonomous driving data is identical to that illustrated in
Although the processing flows of
On the other hand, in a case of
It is possible to reduce the amount of information on the autonomous driving related data to be transmitted and received between the ECUs at the time of the network failure occurrence or at the time of the other event occurs, by the operation described above. Therefore, it is possible to configure the backup use network 20 so as to have a narrower bandwidth than that of the main use network 10, or to share a network between a plurality of ECUs like a bus type topology such as the CAN. Thus, in comparison with the CAN, it is possible to construct a network with low cost and high reliability in comparison with a case in which a communication method with high cost such as Ethernet is applied to the backup use network 20.
In addition, in the examples 1 to 3, the method of reducing the amount of information on the autonomous driving data which is transmitted from the data ECU 2 to the autonomous driving ECU 1 at the time of the network failure or the other event occurs is described. However, at the time of the network failure or the other event occurrence, data may not be transmitted from the data ECU 2 to the autonomous driving ECU 1 on the basis of an instruction of the autonomous driving ECU 1.
Furthermore, the data ECU 2 may not transmit data to the autonomous driving ECU 1 spontaneously. Therefore, it is possible to reduce the amount of data which is transmitted from the data ECU 2 to the autonomous driving ECU 1. Thus, it is possible to reduce a bandwidth of the backup use network 20 or the CPU processing load of the autonomous driving ECU 1.
1 autonomous driving ECU, 2 data ECU, 6 network switch, 10 main use network, 20 backup use network, 100 high speed NW interface, 101 low speed NW interface, 102 communication control unit, 103 NW failure detection unit, 104 demand information determination unit, 105 autonomous driving situation determination unit, 106 vehicle control plan unit, 107 demand autonomous driving data construction unit, 108 vehicle control unit, 109 control NW interface, 200 high speed NW interface, 201 low speed NW interface, 202 NW failure detection unit, 203 communication control unit, 204 demand autonomous driving data reception determination unit, 205 demand autonomous driving data response construction transmission unit, S100 NW failure detection processing, S101 demand information determination processing, S102 autonomous driving situation determination processing, S103 vehicle control plan determination processing, S104 demand autonomous driving data request construction transmission processing, S105 demand autonomous driving data request reception determination processing, S106 demand autonomous driving data determination processing, S107 demand autonomous driving data construction processing, S108 demand autonomous driving data response transmission processing, S200 failure occurrence location determination processing, S201 information reduction pattern 1 processing, S202 information reduction pattern 2 processing, S203 information reduction pattern 3 processing, 400 demanded autonomous driving data number, 401 data transmission pattern, 500 host vehicle, 501 another vehicle, 502 range of vehicle object recognized from sensor, 503 range of vehicle object transmitted from data ECU 2 to autonomous driving ECU 1, 504 host vehicle driving speed, 600 host vehicle during autonomous driving, 601 driving plan track, 602 map with high precision loaded to autonomous driving ECU 1, 603 map with high precision scheduled to be newly loaded later, 604 autonomous driving cancel release schedule point, 800 NW failure information notification unit, 801 NW failure information notification unit, 802 backup NW transmission autonomous driving data determination unit, 803 backup NW transmission autonomous driving data construction unit, S400 NW failure detection processing, S401 NW failure information notification processing, S402 NW failure detection processing, S403 NW failure information notification processing, S404 backup NW transmission autonomous driving data determination processing, S405 backup NW transmission autonomous driving data construction processing, S406 backup NW transmission autonomous driving data transmission processing, S407 autonomous driving data reception determination processing, 1000 autonomous driving performance possibility or impossibility determination unit, 1001 autonomous driving performance possibility or impossibility information reception determination unit, 1002 autonomous driving data construction transmission unit, 1100 autonomous driving performance possibility or impossibility determination unit, 1101 autonomous driving data construction transmission unit
| Number | Date | Country | Kind |
|---|---|---|---|
| JP2015-204170 | Oct 2015 | JP | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2016/076225 | 9/7/2016 | WO | 00 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2017/064944 | 4/20/2017 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 8509982 | Montemerlo | Aug 2013 | B2 |
| 9690290 | Prokhorov | Jun 2017 | B2 |
| 9915950 | Hartung | Mar 2018 | B2 |
| 20030018422 | Akiyama | Jan 2003 | A1 |
| 20030076221 | Akiyama | Apr 2003 | A1 |
| 20060173614 | Nomura | Aug 2006 | A1 |
| 20070076593 | Sakurai | Apr 2007 | A1 |
| 20070286225 | Enders et al. | Dec 2007 | A1 |
| 20150158499 | Koravadi | Jun 2015 | A1 |
| 20150256356 | Armbruster et al. | Sep 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 10 2004 008 910 | Sep 2005 | DE |
| 10 2007 013 511 | Sep 2008 | DE |
| 10 2011 117 116 | May 2013 | DE |
| 10 2012 219 176 | Apr 2014 | DE |
| 2003-191804 | Jul 2003 | JP |
| 2014-118072 | Jun 2014 | JP |
| Entry |
|---|
| Liu, “Vision-based long-distance perception and front vehicle location for full autonomous vehicles on highway roads”, 2012, Springer, J. Cent. South Univ., 19, 1454-1465 (Year: 2012). |
| International Search Report of PCT/JP2016/076225 dated Dec. 20, 2016. |
| German Office Action received in corresponding German Application No. 11 2016 004 174.8 dated Jun. 18, 2021. |
| Number | Date | Country | |
|---|---|---|---|
| 20180304828 A1 | Oct 2018 | US |
