Description:REMOTE VEHICLE IMMOBILISATION SYSTEM

FIELD OF THE DISCLOSURE
[0001] This invention generally relates to a field of vehicle immobilisation, in particular relates to a remote vehicle immobilisation system without using sensors or any hardware change in the vehicle.

BACKGROUND
[0002] An immobilizer is a vehicle security system designed to prevent unauthorized ignition of engine, providing an effective deterrent against theft. The immobilizer works by electronically linking the vehicle's ignition system to an authorized key or signal, ensuring that only approved users start and operate the vehicle. The immobilizer is typically integrated into the vehicle's electronic control unit (ECU) and functions by recognizing a unique code embedded in the key or fob. When the key or fob is inserted into the ignition or brought within range, the immobilizer system checks the code against a stored, pre-programmed list. If the code matches, the system allows the engine to crank and start. If the code is invalid or absent, the system prevents the engine from starting, effectively disabling the vehicle and protecting it from theft. Modern immobilizers may also incorporate advanced technologies, such as RFID (Radio Frequency Identification), to enhance security.
[0003] Conventional immobilization methods often involve the installation of additional hardware, which increase costs and complicate the process. These hardware modifications also affect the vehicle’s warranty and require skilled labor for installation and ongoing maintenance. Conventional immobilization methods often involve the installation of physical devices such as steering wheel locks, kill switches, or additional wiring that interfere with the vehicle's electrical system. These systems tend to be costly and require significant time and effort to install.
[0004] According to a patent application “US20140229061A1” titled “CAN based vehicle immobilizer” discloses a vehicle immobilizer which utilizing the CAN bus (204) of the engine (powertrain) CAN connection on the OBDII/J1962 port or the vehicle CAN system, will completely immobilize a vehicle, preventing use of said vehicle and the starting of said vehicle engine. The vehicle immobilizer system can be installed by a 3rd party on an aftermarket basis and used to immobilize a vehicle despite an immobilization system being already present on said vehicle is not accessible by said 3rd party. The vehicle immobilizer system enables a user to immobilize the vehicle engine efficiently without shorting the CAN network bus lines, and with a minimum of modifications to the vehicle. The vehicle immobilizer system enables a user to immobilize a vehicle from starting the engine and from being driven with minimal modifications to vehicle wiring and with limited to no changes to the vehicle electrical system.
[0005] According to another patent application “US8056538B2” titled “Method and system to prevent unauthorized uses of engine controllers” discloses a method and control module for enabling or disabling control of an engine includes a check module receiving signals through a wiring harness and comparing the check signals to a threshold. The control module also includes an engine control module disabling the engine when the check signals correspond to an unauthorized us.
[0006] The cited prior arts and also the current systems and processes for vehicle immobilization during theft often involves modifications in the vehicle using sensors and other forms of electronics. Further, improper installation or system malfunctions due to these modifications could inadvertently affect the performance of other vehicle components, leading to potential repair costs and vehicle downtime.
OBJECTIVES OF THE INVENTION
[0007] The objective of invention is to provide a remote vehicle immobilisation system that leverages the vehicle's existing electronic control units (ECUs) and utilizes CAN (Controller Area Network) messages for communication during the vehicle immobilization.
[0008] The objective of invention is to provide the remote vehicle immobilisation system that disables the ignition from engine or locks key operations to immobilize the vehicle in the event of unauthorized access or theft attempts.
[0009] Furthermore, the objective of present invention is to provide the remote vehicle immobilisation system that integrates the vehicle’s existing sensors to continuously monitor signals and perform immobilization actions when unauthorized by owner of the vehicle.
[0010] Furthermore, the objective of present invention is to provide the remote vehicle immobilisation system that offers robust theft prevention by enabling control over the vehicle even if an unauthorized individual gains access to the keys.
[0011] Furthermore, the objective of present invention is to provide the remote vehicle immobilisation system that is operated remotely using telematics to provide seamless and flexible vehicle security management.
SUMMARY
[0012] According to an aspect, the present invention discloses a remote vehicle immobilisation system comprising a computing unit configured to initiate an immobilisation request for a vehicle, a cloud database communicatively coupled to the computing unit to store at least a vehicle information, a telematics server module communicatively coupled to the computing unit to identify the vehicle based at least on the vehicle information, generate one or more command message based at least on the received immobilisation request and send the generated one or more command message to the identified vehicle. Further, the system comprises a telematics module wherein the telematics module is configured to generate a CAN (Controller Area Network) message based at least on the received one or more command message. The telematics server module facilitates the ECU to compare the CAN message received from the telematics module with respect to a default CAN message and activate an engine auxiliary shutdown switch of the vehicle based at least on the CAN message to immobilise the vehicle.
[0013] In some embodiments, the ECU is configured to activate the engine auxiliary shutdown switch when the CAN message is different from the default CAN message, wherein the engine auxiliary shutdown switch is configured to control fuel supply and/or ignition of the vehicle based at least on the CAN message. Further, the ECU is configured to generate a user feedback over the computing unit upon immobilisation of the vehicle.
[0014] In some embodiments, upon immobilising the vehicle, the ECU is configured to re-change the CAN message to reset the vehicle. Further, upon activating the engine auxiliary shutdown switch, the ECU is configured to crank the vehicle.
[0015] In some embodiments, the system further comprises a cloud database communicatively coupled to the computing unit, wherein the cloud database is configured to store the vehicle information. Further, the vehicle information corresponds to a vehicle registry.
[0016] In some embodiments, the system further comprise a communication module configured to communicatively couple the telematics server module and the cloud database to the computing unit and the ECU. The communication module corresponds to the CAN (Controller Area Network) bus.
[0017] In some embodiments, the computing unit is installed with a user interface that is accessed by a user to generate the immobilisation request for the vehicle.
[0018] According to an aspect, the present invention discloses a method for immobilising a vehicle remotely. The method comprising the steps of initiating, via a computing unit, an immobilisation request for a vehicle, identifying, via a telematics server module communicatively coupled to the computing unit, the vehicle based at least on the vehicle information, generating, via the telematics server module integrated with the vehicle, one or more command message based at least on the received immobilisation request, sending, via the telematics server module, the generated one or more command message to the identified vehicle, generating, via a telematics module integrated with the vehicle a CAN (Controller Area Network) message based at least on the received one or more command message, comparing, via an electronic control unit (ECU) facilitated by the telematics module, the CAN message received from the telematics module with respect to a default CAN message, and activating, via the ECU, an engine auxiliary shutdown switch of the vehicle based at least on the CAN message to immobilise the vehicle.
BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings illustrate various embodiments of systems, methods, and embodiments of various other aspects of the disclosure. Any person with ordinary skills in the art will appreciate that the illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures represent one example of the boundaries. It may be that in some examples one element may be designed as multiple elements or that multiple elements may be designed as one element. In some examples, an element shown as an internal component of one element may be implemented as an external component in another, and vice versa. Furthermore, elements may not be drawn to scale. Non-limiting and non-exhaustive descriptions are described with reference to the following drawings. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating principles.
[0020] FIG. 1 illustrates a block diagram of a remote vehicle immobilisation system, according to an embodiment of the present invention;
[0021] FIG. 2 illustrates an architectural diagram of the remote vehicle immobilisation system, according to an embodiment of the present invention;
[0022] FIG. 3 illustrates a flowchart depicting working of the remote vehicle immobilisation system, according to an embodiment of the present invention; and
[0023] FIG. 4 illustrates a flowchart of a method for immobilising a vehicle remotely, according to an embodiment of the present invention.

DETAILED DESCRIPTION
[0024] Some embodiments of this disclosure, illustrating all its features, will now be discussed in detail. The words “comprising,” “having,” “containing,” and “including,” and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items or meant to be limited to only the listed item or items. It must also be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise.
[0025] Although any systems and methods similar or equivalent to those described herein can be used in the practice or testing of embodiments of the present disclosure, the preferred, systems and methods are now described. Embodiments of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings in which like numerals represent like elements throughout the several figures, and in which example embodiments are shown. Embodiments of the claims may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. The examples set forth herein are non-limiting examples and are merely examples among other possible examples.
[0026] The present invention discloses about a remote vehicle immobilisation system. The embodiments comprise a computing unit, a telematics server module, a telematics module and an electronic control unit (ECU). The embodiments are configured to immobilise the vehicle during an unauthorized attempt of theft.
[0027] FIG. 1 illustrates a block diagram of a remote vehicle immobilisation system (100), according to an embodiment of the present invention. FIG. 2 illustrates an architectural diagram (200) of the remote vehicle immobilisation system (100), according to an embodiment of the present invention. FIG. 2 is explained in conjunction with FIG. 1.
[0028] In some embodiments, the remote vehicle immobilisation system (100) comprises a computing unit (102). It may be noted that the term remote vehicle immobilisation (100) and system (100) is used interchangeably. In some embodiments, the computing unit (102) is operated by a user to initiate an immobilization request for a vehicle (104). The immobilisation request corresponds to a command to turn on the vehicle (104) or turn off the vehicle (104) given by the user over the computing unit (102). The computing unit (102) may further be installed with a user interface (202) as shown in FIG.2, that is accessed by the user to generate the immobilisation request. In an example, the computing unit (102) corresponds to a smartphone, a tablet, a laptop or alike. The user is able to control one or more functions of the vehicle (104) using the user platform installed on the computing unit.
[0029] In some embodiments, a cloud database (106) is communicatively coupled to the computing unit (102). The cloud database (106) stores at least a vehicle information. The vehicle information corresponds to a vehicle registry (208). In an example, the vehicle information may also correspond to model, unique identification number (VIN), registration details, and potentially even the vehicle’s immobilization history or status. The vehicle information stored in the cloud database (106) is accessed remotely by the user via the computing unit (102).
[0030] In some embodiments, a telematics server module (108) is linked to the computing unit (102). The telematics server module (108) is configured to identify the vehicle (104) based at least on the vehicle information and the immobilisation request. The telematics server module (108) serves as an intermediary between the computing unit (102) and the vehicle (104). The telematics server module (108) is responsible for processing requests and managing communication between the user and the vehicle (104). In some embodiments, once the immobilisation request is generated by the user, via the computing unit (102), the immobilisation request is processed by ECU (112). In some embodiments, the immobilization request is transmitted towards the telematics server module (108) by means of an API gateway (204) as shown in FIG. 2.
[0031] The API gateway (204) acts as a mediator, ensuring data integrity and manages the immobilisation request to be transmitted towards the telematics server module (108) and other backend mechanisms. Additionally, the API gateway (204) provides feedback (214) to the user in case of errors or successful execution, enabling seamless interaction between the user interface and the telematics server module (108).
[0032] In an example, when the user initiates an immobilization request, the telematics server module (108), identifies the vehicle (104) by cross-referencing the vehicle information stored in the cloud database (106) with the immobilization request details. The ECU (112) verifies details such as the vehicle's unique identifiers (like the VIN), current location of the vehicle (104), or other relevant data provided by the user. By linking the vehicle information with the immobilization request, the telematics server module (108) via the ECU (112) helps to ensure that only the authorized user initiate the immobilisation request.
[0033] In some embodiments, a telematics module (110) is integrated with the vehicle (104). The telematics module (110) is configured to generate a CAN (Controller Area Network) message based at least on the vehicle (104) identified, the vehicle information and the immobilisation request. The telematics module (110) are usually integrated with the vehicle (104) to facilitate communication between the vehicle (104) and one or more external devices such as the computing unit (102). Further, the telematics module (110) is configured to collect real time status of the vehicle (104).
[0034] In an example, when the immobilization request is generated by the user, via the computing unit (102), the telematics server module (108) generate one or more command message based at least on the received immobilisation request and send the generated one or more command message to the identified vehicle (104). The one or more command messages correspond to immobilise CAN signal (210) that contains information (212) related to immobilisation of the vehicle (104). Further, the vehicle’s telematics module (110) generates a CAN (Controller Area Network) message based at least on the received one or more command message. In an example, the telematics module (110) generates the CAN message based at least on the vehicle identified, the vehicle registry (208) and the immobilisation request.
[0035] The CAN message is a standardized communication protocol used in vehicles to allow various control units (such as the engine control module, transmission, or immobilizer) to communicate with the computing unit (102) via the telematics server module (108). Further, ECU (112) may be integrated with the vehicle (104) and communicatively coupled to the telematics module (110) via a communication module (114). The communication module (114) may correspond to CAN (Controller Area Network) bus (204). The ECU (112) corresponds to electronic control units (ECUs) within the vehicle (104). Further, the communication module (114) uses the CAN bus protocol to transmit the CAN messages. The communication module (114) uses the CAN bus protocols to transmit commands from the ECU (112) to the ECUs.
[0036] In an example, when the user generates the immobilisation request via the computing unit (102), the telematics module (110) generates the CAN message based on the vehicle (104) identified by the telematics server module based on match between the immobilisation request and the vehicle registry (208). Further, the ECU (112) compares the CAN message received from the telematics module (110) with respect to a default CAN message.
[0037] In an example, the default CAN message corresponds to “Tx 0x18F0010Bx8 00 00 00 00 00 00 00 00”, wherein the CAN message is transmitted with data filled with zeros. The default CAN message represents an inactive condition of the vehicle, preparing the remote vehicle immobilisation system (100) for further action. In an example, when the CAN message is updated with a specific value ‘10’ in one of the data fields, then the ECU (112) activates the engine auxiliary shutdown switch of the vehicle (104), that signals the ECU to initiate shutdown process of the vehicle. In some embodiments, the engine auxiliary shutdown switch is configured to control fuel supply and/or ignition of the vehicle (104). Once the engine auxiliary shutdown switch of the vehicle (104) is activated, then the ECU deactivates the engine of the vehicle (104) by cutting off the fuel supply, disabling the ignition or stopping the cranking mechanism, thus immobilizing the vehicle (104). In some embodiments, the ECU (112) is configured to generate a user feedback (214) over the computing unit (102) upon immobilisation of the vehicle (104). In an example, the ECU sends a confirmation back to the user interface, informing the user of the vehicle immobilization status (e.g. "Vehicle Immobilized").
[0038] In some embodiments, upon immobilising the vehicle (104), the ECU (112) is configured to re-change the CAN message to reset the vehicle (104). Further, upon activating the engine auxiliary shutdown switch, the ECU (112) is configured to crank the vehicle (104). In an example, once the engine shutdown is complete, the CAN message is transmitted again with the data fields as zeros, representing that the vehicle (104) is ready for reactivation. Further, following the engine shutdown, the vehicle (104) enters cranking phase, representing that the vehicle (104) is prepared to restart the engine.
[0039] FIG. 3 illustrates a flow chart (300) depicting working of the remote vehicle immobilisation system, according to an embodiment of the present invention. FIG. 4 illustrates a flowchart (400) of a method for immobilising a vehicle remotely, according to an embodiment of the present invention. FIG. 3 is explained in conjunction with FIG. 4.
[0040] At step (402), an immobilisation request for a vehicle (104) is initiated via a computing unit (102). In an example, the computing unit (102) corresponds to a smartphone, a tablet, a laptop or alike. The computing unit (102) may further be installed with a user interface (200) as shown in FIG.2, that is accessed by the user to generate the immobilisation request.
[0041] In an example, consider a fleet manager overseeing a group of vehicles for a logistics company. One day, the manager notices that vehicle 104 is off-route and might be at risk of theft. The manager operates the computing unit (102) designed to manage the fleet, the manager accesses the user interface on the computing unit (102), which displays a map with the locations of all vehicles and various control options. Upon spotting suspicious movement of the vehicle (104), the manager taps the "Immobilize Vehicle" button on the user interface. This action sends an immobilization request to the vehicle.
[0042] At step (404), the vehicle (104) is identified by the telematics server module (108) based at least a vehicle information that is stored in a cloud database (106). The cloud database (106) stores at least a vehicle information. The vehicle information corresponds to a vehicle registry (208). In an example, the vehicle information may also correspond to model, unique identification number (VIN), registration details, and potentially even the vehicle’s immobilization history or status. The vehicle information stored in the cloud database (106) is accessed remotely by the user via the computing unit (102).
[0043] In an example, the vehicle information (of the vehicle 104) is stored in the cloud database (106) that is connected to the manager's computing unit 102. The information stored in the cloud database (106) could include details such as the vehicle's model, unique identification number (VIN), registration details, and potentially a history of previous immobilization requests or the vehicle's status (e.g., if it has been immobilized before). For instance, the cloud database (106) might also track the last time the vehicle was immobilized, providing a complete history for the fleet manager.
[0044] Further, When the immobilization request is sent, the telematics server module (108) checks the vehicle’s information in the cloud database (106), identifies the vehicle (104) using data like the VIN or model, and confirms that the immobilization request corresponds to the correct vehicle. The telematics server module (108) then processes the request, ensuring that the proper actions are taken to immobilize the vehicle (104).
[0045] At step (408), a telematics module (110) generates one or more command messages to identify the vehicle (104). Further, at step (410), the one or more command messages are sent to the identified vehicle. At step (412), the telematics module (110) integrated with the vehicle (104) generates a CAN (Controller Area Network) message based at least on the received one or more command message. The telematics module (110) are usually integrated with the vehicle (104) to facilitate communication between the vehicle (104) and one or more external devices such as the computing unit (102).
[0046] In an example, telematics module (110) sends the CAN message to the vehicle’s ECU (112), containing the instructions to shut down or prevent ignition of the vehicle’s engine. The CAN message carry information about the vehicle’s unique identification (VIN), model, and immobilization status, ensuring the message is processed only for the vehicle 104.
[0047] At step (412), the ECU (112) integrated with the vehicle (104) and communicatively coupled to the telematics module (110) via a communication module (114) compares the CAN message received from the telematics module (110) with respect to a default CAN message. At step (414), the ECU (112) activates an engine auxiliary shutdown switch of the vehicle (104) based at least on the CAN message to immobilise the vehicle (104).
[0048] In an example, the initiation of the vehicle (104) control via the remote vehicle immobilisation system (100) is illustrated in FIG. 3. When the vehicle (104) is activated, the ECU (112) communicates over the CAN bus (206). The ignition switch enables the transmission and reception of CAN messages. Further, the ECU (112) uses the J1939 protocol, a standardized communication protocol for vehicles, to facilitate data exchange between various ECUs. Further, a specific CAN message is sent when the vehicle (104) is identified by the telematics module (110) on the basis of the unique identifier in the vehicle registry (208). The key identifier includes key information, such as message priority, source, and destination address, and indicates the specific function.
[0049] Further, the engine auxiliary shutdown switch is controlled based on the transmitted CAN message. The various data fields within the CAN message determine the action of the engine auxiliary shutdown switch. Initially, the CAN message is transmitted with a data field filled with zeros i.e. (Tx 0x18F0010Bx8 00 00 00 00 00 00 00 00). Once the shutdown switch is triggered, the engine is deactivated. This may involve cutting off the fuel supply, disabling ignition, or stopping the cranking mechanism, effectively immobilizing the vehicle (104). After the engine shutdown is complete, the CAN message is transmitted again with a data field of all zeros. This reset transmission indicates that the vehicle (104) is ready for reactivation. Following the engine shutdown and the resetting of the CAN message, the vehicle (104) enters the cranking phase. The vehicle (104) is prepared to restart the engine, completing one cycle.
[0050] The system (100) enables immobilisation of the vehicle (104) without using any external device or sensors or modifications in the vehicle (104). The system (100) improves vehicle’s safety with high level of accuracy and less cost. The system (100) enables immobilisation of the vehicle (104) using the existing vehicle mechanisms and without any form of design alterations.
[0051] It has thus been seen that the remote vehicle immobilisation system (100), as described, in any case could undergo numerous modifications and variants, all of which are covered by the same innovative concept; moreover, all of the details can be replaced by technically equivalent elements. In practice, the components used, as well as the numbers, shapes, and sizes of the components can be whatever according to the technical requirements. The scope of protection of the invention is therefore defined by the attached claims.

Dated this 05th Day of February, 2025 Ishita Rustagi (IN-PA/4097)
Agent for Applicant
, C , Claims:CLAIMS
We Claim:
1. A remote vehicle immobilisation system (100) for a vehicle (104) comprising an electronic control unit (112) (ECU), characterized in that:
a computing unit (102) configured to initiate an immobilisation request for a vehicle (104);
a telematics server module (108) communicatively coupled to the computing unit (102), wherein the telematics server module (108) is configured to:
identify the vehicle (104) based at least on a vehicle information,
generate one or more command message based at least on the received immobilisation request, and
send the generated one or more command message to the identified vehicle (104);
a telematics module (110) integrated with the vehicle (104), wherein the telematics module (110) is configured to generate a CAN (Controller Area Network) message based at least on the received one or more command message,
wherein the telematics server module (108) facilitates the ECU (112) to:
compare the CAN message received from the telematics module (110) with respect to a default CAN message, and
activate an engine auxiliary shutdown switch of the vehicle (104) based at least on the CAN message to immobilise the vehicle (104).

2. The system (100) as claimed in claim 1, wherein the ECU (112) is configured to activate the engine auxiliary shutdown switch when the CAN message is different from the default CAN message, wherein the engine auxiliary shutdown switch is configured to control fuel supply and/or ignition of the vehicle (104) based at least on the CAN message.

3. The system (100) as claimed in claim 2, wherein the ECU (112) is configured to generate a user feedback (214) over the computing unit (102) upon immobilisation of the vehicle (104).

4. The system (100) as claimed in claim 31, wherein upon immobilising the vehicle (104), the ECU (112) is configured to re-change the CAN message to reset the vehicle (104).

5. The system (100) as claimed in claim 1, wherein upon activating the engine auxiliary shutdown switch, the ECU (112) is configured to crank the vehicle (104).

6. The system (100) as claimed in claim 1 further comprising a cloud database (106) communicatively coupled to the computing unit (102), wherein the cloud database (106) is configured to store the vehicle information.

7. The system (100) as claimed in claim 6, wherein the vehicle information corresponds to a vehicle registry (208).

8. The system (100) as claimed in claim 6 further comprising a communication module configured to communicatively couple the telematics server module (108) and the cloud database (106) to the computing unit (102) and the ECU (112), wherein the communication module (114) corresponds to the CAN (Controller Area Network) bus.

9. The system (100) as claimed in claim 1, wherein the computing unit (102) is installed with a user interface that is accessed by a user to generate the immobilisation request for the vehicle (104).

10. A method (400) for immobilising a vehicle remotely, wherein the method (400) comprising:
initiating, via a computing unit (102), an immobilisation request for a vehicle (104), at step (402);
identifying, via a telematics server module (108) communicatively coupled to the computing unit (102), the vehicle (104) based at least on the vehicle information, at step (404);
generating, via the telematics server module (108) integrated with the vehicle (104), one or more command message based at least on the received immobilisation request, at step (406);
sending, via the telematics server module (108), the generated one or more command message to the identified vehicle, at step (408);
generating, via a telematics module (110) integrated with the vehicle (104) a CAN (Controller Area Network) message based at least on the received one or more command message, at step (410);
comparing, via an electronic control unit (112) (ECU) facilitated by the telematics module (110), the CAN message received from the telematics module (110) with respect to a default CAN message, at step (412); and
activating, via the ECU (112), an engine auxiliary shutdown switch of the vehicle (104) based at least on the CAN message to immobilise the vehicle (104), at step (414).

Dated this 05th Day of February, 2025
Ishita Rustagi (IN-PA/4097)
Agent for Applicant