Sign In to Follow Application
View All Documents & Correspondence

Real Time Remote Work Monitoring Of A Vehicle

Abstract: ABSTRACT Monitoring of a vehicle. Embodiments herein relate to vehicles, and more particularly to monitoring a vehicle, using an on-board device. Embodiments herein disclose methods and systems for monitoring a vehicle using an on-board device, wherein the data collected by the on-board device is communicated to at least one electronic device. FIG. 1

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
27 February 2015
Publication Number
39/2016
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
patent@bananaip.com
Parent Application
Patent Number
Legal Status
Grant Date
2024-04-29
Renewal Date

Applicants

Mahindra & Mahindra Limited
Mahindra & Mahindra Ltd., MRV, Mahindra World City (MWC), Plot No. 41/1, Anjur Post, Chengalpattu, Kanchipuram District – 603204 (TN) INDIA

Inventors

1. Karthikeyan Srinivasan
Mahindra & Mahindra Ltd., Innovation Cell MRV, Mahindra World City (MWC), Plot No. 41/1, Anjur Post, Chengalpattu, Kanchipuram District – 603204 (TN) INDIA
2. Sirish Batchu
Mahindra & Mahindra Ltd., Infotronics Tech.- ATS MRV, Mahindra World City (MWC), Plot No. 41/1, Anjur Post, Chengalpattu, Kanchipuram District – 603204 (TN) INDIA

Specification

DESC:FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005

COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)

TITLE OF THE INVENTION

“Monitoring of a vehicle”

APPLICANTS:

Name Nationality Address
Mahindra & Mahindra Limited Indian Mahindra & Mahindra Ltd.,
MRV, Mahindra World City (MWC),
Plot No. 41/1, Anjur Post, Chengalpattu,
Kanchipuram District – 603004 (TN) INDIA

The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-
This application is based on and derives the benefit of Indian Provisional Application, 972/CHE/2015 the contents of which are incorporated herein by reference.

TECHNICAL FIELD
[001] Embodiments herein relate to vehicles, and more particularly to monitoring a vehicle, using an on-board device.

BACKGROUND
[002] Heavy machinery/engineering vehicles are deployed for handling heavy-duty jobs mainly in construction and agriculture fields, such as a tractor. The tractor is widely used for mechanizing agricultural tasks, mainly tillage work. Also, modern tractors are handling many other tasks in addition to tillage.
[003] In an example scenario, consider that an owner does not use the tractor himself, but his employee or another third party uses the tractor, or he may rent out tractors to others. In such situations, the owner is interested in knowing or remotely monitoring actual usage of his/her vehicle, as he may not be actually present where the vehicle is being used. Also, when it comes to construction and agriculture domains, it is not easy for a user to be present at the location of work and monitor the work.

OBJECTS
[004] The principal object of this invention is to propose methods and systems for monitoring a vehicle using an on-board device.
[005] Another object of the invention is to propose methods and systems for monitoring a vehicle using an on-board device, wherein the data collected by the on-board device is communicated to at least one electronic device.
BRIEF DESCRIPTION OF FIGURES
[006] This invention is illustrated in the accompanying drawings, through out which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[007] FIG. 1 depicts a vehicle equipped with a monitoring device and communicating with an external user device, according to embodiments as disclosed herein;
[008] FIG. 2 depicts an example wherein the vehicle is a tractor and the monitoring device is mounted on the PTO lever, according to embodiments as disclosed herein;
[009] FIG. 3 depicts the monitoring system, according to embodiments as disclosed herein;
[0010] FIG. 4 illustrates a plurality of components of the electronic device, according to embodiments as disclosed herein;
[0011] FIG. 5 is an example screenshot of the interface using which the user views data received from the monitoring device, according to embodiments as disclosed herein; and
[0012] FIG. 6 is a flowchart depicting the process of monitoring a vehicle, according to embodiments as disclosed herein.


DETAILED DESCRIPTION
[0013] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0014] The embodiments herein achieve methods and systems for monitoring a vehicle using an on-board device. Referring now to the drawings, and more particularly to FIGS. 1 through 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
[0015] Vehicle refers to a vehicle such as a tractor, construction vehicle, truck, van, or any vehicle comprising of a PTO (Power Take-Off) lever/shaft, or any other device with similar functionality.
[0016] FIG. 1 depicts a vehicle equipped with a monitoring device and communicating with an external user device. The vehicle 100 is equipped with a monitoring device 101. The monitoring device 101 can be connected to a lever and/or switch or any such suitable component of the vehicle 100, movement of which indicates active hours in terms of work being done. The monitoring device 101 can be mounted on the PTO lever 201 (as depicted in an example in FIG. 2, wherein the vehicle 100 in FIG. 2 is a tractor). The monitoring device 101 can collect at least one input such as but not limited to vibration of the lever to which the monitoring device 101 is connected.
[0017] The monitoring device 101 can communicate with at least one electronic device 102. The monitoring device 101 can communicate with the electronic device 102 using a suitable wired and/or wireless means. The electronic device 102 can be at least one of a mobile phone, a smart phone, a tablet, a computer, a wearable computing device, or any other device capable of communicating with the monitoring device 101. The monitoring device 101 can communicate with the electronic device 102 in real time. The monitoring device 101 can communicate with the electronic device 102 at pre-defined intervals. The monitoring device 101 can communicate with the electronic device 102 on pre-defined events occurring. The monitoring device 101 can also communicate with other entities such as a file server, a data server, the Cloud, and so on.
[0018] FIG. 3 is a diagram depicting the monitoring device. The monitoring device 101, as depicted, comprises of a controller 301, an accelerometer 302, at least one recording module 303, a communication interface 304, and a memory 305.
[0019] The recording module 303 can comprise at least one of a camera, a microphone, and so on. The camera can capture images from the rear of the vehicle 100. The communication interface 304 enables the monitoring device 101 to communicate with at least one external entity, such as the electronic device 102. The communication interface 304 can use at least one of wired and/or wireless means. In an example herein, the communication interface 304 can use at least one of a Bluetooth, GPRS (General Packet Radio Service), ZigBee, NFC (Near Field Communication), Wi-Fi, Wi-Fi Direct, LAN (Local Area Network), aux, USB (Universal Serial Bus), and so on. The memory 305 can be at least one of an internal memory, an expandable memory, a data server, a file server, the cloud, and so on. The memory 305 can be distributed in nature.
[0020] An authorized person using the communication interface 304 can configure the controller 301. The configuration can comprise of configuring the data transfer to the electronic device 102, the data to be captured by the device 101, the intervals at which the recording device 303 has to record data, and so on.
[0021] The controller 301 can collect at least one input such as but not limited to vibration of the lever to which the device 101 is connected. The accelerometer 302 can record the movement of the vehicle 100 and the vibrations present in the component to which the monitoring device 101 is attached. The accelerometer 302 can measure data such as when the engine of the vehicle 100 is OFF, vibration is at a zero level; when the engine of the vehicle 100 is ON, the vibration is non zero; and when the PTO is switched on or off using the lever, vibration levels shoot up. The controller 301 can receive inputs from the accelerometer 302. On receiving the input from the accelerometer 302, the controller 301 can fine-tune the received input, so as to make the data compatible for further analysis by the UE 102. The recording module 303 can capture information such as photos, videos, audio, and so on. The recording module 303 can provide the recorded information to the controller 301. The controller 301 can store the received data in the memory 305.
[0022] Based on the configured options, the controller 301 can provide the data to the electronic device 102, using the communication interface 304. The controller 301 can provide the data to the electronic device, on receiving a request from the electronic device 102, using the communication interface 304.
[0023] In an embodiment herein, the controller 301 can reset the monitoring device 101, on receiving an instruction from the electronic device 102.
[0024] In an embodiment herein, the controller 301 can detect tampering with the monitoring device 101. The controller 301 can detect whether the monitoring device 101 has been removed or tampered with during usage. The controller 301 can turn ON the monitoring device 101, only when the monitoring device 101 has been placed in the proper place and the connections are made in the required manner. On detecting that the device 101 has been loosened or removed, the controller 301 records the event in the memory 305 and switches off the monitoring device 101. On detecting that the device 101 has been placed or tightened, the controller 301 records the event in the memory 305 and switches on the monitoring device 101
[0025] FIG. 4 illustrates a plurality of components of the electronic device. Referring to figure 4, the electronic device 102 is illustrated in accordance with an embodiment of the present subject matter. In an embodiment, the electronic device 102 may include at least one processor 401, an input/output (I/O) interface 402 (herein a configurable user interface), and a memory 403. The at least one processor 401 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 401 is configured to fetch and execute computer-readable instructions stored in the memory 403.
[0026] The I/O interface 402 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface such as a display screen, a keyboard, and the like.
[0027] The I/O interface 402 may allow the electronic device 102 to communicate with other devices, such as the monitoring device 101. The I/O interface 402 may facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, Local Area network (LAN), cable, etc., and wireless networks, such as Wireless LAN, cellular, Device to Device (D2D) communication network, Wi-Fi networks, Bluetooth, and so on. The modules 404 include routines, programs, objects, components, data structures, and so on, which perform particular tasks, functions or implement particular abstract data types. In one implementation, the modules 404 may include a device operation module 405. The device operation module 405 can be configured to allow the user to handle one or more tasks of the application, such as configuring the monitoring device 101, receiving data from the monitoring device 101, viewing data received from the monitoring device 101. The device operation module 405 can comprise of a configuration module 406, and a vehicle monitoring module 407. The configuration module 406 can enable the user to configure at least one option related to the monitoring device 101. The electronic device 102 can be connected to more than one monitoring device 101. The vehicle monitoring module 407 can receive data from the monitoring device 101, using the I/O interface 402. The vehicle monitoring module 407 can enable the user to send a request to the monitoring device 101 to send data. The vehicle monitoring module 407 can analyze the received data to identify total hours of active work, and present the information to the user using a suitable user interface. The vehicle monitoring module 407 can enable the user to view the data using the I/O interface 402 (an example interface is depicted in FIG. 5, wherein the electronic device 102 is a smart phone). The vehicle monitoring module 407 can enable the user to view the recorded data using the I/O interface 402. The vehicle monitoring module 407 can enable the user to reset the monitoring device 101, as required. The vehicle monitoring module 407 can store the received data and analyzed data in the memory 403.
[0028] The modules 404 may include programs or coded instructions that supplement applications and functions of the electronic device 102. The data 408, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 404. The data 408 comprises of data received from the monitoring device 101. Further, the names of the other components and modules of the electronic device 102 are illustrative and need not be construed as a limitation.
[0029] FIG. 6 is a flowchart depicting the process of monitoring a vehicle. The monitoring device 101 detects (601) at least one trigger to initiate the data collection pertaining to working of the vehicle 100. For example, the trigger can be switching ON the engine of the vehicle, or a particular switch, or a lever, to which the monitoring device 101 is connected. In an embodiment, the type of trigger can be pre-defined and pre-configured by an authorized person. Upon detecting the trigger, the monitoring device 101 starts collecting (602) data from the vehicle. The data thus collected can be stored in the memory 305, and is then transmitted (603) to the electronic device 102. The electronic device 102 analyzes (604) the data collected from the event recording module 101, and segregates the data based on factors such as number of hours engine of the vehicle was kept ON, number of hours for which active work has been done, and so on. The electronic device 102 may consider the time period for which the lever or handle, which is used for active work, was kept ON/vibrating, and identifies (605) the total hours of active work. The total hours of active work can be presented to the user as number of hours of billable work, or any other format as configured by the user. The various actions in method 600 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 6 may be omitted.
[0030] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Figs. 1, 2 and 3 include blocks, which can be at least one of a hardware device, or a combination of hardware device and software module.
[0031] The embodiment disclosed herein describes methods and systems for monitoring a vehicle using an on-board device Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a software program written in e.g. Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.
[0032] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

STATEMENT OF CLAIMS
We claim:
1. A method for monitoring a vehicle, the method comprising:
capturing data related to the vehicle by a monitoring device, wherein the monitoring device is mounted on a Power Take-Off (PTO) lever present in the vehicle; and
transmitting the captured data to an electronic device, by the monitoring device.
2. The method, as claimed in claim 1, wherein the captured data comprises of at least one of vibration of the PTO lever; and movement of the vehicle.
3. The method, as claimed in claim 1, wherein the captured data comprises of a recording, wherein the recording comprises of at least one of a video; an image; and audio.
4. The method, as claimed in claim 1, wherein the method further comprises of checking if the monitoring device has been tampered.
5. The method, as claimed in claim 1, wherein the method further comprises of analysing the captured data by the electronic device.
6. A monitoring device mounted on a Power Take-Off (PTO) lever present in a vehicle, the monitoring device configured for:
capturing data related to the vehicle; and
transmitting the captured data to an electronic device.
7. The monitoring device, as claimed in claim 6, wherein the captured data comprises of at least one of vibration of the PTO lever; and movement of the vehicle.
8. The monitoring device, as claimed in claim 6, wherein the captured data comprises of a recording, wherein the recording comprises of at least one of a video; an image; and audio.
9. The monitoring device, as claimed in claim 6, wherein the monitoring device is further configured to check if the monitoring device has been tampered.
10. A vehicle comprising a monitoring device, wherein the monitoring device is mounted on a Power Take-Off (PTO) lever present in the vehicle, the monitoring device configured for:
capturing data related to the vehicle; and
transmitting the captured data to an electronic device.
11. The vehicle, as claimed in claim 10, wherein the captured data comprises of at least one of vibration of the PTO lever; and movement of the vehicle.
12. The vehicle, as claimed in claim 10, wherein the captured data comprises of a recording, wherein the recording comprises of at least one of a video; an image; and audio.
13. The vehicle, as claimed in claim 10, wherein the monitoring device is further configured to check if the monitoring device has been tampered.

Date: February 24th, 2016 Signature:
Dr..Kalyan Chakravarthy

ABSTRACT
Monitoring of a vehicle. Embodiments herein relate to vehicles, and more particularly to monitoring a vehicle, using an on-board device. Embodiments herein disclose methods and systems for monitoring a vehicle using an on-board device, wherein the data collected by the on-board device is communicated to at least one electronic device.

FIG. 1
,CLAIMS:STATEMENT OF CLAIMS
We claim:
1. A method for monitoring a vehicle, the method comprising:
capturing data related to the vehicle by a monitoring device, wherein the monitoring device is mounted on a Power Take-Off (PTO) lever present in the vehicle; and
transmitting the captured data to an electronic device, by the monitoring device.
2. The method, as claimed in claim 1, wherein the captured data comprises of at least one of vibration of the PTO lever; and movement of the vehicle.
3. The method, as claimed in claim 1, wherein the captured data comprises of a recording, wherein the recording comprises of at least one of a video; an image; and audio.
4. The method, as claimed in claim 1, wherein the method further comprises of checking if the monitoring device has been tampered.
5. The method, as claimed in claim 1, wherein the method further comprises of analysing the captured data by the electronic device.
6. A monitoring device mounted on a Power Take-Off (PTO) lever present in a vehicle, the monitoring device configured for:
capturing data related to the vehicle; and
transmitting the captured data to an electronic device.
7. The monitoring device, as claimed in claim 6, wherein the captured data comprises of at least one of vibration of the PTO lever; and movement of the vehicle.
8. The monitoring device, as claimed in claim 6, wherein the captured data comprises of a recording, wherein the recording comprises of at least one of a video; an image; and audio.
9. The monitoring device, as claimed in claim 6, wherein the monitoring device is further configured to check if the monitoring device has been tampered.
10. A vehicle comprising a monitoring device, wherein the monitoring device is mounted on a Power Take-Off (PTO) lever present in the vehicle, the monitoring device configured for:
capturing data related to the vehicle; and
transmitting the captured data to an electronic device.
11. The vehicle, as claimed in claim 10, wherein the captured data comprises of at least one of vibration of the PTO lever; and movement of the vehicle.
12. The vehicle, as claimed in claim 10, wherein the captured data comprises of a recording, wherein the recording comprises of at least one of a video; an image; and audio.
13. The vehicle, as claimed in claim 10, wherein the monitoring device is further configured to check if the monitoring device has been tampered.

Documents

Application Documents

# Name Date
1 972-CHE-2015-IntimationOfGrant29-04-2024.pdf 2024-04-29
1 Form5.pdf ONLINE 2015-03-03
2 FORM3.pdf ONLINE 2015-03-03
2 972-CHE-2015-PatentCertificate29-04-2024.pdf 2024-04-29
3 Form 2_PS.pdf ONLINE 2015-03-03
3 972-CHE-2015-PETITION UNDER RULE 137 [09-11-2023(online)]-1.pdf 2023-11-09
4 Drawings.pdf ONLINE 2015-03-03
4 972-CHE-2015-PETITION UNDER RULE 137 [09-11-2023(online)].pdf 2023-11-09
5 Form5.pdf 2015-03-13
5 972-CHE-2015-Written submissions and relevant documents [08-11-2023(online)].pdf 2023-11-08
6 FORM3.pdf 2015-03-13
6 972-CHE-2015-FORM-26 [06-10-2023(online)].pdf 2023-10-06
7 Form 2_PS.pdf 2015-03-13
7 972-CHE-2015-Correspondence to notify the Controller [05-10-2023(online)].pdf 2023-10-05
8 Drawings.pdf 2015-03-13
8 972-CHE-2015-US(14)-HearingNotice-(HearingDate-31-10-2023).pdf 2023-10-05
9 Drawing [24-02-2016(online)].pdf 2016-02-24
9 972-CHE-2015-CLAIMS [03-06-2020(online)].pdf 2020-06-03
10 972-CHE-2015-CORRESPONDENCE [03-06-2020(online)].pdf 2020-06-03
10 Description(Complete) [24-02-2016(online)].pdf 2016-02-24
11 972-CHE-2015-FER.pdf 2019-12-05
11 972-CHE-2015-FER_SER_REPLY [03-06-2020(online)].pdf 2020-06-03
12 972-CHE-2015-OTHERS [03-06-2020(online)].pdf 2020-06-03
13 972-CHE-2015-FER.pdf 2019-12-05
13 972-CHE-2015-FER_SER_REPLY [03-06-2020(online)].pdf 2020-06-03
14 972-CHE-2015-CORRESPONDENCE [03-06-2020(online)].pdf 2020-06-03
14 Description(Complete) [24-02-2016(online)].pdf 2016-02-24
15 972-CHE-2015-CLAIMS [03-06-2020(online)].pdf 2020-06-03
15 Drawing [24-02-2016(online)].pdf 2016-02-24
16 972-CHE-2015-US(14)-HearingNotice-(HearingDate-31-10-2023).pdf 2023-10-05
16 Drawings.pdf 2015-03-13
17 972-CHE-2015-Correspondence to notify the Controller [05-10-2023(online)].pdf 2023-10-05
17 Form 2_PS.pdf 2015-03-13
18 972-CHE-2015-FORM-26 [06-10-2023(online)].pdf 2023-10-06
18 FORM3.pdf 2015-03-13
19 972-CHE-2015-Written submissions and relevant documents [08-11-2023(online)].pdf 2023-11-08
19 Form5.pdf 2015-03-13
20 Drawings.pdf ONLINE 2015-03-03
20 972-CHE-2015-PETITION UNDER RULE 137 [09-11-2023(online)].pdf 2023-11-09
21 Form 2_PS.pdf ONLINE 2015-03-03
21 972-CHE-2015-PETITION UNDER RULE 137 [09-11-2023(online)]-1.pdf 2023-11-09
22 FORM3.pdf ONLINE 2015-03-03
22 972-CHE-2015-PatentCertificate29-04-2024.pdf 2024-04-29
23 Form5.pdf ONLINE 2015-03-03
23 972-CHE-2015-IntimationOfGrant29-04-2024.pdf 2024-04-29

Search Strategy

1 monitoringvehicle_06-11-2019.pdf

ERegister / Renewals

3rd: 13 Jun 2024

From 27/02/2017 - To 27/02/2018

4th: 13 Jun 2024

From 27/02/2018 - To 27/02/2019

5th: 13 Jun 2024

From 27/02/2019 - To 27/02/2020

6th: 13 Jun 2024

From 27/02/2020 - To 27/02/2021

7th: 13 Jun 2024

From 27/02/2021 - To 27/02/2022

8th: 13 Jun 2024

From 27/02/2022 - To 27/02/2023

9th: 13 Jun 2024

From 27/02/2023 - To 27/02/2024

10th: 13 Jun 2024

From 27/02/2024 - To 27/02/2025

11th: 03 Feb 2025

From 27/02/2025 - To 27/02/2026