FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
AND
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“A METHOD AND SYSTEM FOR VEHICLE DRIVING OPTIMIZATION”
MINDA CORPORATION LIMITED an Indian company, of E-5/2, Chakan Industrial Area, Phase - III, M.I.D.C, Nanekarwadi, Tal - Khed, Dist. Pune, Maharashtra 410501, Indian
The following specification particularly describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD
[001] The present disclosure generally relates to automotive industry. Particularly, the present disclosure relates to a method and system for performing vehicle driving optimization in accordance with prescribed driving norms.
BACKGROUND OF INVENTION
[002] The following description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[003] Digital key transfer based multi-user vehicle operation is becoming widespread as a means towards achieving shared mobility. The shared mobility in automotive industry is referred to as usage of a vehicle collectively by commuters for transportation without owning it. However, this also means that the vehicle will be driven by different drivers with diverse driving habits. The driving habits may comprise, but not limited to, aggressive driving habits such as sudden intensive acceleration followed by panic braking, rapid gear changes etc., or normal driving habits, which generally comply with prescribed driving norms for driving the vehicle in a certain territory. The aggressive driving habits adversely impact a vehicle’s service life and increase chances of preaging of different components of the vehicle. Moreover, the aggressive driving habits may also lead to unforeseen circumstances such as accidents or loss of human/animal life etc. Thus, there is need for solutions to minimize or control aggressive driving operations under shared mobility usage.
[004] Existing prior arts provide few solutions for minimizing the aggressive driving operations. One such solution may include detecting abnormal driving behavior of the driver. Another such solution may include providing an alert based upon a risk score of a driver. However, none of the existing prior arts provide a complete solution for solving the above identified problems. For example, a driver with aggressive driving

habits or a driver who continuously violates the prescribed driving norms may still access the vehicle which may increase chances of preaging of different vehicle components, reduction in the service life of the vehicle, loss of human/animal life, and the like.
[005] Thus, there exists a need to provide an improved method and system for vehicle driving optimization which can overcome all the above-mentioned difficulties or drawbacks of disadvantages of prior arts mentioned above.
SUMMARY OF INVENTION
[006] The present disclosure overcomes one or more shortcomings of the prior art and provides additional advantages discussed throughout the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.
[007] In one non-limiting embodiment of the present disclosure, a system for vehicle driving optimization is disclosed. The system comprises a vehicle controller configured to authenticate a vehicle driver before providing access of the vehicle to the vehicle driver using a predefined authentication technique. The vehicle controller receives a plurality of vehicle data from a plurality of sensors configured in the vehicle and compare the plurality of vehicle data with a set of prescribed driving norms. Based on the comparison, the vehicle controller classifies a driving behavior of a vehicle driver as at least one of “aggressive” or “normal”. The vehicle controller provides a warning to the vehicle driver to adhere to the set of prescribed driving norms upon classifying the driver behavior as “aggressive”. The vehicle controller automatically switches to an “economy” driving mode if the vehicle driver flouts the warning. The system further comprises a memory configured to store data required for operation of the vehicle controller.

[008] In one non-limiting embodiment of the present disclosure, wherein the plurality of vehicle data comprises at least one of a braking profile, a turning profile, an acceleration profile, and a turn indicator profile.
[009] In one non-limiting embodiment of the present disclosure, wherein the vehicle controller is further configured to compare the driving behavior of the vehicle driver with a set of historical activities of the vehicle driver to determine a driving pattern of the vehicle driver.
[0010] In one non-limiting embodiment of the present disclosure, wherein the vehicle controller classifies the driving behavior of the vehicle driver as “normal” when values of each of the plurality of vehicle data is within threshold values specified in the set of prescribed driving norms.
[0011] In one non-limiting embodiment of the present disclosure, wherein the vehicle controller classifies the driving behavior of the vehicle driver as “aggressive” when value of at least one of the plurality of vehicle data exceeds threshold values specified in the set of prescribed driving norms.
[0012] In one non-limiting embodiment of the present disclosure, wherein the vehicle controller restricts speed of the vehicle to a predefined speed limit according to the prescribed driving norms and prevents acceleration of the vehicle in the “economy” driving mode.
[0013] In one non-limiting embodiment of the present disclosure, wherein the vehicle controller is further configured to assign a driver score to the vehicle driver based on classification of the driving behavior. The vehicle controller blacklists the vehicle driver when the driver score is more than a predefined threshold driver score

[0014] In one non-limiting embodiment of the present disclosure, wherein the vehicle controller is further configured to deny the access of the vehicle to the vehicle driver when the vehicle driver is blacklisted.
[0015] In one non-limiting embodiment of the present disclosure, a method of vehicle driving optimization is disclosed. The method comprises authenticating a vehicle driver before providing access of the vehicle to the vehicle driver using a predefined authentication technique. The method receives a plurality of vehicle data from a plurality of sensors configured in the vehicle and comparing the plurality of vehicle data with a set of prescribed driving norms. Based on the comparison, the method classifies a driving behavior of a vehicle driver as at least one of “aggressive” or “normal”. The method further comprises step of providing a warning to the vehicle driver to adhere to the set of prescribed driving norms upon classifying the driver behavior as “aggressive”. The method further comprises step of automatically switching to an “economy” driving mode if the vehicle driver flouts the warning.
[0016] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF DRAWINGS
[0017] The embodiments of the disclosure itself, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings. One or more embodiments are now described, by way of example only, with reference to the accompanying drawings in which:
[0018] Figure 1 shows a generic environment 100 of a vehicle according to an embodiment of the present disclosure;

[0019] Figure 2 discloses a block diagram 200 of a vehicle controller indicating various components involved in vehicle driving optimization, according to an embodiment of the present disclosure;
[0020] Figure 3 illustrates a flowchart 300 of a method of vehicle driving optimization, in accordance with an embodiment of the present disclosure; and
[0021] The figures depict embodiments of the disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.
DETAILED DESCRIPTION
[0022] The foregoing has broadly outlined the features and technical advantages of the present disclosure in order that the detailed description of the disclosure that follows may be better understood. It should be appreciated by those skilled in the art that the conception and specific embodiment disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure.
[0023] The novel features which are believed to be characteristic of the disclosure, both as to its organization and method of operation, together with further objects and advantages will be better understood from the following description when considered in connection with the accompanying Figures. It is to be expressly understood, however, that each of the figures is provided for the purpose of illustration and description only and is not intended as a definition of the limits of the present disclosure.
[0024] Disclosed herein is a method and system for vehicle driving optimization. The present disclosure aims to enhance vehicle life by ensuring that vehicle drivers adhere to prescribed driving norms. To do so, the vehicle driver is authenticated using a

predefined authentication technique. Under shared mobility, the predefined authentication technique may be referred to as authenticating vehicle driver before the vehicle driver is given an access to the vehicle. The vehicle driver may be authenticated using a digital key fob which may include, but not limited to, a mobile application etc. To perform authentication. a vehicle controller of the vehicle may consider various authenticating entities such as an identification number (Aadhar card number, license number, etc.,), a mobile number, a fingerprint sensor, a wearable device (such as watch), or a Near-Field Communication (NFC) card, which may allow the vehicle driver to access the vehicle. Further, the authenticating entities are also shared with an owner or administrator of the shared vehicle.
[0025] Upon successful authentication, the system receives data from a plurality of sensors of the vehicle. Based on the received data, driving behavior of the vehicle driver is validated or compared against a set of prescribed driving norms of the vehicle. Based on the comparison, the driving behavior of the vehicle driver is classified as “aggressive” or “normal”. For example, if the vehicle driver is driving the vehicle at a speed greater than a predefined threshold speed or abnormally applies brakes, then the vehicle driver may be considered to have an “aggressive” driving behavior. The present disclosure generates a warning in response to determining that the driving behavior of the vehicle driver is aggressive. If the vehicle driver ignores or flouts the warning, then the vehicle may be automatically switched to an economy driving mode and the vehicle driver is blacklisted. In the economy driving mode, the vehicle speed is restricted within the predefined speed threshold, as prescribed in the driving norms. In this manner, the present disclosure helps in preventing potential accidents, as well as reduces vehicle maintenance cost due to rapid aging of various drive-train components of the vehicle. In other words, the present disclosure helps in prolonged life of vehicle components by preventing rapid aging or early damage of vehicle components. Also, the present disclosure advantageously reduces fuel consumption, wear and tear of different components of the vehicle and increases the efficiency of the vehicle components.

[0026] It may further be noted that the present disclosure is described for two-wheeler vehicles, three-wheeler vehicles, four wheeler vehicles, and therefore, the term “vehicle” may be used hereafter for any type of the vehicles mentioned above. Further, the term “rider” may be interchangeably used in place of “driver”. However, it may be noted that the techniques of the present disclosure may be implemented in different types of vehicles such as three-wheeler and four-wheeler vehicles.
[0027] Figure 1 shows an exemplary environment 100 depicting a scenario to implement vehicle driving optimization, in accordance with an embodiment of the present disclosure. The environment 100 illustrates a system 101 residing inside a vehicle 103. The system communicates with a vehicle data server 113 via a communication network 111. In some embodiments, the vehicle 103 may refer to, but not limited to, an internal combustion engine vehicle, an electric vehicle, a semi-autonomous vehicle, an autonomous vehicle etc. In some embodiments, the vehicle 103 may be any multi-wheel vehicle (e.g., a two-wheeler vehicle, three-wheeler vehicle, four-wheeler vehicle, and alike). The detailed explanation of the exemplary environment 100 is explained in conjunction with Figure 2 that shows a block diagram 200 of a system 101 for vehicle driving optimization, in accordance with an embodiment of the present disclosure.
[0028] In one implementation, the system 101 comprises a vehicle controller 105 coupled with a plurality of sensors 107, and a memory 109. The vehicle controller 105 may be communicatively coupled to the memory 109 and the plurality of sensors 107. It may be worth noting that though the plurality of sensors 107 reside inside the system 101 , or the plurality of sensors 107 may reside outside the system 101 as well. The plurality of sensors 107 may comprise, but not limited to, accelerometers, gyroscopes, proximity sensors, or any other sensors for performing desired functionality. In another implementation, the system 101 may include one or more cameras (not shown) communicatively coupled with the vehicle controller 105 to cover interior and exterior views of the vehicle 103. The one or more cameras may capture real-time and/or non-

real time data related to a number of lanes on a road, nearby vehicles, speed brakers, turns on the road, but not limited thereto. Further, the vehicle data server 113 may be configured to, but limited to, store data retrieved from the plurality of sensors 107 and data related to operations performed by the vehicle controller 105. In some embodiments, the vehicle data server 113 may be located at a remote location.
[0029] In some embodiments, the vehicle controller 105 may include any suitable hardware for processing data received from the plurality of sensors 107. Examples of the vehicle controller 105 may include, but not limited to, an Electronic Control Unit (ECU), a microprocessor, a processor, central processing unit, digital signal processing unit, single core processor, dual core processor, quad core processor, mobile device processor, desktop processor, a system-on-chip (SoC) device, complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or any other type of processor or processing circuit on a single chip or integrated circuit.
[0030] In an aspect of the present disclosure, the vehicle controller 105 may be configured to authenticate a vehicle driver of the vehicle 103 via a predefined authentication technique. The predefined authentication technique may be defined as authenticating the vehicle driver before providing access of the vehicle to the vehicle driver. The vehicle driver may be authenticated using a digital key fob (not shown) which may include, but not limited to, a mobile application. The digital key fob may authenticate the vehicle driver using various authenticating entities, which may include an identification number (Aadhar card number, license number, etc.,), a mobile number, a fingerprint or biometric sensor, a wearable device (such as watch), or a near-field communication (NFC) card associated with the vehicle driver. In an exemplary embodiment, when the vehicle driver attempts to access the vehicle, a signal from the digital key fob may be sent to the vehicle controller 105. The signal may relate to a process of authenticating the vehicle driver. The vehicle controller 105, upon receiving the signal from the digital key fob, may verify the authenticating entities stored in the

memory 109 or the vehicle data server 113. Upon successfully authenticating the driver, access to the vehicle may be provided to the vehicle driver. In case the authentication fails, the vehicle controller 105 may deny the access of the vehicle 103 to the vehicle driver. In a non-limiting embodiment, the authentication of the vehicle driver may be performed by an authenticating unit 203 as shown in figure. 2.
[0031] Further, the vehicle controller 105 may be configured to receive a plurality of vehicle data from a plurality of sensors 107 configured in the vehicle 103. In some embodiments, the plurality of vehicle data may be received in real-time or may be accumulated and stored in the memory 109 or at the vehicle data server 113. The plurality of vehicle data may comprise a braking profile, a turning profile, an acceleration profile, a turn indicator profile, and alike. In an exemplary embodiment, the braking profile may comprise a deceleration curve, a brake position, or any combination thereof. In some embodiments, the turning profile may comprise a steering wheel turning rate, a preferred turning radius, or any combination thereof. In another exemplary embodiment, steering wheel turning rate may be correlated with timely operation of turn indicators. The acceleration profile may indicate whether the speed of the vehicle 103 lies within a predefined speed threshold. The predefined speed threshold may be as the speed prescribed as per the driving norms. In some embodiments, the acceleration profile may comprise an acceleration rate coming up to highway speed, an acceleration rate from a stop, an acceleration rate when passing another vehicle, or any combination thereof. In some embodiments, the turn indicator profile may comprise a distance up to which a turn indicator is lit before turning into a street, total time the turn indicator is lit before changing lanes on a highway, or any combination thereof. However, the above description should not be taken into limiting sense. In some embodiments, the vehicle controller 105 may be configured to retrieve additional vehicle data which may include location data, proximity data, driver wise fuel consumption/efficiency and so on from the plurality of sensors 107. In non-limiting embodiment, the plurality of vehicle data may be received by a receiving unit 205 as shown in fig. 2.

[0032] The vehicle controller 105 may be configured to compare the plurality of vehicle data with a set of prescribed driving norms. For example, the vehicle controller 105 may derive a comparison on how many times the vehicle driver exceeds a speed threshold value for driving the vehicle on highway with a predefined speed threshold value as per the prescribed driving norms. In similar manner, the vehicle controller 105 may be configured to derive comparison of threshold values of aforementioned vehicle data with the threshold values as per the prescribed driving norms. In non-limiting embodiment, the comparison may be carried out by a comparing unit 207 as shown in fig. 2.
[0033] Based on the comparison, the vehicle controller 105 may be configured to classify driving behavior of the vehicle driver as at least one of “aggressive” behavior or “normal” behavior. For example, the vehicle controller may classify the driving behavior of the vehicle driver as “normal” behavior when values of each of the plurality of vehicle data lies within threshold values specified in the set of prescribed driving norms. Once it has been classified that the driving behavior of the vehicle driver is “normal”, the vehicle driver will be allowed to access the vehicle in future.
[0034] Further, the vehicle controller may classify the driving behavior of the vehicle driver as “aggressive” when value of at least one of the plurality of vehicle data exceeds threshold values specified in the set of prescribed driving norms. In non-limiting embodiment, the driving behavior of the vehicle driver may be classified by a classifying unit 209 as shown in fig. 2. In some embodiments, the vehicle controller may be configured to compare the driving behavior of the vehicle driver with a set of historical activities of the vehicle driver to determine a driving pattern of the vehicle driver. The set of historical activities may comprise a record of how the driver typically drives. For example, set of historical activities may include but not limited to a record of the driving behavior of the vehicle driver over last few months. The record may be stored in the memory 109 or at the vehicle data server 113.

[0035] The vehicle controller 105 may be configured to provide a warning to the vehicle driver to adhere to the set of prescribed driving norms upon classifying the driving behavior as “aggressive”. In some embodiments, the vehicle controller 105 may be communicatively coupled to a display/or console (not shown) for displaying the warning to the vehicle driver based on the classification of the driving behavior as “aggressive”. The warning may be provided in form of, but not limited to, audio alert, haptic alert, notification, display message etc. In non-limiting embodiments, the warning provided to the vehicle driver may be communicated to a shared mobility administrator, who may then blacklist the errant/aggressive vehicle driver. This allows the shared mobility administrator to identify a consistently erring driver and blacklist him/her from accessing the vehicle in future. In non-limiting embodiment, the warning may be provided by a warning generating unit 211 as shown in fig. 2.
[0036] In some embodiments, the vehicle controller 105 may be configured to assign a driving score to the vehicle driver based on the classification of the driving behavior. For example, the driving score may be assigned to the vehicle driver based on the comparison vehicle data with the set of prescribed data norms and a further comparison between the set of historical activities and the plurality of vehicle data received in real time. If the driving score is more than a predefined threshold driving score, then the vehicle controller 105 blacklists the vehicle driver from accessing the vehicle in future. In other words, blacklisting the vehicle driver may be referred to as denying the access of the vehicle to the vehicle driver in future. In non-limiting embodiment, the driving score is assigned by a scoring unit 213 as shown in fig. 2.
[0037] In some embodiments, the vehicle controller 105 may be configured to determine whether the vehicle driver continues to violate/flout the prescribed driving norms and resorts to aggressive driving. If it is determined that the driver continues with the aggressive driving (i.e., the driver performs abrupt and flawed braking, gear switching, and abruptly turning ON and OFF the turn indicators, in general flouts the normal driving norms) and ignores the warning message continuously, then the vehicle

controller 105 may be configured to automatically switch to an “economy” driving mode. In the economy driving mode, the vehicle speed, acceleration pattern etc. are toned down to respective threshold values, as specified in the prescribed driving norms, even though the accelerator pedal is operated vigorously by the vehicle driver. It may be well noted that the toning down of the vehicle speed limit, acceleration pattern will take place after a predetermined amount of time. This helps in cases where the vehicle driver is overtaking another vehicle or performing similar activities to prevent any accident or unforeseen circumstances.
[0038] Thus, the present disclosure aims to prevent potential accidents as well as
reduces vehicle maintenance costs due to rapid aging of various components of the
vehicle. This enables to enhance the vehicle life by ensuring all drivers adhere to the
prescribed driving norms. Further, the presented disclosure proactively penalizes the
vehicle driver by limiting vehicle speed as well as toning down the acceleration during
aggressive driving activities. Furthermore, the present disclosure also helps the shared
mobility administrator to automatically block/black-list errant drivers who are
continuously flouting the prescribed driving norms. Also, the present disclosure
enables to identify the aggressive drivers using cheaper and easy-to-implement sensors
such as voice recognition or thumbprint or biometric sensing. Moreover, the present
disclosure operates on zero incremental hardware alterations and in general avoids
additions to the bill of materials cost of the hardware. Thus, the proposed solution is an
improved, cost-effective, and efficient solution in terms of fuel
consumption/efficiency, causing less wear and tear of different components, achieving prolonged life of components, preventing loss of human-life and animal life while driving the vehicle in compliance with the prescribed driving norms.
[0039] Figure 3 depicts a method 300 of vehicle driving optimization, in accordance with an embodiment of the present disclosure. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions may include routines, programs, objects, components, data

structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.
[0040] The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described.
[0041] Further, the method 300 is implemented in a scenario where a vehicle is driven by different vehicle drivers with diverse driving habits in shared mobility. At block 301, the method 300 may include authenticating a vehicle driver before providing access of the vehicle to the vehicle driver using a predefined authentication technique. The predefined authentication technique may include authenticating the vehicle driver using a digital key fob such as mobile application installed on a mobile device.
[0042] The method at block 303 may include receiving a plurality of vehicle data from a plurality of sensors configured in the vehicle. The plurality of vehicle data may comprise at least one of at least one of: a braking profile, a turning profile, an acceleration profile, and a turn indicator profile.
[0043] At block 305, the method may disclose comparing the plurality of vehicle data with a set of prescribed driving norms. In some embodiments, the method may disclose comparing the driving behavior of the vehicle driver with a set of historical activities of the vehicle driver to determine a driving pattern of the vehicle driver.
[0044] At block 307, the method may disclose classifying driving behavior of the vehicle driver as at least one of “aggressive” or “normal” based on comparison. The driving behavior of the vehicle driver may be classified as “normal” when values of each of the plurality of vehicle data is within threshold values specified in the set of prescribed driving norms. The method may further comprise providing access of the

vehicle to the vehicle driver in future when the driving behavior of the vehicle driver is classified as “normal”. In some embodiment, the method may comprise providing reward points to the vehicle driver based on the classified “normal” driving behavior. Further, the driving behavior of the vehicle driver is classified as “aggressive” when value of at least one of the plurality of vehicle data exceeds threshold values specified in the set of prescribed driving norms.
[0045] The method at block 309 may include providing a warning to the vehicle driver to adhere to the set of prescribed driving norms upon classifying the driver behavior as “aggressive”. In some embodiments, the warning may be provided in form of audio alert, haptic alert, notification to be displayed on display panel of the vehicle, etc.
[0046] At last, the method at block 311 may include automatically switching to an “economy” driving mode if the vehicle driver flouts the warning. In some embodiments, the method may include assigning a driver score to the vehicle driver based on classification of the driving behavior. In some embodiments, the method may include blacklisting the vehicle driver when the driver score is more than a predefined threshold driver score. The method may further include denying the access of the vehicle to the vehicle driver when the vehicle driver is blacklisted.
[0047] A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.
[0048] When a single device or article is described herein, it will be clear that more than one device/article (whether they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether they cooperate), it will be clear that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality

and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the invention need not include the device itself.
[0049] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present invention are intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
[0050] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
[0051]
Reference Numerals

Reference Numeral Description
100 Generic environment of vehicle driving optimization
101 System
103 Vehicle
105 Vehicle controller/processor
107 Plurality of sensors
109 Memory
200 Block diagram of the system
203 Authenticating unit
205 Receiving unit

207 Comparing unit
209 Classifying unit
211 Warning generating unit
213 Score assigning unit
300 Method of vehicle driving optimization
301-311 Method steps

We Claim:
1. A system for vehicle driving optimization, the system comprising:
a vehicle controller configured to:
authenticate a vehicle driver before providing access of the vehicle to the vehicle driver using a predefined authentication technique;
receive a plurality of vehicle data from a plurality of sensors configured in the vehicle;
compare the plurality of vehicle data with a set of prescribed driving norms;
classify a driving behavior of a vehicle driver as at least one of “aggressive” or “normal” based on comparison;
provide a warning to the vehicle driver to adhere to the set of prescribed driving norms upon classifying the driver behavior as “aggressive”; and
automatically switch to an “economy” driving mode if the vehicle driver flouts the warning; and
a memory configured to store data required for operation of the vehicle controller.
2. The system as claimed in claim 1, wherein the plurality of vehicle data comprises at least one of a braking profile, a turning profile, an acceleration profile, and a turn indicator profile.
3. The system as claimed in claim 1, wherein the vehicle controller is further configured to compare the driving behavior of the vehicle driver with a set of historical activities of the vehicle driver to determine a driving pattern of the vehicle driver.
4. The system as claimed in claim 1, wherein the vehicle controller classifies the driving behavior of the vehicle driver as “normal” when values of each of the plurality of vehicle data is within threshold values specified in the set of prescribed driving norms.

5. The system as claimed in claim 1, wherein the vehicle controller classifies the driving behavior of the vehicle driver as “aggressive” when value of at least one of the plurality of vehicle data exceeds threshold values specified in the set of prescribed driving norms.
6. The system as claimed in claim 1, wherein the vehicle controller restricts speed of the vehicle to a predefined speed limit according to the prescribed driving norms and prevents acceleration of the vehicle in the “economy” driving mode.
7. The system as claimed in claim 1, wherein the vehicle controller is further configured to:
assign a driver score to the vehicle driver based on classification of the driving behavior; and
blacklist the vehicle driver when the driver score is more than a predefined threshold driver score.
8. The system as claimed in claim 7, wherein the vehicle controller is further
configured to deny the access of the vehicle to the vehicle driver when the vehicle
driver is blacklisted.
9. A method of vehicle driving optimization, the method comprising:
authenticating a vehicle driver before providing access of the vehicle to the
vehicle driver using a predefined authentication technique;
receiving a plurality of vehicle data from a plurality of sensors configured in the vehicle;
comparing the plurality of vehicle data with a set of prescribed driving norms;
classifying a driving behavior of a vehicle driver as at least one of “aggressive” or “normal” based on comparison;
providing a warning to the vehicle driver to adhere to the set of prescribed driving norms upon classifying the driver behavior as “aggressive”; and

automatically switching to an “economy” driving mode if the vehicle driver flouts the warning.
10. The method as claimed in claim 9, wherein the plurality of vehicle data comprises at least one of: a braking profile, a turning profile, an acceleration profile, and a turn indicator profile.
11. The method as claimed in claim 9, further comprises comparing the driving behavior of the vehicle driver with a set of historical activities of the vehicle driver to determine a driving pattern of the vehicle driver.
12. The method as claimed in claim 9, wherein the driving behavior of the vehicle driver is classified as “normal” when values of each of the plurality of vehicle data is within threshold values specified in the set of prescribed driving norms.
13. The method as claimed in claim 9, wherein the driving behavior of the vehicle driver is classified as “aggressive” when value of at least one of the plurality of vehicle data exceeds threshold values specified in the set of prescribed driving norms.
14. The method as claimed in claim 9, further comprising restricting speed of the vehicle to a predefined speed limit according to the prescribed driving norms and preventing acceleration of the vehicle in the “economy” driving mode.
15. The method as claimed in claim 9, further comprising:
assigning a driver score to the vehicle driver based on classification of the driving behavior; and
blacklisting the vehicle driver when the driver score is more than a predefined threshold driver score.
16. The method as claimed in claim 9, further comprising denying the access of the
vehicle to the vehicle driver when the vehicle driver is blacklisted.