Road congestion management
By generating and applying a long-term shared world model, traffic congestion problems are solved, efficient and coordinated operation of networked vehicles and automated vehicles is achieved, traffic congestion and carbon emissions are reduced, and the safety and efficiency of vehicles are improved.
Patent Information
- Application Number
- CN202380030847.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-29
- Filing Date
- 2023-02-16
- Publication Date
- 2024-11-12
AI Technical Summary
The high costs, excessive carbon emissions and vehicle accidents caused by traffic congestion have increased, and existing connected vehicles and automated vehicles are difficult to effectively reduce traffic congestion.
By accessing data from multiple networked vehicles on the road, generating long-term shared world models, applying traffic flow models to predict future speeds, and transmitting control signals to networked autonomous vehicles to optimize their operations.
Effectively reduce traffic congestion, reduce carbon emissions, improve the operating efficiency and safety of carrier tools, and reduce the possibility of accidents.
Smart Images

Figure CN118946918A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to connected vehicles and connected automated vehicles, and more particularly to generating a long-term shared world model of roads and using the long-term shared world model in the operation of a connected automated vehicle. Background Art
[0002] Traffic congestion has high costs in terms of, for example, lost work time, excess carbon emissions, and increased likelihood of vehicle accidents. The proportion of vehicles on the road that are connected vehicles (CVs) capable of transmitting data over a network and connected automated vehicles (CAVs) capable of transmitting data over a network and receiving control signals over a network is increasing. Summary of the invention
[0003] Disclosed herein are aspects, features, elements, implementations, and embodiments for making real-time decisions using belief state determinations as vehicles are traveling through a vehicle transportation network.
[0004] One aspect of the disclosed embodiment is a method for generating and transmitting control signals to a vehicle. The method includes accessing vehicle data from a plurality of networked vehicles, i.e., a subset of a plurality of CVs, on a road portion, the vehicle data including at least one of position, speed, and headway. The method includes generating a long-term shared world model based on the accessed vehicle data. The method includes generating a data structure using the long-term shared world model by applying a traffic flow model to the long-term shared world model, the data structure representing predicted future speeds on the road portion by position and time. The method includes transmitting a control signal to a networked autonomous vehicle, i.e., a CAV, for controlling the operation of the CAV based on the generated data structure.
[0005] One aspect of the disclosed embodiment is a device for generating a control signal and transmitting the control signal to a vehicle. The device includes a processor and a memory. The memory stores instructions. The processor executes instructions to: access vehicle data from each CV in a subset of a plurality of networked vehicles, i.e., a plurality of CVs, on a road portion, the vehicle data including at least one of position, speed, and headway. The processor executes instructions to generate a long-term shared world model based on the accessed vehicle data. The processor executes instructions to: generate a data structure using the long-term shared world model by applying a traffic flow model to the long-term shared world model, the data structure representing a predicted future speed on the road portion by position and time. The processor executes instructions to transmit a control signal to a networked autonomous vehicle, i.e., a CAV, for controlling the operation of the CAV based on the generated data structure.
[0006] One aspect of the disclosed embodiment is a computer-readable medium for generating a control signal and transmitting the control signal to a vehicle. The computer-readable medium stores instructions. The instructions include code to: access vehicle data from a plurality of networked vehicles, i.e., each CV in a subset of a plurality of CVs on a road portion, the vehicle data including at least one of position, speed, and headway. The instructions include code to generate a long-term shared world model based on the accessed vehicle data. The instructions include code to: generate a data structure using the long-term shared world model by applying a traffic flow model to the long-term shared world model, the data structure representing a predicted future speed on the road portion by position and time. The instructions include code to: transmit a control signal to a networked autonomous vehicle, i.e., a CAV, for controlling the operation of the CAV based on the generated data structure.
[0007] Variations of these and other aspects, features, elements, implementations, and embodiments of the methods, devices, processes, and algorithms disclosed herein are described in further detail below. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Various aspects disclosed herein will become more apparent by reference to the examples provided in the following description and accompanying drawings, in which like reference numerals refer to like elements.
[0009] Figure 1 is a diagram of an example of a vehicle that can implement the aspects, features, and elements disclosed herein.
[0010] Figure 2 is a diagram of an example of a portion of a vehicle transportation and communication system that may implement the aspects, features, and elements disclosed herein.
[0011] Figure 3 is a data flow diagram of a technique for generating control signals using vehicle data according to an embodiment of the present disclosure.
[0012] Figure 4 is a data flow diagram of a long-term shared world model architecture according to an embodiment of the present disclosure.
[0013] Figure 5 A flow diagram in space and time according to an embodiment of the present disclosure is illustrated.
[0014] Figure 6 Speed and headway values measured for a probe vehicle according to an embodiment of the present disclosure are illustrated.
[0015] Figure 7 is a data flow diagram for traffic status determination according to an embodiment of the present disclosure.
[0016] Figure 8 An example vehicle communication and control architecture is illustrated in accordance with an embodiment of the present disclosure.
[0017] Fig. 9 is a data flow diagram for vehicle communications and control according to an embodiment of the present disclosure.
[0018] Fig.10 is a flow chart of a method for operating a vehicle using a long-term shared world model according to an embodiment of the present disclosure.
[0019] Fig.11 is a flowchart of a method for predicting future traffic data according to an embodiment of the present disclosure.
[0020] Fig.12 is a flow chart of a method for controlling vehicles using a multi-vehicle strategy selector according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0021] As described above, traffic congestion has a high cost in terms of, for example, lost work time, excess carbon emissions, and increased likelihood of vehicle accidents. The proportion of vehicles on the road that are networked vehicles (CVs) capable of transmitting data over a network and networked automated vehicles (CAVs) capable of transmitting data over a network and receiving control signals over a network is increasing. Techniques that utilize CV or CAV technology to reduce traffic congestion may be desirable.
[0022] According to some embodiments, a vehicle control server (which may be implemented as one or more than one physical or virtual machine) accesses vehicle data of each CV in a subset of multiple CVs on a road portion. Vehicle data from road sensors may also be accessed. Vehicle data may include the location of the vehicle or other vehicle providing the data, the speed of the vehicle or other vehicle providing the data, and / or the following distance of the vehicle or other vehicle providing the data. The vehicle control server stores the accessed vehicle data in a long-term shared world model. The vehicle control server generates a data structure by applying a traffic flow model to the long-term shared world model and using the long-term shared world model, which represents the predicted future speed on the road portion by position and time. The traffic flow model may be, for example, an artificial intelligence model trained using at least one of supervised learning, unsupervised learning, reinforcement learning, and online learning. The vehicle control server transmits a control signal to the CAV for controlling the operation of the CAV based on the generated data structure.
[0023] As used herein, the term "model" may include at least one of a classical planning model, an artificial intelligence (AI) model, and a machine learning (ML) model using supervised learning, unsupervised learning, or reinforcement learning, etc. The model may be based on data generated in the past and may be used to predict future data. For example, a long-term shared world model of a road portion may store data related to the average speed and congestion (e.g., the number of vehicles per unit distance) of the road portion in the past (e.g., at multiple times in the past three years) and used to predict the average speed and congestion of the road portion in the future (e.g., at 9 a.m. next Monday). For example, AI or ML techniques or other mathematical modeling techniques may be used to make predictions.
[0024] As used herein, the term "shared" may indicate a shared item accessed by at least two entities, etc. For example, at least two vehicles may contribute data to a shared model and / or receive data derived from a shared model. As used herein, the term "long-term" may indicate that the data is based on a time period exceeding a threshold. For example, a long-term model may be based on data generated over a time period exceeding one hour, two hours, one day, three days, one week, five weeks, one month, six months, or one year, etc. As used herein, the term "world" may indicate data based on two or more points in space, etc.
[0025] As used herein, a road portion may include a continuous portion of a road (e.g., a 1-2 kilometer stretch of a road). A road portion may be subdivided into a plurality of road segments. For example, a 1 kilometer road portion may be divided into 10 mutually exclusive and completely exhaustive road segments of 100 meters each.
[0026] It should be noted that every CAV is a CV. However, a vehicle may be a CV rather than a CAV. For example, a vehicle operated by a human driver that is capable of transmitting on a network would be a CV rather than a CAV. In some implementations, with appropriate permissions, CV technology may be implemented by an onboard computing device (e.g., a mobile phone) on the vehicle. For example, the computing device may determine the speed of the vehicle (e.g., using a global positioning system (GPS) on the device and a clock on the device) and transmit the speed of the vehicle on the network.
[0027] Figure 1 1 is a diagram of an example of a vehicle that may implement aspects, features, and elements disclosed herein. As shown, the vehicle 100 includes a chassis 110, a powertrain 120, a controller 130, and wheels 140. Although for simplicity, the vehicle 100 is shown as including four wheels 140, one or more other propulsion devices (such as pushers or running boards, etc.) may be used. Figure 1 1, the lines interconnecting elements such as powertrain 120, controller 130, and wheels 140 indicate that information such as data or control signals, power such as electricity or torque, or both information and power can be communicated between the various elements. For example, controller 130 can receive power from powertrain 120 and can communicate with powertrain 120, wheels 140, or both to control vehicle 100, which can include accelerating, decelerating, steering, or otherwise controlling vehicle 100.
[0028] As shown, the powertrain 120 includes a power source 121, a transmission 122, a steering unit 123, and an actuator 124. Other elements of the powertrain (such as a suspension, a drive shaft, an axle, or an exhaust system, etc.) or a combination of elements may be included. Although shown separately, the wheel 140 may be included in the powertrain 120.
[0029] The power source 121 may include an engine, a battery, or a combination thereof. The power source 121 may be any device or combination of devices operable to provide energy (such as electrical energy, thermal energy, or kinetic energy, etc.). For example, the power source 121 may include an engine (such as an internal combustion engine, an electric motor, or a combination of an internal combustion engine and an electric motor, etc.), and may be operable to provide kinetic energy as a motive force to one or more wheels in the wheels 140. The power source 121 may include a potential energy unit, such as one or more dry cells (such as nickel-cadmium (NiCd) batteries, nickel-zinc (NiZn) batteries, nickel-metal hydride (NiMH) batteries, lithium-ion (Li-ion) batteries, etc.), solar cells, fuel cells, or any other device capable of providing energy, etc.
[0030] The transmission 122 can receive energy (such as kinetic energy, etc.) from the power source 121, and can transmit the energy to the wheel 140 to provide motive force. The transmission 122 can be controlled by the controller 130, the actuator 124, or both. The steering unit 123 can be controlled by the controller 130, the actuator 124, or both, and the steering unit 123 can control the wheel 140 to steer the vehicle. The actuator 124 can receive a signal from the controller 130, and can actuate or control the power source 121, the transmission 122, the steering unit 123, or any combination thereof to operate the vehicle 100.
[0031] As shown, the controller 130 may include a positioning unit 131, an electronic communication unit 132, a processor 133, a memory 134, a user interface 135, a sensor 136, an electronic communication interface 137, or any combination thereof. Although shown as a single unit, any one or more of the elements of the controller 130 may be integrated into any number of separate physical units. For example, the user interface 135 and the processor 133 may be integrated into a first physical unit, and the memory 134 may be integrated into a second physical unit. Although in Figure 1 Although not shown, the controller 130 may include a power source such as a battery, etc. Although shown as separate elements, the positioning unit 131, the electronic communication unit 132, the processor 133, the memory 134, the user interface 135, the sensor 136, the electronic communication interface 137, or any combination thereof may be integrated into one or more electronic units, circuits, or chips.
[0032] The processor 133 may include any device or combination of devices that are currently available or subsequently developed and that can manipulate or process signals or other information, including an optical processor, a quantum processor, a molecular processor, or a combination thereof. For example, the processor 133 may include one or more dedicated processors, one or more digital signal processors, one or more microprocessors, one or more controllers, one or more microcontrollers, one or more integrated circuits, one or more dedicated integrated circuits, one or more field programmable gate arrays, one or more programmable logic arrays, one or more programmable logic controllers, one or more state machines, or any combination thereof. The processor 133 may be operably coupled to the positioning unit 131, the memory 134, the electronic communication interface 137, the electronic communication unit 132, the user interface 135, the sensor 136, the powertrain 120, or any combination thereof. For example, the processor may be operably coupled to the memory 134 via the communication bus 138.
[0033] The memory 134 may include any tangible, non-transitory computer-usable or computer-readable medium that can, for example, contain, store, communicate, or transport machine-readable instructions or any information associated therewith, for use by or in connection with the processor. The memory 134 may, for example, be one or more solid-state drives, one or more memory cards, one or more removable media, one or more read-only memories, one or more random access memories, one or more disks (including hard disks, floppy disks, optical disks), magnetic or optical cards, or any type of non-transitory media suitable for storing electronic information, or any combination thereof.
[0034] The communication interface 137 may be a wireless antenna as shown, a wired communication port, an optical communication port, or any other wired or wireless means capable of interacting with the wired or wireless electronic communication medium 150. Figure 1 The communication interface 137 is shown communicating via a single communication link, but the communication interface may be configured to communicate via multiple communication links. Figure 1 A single communication interface 137 is shown, but the vehicle may include any number of communication interfaces.
[0035] The communication unit 132 may be configured to send or receive signals via a wired or wireless electronic communication medium 150, such as via a communication interface 137 or the like. Figure 1 Although not explicitly shown, the communication unit 132 may be configured to transmit, receive, or both via any wired or wireless communication medium, such as radio frequency (RF), ultraviolet (UV), visible light, optical fiber, wireline, or a combination thereof. Figure 1 A single communication unit 132 and a single communication interface 137 are shown, but any number of communication units and any number of communication interfaces may be used. In some embodiments, the communication unit 132 may include a dedicated short range communication (DSRC) unit, an on-board unit (OBU), or a combination thereof.
[0036] The positioning unit 131 may determine geographic location information, such as the longitude, latitude, altitude, direction of travel, or speed of the vehicle 100. For example, the positioning unit may include a global positioning system (GPS) unit, such as a National Marine Electronics Association (NMEA) unit enabled with a wide area augmentation system (WAAS), a radio triangulation unit, or a combination thereof. The positioning unit 131 may be used to obtain information indicating, for example, the current heading of the vehicle 100, the current position of the vehicle 100 in two or three dimensions, the current angular orientation of the vehicle 100, or a combination thereof.
[0037] The user interface 135 may include any unit that can interact with a person, such as a virtual or physical keyboard, a touch pad, a display, a touch display, a head-up display (heads-up display), a virtual display, an augmented reality display, a tactile display, a feature tracking device (such as an eye tracking device, etc.), a speaker, a microphone, a camera, a sensor, a printer, or any combination thereof. As shown, the user interface 135 may be operably coupled to the processor 133, or operably coupled to any other element of the controller 130. Although shown as a single unit, the user interface 135 may include one or more than one physical unit. For example, the user interface 135 may include an audio interface for audio communication with a person and a touch display for visual and touch-based communication with a person. The user interface 135 may include multiple displays, such as physically separated multiple units, multiple definition parts in a single physical unit, or a combination thereof.
[0038] Sensors 136 may include one or more sensors (such as a sensor array, etc.) that may be operable to provide information that may be used to control the vehicle. Sensors 136 may provide information related to the current operating characteristics of the vehicle 100. Sensors 136 may include, for example, speed sensors, acceleration sensors, steering angle sensors, traction-related sensors, brake-related sensors, steering wheel position sensors, eye tracking sensors, seat position sensors, or any sensor or combination of sensors that are operable to report information related to certain aspects of the current dynamic situation of the vehicle 100.
[0039] Sensor 136 may include one or more sensors operable to obtain information about the physical environment surrounding vehicle 100. For example, one or more sensors may detect road geometry and features (such as lane lines, etc.) and obstacles (such as fixed obstacles, vehicles, and pedestrians, etc.). Sensor 136 may be or may include one or more cameras, laser sensing systems, infrared sensing systems, acoustic sensing systems, or any other suitable type of vehicle-mounted environment sensing device, or combination of devices, now known or subsequently developed. In some embodiments, sensor 136 and positioning unit 131 may be a combined unit.
[0040] Although not shown separately, the vehicle 100 may include a trajectory controller. For example, the controller 130 may include a trajectory controller. The trajectory controller is operable to obtain information describing the current state of the vehicle 100 and the route planned for the vehicle 100, and to determine and optimize the trajectory of the vehicle 100 based on the information. In some embodiments, the trajectory controller may output a signal operable to control the vehicle 100 so that the vehicle 100 follows the trajectory determined by the trajectory controller. For example, the output of the trajectory controller may be an optimized trajectory, which may be supplied to the powertrain 120, the wheel 140, or both. In some embodiments, the optimized trajectory may be a control input such as a set of steering angles, wherein each steering angle corresponds to a point in time or a position. In some embodiments, the optimized trajectory may be one or more than one path, route, curve, or a combination thereof.
[0041] One or more of the wheels 140 may be: a steering wheel that can be pivoted to a steering angle under the control of the steering unit 123; a propulsion wheel that can be twisted to propel the vehicle 100 under the control of the transmission 122; or a steering propulsion wheel that can steer and propel the vehicle 100.
[0042] The vehicle may include Figure 1 The units or elements explicitly shown in the (Bluetooth) module, frequency modulation (FM) radio unit, near field communication (NFC) module, liquid crystal display (LCD) display unit, organic light emitting diode (OLED) display unit, speaker or any combination thereof, etc.
[0043] The vehicle 100 may be an autonomous vehicle that is autonomously controlled to traverse a portion of a vehicle transportation network without direct human intervention. Figure 1 Although not shown separately, the autonomous vehicle may include an autonomous vehicle control unit that can perform autonomous vehicle routing, navigation, and control. The autonomous vehicle control unit may be integrated with other units of the vehicle. For example, controller 130 may include an autonomous vehicle control unit. The teachings herein are equally applicable to semi-autonomous vehicles.
[0044] The autonomous vehicle control unit may control or operate the vehicle 100 to traverse a portion of the vehicle transportation network based on current vehicle operating parameters. The autonomous vehicle control unit may control or operate the vehicle 100 to perform defined operations or maneuvers, such as parking the vehicle, etc. The autonomous vehicle control unit may generate a driving route from a starting point, such as the current location of the vehicle 100, to a destination based on vehicle information, environmental information, vehicle transportation network data representing the vehicle transportation network, or a combination thereof, and may control or operate the vehicle 100 to traverse the vehicle transportation network based on the route. For example, the autonomous vehicle control unit may output the driving route to a trajectory controller, and the trajectory controller may use the generated route to operate the vehicle 100 to travel from the starting point to the destination.
[0045] Figure 2 is a diagram of an example of a portion of a vehicle transportation and communication system that may implement aspects, features, and elements disclosed herein. The vehicle transportation and communication system 200 may include, for example, Figure 1 One or more vehicles 210 / 211 of the vehicle 100 shown, etc., can travel via one or more portions of one or more vehicle transportation networks 220 and can communicate via one or more electronic communication networks 230. Although in Figure 2 Although not explicitly shown, the vehicle may traverse areas that are not explicitly or fully included in the vehicle transportation network (such as off-road areas, etc.).
[0046] The electronic communication network 230 may be, for example, a multiple access system and may provide communications between the vehicles 210 / 211 and one or more communication devices 240, such as voice communications, data communications, video communications, messaging communications, or a combination thereof. For example, the vehicle 210 / 211 may receive information such as information representing the vehicle transportation network 220 from the communication device 240 via the network 230.
[0047] In some embodiments, the vehicle 210 / 211 can communicate via a wired communication link (not shown), a wireless communication link 231 / 232 / 237, or a combination of any number of wired or wireless communication links. For example, as shown, the vehicle 210 / 211 can communicate via a ground wireless communication link 231, via a non-ground wireless communication link 232, or via a combination thereof. The ground wireless communication link 231 may include an Ethernet link, a serial link, a Bluetooth link, an infrared (IR) link, a UV link, or any link capable of providing electronic communication.
[0048] The vehicle 210 / 211 can communicate with another vehicle 210 / 211. For example, the host vehicle or subject vehicle (HV) 210 can receive one or more automated inter-vehicle messages (such as basic safety messages (BSM)) from the remote or target vehicle (RV) 211 via a direct communication link 237 or via a network 230. For example, the remote vehicle 211 can broadcast the message to the host vehicle within a defined broadcast range (such as 300 meters, etc.). In some embodiments, the host vehicle 210 can receive the message via a third party such as a signal repeater (not shown) or other remote vehicles (not shown). The vehicle 210 / 211 can periodically send one or more automated inter-vehicle messages based on, for example, a defined interval (such as 100 milliseconds, etc.).
[0049] The automated inter-vehicle message may include vehicle identification information, geospatial state information (such as longitude, latitude, or altitude information, etc.), geospatial location accuracy information, kinematic state information (such as vehicle acceleration information, yaw rate information, speed information, vehicle heading information, brake system status information, throttle information, steering wheel angle information, etc.), or vehicle routing information, or vehicle operating state information (such as vehicle size information, headlight status information, turn signal information, wiper status information, transmission information, or any other information or combination of information related to shifting vehicle states, etc.). For example, the transmission state information may indicate whether the transmission that shifts the vehicle is in a neutral state, a parking state, a forward state, or a reverse state.
[0050] The vehicle 210 can communicate with the communication network 230 via an access point 233. The access point 233, which may include a computing device, can be configured to communicate with the vehicle 210, the communication network 230, one or more communication devices 240, or a combination thereof via a wired or wireless communication link 231 / 234. For example, the access point 233 can be a base station, a base transceiver station (BTS), a Node-B, an enhanced Node-B (eNode-B), a Home Node-B (HNode-B), a wireless router, a wired router, a hub, a repeater, a switch, or any similar wired or wireless device. Although in Figure 2 Although shown as a single unit, an access point may include any number of interconnected elements.
[0051] Vehicle 210 may communicate with communication network 230 via satellite 235 or other non-terrestrial communication means. Satellite 235, which may include a computing device, may be configured to communicate with vehicle 210, with communication network 230, with one or more communication devices 240, or a combination thereof via one or more communication links 232 / 236. Figure 2 Although shown as a single unit, a satellite may include any number of interconnected elements.
[0052] The electronic communications network 230 may be any type of network configured to provide voice communications, data communications, or any other type of electronic communications. For example, the electronic communications network 230 may include a local area network (LAN), a wide area network (WAN), a virtual private network (VPN), a mobile or cellular telephone network, the Internet, or any other electronic communications system. The electronic communications network 230 may use communications protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), the Internet Protocol (IP), the Real-time Transport Protocol (RTP), the Hypertext Transfer Protocol (HTTP), or a combination thereof. Although in Figure 2 Although shown as a single unit in FIG, the electronic communications network may include any number of interconnected elements.
[0053] The vehicle 210 can identify a portion or condition of the vehicle transportation network 220. For example, the vehicle 210 can include one or more onboard sensors (such as Figure 1 The one or more onboard sensors may include a speed sensor, a wheel speed sensor, a camera, a gyroscope, an optical sensor, a laser sensor, a radar sensor, an acoustic sensor, or any other sensor or device or combination thereof capable of determining or identifying a portion or condition of the vehicle transportation network 220. The sensor data may include lane data, remote vehicle location data, or both.
[0054] Vehicles 210 may traverse one or more portions of one or more vehicle transportation networks 220 using information communicated via network 230, such as information representative of vehicle transportation network 220, information identified by one or more onboard sensors, or a combination thereof.
[0055] Although for simplicity, Figure 2 Two vehicles 210, 211, a vehicle transport network 220, an electronic communications network 230, and a communications device 240 are shown, but any number of vehicles, networks, or computing devices may be used. The vehicle transport and communications system 200 may include Figure 2Although vehicle 210 is shown as a single unit, the vehicle may include any number of interconnected elements.
[0056] Although vehicle 210 is shown communicating with communication device 240 via network 230, vehicle 210 may communicate with communication device 240 via any number of direct or indirect communication links. For example, vehicle 210 may communicate with communication device 240 via a direct communication link such as a Bluetooth communication link.
[0057] In some embodiments, the vehicle 210 / 211 may be associated with an entity 250 / 260, such as a driver, operator, or owner of the vehicle. In some embodiments, the entity 250 / 260 associated with the vehicle 210 / 211 may be associated with one or more personal electronic devices 252 / 254 / 262 / 264, such as a smart phone 252 / 262 or a computer 254 / 264. In some embodiments, the personal electronic devices 252 / 254 / 262 / 264 may communicate with the respective vehicle 210 / 211 via a direct or indirect communication link. Although in Figure 2 One entity 250 / 260 is shown in FIG. 2 as being associated with a corresponding vehicle 210 / 211, but any number of vehicles may be associated with an entity, and any number of entities may be associated with a vehicle.
[0058] The vehicle transportation network 220 only shows navigable areas (e.g., roads), but the vehicle transportation network may also include one or more non-navigable areas (such as buildings, etc.), one or more partially navigable areas (such as parking areas or sidewalks), or a combination thereof. The vehicle transportation network 220 may also include one or more grade separations between one or more navigable or partially navigable areas. A portion of the vehicle transportation network 220 (such as a road, etc.) may include one or more lanes and may be associated with one or more directions of travel.
[0059] The vehicle transportation network or a portion thereof may be represented as vehicle transportation network data. For example, the vehicle transportation network data may be expressed as a hierarchy of elements (such as markup language elements, etc.), which may be stored in a database or file. For simplicity, the accompanying drawings herein depict vehicle transportation network data representing a portion of the vehicle transportation network as a graph or map; however, the vehicle transportation network data may be expressed in any computer-usable form capable of representing the vehicle transportation network or a portion thereof. The vehicle transportation network data may include vehicle transportation network control information, such as driving direction information, speed limit information, toll information, slope information (such as inclination or angle information, etc.), surface material information, aesthetic information, defined hazard information, or a combination thereof.
[0060] A portion or combination of portions of the vehicle transportation network 220 may be identified as a point of interest or a destination. For example, the vehicle transportation network data may identify a building as a point of interest or a destination. A point of interest or a destination may be identified using a discrete uniquely identifiable geographic location. For example, the vehicle transportation network 220 may include a defined location for a destination, such as a street address, a postal address, a vehicle transportation network address, a GPS address, or a combination thereof.
[0061] Figure 3 is a data flow diagram of a technique 300 for generating control signals using vehicle data according to an embodiment of the present disclosure.
[0062] As shown, a networked vehicle (CV) 302 transmits vehicle data 304 to a long-term shared world model 306. Although a single CV 302 is illustrated, multiple CVs including the CV 302 may transmit vehicle data 304 to the long-term shared world model 306. The vehicle data 304 may include at least one of location data, speed data, and headway (e.g., following distance) data. The vehicle data 304 may relate to the CV or other vehicles approaching the CV. Although the vehicle data 304 is shown as being transmitted from the CV 302, all or a portion of the vehicle data may be transmitted from a road sensor (e.g., a radar, lidar, or computer vision-based sensor). The vehicle data 304 is used to generate or modify the long-term shared world model 306. The long-term shared world model 306 stores historical traffic speed, congestion, and / or headway data related to multiple road segments, and may be used to predict future traffic speed, congestion, and / or headway data for all or a portion of the multiple road segments. As shown, the prediction engine 308 accesses the long-term shared world model 306 to make predictions regarding future traffic speed, congestion, and / or headway data for the road segment. The predictions are stored in a prediction data structure 310. A control signal 312 is generated based on the prediction data structure 310 and transmitted to a networked automated vehicle (CAV) 314. The control signal 312 controls the speed or travel path of the CAV 314.
[0063] Location data may represent the geographic location of a vehicle. For example, location data may indicate the latitude and longitude of a vehicle, a street address of a vehicle, or other identifier of a geographic location. Location data may be obtained using road sensors at the vehicle, using global positioning system (GPS) technology, and / or using cellular tower triangulation. Speed data represents the speed and direction of travel of a vehicle. Speed data may include measurements in units of speed (e.g., kilometers per hour) and direction (e.g., north by east n degrees, where n is a number). Headway data represents the distance between the front end of a vehicle and the front end (or alternatively, the rear end) of another vehicle that the vehicle is following. Headway data may be measured in units of distance (e.g., meters).
[0064] CV 302 and / or CAV 314 may correspond to one or more than one of vehicles 100, 210, 211. Long-term shared world model 306, prediction engine 308, and / or prediction data structure 310 may be implemented using software and / or hardware residing at a server connected to vehicle transportation network 220 and / or electronic communication network 230. For example, long-term shared world model 306, prediction engine 308, and / or prediction data structure 310 may be implemented using software and / or hardware residing at communication device 240.
[0065] According to some implementations, the long-term shared world model 306 accesses and stores vehicle data 304 from the CV 302. The prediction engine 308 generates a prediction data structure 310 using the long-term shared world model 306 by applying a traffic flow model to the long-term shared world model 306, and the prediction data structure 310 represents the predicted future speed on the road portion by location and time. The traffic flow model is based on at least one of the following: the average vehicle speed in at least one road segment during the time slice, the vehicle density in at least one road segment during the time slice, and the flow or net flow of vehicles entering or leaving at least one road segment during the time slice. A control signal 312 is generated based on the prediction data structure 310, and the control signal 312 is transmitted to the CAV 314 to control its operation (e.g., speed or travel path). The term "time slice" can include a continuous time period (e.g., the time period between 4:00 p.m. and 4:02 p.m. on February 1, 2022), etc.
[0066] Figure 4 4 is a data flow diagram of a long-term shared world model architecture 400 according to an embodiment of the present disclosure. As shown, a vehicle 402 provides vehicle data (e.g., GPS data) to a delivery engine 404. The delivery engine 404 delivers the vehicle data 406 to a positioning engine 408. The positioning engine 408 calculates the position, velocity, and headway 410 of the vehicle and provides the position, velocity, and headway 410 to an estimation engine 412. The estimation engine 412 estimates flow, density, and velocity 414 and provides the data to the delivery engine 404 and the vehicle 402 for use in controlling the vehicle (e.g., by an autonomous driving engine or by a human driver).
[0067] Some implementations involve reducing traffic congestion. The long-term shared world model 306, 400 may include a traffic state estimator that collects and aggregates data from probe vehicles throughout the network to produce a meaningful macro prediction of the state and evolution of traffic. This information is maintained in a database (or other data storage unit) and provided to the control strategy at a later stage to help improve the decision-making and coordination of CVs and CAVs.
[0068] The transmission engine 404 aggregates data from the vehicle 402 (which may be a CV or CAV) into vehicle data 406, and in some cases aggregates data from other vehicles into a shared data repository that is stored on a network and accessible in real time. The transmission engine 404 may collect GPS, controller area network (CAN), and other available data sources from the vehicle 402, and may transmit this data to a server. The transmission engine 404 also stores data that may be accessed by the vehicle 402. The structure of the available shared repository may be optimized to reduce the overhead associated with storing and accessing individual vehicle data points.
[0069] Positioning engine 408 extracts and processes relevant information from vehicle data 406. Vehicle data 406 may be collected from a shared data repository. Positioning engine 408 may perform filtering operations to reduce noise. Information collected by positioning engine 408 for each vehicle i at time t may include the information shown in Table 1.
[0070] Table 1
[0071] x i (t): position of vehicle i (relative to some fixed reference point)
[0072] v i (t): speed of vehicle i
[0073] h i (t): The headway distance between vehicle i and the vehicle ahead of vehicle i (front bumper to front bumper)
[0074] v i,lead (t): speed of the leading vehicle in the same lane as vehicle i
[0075] v L i,lead (t): speed of the leading vehicle in the lane to the left of vehicle i
[0076] h L i,lead (t): Headway between leading vehicles in the lane to the left of vehicle i
[0077] v L i,follow (t): speed of the following vehicle in the lane to the left of vehicle i
[0078] h L i,follow (t): Headway between vehicles following vehicle i in the lane to the left
[0079] v R i,lead (t): speed of the leading vehicle in the lane to the right of vehicle i
[0080] h R i,lead (t): Headway between leading vehicles in the lane to the right of vehicle i
[0081] v R i,follow (t): speed of the following vehicle in the lane to the right of vehicle i
[0082] h R i,follow (t): Headway between vehicles following vehicle i in the lane to the right of vehicle i
[0083] The estimation engine 412 collects the information stored by the transmission engine 404 and modified by the positioning engine 408 (e.g., position, speed, and headway 410), and uses this information to approximate the macroscopic state of traffic at different road segments. In particular, consider a road segment of length L and total time T seconds. N and M are integers. The estimation engine 412 takes N steps J of length Δt=T / N. j (0<=j<=N) and M spatial units I with length Δx=L / M i (0<=i<=M) is used to discretize time and space, and the metrics shown in Table 2 are calculated for each spatiotemporal region.
[0084] Table 2
[0085] v i j : The average speed of vehicles on road segment i in time interval j
[0086] ρ i j : Vehicle density of road segment i at time interval j
[0087] q i j : The flow of vehicles from road segment i to road segment i+1 at time interval j
[0088] The information calculated by the estimation engine 412 (flow, density, and speed 414 ) is provided to the delivery engine 404 for storage in a data repository or for use by a vehicle (eg, vehicle 402 ) in communication with the delivery engine 404 .
[0089] One advantage of the architecture 400 is the flexibility provided by the modularity of the different subcomponents. This allows some implementations to generalize various features to multiple different vehicles and estimation algorithms. For example, if multiple vehicles with different sensing / communication specifications are utilized, the errors associated with each type of vehicle can be accommodated by utilizing a different positioning module for each vehicle type while keeping all other modules static. In addition, if penetration effects or other specifications require the use of a different estimated traffic state estimation algorithm, the algorithm can simply be replaced without modifying anything else.
[0090] The data repository in the transmission engine 404 can be a database (e.g., SQL, MongoDB, etc.) or other data storage unit. The type of information shared between the vehicles (e.g., vehicle 402) accessing the transmission engine 404 can depend on the sensors available on the vehicle. The positioning engine 408 can use different filtering techniques to access and process historical data. The estimation engine 412 can utilize different traffic state estimators. For example, when less than a threshold amount of data is available, a statistical or data-driven estimator can be used to produce a moderately granular result. When more than a threshold amount of data is available, a model-based estimator (e.g., an AI or ML estimator) can be used to produce a more fine-grained estimate.
[0091] In order to enable CVs and CAVs to efficiently collaborate and regulate traffic flow, a long-term shared world model 306 (or other shared models of traffic state) may be used. Traffic state estimation algorithms may provide techniques for defining such models. Some techniques convert local vehicle sensor data (vehicle position, headway, and speed) into quantities that can define shared states between vehicles in spatial and temporal regions (e.g., one or more road sections). Due to limitations of sensing infrastructure, etc., some techniques rely on sparse amounts of data. The rise of vehicle automation has greatly improved the quality of onboard vehicle sensing, producing vehicles that can sense not only what is happening in front of the vehicle, but also what is happening in adjacent lanes. Some implementations take advantage of improvements that have occurred in sensing infrastructure and define the following process, by which these additional observations can be used to improve the quality of existing traffic state estimation methods.
[0092] Some implementations involve replicating the Edie flow from the perspective of the probe vehicle. However, the estimator utilized (for replicating the Edie flow) may be prone to error. Errors in the estimate may come from biases in the sample (probe) vehicle data. In some cases, some vehicles may be driving faster or slower (or have longer or shorter headways) than other vehicles, and additional corrections may be used to produce more accurate results. In some implementations, for a spatiotemporal region (e.g., a road portion, a road segment, multiple road portions, or multiple road segments) A corresponding to a spatial interval i and a time interval j, the error in the estimate may be due to biases in the sample (probe) vehicle data. In some cases, some vehicles may be driving faster or slower (or have longer or shorter headways) than other vehicles, and additional corrections may be used to produce more accurate results. i j , r1 may be a speed correction factor, and r2 may be a headway correction factor. The relationship between the actual traffic state and the estimated traffic state may be:
[0093]
[0094] In the above formula, q i j and q_hat i j are the true and predicted mean flows in spatial interval i and time interval j, respectively; v i j and v_hat i j are the true and predicted average velocities in spatial interval i and time interval j, respectively; ρ i j and ρ_hat i j are the true and predicted mean densities in spatial interval i and time interval j, respectively.
[0095] Some implementations involve defining values for r1 and r2. The true values of r1 and r2 may depend on global state information, which may be unknown. To estimate the values of r1 and r2, some implementations rely on data from lanes adjacent to the lane of the detection vehicle and data from the lane of the detection vehicle. Some implementations collect data related to speed (e.g., in units of distance divided by time) and headway (e.g., in units of distance) from adjacent lanes and the detection lane. For example, the data shown in Table 1 may be collected. After collecting the data, r1 and r2 may be calculated as follows:
[0096]
[0097] In the above formula, t i,j n is the vehicle n in area A i jThe addition of 0.5 to the speed correction is intended to balance the influence of each lane on the cumulative estimate. It should be noted that whenever only a subset of the above data is available, this value is ignored and the average is performed over the smaller subset.
[0098] Figure 5 Flow graphs in space and time are illustrated. Plot 502 depicts a space-time region, and plot 504 depicts data used in the prediction techniques disclosed herein. Figure 6 Speed and headway values 600 measured for a probe vehicle 602 are illustrated.
[0099] This correction can be important in many situations because variations between driving behaviors between lanes can reduce the accuracy of the estimates generated. Examples of situations where this concern may arise include the presence of a truck downstream in one lane (e.g., which is larger and moves slower than a passenger vehicle), or the presence of a high occupancy vehicle (HOV) or other fast-moving lane not used by the detected vehicle. Some implementations can mitigate the impact of lane-level features on the returned estimates by sensing and correcting for the behavior of vehicles in adjacent lanes.
[0100] In some implementations, correction factors r1 and r2 can be calculated based on local real-time sensor data. Some implementations include Bayesian priors for modeling lane-level dynamic distributions to improve accuracy in the presence of sparse data. Some implementations express correction values for flow and density as a function of the offset of the mean speed. This is relevant when neither the leading vehicle nor the following vehicle in the adjacent lane can be found, thereby presenting a quantification of the headway. For example, defining the form of the flow-density relationship using a triangular base graph and calibrating a model of the relationship can help produce approximate values for the correction factors r1 and r2.
[0101] Figure 7 700 is a data flow diagram for traffic state determination according to an embodiment of the present disclosure. Figure 7As shown, CV 702 (e.g., corresponding to CV 302) provides speed data 704 and headway data 706 (e.g., all or part of the speed data and headway data listed in Table 1) to vehicle control server 708. Vehicle control server 708 calculates speed correction factor 710 (r1) and headway correction factor 712 (r2). Prediction engine 714 (e.g., corresponding to prediction engine 308) accesses speed data 704 and headway data 706 and predicts (e.g., using artificial intelligence, machine learning and / or mathematical formulas) future flow 716, future average speed 718, and future density 720 for at least one road segment or road portion. The predicted future flow 716, future average speed 718, and future density 720 are provided to adjustment engine 722 of vehicle control server 708 along with the calculated speed correction factor 710 and headway connection factor 712. The adjustment engine adjusts the predicted future flow 716, the future average speed 718, and the future density 720, and provides an output based on the adjustment to the control signal generator 724. The control signal generator 724 generates a control signal 726 for controlling a CAV 728 (e.g., corresponding to the CAV 314), and provides the control signal 726 to the CAV 728. The CAV 728 adjusts the operation (e.g., speed or travel path) of the CAV 728 in response to the control signal 726.
[0102] Traffic congestion increases fuel consumption and greenhouse gas emissions while reducing driving comfort and driving safety. Technologies that use connected and / or automated vehicle technologies to reduce traffic congestion may be desirable.
[0103] In some implementations, a portion of the vehicles are connected vehicles (vehicles that can share information to the cloud but are manually driven by human drivers), a portion of the vehicles are connected and automated vehicles (vehicles that can share information and are automatically controlled by the cloud), and a portion of the vehicles are human-driven vehicles that are neither connected nor automated (do not have connectivity to the cloud). CVs and CAVs can share traffic-related measurements using onboard sensors with the cloud (including vehicle speed, acceleration, relative distance and relative speed to surrounding vehicles, etc.).
[0104] Figure 8An example vehicle communication and control architecture 800 is illustrated. As shown, the vehicle communication and control architecture 800 includes a non-networked vehicle 802, a CV 804, a CAV 806, and a roadside unit (RSU) 808 on a road portion 810. The non-networked vehicle 802 may be a conventional vehicle operated by a human driver and may not be able to transmit traffic state information (e.g., speed information, driving path information, or information obtained by onboard sensors, etc.) to a network. The RSU 808 may include a router for transmitting network communications to and receiving network communications from the CV 804 and CAV 806. The RSU 808 may include a road sensor (e.g., a camera system, a radar system, or a lidar system). As shown, the CV 804, the CAV 806, and the RSU 808 communicate status and perception data 812 for generating a long-term shared world model 814. The long-term shared world model 814 may correspond to the long-term shared world model 306. As shown, the long-term shared world model 814 is accessed by a cooperative multi-vehicle strategy selector 816. The cooperative multi-vehicle strategy selector 816 transmits control signals 818 to the CAV 806. The control signals 818 are coordinated and optimized to achieve traffic control goals, such as reducing traffic inflow 820 or reducing stop-and-go traffic 822 at various portions of the road portion 810. As shown, the long-term shared world model 814 and the cooperative multi-vehicle strategy selector 816 are stored on a network 824, such as at a server or data repository connected to the network 824.
[0105] According to some implementations, an engine of the network 824 (e.g., the long-term shared world model 814 or the cooperative multi-vehicle strategy selector 816) receives information from and sends information to the CV 804 and / or CAV 806 via wireless communications. The situation and perception data 812 from the CV 804 and / or CAV 806 is processed and then control signals 818 are sent to the CAV 806.
[0106] The long-term shared world model 814 is a real-time and accurate model of the traffic state based on the situation and perception data 812 from the CVs 804 and CAVs 806. The long-term shared world model 814 is used to provide the cooperative multi-vehicle strategy selector 816 with the information needed to generate control signals 818 for the CAVs 806. The data from the long-term shared world model 814 can be used in two ways: to share traffic conditions directly with the CAVs 806 to allow individual CAVs 806 to adapt to traffic conditions using their onboard computers, or to enable the cooperative multi-vehicle strategy selector 816 to determine the optimal actions for the CAVs 806 based on macro metrics (e.g., network throughput, traffic rate changes, or greenhouse gas emissions, etc.). The optimal actions for individual CAVs 806 are communicated from the cooperative multi-vehicle strategy selector 816 to the associated CAVs 806 using control signals 818. By coordinating the driving behaviors of the CAV 806, traffic flow may be more efficiently controlled and optimized, traffic influx may be reduced in road areas, and / or stop-and-go traffic may be reduced.
[0107] Fig. 9 900 is a data flow diagram for vehicle communication and control 900 according to an embodiment of the present disclosure. As shown, CV 902 generates traffic state information 904 and provides traffic state information 904 to long-term shared world model 906. CV 902 may correspond to one of CVs 804 or one of CAVs 806. Traffic state information 904 may correspond to condition and perception data 812 or other information generated by CV 902 or available at CV 902. Long-term shared world model 906 may correspond to at least one of long-term shared world models 306, 814.
[0108] As shown, the long-term shared world model 906 communicates data to a multi-vehicle strategy selector 908 (e.g., the collaborative multi-vehicle strategy selector 816). The multi-vehicle strategy selector 908 utilizes an optimization engine 910 to optimize traffic conditions (e.g., reduce traffic inflow into high traffic areas and / or reduce stop-and-go traffic) to generate a control signal 912 (e.g., from the control signal 818) for a CAV 914 (e.g., one of the CAVs 806). The multi-vehicle strategy selector 908 transmits the control signal 912 to the CAV 914. The CAV 914 adjusts its operation (e.g., its speed or its travel path) based on the control signal 912.
[0109] Fig.101 is a flow chart of a method 1000 for operating a vehicle using a long-term shared world model according to an embodiment of the present disclosure. A server may be used to implement the method 1000. The server may include a server connected to the vehicle transportation network 220 and / or the electronic communication network 230. The server may include a single computing device or multiple computing devices working together.
[0110] At box 1002, the server accesses vehicle data of each CV in a subset of multiple CVs on the road portion. The vehicle data may include at least one of position, speed, and headway. The server may also access additional data from road sensors. The additional data may include vehicle position data, vehicle speed data, and / or vehicle headway data. Additional data may be sensed at the road sensor using computer vision, radar, and / or lidar. The vehicle data may be associated with other vehicles (e.g., other CVs or non-networked vehicles) whose data near the CV may be accessed by the onboard sensors of the CV. Additional data may be associated with a CV or a non-networked vehicle.
[0111] At box 1004, the server generates a long-term shared world model (e.g., one of long-term shared world models 306, 814, 906) based on the accessed vehicle data and / or additional data. In some cases, the accessed vehicle data is received from a first vehicle and includes a position, speed, or headway of a second vehicle. The first vehicle is different from the second vehicle. For example, the second vehicle may be traveling immediately in front of the first vehicle, immediately behind the first vehicle, or in a driving lane adjacent to the driving lane of the first vehicle.
[0112] At block 1006, the server generates a data structure using the long-term shared world model by applying the traffic flow model to the long-term shared world model, the data structure representing the predicted future speed on the road portion by location and time. For example, the data structure can be a two-dimensional array with one dimension representing the road segment and another dimension representing the time slice. The value in each cell of the two-dimensional array can represent the predicted future speed for the corresponding road segment and time slice.
[0113] According to some implementations, the road portion is subdivided into a plurality of road segments. The traffic flow model is based on at least one of an average vehicle speed in at least one road segment during a time slice, a vehicle density in at least one road segment during a time slice, and a flow or net flow of vehicles entering or leaving at least one road segment during a time slice. The average vehicle speed, vehicle density, flow or net flow may be calculated using a long-term shared world model.
[0114] At block 1008, the server transmits a control signal to the CAV for controlling the operation of the CAV based on the generated data structure. The CAV may adjust its operation based on the control signal. For example, the CAV may adjust its speed or its driving path based on the control signal.
[0115] Fig.11 1 is a flow chart of a method 1100 for predicting future traffic data according to an embodiment of the present disclosure. The server may include a vehicle control server 708 or a server connected to the vehicle transportation network 220 and / or the electronic communication network 230. The server may include a single computing device or multiple computing devices working together.
[0116] At block 1102, the server receives speed data from the CV representing the speed of the CV and additional vehicles approaching the CV. The server calculates a speed correction factor based on the speed data, for example, using Equation 4 above. The additional vehicles approaching the CAV may include a vehicle in front of the CV in a lane adjacent to the CV or a vehicle behind the CV in a lane adjacent to the CV.
[0117] At block 1104, the server receives headway data from the CV representing the headway between the CV and an additional vehicle proximate to the CV. The server calculates a headway correction factor based on the headway data, for example using Equation 5 above. In some implementations, the server receives speed data and headway data from a plurality of CVs including the CV. The speed correction factor is calculated based on the speed data from the plurality of CVs. The headway correction factor is calculated based on the headway data from the plurality of CVs.
[0118] At block 1106, the server determines the future flow, future average speed, and future density for the segment of the road using a prediction engine at the server. In some implementations, the prediction engine utilizes a long-term shared world model (e.g., one of the long-term shared world models 306, 814, 906) that stores data received from a plurality of CVs and a plurality of road sensors.
[0119] At box 1108, the server adjusts the determined future flow based on the speed correction factor and the headway correction factor. The server adjusts the determined future average speed based on the speed correction factor. The server adjusts the determined future density based on the headway correction factor. Adjusting the determined future flow based on the speed correction factor and the headway correction factor may include multiplying the determined future flow by a quotient of the speed correction factor and the headway correction factor. Adjusting the determined future average speed based on the speed correction factor may include multiplying the determined future average speed by the speed correction factor. Adjusting the determined future density based on the headway correction factor may include dividing the determined future density by the headway correction factor.
[0120] According to some implementations, the server generates a control signal for the CAV based on at least one of: the determined future flow, the determined future average speed, and the determined future density. The server transmits the generated control signal to the CAV.
[0121] Fig.12 1 is a flow chart of a method 1200 for controlling a vehicle using a multi-vehicle strategy selector according to an embodiment of the present disclosure. A server may be used to implement the method 1200. The server may include a server connected to the vehicle transportation network 220 and / or the electronic communication network 230. The server may include a single computing device or multiple computing devices working together.
[0122] At box 1202, the server receives traffic status information from road sensors, CVs and CAVs. The traffic status information may include at least one of the location of a vehicle, the speed of a vehicle, the following distance between a vehicle and another vehicle, and the number of vehicles on a road portion. The vehicle may be a non-networked vehicle, a CV or a CAV. For a non-networked vehicle, the traffic status information may be determined (and transmitted to the server) by at least one of a road sensor, a CV and a CAV approaching the non-networked vehicle. CVs, CAVs and / or non-networked vehicles may be traveling on a road portion. Alternatively, CVs, CAVs and / or non-networked vehicles may include vehicles that are not traveling on a road portion (e.g., vehicles approaching a road portion or vehicles that have recently left a road portion).
[0123] At block 1204, the server generates a long-term shared world model (e.g., one of the long-term shared world models 306, 814, 906) based on the received traffic state information. The long-term shared world model may use any modeling technique. For example, the long-term shared world model may use statistical modeling, machine learning, or artificial intelligence techniques.
[0124] At block 1206, the server generates control signals to control the CAVs based on the long-term shared world model using a multi-vehicle strategy selector (e.g., multi-vehicle strategy selector 908). The multi-vehicle strategy selector generates the control signals using an optimization to reduce congestion on the road portion. Each control signal is transmitted to an associated CAV and controls a speed or travel path of the associated CAV. The optimization to reduce congestion on the road includes at least ensuring a minimum threshold following distance between each CAV and a vehicle ahead of the CAV.
[0125] Some implementations are described below as numbered examples (Example 1, 2, 3, etc.) These examples are provided as examples only and do not limit other implementations disclosed herein.
[0126] Example 1 is a method for generating a control signal and transmitting the control signal to a vehicle, the method comprising: accessing vehicle data from each CV in a subset of a plurality of networked vehicles, i.e., a plurality of CVs, on a road portion, the vehicle data comprising at least one of position, speed, and headway; generating a long-term shared world model based on the accessed vehicle data; generating a data structure using the long-term shared world model by applying a traffic flow model to the long-term shared world model, the data structure representing a predicted future speed on the road portion by position and time; and transmitting a control signal to a networked autonomous vehicle, i.e., a CAV, for controlling the operation of the CAV based on the generated data structure.
[0127] In Example 2, the subject matter of Example 1 includes: accessing additional data from road sensors, the additional data including at least one of vehicle position data, vehicle speed data, and vehicle headway data; and storing the accessed additional data in the long-term shared world model.
[0128] In Example 3, the subject matter of Examples 1-2 includes, wherein the vehicle position data, the vehicle speed data, or the vehicle headway data is associated with a non-networked vehicle.
[0129] In Example 4, the subject matter of Examples 1 to 3 includes, wherein the road portion is subdivided into a plurality of road segments, wherein the traffic flow model is based on at least one of: an average vehicle speed in at least one road segment during a time slice, a vehicle density in the at least one road segment during the time slice, and a flow or net flow of vehicles entering or leaving the at least one road segment during the time slice.
[0130] In Example 5, the subject matter of Example 4 includes, wherein the average vehicle speed, the vehicle density, the flow, or the net flow is calculated using the long term shared world model.
[0131] In Example 6, the subject matter of Examples 1-5 includes, wherein the accessed vehicle data is received from a first vehicle and includes a position, speed, or headway of a second vehicle, wherein the first vehicle is different than the second vehicle.
[0132] In Example 7, the subject matter of Example 6 includes wherein the second vehicle is traveling immediately in front of the first vehicle, immediately behind the first vehicle, or in a driving lane adjacent to a driving lane of the first vehicle.
[0133] Example 8 is a device for generating a control signal and transmitting the control signal to a vehicle, the device comprising: a memory storing instructions; and a processor for executing the stored instructions to: access vehicle data from each CV in a subset of a plurality of networked vehicles, i.e., a plurality of CVs, on a road portion, the vehicle data comprising at least one of position, speed, and headway; generate a long-term shared world model based on the accessed vehicle data; generate a data structure by applying a traffic flow model to the long-term shared world model and using the long-term shared world model, the data structure representing a predicted future speed on the road portion by position and time; and transmit a control signal to a networked autonomous vehicle, i.e., a CAV, for controlling the operation of the CAV based on the generated data structure.
[0134] In Example 9, the subject matter of Example 8 includes the processor executing the stored instructions to: access additional data from road sensors, the additional data including at least one of vehicle position data, vehicle speed data, and vehicle headway data; and store the accessed additional data in the long-term shared world model.
[0135] In Example 10, the subject matter of Examples 8-9 includes, wherein the vehicle position data, the vehicle speed data, or the vehicle headway data is associated with a non-networked vehicle.
[0136] In Example 11, the subject matter of Examples 8 to 10 includes, wherein the road portion is subdivided into a plurality of road segments, wherein the traffic flow model is based on at least one of: an average vehicle speed in at least one road segment during a time slice, a vehicle density in the at least one road segment during the time slice, and a flow or net flow of vehicles entering or leaving the at least one road segment during the time slice.
[0137] In Example 12, the subject matter of Example 11 includes, wherein the average vehicle speed, the vehicle density, the flow, or the net flow is calculated using the long term shared world model.
[0138] In Example 13, the subject matter of Examples 8 to 12 includes, wherein the accessed vehicle data is received from a first vehicle and includes a position, speed, or headway of a second vehicle, wherein the first vehicle is different than the second vehicle.
[0139] In Example 14, the subject matter of Example 13 includes wherein the second vehicle is traveling immediately in front of the first vehicle, immediately behind the first vehicle, or in a driving lane adjacent to a driving lane of the first vehicle.
[0140] Example 15 is a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: accessing vehicle data from a plurality of networked vehicles, i.e., each CV in a subset of a plurality of CVs, on a road portion, the vehicle data including at least one of position, speed, and headway; generating a long-term shared world model based on the accessed vehicle data; generating a data structure using the long-term shared world model by applying a traffic flow model to the long-term shared world model, the data structure representing predicted future speeds on the road portion by position and time; and transmitting a control signal to a networked autonomous vehicle, i.e., a CAV, for controlling the operation of the CAV based on the generated data structure.
[0141] In Example 16, the subject matter of Example 15 includes that the operation further includes: accessing additional data from road sensors, the additional data including at least one of vehicle position data, vehicle speed data, and vehicle headway data; and storing the accessed additional data in the long-term shared world model.
[0142] In Example 17, the subject matter of Examples 15-16 includes, wherein the vehicle position data, the vehicle speed data, or the vehicle headway data is associated with a non-networked vehicle.
[0143] In Example 18, the subject matter of Examples 15 to 17 includes, wherein the road portion is subdivided into a plurality of road segments, wherein the traffic flow model is based on at least one of: an average vehicle speed in at least one road segment during a time slice, a vehicle density in the at least one road segment during the time slice, and a flow or net flow of vehicles entering or leaving the at least one road segment during the time slice.
[0144] In Example 19, the subject matter of Example 18 includes, wherein the average vehicle speed, the vehicle density, the flow, or the net flow is calculated using the long term shared world model.
[0145] In Example 20, the subject matter of Examples 15 to 19 includes, wherein the accessed vehicle data is received from a first vehicle and includes a position, speed, or headway of a second vehicle, wherein the first vehicle is different than the second vehicle.
[0146] Example 21 is a method comprising: receiving speed data representing the speed of a networked vehicle, i.e., a CV, at a control server and from the CV; calculating a speed correction factor based on the speed data; receiving headway data representing the headway between the CV and the additional vehicles approaching the CV at the control server and from the CV; calculating a headway correction factor based on the headway data; using a prediction engine at the control server to determine a future flow, a future average speed, and a future density for a segment of a road; adjusting the determined future flow based on the speed correction factor and the headway correction factor; adjusting the determined future average speed based on the speed correction factor; adjusting the determined future density based on the headway correction factor; generating a control signal for a networked automated vehicle, i.e., a CAV, at the control server based on at least one of the determined future flow, the determined future average speed, and the determined future density; and transmitting the generated control signal to the CAV.
[0147] In Example 22, the subject matter of Example 21 includes, wherein the additional vehicles approaching the CV include at least one of: a vehicle in front of the CV in a lane adjacent to the CV, and a vehicle behind the CV in a lane adjacent to the CV.
[0148] In Example 23, the subject matter of Examples 21 to 22 includes, wherein the control server receives the speed data and the headway data from a plurality of CVs including the CV, wherein the speed correction factor is calculated based on the speed data from the plurality of CVs, and wherein the headway correction factor is calculated based on the headway data from the plurality of CVs.
[0149] In Example 24, the subject matter of Examples 21 to 23 includes, wherein the prediction engine utilizes a long-term shared world model that stores data received from the plurality of CVs and the plurality of road sensors.
[0150] In Example 25, the subject matter of Examples 21 to 24 includes, wherein adjusting the determined future flow based on the speed correction factor and the headway correction factor comprises: multiplying the determined future flow by a quotient of the speed correction factor and the headway correction factor.
[0151] In Example 26, the subject matter of Examples 21 to 25 includes, wherein adjusting the determined future average speed based on the speed correction factor includes multiplying the determined future average speed by the speed correction factor.
[0152] In Example 27, the subject matter of Examples 21 to 26 includes, wherein adjusting the determined future density based on the headway correction factor comprises dividing the determined future density by the headway correction factor.
[0153] Example 28 is a device comprising: a memory storing instructions; and a processor for executing the stored instructions to: receive speed data representing the speed of a networked vehicle, i.e., a CV, at a control server and from the CV; calculate a speed correction factor based on the speed data; receive headway data representing the headway between the CV and the additional vehicles approaching the CV at the control server and from the CV; calculate the headway correction factor based on the headway data; use a prediction engine at the control server to determine a future flow, a future average speed, and a future density for a segment of a road; adjust the determined future flow based on the speed correction factor and the headway correction factor; adjust the determined future average speed based on the speed correction factor; adjust the determined future density based on the headway correction factor; generate a control signal for a networked automated vehicle, i.e., a CAV, at the control server based on at least one of the determined future flow, the determined future average speed, and the determined future density; and transmit the generated control signal to the CAV.
[0154] In Example 29, the subject matter of Example 28 includes, wherein the additional vehicles approaching the CV include at least one of: a vehicle in front of the CV in a lane adjacent to the CV, and a vehicle behind the CV in a lane adjacent to the CV.
[0155] In Example 30, the subject matter of Examples 28 to 29 includes, wherein the control server receives the speed data and the headway data from a plurality of CVs including the CV, wherein the speed correction factor is calculated based on the speed data from the plurality of CVs, and wherein the headway correction factor is calculated based on the headway data from the plurality of CVs.
[0156] In Example 31, the subject matter of Examples 28 to 30 includes, wherein the prediction engine utilizes a long-term shared world model that stores data received from the plurality of CVs and the plurality of road sensors.
[0157] In Example 32, the subject matter of Examples 28 to 31 includes, wherein adjusting the determined future flow based on the speed correction factor and the headway correction factor comprises: multiplying the determined future flow by a quotient of the speed correction factor and the headway correction factor.
[0158] In Example 33, the subject matter of Examples 28 to 32 includes, wherein adjusting the determined future average speed based on the speed correction factor includes multiplying the determined future average speed by the speed correction factor.
[0159] In Example 34, the subject matter of Examples 28 to 33 includes, wherein adjusting the determined future density based on the headway correction factor includes dividing the determined future density by the headway correction factor.
[0160] Example 35 is a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: receiving, at a control server and from a networked vehicle, i.e., a CV, speed data representing the speed of the CV and additional vehicles approaching the CV; calculating a speed correction factor based on the speed data; receiving, at the control server and from the CV, headway data representing the headway between the CV and the additional vehicles approaching the CV; calculating a headway correction factor based on the headway data; using a prediction engine at the control server to determine a future flow, a future average speed, and a future density for a segment of a road; adjusting the determined future flow based on the speed correction factor and the headway correction factor; adjusting the determined future average speed based on the speed correction factor; adjusting the determined future density based on the headway correction factor; generating a control signal for a networked automated vehicle, i.e., a CAV, at the control server based on at least one of the determined future flow, the determined future average speed, and the determined future density; and transmitting the generated control signal to the CAV.
[0161] In Example 36, the subject matter of Example 35 includes, wherein the additional vehicles approaching the CV include at least one of: a vehicle in front of the CV in a lane adjacent to the CV, and a vehicle behind the CV in a lane adjacent to the CV.
[0162] In Example 37, the subject matter of Examples 35 to 36 includes, wherein the control server receives the speed data and the headway data from a plurality of CVs including the CV, wherein the speed correction factor is calculated based on the speed data from the plurality of CVs, and wherein the headway correction factor is calculated based on the headway data from the plurality of CVs.
[0163] In Example 38, the subject matter of Examples 35 to 37 includes, wherein the prediction engine utilizes a long-term shared world model that stores data received from the plurality of CVs and the plurality of road sensors.
[0164] In Example 39, the subject matter of Examples 35 to 38 includes, wherein adjusting the determined future flow based on the speed correction factor and the headway correction factor comprises: multiplying the determined future flow by a quotient of the speed correction factor and the headway correction factor.
[0165] In Example 40, the subject matter of Examples 35 to 39 includes, wherein adjusting the determined future average speed based on the speed correction factor includes multiplying the determined future average speed by the speed correction factor.
[0166] Example 41 is a method comprising: receiving traffic status information from road sensors, connected vehicles (CVs), and connected automated vehicles (CAVs); generating a long-term shared world model based on the received traffic status information; and using a multi-vehicle strategy selector to generate control signals for controlling the CAV based on the long-term shared world model, wherein the multi-vehicle strategy selector generates the control signals using optimization for reducing congestion on a road portion, wherein each control signal controls the speed or travel path of the associated CAV.
[0167] In Example 42, the subject matter of Example 41 includes, wherein the optimization to reduce congestion on the road includes at least ensuring a minimum threshold following distance between each CAV and a vehicle ahead of the CAV.
[0168] In Example 43, the subject matter of Examples 41 to 42 includes, wherein the traffic status information includes at least one of the location of the vehicle, the speed of the vehicle, the following distance between the vehicle and other vehicles, and the number of vehicles on the road portion.
[0169] In Example 44, the subject matter of Example 43 includes, wherein the vehicle comprises a CV or a CAV.
[0170] In Example 45, the subject matter of Examples 43-44 includes, wherein the vehicle comprises a non-networked vehicle, wherein traffic state information of the non-networked vehicle is determined using one or more of the road sensors.
[0171] In Example 46, the subject matter of Examples 43 to 45 includes, wherein the vehicle comprises a non-networked vehicle, wherein traffic status information of the non-networked vehicle is determined using at least one of the CV and the CAV.
[0172] In Example 47, the subject matter of Examples 41 to 46 includes, wherein the CV, the CAV, and the non-networked vehicle are traveling on the road portion.
[0173] In Example 48, the subject matter of Examples 41 to 47 includes, wherein the CV or the CAV includes at least one vehicle that is not on the road portion.
[0174] Example 49 is a device comprising: a memory storing instructions; and a processor for executing the stored instructions to: receive traffic status information from road sensors, connected vehicles (CVs), and connected automated vehicles (CAVs); generate a long-term shared world model based on the received traffic status information; and use a multi-vehicle strategy selector to generate control signals for controlling the CAV based on the long-term shared world model, wherein the multi-vehicle strategy selector generates the control signals using optimization for reducing congestion on a road portion, wherein each control signal controls the speed or travel path of the associated CAV.
[0175] In Example 50, the subject matter of Example 49 includes, wherein the optimization to reduce congestion on the road includes at least ensuring a minimum threshold following distance between each CAV and a vehicle ahead of the CAV.
[0176] In Example 51, the subject matter of Examples 49 to 50 includes, wherein the traffic status information includes at least one of the location of the vehicle, the speed of the vehicle, the following distance between the vehicle and other vehicles, and the number of vehicles on the road portion.
[0177] In Example 52, the subject matter of Example 51 includes, wherein the vehicle comprises a CV or a CAV.
[0178] In Example 53, the subject matter of Examples 51-52 includes, wherein the vehicle comprises a non-networked vehicle, wherein traffic state information of the non-networked vehicle is determined using one or more of the road sensors.
[0179] In Example 54, the subject matter of Examples 51 to 53 includes, wherein the vehicle comprises a non-networked vehicle, wherein traffic status information of the non-networked vehicle is determined using at least one of the CV and the CAV.
[0180] In Example 55, the subject matter of Examples 49 to 54 includes, wherein the CV, the CAV, and the non-networked vehicle are traveling on the road portion.
[0181] In Example 56, the subject matter of Examples 49 to 55 includes, wherein the CV or the CAV includes at least one vehicle that is not on the road portion.
[0182] Example 57 is a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: receiving traffic status information from road sensors, networked vehicles, i.e., CVs, and networked automated vehicles, i.e., CAVs; generating a long-term shared world model based on the received traffic status information; and using a multi-vehicle strategy selector to generate control signals for controlling the CAV based on the long-term shared world model, wherein the multi-vehicle strategy selector generates the control signals using optimization for reducing congestion on a road portion, wherein each control signal controls the speed or travel path of the associated CAV.
[0183] In Example 58, the subject matter of Example 57 includes, wherein the optimization to reduce congestion on the road includes at least ensuring a minimum threshold following distance between each CAV and a vehicle ahead of the CAV.
[0184] In Example 59, the subject matter of Examples 57 to 58 includes, wherein the traffic status information includes at least one of the location of the vehicle, the speed of the vehicle, the following distance between the vehicle and other vehicles, and the number of vehicles on the road portion.
[0185] In Example 60, the subject matter of Example 59 includes, wherein the vehicle comprises a CV or a CAV.
[0186] Example 61 is at least one machine-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to operate to implement any of Examples 1 to 60.
[0187] Example 62 is an apparatus comprising components to implement any one of Examples 1 to 60.
[0188] Example 63 is a system for implementing any one of Examples 1 to 60.
[0189] Example 64 is a method for implementing any one of Examples 1 to 60.
[0190] As used herein, the term "instruction" may include instructions or expressions for performing any method disclosed herein or one or more than one arbitrary part thereof, and may be implemented in hardware, software, or any combination thereof. For example, an instruction may be implemented as information stored in a memory (such as a computer program, etc.), which may be executed by a processor to perform any of the various methods, algorithms, aspects, or combinations thereof as described herein. An instruction or a portion thereof may be implemented as a dedicated processor or circuit, which may include dedicated hardware for performing any of the methods, algorithms, aspects, or combinations thereof as described herein. In some implementations, a portion of an instruction may be distributed across multiple processors on a single device or multiple devices, which may communicate directly or across a network (such as a local area network, a wide area network, the Internet, or a combination thereof, etc.).
[0191] As used herein, the terms "example", "embodiment", "implementation", "aspect", "feature" or "element" indicate use as an example, instance or illustration. Unless explicitly indicated otherwise, any example, embodiment, implementation, aspect, feature or element is independent of each other example, embodiment, implementation, aspect, feature or element and can be used in combination with any other example, embodiment, implementation, aspect, feature or element.
[0192] As used herein, the terms "determine" and "identify" or any variations thereof include selecting, ascertaining, calculating, searching, receiving, determining, establishing, obtaining, or otherwise identifying or determining in any manner using one or more of the devices shown and described herein.
[0193] As used herein, unless otherwise specified or clear from context, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." Additionally, the articles "a" and "an" as used in this application and the appended claims should generally be understood to mean "one or more than one," unless otherwise specified or clear from context to direct to the singular.
[0194] In addition, for simplicity of explanation, although the accompanying drawings and description herein may include the sequence or series of steps or stages, the key elements of the method disclosed herein may occur in various orders or in parallel. Additionally, the key elements of the method disclosed herein may occur with other key elements that are not clearly presented and described herein. In addition, all key elements of the method described herein may not be required to realize the method according to the present invention. Although aspects, features and key elements are described in this article with specific combinations, each aspect, feature or key element may be used independently, or may be used in various combinations with other aspects, features and key elements or in various combinations without other aspects, features and key elements.
[0195] In order to make it easy to understand the present invention, the above aspects, examples and implementations are described, but the present invention is not restrictive. On the contrary, the present invention covers various modifications and equivalent arrangements included within the scope of the appended claims, and the scope should be given the broadest interpretation to cover all such modifications and equivalent structures permitted by law.
Claims
1. A method comprising: receiving traffic status information from road sensors, connected vehicles (CVs), and connected automated vehicles (CAVs); generating a long-term shared world model based on the received traffic status information; as well as Using a multi-vehicle strategy selector, control signals for controlling the CAV are generated based on the long-term shared world model, wherein the multi-vehicle strategy selector generates the control signals using optimization for reducing congestion on a road portion, wherein each control signal controls a speed or travel path of an associated CAV.
2. The method according to claim 1, wherein: Optimization to reduce congestion on the road includes at least ensuring a minimum threshold following distance between each CAV and a vehicle ahead of the CAV.
3. The method according to claim 1, wherein: The traffic status information includes at least one of the location of the vehicle, the speed of the vehicle, the following distance between the vehicle and other vehicles, and the number of vehicles on the road portion.
4. The method according to claim 3, wherein: The vehicle comprises a CV or a CAV.
5. The method according to claim 3, wherein: The vehicle comprises a non-networked vehicle, wherein traffic status information of the non-networked vehicle is determined using one or more of the road sensors.
6. The method according to claim 3, wherein: The vehicle comprises a non-networked vehicle, wherein traffic status information of the non-networked vehicle is determined using at least one of the CV and the CAV.
7. The method according to claim 1, wherein: The CV, the CAV and the non-networked vehicle are traveling on the road portion.
8. The method according to claim 1, wherein: The CV or the CAV includes at least one vehicle that is not on the road portion.
9. A device comprising: a memory storing instructions; as well as A processor for executing stored instructions to: receiving traffic status information from road sensors, connected vehicles (CVs), and connected automated vehicles (CAVs); generating a long-term shared world model based on the received traffic status information; as well as Using a multi-vehicle strategy selector, control signals for controlling the CAV are generated based on the long-term shared world model, wherein the multi-vehicle strategy selector generates the control signals using optimization for reducing congestion on a road portion, wherein each control signal controls a speed or travel path of an associated CAV.
10. The device according to claim 9, wherein: Optimization to reduce congestion on the road includes at least ensuring a minimum threshold following distance between each CAV and a vehicle ahead of the CAV.
11. The device according to claim 9, wherein: The traffic status information includes at least one of the location of the vehicle, the speed of the vehicle, the following distance between the vehicle and other vehicles, and the number of vehicles on the road portion.
12. The device according to claim 11, wherein The vehicle comprises a CV or a CAV.
13. The device according to claim 11, wherein: The vehicle comprises a non-networked vehicle, wherein traffic status information of the non-networked vehicle is determined using one or more of the road sensors.
14. The device according to claim 11, wherein: The vehicle comprises a non-networked vehicle, wherein traffic status information of the non-networked vehicle is determined using at least one of the CV and the CAV.
15. The apparatus according to claim 9, wherein: The CV, the CAV and the non-networked vehicle are traveling on the road portion.
16. The apparatus according to claim 9, wherein: The CV or the CAV includes at least one vehicle that is not on the road portion.
17. A non-transitory computer readable medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising: receiving traffic status information from road sensors, connected vehicles (CVs), and connected automated vehicles (CAVs); generating a long-term shared world model based on the received traffic status information; as well as Using a multi-vehicle strategy selector, control signals for controlling the CAV are generated based on the long-term shared world model, wherein the multi-vehicle strategy selector generates the control signals using optimization for reducing congestion on a road portion, wherein each control signal controls a speed or travel path of an associated CAV.
18. The computer-readable medium of claim 17, wherein: Optimization to reduce congestion on the road includes at least ensuring a minimum threshold following distance between each CAV and a vehicle ahead of the CAV.
19. The computer-readable medium of claim 17, wherein: The traffic status information includes at least one of the location of the vehicle, the speed of the vehicle, the following distance between the vehicle and other vehicles, and the number of vehicles on the road portion.
20. The computer-readable medium of claim 19, wherein: The vehicle comprises a CV or a CAV.
