DESC:Form 2
The Patent Act 1970
(39 of 1970)
AND
Patent Rules 2003
Complete Specification
(Sec 10 and Rule 13)
Title Method, System and Device for Smart Access to a Scooter
Applicant(s) Vogo Automotive Pvt. Ltd.
Nationality India
Address
#483, 17th Cross, 27th Main Road, Sector 2, HSR Layout,
Bengaluru-560102, Karnataka, India.
The following specification particularly describes the invention and the manner in
which it is to be performed.
2
DESCRIPTION
FIELD OF INVENTION
[0001] Embodiments of the present disclosure relate generally to smart access to a vehicle and
more specifically to a method, system and device for regulating a vehicle access.
RELATED ART
[0002] In recent times, many people are opting to rental vehicles and shared-use vehicles due to
various reasons such as parking issues, time management, heavy traffic, unaffordability etc.
There is a sharp rise in using the rental bikes and scooters all over the world and many systems
have been described for renting a vehicle and sharing access or shared-use vehicles. This has also
increased the concern of the vehicle owners or proprietors in protecting their rented vehicle in
terms of damage and operation.
[0003] Hence, few researchers have come up with a solution to provide smart/remote access to
the users of rental vehicles by getting the complete user information. However, these remote
access or smart access of the vehicle is enabled in the prior art by placing a huge box within the
vehicle to access the key. In recent days, few inventors have come up with a digitalized keypad
which need to be accessed by an OTP generated and sent to the registered mobile number.
Though, this digitalized keypad functionality is proved to be beneficial, it is bulky in nature and
takes time for accessing the vehicle in certain times due to poor network connectivity and other
external unforeseen factors. Further, in case of damage to the keypad, the user may not be able to
use the vehicle unless the keypad is replaced. Also, it is complex to use in poor vision climate
such as heavy rains or other external factors.
[0004] Hence, there is a need to simplify the system and provide an efficient, commercially
feasible and simple method and system for providing smart access to a vehicle.
SUMMARY
[0005] According to an aspect of the present disclosure, a system for providing smart access to a
vehicle comprising an electronic device (102) communicating a registered user details to a
central server (112), an integrated vehicle unit (106) to authenticate the registered user and
communicate with a central server (112) for smart access to the vehicle, an ignition switch
controller (126) and an under-seat storage accessing unit (124) configured within the integrated
vehicle unit (106) that are operated by a plurality of commands received from the central server
(112), and a data storage (110) to store the registered user details and plurality of parameters with
3
respect to a ride data received from the integrated vehicle unit (106), wherein the electronic
device (102) and the integrated vehicle unit (106) are connected to each other and communicates
with the central server providing smart access to the vehicle by providing access to the ignition
switch and seat lock/unlock configuration.
[0006] Several aspects are described below, with reference to diagrams. It should be understood
that numerous specific details, relationships, and methods are set forth to provide a full
understanding of the present disclosure. One who skilled in the relevant art, however, will readily
recognize that the present disclosure can be practiced without one or more of the specific details,
or with other methods, etc. In other instances, well-known structures or operations are not shown
in detail to avoid obscuring the features of the present disclosure.
BRIEF DESCRIPTION OF DRAWINGS
[0007] FIG. 1A is a block diagram of an example system in which various aspects of the present
invention may be seen.
[0008] FIG. 1B is a block diagram illustrating a vehicle unit integrated within a scooter/vehicle in
an embodiment of the present disclosure.
[0009] FIG. 1C is a block diagram illustrating the vehicle built-in components that are
communicated with the integrated vehicle unit.
[0010] FIG. 2A is a flowchart illustrating the steps involved in providing smart access to ignition
switch and seat lock buttons of the vehicle.
[0011] FIG. 2B is a flowchart illustrating the steps involved in immobilising the vehicle in case of
arbitration.
[0012] FIG. 2C is a flowchart illustrating the steps involved in determining status of the ride at
regular intervals.
[0013] FIG. 3A is a schematic diagram illustrating the ignition switch and seat lock buttons
integrated within the vehicle that are controlled by a central server in an exemplary embodiment
of the present disclosure.
[0014] FIG. 3B through 3D are the diagrams illustrating front, rear and perspective views of the
ignition switch and seat lock buttons in the vehicle.
[0015] FIG. 4 is a flowchart illustrating a method of providing smart access to the vehicle in yet
another embodiment of the present disclosure.
4
DETAILED DESCRIPTION OF THE PREFERRED EXAMPLES
[0016] FIG. 1A is a block diagram of an example system in which various aspects of the present
invention may be seen. The example system 101 is shown comprising an electronic device 102, a
vehicle unit 106, communication network 104, 108, a central server 112 and a data storage 110.
Each element is described in further detail below.
[0017] The vehicle unit 106 determines a plurality of parameters relating to the vehicle number,
status and condition of the vehicle such as fuel capacity, battery, pending traffic violation dues,
location of the vehicle and actuators. The determined parameters are tagged to or associated to a
profile of a registered user of the electronic device. In an embodiment, the vehicle unit 106
determines these parameters by communicating with the central server 112 over the wireless
communication network 108.
[0018] The electronic device 102 connects to the corresponding vehicle unit 106 through the
network 104 and stores the vehicle information from time to time. Further, the electronic device
102 may also connect to the central server for user authentication over the network 108. The
communication network 104 and 108 connects the electronic device 102, the vehicle unit 106 and
the central server 112 to each other independently or in combination. In one embodiment, the
communication network 104 may employ communication standards and protocols such as
Bluetooth, Wi-Fi, and alternatively any other short distance communication standards. Similarly,
the communication network 108 may employ communication standards and protocols such as
GSM, 3G, 4G, 5G etc. In an embodiment, the electronic device comprises a Bluetooth based
smartphone or mobile handset.
[0019] The central server 112 processes the information received from the vehicle unit, the
electronic device and the data storage 110 to trigger preconfigured commands in the vehicle unit
that operates and provides smart access to the associated vehicle. In one embodiment, the
processed information is shared between the vehicle unit, electronic device, central server and
data storage over the communication networks 104 and 108 to exploit available processing power
and reduce communication overheads on the devices.
[0020] Data storage 110 stores data received from the central server 112 that may comprise the
information received from the electronic device 102, processed results, indications and warnings,
profiles of the person etc., for further processing and reference. In one embodiment, the central
server 112 and the data storage 110 may be deployed in plurality of servers and storage units
5
spread over multiple geographical location or at same place that are interconnected to operate in
conjunction to provide the processing and storage resources to manage, control and process the
desired functionality of the system 101.
[0021] FIG. 1B is a block diagram illustrating the vehicle unit integrated within a scooter/vehicle
in an embodiment of the present disclosure. The vehicle unit is deployed within a vehicle and
configured to communicate with the central server 112, data storage 110 and the electronic device
102 over the communication networks 104 and 108. As shown there, the vehicle unit comprises a
processor 114, a memory unit 116, a wireless transceiver 118, a plurality of sensors 120, vehicle
built-in components, an ignition switch controller 126 and an under-seat storage accessing unit
124. Each element is further described in detail below.
[0022] The wireless transceiver 118 operates to transmit and receive the information to and from
the network 104 and 108. The wireless transceiver 118 may comprise encoder, modulator,
frequency translator, RF front end and antenna (that are not shown) interfaced to the other
elements on an integrated circuit for compact and power efficient deployment.
[0023] The plurality of sensors 120 operate to sense condition around the vehicle and captures
signal that determine the motional behaviour, pattern and characteristics and the plurality of
parameters of the vehicle. In one embodiment, the plurality of sensors 120 comprise inertial
navigation sensors like gyroscopes, accelerometers, magnetic compass, proximity sensor, motion
sensors, infrared, Lidar, Radar, camera, etc. Further, the plurality of sensors 120 may also
comprise sensors to monitor and determine the acceleration of the vehicle, detecting helmet, seat
lock, handle lock, wheel lock, ignition on/off detection and side stand detection.
[0024] The vehicle built in components 122 detects condition and status of the vehicle, like
ignition on/off, engine rpm, speed, load, cabin temperature, occupancy, engine temperature, fuel
etc. In one embodiment the vehicle built in components 122 are interfaced to the vehicle unit 106
through a communication bus, thus, making it a part of the vehicle unit 106. The communication
bus may be data interface lines like CAN bus or any other proprietary vehicle bus made available
for interfacing the vehicle built in components 122. The data and profile of the vehicle may also
be transferred on the CAN bus to the processor 114. The profile of the vehicle may comprise
engine type, make, power, braking, fuel type and analysis, gear assembly, axle weight, or any data
from OBD or telematics.
6
[0025] The processor 114 receives data from the plurality of sensors 120, vehicle built in
components 122, and wireless transceiver 118 and performs various operations such as signal
processing, image processing, on the data received to generate the plurality of parameters,
notifications, and alerts. Further, the processor 114 may transfer the data thus collected from the
plurality of sensors 120, vehicle built in components 122 through the wireless transceiver 118 to
the electronic device/vehicle unit/central server. The processor 114 may save the data received
from the plurality of sensors 120/vehicle built in components 122 in the memory 116 for further
processing or while processing.
[0026] The ignition switch controller 126 is configured to provide access to the ignition button
based on the commands received from the processor 114 of the vehicle unit. The vehicle unit 106
provides the commands either independently from the processed information of the processor 114
or in conjunction with the information received from the central server 112.
[0027] The under-seat storage accessing unit 124 is configured to provide access to the under-seat
storage compartment in the vehicle based in the inputs received from the central server 112. In an
embodiment, the ignition switch controller and the under-seat storage accessing unit together
works in conjunction with the inputs received from the central server 112. The central server 112
provides access to the ignition switch and seat lock/unlock buttons after authenticating the
registered user profile in the electronic device that is connected to the vehicle over the
communication networks 104 and 108.
[0028] FIG. 1C is a block diagram illustrating the vehicle built-in components that are
communicated with the integrated vehicle unit. In an embodiment, the vehicle unit determines
various parameters related to the user authentication and providing smart access to the vehicle
based on the plurality of parameters obtained from the vehicle built-in components such as geofencing
128, fuel detector 130, pulse detector 132, basement detector 134, helmet detector 136,
speed detector 138, location detector 140, starter detector 142 and battery level indicator 144.
Each element is further described below. In geo-fencing 128, the vehicle is configured to switch
the ignition ON by restricting the ride only for a specified range of particular region. In case of
any violation of geo-fencing, the vehicle gets immobilized by the central server 112.
[0029] The fuel detector 130 detects the amount of fuel present in the vehicle by determining
resistance values offered by a proprietary vehicle built-in fuel sensor of the vehicle. The pulse
7
detector 132 determines the frequency of rotating wheel to detect the pulse by using values of an
odometer sensor of the vehicle.
[0030] The basement detector 134 is configured to determine the location of the vehicle when the
vehicle enters a basement or a closed area based on Signal-to-Noise Ratio (SNR) and Received
Signal Strength Indication (RSSI) values of that corresponding vehicle unit. The helmet detector
136 helps to detect the presence of helmet in the vehicle wherein the ride remains continue until
the helmet is replaced in its original position within the vehicle.
[0031] The speed detector 138 determines the speed of the vehicle based on the rate of change in
pulse on the vehicle. The location detector 140 considers latitude and longitude of the GPS and
GSM module coupled to the vehicle unit for tracking movement of the vehicle.
[0032] The starter detector 142 detects the start of a ride in the vehicle by sensing the ignition
button of the vehicle is ON/OFF and sends the information to the central server 112 for change the
status of the ride from ride booked to ride active. The battery level indicator 144 detects the
battery charge by measuring the voltage of the vehicle battery. In an embodiment, the outputs of
all these vehicle built-in components are fed to the processor of the vehicle unit as well as to the
central processor to determine authenticity of the user, vehicle condition thereby providing smart
access to the vehicle.
[0033] FIG. 2A is a flowchart illustrating the steps involved in providing smart access to ignition
switch and seat lock buttons of the vehicle. In step 202, a vehicle with an integrated vehicle unit of
the present disclosure is identified. Initially, the identified vehicle is in sleep mode and beaconing
its presence with minimum consumption of battery charge.
[0034] In step 204, a registered electronic device or an electronic device comprising an
application with registered user profile is used to scan a QR code present on the vehicle. This
enables the central server to book a ride on the vehicle corresponding to that QR code.
[0035] In step 206, the registered user profile and mac address of the electronic device that is
trying to connect with the vehicle are retrieved and sent back to the user profile for authentication
purpose. This connects the vehicle unit and the registered user profile in the electronic device and
tagged or associated with the status of “ride booked” in the central server.
[0036] In step 208, the electronic device connected to the vehicle is forced to enable the wireless
communication channel for example, Bluetooth in order to pair with the vehicle unit integrated
within the vehicle.
8
[0037] In step 210, the ignition and seat lock/unlock buttons are given access to the registered user
once the electronic device is paired with the vehicle unit. Thus, the registered user is able to
switch on ignition button and start the vehicle as well as unlock the seat so that under-seat storage
is made accessible.
[0038] In step 212, the moment the ignition switch is ON and the ride has started, the status of the
“ride booked” in the central server is changed to the “ride active” based on the inputs i.e., ignition
status received from the vehicle unit.
[0039] FIG. 2B is a flowchart illustrating the steps involved in immobilising the vehicle in case of
arbitration. In step 212, the status of the ride gets updated in the central server as “ride active” and
periodically gets updated at regular intervals of time.
[0040] In step 214, various parameters of the vehicle status and ride status are determined based
on the inputs received from the vehicle built-in components as well as the ignition switch
controller and the under-seat storage accessing unit. These parameters are further fed to the central
server and the data storage for further processing and updating.
[0041] In step 216, the determined plurality of parameters is analysed by the server for any user
compliance violations such as geo-fencing or misuse of the vehicle against the terms and
conditions as laid by the vehicle owner.
[0042] In step 218, if any user compliance violation is found or in case of any other arbitration,
the vehicle gets immobilised by the central server once the ignition switch is turned off.
[0043] FIG. 2C is a flowchart illustrating the steps involved in determining status of the ride at
regular intervals. In step 222, the plurality of parameters from the vehicle built-in components are
determined and analysed to know the real time status of the ride. The real time information is fed
to the central server over a communication network at regular intervals of time to trigger various
commands in the vehicle unit.
[0044] In step 224, the sleep mode in the vehicle unit is triggered when the user pauses the ride by
choosing pause ride option from the registered electronic device. This pushes the vehicle into
sleep mode without ending the ride so that the user can resume the ride only by using the same
registered electronic device connected to the vehicle unit.
[0045] In step 226, the user may resume or end the ride which gets communicated immediately to
the central server by the vehicle unit. The central server analyses the status of the ride and
plurality of parameters for any arbitration and ends the ride if no arbitration is found. In case of
9
any arbitration, the vehicle gets immobilised by the central server and alerts the concerned official
or owner of the vehicle along with the registered user of the vehicle.
[0046] In step 228, the paired electronic device is then disconnected with the vehicle unit once the
end ride is registered and updated in the status of the central server. Thus, the ride is ended and
communicated to the registered user after checking the user compliance violations.
[0047] In step 230, a receipt gets generated by the central server within the registered user account
for using the vehicle and the user gets charged for that corresponding amount. Thus, the ride gets
ended and the vehicle undergoes the sleep mode enabling other users to book a ride.
[0048] FIG. 3A is a schematic diagram illustrating the ignition switch and seat lock buttons
integrated within the vehicle that are controlled by a central server in an exemplary embodiment
of the present disclosure. As shown in the figure, the lock key of an existing vehicle is replaced
with the ignition ON/OFF and seat Unlock buttons that are coupled to the ignition switch
controller and under-seat storage accessing unit of the vehicle unit. This allows the vehicle unit to
control the smart access to the ignition and seat lock buttons based on the inputs received from the
central server.
[0049] FIG. 3B through 3D are the diagrams illustrating front, rear and perspective views of the
ignition switch and seat lock buttons in the vehicle. As shown there, the ignition ON/OFF 310 and
seat unlock 320 buttons are coupled together and connected to the vehicle unit 106 of the present
disclosure that is integrated within the vehicle. Thus, the vehicle unit of the present disclosure
plays a vital role in providing smart access to the ignition ON/OFF 310 and seat unlock 320
buttons based on the inputs from the central server.
[0050] FIG. 4 is a flowchart illustrating a method of providing smart access to the vehicle in yet
another embodiment of the present disclosure. In step 402, the integrated vehicle unit of the
present disclosure is in sleep mode consuming minimum battery charge. In an embodiment, the
vehicle unit is preconfigured with advertisements that may be displayed on a display screen
coupled to the vehicle. In step 404, the user scans the QR code placed on the vehicle through a
smart controller/application installed on his\her electronic device. In step 406, the ride status gets
changed from sleep mode to “ride booked” after scanning the QR code. In an embodiment, the
QR code associated with the vehicle number is registered as “ride booked” at the server end.
[0051] In step 408, the smart controller/application installed on his\her electronic device is
connected to the vehicle based on the mac address of the smart controller or the electronic device
10
paired with the booked vehicle number information on the central server. Further, the mac ID of
the device is sent back to the user’s application, notifying the connectivity access to the user.
[0052] In step 410, the smart controller/electronic device is forced to switch on wireless
communication means for example, Bluetooth in order to pair with the integrated vehicle unit. The
pairing of the smart controller/electronic device with the vehicle unit is checked and if the pairing
is successful, it goes to step 420 or else to step 412. In step 412, the user gets a notification of
unsuccessful pairing of the device with the vehicle unit and asked to trigger SMS mode of pairing
by long pressing the ignition ON/OFF button for at least 3 seconds of predetermined period of
time. In step 414, the SMS containing “ride access” command is triggered at the server end and
communicates the same to the vehicle unit. In step 416, the vehicle unit receives the SMS
command from the server and enables the vehicle to accept SMS to provide smart access to the
vehicle. In step 418, the SMS received by the user on his/her registered mobile number or the
registered user profile needs to be validated. If the SMS validation is successful, it goes to step
420 or else to step 402.
[0053] In step 420, the status of the ride gets updated in the central server as “ride active” and
gives access to the ignition and seat unlock buttons for the registered user. Once the ride active
mode is enabled in the step 420, the ignition button and the seat unlock buttons are monitored
regularly at a pre-programmed period of time to check whether the ignition is ON or OFF (422 &
424) and the seat unlock button is accessible or not (426).
[0054] In step 430, the user may chose pause or end ride from the smart controller/electronic
device connected to the vehicle unit. In case of pause ride, the control goes to step 420. In step
432, if the ignition is turned OFF, it goes to step 402 or else to step 430. In step 428, the status of
the ride as well as plurality of parameters from the vehicle built-in components and the vehicle
unit are determined and analysed by the central server at regular intervals for example, for every 2
seconds when ignition is ON and for every 1 hour when the ignition is OFF.
[0055] In step 434, the central system checks for any arbitration and if yes, it goes to step 436 or
else to step 438. In step 436, the central server sends a command to the vehicle unit to immobilise
the vehicle in case of arbitration. This immobilises the vehicle after ignition is turned off from the
time immobilization command is triggered. In step 438, the vehicle remains mobilized.
[0056] While various embodiments of the present disclosure have been described above, it should
be understood that they have been presented by way of example only, and not limitation. Thus, the
,CLAIMS:CLAIMS
I/We Claim,
1. A system (101) for providing smart access to a vehicle comprising:
an electronic device (102) communicating a registered user details to a central server (112);
an integrated vehicle unit (106) to authenticate the registered user and communicate with a
central server (112) for smart access to the vehicle;
an ignition switch controller (126) and an under-seat storage accessing unit (124) configured
within the integrated vehicle unit (106) that are operated by a plurality of commands
received from the central server (112); and
a data storage (110) to store the registered user details and plurality of parameters with
respect to a ride data received from the integrated vehicle unit (106) and the electronic
device (102),
wherein the electronic device (102) and the integrated vehicle unit (106) are connected to
each other over a communication network and communicates with the central server
providing smart access to the vehicle by providing access to the ignition and seat
lock/unlock button configuration.
2. The system as claimed in claim 1, wherein the electronic device (102) comprises a
Bluetooth based mobile handset connected to the central server (112) over a communication
network (104).
3. The system as claimed in claim 1, wherein the electronic device (102) sends a connection
request to the central server (112) by scanning a digital code on the vehicle.
4. The system as claimed in claim 1, wherein the central server (112) updates status of a ride
associated with the vehicle as ride booked after receiving a connecting request from the
electronic device (102) to connect with the vehicle.
5. The system as claimed in claim 1, wherein the central server (112) stores vehicle number
and associated vehicle information that is connected with the electronic device (102) in the
data storage along with the registered user, date and time of connection request and
necessary parameters that are fetched from the electronic device.
6. The system as claimed in claim 1, wherein the central server (112) sends an access
command to the integrated vehicle unit (106) after authenticating the registered user in the
electronic device that is connected to the vehicle.
13
7. The system as claimed in claim 1, wherein the integrated vehicle unit (106) grants access to
the registered user of the electronic device (102) after receiving the access command from
the central server (112) to access the ignition and seat unlock buttons.
8. A method of regulating vehicle access comprising:
connecting (204) a registered electronic device to a vehicle unit in sleep mode for booking a
ride;
retrieving (206) a registered user profile and mac address of the connected electronic device;
pairing (208) the vehicle unit and the registered electronic device through a wireless
communication channel;
providing (210) access to an ignition and seat lock buttons in the vehicle;
activating (212) ride mode for an associated vehicle with the paired vehicle unit at a central
server station;
determining (214) and analyzing (222) parameters of the ride for assessing the user
compliance violation and status of the ride;
immobilizing (218) the vehicle in case of any arbitration; and
disconnecting the paired vehicle unit and the registered electronic device at the end of the
ride,
wherein the parameters of the ride comprising status of ride, location of the vehicle, vehicle
condition are assessed to provide smart access to the vehicle by the central server station.
9. A method, system and apparatus providing one or more features as described in the
paragraphs of this specification.