DESC:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

TITLE OF INVENTION:
SYSTEM AND METHOD FOR ENABLING KEYLESS ACCESS TO A VEHICLE

APPLICANT:
MICELIO MOTORS PRIVATE LIMITED

A Company incorporated in India
Having address:
No.58, 15th cross, 2nd phase JP Nagar, Bengaluru-560078, India

The following specification describes the invention and the manner in which it is to be performed.

CROSS-REFERENCE TO RELATED APPLICATIONS
The present application claim priority from Indian provisional patent application 202141062096 filed on 31 December 2021

TECHNICAL FIELD
The present invention relates to a secure vehicle fleet management system, and in particular, secure vehicle allocation to the user by using keyless entry.
BACKGROUND
The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.
In a fleet management system of a vehicle, fleet operators own the vehicles in order to rent the vehicle for a specific period of time to the user. Generally, the one vehicle is assigned to the one rider. In the fleet management system, while assigning the vehicle to user, maintaining the keys as an asset is a cumbersome task. Also, the process of reassigning the vehicles to riders is complex to keep track of. Therefore, any vehicle anomalies noted during operations, if determined to be caused by intentional sabotage, may be difficult to map to the user of the vehicle at the time.
Therefore, the problem of the existing technology is the secure vehicle allocation along with the key and to keep track of it. Therefore, there is a need to solve the problem of the existing technology. This need can be met by a keyless entry system for the two-wheeler vehicle.

SUMMARY
This summary is provided to introduce concepts related to a keyless entry system for a two-wheeler vehicle for transforming the traditional vehicle access system into the smart access system of the vehicle. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
In one embodiment the proposed the keyless entry system of the vehicle is configured for indicating the state of the vehicle, enabling the user to access the vehicle if the vehicle is in available state, switching ON/OFF the vehicle, locking the vehicle, pausing/unpausing the vehicle, seat locking/ unlocking of the vehicle, etc. and hence has the ability to convert the existing vehicle access system to the keyless vehicle access system.
In one embodiment, the vehicle keyless entry system consists of an OTC (Onboard Telematics and Control), a vehicle keypad, a buzzer, a boot lock actuator, a vehicle DC-DC Converter, a vehicle peripherals, an OTC controlled relay, an ignition circuit, a battery, a motor controller, a motor, a mobile application, a Cloud IoT platform, a display, a seat lock actuator which enables the user to change the state of the vehicle such as vehicle locked state to unlock state, vehicle ignition ON state (vehicle ignition start done), vehicle pause/unpause state, keypad blocked state, etc. The vehicle keypad (202) comprises a numeric keys to enter the OTP, a keys to change/select the state of the vehicle and, a vehicle keypad activation key to activate the vehicle keypad (202), wherein the activation key further shows the current state of the vehicle.
In the keyless access system of the vehicle, the vehicle keypad may be communicatively coupled with the onboard telematics and control unit (OTC) which may further comprises a one-time password (OTP) generation engine which may generate the vehicle side OTP. A validation engine may be configured to validate the OTP received from the vehicle keypad with the vehicle side OTP. The OTP received from the vehicle keypad may be received at a user device from a server/cloud platform wherein the server side OTP may be generated by the server/cloud platform. Finally, the vehicle may be unlocked after successful validation of the OTP by the validation engine.
The benefits of the proposed vehicle keyless entry system include:
- The mobile application is not necessary every time to operate the vehicle except for OTP generation.
- All controls necessary for the user during operations are on the keypad.
- In comparison to bluetooth based mechanism, the present invention is repeatable hassle-free without mobile phone usage for frequent and short distance pauses.

BRIEF DESCRIPTION OF THE DRAWINGS
The drawings incorporated in the description and constituting a part of the description show the embodiments of the present invention and are used for explaining the principle of the present invention in combination with the description. In these drawings, the same reference numerals are used throughout the drawings to refer like features and components. The similar reference numerals represent similar elements. The drawings described hereinafter are some of but not all of the embodiments of the present invention. A person of ordinary skill in the art can obtain other drawings according to these drawings without paying any creative effort.
Figure 1 illustrates a network implementation of a keyless entry system of a vehicle, in accordance with an embodiment of the present subject matter;
Figure 2 illustrates a block diagram representing the components related to the keyless entry system of the vehicle and how they are communicating with each other, in accordance with an embodiment of the present subject matter;
Figure 3 illustrates a flow diagram for detecting whether the vehicle is assigned or not, in accordance with an embodiment of the present subject matter;
Figure 4 illustrates a flow diagram indicating steps to access the vehicle, in accordance with an embodiment of the present subject matter;

Figure 5 illustrates a keypad of the vehicle representing the unassigned state of the vehicle, in accordance with an embodiment of the present subject matter;
Figure 6A illustrates successful unlocking of the vehicle, in accordance with an embodiment of the present subject matter;
Figure 6B illustrates unsuccessful unlocking of the vehicle, in accordance with an embodiment of the present subject matter;
Figure 7 illustrates steps to ON or OFF the vehicle after successful unlocking of the vehicle, in accordance with an embodiment of the present subject matter;
Figure 8 illustrates steps to lock the vehicle after successful unlocking of the vehicle, in accordance with an embodiment of the present subject matter;
Figure 9 illustrates steps to pause and unpause the vehicle after successful unlocking of the vehicle, in accordance with an embodiment of the present subject matter;
Figure 10 illustrates steps to unlock the seat/boot of the vehicle after successful unlocking of the vehicle, in accordance with an embodiment of the present subject matter; and
Figure 11 illustrates an auto lock and auto pause state of the vehicle after successful unlocking of the vehicle, in accordance with an embodiment of the present subject matter.

DETAILED DESCRIPTION OF THE PRESENT INVENTION
To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are just some but not all of the embodiments of the present invention. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without paying any creative effort shall fall into the protection scope of the present invention. It is to be noted that the embodiments in the present invention and the features in the embodiments can be combined at will if not conflicted.
Referring now to figure 1, a network implementation of a keyless entry system (100) is illustrated. The keyless entry system (100) is herein after referent to as the system (100). The system (100) may comprise a vehicle (101), a user device (102), a network (103), and a server/cloud platform (104). The user device (102) may be connected to the server/cloud platform (104) through the network (103).
Referring to figure 2, the block diagram representing the components related to the system (100) and how they are communicating with each other is illustrated. The system (100) may consist of an Onboard Telematics control Unit (OTC) (205), an one-time password (OTP) generation engine (214), a validation engine (215), a 4x4 backlit vehicle keypad (202), a mobile application (201), QR sticker on the vehicle (101) and the server/cloud platform (104). The overall keyless entry mechanism is controlled by the smart access state machine. The vehicle keypad (202) comprises a numeric keys to enter the OTP, a keys to change/select the state of the vehicle (101) and, a vehicle keypad activation key to activate the vehicle keypad (202), wherein the activation key further shows the current state of the vehicle (101). The numeric keys may further comprise the keys from 0-9, the keys to change/select the state of the vehicle (101) may further comprise a lock key, an on/off key, a pause key, a seat key, and a SOS keys. The activation key may be a ? key on the vehicle keypad (202).
The user device (102) is connected to the server/cloud platform (104) through internet, wherein the user device (102) may consist of the mobile application (201) installed on it. The server/cloud platform (104) may generate a server OTP based on receipt of the OTP generation request from the user device (102), wherein the OTP generation request may comprise a vehicle identifier which may be captured by the scanning a QR code displayed on the vehicle (101) or by entering vehicle identification number associated with the vehicle (101) the by using the user device (102). The server OTP may be entered on the vehicle keypad (202) by the user, wherein the vehicle keypad (202) may be communicatively coupled with the onboard telematics and control unit (OTC) (205) of the vehicle (101). The OTC (205) of the vehicle (101) comprises a one-time password (OTP) generation engine (214) in order to generate the vehicle side OTP. The OTP generation engine (214) of the vehicle (101) may generate the vehicle side OTP only when it gets the inputs from the user through the vehicle keypad (202). The user inputs entered on the vehicle keypad (202) may be the server OTP generated from the server/cloud platform (103). The user may enter the inputs through the vehicle keypad (202) by pressing the activation key on the vehicle keypad (202). The activation key of the vehicle keypad (202) may wake the OTC (205) of the vehicle (101). The OTC (205) of the vehicle (101) further comprises the OTP generation engine (214) which may generate the vehicle side OTP based on the current timestamp and a secret key associated with the vehicle (101) when the set of conditions get satisfied. Further the validation engine (215) of the vehicle (101) may receive the server OTP from the vehicle keypad (202) which further validates the server OTP with the vehicle side OTP. After successful validation, the vehicle (101) may get unlocked, and the user may be granted access to the vehicle (101) for further operations.
The set of condition mentioned above may include the set of conditions related to the vehicle (101) in order to give access to the user. The set of conditions may comprise a battery (208) may present with no battery errors, wherein the battery (208) may have a state of charge (SOC) greater than a predefined value. The predefined value may be 30% state of charge of the battery (208) which is the minimum value of the state of charge of the battery (208) in order to access the vehicle (101). Another condition out of set of conditions may comprises a motor controller (213) may present with no motor controller error and the vehicle (101) may currently not assigned or not accessed by a key by the user. The OTP generation engine (214) of the vehicle (101) may be configured to use the timestamp and the secret key associated with the vehicle (101) in order to generate a new OTP each time an OTP generation request is received from the vehicle keypad (202) (by pressing activation key) by the user. It must be noted that the vehicle side OTP is valid only for a limited duration of time (e.g., 1 min, 5 min) since the OTP is generated based on the current timestamp and the secret key associated with the vehicle (101). The vehicle side OTP may be valid for limited duration of time, wherein the limited duration may refer to a time required to enter the server OTP on the vehicle keypad (202) after successful activation of the vehicle keypad (202) by pressing the activation key on the keypad.

In one embodiment, the following may be the various states of the vehicle (101) that the vehicle (101) may be in:
-Vehicle Locked & Available State (No rider currently signed in)
-Vehicle Locked & Unavailable State (No rider currently signed in, battery/ies not available in vehicle)
-Vehicle Unlocked State (Rider has signed in, not enabled ignition)
-Vehicle Ignition Enabled State (Ignition has been enabled, but ignition start not done)
-Vehicle Ignition ON/OFF State (Vehicle ignition start done)
-Vehicle Pause/unpause state
- Seat/ boot unlock state
- Auto lock and auto pause state
-Keypad Blocked State (Max number of wrong OTPs reached)
Each feature of the system (100) is described below.
Now referring to figure 3, a flow diagram for detecting whether the vehicle is assigned or not is illustrated. As shown in figure.3, the system (100) may consist of the vehicle availability indication feature which may indicate the user whether the vehicle (101) is assigned or not and not accessed by key by any user. The feature may let the user know that the vehicle (101) is available for the use.
The vehicle (101) may be determined to be available based on a following set of criteria:
-The battery SoC is greater than 30% (303)
-The battery is present & no battery errors detected (details below) (302)
-The motor controller (213) is present & no motor/motor controller error detected (details below)
When the user finds the above criteria satisfied only then the user can say that the vehicle (101) is currently not assigned to any user and not accessed by physical key by any user and therefore it may deem ready and fit for use for a new user and available for the use.
The vehicle (101) is not assigned to any user if the following conditions are met:
- the vehicle (101) is not accessed by any user using OTP and is in locked state. (Pause state is considered assigned state)
- the vehicle (101) key use is not detected (Detected if ignition enable/ON is detected without OTP entry)
Now referring to figure 4, steps to access the vehicle (101) are illustrated as below.
At step 401, the user device (102) may be connected to the server/cloud platform (104) through internet, wherein the user device (102) may consist of the mobile application (201) installed on it. The user may scan the QR Code or enter vehicle identification number in the mobile application (201) of the user device (102) to generate an OTP (One-Time Passcode). The OTP generated may be a 4-digit OTP.
At step 402, once the user scans the QR code or enter vehicle identification number in the mobile application (201), it may be then sent by the mobile application (201) to the server/ cloud platform (104) as part of OTP generation request. The server/cloud platform (104) may generate a server OTP based on receipt of the OTP generation request from the user device (102), wherein the OTP generation request may comprise a vehicle identifier which may be captured by the scanning a QR code displayed on the vehicle (101) or by entering vehicle identification number associated with the vehicle (101) the by using the user device (102).
At step 403, the server/cloud platform (104) validates the user as an authorized user of the fleet and may generate the server OTP which may then sent to the mobile application (201) of the user device (102).
The server OTP may be entered on the vehicle keypad (202) by the user, wherein the vehicle keypad (202) may be communicatively coupled with the OTC (205) of the vehicle (101).
At step 404, the user may activate the vehicle keypad (202) by pressing activation key on the vehicle keypad (202) which may wake the OTC (205) to generate OTP based on the current timestamp and the secret key associated with the vehicle (101). The activation key may be a ? key on the vehicle keypad (202). The user may enter the server OTP on the vehicle keypad (202) by pressing activation key (? key) followed by server OTP on the vehicle keypad (202). The OTC (205) of the vehicle (101) further comprises the OTP generation engine (214) which may generate the vehicle side OTP based on the current timestamp and a secret key associated with the vehicle (101) when the set of conditions get satisfied. The OTP generation engine (214) of the vehicle (101) may generate the vehicle side OTP only when it gets the inputs from the user through the vehicle keypad (202). The user inputs entered on the vehicle keypad (202) may be the server OTP generated from the server/cloud platform (104). Here the OTC (205) may not need the internet connection to generate the vehicle side OTP. However, the mobile application (201) needs to be connected to the internet to fetch a server OTP.
At step 405, the validation engine (215) of the vehicle (101) further validates the server OTP with the vehicle side OTP. After successful validation, the user may be granted access to the vehicle (101) for further operations after successful unlocking of the vehicle (101).
At step 406, after successful validation, the vehicle (101) may get unlocked. After every successful/ unsuccessful user action, a buzzer may sound with specific tone. The successful note/sound may be indicated by 2 beeps. The failure of the action may be indicated by 3 beeps.
Here, the server OTP explained above may be used through the entire ride even when paused and unpaused state of the vehicle (101). The server OTP may only expire when users sign out (LOCK operation) of the vehicle (101).
The set of condition mentioned in the step 404 may include the set of conditions related to the vehicle (101) in order to give access to the user. The set of conditions may comprise the battery (208) may present with no battery errors, wherein the battery (208) may have a state of charge (SOC) greater than a predefined value. The predefined value may be 30% state of charge of the battery (208) which is the minimum value of the state of charge of the battery (208) in order to access the vehicle (101). The set of conditions may also comprise the motor controller (213) may present with no motor controller error and the vehicle (101) may currently not assigned or not accessed by a key by the user.
The OTP generation engine (214) of the vehicle (101) may be configured to use the timestamp and the secret key associated with the vehicle (101) in order to generate a new OTP each time an OTP generation request is received from the vehicle keypad (202) (by pressing activation key) by the user. It must be noted that the vehicle side OTP is valid only for a limited duration of time (e.g., 1 min, 5 min) since the OTP is generated based on the current timestamp and the secret key associated with the vehicle (101).
Referring to figure 5, the keypad of the vehicle representing the unassigned state of the vehicle is illustrated. The vehicle availability is indicated on the vehicle keypad (202) of the vehicle (101). The ? Key may blink with “white” backlight at an interval of 500ms to indicate vehicle is available. The ? Key is OFF if vehicle (101) is unavailable.
Referring to figure 6A, successful unlocking of the vehicle is illustrated. As shown in Fig. 6A, in order to unlock the vehicle (101), the user may Press ? Key + correct OTP received on the mobile application (201). Upon pressing the activation key of the vehicle keypad, it displays the current state of the vehicle (101) (Shown by amber color). After successful OTP, vehicle (101) may get unlocked. After 5s of the vehicle keypad (202) inactivity, the vehicle keypad (202) may get turn off except only ? Key will lit static white.
Referring to figure 6B, unsuccessful unlocking of the vehicle is illustrated. As shown in Fig. 6B, the vehicle (101) may also have a keypad block state after unsuccessful unlocking of the vehicle (101). When the OTP entered to unlock the vehicle (101) is wrong consecutively for 5 times, the vehicle keypad (202) may move into a blocked state where it no longer accepts any inputs for a period of time that is configurable (Default: 5 mins). In case of 5 unsuccessful OTP, the numeric keys of the vehicle keypad (202) may blink 3 times and gets back to vehicle unassigned state (Idle state) (? Key may blink with “white” backlight at an interval of 500ms).

Referring to figure 7, steps to ON or OFF the vehicle after successful unlocking of the vehicle is illustrated. As shown in Fig. 7, in order to ON/OFF the vehicle (101) after successful unlocking, the user may press ? Key + on/off button. This may disengage the kill switch and side stand if engaged if the user wants to turn on the vehicle (101). Now, the user may hold the brake and press ignition start button on switchgear in order to enable ignition ON of the vehicle (101) so that the user can start the ride. The ON/OFF state of the vehicle (101) may be displayed on the vehicle keypad (202) shown by amber colour. After 5s of keypad inactivity, the vehicle keypad (202) may turn off except only ? Key will lit static white. Upon pressing the activation key of the vehicle keypad (202), it displays the current state of the vehicle(101) (Shown by amber color). The rider may use the ON/OFF button (after pressing ? key) to move the vehicle (101) back to unlocked state anytime when in ignition enable state or ignition ON state.
When user presses ? followed by ON/OFF, an OTC controlled relay (207) may toggle to connect the 12V from a DC-DC to a vehicle peripheral (210). This is in parallel to the key lock line electrically. Display turns ON and buzzer (204) sounds with a successful note. ON/OFF button backlight may turn Amber. Vehicle state machine moves to ignition enable state. Upon pressing ignition start, vehicle (101) moves into ignition ON state. ON indication on display turns green to indicate vehicle (101) is in ON condition. The successful action may be indicated by 2 beeps to indicate that ignition start was done.
Referring to figure 8, steps to lock the vehicle after successful unlocking of the vehicle is illustrated. As shown in Fig. 8, the user may lock the vehicle (101) by pressing ? button followed by LOCK button followed by OTP and sign out. After the locking the vehicle (101), the mobile application (201) may also reflect that user is signed out of vehicle (101). The technical steps for locking the vehicle (101) may include, the user may press ? key followed by LOCK followed by correct OTP, then the vehicle state may move into the LOCK state. If vehicle (101) is in ignition enable or in ignition ON state, the OTC controlled relay (207) may turn OFF to cut the power off. After the successful action, the buzzer (204) may sound with the successful tone indicated by 2 beeps to indicate success of user action. Also, the OTP generated earlier is made to expire. The secret key associated with the vehicle is regenerated and synced with the server/cloud platform (104). Once the secret key exchange is successful, the vehicle (101) is indicated as available. The user may not be allowed to lock the vehicle (101) if Seat is open.
Referring to figure 8, steps to pause and unpause the vehicle after successful unlocking of the vehicle is illustrated. As shown in Fig.9, the user may pause and un-pause the vehicle (101) after successful unlocking the vehicle (101). When the vehicle (101) is in any state other than Locked (Not signed in), the user may press ? followed by pause to put the vehicle (101) in a temporary lock state. The pause button may blink in amber as long as the vehicle is in pause state to indicate that the vehicle (101) is in pause state. In this state, the vehicle (101) is as good as the locked state but is not made ‘available’ and OTP will not expire. The user may un-pause the vehicle (101) by pressing the ? key followed by the same OTP. When the vehicle (101) is in the temporary lock state i.e., in the pause state, then the OTP may not expire. The OTP is a session OTP and may not expire unless the user logs out (Lock action) of the vehicle (101). The OTP may only expire when users sign out (LOCK operation) of the vehicle (101) by pressing ? key followed by LOCK followed by correct OTP. By following this action, the vehicle state may move into the LOCK state and the session OTP may then expire after successful LOCK action. After the successful action, the buzzer (204) may sound with the successful tone indicated by 2 beeps to indicate success of user action. Also, the OTP generated earlier is made to expire
When the user presses ? followed by Pause, the OTC controlled relay (207) may turn OFF if it was ON. Also, the buzzer (204) may sound with successful tone indicated by 2 beeps to indicate success of user action. When the vehicle (101) is unpaused by pressing ? followed by same OTP, the OTC controlled relay (207) may turn ON so that user can start rider easily. The rider may not be required to press ON/OFF again. The vehicle state machine moved to Ignition Enabled state.
As shown in Fig. 10, the user may unlock the boot/seat when he has already signed in (successful unlocking of the vehicle), by pressing ? followed by the SEAT button. This may open the boot/seat. If the vehicle (101) is in Ignition ON or Ignition Enabled state, it may go back to unlocked state. Seat is locked again by pressing. When user press the ? button followed by SEAT, the OTC controlled relay (207) may turn OFF if it was ON, thus bringing the vehicle (101) back to unlocked state if it was in ignition enabled or ignition ON state. A seat lock actuator (206) may be enabled momentarily to allow for dislodging of the seat lock and hence unlock the seat. The SEAT button may turn amber to indicate seat is open. The buzzer (204) may sound with successful tone to indicate success of user action. The state of the boot lock may be continuously sensed via 12V input line and backlight is updated accordingly. The users may be allowed to move to ignition enable and ignition ON state while seat is in unlocked state to ensure any mechanical failures of seat lock do not leave riders stranded. However, rider cannot Lock/sign out while Seat is open.
As shown in Fig.11, the system (100) may have a provision to auto lock and auto pause the vehicle (101). When a rider has signed into the vehicle (101) and the vehicle (101) is in unlocked state (not Ignition Enabled or Ignition ON) for a period of more than 10 minutes without any state transitions, without any user interaction on the vehicle keypad (202), the vehicle (101) may automatically move into the pause state. If the vehicle (101) remains in pause state without any user interaction on the vehicle keypad (202) for more than 1 hour, the vehicle (101) may automatically sign out the user and moves into locked state. The auto lock and auto pause are security features as well as productivity features of the present invention. in terms of safety, it may prevent theft of vehicles deserted/stranded without anyone attending to it. It is a productivity feature as it may disallows vehicles to be left unutilized but assigned to a rider unnecessarily and makes the vehicle available for another user by automatically signing out such users. The auto pause and auto lock time intervals are configurable.
In the system (100), there may be a provision to detect a key use instead of using the vehicle keypad (202) to unlock the vehicle (101). In the key use detection step, when a rider uses a physical key instead of keyless entry via the vehicle keypad (202), then it may be detected by the voltage levels on ignition enable line and the vehicle state may get changed accordingly. Also, when key use is detected, the smart access/keyless entry mechanism may suspend, and the vehicle keypad (202) may get disabled until the key is removed. This is detected by key brought back to ignition enable off position (unlocked). The key use is detected and may send as an alert to the server/ cloud platform (104). If the vehicle (101) was accessed via keyless entry and while being signed in, if the rider uses key, the same actions as above may be implemented. The keyless entry mechanism and the vehicle keypad (202) may get disabled.

The foregoing description shall be interpreted as illustrative and not in any limiting sense. A person of ordinary skill in the art would understand that certain modifications could come within the scope of this disclosure. The embodiments, examples and alternatives of the preceding paragraphs or the description and drawings, including any of their various aspects or respective individual features, may be taken independently or in any combination. Features described in connection with one embodiment are applicable to all embodiments unless such features are incompatible.
,CLAIMS:We claim:
1. A vehicle (101) for enabling keyless access, the vehicle (101) comprising:
a vehicle keypad (202);
an Onboard Telematics and Control (OTC) (205), communicatively coupled with the vehicle keypad (202), the OTC (205) comprising,
an one-time password (OTP) generation engine (214), wherein the OTP generation engine (214) is configured to generate a vehicle side OTP, when a set of conditions are satisfied, wherein the vehicle side OTP is generated based on a current timestamp and a vehicle secret key, wherein the vehicle side OTP is generated upon receipt of user inputs through the vehicle keypad (202);
a validation engine (215) configured to receive a server OTP from the vehicle keypad (202), wherein the server OTP is received at a user device (102) of a user from a server/cloud platform (104), wherein the server/cloud platform (104) is configured to generate the server OTP upon receipt of OTP generation request from the user device (102), wherein the validation engine (215) is configured to unlock the vehicle (101) based on comparison of the vehicle side OTP and the server OTP.

2. The vehicle (101) as claimed in claim 1, wherein the OTP generation request comprises a vehicle identifier, wherein the vehicle identifier is captured by scanning a QR code displayed on the vehicle (101) by using the user device (102).

3. The vehicle (101) as claimed in claim 1, wherein the OTP generation request comprises the vehicle identifier, wherein the vehicle identifier is entered by the user by using the user device (102).

4. The vehicle (101) as claimed in claim 1, wherein the server/cloud platform (104) is configured to generate the server OTP based on the current timestamp and the secret key stored at the server, wherein the secret key stored at the server is selected based on the vehicle identifier.

5. The vehicle (101) as claimed in claim 1, wherein the server OTP is a session OTP and is configured to expire only when the user logs out (LOCK action) of the vehicle (101).

6. The vehicle (101) as claimed in claim 1, wherein the server OTP does not expire when the vehicle (101) is in temporary LOCK state or in pause state.

7. The vehicle (101) as claimed in claim 1, wherein the vehicle side OTP is a session OTP and is configured to valid only for a limited duration of time, wherein the limited duration refers to a time required to enter server OTP on the vehicle keypad (202) after successful activation of the vehicle keypad (202).

8. The vehicle (101) as claimed in claim 1, wherein the set of conditions comprises a battery (208) is present with no battery errors, wherein the battery (208) having a state of charge (SOC) greater than a predefined value.

9. The vehicle (101) as claimed in claim 1, wherein the set of conditions comprises a motor controller (213) is present with no motor controller error.

10. The vehicle (101) as claimed in claim 1, wherein the set of conditions comprises the vehicle (101) is currently not assigned or not accessed by a key by the user.

11. The vehicle (101) as claimed in claim 1, wherein the vehicle keypad (202) comprises a numeric keys to enter the OTP, a keys to change/select the state of the vehicle (101) and, a vehicle keypad activation key to activate the vehicle keypad (202), wherein the activation key further shows the current state of the vehicle (101).

12. A method for enabling keyless access of a vehicle (101), the method comprising:
Connecting, via a network (103), a user device (102) to a server/cloud platform (104);
Generating, via the server/cloud platform (104), a server OTP based on the receipt of OTP generation request from the user device (102);
Receiving, via the user device (102), a server OTP from the server/cloud platform (104);
Generating, via an one-time password (OTP) generation engine (214), a vehicle side OTP based on the receipt of user inputs through a vehicle keypad (202) based on a current timestamp and a vehicle secret key, when a set of conditions are satisfied, wherein an Onboard Telematics and Control unit (OTC) (205) is communicatively coupled with the vehicle keypad (202);
Receiving, via a validation engine (215), a server OTP from the vehicle keypad (202);
Comparing, via the validation engine (215), the vehicle side OTP and the server OTP;
Unlocking the vehicle (101), via the validation engine (215), based on the comparison of the vehicle side OTP and the server OTP.

13. The method as claimed in claim 12, wherein the OTP generation request comprises a vehicle identifier, wherein the vehicle identifier is captured by scanning a QR code displayed on the vehicle (101) by using the user device (102).

14. The method as claimed in claim 12, wherein the OTP generation request comprises the vehicle identifier, wherein the vehicle identifier is entered by the user by using the user device (102).

15. The method as claimed in claim 12, wherein the server/cloud platform (104) is configured to generate the server OTP based on the current timestamp and the secret key stored at the server, wherein the secret key stored at the server is selected based on the vehicle identifier.

16. The method as claimed in claim 12, wherein the server OTP is a session OTP and is configured to expire only when the user logs out (LOCK action) of the vehicle (101).

17. The method as claimed in claim 12, wherein the server OTP does not expire when the vehicle (101) is in temporary LOCK state or in pause state.

18. The method as claimed in claim 12, wherein the vehicle side OTP is a session OTP and is configured to valid only for a limited duration of time, wherein the limited duration refers to a time required to enter server OTP on the vehicle keypad (202) after successful activation of the vehicle keypad (202).

19. The method as claimed in claim 12, wherein the set of conditions comprises the battery (208) is present with no battery errors, wherein the battery (208) having a state of charge (SOC) greater than a predefined value.

20. The method as claimed in claim 12, wherein the set of conditions comprises the motor controller (213) is present with no motor controller error.

21. The method as claimed in claim 12, wherein the set of conditions comprises the vehicle (101) is currently not assigned or not accessed by a key by the user.

22. The method as claimed in claim 12, wherein the vehicle keypad (202) comprises a numeric keys to enter the OTP, a keys to change/select the state of the vehicle (101) and, a vehicle keypad activation key to activate the vehicle keypad (202), wherein the activation key further shows the current state of the vehicle (101).

Dated this 31st Day of December 2021