JP6189115B2 - Travel control system and travel control device - Google Patents

Description

  The subject matter disclosed in the present specification relates to a system for performing traveling control of a vehicle, an apparatus used therefor, a server, and a program.

  2. Description of the Related Art There is known a system for controlling vehicle travel using information such as road shape (curves, intersections, etc.) and attributes (speed limit, road gradient, etc.). These systems estimate the position of the host vehicle on the road, grasp the shape and attributes of the road on which the host vehicle will run, predict the future behavior of the host vehicle, and control the driving of the vehicle. ing. According to such a method, the surrounding environment of the vehicle can be grasped in more detail than conventional travel control using only short-range information that can be acquired by an on-vehicle sensor such as a radar or a camera. Travel control is possible.

  However, since a wider range of information is handled on the other hand, various unexpected cases occur and the possibility of malfunctions increases. For example, information such as the shape and attributes of the road used for travel control may be old and different from the actual road state. Moreover, the case where the position on the road of the own vehicle is estimated incorrectly is also considered.

  In order to solve this problem, Patent Document 1 manages whether or not a field survey is performed on the attribute data of a road used for travel control in units of map areas constituting a map, and a field survey of attribute data is not performed. When the vehicle is located in the map area, the travel control using the attribute data is not performed (paragraph 0010).

US Patent Application Publication No. 2008/0147305

  In the case of Patent Document 1 described above, it is possible to suppress malfunctions that occur when information on the shape and attributes of the road used for travel control is different from the actual road, but information on the shape and attributes of the road is correct. However, malfunctions that occur are not subject to suppression.

  In order to estimate the position of the host vehicle on the road, for example, the geographical position (latitude and longitude) of the host vehicle is estimated using GNSS (Global Navigation Satellite System), and then the road information on the map data. A method of estimating the traveling road in light of the above is used. However, an error occurs in the position estimation of the host vehicle by GNSS. For example, a GNSS signal received by a vehicle from a satellite may be affected by multipath due to a high-rise building or the like, and an error of several tens of meters may occur. In such a case, it is erroneously determined that the vehicle is traveling on another road, which may cause a malfunction of the traveling control. Even if the geographical position of the vehicle is correctly estimated, if there are multiple roads that are very close to each other, such as when a road runs under the elevated road in parallel with the elevated road, There was a problem that there was a possibility of estimation by mistake.

  Even if the position of the host vehicle on the road can be correctly estimated, there may be a case where the travel control malfunctions because the shape or attribute of the road is special. There are various forms of road shapes and attributes, and it is substantially difficult to realize travel control that covers the shapes and attributes of all roads in the world including future possibilities. For this reason, there is a problem in that a malfunction occurs due to encountering a road having a shape or an attribute that cannot be assumed when the travel control system is mounted on the vehicle.

  Note also that the surrounding environment, such as high-rise buildings, etc., the shape and attributes of the road may change from day to day. Even if the travel control is operating normally at a certain point in time, there is a problem that malfunction may occur due to changes in the surrounding environment, road shape, or attributes.

  Therefore, there is a need for a technique that can suppress a malfunction of travel control that occurs due to the influence of the surrounding environment or the shape and attributes of the road even when information on the shape and attributes of the road can be acquired correctly.

In order to solve the above problems, the present invention is a travel control system that includes a travel control device that is mounted on a vehicle and controls the travel of the vehicle, and a server device that communicates with the travel control device, The travel control device includes a first interface that communicates with the server device via a network, a first processor connected to the first interface, and a first storage device connected to the first processor. The server device includes a second interface connected to the network, a second processor connected to the second interface, and a second storage device connected to the second processor, The second storage device includes at least map information including road network information, points on the map, and the vehicle traveling on the road indicated by the map. Information associated with the travel control to be used, and feature point information including an evaluation value indicating the validity of the association between the point on the map and the travel control, and the travel control device includes at least Information indicating the position of the vehicle is transmitted to the server device, and the server device, based on the feature point information, transmits the feature point information related to a point where a relationship with the vehicle position satisfies a predetermined condition. The travel control device stores the received feature point information in the first storage device, and based on the feature point information stored in the first storage device, the travel control device stores the received feature point information, A point satisfying a predetermined condition is identified, a travel control associated with the identified point is identified based on the feature point information stored in the first storage device, and the identified Point and Based on the evaluation value corresponding to the specified travel control, it is determined whether to execute the specified travel control, it is determined to execute the specified travel control, and a predetermined condition is satisfied. Based on this, when it is determined that the timing for executing the specified travel control has arrived, a control instruction for executing the specified travel control is transmitted, and information acquired from a sensor mounted on the vehicle Based on the above, the actual vehicle operation performed by the driver of the vehicle in a predetermined period determined based on the period during which the identified travel control is performed is identified, the identified travel control, When the result of comparison with the specified actual vehicle operation is transmitted to the server device and it is determined not to execute the specified travel control, a control for executing the specified travel control is performed. An actual vehicle executed by the driver of the vehicle during a predetermined period determined based on a period during which the specified travel control should be executed if the control instruction is transmitted without transmitting the control instruction An operation is identified, and a result of comparison between the identified travel control and the identified actual vehicle operation is transmitted to the server device, and the server device is identified based on the result of the comparison. An evaluation value for associating the determined point with the identified travel control is acquired.

  According to an embodiment of the present invention, it is possible to suppress a malfunction in travel control that occurs due to the influence of the surrounding environment, road shape, attributes, or the like.

It is a functional block diagram which shows an example of a structure of the traveling control system by Example 1 of this invention. It is explanatory drawing of an example of the information stored in the map data group, the feature point data group, and the road event data group which the vehicle travel control assistance server of Example 1 of this invention hold | maintains. It is explanatory drawing of an example of the data structure of the feature point data group which the vehicle travel control assistance server of Example 1 of this invention hold | maintains. It is explanatory drawing of an example of the data structure of the road event data group which the vehicle travel control assistance server of Example 1 of this invention hold | maintains. It is explanatory drawing of an example of the data structure of the traveling control classification data group which the vehicle traveling control assistance server of Example 1 of this invention hold | maintains. It is explanatory drawing of an example of the data structure of the data group according to vehicle which the vehicle travel control assistance server of Example 1 of this invention hold | maintains. It is explanatory drawing of an example of the information stored in the surrounding map data group, the related feature point data group, the related road event data group, and the surrounding object data group which the driving | running | working control apparatus of Example 1 of this invention hold | maintains. It is explanatory drawing of an example of the data structure of the related feature point data group which the traveling control apparatus of Example 1 of this invention hold | maintains. The flow of the related periphery information acquisition process performed in the vehicle travel control system of Example 1 of this invention is shown. It is explanatory drawing of an example of a format of the vehicle information message which the traveling control apparatus of Example 1 of this invention transmits. It is explanatory drawing of an example of a format of the related periphery information message which the vehicle travel control assistance server of Example 1 of this invention transmits. The flow of the traveling control process which the traveling control apparatus of Example 1 of this invention performs is shown. The flow of the traveling control evaluation management process performed in the vehicle traveling control system of Example 1 of this invention is shown. It is explanatory drawing of an example of a format of the traveling control evaluation result message which the traveling control apparatus of Example 1 of this invention transmits. It is explanatory drawing of an example of the information regarding the traveling control which the traveling control information output part of the input / output device of Example 1 of this invention displays. 5 shows a traveling control information display processing flow executed by the input / output device of Embodiment 1 of the present invention to display traveling control information. It is explanatory drawing of an example of a format of the traveling control information message which the traveling control apparatus of Example 1 of this invention transmits. The processing flow for making the setting regarding the traveling control of the traveling control device via the input / output device according to the first embodiment of the present invention is shown. It is a block diagram which shows an example of the hardware constitutions of the traveling control system by Example 1 of this invention.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a functional block diagram illustrating an example of a configuration of a travel control system according to the first embodiment of the present invention.

  As shown in FIG. 1, a travel control system 1 according to the present embodiment is a travel control system that supports travel control of one or more vehicles 2, for example, and is wireless from one or more vehicles 2 and road infrastructure. One or more roadside devices 4 for providing information to the vehicle 2 by communication, a travel control support server 10 for providing information for supporting travel control to the one or more vehicles 2, and the network 3. Consists of including.

  The vehicle 2 includes a travel control device 20, a wireless communication device 30, a vehicle positioning device 40, an input / output device 50, a peripheral object detection device 60, a vehicle control device group 70, and a sensor group 80. Have.

  The travel control device 20 is, for example, an ECU (Electronic Control Unit) for realizing an advanced driver assistance system (ADAS: Advanced Driver Assistance Systems), and includes a processing unit 200, a storage unit 210, a communication unit 220, and the like. Have

  The processing unit 200 includes, for example, a CPU (Central Processing Unit) and a RAM (Random Access Memory), and implements the function of the traveling control device 20 by executing a predetermined operation program. (See FIG. 19). In addition, the processing unit 200 includes, as functional blocks, a related peripheral information acquisition unit 201 that acquires peripheral information of the vehicle 2 related to travel control, a host vehicle position estimation unit 202 that estimates the position of the vehicle 2, and a travel of the vehicle 2 The travel control content determined by the travel control determination unit 204, the travel control determination unit 204 that determines the travel control content instructed to part or all of the vehicle control device group 70, and the travel control determination unit 204. The traveling control evaluation unit 205 to evaluate, the traveling control content determined by the traveling control determination unit 204 to a part or all of the vehicle control device group 70, the traveling control instruction unit 206, the input / output device 50, etc. A travel control information providing unit 207 that provides information related to the travel control information setting unit 208 that processes a setting change request related to travel control from the input / output device 50 and the like, and Vehicle information acquisition unit 209 for acquiring information on the vehicle from the capacitors group 80, etc., and the like.

  The storage unit 210 includes, for example, a storage device such as an HDD (Hard Disk Drive), a flash memory, and a ROM (Read Only Memory), and a program executed by the processing unit 200 and data necessary for realizing the system. Groups are stored (see FIG. 19). In this embodiment, in particular, the surrounding map data group 211, the related feature point data group 212, the related road event data group 213, the surrounding object data group 214, the travel control parameter data group 215, and the like are stored in the storage unit 210. .

  The communication unit 220 includes, for example, a network card conforming to a communication standard such as Ethernet (registered trademark) or CAN (Controller Area Network), and data based on other devices mounted on the vehicle 2 and various protocols. Send and receive. The connection form between the communication unit 220 and another device mounted on the vehicle 2 is not limited to a wired connection such as Ethernet, but is not limited to Bluetooth (registered trademark) or a wireless LAN (Local Area Network). It may be a short-range wireless connection.

  The wireless communication device 30 includes, for example, a network card that conforms to a long-range wireless communication standard such as LTE (Long Term Evolution) or a short-range wireless communication standard such as a wireless LAN or DSRC (Dedicated Short Range Communications), For example, the vehicle traveling control support server 10, one or a plurality of roadside devices 4, a wireless communication device 30 mounted on one or a plurality of other vehicles, a communication terminal owned by one or a plurality of persons ( (Not shown) and the like.

  The wireless communication device 30 performs data communication with the vehicle travel control support server 10 via the network 3. The wireless communication device 30 is preferably connected to the network 3 using long-range wireless communication, and performs transmission / reception of data generated based on, for example, various IP (Internet Protocol) protocols. The wireless communication device 30 is not limited to long-distance wireless communication, and may be directly connected to the network 3 using short-range wireless communication, or connected to the network 3 via another communication device such as the roadside device 4. You may do it.

  On the other hand, the wireless communication device 30 is preferably connected to the network 3 using short-range wireless communication between the roadside device 4, a wireless communication device mounted on another vehicle 2, or a communication terminal held by a person or the like. Direct data communication without going through. This assumes, for example, a road-to-vehicle / vehicle-to-vehicle communication system. However, the wireless communication device 30 is not limited to short-range wireless communication, and may perform data communication with various communication devices via the network 3 using long-range wireless communication. The wireless communication device 30 may be configured to comply with a combination of two or more of any long-range wireless communication standard and short-range wireless communication standard.

  The own vehicle position measuring device 40 is a device that measures the geographical position of the vehicle 2 and provides the information, and corresponds to, for example, a GNSS receiving device. The own vehicle positioning device 40 may be configured to simply provide positioning results based on radio waves received from GNSS satellites, or acquired from the sensor group 80 such as the moving speed and traveling azimuth of the vehicle 2. It may be configured to perform position interpolation and error correction by utilizing possible information.

  The own vehicle position measurement device 40 may be a device other than the GNSS reception device as long as it is a device that measures the geographical position of the vehicle 2. For example, the own vehicle position measuring device 40 has information for identifying the road on which the vehicle 2 is traveling from the roadside machine 4 and information indicating the position of the vehicle 2 on the road (for example, information indicating the distance from the starting point of the road). May be obtained and the geographical position of the vehicle 2 may be determined based thereon. Further, the information indicating the position of the vehicle 2 acquired by the own vehicle position measurement device 40 is typically a coordinate value such as latitude and longitude described later, but the positional relationship between the feature point described later and the vehicle 2. Information other than the above may be used as long as the information can be used to identify the information. For example, the information indicating the position of the vehicle 2 may be information indicating a road on which the vehicle 2 is traveling and a position on the road.

  The input / output device 50 is, for example, an in-vehicle display or a smartphone, and is configured to be able to present information to a person who is on the vehicle 2 or to input information. The input / output device 50 in this embodiment includes a travel control information output unit 51 for outputting information related to travel control to the driver or passenger of the vehicle 2, and travel to the driver or passenger of the vehicle 2. A travel control information input unit 52 for receiving information related to control is included.

  The peripheral object detection device 60 includes, for example, a radar or a camera, detects an object around the vehicle 2 based on sensor data acquired from the sensor group 80 mounted on the vehicle 2, and provides information on the detected object. It is configured as follows.

  The vehicle control device group 70 is a device group for controlling various components of the vehicle 2, for example, an ECU for controlling an engine, a brake, an automatic transmission, and the like.

  The sensor group 80 is a group of devices that detect the state of various parts of the vehicle 2 (for example, travel speed, steering angle, accelerator operation amount, brake operation amount, etc.), for example, on an in-vehicle network such as CAN. The detected state quantity is output periodically. A device connected to the in-vehicle network including the travel control device 20 is configured to be able to acquire state quantities of various components.

  The network 3 is a communication network configured by an arbitrary combination of a circuit switching network or a packet switching network using wireless and / or wired media, and the wireless communication device 30 mounted on the vehicle travel control support server 10 and the vehicle 2. Are configured to be able to transmit / receive data to / from each other. The travel control device 20 can communicate with the vehicle travel control support server 10 via the network 3 via the wireless communication device 30.

  The roadside machine 4 is, for example, a device installed on the side or upper side of a road, and is configured to be able to wirelessly communicate with the wireless communication devices 30 of one or more vehicles 2. The roadside machine 4 is connected to, for example, a road IT infrastructure system managed by a road operator or a contractor thereof. For example, the roadside machine 4 is configured to be communicable with a center system such as a road control center or a road traffic information center, and the center system is connected to one or a plurality of vehicles 2 traveling on an installed road. It is possible to distribute the information requested from

  The vehicle travel control support server 10 is, for example, a system configured by one server or a plurality of servers for realizing an advanced driving support system (ADAS) of the vehicle 2, and includes a processing unit 100 and a storage unit 110. And a communication unit 120.

  The processing unit 100 includes, for example, a CPU, a RAM, and the like, and performs a process for realizing the functions of the vehicle travel control support server 10 by executing a predetermined operation program (see FIG. 19). In addition, the processing unit 100 includes, as functional blocks, a vehicle information receiving unit 101 that receives information about the vehicle from one or more vehicles 2, and a travel route of the vehicle based on the vehicle information received from the vehicle information receiving unit 101. The vehicle traveling route estimation unit 102 to be estimated, the related peripheral information extraction unit 103 that extracts the peripheral information related to the travel control of the vehicle 2, and the related peripheral information extracted by the related peripheral information extraction unit 103 are transmitted to the vehicle 2. Peripheral information transmitting unit 104, a traveling control evaluation result receiving unit 105 that receives an evaluation result regarding traveling control of the vehicle 2 from one or more vehicles 2, and an evaluation regarding traveling control of the vehicle 2 received by the traveling control evaluation result receiving unit 105. The results are managed by the traveling control evaluation management unit 106 that stores and manages the results in the storage unit 110 according to a predetermined method, and the traveling control evaluation management unit 106. Travel control permission determination unit 107 that determines the running control whether based on the running control evaluation, and the like.

  The storage unit 110 includes, for example, a storage device such as an HDD, a flash memory, and a ROM, and stores a program executed by the processing unit 100 and a data group necessary for realizing the system (see FIG. 19). ). In the present embodiment, in particular, the map data group 111, the feature point data group 112, the road event data group 113, the travel control type data group 114, the vehicle-specific data group 115, and the like are stored in the storage unit 110.

  The communication unit 120 includes, for example, a network card conforming to a wired LAN standard such as Ethernet, and accesses the network 3 to transmit and receive data generated based on, for example, various IP protocols. Do. The connection form of the communication unit 120 to the network 3 is not limited to a wired connection such as Ethernet, and may be a short-distance wireless connection such as a wireless LAN, or a communication system of a mobile phone. A long distance wireless connection may be used.

  The map data group 111 of the vehicle travel control support server 10 is a collection of data relating to a digital road map including information such as the network structure, attributes, and shape of the road. In this specification, the road means a road on which the vehicle can travel, and is not limited to a public road, and may include a private road or a traveling path in a facility such as a parking lot. The map data group 111 may further include facility information along the road in addition to the digital road map data, and may further include a feature point data group 112 and a road event data group 113 described later.

  The feature point data group 112 of the vehicle travel control support server 10 is a set of data entries related to feature points on the travel road used for travel control of the vehicle 2, for example. In this specification, one set composed of one or more different data is called an entry. Further, in this specification, a traveling road of a certain vehicle 2 is a road on which the vehicle 2 is traveling or stopped, and is distinguished in consideration of the traveling direction. That is, even on the same road, a lane (opposite lane) for traveling in the direction opposite to the direction in which the vehicle 2 travels is distinguished as another traveling road. In addition, in this specification, the feature point is the shape, attribute, or state of the road on the traveling road that the traveling control device 20 of the vehicle 2 uses or may use when determining the traveling control content. For example, points such as an intersection, a speed limit change point, a curve start point, a road junction, a road branch point, a railroad crossing, a toll booth, a road slope change point, and the like are included. In addition, since feature points are defined for each traveling road, even if there is a single point on the map data such as an intersection, if there are multiple traveling directions of the road passing through that point, the corresponding points Note that it is managed as multiple feature points.

  The road event data group 113 of the vehicle travel control support server 10 is a set of data entries related to road events that have occurred dynamically in road traffic, for example. In this specification, the road event means a dynamic event that affects the traffic flow on the road, and includes, for example, information such as construction, road closures, broken cars, accidents, or traffic jams.

  FIG. 19 is a block diagram illustrating an example of a hardware configuration of the travel control system according to the first embodiment of the present invention.

  The vehicle travel control support server 10 includes a CPU 1900, a storage device 1910, and an interface 1920 that are connected to each other.

  The interface 1920 is a device for realizing the communication unit 120, and is, for example, a network card conforming to an arbitrary communication standard that can be connected to the network 3, such as a wired LAN or a wireless LAN.

  The storage device 1910 may be any type of storage device such as RAM, HDD, flash memory or ROM, or a combination of two or more thereof. Typically, the storage device 1910 includes a volatile storage device such as a RAM and a non-volatile storage device such as an HDD or a flash memory. The storage device 1910 stores at least a processing program 1911, a map data group 111, a feature point data group 112, a road event data group 113, a travel control type data group 114, and a vehicle-specific data group 115. These programs and data groups may be stored in the HDD, for example, and at least a part of them may be copied to the RAM as necessary.

  The CPU 1900 is a processor that implements the functions of the processing unit 100 by executing the processing program 1911. For example, the vehicle information reception unit 101, the vehicle travel route estimation unit 102, the related peripheral information extraction unit 103, the related peripheral information transmission unit 104, the travel control evaluation result reception unit 105, the travel control evaluation management unit 106, and the travel control availability determination unit 107 The CPU 1900 includes a vehicle information reception program, a vehicle travel route estimation program, a related peripheral information extraction program, a related peripheral information transmission program, a travel control evaluation result reception program, and a travel control evaluation management program, which are included in the processing program 1911, respectively. And a travel control availability determination program (both not shown). In the following description, the processing executed by each unit in the processing unit 100 is actually executed by the CPU 1900 according to the processing program 1911.

  The travel control device 20 includes a CPU 1930, a storage device 1940, and an interface 1950 that are connected to each other.

  The interface 1950 is a device for realizing the communication unit 220, and is, for example, a network card that complies with an arbitrary communication standard capable of transmitting and receiving data to and from other devices mounted on the vehicle 2, such as Ethernet or CAN. .

  The storage device 1940 may be any type of storage device such as RAM, HDD, flash memory or ROM, or a combination of two or more thereof. The storage device 1940 stores at least a processing program 1941, a surrounding map data group 211, a related feature point data group 212, a related road event data group 213, a surrounding object data group 214, and a traveling control parameter data group 215.

  The CPU 1930 is a processor that implements the functions of the processing unit 200 by executing the processing program 1941. For example, the related peripheral information acquisition unit 201, the own vehicle position estimation unit 202, the own vehicle travel route estimation unit 203, the travel control determination unit 204, the travel control evaluation unit 205, the travel control instruction unit 206, the travel control information provision unit 207, the travel The functions of the control information setting unit 208 and the vehicle information acquisition unit 209 are as follows. The CPU 1930 includes a related peripheral information acquisition program, an own vehicle position estimation program, an own vehicle travel route estimation program, a travel control determination program included in the processing program 1941, respectively. This is realized by executing a travel control evaluation program, a travel control instruction program, a travel control information providing program, a travel control information setting program, and a vehicle information acquisition program (all not shown). In the following description, processing executed by each unit in the processing unit 200 is actually executed by the CPU 1930 according to the processing program 1941.

  FIG. 2 is an explanatory diagram illustrating an example of information stored in the map data group 111, the feature point data group 112, and the road event data group 113 held by the vehicle travel control support server 10 according to the first embodiment of the present invention. Specifically, FIG. 2 shows a part of the road network extracted, and the characteristic points in the road network and the road events occurring are schematically illustrated as an example. In FIG. 2, the solid line excluding the outer frame represents a road. A broken line represents an occurrence range on the road of a road event occurring on the nearby road. Terms (7100 to 7105) surrounded by a solid frame line are descriptions of feature points and road events.

  In the map data group 111, a road is composed of a set of nodes representing road links representing section roads and end points of section roads. Each node has an identifier called a node ID. In FIG. 2, node IDs 7000 to 7040 are shown as examples of nodes. Hereinafter, the value of the node ID is also used as a reference code of the node identified by the node ID. For example, a node identified by the node ID 7000 is also simply referred to as a node 7000.

  On the other hand, a link is expressed by a pair of node IDs, for example. That is, the road link ID of the section road between the node 7000 and the node 7001 is represented by (7000, 7001). In this specification, the road link is expressed by distinguishing the traveling direction, the road link (7000, 7001) is a section road traveling from the node 7000 to the node 7001, and the road link (7001, 7000) is the node 7001 to the node 7000. It is assumed that each of the section traveling roads that travels to is represented. The road link expression method is not limited to this. For example, the road link (7000, 7001) represents a section road including bidirectional directions between the node 7000 and the node 7001, and is combined with data representing the traveling direction. The section road may be expressed as

  Since the data structure of the map data group 111 may be an arbitrary structure including a publicly known one such as that employed in a so-called in-vehicle navigation device, a description thereof will be omitted.

  FIG. 3 is an explanatory diagram showing an example of the data structure of the feature point data group 112 held by the vehicle travel control support server 10 according to the first embodiment of the present invention. Specifically, FIG. 3 represents a part of information on feature points on the road network of FIG.

  The feature point ID 301 is an identifier (ID) for identifying the feature point. In the following description, the value of the feature point ID 301 may be used as a reference code for the feature point identified by the value. For example, the feature point identified by the value “5000” of the feature point ID 301 may be described as the feature point 5000.

  The feature point type 302 represents the type of each feature point. The type of feature point is, for example, a no-signal intersection where the travel road has priority, a no-signal intersection where the travel road has no priority, a signal intersection, a curve start point, or a speed control change point.

  The travel control evaluation value 303 stores an evaluation value related to travel control using each feature point. The evaluation value related to the travel control is expressed by quantifying the preference of the travel control. For example, the success rate of the travel control (described later) is given as an example. The evaluation value is managed for each type of travel control. Specifically, when there is no travel control type related to the feature point, a value corresponding to “not applicable” is stored in the travel control evaluation value 303 of the feature point, and a plurality of travels are performed for one feature point. When the control type is related, an evaluation value for each travel control type is stored in the travel control evaluation value 303 of the feature point.

  A high evaluation value of a certain type of travel control associated with a certain feature point is related to the feature point (for example, in the vehicle 2 whose positional relationship with the feature point satisfies a predetermined condition). It means that it is preferable to carry out the control, in other words, the validity of the association between the feature point and the type of travel control is high. That is, the evaluation value is an index indicating the high validity of the association between the feature point and the travel control type. In this case, a low evaluation value of a certain type of travel control associated with a certain feature point means that the validity of the association between that feature point and that type of travel control is low. Specifically, for example, when the relevance of travel control to the feature point was inappropriate from the beginning due to improperness, or temporarily due to an event such as road construction or traffic jam It may be less relevant.

  In the present embodiment, the success rate of travel control is given as an example of an evaluation value, and information indicating whether or not travel control is determined based on the success rate (executable control 304 described later) is an evaluation value for convenience. Although it is treated as another index, it can be said that the information indicating whether or not the travel control can be performed is also a kind of index indicating the high validity of the association between the feature point and the travel control type. Also good. Alternatively, an index other than the above indicating the validity of the association between the feature point and the travel control type may be used as the evaluation value.

  The feasible control 304 stores a list of travel control types that can be implemented in relation to each feature point. When there is no travel control type that can be implemented at each feature point, a value corresponding to “not applicable” is stored. The determination of whether or not each type of travel control can be performed will be described later (see FIGS. 12 and 13).

  The traveling road link 305 represents the link ID of the section traveling road where each feature point is located.

  The travel road link position 306 indicates the distance along the road from the position of the start node of the section travel road represented by the travel road link to each feature point. For example, the feature point 5000 exists at a position 200 m ahead (separated) from the position of the node 7000 that is the starting point node of the section traveling road represented by the traveling road link (7000, 7001).

  The related road event 307 represents a road event related to each feature point. In addition to the feature points that exist fixedly due to the shape of the road, such as intersections and curve start points, the feature points also dynamically occur due to road events. For example, the lane decrease of the feature point 5201 occurs due to one lane being blocked by the work 7104. The related road event 307 stores the ID of the road event that caused the characteristic point to dynamically occur (in the above example, the ID “7104” of the work 7104). If the road event is resolved, the feature point data entry is also deleted from the feature point data group 112. In the case of feature points that exist in a fixed manner, nothing is stored in the related road event 307.

  The related information 308 stores arbitrary unique information possessed by the feature point. For example, an R value representing the curvature of the curve is stored at the curve start point of the feature point 5020 in FIG.

  FIG. 4 is an explanatory diagram showing an example of the data structure of the road event data group 113 held by the vehicle travel control support server 10 according to the first embodiment of the present invention. Specifically, FIG. 4 represents a part of information regarding road events on the road network of FIG.

  The road event ID 311 is an identifier for identifying a road event. In the following description, the value of the road event ID 311 may be used as a reference code for the road event identified by the value. For example, a road event identified by the value “7104” of the road event ID 311 may be described as a road event 7104.

  The road event type 312 represents the type of each road event. The types of road events are, for example, road construction, traffic jams, accidents, closed roads, and the like. For example, in FIG. 2, a character string “construction” is displayed as the road event 7104, which is the value of the road event type 312 of the road event 7104.

  The road event section 313 is a section traveling road where each road event occurs, and is represented by a list of combinations of the traveling road link ID and the corresponding range in the traveling road link. For example, the road event section of the road event 7106 in FIG. 4 has a range of 300 m from the start point (node 7012) of the travel road link (7012, 7003) (equivalent to the distance from the node 7012 to the node 7003), A range of 100 m from the start point (node 7003) of the road link (7003, 7014) is shown.

  The expiration date 314 is the expiration date of information regarding each road event. For the construction of the road event 7104, for example, it has been found that the construction will be continued until 21:00 on March 31, 2013 from information such as a road construction plan. Therefore, the construction end time is set as the expiration date 314 Yes. On the other hand, since the traffic events 7105 and 7106 are temporarily occurring, it is unclear how long it will continue. Therefore, for example, the time after a certain period has elapsed since the last traffic jam information was acquired may be set as the expiration date 314 of the road event 7105 or the like. The data entry related to the road event for which the expiration date has passed is deleted from the road event data group 113. Note that these road event information may be acquired from a road traffic information center (not shown) or the like via the network 3 or based on information collected from one or more vehicles 2. May guess.

  FIG. 5 is an explanatory diagram showing an example of the data structure of the travel control type data group 114 held by the vehicle travel control support server 10 according to the first embodiment of the present invention.

  The travel control type 321 represents the type of one or more travel control methods managed by the vehicle travel control system 1. In the example of FIG. 5, traveling control A, traveling control B, traveling control C, and the like are stored as the traveling control type 321. These correspond to those stored in the travel control evaluation value 303 and the feasible control 304 in FIG. The specific content of the travel control type may be anything, but typical examples include "activate the brake to reduce the travel speed to the specified value", " For example, “operate to increase the traveling speed to a specified value” or “set the rudder angle to a specified value”.

  The related feature point 322 represents a list of types of related feature points used when each travel control type determines the travel control content.

  The service availability 323 indicates whether each travel control type is a support target of the vehicle travel control system 1. If the service availability 323 regarding a certain travel control type is “permitted”, the vehicle travel control support server 10 supports the execution of the travel control regarding the travel control type in the vehicle 2. The travel control related to the travel control type is not performed.

  The service stop road event type 324 stores a road event type that suppresses execution of travel control related to each travel control type. For example, “traffic jam” is set in the service stop road event type 324 corresponding to the travel control B. In this case, it means that the execution of the travel control B is suppressed (that is, the travel control B is not performed) in the travel road section where the traffic congestion is occurring.

  FIG. 6 is an explanatory diagram showing an example of the data structure of the vehicle-specific data group 115 held by the vehicle travel control support server 10 according to the first embodiment of the present invention.

  The vehicle ID 351 is an ID uniquely assigned to each vehicle 2 and is an ID for identifying each vehicle 2. The corresponding travel control 352 is a list of travel control types that each vehicle 2 corresponds to (that is, travel control types that have a function that each vehicle 2 performs).

  The vehicle information 353 is information related to each vehicle 2 and includes, for example, position information 361, travel information 362, travel road link information 363, destination information 364, route information 365, and the like. The position information 361 is the latitude and longitude of the point where each vehicle 2 is located. The travel information 362 is a data group relating to travel of each vehicle 2 such as speed and travel azimuth. The traveling road link information 363 is information regarding the traveling road link estimated that each vehicle 2 is located. The destination information 364 is information related to the destination set by each vehicle 2. The route information 365 is information related to the travel route estimated for each vehicle 2 to travel.

  Note that the vehicle information 353 may not include all of the above items. For example, when the destination of a certain vehicle 2 is not specified, and therefore the travel route to the destination is not estimated, the destination information 364 and the route information 365 regarding the vehicle 2 may be empty.

  The vehicle-specific travel control information 354 is information unique to each vehicle regarding travel control, and includes a history regarding travel control executed by each vehicle 2 in the past and a setting value regarding the travel control. The vehicle-specific travel control information 354 includes, for example, a feature point ID 371, a control type 372, a history 373, a forced OFF flag 374, and the like, and constitutes one data entry for each combination of the feature point ID 371 and the control type 372. .

  The feature point ID 371 is an identifier of a feature point that each vehicle 2 has executed traveling control on. The control type 372 is a type of travel control performed at the feature point identified by the feature point ID 371. The history 373 includes the number of successes and the number of executions of the travel control identified by the type 372 performed at the feature point identified by the feature point ID 371, and may further include the success rate calculated from the number of times. .

  The forced OFF flag 374 is a flag that suppresses the execution of the travel control identified by the type 372 at the feature point identified by the feature point ID 371. When the forced OFF flag 374 is Yes, the travel control is not performed. A method for setting the forced OFF flag 374 will be described later.

  Next, a data group held by the travel control device 20 will be described.

  The peripheral map data group 211 of the travel control device 20 is a collection of data related to information on surrounding roads related to the travel control of the vehicle 2, and the data structure is the same as the map data group 111 of the vehicle travel control support server 10. . The peripheral map data group 211 may further include any one or more of a related feature point data group 212 and a related road event data group 213 described later.

  The related feature point data group 212 of the travel control device 20 is a data entry related to a feature point related to the travel control type to which the vehicle 2 is on a travel road on which the vehicle 2 may travel from now on. It is a set.

  The related road event data group 213 of the travel control device 20 is a set of data entries relating to road events occurring on the travel road where the vehicle 2 may travel from now on.

  In the peripheral object data group 214 of the travel control device 20, information on peripheral objects detected by the peripheral object detection device 60 of the vehicle 2 and wireless communication from one or more other vehicles 2 via the wireless communication device 30 are acquired. The information of the other vehicle 2 (geographic position of the other vehicle 2, travel speed, traveling direction, vehicle sensor information, etc.) is stored.

  FIG. 7 shows information stored in the peripheral map data group 211, the related feature point data group 212, the related road event data group 213, and the peripheral object data group 214 held by the travel control apparatus 20 according to the first embodiment of the present invention. It is explanatory drawing of an example.

  Specifically, FIG. 7 shows a traveling control device 20 of a certain vehicle 2 in relation to the same area as the geographical area shown in FIG. 2 in order to contrast with the information stored in the storage unit 110 by the vehicle traveling control support server 10. FIG. 6 schematically illustrates information held in the storage unit 210 as an example.

  In FIG. 7, a symbol denoted by reference numeral 7500 indicates the host vehicle 2 traveling in the upward direction on the map (that is, the vehicle 2 holding the map data group 211 and the like illustrated in FIG. 7). A thick line to which reference numeral 7501 is attached indicates an estimated travel route of the host vehicle 2. A plurality of symbols to which reference numeral 7510 is attached indicates other vehicles 2 around the own vehicle 2 (traveling in the direction of the apex of a triangle in contact with the road). A character string to which reference numeral 7520 is attached indicates signal information of signaled intersection 7002.

  Whereas the map data group 111 stores all the travel road information in the service provision range of the vehicle travel control system 1, the surrounding map data group 211 is preferably estimated that the host vehicle 2 will travel from now on. Basically, only road information related to the estimated travel route is included.

  The estimated travel route is estimated from, for example, route information that can be acquired from a navigation system (not shown). When route information or the like by the navigation system cannot be used, the travel route may be estimated based on the assumption that the current travel road travels along the road. The road related to the estimated travel route may be, for example, a road on the estimated travel route and a road intersecting with the road, or all roads within a certain distance from the estimated travel route, or the host vehicle It may be all roads that can be reached from the position 2 with a certain traveling distance, or any combination thereof. By storing only road information related to the estimated travel route, it is possible to prevent the capacity of the storage unit 210 from being consumed by information unnecessary for travel control.

  FIG. 8 is an explanatory diagram showing an example of the data structure of the related feature point data group 212 held by the travel control device 20 according to the first embodiment of the present invention. Specifically, FIG. 8 represents information of the related feature point data group 212 in the situation shown in FIG.

  Feature point ID 401, feature point type 402, travel road link ID 405, travel road link position 406, and related information 407 are feature point ID 301, feature point type 302, travel road link 305, travel road in feature point data group 112, respectively. It corresponds to the position 306 on the link and the related information 308.

  The travel control enable / disable 403 indicates whether the travel control may be performed on each feature point in each travel control type supported by the vehicle 2. For example, it is assumed that the traveling control types that the host vehicle 2 supports (that is, can be implemented) are the traveling controls A and B. On the other hand, travel control A, B, and C can be performed at a feature point 5010 whose type is “signal intersection” (see FIG. 3). In this case, the host vehicle 2 may implement travel control A and B at the feature point 5010. Therefore, in the data entry of the feature point 5010, the travel control availability information 403 indicates the travel control availability information of the travel controls A and B. In this example, both the travel controls A and B are set to be executable.

  The invalid travel control 404 represents individual settings related to travel control for each feature point in the host vehicle 2. For example, in the data entry of the feature point 5010, the traveling control B is set to be invalid. For this reason, although it is evaluated that the travel control B can be performed in the travel control enable / disable 403, the travel control B for the feature point ID 5010 is not performed in the host vehicle 2.

  The data structure of the related road event data group 213 is the same as in FIG. However, the road event data group 113 of the vehicle travel control support server 10 may include all road event information in the service provision range of the vehicle travel control system 1, whereas the related road event data of the travel control device 20 The group 213 basically includes only road event information occurring on the road related to the estimated travel route.

  The peripheral object data group 214 is a set of data entries related to each object detected in the vicinity of the host vehicle 2. Each data entry includes, for example, the type of each object (vehicle, person, etc.), the position of each object, the speed at which each object moves, the direction and acceleration, and various information according to each object type.

  The travel control parameter data group 215 of the travel control device 20 is a set of various parameter data related to travel control. For example, the travel control parameter data group 215 includes a flag indicating whether the travel control function of the travel control device 20 is valid, a vehicle ID of the host vehicle 2, a flag indicating a travel control function learning mode (described later), and travel A data group related to the host vehicle 2 used for the control is included.

  Next, the operation of the vehicle travel control system 1 will be described.

  The travel control device 20 in the vehicle travel control system 1 determines, as main processes, related peripheral information acquisition processing for acquiring information necessary for travel control periodically or according to necessity, and the content of the travel control to control the vehicle. The travel control process instructing the device group 70 is executed. Each process will be described in turn.

  FIG. 9 shows a flow 500 of related peripheral information acquisition processing executed in the vehicle travel control system 1 according to the first embodiment of the present invention.

  The related peripheral information acquisition unit 201 of the travel control device 20 first confirms whether the travel control function of the vehicle 2 is effective after waiting for a predetermined time (step (S) 501) (step 502). The waiting for a predetermined time here means waiting for a time until a trigger for acquiring related peripheral information is activated. The trigger for acquiring related peripheral information may be a timer so that it is executed at regular intervals, or when the vehicle 2 deviates from the assumed driving route, depending on the necessity of updating related peripheral information It can be on demand.

  Whether or not the traveling control function is valid can be realized, for example, by storing a flag indicating validity / invalidity of the traveling control function in the traveling control parameter data group 215 and confirming it. The value of this flag can be changed by the driver through the input / output device 50 of the vehicle 2, for example. For example, it may be set directly such that the driver inputs ON / OFF of the travel control function, or the driver selects a driving mode such as the eco mode, and a specific mode is selected. In this case, the traveling control function may be set to ON.

  If the travel control function is invalid in step 502, the process returns to step 501. On the other hand, if the travel control function is valid in step 502, the process proceeds to step 503.

  In step 503, the vehicle information acquisition unit 209 performs processing for acquiring own vehicle information necessary for inquiring the vehicle driving control support server 10 for related peripheral information. The host vehicle information here is a vehicle ID used by the vehicle travel control support server 10 to identify the host vehicle 2, geographical position information (latitude, longitude, etc.) of the host vehicle 2 and travel information (speed, progress). Azimuth, etc.), information on the destination point of the host vehicle 2, and route information to the destination. The vehicle ID is stored in the travel control parameter data group 215, for example. The geographical position information of the own vehicle 2 is acquired from the own vehicle position positioning device 40, for example. The travel information of the host vehicle 2 is acquired from the sensor group 80, for example. The information on the destination point of the host vehicle 2 and the route information to the destination are acquired from a route search device (not shown) such as a navigation device, for example.

  Next, the traveling control device 20 generates a vehicle information message 511 using the own vehicle information acquired in step 503, and transmits the generated message to the vehicle traveling control support server 10 via the network 3 (step 504). .

  FIG. 10 is an explanatory diagram showing an example of a format 550 of the vehicle information message 511 transmitted by the traveling control device 20 according to the first embodiment of this invention. However, illustration of header information related to the communication protocol is omitted.

  The vehicle information message 511 includes the vehicle ID 551, vehicle position information 552, vehicle travel information 553, destination information 554, route information 555, and the like acquired at step 503. The various information may be transmitted as one message like the vehicle information message format 550 shown in the figure, or may be divided into a plurality of arbitrary messages and transmitted.

  The vehicle position information 552 includes, for example, a latitude 561, a longitude 562, a traveling road link ID 563, and the like that represent the estimated position of the host vehicle 2. The traveling road link ID 563 may not be included. The vehicle travel information 553 includes, for example, a speed 571, a traveling azimuth angle 572, a yaw rate 573, and the like of the host vehicle 2. The destination information 554 is information on a destination set by a navigation system or the like connected to the host vehicle 2. The destination latitude 581, longitude 582, road link ID 583 where the destination is located, destination destination information The position 584 on the road link is included. The route information 555 represents route information to the destination, and includes, for example, a list of road link information through which the route from the current position of the host vehicle 2 to the destination passes. Note that the route information 555 does not have to include all road link information, and may be transmitted only to road link information in a range where related peripheral information needs to be acquired. Further, the destination information 554 and the route information 555 are arbitrary and may not be included in the vehicle information message 511.

  Returning to the description of the related peripheral information acquisition processing flow 500 (FIG. 9). The vehicle information reception unit 101 of the vehicle travel control support server 10 receives the vehicle information message 511 transmitted from the related peripheral information acquisition unit 201 of the travel control device 20 in step 504 via the network 3 (step 521). Although not shown in the figure, when receiving the vehicle information message 511, the vehicle information receiving unit 101 analyzes and extracts various vehicle information data according to the vehicle information message format 550, and if necessary, a vehicle-specific data group. 115.

  Next, the vehicle travel route estimation unit 102 of the vehicle travel control support server 10 uses the received vehicle information message 511 to transmit the vehicle 2 that has transmitted the vehicle information message 511 (in the description of steps 521 to 524, this vehicle for convenience. 2 is described as the host vehicle 2). For example, when the received vehicle information includes the route information 555, the vehicle travel route estimation unit 102 sets the route information 555 as the travel route of the host vehicle 2 in the vehicle-specific data group 115. When the received vehicle information does not include the route information 555 and the destination information 554 is included, the vehicle travel route estimation unit 102, based on the destination information 554 and the position information of the host vehicle 2, The route information is calculated using the same method as the navigation system, and the calculated route information is set in the vehicle-specific data group 115 as the estimated travel route of the host vehicle 2.

  On the other hand, if neither the route information 555 nor the destination information 554 is included in the received vehicle information, the vehicle travel route estimation unit 102 first estimates the travel road where the host vehicle 2 is located. When a value is included in the travel road link ID 563 of the vehicle position information 552 of the received vehicle information, the estimated travel road is set as the travel road link ID 563. If not included, for example, the road on which the host vehicle 2 is located by collating with the map data group 111 using a predetermined map matching algorithm using various data of latitude 561, longitude 562, and vehicle travel information 553, for example. Is estimated. Even when a value is included in the travel road link ID 563, the travel road may be similarly estimated by map matching.

  Next, based on the estimated travel road on which the host vehicle 2 is located, for example, one or more routes that are most likely to be selected are estimated as travel routes, starting from that road. It should be noted that the travel route does not necessarily have to be configured by a single line, and may be configured by a plurality of branched lines.

  The route most likely to be selected is, for example, a route along a road. The route along the road may be a route that can travel without presenting a blinker (a direction indicator (not shown) of the host vehicle 2), or a route along the same road type (such as National Route XXX). However, the route selected by any combination thereof may be used. Alternatively, refer to the past traffic flow statistics of the branch points (intersections) that pass between the starting point and the destination, and the route that passes through each branch point in the same direction as the most vehicles passed. Alternatively, it may be selected as a route most likely to be selected.

  The past traffic flow statistics may be obtained by the vehicle travel control support server 10 holding and statistically analyzing the history of vehicle information transmitted from one or more vehicles 2, or a road operator's center system (illustrated). (Omitted) may be obtained via the network 3. The vehicle travel route estimation unit 102 sets the travel route estimated using the method described above in the vehicle-specific data group 115.

  Returning to the description of the related peripheral information acquisition processing flow 500 (FIG. 9). In the next step 523, the related peripheral information extraction unit 103 performs map data group 111, feature point data group 112, road event data based on the travel route of the host vehicle 2 estimated by the vehicle travel route estimation unit 102 in step 522. With reference to the group 113, the travel control type data group 114, and the vehicle-specific data group 115, the travel control related information around the host vehicle 2 is extracted.

  First, the related peripheral information extraction unit 103 extracts road information related to the estimated travel route from the map data group 111. The road related to the estimated travel route may be, for example, a road on the estimated travel route and a road intersecting with the road, or all roads within a certain distance from the estimated travel route, or the host vehicle It may be all roads that can be reached from the position 2 with a certain traveling distance, or any combination thereof.

  Next, the related peripheral information extraction unit 103 extracts the related feature point data entry group and the related road having the same travel road link ID as the travel road link on the estimated travel route from the feature point data group 112 and the road event data group 113. Extract event data entries. Alternatively, the related peripheral information extraction unit 103 has the same travel road link ID as the travel road link included in the road related to the estimated travel route extracted in the above procedure, instead of the travel road link on the estimated travel route. Various related data entry groups may be extracted.

  Subsequently, the related peripheral information extraction unit 103 refers to the travel control type data group 114, and if there is a travel control type in which the service availability 323 is “impossible”, the feature point data extracted in the above procedure. Of the travel control types included in the entry group, the data entry corresponding to the travel control type “impossible” is deleted. The related peripheral information extraction unit 103 extracts a related vehicle data entry group corresponding to the vehicle ID of the host vehicle 2 from the vehicle data group 115.

  The description of the above step 523 is a process of identifying one or more feature points whose relationship with the position of the host vehicle 2 satisfies a predetermined condition and extracting a travel control type associated with each identified feature point. It is an example. In the above example, at least the estimated feature point on the travel route of the host vehicle 2 is specified as the feature point that satisfies the predetermined relationship with the position of the host vehicle 2. Furthermore, a feature point on a road having a predetermined relationship with the estimated travel route (for example, intersecting with the estimated travel route) is identified as a feature point whose relationship with the position of the host vehicle 2 satisfies a predetermined condition. May be.

  Returning to the description of the related peripheral information acquisition processing flow 500 (FIG. 9). In the next step 524, the related peripheral information transmitting unit 104 generates a related peripheral information message 512 based on the travel control related information around the vehicle extracted by the related peripheral information extraction unit 103, and the travel control device for the host vehicle 2. A message generated via the network 3 is transmitted to the network 20.

  FIG. 11 is an explanatory diagram illustrating an example of a format 600 of the related peripheral information message 512 transmitted by the vehicle travel control support server 10 according to the first embodiment of this invention. However, illustration of header information related to the communication protocol is omitted.

  The related peripheral information message 512 includes the peripheral road information 601, the related feature point information 602, the related road event information 603, the vehicle information 604 regarding the host vehicle 2, and the like acquired in step 523.

  The surrounding road information 601 includes a list of node information 611-1 to 611-m and a list of road link information 612-1 to 612-k included in related road information. The node information 611-1 and the like include, for example, a node ID, geographical position information (latitude, longitude, etc.) of the node, node attribute information (intersection, etc.), and the like. The road link information 612-1 and the like include, for example, node IDs of two nodes serving as end points, road link attribute information (number of lanes, traveling direction of each lane, road type (highway, national road, etc.), etc.) Including.

  The related feature point information 602 includes a list of feature point information 621-1 to 621-j related to the travel control of the host vehicle 2 on the surrounding road information 601. The related feature point information 621-1 and the like include information necessary for the own vehicle 2 to configure the related feature point data 212. For example, the travel control is performed for each feature point ID, feature point type, and travel control type. It includes a propriety / forced OFF flag, a traveling road link ID where the feature point is located, position information on the traveling road link, related information of the feature point, and the like. These basically correspond to the related feature point data entry group acquired in step 523. The forced OFF flag for each travel type can be acquired by referring to the feature point ID and the forced OFF flag 374 for the travel type from the related vehicle-specific data entry group.

  Note that the related feature point information 621-1 or the like is an evaluation value (for example, a feature point data group) instead of (or in addition to) information indicating whether or not the travel control can be performed for each travel control type. 112, a value equivalent to the traveling control evaluation value 303 of 112). In that case, the travel control enable / disable 403 of the related feature point data group 212 is instead of (or in addition to) information indicating whether each type of travel control can be performed (Yes) or not (No). In addition, evaluation values such as success rates of various types of traveling control are included.

  The related road event information 603 includes a list of road event information 631-1 to 631-i on the surrounding road information 601. The road event information 631-1 and the like include, for example, a road event ID, a road event type, one or more traveling road link IDs in which the road event has occurred, an occurrence range on the traveling road link, and the like.

  The vehicle information 604 includes, for example, a travel road link ID 641 where the host vehicle 2 is located, estimated travel route information 642 of the host vehicle 2, and the like. The travel route information 642 is travel route information estimated by the vehicle travel route estimation unit 102 in step 522 of the related peripheral information acquisition flow 500, and is the same as the route information 555 of the vehicle information message format 550.

  Note that the various types of information described above may be transmitted as one message like the vehicle information message format 600 shown in the figure, or may be divided into a plurality of arbitrary messages and transmitted.

  Returning to the description of the related peripheral information acquisition processing flow 500 (FIG. 9). The related peripheral information acquisition unit 201 of the travel control device 20 receives the related peripheral information message 512 transmitted from the related peripheral information transmission unit 104 of the vehicle travel control support server 10 in step 504 via the network 3 (step 505). Although not shown in the figure, when the related peripheral information acquisition unit 201 receives the related peripheral information message 512, it analyzes various data according to the related peripheral information message format 600, and the peripheral road information 601 and the related feature point information. 602, related road event information 603, and vehicle information 604 are extracted. In step 505, the related peripheral information acquisition unit 201 extracts the extracted related road information 601 in the peripheral map data group 211, the extracted related feature point information 602 in the related feature point data group 212, and the extracted related road event information. 603 is stored in the related road event data group 213, and the extracted vehicle information 604 is stored in the travel control parameter data group 215 (step 506).

  Thus, one cycle of the related peripheral information acquisition process flow 500 is completed, the process returns to step 501 again, and the same process is repeatedly executed.

  FIG. 12 shows a flow 800 of a travel control process executed by the travel control device 20 according to the first embodiment of the present invention.

  The travel control determination unit 204 of the travel control device 20 first checks whether the travel control function of the host vehicle 2 is valid (step 801). This is a process equivalent to step 502 in the related peripheral information acquisition process flow 500. If the traveling control function is invalid, the process proceeds to step 820 and waits for a predetermined time. As with step 501 of the related peripheral information acquisition processing flow 500, the standby may be canceled by a timer so as to be executed at regular intervals, or the necessity of the travel control process may be required. Accordingly, the standby may be canceled on demand. If the travel control function is valid in step 801, the process proceeds to step 802.

  In step 802, the host vehicle position estimation unit 202 estimates host vehicle position information. Here, the estimation of the own vehicle position information means that the traveling road on which the own vehicle 2 is located and the position in the traveling road are estimated. For example, the vehicle position information is estimated from geographical position information (latitude, longitude, etc.) of the own vehicle 2 from the own vehicle position measuring device 40, and travel information (vehicle speed, traveling azimuth angle) of the own vehicle 2 from the sensor group 80. , Yaw rate, etc.), the surrounding road information of the vehicle 2 is obtained from the surrounding map data 211, and the most likely traveling road link and the position in the traveling road link are specified according to a predetermined map matching algorithm. This is realized. In this specification, the travel control device 20 performs estimation of the travel road on which the host vehicle 2 is located. For example, another device such as the host vehicle positioning device 40 estimates the travel road, and the information May be acquired by the traveling control device 20. Alternatively, the own vehicle position estimation unit 202 uses the traveling road link ID 641 (stored in the traveling control parameter data group 215) included in the related peripheral information message 600 transmitted from the vehicle traveling control support server 10 as a reference. The traveling road link where the vehicle 2 is located may be specified.

  Subsequently, in step 803, the host vehicle travel route estimation unit 203 estimates the travel route of the host vehicle 2. The estimation of the travel route is realized, for example, by using the travel route information 642 (stored in the travel control parameter data group 215) included in the related peripheral information message 600 transmitted from the vehicle travel control support server 10 as it is. Alternatively, it may be realized in the same manner as the estimation by the vehicle travel route estimation unit 102 of the vehicle travel control support server 10 (step 522 in FIG. 9).

  Next, in step 804, the travel control determination unit 204 uses the feature point information on the travel route estimated in step 803, the travel road link ID 405 of the feature point data entry of the related feature point data group 212, and the travel route. It is obtained by collating the traveling road link IDs. For example, it is assumed that the travel route estimated in step 803 is the route 7501 in FIG. Then, since the travel road link ID of the travel route is (7000, 7001), (7001, 7002), (7002, 7003), (7003, 7004), etc., the related feature point data group in FIG. The feature point 5010 corresponding to the travel road link ID (7001, 7002), the feature point 5020, 5030,... Corresponding to the travel road link ID (7002, 7003), etc. are acquired with reference to the travel road link ID 405 of 212. Can do.

  Next, proceeding to step 805, the travel control determination unit 204 confirms whether or not the conditions for executing the travel control associated with the feature point acquired at step 804 in the host vehicle 2 are satisfied. This confirmation is performed based on whether or not the relationship between the position of the host vehicle 2 and the feature point satisfies a predetermined condition.

  Specifically, first, the travel control determination unit 204 refers to the travel control enable / disable 403 of each data entry of the feature point information, and includes information on the travel control type supported by the travel control function of the host vehicle 2. Check whether it is If the feature point information does not include information related to the travel control type supported by the travel control function of the host vehicle 2, the process proceeds to step 820, waits for a predetermined time, and returns to step 801. On the other hand, when there are one or more corresponding feature point data entries, the travel control determination unit 204 determines whether the various travel control functions of the host vehicle 2 are next at the timing of executing travel control on the feature points. Check.

  For example, if a process related to travel control of a certain travel control type is executed when the distance from the host vehicle 2 to the feature point is within 100 m, the relative distance between the feature point and the host vehicle 2 is calculated. Then, it is confirmed whether it is larger than a predetermined threshold value. If it is determined that all the feature point data entries are not at the timing for executing the traveling control, the process also proceeds to step 820. On the other hand, if it is determined that one or more feature point data entries are at the timing for executing the travel control, the process proceeds to the next step 806.

  For example, in FIGS. 7 and 8, when the position of the host vehicle 2 is on the travel road link (7000, 7001) and the effective travel control function is the travel control A, the feature points 5010, 5020, 5030,. Corresponds to the estimated feature point on the travel route. However, if the condition executed by the traveling control A is, for example, the case where the distance from the own vehicle 2 to each feature point is within 100 m, the condition is not satisfied, and the process proceeds to step 820. On the other hand, when the host vehicle 2 travels on the travel route and reaches the travel road link (7001, 7002), the distance to the feature point ID 5010 is 100 m, so the condition for executing the travel control A is satisfied. Proceed to step 806.

  In step 806, the traveling control determination unit 204 determines the traveling control content using the feature point information (that is, the feature point information that satisfies the condition of step 805) according to a predetermined traveling control algorithm. At this time, the travel control determination unit 204 determines the content of the travel control in an integrated manner including information acquired from the peripheral object data group 214 and the sensor group 80 according to the necessity according to the predetermined travel control algorithm. To do. In the example given above, when the traveling control A is, for example, “automatic regenerative braking”, the relative distance to the signalized intersection (feature point ID5010) that is the target feature point, the signal state and / or signal of the signalized intersection Switching timing (obtained from the related information 407), information on the state and operation of the own vehicle 2 such as the speed, accelerator opening, and brake amount of the own vehicle 2 (obtained from the sensor group 80), traveling in front of the own vehicle 2 The amount and timing of the regenerative brake are determined by comprehensively taking into account information on other vehicles that are running (obtained from the peripheral object data group 214), and the like.

  When a plurality of types of travel control functions are executed for the same feature point, the travel control contents may conflict. In that case, it is necessary to determine the final driving control content by integrating the driving control content determined by each driving control function according to the priority. This may be executed by the travel control device 20, or may be executed by the vehicle control device group 70 by transmitting an instruction regarding each travel control content to the vehicle control device group 70. For the travel control function that is not considered in the final travel control content, it is treated that the travel control for the feature point has not been performed. This prevents the travel control evaluation described later from being performed erroneously.

  Subsequently, the traveling control determination unit 204 confirms whether traveling control using the feature point information can be performed (step 807). Specifically, with reference to the travel control enable / disable 403 in the data entry of the feature point, it is confirmed whether the travel control enable / disable of the corresponding travel control type is “Yes”. When the propriety of the corresponding travel control type is “possible”, the travel control may actually be performed (that is, the association of the corresponding travel control type to the feature point is appropriate). And go to step 809.

  In step 809, the travel control instruction unit 206 transmits a control content instruction to the vehicle control device group 70 related to the travel control content in order to execute the travel control content determined by the travel control determination unit 204, Proceed to step 810. For example, in the example of the automatic regenerative brake, the control content instruction is transmitted to the ECU that controls the regenerative brake according to the timing and amount of the regenerative brake determined by the travel control determination unit 204.

  On the other hand, if it is determined in step 807 that the travel control type of the corresponding travel control type is not “permitted”, the travel control must not be performed (that is, the association of the corresponding travel control type to the feature point is not valid). Therefore, step 809 is not executed and step 808 is executed. By not executing Step 809, the malfunction of the traveling control that occurs due to the influence of the surrounding environment, the shape of the road, the attribute, or the like is suppressed.

  In the case where an evaluation value such as the success rate of each type of traveling control is transmitted from the vehicle traveling control support server 10 and is stored in the related feature point data group 212, based on the evaluated value. The traveling control device 20 may determine whether or not traveling control of the corresponding traveling control type is possible by performing processing similar to steps 853 to 855 (FIG. 13) described later.

  In step 808, the traveling control determination unit 204 confirms whether or not the learning mode of the traveling control device 20 is ON. Parameters relating to the learning mode of the travel control device 20 are stored in the travel control parameter data group 215. If the learning mode is ON, the process proceeds to step 810. Otherwise, the process proceeds to step 820, and after waiting for a predetermined time, the process returns to step 801.

  Note that the processing procedure shown in the present embodiment is merely an example, and for example, various modifications can be considered for the procedure up to step 809 described above. One of the modifications is as follows.

  After executing step 804, the travel control determination unit 204 identifies the travel control type associated with the feature points based on the feature point type 302 acquired in step 804. Next, the traveling control determination unit 204 determines whether the identified traveling control type can be executed based on the evaluation value of the identified traveling control type regarding the feature point acquired in Step 804. This determination is performed in the same manner as in step 807 described above.

  Next, the travel control determination unit 204 determines whether or not the timing for executing the travel control has arrived for the identified travel control type according to a predetermined travel control algorithm. This timing is specified by the same method as in Step 806. If the travel control determination unit 204 determines that the timing for executing the travel control has arrived for the travel control type determined to be executable, the travel control instruction unit 206 transmits a control content instruction (step 809).

  In any case, it is determined that the travel control can be performed based on the evaluation value of the travel control associated with each feature point, and the travel control is performed according to a predetermined travel control algorithm. When it is determined that the timing has arrived, a control content instruction for executing the travel control is transmitted.

  In the processing after step 810, the traveling control evaluation unit 205 evaluates the traveling control content. First, when step 809 is executed and then step 810 is executed, in step 810, the traveling control evaluation unit 205 determines a predetermined time period determined based on the time period when the traveling control based on the instruction in step 809 is performed. Data relating to the vehicle operation detected by the sensor group 80 is acquired during the time period. If step 808 is executed and then step 810 is executed, in step 810, the travel control evaluation unit 205 determines that the travel control is determined to be available if the travel control determined to be unavailable in step 807 is available. Data relating to vehicle operation detected by the sensor group 80 is acquired in a predetermined time zone determined based on the time zone estimated to have been executed.

  Here, the above-mentioned “predetermined time zone” is a time zone in which the vehicle operation corresponding to the travel control specified in step 806 is highly likely to be performed by the driver of the host vehicle 2. For example, when step 810 is executed subsequent to step 809, the travel control specified in step 806 is actually performed. At this time, if the executed travel control is not appropriate, it is assumed that the vehicle operation contrary to the travel control is performed by the driver in the time zone in which the travel control is performed or in a time zone near the time zone. Alternatively, when step 810 is executed subsequent to step 808, the travel control specified in step 806 is not performed, but when the specified travel control is appropriate, the specified travel control can be performed. It is assumed that a vehicle operation that does not violate the specified travel control is performed by the driver in a time zone that would have been implemented if any. Specifically, the “predetermined time zone” may be, for example, the same time zone as the time zone in which the specified travel control is (or will be) implemented, It may be a time zone including a time zone and a time zone of a predetermined length before and after the time zone, or a time zone during which the travel control determining unit 204 calculates the travel control content for the feature point or a time zone before and after the time zone. It may be a time zone including.

  The data relating to the vehicle operation is data indicating the vehicle operation actually detected by the driver of the host vehicle 2 detected by the sensor group 80. For example, the accelerator opening (accelerator operation) of the host vehicle 2, the friction brake, and the like. , Various brake amounts (brake operation) such as regenerative brake or exhaust brake, shift lever position (gear operation), winker information (winker operation), steering angle / yaw rate information (handle operation), and the like.

  Subsequently, the travel control evaluation unit 205 compares the travel control instruction content specified in step 806 with the data related to the vehicle operation acquired in step 810 in step 811 and evaluates the travel control instruction content. Specifically, it is confirmed whether or not the specified traveling control instruction content is actually contrary to the vehicle operation performed by the driver of the host vehicle 2. For example, in the above-described example of the regenerative brake, since the travel control content is an operation related to the brake, the regenerative brake travel control instruction is transmitted (that is, the regenerative brake is operated based on the travel control instruction). When the driver of the host vehicle 2 performs an accelerator operation, the traveling control instruction and the vehicle operation are contradictory. Therefore, the identified traveling control is evaluated as malfunctioning (failed). Note that the evaluation value may be expressed as a binary value such as failure and success, or may be a numerical value of the degree of success of the traveling control using an evaluation function related to the traveling control instruction and the vehicle operation.

  Examples of vehicle operations that conflict with the travel control instructions include the accelerator operation (or vice versa) for the brake operation described above, the downshift for shift up (or vice versa), the winker operation on the side different from the travel control instruction, and travel Steering in the direction opposite to the control instruction can be mentioned.

  In the evaluation in step 811 in the learning mode, a different standard from the evaluation in step 811 after step 809 is executed may be used. For example, when step 809 is executed and the driver does not perform any vehicle operation that does not or does not contradict the implemented travel control (for example, the implemented travel control is the use of a regenerative brake). When the driver did not perform either the brake operation or the accelerator operation during the predetermined time period corresponding to the travel control), the travel control performed was appropriate (that is, the travel control was successful) Can be estimated. However, if step 809 is not executed and step 811 is executed in the learning mode, if the driver does not perform any vehicle operation that does not or does not contradict the driving control specified in step 806, It may be determined that the travel control has failed because the travel control performed may not have been actually required.

  Thereafter, the traveling control evaluation unit 205 transmits the result evaluated in step 811 to the vehicle traveling control support server 10 in step 812. After waiting for a predetermined time (step 820), the process returns to step 801 and repeatedly executes the above-described processing. .

  The process of the travel control support server 10 includes, as main processes, a related peripheral information providing process for providing related peripheral information to the travel control apparatus 20 of the vehicle 2 and a travel control apparatus 20 of one or more vehicles 2. And a traveling control evaluation management process for managing traveling control evaluation for each feature point based on the received traveling control evaluation result information. The former related peripheral information provision processing has already been shown in the related peripheral information acquisition processing flow 500 of the travel control device 20. Therefore, next, the traveling control evaluation management process will be described.

  FIG. 13 shows a flow 850 of the travel control evaluation management process executed in the vehicle travel control system 1 of the first embodiment of the present invention.

  The travel control evaluation result receiving unit 105 of the travel control support server 10 first waits for reception of a travel control evaluation result message 860 transmitted from one or more vehicles 2. When the travel control evaluation result message 860 is transmitted from the travel control device 20 of the vehicle 2 via the network 3 in step 812 of the travel control processing flow 800 of the travel control device 20 described above, the travel control evaluation result reception unit 105 The travel control evaluation result message 860 is received (step 851). Although not shown in the figure, when the traveling control evaluation result receiving unit 105 receives the traveling control evaluation result message 860, the traveling control evaluation result receiving unit 105 analyzes and extracts various data according to a traveling control evaluation result message format 870 described later.

  FIG. 14 is an explanatory diagram illustrating an example of a format 870 of the travel control evaluation result message 860 transmitted by the travel control device 20 according to the first embodiment of this invention. However, illustration of header information related to the communication protocol is omitted.

  The travel control evaluation result message 860 includes a vehicle ID 871 of the host vehicle 2, a feature point ID 872 indicating a feature point to be evaluated for travel control, a travel control evaluation result 873, and the like. The travel control evaluation result 873 is the travel control evaluation result in Step 811 of the travel control processing flow 800, and the travel control type 881 (881-1 to 881-h in the example of FIG. 14) and the evaluation value 882 for the travel control type. It is a list of combinations (882-1 to 882-h in the example of FIG. 14). The evaluation value 882 may be expressed by a binary value of success (= 1) or failure (= 0). Alternatively, an index of the degree of success that allows an arbitrary intermediate value such as 0 point (complete failure) to 100 point (complete success) may be used as the evaluation value 882.

  Subsequently, in step 852, the traveling control evaluation management unit 106 updates traveling control evaluation information corresponding to the feature point ID 872 based on the information of the traveling control evaluation result message 860 received in step 851. Specifically, first, the traveling control evaluation management unit 106 acquires a data entry having the same feature point ID 301 as the feature point ID 872 from the feature point data group 112. Subsequently, the traveling control evaluation management unit 106 selects all the travelings included in the traveling control evaluation result 873 among the evaluation values of one or more traveling control types included in the traveling control evaluation value 303 of the acquired feature point data entry. The evaluation value of the same travel control type as the control type 881 is updated.

  For example, when an evaluation value (e.g., evaluation value 882-1) included in the travel control evaluation result 873 is successful, a predetermined numerical value is added to the evaluation value held as the travel control evaluation value 303 (e.g., +0.1 ), The evaluation value may be updated by subtracting a numerical value from the evaluation value of the traveling control evaluation value 303 (for example, −3.0) when it is a failure. If the numerical value to be subtracted from the evaluation value at the time of failure is made sufficiently larger than the numerical value to be added at the time of success, the evaluation value rapidly decreases when the failure frequency of the traveling control increases. As a result, the evaluation value for the travel control type with a high failure frequency at the feature point can be quickly lowered.

  The traveling control evaluation value 303 may be expressed by a success rate of traveling control in a predetermined period. In this case, if the predetermined period is, for example, one month, the number of successes per unit time (for example, one day) and the number of control evaluations (success number + failure number) with a sufficiently small granularity with respect to the predetermined period are managed. The traveling control evaluation value 303 may be calculated by calculating the success rate during the corresponding predetermined period. The evaluation value is updated by reflecting the traveling control evaluation result on the current number of successes and the number of control evaluations.

  In the above example, the update method of the evaluation value by adding a predetermined numerical value (for example, +0.1 or −3.0, respectively) depending on whether the evaluation value is success or failure is successful. This is equivalent to calculating the success rate after assigning different weights to the number and the number of failures. For example, by calculating the success rate by weighting the number of failures 30 times the number of successes, as in the case of adding the above +0.1 or -3.0, the evaluation for the travel control type with a high failure frequency is performed. The value can be lowered quickly.

  When the update of the travel control evaluation value of the feature point is completed in Step 852, in Step 853, the travel control availability determination unit 107 determines whether or not the travel control evaluation value updated in Step 852 exceeds a predetermined threshold (Eth). Confirm. If the traveling control evaluation value exceeds the threshold value, traveling control availability determination unit 107 sets that traveling control is possible for the traveling control type at the feature point (step 854). Specifically, the travel control type is registered in the feasible control 304 in the data entry of the feature point in the feature point data group 112. If the travel control evaluation value does not exceed the threshold value, the travel control availability determination unit 107 sets the travel control impossibility for the travel control type at the feature point (step 855). Specifically, the travel control type is excluded from the feasible control 304 in the feature point data entry. In any case, when step 854 or step 855 is completed, the process returns to step 851.

  As a result of the above processing, the traveling control evaluation results collected from one or more vehicles 2 are statistically reflected, and therefore it is possible to quickly determine that traveling control is impossible for feature points that frequently fail in traveling control. it can. Therefore, the evaluation value of the travel control can be kept low at the feature point where the malfunction of the travel control is likely to occur due to the influence of the surrounding environment, the shape or the attribute of the road, etc. Implementation of control can be suppressed.

  If the related feature point information 621-1 of the related peripheral information message 512 does not include information indicating whether or not the travel control can be performed and includes an evaluation value such as a success rate, the processing unit 100 performs steps 853 to 855. May be omitted.

  Preferably, the vehicle travel control system 1 uses the input / output device 50 to present information related to travel control to the driver or passenger of the vehicle 2 or the driver or passenger makes settings related to travel control. You can do that.

  FIG. 15 is an explanatory diagram of an example of information related to traveling control displayed by the traveling control information output unit 51 (assuming a display in the present specification) of the input / output device 50 according to the first embodiment of the present invention.

  The input / output device 50 is, for example, a navigation system device. On the map screen 1001 of the travel control information output unit 51, for example, a road map around the vehicle position 1050 in the navigation system and a route 1041 being guided are displayed. If there is no route information being guided due to reasons such as route guidance not being set, the travel route estimated by the vehicle travel route estimation unit 203 may be displayed as the route 1041.

  Further, on the route 1041 being guided, the positions of the feature points 1051 to 1053 targeted by the travel control function enabled by the travel control device 20 are displayed. In particular, it is desirable that the feature points corresponding to the running control during operation are highlighted. In the example of FIG. 15, since the traveling control corresponding to the feature point 1051 is operating, the feature point 1051 is highlighted. The highlighting may be performed, for example, by enlarging an icon representing a feature point, blinking, or changing a display color.

  Furthermore, it is desirable that the display method is changed depending on whether the traveling control for the feature points is enabled or disabled. For example, the icon of the feature point 1052 for which traveling control is disabled is grayed out or the display is reduced to show the difference from the enabled feature point 1051. Here, “valid / invalid” refers to whether the user of the host vehicle 2 operates the travel control with respect to the feature point that can be travel controlled, instead of whether the feature control determined by the vehicle travel control support server 10 is possible. It is assumed that they are set individually.

  While the travel control is in operation, for example, a pop-up screen 1060 is displayed on the map screen 1001 in a form that does not interfere with the original display, and an image 1061 indicating the feature point corresponding to the travel control in operation is displayed. In this example, the feature point 1051 corresponding to the running control during operation is a signalized intersection, and since the automatic regenerative brake is operated when the signal is red, an icon representing a red signal is displayed as the image 1061. ing.

  Further, for example, detailed information regarding the travel control is displayed on the travel control information display screen 1002 of the travel control information output unit 51. This is a screen that is displayed when, for example, an operator (for example, a driver or a passenger) in the input / output device 50 selects to display the detailed information of the travel control information according to a menu screen or the like. In the example of FIG. 15, the travel control information display screen 1002 includes a travel control operation state screen 1010 and an assumed travel control information screen 1020.

  The traveling control operation state screen 1010 displays the current state relating to traveling control. For example, in FIG. 15, since the automatic regenerative brake for the signalized intersection is in operation, the travel control operation state screen 1010 is operating in the form of “automatic regenerative brake in operation!” (Display 1011), for example. The traveling control type is displayed. Note that the display means is not limited to text, and an image icon or animation representing the running control type being operated may be displayed. In addition, the travel control operation state screen 1010 includes a feature point type 1012 (“signal intersection” in FIG. 15) targeted for travel control during operation and related information 1013 (“red signal: 10 seconds ") may also be displayed.

  The feature point related information 1013 is, for example, attribute information of the feature point related to the behavior of running control during operation. If it is a signalized intersection, the signal state (red) and its retention time (or Switching timing to the state), and the curvature of the curve (R value) at the curve start point. By displaying such attribute information together, the driver or passenger can recognize the reason for the operation of the traveling control, and the uncomfortable feeling caused by the automatic operation of the control can be suppressed.

  The assumed travel control information screen 1020 displays feature point information related to future travel control. For example, in FIG. 15, one or more feature point information related to the travel control type currently enabled by the current travel control device 20 on the route 1041 is displayed. Each feature point information includes, for example, each feature point type 1021, a distance 1022 (distance on the road) from the own vehicle 2 to each feature point, a target travel control type 1023, a target travel control state 1024, Etc. are included. The state of the target travel control is “in operation” if the travel control is already in operation, and whether the travel control for the feature point is in effect if it is not yet in operation (“valid” or “invalid” ]) Is displayed.

  It is desirable that the display method is changed in accordance with the state of each traveling control. For example, feature point information during operation is highlighted by making it red or making characters bold, and invalid feature point information is made effective by making characters of light color or making characters smaller. Express the difference between

  For feature points that have not yet been operated, for example, buttons 1025 and 1026 may be provided to allow the driver or passengers to input travel control valid / invalid settings for the feature points. good. For example, when a driver or a passenger touches the button 1025 or the like, the traveling control information input unit 52 of the input / output device 50 recognizes that the button 1025 or the like is pressed, and a predetermined operation is executed.

  For example, for an invalid feature point, an “validate” button 1025 is displayed, and when this button 1025 is pressed, the input / output device 50 communicates with the traveling control device 20 to indicate the feature point. Set the travel control to valid. On the other hand, for the feature points that are enabled, an “invalidate” button 1026 is displayed, and when this button 1026 is pressed, the input / output device 50 communicates with the travel control device 20 to indicate the feature point. The traveling control is set to be invalid. The travel control invalidated in this way is registered in the invalid travel control 404 of the related feature point data group 212. As will be described later, the registration of the invalid travel control 404 is reflected in the setting of the forced OFF flag 374.

  FIG. 16 shows a travel control information display processing flow 1100 executed by the input / output device 50 according to the first embodiment of the present invention to display the travel control information.

  First, in step 1101, the input / output device 50 confirms whether or not the traveling control information display screen is valid. The input / output device 50 manages the state of the screen displayed by the traveling control information output unit 51, and displays the traveling control information display screen even if the traveling control information display screen is displayed or not displayed. If the program has been started, it is determined that the program is valid (Yes in step 1101). On the other hand, when the program for displaying the traveling control information display screen is not started, it is determined that the program is invalid (No in step 1101).

  If No in step 1101, the process proceeds to step 1106. After waiting for a predetermined time, the process returns to step 1101 again. On the other hand, if Yes in step 1101, the process proceeds to step 1102, and the input / output device 50 generates a message requesting the travel control information (travel control information request message 1121) and transmits it to the travel control device 20.

  The traveling control information request message 1121 includes, for example, a message type indicating that this message is a traveling control information request message, a request information flag designating the type of traveling control information desired to be transmitted, and the like. The types of travel control information correspond to, for example, peripheral road information 601, related feature point information 602, related road event information 603, vehicle information 604, and the like in the related peripheral information message format 600. For example, if the input / output device 50 is a navigation system device and already holds surrounding road information and vehicle information, it is not necessary to have the travel control device 20 provide them. It can be specified that surrounding road information and vehicle information are not transmitted.

  When the traveling control information providing unit 207 receives the traveling control information request message 1121 transmitted from the input / output device 50 (step 1111), the traveling control device 20 acquires necessary traveling control information from the storage unit 210 according to the requested content. In step 1112, the acquired travel control information is configured as a travel control information message 1122 and transmitted to the input / output device 50 (step 1113).

  FIG. 17 is an explanatory diagram illustrating an example of a format 1150 of the travel control information message 1122 transmitted by the travel control device 20 according to the first embodiment of this invention. However, illustration of header information related to the communication protocol is omitted.

  The travel control information message 1122 includes the travel control information acquired in step 1112. The travel control information acquired in step 1112 includes, for example, surrounding road information 1151, related feature point information 1152, related road event information 1153, vehicle information 1154, travel control state information 1155, and the like. The various information 1151-1154 is the same as the information 601-604 of the related peripheral information message format 600.

  The traveling control state information 1155 includes, for example, in-operation feature points indicating the traveling control types 1161-1 to 1161-h to which the traveling control device 20 corresponds and the feature points of the target on which that type of traveling control is operating. A list of IDs 1162-1 to 1162-h is included. In the operating feature point ID 1162-1 and the like, when the traveling control is operating, the target feature point ID is set, whereas when it is not operating, a value corresponding to “not applicable” is set. Is done. In addition, when the information to be transmitted is specified by the request information flag of the travel control information request message 1121, only the specified information may be included in the travel control information message 1122. Moreover, the traveling control information message 1122 may be transmitted as one message, or may be divided into a plurality of arbitrary messages and transmitted.

  When the input / output device 50 receives the traveling control information message 1122 transmitted from the traveling control device 20 (step 1103), the input / output device 50 analyzes the received message according to the message format 1150, extracts the various data, and extracts the extracted various data. According to the data, for example, the travel control information in the format shown in FIG. 15 is displayed (step 1104). Then, after waiting for a predetermined time (step 1106), the process returns to step 1101 and the same processing is executed.

  FIG. 18 shows a process flow 1200 for setting the travel control of the travel control device 20 via the input / output device 50 according to the first embodiment of the present invention.

  The input / output device 50 monitors the input from the travel control information input unit 52, and first confirms whether there is an input related to the travel control setting (step 1201). If there is no input (No in step 1201), the process proceeds to step 1206, and after waiting for a predetermined time, the process returns to step 1201 again. When there is an input, the input / output device 50 acquires information related to the travel control setting from the input information (step 1202). Then, the input / output device 50 configures a message 1231 including the acquired traveling control setting information according to a predetermined format, and transmits the message 1231 to the traveling control device 20 (step 1203).

  The travel control setting information is, for example, information that specifies travel control validation / invalidation settings at a certain feature point, travel control function learning mode ON / OFF settings, and the like. The message for setting the validation / invalidation of the travel control includes, for example, a setting message type that represents the type of setting content, a feature point ID that represents a feature point to be changed, and a travel control that is to be changed , A travel control type flag indicating a setting change value (validation / invalidation), and the like. The message for changing the learning mode of the travel control function includes, for example, a setting message type indicating the type of setting content, a learning mode flag indicating a setting change value (learning mode ON / OFF), and the like.

  When the travel control setting information is transmitted as the message 1231 from the input / output device 50, the travel control information setting unit 208 of the travel control device 20 receives the message 1231 (step 1211), and performs the travel control according to the content of the message 1231. The setting is updated (step 1212). For example, a setting value indicating whether the travel control is valid / invalid at a certain feature point is reflected by changing the invalid travel control 404 of the data entry of the feature point in the related feature point data group 212. Specifically, for example, when the travel control A for the feature point is invalidated in response to an operation of the “invalidate” button 1026 or the like, the travel control information setting unit 208 invalidates the travel control 404 for the data entry of the feature point. To “running control A”. In the case of validation, conversely, “travel control A” is deleted from the invalid travel control 404. Further, for example, a setting value indicating ON / OFF of the learning mode is stored in the travel control parameter data group 215, and the setting change is realized by changing the value.

  When the update of the travel control setting is completed in step 1212, the travel control information setting unit 208 transmits a notification (message 1232) indicating the setting reflection to the input / output device 50 (step 1213). When the input / output device 50 receives the setting reflection notification message 1232 (step 1204), the input / output device 50 reflects the reflected information on the display screen of the travel control information (for example, the travel control information display screen 1002 in FIG. 15) (step 1205). ). Then, after waiting for a predetermined time (step 1206), the process returns to step 1201 to continue the processing.

  On the other hand, the travel control information setting unit 208 of the travel control device 20 transmits the travel control setting information to the vehicle travel control support server 10 when the setting reflection notification is transmitted in Step 1213 (message 1233). Note that the message 1233 includes information equivalent to the message 1231.

  When receiving the message 1233 (step 1221), the vehicle travel control support server 10 extracts the data entry related to the host vehicle 2 from the vehicle-specific data group 115 and corrects the corresponding value. For example, when the message 1233 includes a setting value that indicates the validity / invalidity of a certain travel control at a certain feature point, the vehicle travel control support server 10 complies with the feature point ID 371 and the travel control 372 in the vehicle-specific data group 115. The OFF flag 374 is corrected according to the received set value.

  In the present embodiment, the technique for changing the settings related to the host vehicle 2 via the input / output device 50 of the vehicle 2 is described as a specific example. However, the operator uses a terminal such as a personal computer (not shown) to connect to the Internet. The setting may be changed via a web browser by accessing the vehicle travel control support server 10 via the web browser. In that case, when a web server is mounted on the vehicle travel control support server 10 and access is received from the terminal, authentication is performed based on the vehicle ID or the user ID associated with the vehicle ID, and the vehicle-specific data group 115. The vehicle travel control system 1 is configured so that the settings related to the vehicle 2 specified by the vehicle ID or the user ID can be executed via the terminal.

  In addition, the administrator of the vehicle travel control system 1 can make settings related to the vehicle travel control system 1 using a similar interface. For example, in order to invalidate the travel control type for which support has ended, the service availability 323 in the data entry of the travel control type in the travel control type data group 114 can be set to “impossible”. Further, for example, a new feature point data entry can be added to the feature point data group 112.

  Furthermore, in this embodiment, it is also possible to dynamically add or invalidate feature point data entries to the feature point data group 112. Since the road event occurs dynamically, the feature points resulting from the road event are not included in the normal feature point data group 112. For example, in the case of a road event such as construction or traffic jam, the shape or attribute of the road may be changed semi-fixed for a certain period. In that case, feature points that should be usable in traveling control may appear or disappear. When a new feature point appears, a feature point data entry corresponding to the feature point data group 112 is added. At this time, if the feature point data entry is temporarily generated by a specific road event, a road event ID corresponding to the related road event 307 of the feature point data group 112 is set.

  Accordingly, when the vehicle travel control support server 10 provides the feature point information to the vehicle 2, when the related road event 307 of the corresponding feature point data entry is set, the road event data group 113 is referred to and the road By confirming whether the event is valid, the feature point data entry can be immediately invalidated when the road event disappears. On the other hand, in order to prevent the malfunction of the travel control corresponding to the existing feature point from occurring due to the occurrence of the road event, it is possible to temporarily not perform the travel control when the road event occurs. For example, when it is known that the trouble is likely to occur when the travel control B is performed when a traffic jam occurs, “congestion” is set in the service stop road event type 324 in the data entry of the travel control B in the travel control type data group 114. Keep it. In step 853 of the travel control evaluation management processing flow 850, a road event occurring near the feature point is confirmed in the road event data group 113. In this case, for the travel control type in which the road event type is registered in the service stop road event type 324 of the travel control type data group 114, the travel control is not possible even if the evaluation value for the feature point is equal to or greater than the threshold value. Is set (step 855). This makes it possible to suppress temporary malfunctions due to the occurrence of dynamic road events.

  As described above, according to the present embodiment, the traveling control device 20 of each vehicle 2 evaluates the success or failure of the traveling control result for each feature point, and the traveling control evaluation result is aggregated by the vehicle traveling control support server 10. Thus, it is possible to quantitatively evaluate the ease of occurrence of a malfunction in travel control at each feature point. If the driving control malfunction is likely to occur more than a predetermined value (for example, when the driving control success rate is lower than the predetermined value), it is excluded from the driving control target. It is possible to adaptively suppress the malfunction of the travel control that is difficult to predict in advance, which is caused by the influence of the shape and attributes.

  Ease of occurrence of such a malfunction is evaluated based on information collected from the travel control devices 20 of a plurality (preferably a large number) of vehicles 2. For this reason, even on a road on which a certain vehicle 2 travels for the first time, malfunction of travel control can be suppressed based on information from other vehicles 2 that have already traveled on the road.

  Further, according to the present embodiment, the travel control device 20 does not actually execute the travel control for a certain feature point, and the vehicle operation that contradicts the travel control is performed during the period in which the travel control is assumed to be performed. By checking whether it is not performed, it is possible to evaluate whether the traveling control content is correct or incorrect. Therefore, it is not necessary to accumulate actual examples of malfunctions, and statistical data for determining whether or not traveling control can be performed can be collected. Further, since the evaluation regarding the travel control can be continued even when the travel control is impossible (if the learning mode is ON), if the environment changes and the malfunction of the travel control does not occur, the travel control can be performed. As a result, it is possible to adaptively set the propriety of the travel control so that the travel control can be executed. On the other hand, when it is not necessary to perform such learning, the evaluation relating to the traveling control is not performed (therefore, the evaluation result is not transmitted to the vehicle traveling control support server), so Traffic can be reduced.

  In addition, embodiment described above is an example and this invention is not limited to this. That is, various applications are possible, and all the embodiments are included in the scope of the present invention.

  For example, in the above embodiment, each process of the travel control device and the vehicle travel control support server is realized by executing a predetermined operation program using a processor and a RAM. It can also be realized by hardware. In the above embodiment, the travel control device, the wireless communication device, the vehicle positioning device, the input / output device, the peripheral object detection device, the vehicle control device group, and the sensor group are described as individual devices. It is also possible to realize any combination of two or more according to the above.

  When each of the above processes is realized by a processor executing a predetermined operation program, information such as an operation program, a table, and a file for realizing each process is stored in a nonvolatile semiconductor memory, a hard disk drive, an SSD (Solid State). Drive) or a computer-readable non-transitory data storage medium such as an IC card, SD card, or DVD.

  In the above embodiment, the travel control device 20 is configured to acquire the surrounding map data group from the vehicle travel control support server 10, but the travel control device 20 itself stores data corresponding to the map data group 111. It may be managed or acquired from another device in the vehicle 2. In that case, the present invention can be realized by receiving only the feature point information around the vehicle 2 from the vehicle travel control support server 10.

  Or each vehicle 2 may hold | maintain the information equivalent to the memory | storage part 110 of the vehicle travel control support server 10, and may evaluate each travel control corresponding to each feature point based on it. In that case, the vehicle travel control support server 10 becomes unnecessary. However, as shown in the first embodiment, by using the vehicle travel control support server 10, each vehicle 2 does not need to hold map data and feature point data not related to the own vehicle 2, and the own vehicle Even on the road on which the vehicle 2 travels for the first time, the malfunction of the travel control can be suppressed based on the evaluation results collected by the vehicle travel control support server 10 from the other vehicle 2.

  In the drawings, control lines and information lines considered necessary for describing the embodiment are shown, and all control lines and information lines included in an actual product to which the present invention is applied are not necessarily shown. Not necessarily. Actually, it may be considered that almost all the components are connected to each other.

1: vehicle travel control system 2: vehicle 3: network 4: roadside machine 10: vehicle travel control support server 20: travel control device 30: wireless communication device 40: own vehicle position positioning device 50: input / output device 51: travel control information Output unit 52: Travel control information input unit 60: Surrounding object detection device 70: Vehicle control device group 80: Sensor group 100: Processing unit 101 of vehicle travel control support server 10: Vehicle information reception unit 102: Vehicle travel route estimation unit 103 : Related peripheral information extraction unit 104: related peripheral information transmission unit 105: travel control evaluation result reception unit 106: travel control evaluation management unit 107: travel control availability determination unit 110: storage unit 111 of the vehicle travel control support server 10: map data Group 112: Feature point data group 113: Road event data group 114: Travel control type data group 115: Vehicle-specific data group 120: Vehicle travel Communication unit 200 of the support server 10: Processing unit 201 of the travel control device 20: Related peripheral information acquisition unit 202: Own vehicle position estimation unit 203: Own vehicle travel route estimation unit 204: Travel control determination unit 205: Travel control evaluation unit 206: Travel control instruction unit 207: Travel control information providing unit 208: Travel control information setting unit 209: Vehicle information acquisition unit 210: Storage unit 211 of the travel control device 20: Peripheral map data group 212: Related feature point data group 213: Related road event data group 214: Surrounding object data group 215: Travel control parameter data group 220: Communication unit of travel control device 20

Claims (9)

A travel control system that includes a travel control device that is mounted on a vehicle and controls travel of the vehicle, and a server device that communicates with the travel control device,
The travel control device includes a first interface that communicates with the server device via a network, a first processor connected to the first interface, and a first storage device connected to the first processor. And
The server device includes a second interface connected to the network, a second processor connected to the second interface, and a second storage device connected to the second processor,
The second storage device
Map information including at least road network information,
Information associating a point on the map with the travel control applied to the vehicle traveling on the road indicated by the map, and an evaluation value indicating the validity of the association between the point on the map and the travel control And feature point information including
The travel control device transmits at least information indicating the position of the vehicle to the server device,
The server device transmits, based on the feature point information, the feature point information related to a point where a relationship with a position of the vehicle satisfies a predetermined condition to the travel control device,
The travel control device includes:
Storing the received feature point information in the first storage device;
Based on the feature point information stored in the first storage device, a point where a relationship with the position of the vehicle satisfies a predetermined condition is specified,
Based on the feature point information stored in the first storage device, the traveling control associated with the identified point is identified,
It is determined whether or not to execute the specified travel control based on the identified point and the evaluation value corresponding to the identified travel control,
In order to execute the specified travel control when it is determined to execute the specified travel control and it is determined that the timing for executing the specified travel control has arrived based on a predetermined condition Send control instructions,
Based on information acquired from a sensor mounted on the vehicle, an actual vehicle operation performed by the driver of the vehicle during a predetermined period determined based on a period during which the identified travel control is performed is identified And
A result of comparison between the identified travel control and the identified actual vehicle operation is transmitted to the server device;
If it is determined not to execute the specified travel control, a control instruction for executing the specified travel control is not transmitted, and if the control instruction is transmitted, the specified travel control is performed. An actual vehicle operation performed by the driver of the vehicle during a predetermined period determined based on the expected period, and a comparison between the identified travel control and the identified actual vehicle operation Sending the result to the server device;
The server device obtains an evaluation value for associating the identified point with the identified traveling control based on the comparison result. A travel control device that is mounted on a vehicle and controls the travel of the vehicle,
A processor and a storage device connected to the processor;
The storage device stores feature point information including information indicating traveling control associated with any point and an evaluation value indicating validity of association between any point and the traveling control. ,
The travel control device includes:
Based on the feature point information, identify a point where the relationship with the vehicle position satisfies a predetermined condition,
Based on the feature point information, identify the travel control associated with the identified point,
It is determined whether or not to execute the specified travel control based on the identified point and the evaluation value corresponding to the identified travel control,
If it is determined not to execute the specified travel control, a control instruction for executing the specified travel control is not transmitted, and if the control instruction is transmitted, the specified travel control is performed. An actual vehicle operation performed by the driver of the vehicle during a predetermined period determined based on the expected period, and a comparison between the identified travel control and the identified actual vehicle operation A travel control device that outputs a result . The travel control device according to claim 2,
It is determined to perform the specified travel control, and, based on a predetermined condition, when the timing of executing the specified travel control is determined to have arrived, in order to perform the specified travel control And is executed by a driver of the vehicle during a predetermined period determined based on a period during which the specified travel control is executed based on information acquired from a sensor mounted on the vehicle. Identify actual vehicle operation,
A travel control device that outputs a result of comparison between the identified travel control and the identified actual vehicle operation. The travel control device according to claim 2 or 3,
  When the specified actual vehicle operation is an operation contrary to the specified travel control, it is determined that the specified travel control has failed,
  A travel control device that outputs information indicating whether or not the specified travel control has failed as a result of the comparison. The travel control device according to claim 4,
  An interface connected to the processor and communicating via a network;
  When the feature point information regarding one or more points whose relationship with the position of the vehicle satisfies a predetermined condition is received from the server device, the received feature point information is stored in the storage device,
  A travel control device that transmits a result of comparison between the identified travel control and the identified actual vehicle operation to the server device. The travel control system according to claim 1,
  The server device calculates a success rate of each traveling control associated with each point based on the comparison results received from a plurality of the vehicles, and acquires the calculated success rate as the evaluation value. A travel control system characterized by The travel control system according to claim 6,
  The server device
  When the success rate of each traveling control associated with each point exceeds a predetermined threshold, information indicating that the traveling control associated with each point is executable is generated, and Obtain the generated information as the evaluation value,
  The feature point information to be transmitted to the vehicle includes, as the evaluation value, either the success rate or information indicating whether or not each traveling control associated with each point can be executed. A featured travel control system. The travel control system according to claim 7,
  The server device
  Obtained from the result of the comparison received from the plurality of vehicles, after weighting the number of successes and the number of failures of each of the travel control associated with each point, to calculate the success rate,
  A travel control system characterized in that a weight attached to the number of failures is larger than a weight attached to the number of successes. A travel control system according to any one of claims 1, 6, 7 or 8,
  The server device
  Based on the information indicating the position of the vehicle and the map information, the travel route of the vehicle is estimated,
  A travel control system characterized in that at least one or more points on the estimated travel route are identified as points where a relationship with a position of the vehicle satisfies a predetermined condition.

Images