KR20230008177A - Automatic driving actions for determined driving conditions - Google Patents

Abstract

The driving control system automatically controls driving systems (eg, cruise control, headlights, radio volume, in-vehicle infotainment (IVI) display, etc.) or performs driving actions, such as providing notifications to the driver or a third party. can be applied The driving control system may obtain current driving requirements such as explicit speed limits, estimated reduced speeds, conditions for enhanced driver focus, headlight requirements, and the like. The driving control system may compare the current driving requirements to current driving conditions such as current speed, headlight indicators, radio or IVI status, and the like to determine a mismatch. Any such mismatches can be indexed into a mapping of mismatches to driving actions, and if a mismatch is mapped to a driving action, a driving action can be taken.

Description

Automatic driving actions for determined driving conditions

The present disclosure relates to autonomous driving actions for hybrid vehicle control by humans and computerized systems.

There are over a billion cars on the world's roads today. In the United States alone, it is estimated that drivers drive 70 billion hours, drive 2.6 trillion miles, and cause 6 million car accidents each year. Many of these accidents are due to the driver's failure to comply with driving requirements such as speed limits, weather restrictions, headlight requirements, and the like. Law enforcement agencies attempt to prevent these failures by monitoring and issuing citations for drivers who comply with driving requirements. However, drivers are often less attentive or unaware of current driving conditions or ignore such deterrence measures, making them less effective.

1 is a block diagram illustrating an overview of devices in which some implementations may operate.
2 is a block diagram illustrating an overview of a network environment in which some implementations may operate.
3 is a block diagram illustrating components that, in some implementations, may be used in a system employing the disclosed technology.
4 is a flow diagram illustrating a process used in some implementations to apply driving actions depending on mismatches between current driving requirements and current driving conditions.
5A is a conceptual diagram illustrating an example of automating speed controls to a vehicle according to speed requirements provided to the vehicle by a mobile device.
5B is a conceptual diagram illustrating an example of highlighting speed notifications identified by the camera system using a projection display.
The techniques introduced herein may be better understood by referring to the following detailed description in conjunction with the accompanying drawings, in which like reference numbers indicate identical or functionally similar elements.

A driving control system that applies driving actions according to current driving requirements and mismatches of the current driving conditions is described. The driving control system automatically controls driving systems (eg, cruise control, headlights, radio volume, in-vehicle infotainment (IVI) display, etc.) or performs driving actions, such as providing notifications to the driver or a third party. can be applied

The drive control system may obtain current driving requirements such as explicit speed limits, estimated reduced speeds, conditions for heightened driver focus, headlight requirements, windshield wiper requirements, and the like. The driving control system may compare the current driving requirements to current driving conditions such as current speed, headlight indicators, radio or IVI status, and the like to determine a mismatch. Any such mismatches can be indexed into a mapping of mismatches to driving actions, and if a mismatch is mapped to a driving action, a driving action can be taken.

As a first example, the drive control system may have a mapping that specifies that a difference of more than 5 miles (MPH) in the current vehicle speed to the current speed limit triggers a drive action that reduces the vehicle speed to the current speed limit. The driving control system may be programmed with a geographic mapping system that specifies speed limits for particular roads (eg, provided by a government database or a third party). Using the current driving condition defining the GPS coordinates, the driving control system can use the geographic mapping system to obtain the current driving requirement specifying the current speed limit. The drive control system may also interface with the vehicle speed monitoring system to obtain current drive conditions that specify the current speed of the vehicle. The drive control system may compare the current vehicle speed to the speed limit and, as specified in the mapping, if the current vehicle speed exceeds the speed limit by greater than 5 MPH, the drive control system may reduce the speed of the vehicle to the current speed limit. It can interface with the vehicle's cruise control system for this purpose.

As another example, the drive control system may be integrated with a commercial vehicle, and if the vehicle's current speed exceeds 35 MPH and exceeds the current speed limit by more than 10%, the drive control system notifies the company record system of the excessive speed. You can have a mapping that specifies what to do. The driving control system may include a camera and computer vision system configured to determine the current speed limit by capturing images along the road and specifying which speed limits and what those speed limits are. The drive control system may also interface with the vehicle speed monitoring system to obtain the current vehicle speed. The drive control system may compare the current vehicle speed to the speed limit and determine if the current speed exceeds 35 MPH and exceeds the current speed limit by at least 10%, as specified in the mapping. If so, the drive control system can store the excessive speed log and post the log to provide to the company recording system the next time the vehicle returns to the company loading dock with WiFi access.

Some implementations are discussed in more detail below with reference to the figures. 1 is a block diagram illustrating an overview of devices in which some implementations of the disclosed technology may operate. Devices may include hardware components of device 100 capable of applying driving actions depending on mismatches between current driving requirements and current driving conditions. Device 100 includes one or more input devices 120 that provide input to processor(s) 110 (eg, CPU(s), GPU(s), HPU(s), etc.) to notify actions. can include Actions may be mediated by a hardware controller that interprets the signals received from the input device and communicates the information to the processors 110 using a communication protocol. Input devices 120 may include, for example, a mouse, keyboard, touch screen, infrared sensor, touchpad, wearable input device, camera or image-based input device, microphone, temperature sensors, moisture sensors, inertial motion (e.g. eg acceleration) sensors, tilt or level sensors, proximity or sonar sensors, or other input devices.

Processors 110 may be a single processing unit or multiple processing units within a device or may be distributed across multiple devices. Processors 110 may be coupled to other hardware devices using a bus, such as, for example, a PCI bus or a SCSI bus. Processors 110 may communicate with a hardware controller for devices such as display 130 . Display 130 may be used to display text and graphics. In some implementations, display 130 provides graphical and textual visual feedback to the user. In some implementations, display 130 includes an input device as part of the display, such as when the input device is a touchscreen or equipped with an eye direction monitoring system. In some implementations, the display is separate from the input device. Examples of display devices are: LCD display screens, LED display screens, projected, holographic, or augmented reality displays (eg, head-up display devices or head-mounted devices), and the like. Other I/O devices 140, such as network cards, video cards, audio cards, USB, FireWire or other external devices, cameras, printers, speakers, CD-ROM drives, DVD drives, disk drives, or Blu-ray devices. This may also be coupled to the processor.

In some implementations, device 100 also includes a communication device capable of wirelessly or wire-based communication with a network node. A communication device may communicate with another device or server over a network using, for example, a TCP/IP protocol. Device 100 may utilize a communication device to distribute operations across multiple network devices.

Processors 110 may have access to memory 150 within a device or distributed across multiple devices. Memory includes one or more of a variety of hardware devices for volatile and nonvolatile storage, and may include both read-only and writeable memory. For example, memory includes random access memory (RAM), various caches, CPU registers, read only memory (ROM), and flash memory, hard drives, floppy disks, CDs, DVDs, magnetic storage devices , tape drives, and the like. Memory is not a propagating signal separate from the underlying hardware; Thus, memory is non-temporary. The memory 150 may include a program memory 160 that stores programs and software such as an operating system 162 , a driving control system 164 , and other application programs 166 . Memory 150 may also include data memory 170, for example, stored driving requirements, driving conditions, or deltas therebetween; Mappings to driving actions of current driving conditions and current driving requirement mismatches, data structures for interfacing with driving systems or communication systems to perform driving actions, configuration data, settings, user options or preferences and the like, which may be provided to program memory 160 or any element of device 100 .

Some implementations may operate in conjunction with a number of different computing system environments or configurations. Examples of computing systems, environments, and/or configurations that may be suitable for use with the technology include personal computers, server computers, handheld or laptop devices, cell phones, wearable electronic devices, tablet devices distributed computing environments, including any of the above systems or devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronic devices, networked PCs, minicomputers, mainframe computers, and the like, but are not limited thereto.

2 is a block diagram illustrating an overview of an environment 200 in which some implementations of the disclosed technology may operate. Environment 200 may include one or more client computing devices 205A-D, examples of which may include device 100 . Client computing devices 205 can operate in a networked environment using logical connections to one or more remote computers, such as a server computing device, via network 230 .

In some implementations, server 210 may be an edge server that receives client requests and coordinates fulfillment of these requests via other servers, such as servers 220A-C. Server computing devices 210 and 220 may include computing systems such as device 100 . Although each server computing device 210 and 220 is logically displayed as a single server, the server computing devices may be a distributed computing environment that includes multiple computing devices each located at the same or geographically different physical locations. In some implementations, each server 220 corresponds to a group of servers.

Client computing devices 205 and server computing devices 210 and 220 can each act as a server or client to other server/client devices. Server 210 may connect to database 215 . Servers 220A-C may each connect to a corresponding database 225A-C. As discussed above, each server 220 may correspond to a group of servers, and each of these servers may share a database or may have their own database. Databases 215 and 225 may warehouse (eg, store) information. Although databases 215 and 225 are logically displayed as single units, databases 215 and 225 can each be a distributed computing environment that includes multiple computing devices, can be located within their corresponding servers, or can be identical to one another. or may be located in geographically different physical locations.

Network 230 may be a local area network (LAN) or a wide area network (WAN), but may also be other wired or wireless networks. Network 230 may be the Internet or some other public or private network. Client computing devices 205 may be connected to network 230 through a network interface, such as wired or wireless communication. Although the connections between server 210 and servers 220 are shown as separate connections, these connections can be any kind of local, wide area, wired or wireless network, including network 230 or a separate public or private network. can be

3 is a block diagram illustrating components 300 that, in some implementations, may be used in a system employing the disclosed technology. Components 300 include hardware 302 , general software 320 , and special components 340 . As discussed above, a system implementing the disclosed technology includes processing units 304 (eg, CPUs, GPUs, APUs, etc.), working memory 306, storage memory 308 (local storage or A variety of hardware may be used, including input and output devices 310), and input and output devices 310 as an interface to remote storage, such as storage 215 or 225. In various implementations, storage memory 308 can be one or more of local devices, interfaces to remote storage devices, or combinations thereof. For example, storage memory 308 may be a set of one or more hard drives (eg, a redundant array of independent disks (RAID)) accessible via a system bus, or cloud storage accessible via one or more communication networks. It may be a provider or other network storage (eg, a network accessible storage (NAS) device, such as storage provided through storage 215 or other server 220). Components 300 may be implemented on a client computing device, such as client computing devices 205 or on a server computing device, such as server computing device 210 or 220 .

General software 320 may include various applications including an operating system 322 , local programs 324 , and basic input output system (BIOS) 326 . Special components 340 may be subcomponents of a general software application 320 , such as local programs 324 . Special components 340 provide driving requirement detector 344, driving condition detector 346, mismatch mappings 348, mapping applicator 350, and user interfaces, transmit data, interfaces 342 may include components that may be used to control special components. In some implementations, components 300 can reside in a computing system that is distributed across multiple computing devices, or can be an interface to a server-based application running one or more of specialized components 340. .

Driving requirements detector 344 may obtain current driving requirements using interfaces to 342 that have access to data from vehicle sensors and/or data from sources external to the vehicle, eg, over a network. there is. Some current driving requirements may include the current speed limit from a geographic mapping system with speed limit data, from capturing and recognizing speed limit signs, or from transponders located along the roadway. there is. Additional current driving requirements may be for enhanced driver focus, which include cameras, temperature sensors, moisture sensors, altitude sensors, angle sensors to determine road grade percentages, inertial motion units and/or turning The turn radius can be determined based on conditions surrounding the vehicle determined using data from steering wheel position sensors or the like to determine the turn radius. However, additional current driving requirements may be reduced speed, headlight requirements, or other driving requirements (eg, traffic rules, safety requirements, company or vehicle owner policy, etc.). Additional details on obtaining current driving requirements are provided below with respect to block 402 of FIG. 4 .

Driving condition detector 346 may obtain current driving conditions using interfaces to 342 that have access to vehicle sensors and/or data from the vehicle on-board computer. Some current driving conditions may include current vehicle speed, headlight condition, windshield condition, radio or IVI settings, current gear selection, current motor rotation frequency, and the like. Additional details on obtaining current driving conditions are provided below with respect to block 404 of FIG. 4 .

Mismatch mappings 348 may include A) mismatches (e.g., for comparing current driving conditions obtained by driving condition detector 346 with current driving requirements obtained by driving requirement detector 344). conditions) versus B) may store a set of mappings of driving actions that the system 300 will perform when the conditions of the mismatch occur. Various mismatch mappings 348 may be provided by one or more entities such as vehicle drivers, vehicle owners, employers, government agencies, and the like. In some implementations, the mapping can map mismatches and/or driving characteristics to driving actions.

Mapping applicator 350 converts mismatch mappings 348 (or characteristic mappings) to current driving requirements obtained by driving requirements detector 344 and current driving conditions obtained by driving condition detector 346. can be applied to determine whether any mismatches (or specific characteristics) are occurring. When mapping applicator 350 determines that such a mismatch or driving characteristic is occurring, it can cause one or more driving actions mapped to that mismatch or driving characteristic to occur. For example, when indicated by a specific driving action, mapping applicator 350 interfaces with a vehicle cruise control system or other acceleration or braking system to control vehicle speed, windshield wiper controls, or headlight status. It can interface with the vehicle's on-board computer to set up settings, interface with a radio or other IVI system to change the volume or set brightness levels, or interface with the gearing system to select the current driving gear. Additional details regarding identifying mismatches specified in the mapping and taking corresponding driving actions are provided below with respect to blocks 406 - 410 of FIG. 4 .

One skilled in the art will appreciate that in each of the components illustrated in FIGS. 1-3 described above, and the flow diagrams discussed below, can be varied in various ways. For example, the order of logic can be rearranged, substeps can be performed in parallel, illustrated logic can be omitted, and other logic can be included. In some implementations, one or more components described above can execute one or more of the processes described below.

4 is a flow diagram illustrating a process 400 used in some implementations to apply driving actions depending on mismatches between current driving requirements and current driving conditions. Process 400 may be performed as the vehicle is operated, eg, as new current driving conditions and/or current driving requirements are pushed to the driving control system or when the driving control system determines current driving conditions and/or current driving requirements. It may be performed periodically when polling sensors and data sources for . In various implementations, process 400 is performed by a computing system integrated with the vehicle or to an external computing system, such as a mobile device capable of interfacing with the vehicle, for example via Bluetooth or via some other wired or wireless connection. can be performed by

At block 402, process 400 may obtain current driving requirements. Current driving requirements may specify values for the environment in which vehicle operation is taking place. In some implementations, process 400 determines the current driving requirements (of driving characteristics) based on the current driving condition used in blocks 406 - 410 and the mapping of current driving requirement mismatches (of driving characteristics) to driving actions. and current driving conditions at block 404). For example, if process 400 positively retrieves current driving requirements and/or current driving conditions, process 400 will attempt to obtain those used in one or more mismatches mapped to driving actions. can In other implementations, current driving conditions and/or current driving requirements are pushed to process 400 that passively receives them. In various implementations, the current driving requirements received at block 402 may be an explicit speed limit, requirements for enhanced driver focus, requirements for reduced speed, headlight requirements, or other driving requirements ( eg, traffic rules, safety requirements, company or vehicle owner policies, etc.).

In some implementations, process 400 can obtain explicit speed limits or daytime headlight requirements from a geographic mapping system that has speed limits or headlight requirements specified for particular roads. This geographic mapping system can be pre-programmed into the drive control system, or linked (eg via Bluetooth) from an external source such as a mobile device or from a third party data source (eg to the Internet). over a cellular connection to Process 400 may then use GPS or other location data to determine the vehicle's current location on the map and corresponding speed limits and/or headlight requirements. In other implementations, process 400 may be used by a computer vision system (e.g., to analyze images to identify headlight requirement signs and/or speed limit signs and which speed limit these signs require). , systems using machine learning models such as deep neural networks) can be used to obtain explicit speed limits or headlight requirements by reading road signs with cameras attached to vehicles being processed. These implementations allow for updates to unusual conditions, such as extreme weather conditions or temporary speed limits set for construction zones that may not be represented in the geographic mapping system. In yet other implementations, the road or road sign may be equipped with a transponder allowing direct and reliable communication of speed limits to driving control systems. In some implementations, process 400 can also determine headlight requirements based on a sensor gauging ambient lighting. In some implementations, for example, by using a geographic mapping system to obtain initial speed or headlight requirements, but updating them once the camera captures an image of a sign or weather indicating that the speed requirement should be modified; Combinations of these systems may be used.

When process 400 obtains current driving requirements for enhanced driver focus and/or reduced speed, these requirements may include analyzing conditions surrounding the vehicle (e.g., cameras, temperature sensors, moisture sensors, altitude sensors, angle sensors to determine road grade percentages, inertial motion units and/or steering wheel position sensors to determine turning radius, etc.) and/or from third parties (e.g., weather forecast systems, government agencies providing road or traffic conditions, information from surrounding vehicles directly or aggregated through third parties, etc.). For example, cameras integrated with a vehicle can capture images, and a computer vision system can be trained to analyze them to recognize traffic, weather, turns, road signs, and the like. In some implementations, various such inputs can be mapped to situations where enhanced driver focus is required and/or reduced speeds are required. In other implementations, these inputs can be provided to a trained machine learning model to identify situations in which enhanced driver focus is required and/or reduced velocities are required. For example, a machine learning model can be trained with training data items that resulted in an accident in which conditions correspond to enhanced driver focus or reduced speed requirement conditions.

At block 404, process 400 can obtain current driving conditions. The current driving conditions are conditions under which the driving control system has some control or the driving control system can provide a notification, which allows the driver to adjust the driving controls or provide information about the driving conditions to third parties. . Current driving conditions, for example, include vehicle speed, whether headlights are active, whether a radio or other sound system is on and its settings (eg volume, brightness, channel or station, etc.), other IVI systems It may include values such as whether it is active and its settings, whether windshield wipers are active, current gear selection, current engine revolutions per minute (RPM), and the like. In some cases, process 400 may obtain values for various current driving conditions through integration with the vehicle. For example, the vehicle may directly provide the current speed to the drive control system (eg, using a sensor system based on tire size and accelerator rotation). As another example, the on-board computer system on the vehicle can determine whether the headlights are active, whether the radio or IVI system is on and its settings, whether the windshield wipers are active, the current gear selection, the current engine revolutions per minute (RPM) You can provide values for etc. In other cases, process 400 may obtain values for various current driving conditions through external systems. For example, vehicle speed may be determined based on a measured difference between GPS coordinates over a period of time, from accelerometer measurements from a known initial (eg, zero) speed, or object location in images over a period of time. It can be determined based on captured images that measure the change in . As another example, radio or IVI status and settings may be determined based on a microphone or camera of a mobile device in a vehicle.

At block 406 , process 400 can compare the current driving requirements from block 402 to the current driving conditions from block 404 . In some implementations, process 400 can achieve this by comparing current driving requirements to current driving conditions of the same type (eg, speed) to determine a delta for that type. In other implementations, process 400 may be used to determine whether any mapping mismatches (or other driving characteristics) are occurring (mismatches between current driving requirements and current driving conditions). It can achieve this by iterating through a set of mappings (specific to driving actions). In various implementations, some or all of the mapping entries may be established by a vehicle operator, vehicle owner, employer, government agency, or the like.

The mapping is current driving condition speed to current driving requirement speed (explicitly set or implied from reduced speed requirements), current driving condition headlight setting to current driving requirement headlight requirement, current driving requirement augmented focus requirement current driving condition for radio or IVI status, current driving condition gear selection and/or current driving condition motor RPM for current driving condition road grade condition, current driving condition for current driving condition weather condition windshield wiper settings etc. can include Although referred to herein as “mismatches,” the mapping can be < (less than), > (greater than), <= (less than or equal to), >= (greater than or equal to), != (not equal to), or You can have different types of comparisons using different comparator operators, such as other standard comparison operators. In some implementations, the mapping can specify the current driving requirement or transforms or constants to apply to the current driving condition to determine the mismatch. As examples, the comparison can be between the current speed and 10% of the current speed limit, the current speed plus a constant value, the current speed can be compared to a constant, or other transformations or constant conditions. In some implementations, the mapping can specify combinations of current driving condition and current driving requirement comparisons. For example, the mapping is [current speed 7% above current speed limit and current speed is at least 35 MPH] OR [current speed is 5% above current speed limit and current turn angle is greater than 25 degrees] Mismatch can be specified to occur. AND (each condition must be met), OR (any one condition must be met), XOR (exactly one of the conditions must be met), NOT (condition must not be met), or any other standard combination A variety of combinatorial operators, such as operators, can be used in such combinations. The symbols and terms described for the above operators are examples only, and other equivalent operator symbols and terms may be used.

At block 408, process 400 can determine whether any determined mismatches are mapped to driving actions. In some implementations, this may include determining whether any deltas for particular types of comparisons of current driving requirements with current driving conditions from block 406 are mapped to one or more driving actions. there is. In other implementations, this may include identifying one or more driving actions mapped to any mismatches determined at block 406 in a mapping that specifies the mismatch conditions. If any such travel actions are identified, process 400 may continue to block 410 . If no such driving actions are identified, process 400 may skip block 410 and end.

At block 410 , process 400 can perform the travel action(s) identified at block 408 . In various implementations, driving actions include changing the speed of the vehicle, modifying a driving system setting (eg, activating headlights; disabling a radio or other IVI, controlling volume, or brightness; activating windshield wipers; activating the windshield defroster, etc.), changing the current gear selection (eg, via a dashboard indicator, heads-up display (HUD) or other projection system, via a paired mobile device, via audio notification, etc.) ) to provide notifications to the driver of the vehicle, to provide notifications to other systems (e.g., email, text, or other contact, log or database item entry for a specified account, driving report to the driver of the vehicle). serving, activating URLs or messaging specific addresses, or other communication systems), and the like. In some implementations where driving actions include changes other than notification, options may be provided that allow the driver to override the driving action. For example, if the driving action includes a change in speed, change in headlight settings, etc., process 400 can provide a notification that a change is about to occur, and the driver can push a particular button, e.g. For example, you can override it with a voice command.

In some implementations, controlling the speed of the vehicle can include interfacing with the vehicle's cruise control system or directly controlling the acceleration system. In some implementations, an automatic speed or other driving system change may be accompanied by notification to the driver of the automatic change. For example, a voice message can be played through the vehicle audio system, an alarm can sound, a dashboard notification can be illuminated, a HUD or other projection display can be activated, and the like. In some implementations, the notification can depend on the severity of the mismatch or based on the type of mismatch. For example, different notifications or notification settings may be provided according to different thresholds (eg, 5 MPH above or below the speed limit, 10 MPH above or below the speed limit, and 15 MPH above or below the speed limit). (eg, green, yellow, or red notifications; whether the notification is on solid or flashing; setting the notification volume; whether the notification is provided via the dashboard or via the HUD; etc.). In some implementations, an initial notification can be provided to the driver indicating, for example, that the current vehicle speed is above or below the limit or an amount of difference between the current vehicle speed and the limit, the driver may be provided with a threshold for taking corrective action. An amount of time (eg, 10 seconds, 30 seconds, 1 minute, 5 minutes, etc.) may be given. If the driver does not take a corrective action (such as changing the speed to the speed limit or within a speed limit threshold - for example, 5 MPH) within a threshold amount of time, the vehicle's speed is automatically reduced to the speed limit or within the speed limit threshold. can be adjusted

In some implementations, the notification can provide an indication of a difference between the current driving condition and the current driving requirement. For example, the notification may specify that the vehicle is 10 MPH above the current speed limit of 40 MPH. In some implementations, the notification can automatically accentuate factors in the environment in which process 400 is used to identify current driving requirements. For example, if process 400 determines a current speed limit based on speed limit signs detected in images captured by a camera integrated with a vehicle, and process 400 determines a miss between that speed limit and the vehicle's current speed, If it is determined that there is a match, a HUD or other projection system may be used to allow the driver of the vehicle to see the features emphasized by the speed limit sign (eg, changing color, blinking, highlighting a boundary). As another example, process 400 can determine, based on a current weather report for an area displaying heavy fog, that the vehicle should drive with low beam headlights, and the vehicle's headlight system (with high beams) and low beam current driving requirements. In response, process 400 may provide an audible notification indicating that there is heavy fog and low beams should be used. In some implementations, a voice activation system can also be implemented. For example, continuing the previous example, following the voice fog notification, the system may ask the driver if the drive control system would like to switch to low beam headlights, and the driver responds with a voice yes or no command. can do. Following implementation of the driving actions at block 410, process 400 may end (or may repeat as new current driving conditions and/or current driving requirements are obtained).

5A is a conceptual diagram illustrating an example 500 of automating speed controls to a vehicle according to speed requirements provided to the vehicle by a mobile device. Example 500 includes mobile device 502 having a cellular connection 504 to the Internet and a Bluetooth connection 506 . Example 500 also includes a vehicle 510 that has a dashboard notification system 508 and can interface with a mobile device 502 via a Bluetooth connection 506 . In example 500 , mobile device 502 runs a geographic mapping application that receives a map of a current area with speed limit indicators for various roads via cellular connection 504 . Using the GPS data, mobile device 502 identifies the current road on which vehicle 510 is traveling and a corresponding speed limit of 45 MPH. Using Bluetooth connection 506, mobile device 502 also receives current driving conditions indicating that vehicle 510 is moving at 57 MPH. Using the mapping of the current driving condition and current driving requirement mismatches to the driving actions programmed into mobile device 502, mobile device 502 determines the number of misses that occur when the vehicle exceeds the current speed limit by more than 10 MPH. identify a match In response, mobile device 502 interfaces with the cruise control system of vehicle 510 using Bluetooth connection 506 to set the current speed of vehicle 510 to the current driving requirement speed limit of 45 MPH. Dashboard notification system 508 also displays a message indicating that speed control has been activated.

5B is a conceptual diagram illustrating an example 550 of highlighting speed notifications identified by the camera system using a projection display. Example 550 includes speed limit sign 562 and vehicle 560 having integrated camera and computer vision system 552 , projection display 554 , and dashboard notification system 558 . In example 550, as vehicle 560 proceeds down the road, camera and computer vision system 552 capture an image of sign 562 and recognize a current driving requirement speed limit of 45 MPH. Vehicle 560 compares this speed limit to the current driving condition vehicle speed of 60 MPH specified in the programmed mapping. Vehicle 560 determines that these conditions correspond to a mismatch, which notifies the driver via projection display 554 and dashboard notification system 558 that the current driving condition speed is 10% higher than the current driving requirement speed limit. specifies that it should provide Based on this determination, the vehicle activates a “speed limit exceeded” notification on dashboard notification system 558 and projection by projection display 554, (monitored by another camera system, the driver's determined eye). Based on location - not shown) this causes the driver to see the sign highlight 556 as a blinking border around the sign 562 .

Some implementations of the disclosed technology are described above with reference to the figures. Computing devices in which the described technology may be implemented include one or more central processing units, memory, input devices (eg, keyboard and pointing devices), output devices (eg, display devices), storage devices (eg, disk drives), and network devices (eg, network interfaces). Memory and storage devices are computer readable storage media capable of storing instructions implementing at least portions of the described technology. Also, data structures and message structures may be stored or transmitted over a data transmission medium such as a signal on a communication ring. Various communication links may be used, such as the Internet, a local area network, a wide area network, or a point-to-point dial-up connection. Accordingly, computer-readable media may include computer-readable storage media (eg, “non-transitory” media) and computer-readable transmission media.

References herein to “embodiments” (eg, “some implementations,” “various implementations,” “one implementation,” “an implementation,” etc.) refer to specific features described in connection with the implementation. , means that the structure or characteristic is included in at least one embodiment of the present disclosure. The appearances of these phrases in various places in the specification are not necessarily all referring to the same implementation, nor are separate or alternative implementations mutually exclusive of other implementations. Also, various features are described that may be exhibited by some implementations and not by others. Similarly, various requirements are described that may be requirements for some implementations but not requirements for other implementations.

As used herein, above a threshold means that the value for the item being compared exceeds another specified value, the item being compared is among a specified number of items with the largest value, or It means that the item to be compared has a value within the specified uppermost percentage value. As used herein, being less than a threshold means that the value for the item being compared is less than another specified value, the item being compared is among a specified number of items having the smallest value, or being compared It means that the target item has a value within the specified lower percentage value. As used herein, being within a threshold means that the value for the item being compared is between two specified other values, the item being compared is between a specified number of items in between, or the item being compared is between a specified number of items in between. means that it has a value within this intermediate specified percentage range. Unless defined otherwise, relative terms such as high or unimportant can be understood as assigning a value and determining how that value compares to a set threshold. For example, the phrase “select a fast connection” may be understood to mean selecting a connection assigned a value corresponding to a connection speed higher than a threshold value.

As used herein, the word “or” refers to any possible permutation of a set of items. For example, the phrase "A, B, or C" can refer to at least one of A, B, C, or any combination thereof, such as A; B; C; A and B; A and C; B and C; A, B, and C; or A and A; B, B, and C; A, A, B, C, and multiples of any item such as C, and the like.

Although subject matter has been described in language specific to structural features and/or methodological acts, it should be understood that subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Although specific embodiments and implementations have been described herein for purposes of illustration, various modifications may be made without departing from the scope of the embodiments and implementations. The specific features and acts described above are disclosed as example forms of implementing the following claims. Accordingly, the embodiments and implementations are not limited except as by the appended claims.

Any patents, patent applications, and other references mentioned above are incorporated herein by reference. Aspects may be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide still other implementations. In the event that any statement or subject matter in a document incorporated by reference conflicts with any statement or subject matter in this application, this application controls.

Claims (20)

in the method,
obtaining one or more current driving requirements specifying at least a speed requirement;
obtaining one or more current driving conditions specifying at least a current vehicle speed;
comparing the speed requirement of the one or more current driving conditions with the current vehicle speed of the one or more current driving conditions and, based on the comparison, identifying at least one characteristic specified in the mapping of characteristics to driving actions. step; and
In response to identifying the at least one characteristic, further comprising performing, in the mapping, one or more actions corresponding to the at least one characteristic, wherein performing the one or more driving actions comprises at least a vehicle interfacing with a cruise control system to modify the current vehicle speed. The method of claim 1 , wherein the speed requirement is determined based on a geographic mapping system that correlates speed limits for roads. The method of claim 1 , wherein the speed requirement is determined based on a computer vision system recognizing speed limit signs in images captured by cameras associated with the vehicle. 2. The method of claim 1, wherein the speed requirement is determined based on identification of a requirement for reduced speed from a specified explicit speed limit, the identification of the requirement for reduced speed being based on specific traffic conditions, specific weather conditions, specific road construction conditions, current road grade, specific turning angles, or any combination thereof. According to claim 1,
The comparing step comprises at least two expressions with logical operators each specifying how one or more values in the one or more current driving requirements compare to one or more values in the one or more current driving conditions to satisfy the conditions. including evaluating them;
wherein the combination of the at least two expressions is evaluated using a logical combination operator. The method of claim 1 , wherein performing one or more driving actions further comprises providing a notification that automatic speed control has been activated. 7. The method of claim 6, wherein the notification specifies a difference between a current speed limit and a current vehicle speed. 7. The method of claim 6, wherein the notification is displayed in configurations based on a comparison of a difference between the speed requirement and the current vehicle speed and a threshold corresponding to notification configurations. The method of claim 1 , wherein performing one or more driving actions further comprises providing a notification to a system external to the vehicle indicative of the identified at least one characteristic. A non-transitory computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform operations that:
obtaining one or more current driving requirements specifying at least a speed limit;
obtaining one or more current driving conditions specifying at least a current vehicle speed;
comparing the speed limit of the one or more current driving conditions with the current vehicle speed of the one or more current driving conditions and, based on the comparison, identifying at least one characteristic specified in the mapping of characteristics to driving actions. movement; and
in response to the identifying the at least one characteristic, performing one or more driving actions corresponding to the at least one characteristic in the mapping. 11. The computer readable storage medium of claim 10, wherein performing the one or more driving actions comprises modifying the current vehicle speed by interfacing with at least a cruise control system of the vehicle. 11. The computer readable storage medium of claim 10, wherein the speed limit is determined based on a computer vision system recognizing speed limit signs in an image captured by a camera associated with the vehicle. 11. The system of claim 10, wherein the speed limit is determined based on identification of a requirement for reduced speed, wherein the identification of the requirement for reduced speed includes specific weather conditions, specific road construction conditions, specific turning angles, or any combination thereof. 11. The method of claim 10, wherein the comparing operation comprises a logical operator each specifying how one or more values in the one or more current driving conditions compare to one or more values in the one or more current driving conditions to satisfy conditions. A computer readable storage medium comprising evaluating at least two expressions as . 11. The computer readable storage medium of claim 10, wherein performing the one or more driving actions comprises activating a projection system to cause display of an emphatic feature on a sign specifying the speed limit. 11. The computer readable storage medium of claim 10, wherein performing the one or more driving actions comprises connecting to a system external to the vehicle to provide a driving report indicative of one or more driving conditions of the vehicle. . A computing system for applying autonomous driving actions, the computing system comprising:
one or more processors; and
and one or more memories storing instructions, which instructions, when executed by the one or more processors, cause the computing system to perform operations that:
obtaining one or more current driving requirements;
obtaining one or more current driving conditions;
comparing the one or more current driving requirements with the one or more current driving conditions and determining, based on the comparison, that at least one mismatch specified in the mapping of mismatches to driving actions exists; and
and in response to determining that the at least one mismatch exists, performing one or more driving actions corresponding to the at least one mismatch in the mapping. 18. The computing system of claim 17, wherein performing the one or more driving actions comprises modifying a current vehicle speed by interfacing with at least the vehicle's acceleration system. 18. The computing system of claim 17, wherein the one or more current driving requirements include a speed requirement based on identification of a requirement for reduced speed based on one or more of road construction conditions or a specific turning angle. 18. The computing system of claim 17, wherein performing the one or more driving actions comprises adjusting settings on a vehicle radio or IVI system or adjusting a vehicle's headlight settings.

Images