Patent Grant
10109195
The present disclosure relates to the field of vehicles, and specifically to the field of self-driving vehicles. Still more specifically, the present disclosure relates to the field of selectively controlling a self-driving vehicle's access to a particular roadway based on the autonomous capabilities of the self-driving vehicle.
Self-driving vehicles (SDVs) are vehicles that are able to autonomously drive themselves through private and/or public spaces. Using a system of sensors that detect the location and/or surroundings of the SDV, logic within or associated with the SDV controls the speed, propulsion, braking, and steering of the SDV based on the sensor-detected location and surroundings of the SDV.
In an embodiment of the present invention, a processor-implemented method and/or computer program product selectively blocks a self-driving vehicle's access to a roadway. A vehicle interrogation hardware device receives an autonomous capability signal from an approaching self-driving vehicle, which is approaching an access-controlled roadway. The autonomous capability signal describes a level of autonomous capability of the approaching self-driving vehicle for maneuvering through predefined roadway conditions. One or more processors compare the predefined roadway conditions to current roadway conditions of the access-controlled roadway. In response to the predefined roadway conditions matching the current roadway conditions of the access-controlled roadway within a predetermined range, the processor(s) determine whether the level of autonomous capability of the approaching self-driving vehicle is adequate to safely maneuver the approaching self-driving vehicle through the current roadway conditions of the access-controlled roadway. In response determining that the level of autonomous capability of the self-driving vehicle is not adequate to safely maneuver the approaching self-driving vehicle through the current roadway conditions of the access-controlled roadway, an automatic barricade controlling device positions an automatic barricade to block the approaching self-driving vehicle from accessing the access-controlled roadway.
In an embodiment of the present invention, a roadway access-controlling station includes a supervisory computer, a vehicle interrogation hardware device, and an automatic barricade controlling device. The vehicle interrogation hardware device receives an autonomous capability signal from an approaching self-driving vehicle that is approaching an access-controlled roadway. The autonomous capability signal describes a level of autonomous capability of the approaching self-driving vehicle for maneuvering through predefined roadway conditions. The supervisory computer compares the predefined roadway conditions to current roadway conditions of the access-controlled roadway. In response to the predefined roadway conditions matching the current roadway conditions of the access-controlled roadway within a predetermined range, the supervisory computer determines whether the level of autonomous capability of the approaching self-driving vehicle is adequate to safely maneuver the approaching self-driving vehicle through the current roadway conditions of the access-controlled roadway. The automatic barricade controlling device, in response the supervisory computer determining that the level of autonomous capability of the self-driving vehicle is not adequate to safely maneuver the approaching self-driving vehicle through the current roadway conditions of the access-controlled roadway, positions an automatic barricade to block the approaching self-driving vehicle from accessing the access-controlled roadway.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
Disclosed herein is a system and method that regulates entry to an “SDV-only road” by a barricade (e.g. a gate arm), which is removed (or lifted) only when an SDV authenticates its mode and/or abilities to a controller of the barricade. Further disclosed is the lowering of the barricade whenever a human-operated vehicle and/or an inadequate SDV attempts to enter the SDV-only road.
The pervasiveness of SDVs may lead some political/governmental entities (which are in charge of transportation infrastructures) to design roads that require superhuman (i.e., autonomous) driving abilities. That is, such roads may be devoid of guardrails, traffic lights, have very narrow lanes, etc., thus making them cheaper. While it would be unsafe for a driver of ordinary skill to drive on such a road, a properly set up SDV could safely drive on such a road and/or at speeds that would be unsafe for human drivers. In order to keep unqualified SDVs and/or human drivers off such roadways, barricades would be needed to block access for non-qualified SDVs (i.e., SDVs that do not have the autonomous capabilities to handle the roadway conditions or human drivers that are not qualified to drive on the roadway).
Disclosed herein is a method and a system that utilizes/comprises a road barricade (e.g., an electronic gate arm) and a receiver for receipt of an SDV mode signal from an SDV. In response to receiving a signal describing whether or not the vehicle is in an (adequate) autonomous mode, the barricade deploys or undeploys.
The SDV may be in manual mode or self-driving mode. A standard car (i.e., a vehicle that is not able to drive in a fully autonomous mode) would not, for example, transmit an SDV signal to a control system, and thus will be denied access to roads or special lanes that are appropriate for certain SDVs, which would be better able to handle roads that are narrower or that have other attributes that make them too difficult to handle by human drivers (but that are relatively safe for SDVs). The barrier, barricade, or gate arm may control access to not only a roadway, but also special lane on a roadway, a tunnel, a ferry access lane, a parking spot, a car-wash lane, a service bay in a garage, etc. If desired, the gate or barrier may provide information to drivers (e.g., in the form of an electronic message displayed on a visual display next to the vehicle or inside the cabin of the vehicle) advising the drivers of why they are being denied access. Examples of such an electronic message when trying to access an SDV-only roadway may be “You are not driving an SDV” or “You are not in SDV (automatic/autonomous) mode.”
The road barricade system presented herein may take into account additional factors, such as current or forecast road conditions, weather, daylight levels (in which a driver can or cannot see well), road maintenance, fog level, falling rocks, traffic volume, etc., and then compute a risk level R that is used to determine gate raising and lowering for SDVs and standard vehicles.
The road barricade system may learn about particular cars, classes of cars, car features (e.g., snow tires), particular drivers, particular road conditions, a history of accidents, etc., and then use this information/learning in the decision to raise or lower a gate arm. For example, research has shown that a tight road curve radii will increase the related risk rate, particularly when the vehicle is being manually driven. Thus, the system will be adamant that only SDVs are allowed to enter roadways having tightly-curved sections.
The road barricade system may take into account SDV features (e.g., software version, sensors, processor speed, communication abilities and current signal strength to access artificial intelligence (AI) features in the cloud, superhuman ability levels, etc.) when deciding whether or not to allow an SDV access to a roadway. The system will match the SDV features to current real-time roadway conditions, thus matching a particular SDV to a particular roadway. That is, in one or more embodiments of the present invention, the road barricade system will take into account SDV software version and software patches. In other words, the barricade system (e.g., part of and/or under the control of the roadway access controlling station 206 shown in
The road barricade system may take into account the presence of pedestrians and/or animals near a road or forecast to be near a road in making the decision as to whether or not to allow a certain SDV or a manual vehicle to enter the roadway. For example, if there are numerous pedestrians and/or animals near (or even on) the roadway, then only properly-enabled SDVs may be allowed to drive on that roadway.
The road barricade system may take into account the presence of distracting road noise or other distractions such as road work crews in making the decision as to whether or not to allow a certain SDV or a manual vehicle to enter the roadway. Thus, if there are high levels of distracting road noise (e.g., from work crews, sirens, etc.) that would create a problem for a human driver (but not an autonomous SDV), then autonomous SDVs would be allowed access to the noisy roadway, but vehicles being controlled by humans would not.
The road barricade system may take into account the increased speed with which SDVs might travel on a particular stretch of roadway, therefore limiting travel only to SDVs.
The road barricade system may take into account the terrain for an off-road trail, a dirt road (particularly when wet), and/or a gravel road and determine that it is too difficult for a driver with ordinary skill to travel on it, and thus permit only SDVs to travel on such off-road trails, dirt roads, and/or gravel roads.
The barricade system may manage multiple barricades at a given time, and open appropriate barricades in order to guide the SDV or human operated vehicle to the correct route and/or lane based on the car condition and other factors (e.g., current roadway conditions).
Thus, one or more embodiments of the present invention present a method and system that includes a road barricade (e.g., an electronic gate arm) and a system to receive an SDV mode signal from an SDV such that, based on receiving the SDV mode signal, the barricade deploys or undeploys.
In one or more embodiments of the present invention, the road barricade system takes into account the current level of traffic and types of traffic control devices. For example, if the traffic on a roadway is heavy and/or there are no traffic control lights at intersections, then manually driven cars would not being able to handle such traffic and intersections safely, and are not be permitted to travel on that roadway. However, properly set up SDVs can handle such conditions, and are allowed to travel on that roadway.
In one or more embodiments of the present invention, the road barricade system takes into account the current level of traffic on multilane highways or roadways and may control access to the entrances and exits (i.e., on-ramps and off-ramps) of a highway if the density of traffic is determined to be too high. Thus, traffic flow can be improved, and traffic jams avoided, in situations of traffic congestion due to high density of traffic, collisions, or the presence of emergency vehicles. For example, if an SDV is determined to be capable of quickly merging into the remaining available lanes when a traffic lane is closed, it may be allowed access to the highway on-ramp. Similarly, if an SDV is determined to be able to appropriately accelerate past emergency vehicles without hesitation (i.e., without “rubbernecking” or engaging in other counterproductive or dangerous driving behavior) it may be allowed access to a roadway on-ramp, since the SDV will not obstruct the flow of traffic already on the roadway.
In one or more embodiments of the present invention, the road barricade system may take into account the presence of an SDV when allowing access to or exit from a toll road. For example, if multiple vehicles attempt to use a particular exit on a toll road, thus creating a bottleneck when the multiple vehicles merge into fewer lanes near the particular exit, the barricade system may allow only an approaching SDV that is capable of exiting per predetermined criteria (i.e., at a certain speed, within a certain proximity of other vehicles, etc.), to use the particular toll road exit. Alternatively, only SDVs that match the predetermined exiting criteria may be allowed to enter/access the toll road in the first place, thus altogether eliminating congestion due to hesitation, poor lane-changing skills, etc.
In one or more embodiments of the present invention, the road barricade system will take into account whether a given human driven car is a member of a particular cohort of car types in determining whether or not it should be allowed on the SDV-only section. That is, even if manually driven, if a highly-skilled driver (according to the driver's profile) is driving a high performance vehicle (e.g., a highly responsive sports car), then that driver/vehicle may be allowed on the SDV-only roadway, while slower and/or less responsive vehicles (e.g., semi tractor-trailer rigs) are not.
With reference now to the figures, and in particular to
Exemplary computer 101 includes a processor 103 that is coupled to a system bus 105. Processor 103 may utilize one or more processors, each of which has one or more processor cores. A video adapter 107, which drives/supports a display 109, is also coupled to system bus 105. System bus 105 is coupled via a bus bridge 111 to an input/output (I/O) bus 113. An I/O interface 115 is coupled to I/O bus 113. I/O interface 115 affords communication with various I/O devices, including a keyboard 117, a mouse 119, a media tray 121 (which may include storage devices such as CD-ROM drives, multi-media interfaces, etc.), a transceiver 123 (capable of transmitting and/or receiving electronic communication signals), and external USB port(s) 125. While the format of the ports connected to I/O interface 115 may be any known to those skilled in the art of computer architecture, in one embodiment some or all of these ports are universal serial bus (USB) ports.
As depicted, computer 101 is able to communicate with a software deploying server 149 and/or other systems 155 (e.g., establish communication with SDV 202 and/or roadway access-controlling station 206 shown in
A hard drive interface 131 is also coupled to system bus 105. Hard drive interface 131 interfaces with a hard drive 133. In one embodiment, hard drive 133 populates a system memory 135, which is also coupled to system bus 105. System memory is defined as a lowest level of volatile memory in computer 101. This volatile memory includes additional higher levels of volatile memory (not shown), including, but not limited to, cache memory, registers and buffers. Data that populates system memory 135 includes computer 101's operating system (OS) 137 and application programs 143.
OS 137 includes a shell 139, for providing transparent user access to resources such as application programs 143. Generally, shell 139 is a program that provides an interpreter and an interface between the user and the operating system. More specifically, shell 139 executes commands that are entered into a command line user interface or from a file. Thus, shell 139, also called a command processor, is generally the highest level of the operating system software hierarchy and serves as a command interpreter. The shell provides a system prompt, interprets commands entered by keyboard, mouse, or other user input media, and sends the interpreted command(s) to the appropriate lower levels of the operating system (e.g., a kernel 141) for processing. While shell 139 is a text-based, line-oriented user interface, the present invention will equally well support other user interface modes, such as graphical, voice, gestural, etc.
As depicted, OS 137 also includes kernel 141, which includes lower levels of functionality for OS 137, including providing essential services required by other parts of OS 137 and application programs 143, including memory management, process and task management, disk management, and mouse and keyboard management.
Application programs 143 include a renderer, shown in exemplary manner as a browser 145. Browser 145 includes program modules and instructions enabling a world wide web (WWW) client (i.e., computer 101) to send and receive network messages to the Internet using hypertext transfer protocol (HTTP) messaging, thus enabling communication with software deploying server 149 and other systems.
Application programs 143 in computer 101's system memory (as well as software deploying server 149's system memory) also include Roadway Access Control Logic (RACL) 147. RACL 147 includes code for implementing the processes described below, including those described in
Also within computer 101 is a positioning system 151, which determines a real-time current location of computer 101 (particularly when part of an SDV as described herein). Positioning system 151 may be a combination of accelerometers, speedometers, etc., or it may be a global positioning system (GPS) that utilizes space-based satellites to provide triangulated signals used to determine two-dimensional or three-dimensional locations.
Also associated with computer 101 are sensors 153, which detect an environment of the computer 101, including when incorporated into a vehicle. More specifically, sensors 153 are able to detect other vehicles, road obstructions, pavement, etc. For example, if computer 101 is on board a self-driving vehicle (SDV), then sensors 153 may be cameras, radar transceivers, etc. that allow the SDV to detect the environment (e.g., other vehicles, road obstructions, pavement, etc.) of that SDV, thus enabling it to be autonomously self-driven. Similarly, sensors 153 may be cameras, thermometers, moisture detectors, etc. that detect ambient weather conditions and other environmental conditions of a roadway upon which the SDV is traveling.
The hardware elements depicted in computer 101 are not intended to be exhaustive, but rather are representative to highlight essential components required by the present invention. For instance, computer 101 may include alternate memory storage devices such as magnetic cassettes, digital versatile disks (DVDs), Bernoulli cartridges, and the like. These and other variations are intended to be within the spirit and scope of the present invention.
With reference now to
While access-controlled roadway 208 is depicted as a highway, it is to be understood that in various embodiments of the present invention access-controlled roadway 208 may be any type of roadway surface capable of supporting the weight of a vehicle, such as a parking lot, a particular space in a parking lot, a tunnel, a particular lane in a roadway, a garage, a particular service bay in a maintenance garage, a bridge, an unpaved (off-road) pathway, etc.
As the SDV 202 approaches the roadway access-controlling station 206, a vehicle interrogation hardware device 212 interrogates an on-board computer (e.g., SDV on-board computer 301 described below in
Current conditions of the access-controlled roadway 208, including weather conditions, traffic conditions, construction events, mishap events, etc., can be determined and transmitted by roadway sensor(s) 218 and/or other SDVs to the supervisory computer 201 and/or directly to SDVs (e.g., SDV 202) themselves. That is, supervisory computer 201 is able to receive sensor readings from other SDVs, such as SDV 220, and/or roadway sensor(s) 218 in order to determine current roadway conditions of access-controlled roadway 208. Thus, various on-board sensors on SDV 220 (see exemplary sensors shown in
In accordance with one or more embodiments of the present invention, SDV 202 may be driven in “manual mode” or “autonomous mode”, each of which are referred to herein as an operational mode or a driving mode, where the terms “operational mode” and “driving mode” are synonymous and interchangeable.
As used and described herein, “manual mode” is defined as an SDV being at least partially under the input control of a human driver. That is, if SDV 202 is being steered by a human driver but has cruise control activated, then it is in manual mode, since SDV 202 is partially under the input control (steering) of the human driver. Thus, while in manual mode, even SDV 202 can operate as a traditional motor vehicle, in which a human driver controls the engine throttle, engine on/off switch, steering mechanism, braking system, horn, signals, etc. found on a motor vehicle. These vehicle mechanisms may be operated in a “drive-by-wire” manner, in which inputs to an SDV control processor 303 (shown in
As used and described herein, “autonomous mode” is defined as an SDV being totally controlled by hardware/software logic (e.g., SDV on-board computer 301 and/or driving mode device 307 and/or SDV control processor 303 shown in
Thus, if the sensors provide data that indicates that SDV 202 can be driven safely in manual mode while traveling on access-controlled roadway 208, then the roadway access-controlling station 206 will/may direct the SDV on-board computer 301 and/or driving mode device 307 and/or SDV control processor 303 shown in
Referring now to
As shown in
While in autonomous mode, SDV 202 operates without the input of a human driver, such that the engine, steering mechanism, braking system, horn, signals, etc. are controlled by the SDV control processor 303, which is now under the control of the SDV on-board computer 301. That is, since the SDV on-board computer 301 processes inputs taken from navigation and control sensors 309 and the driving mode device 307 (indicating that the SDV 202 is to be controlled autonomously), then driver inputs to the SDV control processor 303 and/or SDV vehicular physical control mechanisms 305 are no longer needed.
As just mentioned, the SDV on-board computer 301 uses outputs from navigation and control sensors 309 to control the SDV 202. Navigation and control sensors 309 include hardware sensors that 1) determine the location of the SDV 202; 2) sense other cars and/or obstacles and/or physical structures around SDV 202; 3) measure the speed and direction of the SDV 202; and 4) provide any other inputs needed to safely control the movement of the SDV 202.
With respect to the feature of 1) determining the location of the SDV 202, this can be achieved through the use of a positioning system such as positioning system 151 shown in
With respect to the feature of 2) sensing other cars and/or obstacles and/or physical structures around SDV 202, the positioning system 151 may use radar or other electromagnetic energy that is emitted from an electromagnetic radiation transmitter (e.g., transceiver 323 shown in
With respect to the feature of 3) measuring the speed and direction of the SDV 202, this can be accomplished by taking readings from an on-board speedometer (not depicted) on the SDV 202 and/or detecting movements to the steering mechanism (also not depicted) on the SDV 202 and/or the positioning system 151 discussed above.
With respect to the feature of 4) providing any other inputs needed to safely control the movement of the SDV 202, such inputs include, but are not limited to, control signals to activate a horn, turning indicators, flashing emergency lights, etc. on the SDV 202.
In one or more embodiments of the present invention, SDV 202 includes roadway sensors 311 that are coupled to the SDV 202. Roadway sensors 311 may include sensors that are able to detect the amount of water, snow, ice, etc. on the roadway 206 (e.g., using cameras, heat sensors, moisture sensors, thermometers, etc.). Roadway sensors 311 also include sensors that are able to detect “rough” roadways (e.g., roadways having potholes, poorly maintained pavement, no paving, etc.) using cameras, vibration sensors, etc. Roadway sensors 311 may also include sensors that are also able to detect how dark the roadway 206 is using light sensors.
Similarly, a dedicated camera 321 can be trained on access-controlled roadway 208, in order to provide photographic images describing a condition of the access-controlled roadway 208 shown in
Similarly, a dedicated object motion detector 319 (e.g., a radar transceiver capable of detecting Doppler shifts indicative of the speed and direction of movement of other vehicles and/or fixed objects) can be trained on access-controlled roadway 208, in order to detect the movement of SDV 220. Thus, signals from the object motion detector 319 can be used by the roadway access-controlling station 206 shown in
In one or more embodiments of the present invention, also within the SDV 202 are SDV equipment sensors 315. For example, SDV equipment sensors 315 may include cameras aimed at tires on the SDV 202 to detect how much tread is left on the tires. SDV equipment sensors 315 may include electronic sensors that detect how much padding is left of brake calipers on disk brakes. SDV equipment sensors 315 may include drivetrain sensors that detect operating conditions within an engine (e.g., power, speed, revolutions per minute—RPMs of the engine, timing, cylinder compression, coolant levels, engine temperature, oil pressure, etc.), the transmission (e.g., transmission fluid level, conditions of the clutch, gears, etc.), etc. SDV equipment sensors 315 may include sensors that detect the condition of other components of the SDV 202, including lights (e.g., using circuitry that detects if a bulb is broken), wipers (e.g., using circuitry that detects a faulty wiper blade, wiper motor, etc.), etc. Thus, signals from the SDV equipment sensors 315 can be used by the roadway access-controlling station 206 shown in
In one or more embodiments of the present invention, also within SDV 202 is a communications transceiver 317, which is able to receive and transmit electronic communication signals (e.g., RF messages) from and to other communications transceivers found in other vehicles, servers, monitoring systems, etc.
In one or more embodiments of the present invention, also within SDV 202 is a telecommunication device 325 (e.g., a smart phone, a cell phone, a laptop computer, etc.), which may be connected (e.g., via a near field communication—NFC connection) to the SDV on-board computer 301.
In one or more embodiments of the present invention, also within SDV 202 is at least one light sensor 329, which is able to detect the amount of light (from the sun, moon, stars, streetlights, vehicular headlights, etc.) on the access-controlled roadway 208. Thus, signals from the light sensor 329 can be used by the roadway access-controlling station 206 shown in
In one or more embodiments of the present invention, also within SDV 202 and/or SDV 220 is at least one microphone 331, which is able to detect the ambient sounds (e.g., sirens, horns, tire noise, etc.) on the access-controlled roadway 208. Thus, signals from the microphone 331 can be used by the roadway access-controlling station 206 shown in
In one or more embodiments of the present invention, also within SDV 202 is at least one chemical sensor 327, which is able to detect the presence of chemicals (e.g., gasoline fumes, pipeline leaks, etc.) on the access-controlled roadway 208. Thus, readings from chemical sensor 327 can be used by the roadway access-controlling station 206 shown in
With reference now to
After initiator block 402, a vehicle interrogation hardware device (e.g., vehicle interrogation hardware device 212 shown in
When using the roadway access-controlling station 206 shown in
As described in block 406, one or more processors (e.g., part of supervisory computer 201 shown in
For example, assume that the autonomous capability signal for SDV 202 describes that the SDV 202 is able to safely drive on wet and unlit roads even when there are up to 10 vehicles per linear mile of the roadway. Assume further that the access-controlled roadway 208 is dark and wet. If there are no more than 10 vehicles per linear mile on the access-controlled roadway 208, then SDV 202 is deemed safe to travel on the access-controlled roadway 208. However, if there are 20 vehicles per linear mile on the access-controlled roadway 208, then SDV 202 is not deemed to be safe to travel on the access-controlled roadway 208, since 10 vehicles per linear mile is the limit for SDV 202.
As described in block 410, if there is a match in conditions within a predetermined range (in factors and/or degrees of factors) in query block 408, then the roadway access-controlling station 206 determines whether the level of autonomous capability of the approaching self-driving vehicle is adequate to safely maneuver the approaching self-driving vehicle through the current roadway conditions of the access-controlled roadway (as described above).
As just indicated, the predetermined range may be in “factors” or “degrees of factors”. For example, assume that in order to safely travel on a particular roadway, an SDV needs to be able to detect roadway edges without the aid of embedded sensors in the roadway, to “see through” heavy fog, and to come to a stop within 5 seconds when traveling at 100 miles per hour. These three “factors” are therefore what is required of an SDV to travel on that roadway.
“Degrees of factors” are levels of abilities of the factors. For example, assume again that in order to safely travel on a particular roadway, an SDV needs to be able to detect roadway edges without the aid of embedded sensors in the roadway, to “see through” heavy fog, and to come to a stop within 5 seconds when traveling at 100 miles per hour. However, these different factors may be considered at different levels/degrees. For example, the ability to detect roadway edges without the aid of embedded sensors in the roadway may be the ability to stay at least 3 inches from the roadway edge based on this detection, or to stay at least 2 feet from the roadway edge based on this detection. Similarly, the ability to “see through” heavy fog may be the ability to “see through” 100 feet of fog or 300 feet or fog. Similarly, the ability to come to a stop within 5 seconds when traveling at 100 miles per hour may be more stringent (e.g., the ability to come to a stop within 4 seconds) or less stringent (e.g., the ability to come to a stop within 6 seconds). Thus, the system may require a certain “degree of factors” in order to permit the SDV 202 to travel on access-controlled roadway 208.
Thus, the certification/qualification of SDV 202 to travel on access-controlled roadway 208 may be based on basic factors (e.g., the ability to stay in a lane, peer through fog, safely stop autonomously) or certain degrees of factors (e.g., the ability to stay at least 2 feet from a roadway edge, the ability to peer through 300 feet of fog, the ability to stop within 4 seconds).
If the SDV is not deemed adequate to handle the current conditions of the access-controlled roadway 208 (query block 412), then it is prevented from entering the access-controlled roadway 208 (e.g., the automatic barricade in
The flow-chart ends at terminator block 418.
In one embodiment of the presently invention, the vehicle interrogation hardware device 212 shown in
As noted above, even though access-controlled roadway 208 is depicted as a highway, in other embodiments of the present invention the access-controlled roadway is a vehicular surface from a group consisting of street, a tunnel, a ferry, a parking spot, a service bay in a maintenance shop, etc.
In an embodiment of the present invention, the roadway access-controlling station 206 receives sensor readings from sensors (e.g., roadway sensor(s) 218 and/or sensors shown in
In an embodiment of the present invention, the roadway access-controlling station 206 only allows vehicles (either autonomous SDVs or manually operated vehicles) to enter the access-controlled roadway 208 if other similar vehicles and/or the approaching self-driving vehicle have a good safety record while traveling on the access-controlled roadway 208. Thus, the vehicle interrogation hardware device receives a description of a physical state of the approaching self-driving vehicle (what type of vehicle it is, its current mechanical/maintenance state, etc.). The roadway access-controlling station retrieves an accident history (e.g., from an accident history database in the supervisory computer 201) of other vehicles that have a same physical state as that of the approaching self-driving vehicle (202/224) while traveling on the access-controlled roadway 208. The supervisory computer 201 determines whether the accident history of the other vehicles traveling on the access-controlled roadway exceeds a predetermined limit. In response to the supervisory computer determining that the accident history of the other vehicles exceeds the predetermined limit while traveling on the access-controlled roadway, the automatic barricade controlling device 214 positions the automatic barricade 216 to block the approaching self-driving vehicle from accessing the access-controlled roadway 208.
As described herein, in an embodiment of the present invention the current roadway conditions of the access-controlled roadway include a curve radius of a curve in the access-controlled roadway being less than a predefined value.
As described herein, in an embodiment of the present invention the current roadway conditions of the access-controlled roadway include an absence of guardrails on one or more sections of the access-controlled roadway. Thus, if the access-controlled roadway 208 is missing guardrails on dangerous areas (e.g., next to a cliff), then an appropriately-enabled SDV may safely drive on the access-controlled roadway 208, but a manually operated vehicle cannot safely operate thereon, and will be prevented from entering the access-controlled roadway 208.
In one or more embodiments, the present invention is implemented in a cloud environment. It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.
Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.
Referring now to
In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 12 may be described in the general context of computer system-executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
Referring now to
Referring now to
Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.
Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.
In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and roadway access processing 96 (for selectively permitting access to a certain roadway as described herein).
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of various embodiments of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the present invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present invention. The embodiment was chosen and described in order to best explain the principles of the present invention and the practical application, and to enable others of ordinary skill in the art to understand the present invention for various embodiments with various modifications as are suited to the particular use contemplated.
Any methods described in the present disclosure may be implemented through the use of a VHDL (VHSIC Hardware Description Language) program and a VHDL chip. VHDL is an exemplary design-entry language for Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), and other similar electronic devices. Thus, any software-implemented method described herein may be emulated by a hardware-based VHDL program, which is then applied to a VHDL chip, such as a FPGA.
Having thus described embodiments of the present invention of the present application in detail and by reference to illustrative embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the present invention defined in the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4665395 | Van Ness | May 1987 | A |
| 4908988 | Yamamura et al. | Mar 1990 | A |
| 5975791 | McCulloch | Nov 1999 | A |
| 6064970 | McMillian et al. | May 2000 | A |
| 6201318 | Guillory | Mar 2001 | B1 |
| 6326903 | Gross et al. | Dec 2001 | B1 |
| 6393362 | Burns | May 2002 | B1 |
| 6502035 | Levine | Dec 2002 | B2 |
| 6587043 | Kramer | Jul 2003 | B1 |
| 6622082 | Schmidt et al. | Sep 2003 | B1 |
| 6731202 | Klaus | May 2004 | B1 |
| 6810312 | Jammu et al. | Oct 2004 | B2 |
| 7124088 | Bauer et al. | Oct 2006 | B2 |
| 7580782 | Breed et al. | Aug 2009 | B2 |
| 7769544 | Blesener et al. | Aug 2010 | B2 |
| 7877269 | Bauer et al. | Jan 2011 | B2 |
| 7894951 | Norris et al. | Feb 2011 | B2 |
| 7979173 | Breed | Jul 2011 | B2 |
| 8031062 | Smith | Oct 2011 | B2 |
| 8045455 | Agronow et al. | Oct 2011 | B1 |
| 8078349 | Prada Gomez et al. | Dec 2011 | B1 |
| 8090598 | Bauer et al. | Jan 2012 | B2 |
| 8139109 | Schmiedel et al. | Mar 2012 | B2 |
| 8140358 | Ling et al. | Mar 2012 | B1 |
| 8146703 | Baumann et al. | Apr 2012 | B2 |
| 8152325 | McDermott | Apr 2012 | B2 |
| 8180322 | Lin et al. | May 2012 | B2 |
| 8346480 | Trepagnier et al. | Jan 2013 | B2 |
| 8352112 | Mudalige | Jan 2013 | B2 |
| 8442854 | Lawton et al. | May 2013 | B2 |
| 8466807 | Mudalige | Jun 2013 | B2 |
| 8489434 | Otis et al. | Jul 2013 | B1 |
| 8583365 | Jang et al. | Nov 2013 | B2 |
| 8660734 | Zhu et al. | Feb 2014 | B2 |
| 8676466 | Mudalige | Mar 2014 | B2 |
| 8678701 | Aldasem | Mar 2014 | B1 |
| 8781964 | Martin et al. | Jul 2014 | B2 |
| 8786461 | Daudelin | Jul 2014 | B1 |
| 8810392 | Teller et al. | Aug 2014 | B1 |
| 8816857 | Nordin et al. | Aug 2014 | B2 |
| 8874305 | Dolgov et al. | Oct 2014 | B2 |
| 8880270 | Ferguson et al. | Nov 2014 | B1 |
| 8903591 | Ferguson et al. | Dec 2014 | B1 |
| 8928479 | Gonsalves et al. | Jan 2015 | B2 |
| 8948955 | Zhu et al. | Feb 2015 | B2 |
| 8949016 | Ferguson et al. | Feb 2015 | B1 |
| 8954217 | Montemerlo et al. | Feb 2015 | B1 |
| 8954252 | Urmson et al. | Feb 2015 | B1 |
| 8954261 | Das et al. | Feb 2015 | B2 |
| 8958943 | Bertosa et al. | Feb 2015 | B2 |
| 8965621 | Urmson et al. | Feb 2015 | B1 |
| 8970362 | Morley et al. | Mar 2015 | B2 |
| 8983705 | Zhu et al. | Mar 2015 | B2 |
| 8996224 | Herbach et al. | Mar 2015 | B1 |
| 9014905 | Kretzschmar et al. | Apr 2015 | B1 |
| 9024787 | Alshinnawi et al. | May 2015 | B2 |
| 9123049 | Hyde et al. | Sep 2015 | B2 |
| 9170327 | Choe et al. | Oct 2015 | B2 |
| 9189897 | Stenneth | Nov 2015 | B1 |
| 9194168 | Lu et al. | Nov 2015 | B1 |
| 9216745 | Beardsley et al. | Dec 2015 | B2 |
| 9218698 | Ricci | Dec 2015 | B2 |
| 9286520 | Lo et al. | Mar 2016 | B1 |
| 9317033 | Ibanez-guzman et al. | Apr 2016 | B2 |
| 9390451 | Slusar | Jul 2016 | B1 |
| 9399472 | Minoiu-Enache | Jul 2016 | B2 |
| 9463805 | Kirsch et al. | Oct 2016 | B2 |
| 9483948 | Gordon et al. | Nov 2016 | B1 |
| 9552735 | Pilutti et al. | Jan 2017 | B2 |
| 9566958 | Waldmann | Feb 2017 | B2 |
| 9566986 | Gordon et al. | Feb 2017 | B1 |
| 9628975 | Watkins et al. | Apr 2017 | B1 |
| 9646496 | Miller | May 2017 | B1 |
| 9834224 | Gordon et al. | Dec 2017 | B2 |
| 20020026841 | Svendsen | Mar 2002 | A1 |
| 20020128774 | Takezaki et al. | Sep 2002 | A1 |
| 20030065572 | McNee et al. | Apr 2003 | A1 |
| 20030076981 | Smith et al. | Apr 2003 | A1 |
| 20040078133 | Miller | Apr 2004 | A1 |
| 20040199306 | Heilmann et al. | Oct 2004 | A1 |
| 20050021227 | Matsumoto et al. | Jan 2005 | A1 |
| 20050104745 | Bachelder et al. | May 2005 | A1 |
| 20060106671 | Biet | May 2006 | A1 |
| 20060163939 | Kuramochi et al. | Jul 2006 | A1 |
| 20060200379 | Biet | Sep 2006 | A1 |
| 20060241855 | Joe et al. | Oct 2006 | A1 |
| 20070100687 | Yoshikawa | May 2007 | A1 |
| 20070124027 | Betzitza et al. | May 2007 | A1 |
| 20080048850 | Yamada | Feb 2008 | A1 |
| 20080065293 | Placke et al. | Mar 2008 | A1 |
| 20080114663 | Watkins et al. | May 2008 | A1 |
| 20080129475 | Breed et al. | Jun 2008 | A1 |
| 20080201217 | Bader et al. | Aug 2008 | A1 |
| 20080288406 | Seguin et al. | Nov 2008 | A1 |
| 20090094109 | Aaronson et al. | Apr 2009 | A1 |
| 20090138168 | Labuhn et al. | May 2009 | A1 |
| 20090248231 | Kamiya | Oct 2009 | A1 |
| 20090313096 | Kama | Dec 2009 | A1 |
| 20100057511 | Mansouri et al. | Mar 2010 | A1 |
| 20100156672 | Yoo et al. | Jun 2010 | A1 |
| 20100179720 | Lin et al. | Jul 2010 | A1 |
| 20100228427 | Anderson et al. | Sep 2010 | A1 |
| 20100256852 | Mudalige | Oct 2010 | A1 |
| 20110029173 | Hyde et al. | Feb 2011 | A1 |
| 20110035250 | Finucan | Feb 2011 | A1 |
| 20110077807 | Hyde et al. | Mar 2011 | A1 |
| 20110077808 | Hyde et al. | Mar 2011 | A1 |
| 20110137699 | Ben-Ari et al. | Jun 2011 | A1 |
| 20110264521 | Straka | Oct 2011 | A1 |
| 20120072243 | Collins et al. | Mar 2012 | A1 |
| 20120139756 | Djurkovic | Jun 2012 | A1 |
| 20120277947 | Boehringer et al. | Nov 2012 | A1 |
| 20120293341 | Lin | Nov 2012 | A1 |
| 20130030657 | Chatterjee et al. | Jan 2013 | A1 |
| 20130113634 | Hutchinson et al. | May 2013 | A1 |
| 20130131949 | Shida | May 2013 | A1 |
| 20130144502 | Shida | Jun 2013 | A1 |
| 20130231824 | Wilson et al. | Sep 2013 | A1 |
| 20130261871 | Hobbs et al. | Oct 2013 | A1 |
| 20140019259 | Dung et al. | Jan 2014 | A1 |
| 20140088850 | Schuberth | Mar 2014 | A1 |
| 20140092332 | Price | Apr 2014 | A1 |
| 20140095214 | Mathe et al. | Apr 2014 | A1 |
| 20140129073 | Ferguson | May 2014 | A1 |
| 20140136045 | Zhu et al. | May 2014 | A1 |
| 20140136414 | Abhyanker | May 2014 | A1 |
| 20140164126 | Nicholas et al. | Jun 2014 | A1 |
| 20140188999 | Leonard et al. | Jul 2014 | A1 |
| 20140195213 | Kozloski et al. | Jul 2014 | A1 |
| 20140201037 | Mallawarachchi et al. | Jul 2014 | A1 |
| 20140201126 | Zadeh | Jul 2014 | A1 |
| 20140214255 | Dolgov et al. | Jul 2014 | A1 |
| 20140214260 | Eckert et al. | Jul 2014 | A1 |
| 20140222277 | Tsimhoni et al. | Aug 2014 | A1 |
| 20140222577 | Abhyanker | Aug 2014 | A1 |
| 20140282967 | Maguire | Sep 2014 | A1 |
| 20140297116 | Anderson et al. | Oct 2014 | A1 |
| 20140306833 | Ricci | Oct 2014 | A1 |
| 20140309789 | Ricci | Oct 2014 | A1 |
| 20140309806 | Ricci | Oct 2014 | A1 |
| 20140309864 | Ricci | Oct 2014 | A1 |
| 20140309891 | Ricci | Oct 2014 | A1 |
| 20140310186 | Ricci | Oct 2014 | A1 |
| 20140316671 | Okamoto | Oct 2014 | A1 |
| 20140324268 | Montemerlo et al. | Oct 2014 | A1 |
| 20140330479 | Dolgov | Nov 2014 | A1 |
| 20140358331 | Prada Gomez et al. | Dec 2014 | A1 |
| 20140358353 | Ibanez-Guzman et al. | Dec 2014 | A1 |
| 20150006005 | Yu et al. | Jan 2015 | A1 |
| 20150006014 | Wimmer et al. | Jan 2015 | A1 |
| 20150026092 | Abboud et al. | Jan 2015 | A1 |
| 20150035685 | Strickland et al. | Feb 2015 | A1 |
| 20150051778 | Mueller | Feb 2015 | A1 |
| 20150057891 | Mudalige et al. | Feb 2015 | A1 |
| 20150062340 | Datta et al. | Mar 2015 | A1 |
| 20150062469 | Fleury | Mar 2015 | A1 |
| 20150066282 | Yopp | Mar 2015 | A1 |
| 20150066284 | Yopp | Mar 2015 | A1 |
| 20150070178 | Kline | Mar 2015 | A1 |
| 20150088358 | Yopp | Mar 2015 | A1 |
| 20150095190 | Hammad et al. | Apr 2015 | A1 |
| 20150120331 | Russo et al. | Apr 2015 | A1 |
| 20150134178 | Minoiu-Enache | May 2015 | A1 |
| 20150137985 | Zafiroglu et al. | May 2015 | A1 |
| 20150141043 | Abramson | May 2015 | A1 |
| 20150149018 | Attard et al. | May 2015 | A1 |
| 20150149021 | Duncan et al. | May 2015 | A1 |
| 20150160019 | Biswal et al. | Jun 2015 | A1 |
| 20150166059 | Ko | Jun 2015 | A1 |
| 20150196256 | Venkatraman et al. | Jul 2015 | A1 |
| 20150232065 | Ricci et al. | Aug 2015 | A1 |
| 20150242953 | Suiter | Aug 2015 | A1 |
| 20150293994 | Kelly | Oct 2015 | A1 |
| 20150338226 | Mason et al. | Nov 2015 | A1 |
| 20150339639 | Choe | Nov 2015 | A1 |
| 20160001781 | Fung et al. | Jan 2016 | A1 |
| 20160026182 | Boroditsky et al. | Jan 2016 | A1 |
| 20160075512 | Lert, Jr. | Mar 2016 | A1 |
| 20160078695 | McClintic et al. | Mar 2016 | A1 |
| 20160078758 | Basalamah | Mar 2016 | A1 |
| 20160090100 | Oyama et al. | Mar 2016 | A1 |
| 20160139594 | Okumura et al. | May 2016 | A1 |
| 20160140507 | Stevens et al. | May 2016 | A1 |
| 20160176409 | Kirsch et al. | Jun 2016 | A1 |
| 20160202700 | Sprigg | Jul 2016 | A1 |
| 20160205146 | Sugioka et al. | Jul 2016 | A1 |
| 20160264131 | Chan et al. | Sep 2016 | A1 |
| 20160303969 | Akula | Oct 2016 | A1 |
| 20160334797 | Ross et al. | Nov 2016 | A1 |
| 20160344737 | Anton | Nov 2016 | A1 |
| 20160355192 | James et al. | Dec 2016 | A1 |
| 20160364823 | Cao | Dec 2016 | A1 |
| 20170001650 | Park | Jan 2017 | A1 |
| 20170010613 | Fukumoto | Jan 2017 | A1 |
| 20170021830 | Feldman et al. | Jan 2017 | A1 |
| 20170021837 | Ebina | Jan 2017 | A1 |
| 20170057542 | Kim et al. | Mar 2017 | A1 |
| 20170088143 | Goldman-Shenhar et al. | Mar 2017 | A1 |
| 20170106876 | Gordon et al. | Apr 2017 | A1 |
| 20170123428 | Levinson et al. | May 2017 | A1 |
| 20170129487 | Wulf | May 2017 | A1 |
| 20170151958 | Sakuma | Jun 2017 | A1 |
| 20170168689 | Goldman-Shenhar et al. | Jun 2017 | A1 |
| 20170200449 | Penilla et al. | Jul 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 1135063 | Nov 1996 | CN |
| 2349068 | Nov 1999 | CN |
| 1376599 | Oct 2002 | CN |
| 201004265 | Jan 2008 | CN |
| 201635568 | Nov 2010 | CN |
| 202012052 | Oct 2011 | CN |
| 202038228 | Nov 2011 | CN |
| 102650882 | Aug 2012 | CN |
| 202772924 | Mar 2013 | CN |
| 104900018 | Sep 2015 | CN |
| 0582236 | Feb 1994 | EP |
| 2006003661 | Jan 2006 | WO |
| 2014058263 | Apr 2014 | WO |
| 2014066721 | May 2014 | WO |
| 2014147361 | Sep 2014 | WO |
| 2014148975 | Sep 2014 | WO |
| 2014148976 | Sep 2014 | WO |
| 2015024616 | Feb 2015 | WO |
| 2015056105 | Apr 2015 | WO |
| 2015156146 | Oct 2015 | WO |
| Entry |
|---|
| Anonymous, ‘System and Method to Target Advertisements for the Right Focus Group’. ip.com, No. 000218285, May 31, 2012, pp. 1-2. |
| Anonymous, “Car Built-In Mechanism to Enforce Mandatory Self-Driving Mode”, ip.com, No. 000234916, Feb. 14, 2014, pp. 1-3. |
| T. Horberry et al., “Driver Distraction: The Effects of Concurrent In-Vehicle Tasks, Road Enviornment Complexity and Age on Driving Performance”, Elsevier Ltd., Accident Analysis and Prevention, 38, 2006, pp. 185-191. |
| J. Miller, “Self-Driving Car Technology's Benefits, Potential Risks, and Solutions”, The Energy Collective, theenergycollective.com, Aug. 19, 2014, pp. 1-7. |
| Chen S, et al., “A Crash Risk Assessment Model for ROAS Curves”. Inproceedings 20th International Technical Conference on the Enhanced Saftey of Vehicles., 2007. Lyon, France. |
| J. Wei et al., “Towards a Viable Autonomous Driving Research Platform”, IEEE, Intelligent Vehicles Symposium (IV), 2013, pp. 1-8. |
| Anonymous, “Diagnostics Mechanism for Self-Driving Cars to Validate Self-Driving Capabilities”, ip.com, Jun. 6, 2014, pp. 1-5. ip.com. |
| Brownell, “Shared Autonomous Taxi Networks: An Analysis of Transportation Demand in NJ and a 21st Century Solution for Congestion”, Dissertation, Princeton University, 2013, pp. 1-122. |
| Sessa et al., “Blueprint of Alternative City Cyber-Mobility Take-U Scenarios”, Seventh Framework Programme Theme SST.2012.3.1-4, Automated Urban Vehicles Collaborative Project—Grant Agreement No: 314190, 2013, pp. 1-63. |
| Lutin et al., “The Revolutionary Development of Self-Driving Vehicles and Implications for the Transportation Engineering Profession”, ITE Journal 83.7, 2013, pp. 28-32. |
| A. Hars, “Self-Driving Cars: The Digital Transformation of Mobility”, Marktplatze Im Umbruch, Springer Berlin Heidelberg, 2015, pp. 539-549. |
| Jimenez et al.; “Autonomous collision avoidance system based on accurate knowledge of the vehicle surroundings”; Inst Engineering Technology-IET; IET Intelligent Transport Systems vol. 9, No. 1, pp. 105-117; 2015; England. |
| Anonymous, “Avoiding Crashes With Self-Driving Cars: Today's Crash-Avoidance Systems Are the Mile Markers to Tomorrow's Autonomous Vehicles”. Consumer Reports Magazine, Feb. 2014. Web. Sep. 22, 2016. <http://www.consumerreports.org/cro/magazine/2014/04/the-road-to-self-driving-cars/index.htm>. |
| Anonymous, “Google Files Patent for Second-Gen Autonomous Vehicle Without a Steering Wheel, Brake Pedal & More”. patentlymobile.com, Nov. 27, 2015. Web. Sep. 22, 2016. <http://www.patentlymobile.com/2015/11/GOOGLE-FILES-PATENT-FOR-SECOND-GEN-AUTONOMOUS-VEHICLE-WITHOUT-A-STEERING-WHEEL-BRAKE-PEDAL-MORE.HTML>. |
| C. Berger et al., “Cots-Architecture With a Real-Time OS for a Self-Driving Miniature Vehicle”, Safecomp 2013—Workshop ASCOMS of the 32nd International Conference on Computer Safety, Reliability and Security, Sep. 2013, Toulouse, France, pp. 1-13. |
| P. Mell et al., “NIST Definition Fo Cloud Computing”, National Institute of Standards and Tchnology, Information Technology Labratory, Sep. 2011, pp. 1-7. |
| U.S. Appl. No. 15/007,335 Non-Final Office Action dated Jun. 1, 2017. |
| List of IBM Patents or Patent Applications Treated as Related. Oct. 18, 2017. |
| Number | Date | Country | |
|---|---|---|---|
| 20180068558 A1 | Mar 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15007335 | Jan 2016 | US |
| Child | 15800214 | US |
