Patent Description:
Operation of a motor vehicle has been common place for over a century. Vehicles have long been operated by a competent operator using controls within the vehicle, such as a steering wheel and pedals. However, operator proficiency for driving a vehicle varies widely as different operators have different skill levels. As expected, a person who has years of experience driving will be more proficient in navigating roads than a person who is new to driving. Also, different driving situations require different levels of skill to drive safely. For example, an operator may be able to easily navigate certain residential areas, but may not have mastered the skillset to navigate on highways. Operator proficiency can vary by age, training, innate capability or other factors. As vehicles are inherently dangerous devices, operator competency and proficiency are valuable.

<CIT> discloses a computing device and methods for restricting driver interactions with vhicle functions based on a challenging driving environment.

<CIT> discloses an autonomous operating system for controlling permissions for partially autonomous vehicle operation.

The systems and methods described herein include determination of operator proficiency and control of one or more vehicle systems in light of said proficiency. In one embodiment, a vehicle regulation system for regulating vehicle access by an operator according to claim <NUM> is provided.

In another embodiment, a non-transitory computer-readable medium for regulating vehicle access by an operator according to claim <NUM> is provided.

In another embodiment, a method for regulating vehicle access by an operator according to claim <NUM> is provided. Embodiments of the present invention can be more clearly understood with relation to the figures and the description below.

So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope.

To facilitate understanding, identical reference numerals have been used, wherever possible, to designate identical elements that are common to the Figures. Additionally, elements of one embodiment may be advantageously adapted for utilization in other embodiments described herein.

Systems and methods described herein determine operator proficiency with one or more vehicle systems. This proficiency can then be used to restrict or allow access for the operator to said vehicle systems. Embodiments described herein leverage data from the Controller Access Network (CAN) bus, external environment sensors, and other components of the vehicle. The systems and methods monitor the operator's behavior and determine how "trustworthy" or how "skilled" they are, in the operation of the vehicle generally and in the operation of one or more components of the vehicle. In some examples, the vehicle can compare the operator's decision to what the vehicle would do in the same scenario to determine if the operator's skill level.

Once the system and methods have determined the operator's skill level (e.g., operator proficiency), the system and methods can then allow for an appropriate level of vehicle interaction and control. In one example, when maximum skill level is determined, the vehicle can permit the maximum spectrum of behavior. In this regard, the operator can then operate the vehicle in any environment and in any area. However, if the operator is not highly skilled or their normal skill level is otherwise affected (i.e., a new operator or a temporarily diminished operator), the systems and methods described herein can set a "hard ceiling" on the vehicle's capabilities in order to guarantee that the semi-autonomous and autonomous systems can keep the vehicle safe. Operational control can take the form of limiting when the operator operates the vehicle (e.g., certain times of day), where the operator operates the vehicle (e.g., city driving, residential driving, highway driving, etc.), conditions when the operator operates the vehicle (e.g., high traffic, inclement weather, etc.), other forms of operator restriction, or combinations thereof.

Further, the systems and methods described herein are adaptive to a given operator. In one example, if an operator consistently runs stop signs, the systems and methods learn that said operator is less capable, and decreases the vehicle's capabilities. If the operator then learns to stop correctly, the systems and methods can then learn this new behavior and relax the above restrictions. When applied to new operators, the systems and methods can act as a teaching tool. As the operator demonstrates competence in new scenarios, the system unlocks new vehicle capabilities (e.g., speed, freeway access, etc.). In this sense, the systems and methods described herein are a "gamification of driving performance", without actually turning driving itself into a game. The operator is given access to different functionalities as the operator's skills progress. Embodiments of the present application can be more clearly understood with relation to the figures and the description below.

Referring to <FIG>, an example of a vehicle <NUM> is illustrated. As used herein, a "vehicle" is any form of motorized transport. In one or more implementations, the vehicle <NUM> is an automobile. While arrangements will be described herein with respect to automobiles, it will be understood that embodiments are not limited to automobiles. In some implementations, the vehicle <NUM> may be any other form of motorized transport that, for example, can operate autonomously, semi-autonomously, or manually by an in-vehicle operator. The vehicle <NUM> can include a vehicle regulation system <NUM> or capabilities to support a vehicle regulation system <NUM>, and thus benefits from the functionality discussed herein.

The vehicle <NUM> also includes various elements. It will be understood that in various embodiments it may not be necessary for the vehicle <NUM> to have all of the elements shown in <FIG>. The vehicle <NUM> can have any combination of the various elements shown in <FIG>. Further, the vehicle <NUM> can have additional elements to those shown in <FIG>. In some arrangements, the vehicle <NUM> may be implemented without one or more of the elements shown in <FIG>. While the various elements are shown as being located within the vehicle <NUM> in <FIG>, it will be understood that one or more of these elements can be located external to the vehicle <NUM>. Further, the elements shown may be physically separated by large distances.

Some of the possible elements of the vehicle <NUM> are shown in <FIG> and will be described along with subsequent figures. However, a description of many of the elements in <FIG> will be provided after the discussion of <FIG> for purposes of brevity of this description. Additionally, it will be appreciated that for simplicity and clarity of illustration, where appropriate, reference numerals have been repeated among the different figures to indicate corresponding or analogous elements. In addition, the discussion outlines numerous specific details to provide a more thorough understanding of the embodiments described herein.

The vehicle regulation system <NUM> is more clearly described with reference to <FIG>. The vehicle regulation system <NUM> is shown as including a processor <NUM> from the vehicle <NUM>, depicted in <FIG>. Accordingly, the processor <NUM> can be a part of the vehicle regulation system <NUM>, the vehicle regulation system <NUM> can include a separate processor from the processor <NUM> or the vehicle regulation system <NUM> can access the processor <NUM> through a data bus or another communication path. In one embodiment, the vehicle regulation system <NUM> includes the memory <NUM> that stores a measurement module <NUM>, a comparison module <NUM> and an evaluation module <NUM>. The memory <NUM> is a random-access memory (RAM), read-only memory (ROM), a hard-disk drive, a flash memory, or other suitable memory for storing the modules <NUM>, <NUM>, and <NUM>. The modules <NUM>, <NUM>, and <NUM> are, for example, computer-readable instructions that when executed by the processor <NUM>, cause the processor <NUM> to perform the various functions disclosed herein.

The measurement module <NUM> generally includes instructions that function to control the processor <NUM> to determine, using driving capacity information <NUM>, a driving capacity metric <NUM> for an operator in a vehicle. More specifically, the driving capacity information <NUM> broadly covers information on the operator's performance and personal characteristics while operating the vehicle <NUM>, such as behaviors, mannerisms, personality, medical information, and others that may directly or indirectly relate to performance while operating a vehicle. The driving capacity information <NUM> can include the ability of the operator to handle one or more vehicle systems of a vehicle as they relate to operating the vehicle, such as a propulsion system <NUM>, a braking system <NUM>, a steering system <NUM>, a signaling system <NUM>, other systems, and combinations thereof. In one example, the driving capacity information <NUM> can include driving experience, ability to control any or all of the vehicle systems, specific environments the operator is accustomed to, changes in capacity over time, medical information about the operator (e.g., sundown syndrome, onset of dementia, etc.), sensor data, or other information about the operator which can be related to driving capability.

The driving capacity information <NUM> can include information collected using one or more sensors. The sensors, as used herein, can include sensors which are positioned either internal (e.g., positioned inside the vehicle) or external (positioned on the exterior of the vehicle). Exemplary sensors, which can be adapted for the systems and methods described herein, include image capture devices (e.g., cameras, thermal imaging), audio devices (e.g., microphones), and others. The sensors can be part of the sensor system <NUM>, depicted as part of the vehicle <NUM> of <FIG>. In one embodiment, the measurement module <NUM> can receive driving capacity information <NUM> using the sensor system <NUM>. The measurement module <NUM> can receive data from the sensor system <NUM> prior to, during or after an operator has driven the vehicle. Data collected by the sensors about the operator, which can be used in producing the driving capacity information <NUM>, includes facial expressions, gaze, positioning, actions which result in vehicle movement, attentiveness and alertness, and others. As such, the driving capacity information <NUM> is information related to the driving capacity of an operator and can include the driving capacity metric <NUM>.

The driving capacity metric <NUM> is information collected by the vehicle regulation system <NUM> regarding the operator's performance with one or more of the vehicle systems <NUM>. The driving capacity metric <NUM> can be stored as part of the driving capacity information <NUM>. The driving capacity metric <NUM> can be expressed numerically, such as a series of numbers or ranges which indicate some portion of the operator's performance regarding one or more systems. The driving capacity metric <NUM> can be a collection of one or more indicators of the operator's driving capacity. In one embodiment, the driving capacity metric <NUM> can be a series of measurements related to driving characteristics. The driving capacity metric <NUM>, though inherently related to the vehicle system <NUM> it was sourced from, can be applicable, directly or indirectly, to each of the vehicle systems <NUM>. Exemplary embodiments of the driving capacity metric <NUM> include change in position, velocity, acceleration, surging, distance from obstacles, maintenance of lane position and others. Further embodiments are envisioned without specific recitation herein.

The measurement module <NUM>, using the sensor system <NUM>, further collects information about the environment, which are used in evaluating the proficiency level <NUM> of the operator. In one embodiment, the measurement module <NUM> can make a determination of how the operator should perform under a specific set of driving conditions. As such, the measurement module <NUM> can collect environmental information <NUM> which can form the basis for the vehicle regulation system <NUM> determination of the expected operator driving behavior. The environmental information <NUM> can include information collected from the environment around the vehicle <NUM> during one or more time points. In one embodiment, the environmental information <NUM> includes information about the position of the vehicle, the atmospheric conditions, time of day, traffic levels, general location type (neighborhood, highway, etc.) and others. Using the environmental information <NUM> and the driving capacity information <NUM>, the measurement module <NUM> can make an evaluation of the operator capability, which can be stored as part of the driving capacity metric <NUM>.

The comparison module <NUM> generally includes instructions that function to control the processor <NUM> to evaluate a vehicle system <NUM> of the vehicle <NUM> for a vehicle system proficiency <NUM>. The vehicle systems <NUM>, as described above with reference to <FIG>, can include a vehicle system proficiency <NUM>. The vehicle system proficiency <NUM> is the operator proficiency that vehicle regulation system <NUM> has designated as the boundary of access or removal of limitations to one or more of the vehicle systems <NUM>. The vehicle system proficiency <NUM> can be individualized to specific vehicles systems or provided generally. In some embodiments, the vehicle system proficiency <NUM> can be tiered, in that all systems of a specific level are made available, once the operator is determined to have a driving capacity metric <NUM> which qualifies the operator for that level of access. In other embodiments, the vehicle system proficiency <NUM> is individually associated, such that the access levels available to the operator are controlled with respect to operator performance with that vehicle system.

The comparison module <NUM> can further include instructions to compare the driving capacity metric <NUM> and the vehicle system proficiency <NUM>. Once the vehicle system proficiency <NUM> has been established, the driving capacity metric <NUM> can be compared with the vehicle system proficiency <NUM>. The comparison from the comparison module <NUM> can include qualitative measurements (e.g., the operator is performing steering functions at an "average level") and quantitative measurements (e.g., minimum vehicle system proficiency for access to the steering system is <NUM> out of <NUM>, and the driving capacity metric <NUM> for the operator is <NUM>). The vehicle system proficiency <NUM> can include both the limits of human operation of the vehicle and the limits of the vehicle systems <NUM>. As such, the vehicle system proficiency <NUM> can be vehicle specific, having limitations related to a specific operator and/or a specific vehicle. As well, the vehicle system proficiency <NUM> can change over time as the vehicle systems <NUM> deteriorate or are repaired. In further embodiments, the vehicle system proficiency <NUM> can change over time to reflect the limits of safe operation of a system which has more usage or deterioration.

In a further embodiment, the driving capacity metric <NUM> for the operator at a first system can be compared or considered in the comparison of the driving capacity metric <NUM> for the operator at a second system. In one example, the driving capacity metric <NUM> for the operator at the steering system <NUM> (i.e., the second system) compares favorably with the vehicle system proficiency <NUM> for the steering system <NUM>. However, the driving capacity metric <NUM> for the operator at the propulsion system <NUM> (i.e., the first system) compares unfavorably with the vehicle system proficiency <NUM> for the propulsion system <NUM>. The comparison module <NUM> can then use the comparison at the propulsion system <NUM> in the comparison at the steering system <NUM>, or vice versa.

The evaluation module <NUM> generally includes instructions that function to control the processor <NUM> to determine, using the comparison, a proficiency level <NUM> of the operator for the vehicle system. The proficiency level <NUM> of the operator is the operator's competence and proficiency, as determined from the driving capacity metric, for the vehicle systems being considered. The proficiency level <NUM> of the operator can be determined with regards to an anticipated behavior <NUM>. The anticipated behavior <NUM> can be a vehicle control behavior, expected by the vehicle regulation system <NUM>, from the operator. The anticipated behavior <NUM> can be derived from a variety of sources, including collected operator information (e.g., the use of a plurality of operator sources to create an operator model), optimal operator information (e.g., an expert operator), vehicle control models (e.g., expected operator behavior based on the operations of an autonomous driving system), or others which can provide an indication of the expected operator behavior. The anticipated behavior <NUM> can include proper turning, the berth given to other vehicles, maintenance of traction, control under specific driving conditions, action timing, attentiveness, and other safety and vehicle control related factors.

The evaluation module <NUM> can further include instructions to control the vehicle systems <NUM> in light of the proficiency level <NUM>. The evaluation module <NUM> can be in communication with one or more systems or devices in the vehicle <NUM>, such as the data store <NUM>, the sensor system <NUM>, the vehicle systems <NUM>, the autonomous driving module <NUM>, the augmented reality system <NUM>, other systems, or combinations thereof. The evaluation module <NUM> can then either stop or limit access to a connected system, such that the operator level of access to said system reflects the proficiency level <NUM>. The evaluation module <NUM> can further forward guidance to the operator with regard to various restrictions and allowances in the vehicle systems <NUM>. The evaluation module <NUM> can include providing information in a graphical or verbal form to the operator in the vehicle <NUM>, such as through an augmented reality system <NUM>, described with reference to <FIG>.

In an optional embodiment, the anticipated behavior <NUM> can be stored as part of the operator model <NUM>. The operator model <NUM> is a collection of information which provides guidance to the vehicle regulation system <NUM> regarding the quality of one or more driving behaviors and actions. The operator model <NUM> can include driving information collected regarding one or more operators. In this embodiment, the driving information regarding the one or more operators can be used in determining the anticipated behavior <NUM>. In one example, the driving information is used to create a model to predict the anticipated behavior. In another example, the driving information is used to select or modify a preexisting model. One skilled in the art will understand the various permutations available for the use of said driving information.

As noted above, the proficiency level <NUM> can be either tiered or individually-associated implementations. In a tiered implementation, the proficiency level for one or more vehicle systems <NUM> is generalized into a skill range, such as a skill range from novice to expert. In one example of a tiered implementation, once the driving capacity metric <NUM> reaches a level considered to be intermediate, all vehicle systems <NUM> are made available in non-highway environments. In individually-associated implementations, the proficiency level <NUM> for each of the vehicle systems <NUM> is presented individually and vehicle systems <NUM> are controlled based on said individual measurement. In one example of an individually associated implementation, the driving capacity metric <NUM> is determined for steering, braking, control, responsiveness and others, such that the availability of each system is dependent on the individual metric. Other embodiments are contemplated without specific recitation herein.

The evaluation module <NUM> can further include instructions to provide access to the vehicle systems based on the proficiency level <NUM>. In embodiments described herein, the vehicle <NUM>, through the vehicle regulation system <NUM>, can control access to the vehicle systems <NUM>. The evaluation module <NUM> can limit or allow access to one or more vehicle systems <NUM>. In another embodiment, the evaluation module <NUM> can allow access to portions of vehicle systems <NUM>, such as restricting the vehicle speeds. In further embodiments, the evaluation module <NUM> can control access to the vehicle systems <NUM> based on environmental parameters, such as time of day or location that the operator intends to operate the vehicle <NUM>.

Further, the evaluation module <NUM> can include instructions to modulate access to the vehicle systems <NUM> based on a variety of events, such as over time, based on health conditions, or as the proficiency level <NUM> of the operator improves. The vehicle regulation system <NUM> can update over time, collecting information related to the proficiency level <NUM> of the operator. The proficiency level <NUM> can be determined with relation to time of day (e.g., improvement when the sun is up), location (e.g., operator drives more proficiently in neighborhoods), or others. Further, the vehicle regulation system <NUM>, as described above, can be adaptive to multiple operators. The vehicle regulation system <NUM>, through the modules <NUM>, <NUM> and <NUM>, can create multiple profiles. Each profile, as associated to a specific operator, can include the individual proficiency level <NUM> of each operator, such that each operator has access to the vehicle systems <NUM> based on individual capacity.

<FIG> depicts a schematic of the vehicle regulation system <NUM>, according to one or more embodiments. The vehicle regulation system <NUM> collects information regarding the operator and the environment, through measurement module <NUM>. This information is forwarded to the comparison module, which sets the boundaries for access to the systems and compares the operator proficiency to said boundaries. The comparison from the comparison module <NUM> is then forwarded to the evaluation module <NUM>, which determines the operator proficiency and allows access based on said proficiency
As shown here, the measurement module <NUM> receives input from a sensor system, such as the sensor system <NUM>. The information received can include information regarding operator performance in operating the vehicle <NUM> and information about the environment and surroundings. The sensors of the sensor system <NUM> can include image capture devices, audio capture devices, LIDAR, RADAR, and others. The information received can then be processed by the measurement module <NUM> to driving capacity information <NUM> and environmental information <NUM>, described above with reference to <FIG>. The driving capacity information <NUM>, including the driving capacity metric <NUM>, and environmental information <NUM> can then be forwarded to the to the comparison module <NUM>.

The comparison module <NUM> can then apply the driving capacity metric <NUM> and the environmental information <NUM> to a determined vehicle system proficiency <NUM>. Initially, the comparison module <NUM> forms a vehicle system proficiency <NUM>. The vehicle system proficiency <NUM> can be created based on the environmental information <NUM>, circumstantial expectations based on other operator performance or model systems (e.g., the operator model <NUM>), or others. As stated above, the operator model <NUM> can be derived from a number of sources, both local to the vehicle <NUM> and remote (e.g., a server <NUM> via the "cloud" <NUM>). The driving capacity metric <NUM> can then be applied to the vehicle system proficiency, in light of the environmental information <NUM> which is relevant to operator performance. The driving capacity metric <NUM> is shown here as a separate element, but it is to be understood that the driving capacity metric <NUM> can be a portion of the driving capacity information <NUM>, described above with reference to <FIG>.

Further, the driving capacity information <NUM> can be applied to determining or otherwise modifying the comparison of the driving capacity metric <NUM> with the vehicle system proficiency <NUM>. In one example, the driving capacity information <NUM> includes information regard operator road rage. In this instance, the operator would be otherwise qualified to access the vehicle systems <NUM>. However, based on this road rage information and information regarding highway traffic, the vehicle regulation system <NUM> can then modify the comparison to reflect the above information. One skilled in the art will understand the variety of permutations available regarding the above comparison. Other embodiments are contemplated without specific recitation herein.

The comparison module <NUM> can then forward the comparison to the evaluation module <NUM>. The evaluation module <NUM> can then determine the proficiency level <NUM> from the comparison, as described above with reference to <FIG>. The proficiency level of the operator is then used to determine the regulation of the vehicle systems <NUM> for that operator. The evaluation module <NUM> can further be updated, such that as the driving capacity metric <NUM> changes, the proficiency level <NUM> and the access to the vehicle systems <NUM> changes accordingly. Access to the vehicle systems <NUM> can be modified in a number of ways. In one example, if an operator does not have a proficiency level <NUM> which allows for access to one or more vehicle systems <NUM>, control of said vehicle systems <NUM> can be given to an autonomous driving module, such as the autonomous driving module <NUM>. In another example, the vehicle regulation system <NUM> can control said vehicle systems <NUM>. In another example, access to said vehicle systems can be limited rather than stopped entirely, with or without autonomous control of the vehicle systems to complement operator control.

Thus, the vehicle regulation system <NUM> can use the operator proficiency and performance to control the vehicle <NUM>, thus providing numerous benefits to the operator and to the public. The vehicle regulation system <NUM> increase safety on the road by controlling autonomously for the operator, when the operator may not be capable of manual control. Further, the vehicle regulation system <NUM> can help an operator learn to drive more safely by educating the operator about the vehicle regulations. Finally, the vehicle regulation system <NUM> can change control levels over time, thus reaffirming the operator's confidence and providing appropriate vehicle access as driving proficiency changes.

<FIG> depicts an operator <NUM> in an interior portion <NUM> of the vehicle <NUM>, according to embodiments described herein. In this embodiment, the vehicle <NUM> incorporates the vehicle regulation system <NUM>. The operator <NUM> is positioned in the operator seat <NUM> of the vehicle <NUM>. The vehicle <NUM> can be semi-autonomous or autonomous, as described with reference to <FIG>. Generally, the vehicle <NUM> can include a windshield <NUM> and a dashboard <NUM>, and a mirror <NUM>. The vehicle <NUM> can further include internal sensors <NUM>, such as an image capture device 312a and 312b (e.g., a camera or an infrared sensor) and/or one or more audio capture devices 314a and 314b (e.g., microphones or SONAR). In some embodiments, the image capture devices 312a and 312b and the audio capture devices 314a and 314b are integrated into the vehicle <NUM>, such as into the dashboard <NUM> and/or the mirror <NUM>. The sensors used in embodiments described herein can further include external sensors 330a and 330b, which can be one or more of the sensors described as part of the sensor system <NUM> in <FIG>.

In the exemplary embodiment shown here, the vehicle regulation system <NUM> begins through instructions from the measurement module <NUM>. The measurement module <NUM> includes instructions to collect driving capacity information <NUM> for the operator <NUM>. The vehicle regulation system <NUM> can begin with the operator <NUM> operating the vehicle <NUM> through one or more locations, such as neighborhoods, highways, off road, or other locations which vehicles may be operated. The measurement module <NUM> then accesses one or more internal sensors, such as the image capture devices 312a and 312b and/or the audio capture devices 314a and 314b. The image capture devices 312a and 312b can be any device capable of collecting images of one or more objects, such as a video camera. The image capture devices 312a and 312b can be positioned to collect images of a portion of the interior portion <NUM> of the vehicle <NUM>. In one embodiment, the image capture device <NUM> is positioned in the interior portion <NUM> of the vehicle <NUM>, such as integrated with the dashboard <NUM> or the mirror <NUM>.

The measurement module <NUM>, through the internal sensors <NUM>, can collect information regarding the driving capacity information <NUM> of the operator <NUM>, including attention span, focus, spatial recognition, knowledge of applicable driving laws based on location, maneuvering, acceleration, and others. In the embodiment depicted here, the measurement module <NUM> uses the image capture devices 312a and 312b and the audio capture devices 314a and 314b to collect speech, direction of gaze, movement of the steering wheel, positioning and posture, and others from the operator <NUM>. Further vehicle sensors from the sensor system <NUM> (e.g., fuel flow sensors, GPS sensors, and others) can be incorporated into the driving capacity information <NUM> and used provide real time measurement of vehicle action and performance.

The operator <NUM> can operate the vehicle <NUM> in a standard fashion while the measurement module <NUM> collects information about the operator <NUM>. The vehicle regulation system <NUM> can have a default level of access prior to a determination of the proficiency level <NUM> of the operator. The default level of access can be full access, limited access, or others as determined by the vehicle regulation system <NUM>, the operator <NUM> or the end user. The vehicle regulation system <NUM> can collect the driving capacity information <NUM> over a period of time, such as a period of days, weeks or months. The driving capacity information <NUM> can include the driving capacity metric <NUM> for the operator <NUM>. The driving capacity metric <NUM> can include data points for specific vehicle system <NUM>, based on the operator's performance in the vehicle <NUM>. The above data and information can be collected simultaneously with the environmental information <NUM>, which can used to indicate the result of the actions and observations through association with the driving capacity information <NUM>.

In a further embodiment, the operator <NUM> can have operated the vehicle <NUM> or another vehicle having at least a portion of the vehicle regulation system <NUM> one or more previous times. In this case, the vehicle regulation system <NUM> can have the driving capacity information <NUM>, the driving capacity metric, and/or the environmental information <NUM> previously stored in the database <NUM> or in another data store. In this embodiment, the vehicle regulation system <NUM> can access or retrieve the driving capacity information <NUM> and/or the environmental information <NUM>, for use in determining the vehicle regulation described herein. In the example shown here, the operator <NUM> has full access to the vehicle systems <NUM>, by default.

The vehicle regulation system <NUM>, using the measurement module <NUM>, can forward the driving capacity information <NUM>, the driving capacity metric <NUM>, the environmental information <NUM>, and/or the operator model <NUM> to the comparison module <NUM>. The comparison module <NUM> can include instructions to determine or acquire the vehicle system proficiency <NUM>, in light of the environmental information <NUM>. The vehicle system proficiency <NUM> can be determined while the vehicle <NUM> is being operated by the operator <NUM>. Further, the vehicle system proficiency <NUM> can incorporate the operator model <NUM>. As the operator <NUM> controls the vehicle <NUM> during normal operation, the capabilities of the vehicle systems <NUM> can be detected by the vehicle regulation system <NUM>. In the example shown here, the operator <NUM> is operating the vehicle <NUM> on a neighborhood street. Further examples can include different locations, higher rates of speed or other factors which can be used to differentiate the capabilities of the various vehicle systems <NUM>.

During this time, the vehicle regulation system <NUM> is collecting information regarding proper movement of the steering column, abnormal changes in position of the vehicle, maintenance of traction between the tires and the road, quality of fuel flow during acceleration, proper oxygen mixture, and other operational characteristic of the vehicle <NUM>. This information can be collected by either the measurement module <NUM>, the comparison module <NUM> or combinations thereof. The above information can be compared with the operator model <NUM> to create the vehicle system proficiency make a determination of the inputs from a possible operator (e.g., operator <NUM>) which can maintain control and/or safety for each of the system of the vehicle <NUM>, otherwise referred to as the vehicle system proficiency <NUM>.

The comparison module <NUM> can further include instructions to compare the driving capacity metric <NUM> to the vehicle system proficiency <NUM>, in light of driving capacity information <NUM>. As described above, the vehicle system proficiency <NUM> includes inputs or input ranges which can maintain safety and/or control of each of the vehicle systems <NUM>. Thus, the inputs received from the operator <NUM> can then be compared to the vehicle system proficiency <NUM> for at least one of the vehicle systems <NUM>. The comparison can be a determination of whether the driving capacity metric <NUM> falls within or near the vehicle system proficiency <NUM>. In further embodiments, the comparison of the comparison module <NUM> can be based on proximity to the input or input ranges set by the vehicle system proficiency <NUM>. The comparison of the comparison module <NUM> can further include statistical measures of the driving capacity metric <NUM> to the vehicle system proficiency <NUM>. In one example, the operator <NUM> can have made a total of six (<NUM>) turns at an intersection <NUM>. Of the six turns, only five (<NUM>) could have been deemed proficient with the sixth turn being deemed inadequate by a wide margin. In this case, an average might indicate an outlying driving capacity metric <NUM> for the steering system <NUM>. However, standard deviations or exclusion of outliers in the driving capacity metric <NUM> can indicate that the operator <NUM> falls within the vehicle system proficiency <NUM> as described above.

The evaluation module <NUM> can then apply the comparison from the comparison module <NUM> to determine the proficiency level of the operator <NUM>. A comparison of the information from the operator <NUM>, including vehicle system proficiency <NUM> and the driving capacity metric <NUM>, can then be analyzed in light of driving events, conditions and situations provided by the environmental information <NUM> and the driving capacity information <NUM>, to determine the proficiency level <NUM> of the operator <NUM>. Thus, in this way, the evaluation module <NUM> can act as a check on the comparison at the comparison module <NUM>.

Using the example from above, the operator <NUM> is driving neighborhood streets and had one inadequate turn of six total turns at the intersection <NUM>. As noted above, the average of the driving capacity metric <NUM> indicated an outlying driving capacity metric <NUM> for the steering system <NUM>. Here, as the evaluation module <NUM> reviews the driving capacity information <NUM> for information which explains the measurements of the driving capacity metric <NUM>. Further, the evaluation module <NUM> can review the environmental information <NUM> for information which correlates the real world events with the driving capacity metric <NUM>. In this review, the evaluation module <NUM> can recognize from the environmental information <NUM> that during the inadequate turn, an animal crossed into the intersection <NUM>. The evaluation module <NUM> can then confirm, using the driving capacity information <NUM> that the actions of the operator <NUM> were consistent with an evasive maneuver to avoid the animal. The evaluation module <NUM> can then choose to exclude the inadequate turn from the evaluation, and determine that the proficiency level <NUM> accordingly, based on the driving capacity information <NUM> and the environmental information <NUM>. One skilled in the art will understand that the above example can be expanded to a variety of events.

With the determination of the proficiency level <NUM> made, the evaluation module <NUM> can then provide or control access to the vehicle systems <NUM>. As stated for the above example, the vehicle systems <NUM> are available to the operator <NUM>, by default. Here, the evaluation module <NUM> has determined that the operator <NUM> has a proficiency level <NUM> which is adequate for the steering system <NUM>. As such, the evaluation module <NUM> maintains full access for the operator <NUM>. In further embodiments, the evaluation module <NUM> can move from a reduced/restricted access to full access, full access to reduced/restricted access, or others as the situation permits.

In further embodiments, the vehicle regulation system <NUM>, through the evaluation module <NUM>, can provide information to the operator <NUM> regarding the proficiency level <NUM>. In one embodiment, the evaluation module <NUM> can include instructions to provide information to the operator <NUM> using a console display <NUM>. In another embodiment, the evaluation module <NUM> can include instructions to provide information to the operator <NUM> using an augmented reality system <NUM>, shown here as an operator display <NUM>. In either the console display <NUM> or the augmented reality system embodiment, the evaluation module <NUM> provides useful data or guidance to the operator <NUM> regarding the proficiency level <NUM>. In one example, the evaluation module <NUM> provide the proficiency level <NUM> and appropriate explanation for the operator <NUM> or for other operators. The evaluation module <NUM> further offers guidance regarding corrective measures or other hints to help the operator <NUM> improve his or her driving.

The vehicle regulation system <NUM> can provide numerous benefits to a vehicle operator. The vehicle regulation system <NUM> can provide insights into the vehicle operator's driving style and habits and, if there are areas for improvement, guidance for improving their driving. Further, the vehicle regulation system <NUM> can make the roads safer by restricting driving for the operator, if the operator does not show sound decision making or skill during vehicle operation.

<FIG> is a flow diagram of a method <NUM> for regulating vehicle access by an operator, according to one or more embodiments. The method can include determining the proficiency level of the operator, either prior to, during or after operation of the vehicle. Once the operator proficiency level has been established, the method can determine what level of control the operator can safely handle for the vehicle. The level of control can be tiered, situations or others, as described above with regards to the vehicle regulation system <NUM> and as described herein. The method <NUM> can include determining a driving capacity metric for an operator in a vehicle, at <NUM>. A vehicle system of the vehicle can then be evaluated for a vehicle system proficiency, at <NUM>. The driving capacity metric and the vehicle system proficiency can then be compared, at <NUM>. Using the comparison, a proficiency level of the operator can be determined for the vehicle system, at <NUM>. Then, access to the vehicle systems can be provided based on the proficiency level, at <NUM>.

The method <NUM> can begin with determining a driving capacity metric for an operator in a vehicle, at <NUM>. The driving capacity metric is a determination of driving capability for the operator at one or more vehicle systems. The driving capacity metric can include individual or overall skill levels of the operator related to the vehicle systems. In one embodiment, the driving capacity metric are numerical metrics. The driving capacity metric can be substantially similar to the driving capacity metric <NUM>, described with reference to <FIG> and <FIG>. The driving capacity metric can be determined based on collected information from one or more sensors, such as the sensor system <NUM>. As above, the driving capacity metric can be individualized to the specific vehicle system of the vehicle systems <NUM> or the driving capacity metric can be tiered. In further embodiments, the driving capacity metric can be collected by an external source, such as another vehicle, a simulator or others.

In some embodiments, the driving capacity metric can change with operator proficiency. Operator proficiency in a function of experience, practice, age, health, and other factors. As such, the driving capacity metric is expected to change over time. The method <NUM> can include changing the driving capacity metric based on operator proficiency changes. Further, the method <NUM> can include individual driving capacity metrics for each operator. In one or more embodiments, the driving capacity metric can be determined as part of a system, such as the vehicle regulation system <NUM> described with reference to <FIG> and <FIG>. In one embodiment, the measurement module <NUM> of the vehicle regulation system <NUM> can include instructions to determine, using driving capacity information, the driving capacity metric for an operator in a vehicle. The driving capacity metric can include collecting information using one or more sensors, such as the sensor system <NUM> of the vehicle <NUM>. The driving capacity metric can be stored as part of a database, such as the database <NUM> of the vehicle <NUM>.

The vehicle system of the vehicle can then be evaluated for a vehicle system proficiency, at <NUM>. The method <NUM> can then determine the vehicle system proficiency for the vehicle systems <NUM>. The vehicle system proficiency is the proficiency that the method <NUM> uses to mediate access to the vehicle systems <NUM>. The vehicle system proficiency can be substantially similar to the vehicle system proficiency <NUM>, described with reference to <FIG> and <FIG>. The vehicle system proficiency can be determined with relations to the environmental information, the operator model, and others. The vehicle system proficiency can be individualized to a specific vehicle system, tiered to reflect ability to control the vehicle systems generally, or others. The vehicle system proficiency can include various parameters for proficiency, including time of day, location of said operation, inclement weather, and others. Further, the vehicle system proficiency can change over time, based on vehicle deterioration, environmental changes, and others.

In one or more embodiments, the vehicle system proficiency can be determined as part of a system, such as the vehicle regulation system <NUM> described with reference to <FIG> and <FIG>. In one embodiment, the comparison module <NUM> of the vehicle regulation system <NUM> can include instructions to evaluate the vehicle system of the vehicle for a vehicle system proficiency, such as the vehicle system <NUM> of the vehicle <NUM>. The driving capacity metric can include collecting information using one or more sensors, such as the sensor system <NUM> of the vehicle <NUM>. The vehicle system proficiency can be stored as part of a database, such as the database <NUM> of the vehicle <NUM>.

The driving capacity metric and the vehicle system proficiency can then be compared, at <NUM>. The driving capacity metric reflects the capability of the operator, whereas the vehicle system proficiency denotes the effective boundary or boundaries before one or more levels of access to a system are available. As such, the method <NUM> compares the driving capacity metric and determines where the driving capacity metric falls, as compared to the vehicle system proficiency. The comparison from the method <NUM> can include determining relative proximity between the driving capacity metric and the vehicle system proficiency. In one or more embodiments, the comparison can be performed as part of a system, such as the vehicle regulation system <NUM> described with reference to <FIG> and <FIG>. In one embodiment, the comparison module <NUM> of the vehicle regulation system <NUM> can include instructions to determine, using driving capacity information, the driving capacity metric for an operator in a vehicle. The driving capacity metric can include collecting information using one or more sensors, such as the sensor system <NUM> of the vehicle <NUM>. The driving capacity metric can be stored as part of a database, such as the database <NUM> of the vehicle <NUM>.

Using the comparison, a proficiency level of the operator can be determined for the vehicle system, at <NUM>. The method <NUM> can determine the proficiency level of the operator using the comparison, environmental information, driving capacity information, or others. The environmental information can include information collected from the environment around the vehicle during one or more time points. The driving capacity information can include information collected with relations to the driving capacity metric. In one embodiment, the driving capacity metric provides a numerical indication of adequate or inadequate proficiency for the driving systems, while environmental information and driving capacity information provide guidance with regard to the circumstances of the driving capacity metric.

The driving capacity information, the driving capacity metric, and the environmental information can be substantially similar to the driving capacity information <NUM>, the driving capacity metric <NUM>, and the environmental information <NUM> of the vehicle regulation system <NUM>, described with reference to <FIG> and <FIG>. In one or more embodiments, the proficiency level can be determined as part of a system, such as the vehicle regulation system <NUM> described with reference to <FIG> and <FIG>. In one embodiment, the evaluation module <NUM> of the vehicle regulation system <NUM> can include instructions to determine, using the comparison, a proficiency level of the operator for the vehicle system. The proficiency level can be derived using the driving capacity information <NUM>, the driving capacity metric <NUM>, and the environmental information <NUM>. The driving capacity information <NUM>, the driving capacity metric <NUM>, and the environmental information <NUM> can be collected using one or more sensors, such as the sensor system <NUM> of the vehicle <NUM>. The proficiency level <NUM> can be stored as part of a database, such as the database <NUM> of the vehicle <NUM>.

Then, access to the vehicle systems is provided based on the proficiency level, at <NUM>. With the proficiency level determined, the method <NUM> can then alter vehicle system access in light of the proficiency level. In vehicles which start with full access by default, the method <NUM> can reduce access in light of inadequate proficiency levels or otherwise maintain said vehicle system access. In vehicles which start with limited or no access, the method <NUM> increases vehicle system access in light of adequate proficiency levels, maintain limited to no access in light of inadequate proficiency levels, or otherwise alter access to reflect adequate or inadequate proficiency levels.

In further embodiments, the method <NUM> can offer guidance to the operator related to the proficiency level. The guidance can include the operator proficiency level, explanation as to the scoring and the measurements, and possible areas of improvement. The guidance can be delivered verbally, such as through a display. One such display, which can be adapted for the method <NUM>, is the display <NUM> of the vehicle <NUM>, described with reference to <FIG>. In one or more embodiments, the vehicle system access can be provided as part of a system, such as the vehicle regulation system <NUM> described with reference to <FIG> and <FIG>. In one embodiment, the evaluation module <NUM> of the vehicle regulation system <NUM> can include instructions to provide access to the vehicle systems based on the proficiency level. The access to the vehicle systems <NUM> of the vehicle <NUM> can reflect the proficiency level <NUM> of the operator, as described above.

The method <NUM> described herein can control access to one or more vehicle systems, based on the proficiency level of the operator. As such, the method <NUM> provides numerous benefits to both the operator and the surrounding environment. The method <NUM> can provide control limited by the operator capability, which can increase road safety for the operator and other drivers. Further, the method <NUM> can include guidance to the operator regarding proficiency level, which will help the operator improve driving performance.

<FIG> will now be discussed in full detail as an example vehicle environment within which the system and methods disclosed herein may operate. In some instances, the vehicle <NUM> is configured to switch selectively between an autonomous mode, one or more semi-autonomous operational modes, and/or a manual mode. Such switching also referred to as handover when transitioning to a manual mode can be implemented in a suitable manner, now known or later developed. "Manual mode" means that all of or a majority of the navigation and/or maneuvering of the vehicle is performed according to inputs received from an operator (e.g., a human user/driver).

In one or more embodiments, the vehicle <NUM> is an autonomous vehicle. As used herein, "autonomous vehicle" refers to a vehicle that operates in an autonomous mode. "Autonomous mode" refers to navigating and/or maneuvering the vehicle <NUM> along a travel route using one or more computing devices to control the vehicle <NUM> with minimal or no input from an operator. In one or more embodiments, the vehicle <NUM> is highly automated or completely automated. In one embodiment, the vehicle <NUM> is configured with one or more semi-autonomous operational modes in which one or more computing devices perform a portion of the navigation and/or maneuvering of the vehicle along a travel route, and a vehicle operator provides inputs to the vehicle to perform a portion of the navigation and/or maneuvering of the vehicle <NUM> along a travel route. Thus, in one or more embodiments, the vehicle <NUM> operates autonomously according to a particular defined level of autonomy. For example, the vehicle <NUM> can operate according to the Society of Automotive Engineers (SAE) automated vehicle classifications <NUM>-<NUM>. In one embodiment, the vehicle <NUM> operates according to SAE level <NUM>, which provides for the autonomous driving module <NUM> controlling the vehicle <NUM> by braking, accelerating, and steering without operator input but the operator is to monitor the driving and be vigilant and ready to intervene with controlling the vehicle <NUM> if the autonomous driving module <NUM> fails to properly respond or is otherwise unable to adequately control the vehicle <NUM>.

The vehicle <NUM> can include one or more processors <NUM>. In one or more arrangements, the processor(s) <NUM> can be a main processor of the vehicle <NUM>. For instance, the processor(s) <NUM> can be an electronic control unit (ECU). The vehicle <NUM> can include one or more data stores <NUM> for storing one or more types of data. The data store <NUM> can include volatile and/or non-volatile memory. Examples of suitable data stores <NUM> include RAM (Random Access Memory), flash memory, ROM (Read Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof. The data store <NUM> can be a component of the processor(s) <NUM>, or the data store <NUM> can be operably connected to the processor(s) <NUM> for use thereby. The term "operably connected," as used throughout this description, can include direct or indirect connections, including connections without direct physical contact.

In one or more arrangements, the one or more data stores <NUM> can include map data <NUM>. The map data <NUM> can include maps of one or more geographic areas. In some instances, the map data <NUM> can include information or data on roads, traffic control devices, road markings, structures, features, and/or landmarks in the one or more geographic areas. The map data <NUM> can be in any suitable form. In some instances, the map data <NUM> can include aerial views of an area. In some instances, the map data <NUM> can include ground views of an area, including <NUM>-degree ground views. The map data <NUM> can include measurements, dimensions, distances, and/or information for one or more items included in the map data <NUM> and/or relative to other items included in the map data <NUM>. The map data <NUM> can include a digital map with information about road geometry. The map data <NUM> can be high quality and/or highly detailed.

In one or more arrangement, the map data <NUM> can include one or more terrain maps <NUM>. The terrain map(s) <NUM> can include information about the ground, terrain, roads, surfaces, and/or other features of one or more geographic areas. The terrain map(s) <NUM> can include elevation data in the one or more geographic areas. The map data <NUM> can be high quality and/or highly detailed. The terrain map(s) <NUM> can define one or more ground surfaces, which can include paved roads, unpaved roads, land, and other things that define a ground surface.

In one or more arrangement, the map data <NUM> can include one or more static obstacle maps <NUM>. The static obstacle map(s) <NUM> can include information about one or more static obstacles located within one or more geographic areas. A "static obstacle" is a physical object whose position does not change or substantially change over a period of time and/or whose size does not change or substantially change over a period of time. Examples of static obstacles include trees, buildings, curbs, fences, railings, medians, utility poles, statues, monuments, signs, benches, furniture, mailboxes, large rocks, hills. The static obstacles can be objects that extend above ground level. The one or more static obstacles included in the static obstacle map(s) <NUM> can have location data, size data, dimension data, material data, and/or other data associated with it. The static obstacle map(s) <NUM> can include measurements, dimensions, distances, and/or information for one or more static obstacles. The static obstacle map(s) <NUM> can be high quality and/or highly detailed. The static obstacle map(s) <NUM> can be updated to reflect changes within a mapped area.

The one or more data stores <NUM> can include map data <NUM> and/or sensor data <NUM>. In this context, "map data" refers to any data providing relative proximity between two objects, usable by the vehicle <NUM>, one or more systems of the vehicle <NUM>, or the operator. "Sensor data" means any information about the sensors that the vehicle <NUM> is equipped with, including the capabilities and other information about such sensors. As will be explained below, the vehicle <NUM> can include the sensor system <NUM>. The sensor data <NUM> can relate to one or more sensors of the sensor system <NUM>. As an example, in one or more arrangements, the sensor data <NUM> can include information on one or more LIDAR sensors <NUM> of the sensor system <NUM>. In some instances, at least a portion of the map data <NUM> and/or the sensor data <NUM> can be located in one or more data stores <NUM> located onboard the vehicle <NUM>. Alternatively, or in addition, at least a portion of the map data <NUM> and/or the sensor data <NUM> can be located in one or more data stores <NUM> that are located remotely from the vehicle <NUM>.

As noted above, the vehicle <NUM> can include the sensor system <NUM>. The sensor system <NUM> can include one or more sensors. "Sensor" means any device, component and/or system that can detect, and/or sense something. The one or more sensors can be configured to detect, and/or sense in real-time. As used herein, the term "real-time" means a level of processing responsiveness that a user or system senses as sufficiently immediate for a particular process or determination to be made, or that enables the processor to keep up with some external process.

In arrangements in which the sensor system <NUM> includes a plurality of sensors, the sensors can function independently from each other. Alternatively, two or more of the sensors can work in combination with each other. In such a case, the two or more sensors can form a sensor network. The sensor system <NUM> and/or the one or more sensors can be operably connected to the processor(s) <NUM>, the data store(s) <NUM>, and/or another element of the vehicle <NUM> (including any of the elements shown in <FIG>). The sensor system <NUM> can acquire data of at least a portion of the external environment of the vehicle <NUM> (e.g., nearby vehicles).

The sensor system <NUM> can include any suitable type of sensor. Various examples of different types of sensors will be described herein. However, it will be understood that the embodiments are not limited to the particular sensors described. The sensor system <NUM> can include one or more vehicle sensors <NUM>. The vehicle sensor(s) <NUM> can detect, determine, and/or sense information about the vehicle <NUM> itself. In one or more arrangements, the vehicle sensor(s) <NUM> can be configured to detect, and/or sense position and orientation changes of the vehicle <NUM>, such as, for example, based on inertial acceleration. In one or more arrangements, the vehicle sensor(s) <NUM> can include one or more accelerometers, one or more gyroscopes, an inertial measurement unit (IMU), a dead-reckoning system, a global navigation satellite system (GNSS), a global positioning system (GPS), a navigation system <NUM>, and /or other suitable sensors. The vehicle sensor(s) <NUM> can be configured to detect, and/or sense one or more characteristics of the vehicle <NUM>. In one or more arrangements, the vehicle sensor(s) <NUM> can include a speedometer to determine a current speed of the vehicle <NUM>.

Alternatively, or in addition, the sensor system <NUM> can include one or more environment sensors <NUM> configured to acquire, and/or sense driving environment data. "Driving environment data" includes and data or information about the external environment in which an autonomous vehicle is located or one or more portions thereof. For example, the one or more environment sensors <NUM> can be configured to detect, quantify and/or sense obstacles in at least a portion of the external environment of the vehicle <NUM> and/or information/data about such obstacles. Such obstacles may be stationary objects and/or dynamic objects. The one or more environment sensors <NUM> can be configured to detect, measure, quantify and/or sense other things in the external environment of the vehicle <NUM>, such as, for example, lane markers, signs, traffic lights, traffic signs, lane lines, crosswalks, curbs proximate the vehicle <NUM>, off-road objects, etc..

Various examples of sensors of the sensor system <NUM> will be described herein. The example sensors may be part of the one or more environment sensors <NUM> and/or the one or more vehicle sensors <NUM>. Moreover, the sensor system <NUM> can include operator sensors that function to track or otherwise monitor aspects related to the operator of the vehicle <NUM>. However, it will be understood that the embodiments are not limited to the particular sensors described.

As an example, in one or more arrangements, the sensor system <NUM> can include one or more radar sensors <NUM>, one or more LIDAR sensors <NUM>, one or more sonar sensors <NUM>, and/or one or more cameras <NUM>. In one or more arrangements, the one or more cameras <NUM> can be high dynamic range (HDR) cameras, infrared (IR) cameras and so on. In one embodiment, the cameras <NUM> include one or more cameras disposed within a passenger compartment of the vehicle for performing eye-tracking on the operator in order to determine a gaze of the operator, an eye track of the operator, and so on.

The vehicle <NUM> can include an input system <NUM>. An "input system" includes any device, component, system, element or arrangement or groups thereof that enable information/data to be entered into a machine. The input system <NUM> can receive an input from a vehicle passenger (e.g., an operator or a passenger) or from external systems, such as from the vehicle regulation system <NUM>, described above with reference to <FIG>. The vehicle <NUM> can include an output system <NUM>. An "output system" includes any device, component, or arrangement or groups thereof that enable information/data to be transmitted to the vehicle or presented to a vehicle passenger (e.g. a person, a vehicle passenger, etc.). The output system <NUM> can be configured to communicate sensor data and other information to the vehicle regulation system <NUM>, as described above.

The vehicle <NUM> can include one or more vehicle systems <NUM>. Various examples of the one or more vehicle systems <NUM> are shown in <FIG>. However, the vehicle <NUM> can include more, fewer, or different vehicle systems. It should be appreciated that although particular vehicle systems are separately defined, each or any of the systems or portions thereof may be otherwise combined or segregated via hardware and/or software within the vehicle <NUM>. The vehicle <NUM> can include a propulsion system <NUM>, a braking system <NUM>, a steering system <NUM>, throttle system <NUM>, a transmission system <NUM>, a signaling system <NUM>, and/or a navigation system <NUM>. Each of these systems can include one or more devices, components, and/or combination thereof, now known or later developed.

The navigation system <NUM> can include one or more devices, sensors, applications, and/or combinations thereof, now known or later developed, configured to determine the geographic location of the vehicle <NUM> and/or to determine a travel route for the vehicle <NUM>. The navigation system <NUM> can include one or more mapping applications to determine a travel route for the vehicle <NUM>. The navigation system <NUM> can include a global positioning system, a local positioning system or a geolocation system.

The processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> can be operably connected to communicate with the various vehicle systems <NUM> and/or individual components thereof. For example, returning to <FIG>, the processor(s) <NUM> and/or the autonomous driving module(s) <NUM> can be in communication to send and/or receive information from the various vehicle systems <NUM> to control the movement, speed, maneuvering, heading, direction, etc. of the vehicle <NUM>. The processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> may control some or all of these vehicle systems <NUM> and, thus, may be partially or fully autonomous.

The processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> can be operably connected to communicate with the various vehicle systems <NUM> and/or individual components thereof. For example, returning to <FIG>, the processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> can be in communication to send and/or receive information from the various vehicle systems <NUM> to control the movement, speed, maneuvering, heading, direction, etc. of the vehicle <NUM>. The processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> may control some or all of these vehicle systems <NUM>.

The processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> may be operable to control the navigation and/or maneuvering of the vehicle <NUM> by controlling one or more of the vehicle systems <NUM> and/or components thereof. For instance, when operating in an autonomous mode, the processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> can control the direction and/or speed of the vehicle <NUM>. The processor(s) <NUM>, the vehicle regulation system <NUM>, and/or the autonomous driving module(s) <NUM> can cause the vehicle <NUM> to accelerate (e.g., by increasing the supply of fuel provided to the engine), decelerate (e.g., by decreasing the supply of fuel to the engine and/or by applying brakes) and/or change direction (e.g., by turning the front two wheels). As used herein, "cause" or "causing" means to make, force, compel, direct, command, instruct, and/or enable an event or action to occur or at least be in a state where such event or action may occur, either in a direct or indirect manner.

The vehicle <NUM> can include one or more actuators <NUM>. The actuators <NUM> can be any element or combination of elements operable to modify, adjust and/or alter one or more of the vehicle systems <NUM> or components thereof to responsive to receiving signals or other inputs from the processor(s) <NUM> and/or the autonomous driving module(s) <NUM>. Any suitable actuator can be used. For instance, the one or more actuators <NUM> can include motors, pneumatic actuators, hydraulic pistons, relays, solenoids, and/or piezoelectric actuators, just to name a few possibilities.

The vehicle <NUM> can include one or more modules, at least some of which are described herein. The modules can be implemented as computer-readable program code that, when executed by a processor <NUM>, implement one or more of the various processes described herein. One or more of the modules can be a component of the processor(s) <NUM>, or one or more of the modules can be executed on and/or distributed among other processing systems to which the processor(s) <NUM> is operably connected. The modules can include instructions (e.g., program logic) executable by one or more processor(s) <NUM>. Alternatively, or in addition, one or more data store <NUM> may contain such instructions.

In one or more arrangements, one or more of the modules described herein can include artificial or computational intelligence elements, e.g., neural network, fuzzy logic or other machine learning algorithms. Further, in one or more arrangements, one or more of the modules can be distributed among a plurality of the modules described herein. In one or more arrangements, two or more of the modules described herein can be combined into a single module.

The vehicle <NUM> can include one or more autonomous driving modules <NUM>. The autonomous driving module(s) <NUM> can be configured to receive data from the sensor system <NUM> and/or any other type of system capable of capturing information relating to the vehicle <NUM> and/or the external environment of the vehicle <NUM>. In one or more arrangements, the autonomous driving module(s) <NUM> can use such data to generate one or more driving scene models. The autonomous driving module(s) <NUM> can determine position and velocity of the vehicle <NUM>. The autonomous driving module(s) <NUM> can determine the location of obstacles, or other environmental features including traffic signs, trees, shrubs, neighboring vehicles, pedestrians, etc..

The autonomous driving module(s) <NUM> can be configured to receive, and/or determine location information for obstacles within the external environment of the vehicle <NUM> for use by the processor(s) <NUM> , and/or one or more of the modules described herein to estimate position and orientation of the vehicle <NUM>, vehicle position in global coordinates based on signals from a plurality of satellites, or any other data and/or signals that could be used to determine the current state of the vehicle <NUM> or determine the position of the vehicle <NUM> with respect to its environment for use in either creating a map or determining the position of the vehicle <NUM> in respect to map data.

The autonomous driving module(s) <NUM> either independently or in combination with the vehicle regulation system <NUM> can be configured to determine travel path(s), current autonomous driving maneuvers for the vehicle <NUM>, future autonomous driving maneuvers and/or modifications to current autonomous driving maneuvers based on data acquired by the sensor system <NUM>, driving scene models, and/or data from any other suitable source. "Driving maneuver" means one or more actions that affect the movement of a vehicle. Examples of driving maneuvers include: accelerating, decelerating, braking, turning, moving in a lateral direction of the vehicle <NUM>, changing travel lanes, merging into a travel lane, and/or reversing, just to name a few possibilities. The autonomous driving module(s) <NUM> can be configured can be configured to implement determined driving maneuvers. The autonomous driving module(s) <NUM> can cause, directly or indirectly, such autonomous driving maneuvers to be implemented. As used herein, "cause" or "causing" means to make, command, instruct, and/or enable an event or action to occur or at least be in a state where such event or action may occur, either in a direct or indirect manner. The autonomous driving module(s) <NUM> can be configured to execute various vehicle functions and/or to transmit data to, receive data from, interact with, and/or control the vehicle <NUM> or one or more systems thereof (e.g. one or more of vehicle systems <NUM>).

It should be appreciated that the AR system <NUM> can take many different forms but in general functions to augment or otherwise supplement viewing of objects within a real-world environment surrounding the vehicle. That is, for example, the AR system <NUM> can overlay graphics using one or more AR displays in order to provide for an appearance that the graphics are integrated with the real-world through, for example, the windshield of the vehicle <NUM>. Thus, the AR system <NUM> can include displays integrated with the windshield, side windows, rear windows, mirrors and other aspects of the vehicle <NUM>. In further aspects, the AR system <NUM> can include head-mounted displays such as goggles or glasses. In either case, the AR system <NUM> functions to render graphical elements that are in addition to objects in the real-world, modifications of objects in the real-world, and/or a combination of the two. In one embodiment, at least one AR display of the AR system <NUM> fuses a real-time image from a camera (e.g., exterior facing camera) of at least part of the surroundings of the vehicle <NUM> with synthetic objects (e.g., rendered graphical elements) from the AR system <NUM> and/or the vehicle regulation system <NUM>. As one example, a monitor (i.e., AR display) is integrated within or just above a dashboard of the vehicle <NUM> and is controlled to display a fused view of graphical elements rendered by the AR system <NUM> with real-world images from the camera. In this way, the AR system <NUM> can augment or otherwise modify a view of an operator/passenger in order to provide an enriched/embellished visual sensory experience. The noted functions and methods will become more apparent with a further discussion of the figures.

Detailed embodiments are disclosed herein. However, it is to be understood that the disclosed embodiments are intended only as examples. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the aspects herein in virtually any appropriately detailed structure. Further, the terms and phrases used herein are not intended to be limiting but rather to provide an understandable description of possible implementations. Various embodiments are shown in FIGS. <NUM>-<NUM>, but the embodiments are not limited to the illustrated structure or application.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible embodiments of systems, methods and computer program products according to various embodiments. In this regard, each block in the flowcharts or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative embodiments, the functions noted in the block can occur out of the order noted in the Figures.

The systems, components and/or methods described above can be realized in hardware or a combination of hardware and software and can be realized in a centralized fashion in one processing system or in a distributed fashion where different elements are spread across several interconnected processing systems. Any kind of processing system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software can be a processing system with computer-usable program code that, when being loaded and executed, controls the processing system such that it carries out the methods described herein. The systems, components and/or methods also can be embedded in a computer-readable storage, such as a computer program product or other data programs storage device, readable by a machine, tangibly embodying a program of instructions executable by the machine to perform methods and methods described herein. These elements also can be embedded in an application product which comprises all the features enabling the embodiment of the methods described herein and, which when loaded in a processing system, is able to carry out these methods.

Furthermore, arrangements described herein can take the form of a computer program product embodied in one or more computer-readable media having computer-readable program code embodied or embedded, such as stored thereon. Any combination of one or more computer-readable media can be utilized. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The phrase "computer-readable storage medium" means a non-transitory storage medium. A computer-readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk drive (HDD), a solid state drive (SSD), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber, cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present arrangements can be 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 program code can 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.

The terms "a" and "an," as used herein, are defined as one or more than one. The term "plurality," as used herein, is defined as two or more than two. The term "another," as used herein, is defined as at least a second or more. The terms "including" and/or "having," as used herein, are defined as comprising (i.e., open language). The phrase "at least one of. " as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. As an example, the phrase "at least one of A, B and C" includes A only, B only, C only, or any combination thereof (e.g., AB, AC, BC or ABC).

Claim 1:
A vehicle regulation system (<NUM>) for regulating vehicle access by an operator, comprising:
one or more processors (<NUM>); and
a memory (<NUM>) communicably coupled to the one or more processors (<NUM>) and storing:
a measurement module (<NUM>) including instructions that when executed by the one or more processors (<NUM>) cause the one or more processors (<NUM>) to:
determine, using driving capacity information (<NUM>), a driving capacity metric (<NUM>) for an operator in a vehicle; and
collect, using one or more sensors (<NUM>), environmental information (<NUM>) including information about the position of the vehicle, the atmospheric conditions, time of day, traffic levels, or general location type;
a comparison module (<NUM>) including instructions that when executed by the one or more processors (<NUM>) cause the one or more processors (<NUM>) to evaluate at least one vehicle system (<NUM>) in the vehicle for a vehicle system proficiency (<NUM>), and to compare the driving capacity metric (<NUM>) and the vehicle system proficiency (<NUM>); and
an evaluation module (<NUM>) including instructions that when executed by the one or more processors (<NUM>) cause the one or more processors (<NUM>) to determine, using the comparison and the environmental information (<NUM>), a proficiency level (<NUM>) of the operator for the at least one vehicle system (<NUM>), to provide, to the operator, access to the at least one vehicle system (<NUM>) based on the proficiency level, and to deliver guidance to the operator regarding the proficiency level (<NUM>), the guidance including corrective measures or other hints to help the operator improve his or her driving, whereby when access to the at least one vehicle system (<NUM>) starts with limited or no access, access can be increased in light of adequate proficiency levels, maintained in light of inadequate proficiency levels, or otherwise altered to reflect adequate or inadequate proficiency levels.