DESC:SYSTEM AND METHOD FOR SECURE KEY-LESS OPERATION OF AN ELECTRIC VEHICLE
FIELD OF INVENTION:
[001] The present invention generally relates to an electric vehicle and more particularly relates to a secure key-less operation of an electric vehicle.
BACKGROUND AND PRIOR ART AND PROBLEM IN PRIOR ART:
[002] Many high end four wheelers (cars, SUVs, etc.) now offer keyless entry and exit fobs. These fobs allow the user of the vehicle to get in and operate the vehicle without taking out the key fob from their pocket.
[003] This is a massive quality of life improvement and eradicates the need to take out the key from a secure pocket thus resulting in less chances of theft. Also, thieves are not able to operate the vehicle by picking the mechanical cylinders (engine) which are otherwise exposed.
[004] For such a system to work well, the vehicle should detect and authenticate with the paired key fob while the key fob is still 1-2 meters away. Also, it should be able to detect ingress and egress to do the unlock and lock respectively.
[005] In the commercial vehicle space where our Electric Vehicle is operated, an additional requirement comes that the paired key fob can be remotely changed. Eg., rather than Vehicle V1 being paired with only one Key Fob F1 permanently, we can have V1 paired with F1 for a specific time duration and then remotely allocate vehicle V1 to F2, so only person having F2 can use the vehicle for that duration. Hence V1 can be remotely allocated to any one of the F1, F2, F2..Fn etc.
[006] These and other objects and advantages of the present subject matter will be apparent to a person skilled in the art after consideration of the following detailed description taken into consideration with accompanying drawings in which preferred embodiments of the present subject matter are illustrated.

BRIEF DESCRIPTION OF THE DRAWINGS
[007] It is to be noted, however, that the appended drawings illustrate only typical embodiments of the present subject matter and are therefore not to be considered for limiting of its scope, for the invention may admit to other equally effective embodiments. The detailed description is described with reference to the accompanying figures. Some embodiments of system or methods or structure in accordance with embodiments of the present subject matter are now described, by way of example, and with reference to the accompanying figures, in which:
[008] Figure 1 illustrates an environment for implementing a system for secure key-less operation of an electric vehicle (EV) with a remotely updated secure key, according to an embodiment of the present disclosure;
[009] Figure 2 illustrates a block diagram of the system, according to an embodiment of the present disclosure;
[0010] Figure 3 illustrates a block diagram of the system having the VCU, according to an embodiment of the present disclosure;
[0011] Figure 4a-4b illustrates a process flow of a working of the system and method for secure key-less entry with remotely updated secure key, according to embodiments of the present invention; and
[0012] Figure 5 illustrates a method flow for secure key-less operation of the EV with the remotely updated secure key, according to an embodiment of the present disclosure.
[0013] The figures depict embodiments of the present subject matter for the purposes of illustration only. A person skilled in the art will easily 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.
SUMMARY OF THE INVENTION:
[0014] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention nor is it intended for determining the scope of the invention.
[0015] In an aspect of the present disclosure, a method for secure key-less operation of an electric vehicle (EV) with remotely updated secure key is disclosed. The method includes powering on the EV’s telematics associated with a vehicle control unit of the EV. Further, the method includes loading and authenticating a local key using a combination of MacID, IMEI, and hashes. Further, the method includes disabling the EV if a key authentication fails. Further, the method includes authenticating a server using the authenticated local key. Further, the method includes disabling the vehicle if server authentication fails. Further, the method includes querying the server for a public key and ID of a key fob authorized to unlock the EV. Further, the method includes validating the key and the authorized user’s time frame with the server. Further, the method includes disabling keyless entry if validation fails, while allowing vehicle operation via server-issued commands through an application. Further, the method includes determining key fob broadcasts and pairing them with the key fob upon detection. Further, the method includes measuring RSSI values to determine the proximity of the key fob and automatically unlocking the EV when the key fob is near. Further, the method includes locking the EV when the key fob is detected away from a predefined threshold, and updating the EV location to the server.
[0016] In an aspect of the present disclosure, a system for secure key-less operation of an electric vehicle (EV) with remotely updated secure key is disclosed. The system includes a vehicle control unit (VCU) configured to authenticate a local key using a combination of MacID, IMEI, hashes, and challenges, wherein the local key is a base for a chain of trust for the system. The VCU is configured to disable the vehicle if key authentication fails to prevent tampering and theft. The VCU is configured to authenticate a server using the authenticated local key. The VCU is configured to disable the vehicle if server authentication fails to prevent man-in-the-middle (MITM) attacks and unauthorized access. The VCU is configured to query the server for a public key and ID of a key fob authorized to unlock the vehicle. The VCU is configured to validate the key and user authorization period with the server and the chain of trust. The VCU is configured to disable keyless entry if user validation fails, but continue vehicle operation via an application with server commands. A key fob is configured to broadcast its presence to the vehicle for pairing. A key fob is configured to connect to the vehicle using an SPP profile upon detection. A key fob is configured to transmit commands to the vehicle upon successful pairing. A key fob is configured to measure and transmit RSSI (Received Signal Strength Indicator) values to the vehicle for proximity detection. A server is configured to store and manage public keys and IDs of authorized key fobs. A server is configured to validate and update the vehicle's location and status. A server is configured to issue commands for vehicle operation including vehicle on/off, accessories on/off, mode set, geo-fencing, and others. A communication interface between the VCU and the server, configured to enable real-time updates of the vehicle’s location and status and transmission of server commands to the VCU.
[0017] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.
DESCRIPTION OF THE PREFERRED EMBODIMENTS:
[0018] In the following detailed description of the disclosure, reference is made to the accompanying drawings that show, by way of illustration, specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure. It should be understood that the various embodiments of the present disclosure are different but not necessarily mutually exclusive. For example, the specific features, structures, and characteristics described herein in connection with one embodiment can be implemented in other embodiments without departing from the spirit and scope of the present disclosure. It should also be understood that the location or arrangement of individual components in each disclosed embodiment may be changed without departing from the spirit and scope of the present disclosure. For this reason, the following detailed description should not be construed as limiting, and the scope of the present disclosure is defined by the scope of claims, and is appropriately determined based on the entire scope equivalent to the contents of the claims. Interpreted. In the drawings, like reference numbers can indicate identical or similar functions in various ways.
[0019] While the embodiments of the disclosure are subject to various modifications and alternative forms, specific embodiment thereof have been shown by way of example in the figures and will be described below. It should be understood, however, that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.
[0020] The terms “comprises”, “comprising”, or any other variations thereof used in the disclosure, are intended to cover a non-exclusive inclusion, such that a device, system, assembly that comprises a list of components does not include only those components but may include other components not expressly listed or inherent to such system, or assembly, or device. In other words, one or more elements in a system or device proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or device.
[0021] The data processing system includes one or more data processing devices that perform the processes of various embodiments of the present invention. The term “data processing device” or “data processor” is intended to include any data processing device, including, for example, a Central Processing Unit, desktop computer, laptop, information terminals, digital cameras, mobile phones or other devices or components that process data, manage data, and handle data, electrical, magnetic, optical, biological components. It does not matter whether it is implemented in any other way.
[0022] The processor accessible memory system includes one or more processor accessible memories configured to store information, described herein. Information necessary to execute the processes of the various embodiments of the present invention. Processor accessible memory system may be a distributed processor accessible memory system including a plurality of processor accessible memories communicatively coupled to data processing system via a plurality of computers and / or devices. On the other hand, the processor accessible memory system need not be a distributed processor accessible memory, and thus is one or more processor accessible memories located in a single data processor or device.
[0023] The phrase “processor accessible memory” is intended to include volatile, non-volatile electronic, magnetic, optical or any other processor accessible data storage device, such as, but not limited to, a register, floppy It may be a disk, a hard disk, a Compact Disc, a DVD, a flash memory, a ROM, or a RAM.
[0024] The phrase “communicatively connected” is intended to include any type of connection between devices, method, data processors or programs, whether wireless or wired, with which data may be communicated. Furthermore, the phrase “communicatively connected” refers to connections between devices or programs within a single data processor, connections between devices or programs located in different data processors, and data processors. Includes connections between devices that are not deployed. In this regard, although the processor accessible memory system is shown separate from the data processing system, those skilled in the art will understand that the processor accessible memory system may be wholly or partially in the data processing system. It will be appreciated that may be stored in Further in this regard, although the peripheral system and the user interface system are shown separately from the data processing system, those skilled in the art will recognize that one or both of these systems may be used in whole or in part for data processing. It will be appreciated that it may be stored in the system.
[0025] Figure 1 illustrates an environment for implementing a system for secure key-less operation of an electric vehicle (EV) with a remotely updated secure key, according to an embodiment of the present disclosure. Figure 2 illustrates a block diagram of the system, according to an embodiment of the present disclosure.
[0026] Figure 1 demonstrates an environment 100 for implementing a system for secure key-less operation of an electric vehicle (EV) with a remotely updated secure key, in line with an embodiment of the present disclosure. Electric Vehicles (EVs) or battery-powered vehicles—ranging from two-wheelers like scooters and motorbikes to three-wheelers such as auto-rickshaws, and four-wheelers like cars, including Light Commercial Vehicles (LCVs) and Heavy Commercial Vehicles (HCVs)—primarily operate by powering an electric motor using energy from batteries within the EV. Additionally, the EV may be equipped with at least one electrically powered wheel to enable movement. The term ‘wheel’ refers to any ground-contacting component that facilitates the EV’s movement along a path. EV types include Battery Electric Vehicles (BEVs), Hybrid Electric Vehicles (HEVs), and Range Extended Electric Vehicles, though the following paragraphs focus on the components of a Battery Electric Vehicle (BEV).
[0027] In construction, an EV 102 typically includes a battery or battery pack 104 housed within a battery casing, along with a Battery Management System (BMS), an onboard charger 106, a Motor Controller Unit (MCU), an electric motor 108, and an electric transmission system 110. The primary functions of these components are explained in the subsequent paragraphs: The battery 104 of the EV 102 (also referred to as an Electric Vehicle Battery (EVB) or traction battery) is rechargeable and serves as the main energy source for the EV 102. The battery 104 is usually charged from the grid via a charging infrastructure (not shown). Charging can be done using Alternating Current (AC) or Direct Current (DC). In the case of AC charging, the onboard charger 106 converts the AC signal to a DC signal, which is then routed to the battery through the BMS. For DC charging, the onboard charger 106 is bypassed, and the current is sent directly to the battery 104 via the BMS.
[0028] The battery 104 consists of multiple cells grouped into several modules, ensuring that the temperature difference between cells does not exceed a certain predefined value. The terms "battery," "cell," and "battery cell" may be used interchangeably and can refer to various rechargeable cell types and configurations, including, but not limited to, lithium-ion (e.g., lithium iron phosphate, lithium cobalt oxide), lithium-ion polymer, nickel metal hydride, nickel cadmium, nickel hydrogen, nickel-zinc, silver zinc, or other battery types/configurations. The term “battery pack” refers to multiple batteries contained within a single or multi-piece structure. These batteries are electrically interconnected to provide the necessary voltage and capacity for the intended application. The Battery Management System (BMS) is an electronic system designed primarily to ensure the safe and efficient operation of the battery 104. The BMS constantly monitors various battery parameters, such as temperature, voltage, and current, and relays this information to the Electronic Control Unit (ECU) and the Motor Controller Unit (MCU) in the EV 102 using various protocols, including the Controller Area Network (CAN) bus protocol, which allows communication between the ECU/MCU and other EV 102 components without a host computer.
[0029] The MCU controls the electric motor’s operation based on signals received from the vehicle battery. Its primary functions include starting and stopping the electric motor 108, regulating its speed, enabling the EV 102 to move in reverse, and protecting the motor from premature wear. The electric motor 108 primarily converts electrical energy into mechanical energy, which is then transferred to the EV’s transmission system to enable movement. Additionally, during regenerative braking (when kinetic energy generated during braking or deceleration is converted into potential energy and stored in the EV’s battery), the electric motor 108 also functions as a generator. EVs typically use various types of motors, including DC series motors, Brushless DC motors (BLDC motors), Permanent Magnet Synchronous Motors (PMSM), Three Phase AC Induction Motors, and Switched Reluctance Motors (SRM).
[0030] The transmission system 110 in the EV 102 facilitates the transfer of mechanical energy generated by the electric motor 108 to the wheels 112a, 112b of the EV 102. Transmission systems in EVs 102 typically include single-speed and multi-speed (i.e., two-speed) systems. A single-speed transmission system uses a single gear pair to maintain a constant EV 102 speed. In contrast, a multi-speed/two-speed transmission system utilizes a compound planetary gear system with double and single pinion planetary gear sets, resulting in two different gear ratios that provide higher torque and vehicle speed.
[0031] In one embodiment, all data related to the EV 102 and/or charging infrastructure may be collected and processed using a remote server (commonly referred to as the cloud). The processed data 308 is then displayed to the rider/driver of the EV 102 via a display unit located on a human machine interface (HMI) 114. In some embodiments, the display unit may be interactive, while in others, it may be non-interactive.
[0032] In addition to the hardware components, the EV 102 may also feature software modules with intelligent capabilities, including navigation assistance, hill assistance, cloud connectivity, Over-The-Air (OTA) updates, adaptive display techniques, and more. The EV 102 firmware may incorporate Artificial Intelligence (AI) and Machine Learning (ML) modules that can predict various parameters, such as driver/rider behavior, road conditions, and nearby charging infrastructure 120. Data related to these intelligent features can be shown on the display unit within the HMI 114. In one embodiment, the display unit could feature a Liquid Crystal Display (LCD) screen of a specific size. In another embodiment, it could include a Light-Emitting Diode (LED) screen of a specific size. The display unit is water-resistant and supports multiple User-Interface (UI) designs. The EV 102 is compatible with various frequency bands, including 2G, 3G, 4G, and 5G. Additionally, the EV 102 may also be equipped with wireless technologies such as Bluetooth and Wi-Fi, enabling communication with other EVs or the cloud.
[0033] In an alternative embodiment, the system 128 may be located in the remote server or the cloud, without deviating from the scope of the present disclosure. Further details about the construction and operation of system 128 are discussed in the following paragraphs, in conjunction with the Figures, without departing from the scope of the present disclosure.
[0034] In an embodiment, the system 128 is configured for the secure, keyless operation of the EV 102 with the added capability of remotely updating the secure key. The system 128 includes the Vehicle Control Unit (VCU) 204, a key fob 207, and a remote server or known as server 208, all connected through a communication interface 210. The present disclosure addresses the critical need for enhanced security in EVs 102 by implementing a robust authentication mechanism that protects against unauthorized access and theft.
[0035] In an embodiment, the VCU 204 is the central component responsible for managing the security and operational aspects of the EV 102. The VCU 204 functions include authenticating a local key. The VCU 204 begins by authenticating a local key stored within the EV 102, preferably in a memory of the EV 102. This authentication process uses a combination of MacID (Media Access Control Identifier), IMEI (International Mobile Equipment Identity), hashes, and challenges. This combination creates a strong base for a chain of trust, ensuring that the system 128 may reliably verify the key’s authenticity.
[0036] In an embodiment, the MacID refers to a unique identifier assigned to network interfaces for communications at the data link layer.
[0037] In an embodiment, the IMEI refers to a unique identifier for mobile devices, often used in telematics systems within EV 102.
[0038] In an embodiment, the hashes or the cryptographic hashes create a unique digital fingerprint of data, ensuring integrity and security.
[0039] In an embodiment, the challenges indicates the use of challenge-response authentication further strengthens the security by requiring the system 128 to prove possession of the correct key.
[0040] Thus, by combining these elements, the system 128 ensures that the local key cannot be easily spoofed or duplicated, providing a secure starting point for all subsequent operations.
[0041] If the local key fails authentication, the VCU 204 immediately disables the EV 102. This is a crucial security feature designed to prevent tampering, physical hacking, or unauthorized access. Disabling the vehicle ensures that even if an intruder gains physical access to the vehicle, they cannot operate it without the correct key.
[0042] Once the local key is authenticated, the VCU 204 proceeds to authenticate the server using the same key. This step is essential to establish a secure connection between the vehicle and the remote server, which is responsible for managing key updates and other critical operations.
[0043] If the server 208 fails authentication, the VCU 204 again disables the vehicle. This feature protects against man-in-the-middle (MITM) attacks and other forms of unauthorized digital access. By ensuring that only a trusted server can communicate with the vehicle, the system mitigates the risk of remote hacking or digital theft.
[0044] Once the server 208 is authenticated, the VCU 204 queries the server 208 for the public key and the ID of a key fob authorized to unlock the EV 102. This step allows the EV 102 to verify the identity of the key fob that will be used for keyless entry and operation.
[0045] The VCU 204 validates the key and checks the user’s authorization period with the server 208 and the established chain of trust. This ensures that only users with valid, time-bound access can operate the vehicle. If the user is not authorized or the key is invalid, the system 128 disables keyless entry or operation of the EV 102.
[0046] If the key or user validation fails, the VCU 204 disables the keyless entry feature. However, the EV 102 may remain operational via an application with server commands, allowing the owner to retain control of the EV 102 while preventing unauthorized access.
[0047] In an embodiment, the key fob is the user’s interface with the EV 102, enabling secure, keyless entry and operation. Its functions include continuously broadcasting its presence to the EV 102, i.e., signalling that it is within proximity and ready for pairing. Upon detection by the EV 102, the key fob connects using a Serial Port Profile (SPP), a Bluetooth profile that emulates a serial cable to provide wireless communication between devices. After successful pairing, the key fob can transmit commands to the EV 102, such as unlocking the doors, starting the engine, or adjusting vehicle settings. The key fob measures the Received Signal Strength Indicator (RSSI), which indicates how close the fob is to the EV 102. The RSSI values are transmitted to the VCU 204, enabling the system 128 to determine whether the key fob is near enough to permit entry or operation.
[0048] In an embodiment, the server 208 plays a pivotal role in managing the secure operation of the 102. The server 208 securely stores the public keys and IDs of all authorized key fobs. This information is used to validate the key fob when they attempt to unlock or operate the EV 102. The server 208 continuously receives updates on the EV’s 102 location and status, ensuring that it can respond promptly to any security threats or operational commands. The server 208 may issue various commands to the vehicle, including turning the vehicle on or off, controlling accessories, setting the mode (e.g., sport or economy mode), and establishing geo-fences to limit the vehicle’s operation within certain areas.
[0049] In an embodiment, the communication interface between the VCU 204 and the server 208 is crucial for the real-time exchange of data. The communication interface ensures that the EV’s 102 location, status, and commands are updated continuously and securely.
[0050] In an advantageous technical effects, the system 128 disclosed in the present disclosure provides several key advantages:
[0051] Enhanced Security: The multi-layered authentication process involving MacID, IMEI, hashes, challenges, and server validation significantly reduces the risk of unauthorized access. The system's ability to disable the vehicle if authentication fails at any step adds an additional layer of security against both physical and digital theft.
[0052] Remote Key Management: The ability to remotely update the secure key via the server without user intervention is a major advancement. This feature allows for dynamic key management, enabling or disabling access based on real-time decisions without requiring the user to physically interact with the vehicle.
[0053] User Convenience: The keyless entry and operation system, coupled with automatic proximity detection via RSSI values, offers a seamless user experience. Users can access and operate their vehicles without needing to physically handle keys, which is particularly beneficial in modern, fast-paced environments.
[0054] Operational Flexibility: Even if keyless entry is disabled due to validation failure, the vehicle remains operational through server commands. This ensures that the owner retains control of the vehicle under all circumstances, reducing the risk of being stranded due to a security feature.
[0055] Reduced Theft Risk: By eliminating the physical key and securing the system with a robust chain of trust, the system drastically reduces the risk of theft. Even if a potential thief gains physical access to the vehicle, they would be unable to operate it without successfully passing the authentication processes.
[0056] Efficient Key Allocation: The system allows for the remote allocation of vehicle keys to pre-authorized users for specific time periods, reducing the need for physical key management and minimizing human error.
[0057] In an example scenario, consider a fleet management company using the system 128 to manage a fleet of a plurality of EVs. Each EV is equipped with the VCU 204, and authorized drivers are provided with key fobs that have been registered with the server 208. When the EV is powered on, the VCU 204 authenticates the local key using the combination of MacID, IMEI, and hashes. The system 128 then authenticates the server 208, ensuring that it is communicating with a trusted entity. Once the server 208 is authenticated, the VCU 204 queries the server 208 for the public key and ID of the authorized key fob. As a driver approaches the EV, their key fob broadcasts its presence. The VCU 204 detects this broadcast, measures the RSSI values to determine proximity, and pairs with the fob using the SPP profile. Once paired, the driver can unlock the EV and start it without needing to use a physical key. The server 208 continues to validate the key and the driver’s authorization period. Now, suppose an unauthorized individual attempts to use a counterfeit key fob. The VCU 204, upon receiving the broadcast, will measure the RSSI but will fail to validate the key against the stored information. The system 128 will then disable keyless entry, preventing the intruder from accessing the EV. The server 208 will be notified of the failed attempt, and the EV’s location and status will be updated in real-time. Further, the fleet manager decides to temporarily assign the EV to a new driver for a specific project. Using the server’s 208 interface, the manager remotely updates the EV’s secure key to authorize the new driver’s key fob for a limited time. The driver receives access without needing to physically interact with the fleet manager, streamlining the process and reducing downtime.
[0058] Advantageously, the system 128 of the present disclosure represents a significant advancement in the field of EV security and keyless entry systems. By leveraging a multi-layered authentication process, remote key management, and real-time communication between the vehicle and server, it offers enhanced security, user convenience, and operational flexibility. The system’s 128 design effectively addresses the growing need for secure, keyless EV operation in a world where digital threats are increasingly prevalent.
[0059] Figure 3 illustrates a block diagram of the system having the VCU, according to an embodiment of the present disclosure. The essential components of the VCU 204 generally consist of (i) a microcontroller core (or processor unit) or processor 302; (ii) a memory unit or memory 304; (iii) a set of modules 306; and (iv) communication protocols, which include but are not limited to, the CAN protocol, Serial Communication Interface (SCI) protocol, and similar protocols. The sequence of programmed instructions and associated data 308 can be stored in a non-transitory computer-readable medium, such as the memory unit 304 or a storage device. This storage device may be any appropriate memory apparatus, including but not limited to, read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random-access memory (RAM), flash memory, disk drives, and similar devices. In one or more embodiments of the disclosed subject matter, non-transitory computer-readable storage media may be configured with a sequence of programmed instructions for monitoring and controlling the operation of various components of the EV 102.
[0060] The processor 302 may encompass any computing system, including but not limited to, a Central Processing Unit (CPU), an Application Processor (AP), a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), or an AI-dedicated processor such as a Neural Processing Unit (NPU). In one embodiment, the processor may consist of a single processing unit or multiple units, each possibly comprising several computing cores. The processor 302 can be realized as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuits, or any devices capable of manipulating signals according to operational instructions. Among its various capabilities, the processor is designed to fetch and execute computer-readable instructions and data 308 stored in the memory. These instructions may be compiled from source code written in programming languages such as Java, C++, C#.net, or similar languages. The instructions may also include code and data objects provided in accordance with languages such as Visual Basic™, LabVIEW, or other structured or object-oriented programming languages. The processor or processors are responsible for processing input data in alignment with predefined operating rules or artificial intelligence (AI) models stored in both non-volatile and volatile memory. These operating rules or AI models are provided through training or learning algorithms, which can include, but are not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning.
[0061] Additionally, the modules, processes, systems, and devices can be implemented as a single processor or as a distributed processing system. The processes, modules, and sub-modules described in the various figures of and for embodiments herein can be distributed across multiple computers or systems, or they may be consolidated within a single processor or system. Furthermore, the modules 306 can be implemented in hardware, as instructions executed by a processing unit, or through a combination of both. The processing unit may include a computer, a processor like the processor, a state machine, a logic array, or any other suitable device capable of processing instructions. The processing unit can be a general-purpose processor that executes instructions to perform the required tasks, or it can be specifically dedicated to performing those tasks. In another embodiment of the present disclosure, the modules 306 may be machine-readable instructions (software) which, when executed by a processor/processing unit, perform any of the described functionalities.
[0062] Figure 4a-4b illustrates a process flow of a working of the system and method for secure key-less entry with remotely updated secure key, according to embodiments of the present invention. The method 400 may be a computer-implemented method executed, for example, by the system 128 and the modules 306. For the sake of brevity, the constructional and operational features of the system 128 that are already explained in the description of Figures 1-3, are not explained in detail in the description of Figures 4a-4b.
[0063] In an embodiment, the process flow is explained in steps as follows:
• On Battery Connect (or Telematics & Proximity CPU Power ON).
• Using MacID and IMEI and Hashes and challenges, load and authenticate the local key for the device.
• This key is going to be the base of “Chain of Trust” for the entire system. Any future certificates, be it from the server, are going to be validated against it.
• If the Key Authentication fails, then disable the vehicle. This is to prevent tampering and physical Hacking (theft)
• If the Key Authentication succeeds, Authenticate the server using this key.
• If Server Authentication fails, then disable the vehicle. This is to prevent MITM attacks, Digital Takeover and theft.
• Query the server for the Public Key and ID of the FOB which can unlock this vehicle.
• In order for automatically unlocking the vehicle on proximity to a key fob to work, a key fob has to be registered with the server.
• This is usually the driver (or the user’s) phone with our app on it. (The app is optional).
• If registered properly, then validate the key and time for which the user is authorized to use this particular vehicle.
• If no such user is found, disable Keyless Entry.
• Validate the key with the server and Chain of Trust.
• If validation fails, disable Keyless Entry.
• The geolocation and tracking still works. The System waits for commands from server.
• The vehicle can still be operated with the App. On getting a command, execute it. Commands are:
? Vehicle On/Off
? Accessories On/Off
? Mode Set
? Geo Fence
? And many other features as & when required
• Update current vehicle location to the server
• If validation succeeds, Listen for FOB Broadcast, this is before pairing.
• Update the current location to the server.
• Check if FOB is found (in the broadcast). If not found, go back to step 10 (listen for FOB broadcast).
• If FOB is found, connect to it using the SPP profile.
• Update the current location to server.
• Wait to receive commands over SPP.
• If command is given them:
• Execute the command.
• Measure the RSSI.
• Execute Smoothening and Moving Window Algorithm on RSSI.
• Use this value to detect if the key fob is near to the vehicle?
• If near, then unlock the vehicle, then go back to step 14 (update location to server).
• If the key fob is detected far?
• Lock the vehicle, then go back to step 14 i.e., updating location to server).
[0064] The innovation lies in being able to remotely and securely assign vehicle keys to pre authorized people for a limited time period.
[0065] This system innovates on the existing products by being able to remotely and securely assign keys for a specific time frame to a pre-identified group of people for a specific duration of the time. There is no need to exchange the Key information between the server and the human user, as this is done automatically between the machine and the server, without any user intervention.
[0066] This flips the traditional locks on its head, as in this case, the metamorphic lock component is not on the vehicle, but safely with the users (we only use Public keys of the users), while the metaphorical key is handed over to the vehicle. Traditionally, the vehicle has the lock and its keys are distributed, in our case though the locks are changed, the keys to the locks are provided to the vehicle via a verified Chain of Trust for a time bound duration.
[0067] Automation here just results in the reduction of the workforce to handle this flow. Also removes any chance of human error.
[0068] No need for physical Key management at all. Also removes any chance of human error during key allocation.
[0069] Significant reduction of threat of Physical & Digital Theft due to absence of physical key & secured way of assigning Keys only to Pre-authorised people.
[0070] Allocation of the vehicle in the Parking yard is convenient as the vehicle nearest to the exit gate can be accessed then & there without searching for the physical key. Thus, saving time and energy to find the physical key.
[0071] Figure 5 illustrates a method flow 500 for secure key-less operation of the EV with the remotely updated secure key, according to an embodiment of the present disclosure.
[0072] At step 502, the method 500 may include powering on the EV’s telematics associated with a vehicle control unit of the EV.
[0073] At step 504, the method 500 may include loading and authenticating a local key using a combination of MacID, IMEI, and hashes.
[0074] At step 506, the method 500 may include disabling the EV if a key authentication fails.
[0075] At step 508, the method 500 may include authenticating a server using the authenticated local key.
[0076] At step 510, the method 500 may include disabling the vehicle if server authentication fails.
[0077] At step 512, the method 500 may include querying the server for a public key and ID of a key fob authorized to unlock the EV.
[0078] At step 514, the method 500 may include validating the key and the authorized user’s time frame with the server.
[0079] At step 516, the method 500 may include disabling keyless entry if validation fails, while allowing vehicle operation via server-issued commands through an application.
[0080] At step 518, the method 500 may include determining key fob broadcasts and pairing with the key fob upon detection.
[0081] At step 520, the method 500 may include measuring RSSI values to determine the proximity of the key fob and automatically unlock the EV when the key fob is near.
[0082] At step 522, the method 500 may include locking the EV when the key fob is detected away than a predefined threshold, and updating the EV location to the server.
[0083] Although the foregoing description has described the disclosure in connection with specific components, various embodiments, and specific matters such as drawings, these have been presented merely to facilitate understanding of the present disclosure. The disclosure is not limited to the embodiments. It will be apparent to those skilled in the art based on the above description that the above embodiments can be modified and changed in various ways.
[0084] For this reason, the intention of the present disclosure should not be limited to the above-described embodiment, but the scope of the claims and the points modified uniformly or equally are considered to be included in the scope of the present disclosure.
[0085] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances, where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
[0086] It will be further appreciated that functions or structures of a plurality of components or steps may be combined into a single component or step, or the functions or structures of one-step or component may be split among plural steps or components. The present invention contemplates all of these combinations. Unless stated otherwise, dimensions and geometries of the various structures depicted herein are not intended to be restrictive of the invention, and other dimensions or geometries are possible. In addition, while a feature of the present invention may have been described in the context of only one of the illustrated embodiments, such feature may be combined with one or more other features of other embodiments, for any given application. It will also be appreciated from the above that the fabrication of the unique structures herein and the operation thereof also constitute methods in accordance with the present invention. The present invention also encompasses intermediate and end products resulting from the practice of the methods herein. The use of “comprising” or “including” also contemplates embodiments that “consist essentially of” or “consist of” the recited feature.

,CLAIMS:WE CLAIM:
1. A method for secure key-less operation of an electric vehicle (EV) with remotely updated secure key, the method comprising:
powering on the EV’s telematics associated with a vehicle control unit of the EV;
loading and authenticating a local key using a combination of MacID, IMEI, and hashes;
disabling the EV if a key authentication fails;
authenticating a server using the authenticated local key;
disabling the vehicle if server authentication fails;
querying the server for a public key and ID of a key fob authorized to unlock the EV;
validating the key and the authorized user’s time frame with the server;
disabling keyless entry if validation fails, while allowing vehicle operation via server-issued commands through an application;
determining key fob broadcasts and pairing with the key fob upon detection;
measuring RSSI values to determine the proximity of the key fob and automatically unlock the EV when the key fob is near; and
locking the EV when the key fob is detected away than a predefined threshold, and updating the EV location to the server.
2. The method as claimed in claim 1, comprising:
updating the EV key remotely, wherein the server assigns the vehicle key to pre-authorized users for a specified time period.
3. The method as claimed in Claim 1, comprising:
operating the EV using commands issued from the server, including vehicle on/off, accessories on/off, mode setting, and geo-fencing, when keyless entry is disabled.
4. The method as claimed in Claim 1, comprising:
executing a smoothening and moving window algorithm on RSSI values to accurately detect the proximity of the key fob, thereby enabling or disabling vehicle access based on proximity.
5. The method as claimed in Claim 1, comprising:
continuing the EV operation and tracking when keyless entry is disabled, by sending location updates and awaiting server commands for further actions.
6. A system for secure key-less operation of an electric vehicle (EV) with remotely updated secure key, the method comprising:
a vehicle control unit (VCU) configured to:
authenticate a local key using a combination of MacID, IMEI, hashes, and challenges, wherein the local key is a base for a chain of trust for the system;
disable the vehicle if key authentication fails to prevent tampering and theft;
authenticate a server using the authenticated local key;
disable the vehicle if server authentication fails to prevent man-in-the-middle (MITM) attacks and unauthorized access;
query the server for a public key and ID of a key fob authorized to unlock the vehicle;
validate the key and user authorization period with the server and the chain of trust;
disable keyless entry if user validation fails, but continue vehicle operation via an application with server commands;
a key fob configured to:
broadcast its presence to the vehicle for pairing;
connect to the vehicle using an SPP profile upon detection;
transmit commands to the vehicle upon successful pairing;
measure and transmit RSSI (Received Signal Strength Indicator) values to the vehicle for proximity detection;
a server configured to:
store and manage public keys and IDs of authorized key fobs;
validate and update the vehicle's location and status;
issue commands for vehicle operation including vehicle on/off, accessories on/off, mode set, geo-fencing, and others;
a communication interface between the VCU and the server, configured to enable real-time updates of the vehicle’s location and status and transmission of server commands to the VCU.
7. The system as claimed in claim 1, wherein the key fob is a mobile device with an installed application configured to communicate with the server and vehicle, allowing remote key management and vehicle control.

8. The system as claimed in claim 1, wherein the VCU is configured to:
operate a smoothening and moving window algorithm on the RSSI values to detect the proximity of the key fob; and
automatically unlock the vehicle when the key fob is near and lock the vehicle when the key fob is far.
9. The system as claimed in claim 1, wherein the server is configured to remotely assign and update the vehicle key to pre-authorized users for a specified time period, without user intervention.

10. The system as claimed in claim 1 wherein the vehicle control unit (VCU) includes geolocation tracking functionality, enabling vehicle location updates to the server even when keyless entry is disabled.