A vehicle and a method for controlling mobility of the vehicle

Abstract

Methods (1300) and systems for controlling the mobility of a vehicle (102) are disclosed. A vehicle controller (108) associated with the vehicle (102) receives a first command linked with a first unique code (318), via a first communication mode (112), to immobilize the vehicle (102) from a mobilized state. The vehicle controller (108) receives via a second communication mode (114), a second command linked with a second unique code, to mobilize the vehicle (102) from an immobilized state when the vehicle controller (108) is disconnected from the first communication mode (112). The vehicle controller (108) causes the vehicle (102) to be immobilized. Upon successful immobilization, the vehicle controller (108) stores the first unique code (318) at the vehicle controller (108), compares the second unique code with the first unique code (318), and causes the vehicle (102) to mobilize when the second unique code matches with the first unique code (318).

Description

DescriptionTitle of Invention: A VEHICLE AND A METHOD FOR CONTROLLING MOBILITY OF THE VEHICLECross-reference to related applications

[0001] This application claims priority from Indian provisional patent application 20231 10881 18, filed on 22 December 2023; 20231 1088256 filed on 22 December 2023 and 20241 1006543 filed on 31 January 2024 which is incorporated herein in its entirety by this reference thereto.Technical Field

[0002] The present disclosure relates to a vehicle and, more particularly to systems and methods for controlling mobility of the vehicle.Background

[0003] Present-day automobiles come with several systems and devices to enhance the safety and driving experience of a user. Such systems and devices include but are not limited to an Anti-lock Braking System (ABS), Electronic Brake Distribution (EBD), Airbags, active and semi-active suspensions, etc. In addition, to enhance the driving experience of the user, the vehicles are provided with remote mobilization and immobilization features. To perform remote immobilization of the vehicle, the user (e.g., owner or rider of the vehicle) from a remote place through a mobile application associated with the vehicle, can send an immobilization signal to a Telematic Control Unit (TCU) of the vehicle. Once the vehicle is immobilized through this feature, the vehicle cannot be turned ON using the conventional mechanism. The vehicle can only be turned ON once a mobilization signal is received in the same way through the mobile application. In vehicles using an Internal Combustion (IC) engine, the TCU prevents turning ON of the engine until authorization in the form of a mobilization signal is sent by the remote user. In electric vehicles, the TCU prevents turning ON of the batteries, until authorization for mobilization is received from the user through the remote server.

[0004] As may be understood, the remote server is used to send an immobilization / mobilization signal to the vehicle through an internet connectivity (e.g., a cellular network, a wireless broadband connectivity, etc.) upon receiving an immobilization / mobilization command from the mobile application of the user associated with the remote server. In case the internet connectivity is unavailable due to natural calamities, government restrictions, etc., it is difficult to immobilize / mobilize the vehicle. Consequently, if the vehicle is parked and immobilized at a place that does not physically or locally bar intruders from entering and accessing the vehicle, the vehicle becomes more susceptible to theft. Further, the use of Bluetooth, Short Message Service (SMS),and other communication interfaces and / or modes temporarily in place of the internet connectivity may not be secure enough to mobilize the vehicle.SUMMARY

[0005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0006] In order to solve the foregoing problem and to provide other advantages, one aspect of the present disclosure is to provide a method for controlling a mobility of a vehicle. The method performed by a vehicle controller associated with the vehicle includes determining connectivity of the vehicle controller to a first communication mode. The method further includes receiving, via the first communication mode, a first command to immobilize the vehicle from a mobilized state, when the vehicle controller is connected to the first communication mode. The first command is linked with a first unique code. Further, the method includes causing, the vehicle to be immobilized from the mobilized state in response to receiving the first command. Thereafter, the method includes upon successful immobilization of the vehicle, storing the first unique code at the vehicle controller. Furthermore, the method includes receiving, via a second communication mode, a second command to mobilize the vehicle from an immobilized state, when the first communication mode is unavailable. The second command is linked with a second unique code. The method further includes, in response to receiving the second command, comparing, the second unique code with the first unique code. The method includes causing the vehicle to mobilize when the second unique code matches with the first unique code.

[0007] In an aspect, the immobilized state of the vehicle disables at least one function of the vehicle, and the mobilized state of the vehicle enables the disabled function of the vehicle.

[0008] In an aspect, the first communication mode corresponds to an internet connectivity (e.g., a cellular network, a wireless broadband connectivity, etc.) using a Transmission Control Protocol (TCP), an Internet Protocol (IP), etc.

[0009] In an aspect, the second communication mode corresponds to a local connectivity including a Wireless Local Area Network (WLAN), Near-Field Communication (NFC), and a Bluetooth Low Energy (BLE) channel.

[0010] In an aspect, the second communication mode corresponds to a Short Message Service (SMS) connectivity via a SMS gateway.

[0011] In an aspect, the method further includes upon successful mobilization of the vehicle, deleting the first unique code. Further, the method includes transmitting, via the second communication mode, a first positive response message to a mobile device associated with the vehicle. Thereafter, the method includes transmitting, via the first communication mode, the first positive response message to a remote server once the first communication mode is available. The remote serverdeletes the first unique code. The first positive response message indicates a successful mobilization of the vehicle. In said aspect, the second communication mode corresponds to a local connectivity.

[0012] In an aspect, the method further includes upon successful mobilization of the vehicle, deleting the first unique code. Further, the method includes transmitting, via the second communication mode, a first positive response message to the remote server. In said aspect, in response to receiving the first positive response message, the remote server is configured to transmit, via the second communication mode, an indication to a mobile device associated with the vehicle (102) that mobilization is successful. In said aspect, the second communication mode corresponds to a SMS connectivity via a SMS gateway.

[0013] In an aspect, the method further includes causing the vehicle to continue to remain immobilized when the second unique code mismatches with the first unique code. Further, the method includes transmitting, via the second communication mode, a first negative response message to the mobile device. In said aspect, the second communication mode corresponds to the local connectivity. The method further includes transmitting, via the first communication mode, the first negative response message to the remote server when the first communication mode is available. The first negative response message is indicative of an unsuccessful mobilization of the vehicle.

[0014] In an aspect, the method further includes causing the vehicle to continue to remain immobilized when the second unique code mismatches with the first unique code. Further, the method includes transmitting, via the second communication mode, a first negative response message to a remote server. Herein, in response to receiving the first negative response message, the remote server is configured to transmit via the second communication mode, an indication to a mobile device associated with the vehicle (102) that mobilization is unsuccessful. Further, in said aspect, the second communication mode corresponds to a SMS connectivity via a SMS gateway.

[0015] In an aspect, the step of receiving the first command via the first communication mode includes receiving the first command from the remote server. In said aspect, the remote server is configured to receive, via the first communication mode, a third command from the mobile device when the mobile device receives an immobilization request from a user via a vehicle-controlling platform installed on the mobile device. The remote server is further configured to, in response to receiving the third command, generate and store the first unique code. Further, the remote server is configured to transmit, via the first communication mode, the first command along with the first unique code to the vehicle controller. Herein, the first command is derived from the third command.

[0016] In an aspect, the mobile device receives via the first communication mode, the first unique code to mobilize the vehicle from the immobilized state, when the user logs into the vehicle-controlling platform once the first communication mode is available.

[0017] In an aspect, the method further includes receiving, via the first communication mode, the second command to mobilize the vehicle from the immobilized state, when the first communicationmode is available. Further, the method includes, in response to receiving the second command via the first communication mode, causing the vehicle to mobilize. The method further includes upon successful mobilization of the vehicle, deleting the first unique code. The method further includes transmitting, via the first communication mode, a second positive response message to the remote server. The second positive response message indicates the successful mobilization of the vehicle. The remote server deletes the first unique code upon receiving the second positive response message from the vehicle controller.

[0018] In an aspect, the step of receiving the second command via the first communication mode includes receiving the second command from the remote server. In said aspect, the remote server is configured to receive a fourth command from the mobile device, when the mobilization request is initiated by the user via the vehicle-controlling platform installed on the mobile device when the first communication mode is available. The remote server is further configured to transmit the second command derived from the fourth command to the vehicle controller, to mobilize the vehicle from the immobilized state, when the first communication mode is available.

[0019] In an aspect, the step of receiving, by the vehicle controller via the second communication mode, the second command includes receiving the second command from the mobile device when the second communication mode corresponds to the local connectivity.

[0020] In an aspect, receiving, by the vehicle controller via the second communication mode, the second command includes receiving the second command upon successful verification of an identity of the user at the remote server when the second communication mode corresponds to the SMS connectivity via the SMS gateway.

[0021] In an aspect, for performing the step of determining that the identity of the user is successfully verified, the remote server is configured to receive, from the mobile device via the second communication mode, a fifth command when the mobilization request is initiated by the user via the vehicle-controlling platform installed on the mobile device. Herein, the fifth command is linked with a unique user identifier (ID). In response to receiving the fifth command, the remote server is configured to compare the unique user ID with a list of registered user IDs. Herein, the list of registered user IDs corresponds to users that are registered on a vehicle-controlling platform installed on the mobile device. Further, the remote server is configured to successfully verify the identity of the user when the unique user ID matches with one of the list of registered user IDs. Upon successful verification of the identity of the user, the remote server is configured to transmit to the vehicle controller via the second communication mode, a wakeup message. Thereafter, the remote server is configured to transmit, to the vehicle controller, the second command derived from the fifth command to mobilize the vehicle from the immobilized state.

[0022] In an aspect, the method further includes, upon unsuccessful verification of the identity of the user, causing the vehicle to continue to remain immobilized. Further, the method includes transmitting, via the second communication mode, a second negative response message to the remote server. Herein, the remote server transmits the second negative response message via thesecond communication mode to the mobile device. The second negative response message indicates to the user of the vehicle that the verification of the identity of the user is unsuccessful.

[0023] In an aspect, the method further includes receiving, via the second communication mode, the first command to immobilize the vehicle from the mobilized state, when the vehicle controller is disconnected from the first communication mode.

[0024] In an aspect, the step of receiving the first command via the second communication mode includes receiving the first command from a remote server when a mobile device associated with the vehicle (102) is connected to the first communication mode and the second communication mode corresponds to a SMS connectivity via a SMS gateway. Herein, the remote server is configured to receive, via the first communication mode, a sixth command from the mobile device when the mobile device receives an immobilization request from a user via a vehicle-controlling platform installed on the mobile device. In response to receiving the sixth command, the remote server is configured to generate and store the first unique code upon successful verification of an identity of the user at the remote server. Further, the remote server is configured to transmit, via the second communication mode, the first command along with the first unique code to the vehicle controller. Herein, the first command is derived from the sixth command.

[0025] In an aspect, the step of receiving the first command via the second communication mode includes receiving the first command from the remote server when the mobile device is disconnected from the first communication mode. In said aspect, the second communication mode corresponds to the SMS connectivity via the SMS gateway. Herein, the remote server is configured to receive, via the second communication mode, a sixth command from the mobile device when the mobile device receives the immobilization request from the user via the vehicle-controlling platform installed on the mobile device. In response to receiving the sixth command, the remote server is configured to generate and store the first unique code upon successful verification of an identity of the user at the remote server. Further, the remote server is configured to transmit, via the second communication mode, the first command along with the first unique code to the vehicle controller. Herein, the first command is derived from the sixth command.

[0026] In an aspect, the step of receiving the first command via the second communication mode includes receiving the first command from a mobile device associated with the vehicle (102) when the mobile device is disconnected from the first communication mode and the second communication mode corresponds to a local connectivity. In said aspect, the mobile device is configured to generate and store the first unique code in the mobile device in response to an immobilization request from a user via a vehicle-controlling platform installed on the mobile device. The mobile device is further configured to transmit the first command along with the first unique code to the vehicle controller via the second communication mode. Further, the mobile device is configured to transmit, via the first communication mode, the first unique code to the remote server once the mobile device is connected to the first communication mode.

[0027] In an aspect, the step of receiving the first command via the second communication mode includes receiving the first command from the mobile device when the mobile device is connected to the first communication mode. In said aspect, the second communication mode (1 14) corresponds to the local connectivity. Herein, the remote server is configured to receive, via the first communication mode, a sixth command from the mobile device when the mobile device receives the immobilization request from the user via the vehicle-controlling platform installed on the mobile device. In response to receiving the sixth command, the remote server is configured to generate and store the first unique code in the remote server. Further, the remote server is configured to transmit, via the first communication mode, the first command along with the first unique code to the mobile device. The first command is derived from the sixth command. The mobile device transmits the first command along with the first unique code to the vehicle controller via the second communication mode.

[0028] In an aspect, a vehicle includes a vehicle controller. The vehicle controller includes a communication interface, a memory including executable instructions, and a processor communicably coupled to the communication interface and the memory. The processor is configured to cause the vehicle controller to determine connectivity of the vehicle controller to a first communication mode. The processor causes the vehicle controller to receive, via the first communication mode, a first command to immobilize the vehicle from a mobilized state, when the vehicle controller is connected to the first communication mode. Herein, the first command is linked with a first unique code. Further, the process causes the vehicle controller to cause the vehicle to be immobilized from the mobilized state in response to receiving the first command. Upon successful immobilization of the vehicle, the processor causes the vehicle controller to store the first unique code in the memory. The processor causes the vehicle controller to receive a second command, by the communication interface via a second communication mode, to mobilize the vehicle from an immobilized state, when the first communication mode is unavailable. The second command is linked with a second unique code. In response to receiving the second command, the processor causes the vehicle controller to compare the second unique code with the first unique code. The processor causes the vehicle controller to cause the vehicle to mobilize when the second unique code matches with the first unique code.

[0029] In an aspect, the vehicle controller is further caused at least to receive, via the second communication mode, the first command to immobilize the vehicle from the mobilized state, when the vehicle controller is disconnected from the first communication mode.

[0030] Various embodiments of the present disclosure offer multiple advantages and technical effects. The present disclosure uses the second communication mode, for example, a local connectivity including one of a Wireless Local Area Network (WLAN), a Near-Field Communication (NFC), and a Bluetooth Low Energy (BLE) channel, in case the first communication mode (i.e., the internet connectivity) is not available for communication. The second communication can also include a SMS connectivity via a SMS gateway. The second communication mode along with the uniquecode facilitates secured mobilization of the already immobilized vehicle even when the internet connectivity is not available. The second communication mode also facilitates secured immobilization of the already mobilized vehicle in absence of the internet connectivity.

[0031] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.BRIEF DESCRIPTION OF THE FIGURES

[0032] The invention itself, together with further features and advantages, will become apparent from consideration of the following detailed description, taken in conjunction with the accompanying drawings. One or more embodiments of the present disclosure are now described, by way of example only wherein like reference numerals represent like elements and in which:

[0033] Figure 1 shows an example representation of an environment in which various embodiments of the present disclosure may be practiced;

[0034] Figure 2 illustrates a simplified block diagram of a vehicle, according to an embodiment of the present disclosure;

[0035] Figure 3 illustrates a simplified block diagram of a remote server, according to an embodiment of the present disclosure;

[0036] Figure 4A to Figure 4D depict an example representation of User Interfaces (Uls) used for immobilizing the vehicle using a vehicle-controlling platform installed on a mobile device of a user, in accordance with an embodiment of the disclosure;

[0037] Figure 4E and Figure 4F depict an example representation of Uls used for mobilizing the vehicle using the vehicle-controlling platform, in accordance with an embodiment of the disclosure;

[0038] Figure 5 illustrates a sequence flow diagram depicting a process of immobilizing a mobilized vehicle, according to an embodiment of the present disclosure;

[0039] Figure 6 illustrates a sequence flow diagram depicting a process of mobilizing an immobilized vehicle via a first communication mode, according to another embodiment of the present disclosure;

[0040] Figure 7 illustrates a sequence flow diagram depicting a process of mobilizing the immobilized vehicle via a second communication mode, according to an embodiment of the present disclosure;

[0041] Figure 8 illustrates a sequence flow diagram depicting a process of mobilizing the immobilized vehicle via the second communication mode, according to another embodiment of the present disclosure;

[0042] Figure 9 to Figure 12 illustrate sequence flow diagrams depicting a process of immobilizing the mobilized vehicle, according to some embodiments of the present disclosure; and

[0043] Figure 13 illustrates a flowchart representing a method for controlling a mobility of a vehicle, according to another embodiment of the present disclosure.

[0044] The drawings referred to in this description are not to be understood as being drawn to scale except if specifically noted, and such drawings are only exemplary in nature.DETAILED DESCRIPTION

[0045] While the invention is susceptible to various modifications and alternative forms, a specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however, that it is not intended to limit the invention to the particular forms disclosed, but on the contrary, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and the scope of the invention.

[0046] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises... a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus. For a better understanding of this invention, reference would now be made to the embodiment illustrated in the accompanying figures and description below. Further, in the following figures, the same reference numerals are used to identify the same components in various views. The “vehicle” of the present disclosure is not limited to two-wheeled vehicles and four-wheeled vehicles, hence applicable to vehicles of any number of wheels. Further, the vehicle is not limited to Internal Combustion (IC) vehicles, can also include Electrical Vehicles (EV) and hybrid vehicles, etc.

[0047] Figure 1 shows an example representation of an environment (100) in which various embodiments of the present disclosure may be practiced. The environment (100) has a vehicle (102), a mobile device (104), and a remote server (106). The mobile device (104) is associated with the vehicle (102), and the remote server (106). The vehicle (102) has a vehicle controller (108) configured to connect to one or more components of the vehicle (102). In an embodiment, the vehicle controller (108) can collect telemetry data, such as position, speed, engine data, connectivity quality, etc., from the one or more components. Further, the vehicle controller (108) may control the one or more components and one or more operations of the vehicle (102), over data and control busses. The mobile device (104) is associated with a user (e.g., a rider of the vehicle (102)) and has a vehicle-controlling platform (1 10) (e.g., a mobile application). The vehiclecontrolling platform (1 10) is installed in the mobile device (104) of the user and provides one or more options to control one or more functions of the vehicle (102) from the mobile device (104) remotely. In one embodiment, the user registers the vehicle (102) on the vehicle-controlling platform (1 10). Thus, it can be said that the mobile device (104) having the vehicle-controlling platform (1 10) installed, is associated with the vehicle (102). In one scenario, the remote server (106) is connectedto the vehicle (102) and the mobile device (104) via a first communication mode (1 12). The first communication mode (1 12) is not limited to an internet connectivity including a cellular network, a wireless broadband connectivity, etc., that remotely connects the vehicle (102) and the mobile device (104) via the remote server (106). For example, enabling an immobilization option of the vehicle (102) disables a function of the one or more functions of the vehicle (102). On the other hand, disabling the immobilization option of the vehicle (102) activates the disabled function of the vehicle (102). The one or more functions relate to the operation of the vehicle (102) such as, but not limited to, starting the vehicle (102) from a start button of the vehicle (102), starting the vehicle (102) from kick start, unlocking the handlebar (not shown in Figure 1 ) using a vehicle key, allowing the battery (not shown in Figure 1 ) to supply power, etc.

[0048] The mobile device (104) includes an electronic device, such as but not limited to, a smartphone, a tablet, a mobile phone, a laptop, a desktop computer, a personal digital assistant, a web-enabled wearable device, and the like. The user, through the vehicle-controlling platform (1 10) of the mobile device (104), inputs one or more options for controlling one or more systems or sub-systems of the vehicle (102). The one or more options may correspond to one or more operations of the vehicle (102) including but not limited to mobilization of the vehicle (102), immobilization of the vehicle (102), navigation of the vehicle (102), assistance in finding the vehicle (102) when lost, tracking the vehicle (102), opening the boot, sharing the location of the vehicle (102), technical support, locating the nearest dealer, connecting to relationship manager, geofencing, etc.

[0049] The user can enable an option, for example, immobilization of the vehicle (102) in the vehiclecontrolling platform (1 10) by selecting (i.e., clicking or tapping the desired option in one of User Interfaces (Uls) facilitated by the vehicle-controlling platform (1 10)). When the option of ‘immobilization of the vehicle (102)’ is enabled in the mobile device (104), a function in the vehicle (102) that immobilizes the vehicle (102) is triggered. For instance, the battery supply in the case of electric vehicles may be stopped. Upon initiation of immobilization, the remote server (106) generates and stores a first unique code. The first unique code is randomly generated by the remote server (106) at the time of immobilization of the vehicle (102). In one embodiment of the present disclosure, the first unique code is an alpha-numeric code of about four bytes long. The first unique code is stored in the vehicle (102), and the mobile device (104) by transmitting the first unique code to them via the first communication mode (1 12). Also, to trigger the function in the vehicle (102) that immobilizes the vehicle (102), an immobilization command (e.g., a first command) is transmitted, via the first communication mode (1 12), to the vehicle (102) indicating the immobilization of the vehicle (102).

[0050] In a non-limiting implementation, the user can disable a previously enabled option, for example, the immobilization of the vehicle (102) in the vehicle-controlling platform (1 10) by de-selecting the option of ‘immobilization of the vehicle (102)’ which was previously selected for enabling immobilization of the vehicle (102). This way mobilization of the vehicle (102) can be initiated. In response to this, the previously disabled function in the vehicle (102) may be enabled. For instance,the battery supply in the case of electric vehicles may be started. In another non-limiting implementation, the user can enable another option, for example, mobilization of the vehicle (102) in the vehicle-controlling platform (110) by selecting the option of ‘mobilization of the vehicle (102)’ displayed on one of the Uls facilitated by the vehicle-controlling platform (1 10) on the mobile device (104). This way, the previously selected option, for example, the option of ‘immobilization of the vehicle (102)’ may automatically get de-selected and the option of ‘mobilization of the vehicle (102)’ gets selected or enabled. Further, the mobilization of the vehicle (102) is initiated in a way similar to as explained above.

[0051] Upon selection of the one or more options on the vehicle-controlling platform (1 10), the one or more functions of the vehicle (102) are controlled upon communication of one or more commands from and / or between at least one of the mobile device (104) and the remote server (106) via a preferred communication mode. In one embodiment, the preferred communication mode can be one of the first communication mode (1 12) and a second communication mode (1 14). In an embodiment, the second communication mode (1 14) can include, but not limited to one of a Wireless Local Area Network (WLAN), Near-Field Communication (NFC), and a Bluetooth Low Energy (BLE) channel. In another embodiment, the second communication mode (1 14) can include, but not limited to a Short Message Service (SMS) connectivity via a SMS gateway.

[0052] It should be noted that, although the remote server (106) can always be connected to the first communication mode (1 12), the mobile device (104) and the vehicle controller (108) can be connected to either the first communication mode (1 12) or the second communication mode (1 14). For instance, the remote server (106) can remain online (due to connection to the internet connectivity), whereas the vehicle controller (108) and the mobile device (104) can be connected to the second communication mode (1 14) when disconnected from the internet connectivity. In one embodiment, the disconnection from the first communication mode (1 12) can be performed by the user of the vehicle (102). In another embodiment, the disconnection from the first communication mode (1 12) can be automatic due to the unavailability of the first communication mode (1 12).

[0053] Thus, in one scenario of the vehicle (102) being already immobilized, the mobilization of the vehicle (102) can be performed in two modes. More specifically, the vehicle (102) can be immobilized when the first communication mode (1 12) is available. In a first mode, when the first communication mode (1 12) is available, the remote server (106) can directly send a mobilization command (e.g., a second command) to the vehicle controller (108) to mobilize the vehicle (102). In a second mode, when the first communication mode (1 12) is unavailable, the mobile device (104) sends the second command to the vehicle controller (108) via the second communication mode (1 14) along with a second unique code. The mobile device (104) receives the first unique code from the remote server (106) using the first communication mode (1 12). In case the first communication mode (1 12) is unavailable or when the user has logged out of the vehicle-controlling platform (1 10), the user needs to find a place where the first communication mode (1 12) is available to receive the first unique code from the remote server (106). The mobilization of the vehicle (102) is performedwhen the first unique code is the same as that of the second unique code received from the mobile device (104) at the vehicle controller (108) via the second communication mode (1 14). Thus, even when the first communication mode (1 12) is unavailable, immobilization of an already mobilized vehicle (102) is securely performed using the second communication mode (1 14). In either of the first stage or the second stage, or in both stages, the one or more commands can further include, but not be limited to a third command, a fourth command, a fifth command, and so on. In an embodiment, said commands can indicate the remote server (106) to prepare for controlling the operation of the vehicle controller (108) in the different stages of operation of the mobile device (104) and the vehicle controller (108). In another embodiment, said commands can be generated at the mobile device (104) in response to receiving different requests (i.e., mobilization request or immobilization request) from the user. It is noted that the usage of said commands is explained later in the present disclosure.

[0054] In another scenario, the first communication mode (1 12) is partially available during the immobilization of the vehicle (102) that is initially in the mobilized state. In one embodiment, when the vehicle controller (108) is determined to be disconnected from the first communication mode (1 12), the immobilization of the vehicle (102) can be performed in four modes. In the first mode, when the mobile device (104) associated with the vehicle (102) is connected to the first communication mode (1 12), the mobile device (104) sends, via the first communication mode (1 12), a command (i.e., sixth command) to the remote server (106) upon receiving an immobilization request from the user. Thereafter, the remote server (106) generates and stores the first unique code, and transmits the same to the vehicle controller (108) via the second communication mode (1 14) (i.e., SMS connectivity via the SMS gateway) as the vehicle controller (108) is disconnected from the first communication mode (1 12). The first unique code is stored both in the vehicle controller (108) and the mobile device (104) and the same can be used by the vehicle controller (108) at the time of mobilization.

[0055] In the second mode, when the mobile device (104) is disconnected from the first communication mode (1 12), the mobile device (104) sends a command (i.e., sixth command) to the remote server (106) upon receiving an immobilization request from the user via the second communication mode (1 14) (i.e., SMS connectivity via the SMS gateway). Thereafter, the remote server (106) generates and stores the first unique code, and transmits the same to the vehicle controller (108) via the second communication mode (1 14) (e.g., SMS connectivity via the SMS gateway) as the vehicle controller (108) is disconnected from the first communication mode (1 12). The first unique code is stored both in the vehicle controller (108) and the mobile device (104) and the same can be used by the vehicle controller (108) at the time of mobilization.

[0056] In the third mode, when the mobile device (104) is not connected to the first communication mode (1 12), the mobile device (104) generates and stores the first unique code, and transmits the same to the vehicle controller (108) via the second communication mode (1 14) (e.g., BLE). The first unique code is stored both in the vehicle controller (108) and the mobile device (104) and the samecan be used by the vehicle controller (108) at the time of mobilization. Once the mobile device (104) is connected back to the first communication mode (1 12), the first unique code is transmitted to the remote server (106) via the first communication mode (1 12) and stored there for future use.

[0057] In the fourth mode, when the mobile device (104) is connected to the first communication mode (1 12), the mobile device (104) sends, via the first communication mode (1 12), a command (i.e., sixth command) to the remote server (106) upon receiving an immobilization request from the user. Thereafter, the remote server (106) generates and stores the first unique code, and transmits the same to the mobile device (104) via the first communication mode (1 12). The mobile device (104) then transmits the first unique code to the vehicle controller (108) via the second communication mode (1 14) as the vehicle controller (108) is disconnected from the first communication mode (1 12). The first unique code is stored both in the vehicle controller (108) and the mobile device (104) and the same can be used by the vehicle controller (108) at the time of mobilization. In one embodiment, the first unique code is randomly generated by the remote server (106) at the time of immobilization of the vehicle (102) upon receiving the sixth command from the mobile device (104). In some embodiments, the first unique code is randomly generated by the mobile device (104) at the time of immobilization of the vehicle (102), when the remote server (106) is unavailable for direct communication. The first unique code is stored in the vehicle (102) and the remote server (106). Further, to trigger the function in the vehicle (102) that immobilizes the vehicle (102), the immobilization command (e.g., the first command) is transmitted, to the vehicle (102) indicating the immobilization of the vehicle (102) either from the remote server (106) or from the mobile device (104). In case the first unique code is generated in the remote server (106), the first command is derived from the sixth command and then transmitted to the vehicle (102).

[0058] It should be noted that the environment (100) represents one of the systems used for controlling the mobility of the vehicle (102). The environment (100) is not limited to controlling the mobility of the vehicle (102), controlling other operations of the vehicle (e.g., navigation of the vehicle (102), assistance in finding the vehicle (102) when lost, tracking the vehicle (102), opening the boot, sharing the location of the vehicle (102), technical support, locating the nearest dealer, connecting to relationship manager, geofencing, etc.) can also be performed using the environment (100).

[0059] Figure 2 illustrates a simplified block diagram (200) of the vehicle (102), according to an embodiment of the present disclosure. The vehicle (102) has one or more units, systems, or subsystems for performing various operations of the vehicle (102). In one embodiment, the one or more units, systems, or sub-systems include but are not limited to a controller (e.g., the vehicle controller (108)), a navigation system (206), and other components not shown in Figure 2 and that operate together to control various operations of the vehicle (102). In Figure 2, the vehicle controller (108) is embodied to include a Telematic Control Unit (TCU) (202), and an Electronic Control Unit (ECU) (204). In some embodiments, the vehicle controller (108) includes the TCU (202), the ECU (204), and other components that may be needed to enable or disable a function of the vehicle (102)based on an option selected by the user on the mobile device (104) such as mobilization or immobilization of the vehicle (102).

[0060] The TCU (202) is an embedded system located on the vehicle (102) that wirelessly connects the vehicle (102) to the remote server (106) via Vehicle-to-everything (V2X) standards over the first communication mode (1 12). The TCU (202) collects telemetry data such as position, speed, engine data, connectivity quality, etc., from various units, systems, and sub-systems of the vehicle (102), over data and control busses (e.g., (Controller Area Network) CAN bus (208)). The ECU (204) is used to control various units, systems, and sub-systems of the vehicle (102) based on data (e.g., status, condition, etc.,) of various units, systems, and sub-systems of the vehicle (102) for controlling various operations of the vehicle (102). In one embodiment of the present disclosure, the ECU (204) can receive data from the TCU (202) via the CAN bus (208), and then the ECU (204) accordingly controls the various units, systems, and sub-systems of the vehicle (102) based on the data received from the TCU (202). In another embodiment, the TCU (202) can also collect data from the ECU (204) and accordingly communicate the same with remote devices (e.g., the mobile device (104) and the remote server (106)). The navigation system (206) is generally used to provide a navigation map and other navigation details to a vehicle user interface (not shown in Figure 2) of the vehicle (102).

[0061] In an embodiment, the vehicle controller (108) is associated with a communication interface (210), a memory (212) including executable instructions, and a processor (214) communicably coupled to the communication interface (210) and the memory (212) via a centralized communication bus (216). In another embodiment, the vehicle controller (108) includes the communication interface (210), the memory (212), and the processor (214). In yet another embodiment, the TCU (202) is associated with the communication interface (210), the memory (212), and the processor (214). Further, in yet another embodiment, the ECU (204) is associated with the communication interface (210), the memory (212), and the processor (214). In one embodiment, the communication interface (210), the memory (212), and the processor (214) are common to both the TCU (202) and the ECU (204). In some embodiments, the TCU (202) and the ECU (204) can have their respective communication interface (210), the memory (212), and the processor (214) and can be connected to the CAN bus (208).

[0062] In one embodiment of the present disclosure, the TCU (202) collects data including the first command and the second command received via one of the first communication mode (1 12), and the second communication mode (1 14). In an embodiment, the first command is associated with the first unique code. In another embodiment, the second command can be associated with the second unique code. In one embodiment of the present disclosure, the TCU (202) can perform the following processes: a) cause the vehicle controller (108) to at least determine the connectivity of the vehicle controller (108) to the first communication mode (1 12), b) receive, via the first communication mode (1 12), the first command to immobilize the vehicle (102), when the vehicle controller (108) is determined to be connected to the first communication mode (1 12), c) cause thevehicle (102) to be immobilized, d) upon successful immobilization, store the first unique code in the memory (212), e) receive, via the second communication mode (1 14), the second command to mobilize the vehicle (102) from the immobilized state when the first communication mode (1 12) is unavailable, f) in response to receiving the second command, compare the second unique code with the first unique code, g) cause the vehicle (102) to mobilize when the second unique code matches with the first unique code, h) upon successful mobilization of the vehicle (102), delete the first unique code, and i) transmit, via the second communication mode (1 14), a positive response message (e.g., first positive response message) indicating a successful mobilization of the vehicle (102), to the mobile device (104), j) transmit to the remote server (106), via the first communication mode (1 12), the first positive response message once the first communication mode (1 12) is available. Herein, the second communication mode (1 14) corresponds to the local connectivity (e.g., BLE). The remote server (106) deletes the first unique code in response to receiving the first positive response message. Thus, for one transaction, that is immobilization and its corresponding mobilization, a unique code (i.e., the first unique code) is generated during immobilization and the same is deleted upon completion of the mobilization.

[0063] In a scenario, where the second communication mode (1 14) is the SMS connectivity via the SMS gateway, the TCU (202) transmits, via the second communication mode (1 14), the first positive response message to the remote server (106). The remote server (106) transmits, via the second communication mode (1 14), an indication to the mobile device (104) that mobilization is successful.

[0064] In one embodiment, the TCU (202), upon receiving the second command, may internally instruct the ECU (204) to perform the operation of comparing the second unique code with the first unique code. The ECU (204) may also be configured to cause the vehicle (102) to mobilize when the second unique code matches with the first unique code, and upon matching, delete the first unique code from the memory (212).

[0065] In one embodiment of the present disclosure, the communication interface (210) is configured to facilitate sending of messages related to but not limited to a) successful or unsuccessful mobilization of the vehicle (102) via the second communication mode (1 14) to the mobile device (104), b) successful or unsuccessful mobilization of the vehicle (102) via the first communication mode (1 12) to the remote server (106), and c) successful or unsuccessful immobilization of the vehicle (102) via the first communication mode (1 12) to the remote server (106). In one embodiment of the present disclosure, the communication interface (210) is configured to facilitate receiving commands including, but not limited to a) the first command along with the first unique code via the first communication mode (1 12) from the remote server (106), b) the second command via the first communication mode (1 12) from the remote server (106), and c) the second command along with the second unique code via the second communication mode (1 14) from the mobile device (104). The memory (212) is configured to store the first unique code received from the remote server (106) via the first communication mode (1 12) and other information related to the state of the vehicle (102).

[0066] Figure 3 illustrates a simplified block diagram of an example remote server (300), according to an embodiment of the present disclosure. It is noted that the remote server (300) of Figure 3 is identical to the remote server (106) of Figure 1 . In some embodiments, the remote server (300) is embodied as a cloud-based and / or SaaS-based (software as a service) architecture. The remote server (300) is depicted to include a computer system (302), a communication interface (304), a User Interface (Ul) (306), a storage interface (308), and an Input / Output (I / O) module (310). The computer system (302) has a processing module (312), and a memory module (314). In some embodiments, the remote server (300) may include more or fewer components than those depicted herein. The various components of the remote server (300) may be implemented using hardware, software, firmware, or any combination thereof. Further, it is also noted that one or more components of the remote server (300) may be implemented in a single server or a plurality of servers, which are remotely placed from each other.

[0067] Further, the remote server (300) is communicably coupled with a database (316). The database (316) may be incorporated in the remote server (300) or maybe an individual entity connected to the remote server (300) or maybe the database stored in cloud storage. The database (316) is configured to store the first unique code (318) and status information (320) (also referred to as the current state (320)) of the vehicle (102). In various non-limiting examples, the database (316) may further include various instructions or firmware data essential for the operation of the remote server (300). The processing module (312) includes various modules and sub-modules such as a receiving module (322), a unique code generation module (324), an analysis module (326), a controlling module (328), and a transmitting module (330).

[0068] The database (316) may include multiple storage units such as hard drives and / or solid-state drives in a Redundant Array of Inexpensive Disks (RAID) configuration. In some embodiments, the database (316) may include a Storage Area Network (SAN) and / or a Network -Attached Storage (NAS) system. In one embodiment, the database (316) may correspond to a distributed storage system, wherein the individual database is configured to store custom information, such as routing policies, Autonomous System Number (ASN) pool, Internet Protocol (IP) pool, Content Delivery Network (CDN) registration data, etc.

[0069] The receiving module (322) is configured to but is not limited to: a) upon successful mobilization of the vehicle (102), receive from the vehicle controller (108) via the first communication mode (1 12), the first positive response message once the first communication mode (1 12) is available, b) receive, via the first communication mode (1 12), the third command from the mobile device (104) when the mobile device (104) receives the immobilization request from the user via the vehicle-controlling platform (1 10), and c) receive a fourth command from the mobile device (104) when the mobilization request is initiated by the user via the vehicle-controlling platform (1 10) when the first communication mode (1 12) is available.

[0070] The unique code generation module (324) is configured to generate and store the first unique code (318) when the third command indicating immobilization of the vehicle (102) is received fromthe vehicle-controlling platform (1 10). In one embodiment of the present disclosure, the analysis module (326) can perform an analysis of the command (e.g., the third command and the fourth command) received from the mobile device (104) and perform one or more operations, for example, generate the second command for immobilizing the vehicle (102). In one embodiment, the analysis of the third command may include decoding information encoded in the third command. Upon decoding the third command, the analysis module (326) determines a first set of operations to be performed within the remote server 300. In one embodiment, the first set of operations may include generating and storing the first unique code (318). Thus, the analysis module (326) instructs the unique code generation module (324) to generate and store the first unique code (318) in the database (316) once the receiving module (322) receives the third command. Further, in one embodiment, the first set of operations may further include generating or deriving the first command to be transmitted to the vehicle controller (108). Since the third command indicates the immobilization of the vehicle (102) in the mobilized state, the first command may be generated to instruct the vehicle controller (108) to cause the vehicle (102) to immobilize. Thus, the analysis module (326) instructs the controlling module (328) to generate the first command from the third command.

[0071] In another embodiment, the analysis of the fourth command may include decoding information encoded in the fourth command. Upon decoding the fourth command, the analysis module (326) determines a second set of operations to be performed within the remote server 300. Since the fourth command indicates the mobilization of the vehicle (102) in the immobilized state, the second set of operations may include generating or deriving the second command to be transmitted to the vehicle controller (108), the second command instructing the vehicle controller (108) to cause the vehicle (102) to mobilize. Thus, the analysis module (326) instructs the controlling module (328) to generate the second command from the fourth command.

[0072] The controlling module (328) controls one or more operations of the remote server (106) based on the analysis performed by the analysis module (326). The controlling module (328) controls operations performed by the receiving module (322), the unique code generation module (324), the analysis module (326), and the transmitting module (330) based on the analysis performed by the analysis module (326). In one embodiment, the controlling module (328) generates the first command and the second command based on the analysis of the third command and the fourth command, respectively. It should be noted that the first command and the third command indicate immobilizing the vehicle (102) from the mobilized state. Similarly, the second command and the fourth command indicate mobilizing the vehicle (102) from the immobilized state. In addition, each command may be associated with respective source and destination addresses (e.g., IP addresses of corresponding source and destination devices). The transmitting module (330) is configured to at least: a) transmit the first command with the first unique code (318) to the vehicle controller (108) via the first communication mode (1 12), at the time of immobilization of the vehicle (102), b) transmit the first unique code (318) to the mobile device (104), via the first communication mode (1 12), andc) transmit the second command for mobilizing the immobilized vehicle (102) to the vehicle controller (108), via the first communication mode (1 12).

[0073] In one embodiment, the processing module (312) may be embodied as a multi-core processor, a single-core processor, or a combination of one or more multi-core processors and one or more single-core processors. For example, the processing module (312) may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a Digital Signal Processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Microcontroller Unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. In one embodiment, the memory module (314) can store machine-executable instructions, referred to herein as platform instructions. Further, the processing module (312) can execute the platform instructions. In an embodiment, the processing module (312) may be configured to execute hard-coded functionality. In an embodiment, the processing module (312) is embodied as an executor of software instructions, wherein the instructions may specifically configure the processing module (312) to perform the algorithms and / or operations described herein when the instructions are executed.

[0074] The memory module (314) stores instructions / code configured to be used by the processing module (312), or more specifically by the various modules of the processing module (312). The memory module (314) may be embodied as one or more non-volatile memory devices, one or more volatile memory devices, and / or a combination of one or more volatile memory devices and nonvolatile memory devices. For example, the memory module (314) may be embodied as semiconductor memories, such as flash memory, mask ROM, PROM (programmable ROM), EPROM (erasable PROM), RAM (random access memory), and the like.

[0075] In an embodiment, the I / O module (310) may include mechanisms configured to receive inputs (via, e.g., a keyboard, a mouse, a joystick) from and provide outputs (via, e.g., a microphone, a speaker) to an operator of the remote server (300). The communication interface (304) is configured to facilitate communication between the remote server (300) and one or more remote entities over a communication network. For example, the communication interface (304) is capable of facilitating communication with the vehicle controller (108) of the vehicle (102) and the vehicle-controlling platform (1 10), with Internet Service Providers (ISPs), with edge servers associated with CDNs, with content ingestion servers, and the like. The various components of the remote server (300), such as the processing module (312), the memory module (314), the I / O module (310), and the communication interface (304) are configured to communicate with each other via or through a centralized circuit system (332). In one embodiment of the present disclosure, the vehicle controller (108) has one or more elements similar to the remote server (106).

[0076] Figure 4A depicts an example representation of a Ul (400) used for immobilizing the vehicle (102) using the vehicle-controlling platform (1 10) of the mobile device (104) of the user (218), in accordance with an embodiment of the present disclosure. The vehicle-controlling platform (1 10) isinstalled in the mobile device (104) of the user (218) and provides one or more options (402) to control the one or more functions of the vehicle (102) from the mobile device (104) remotely. The user (218) can enable or disable one or more options for remotely controlling one or more operations of the vehicle (102). As shown in Figure 4A, the user (218) can enable the immobilization option (404) on the Ul (400) to immobilize the mobilized vehicle.

[0077] Figure 4B depicts an example representation of a Ul (410) seeking confirmation from the user (218) for immobilizing the vehicle (102), in accordance with an embodiment of the present disclosure. Along with a navigation path (412) between the user (218) and the vehicle (102), an immobilization notification (414) with YES option (416) and NO option (418) is displayed on the Ul (410) of the vehicle-controlling platform (1 10) to get confirmation from the user (218) to immobilize the mobilize vehicle (102). The immobilization notification (414) informs the user (218) that immobilization of the vehicle (102) will refrain the vehicle (102) from starting. The immobilization notification (414) requests the user (218) to confirm the immobilization process by pressing the YES option (416) or discard the immobilization process by pressing the NO option (418).

[0078] Figure 4C depicts an example representation of a Ul (420) showing an immobilization process notification (422) indicating initialization of the immobilization process of the vehicle (102), in accordance with an embodiment of the present disclosure. In one embodiment of the present disclosure, as soon as the user (218) confirms the immobilization of the vehicle (102) by clicking the YES option (416) in the Ul (410), the immobilization process is performed as depicted in the sequence flow diagram (500) of Figure 5. Figure 4D depicts an example representation of a Ul (430) showing an immobilization notification (432) confirming the immobilization of the vehicle (102), in accordance with an embodiment of the present disclosure.

[0079] Figure 4E depicts an example representation of a Ul (440) showing a location map (442) of the user (218) and the vehicle (102) along with an immobilization option, in accordance with an embodiment of the present disclosure. Mobilization of the immobilized vehicle (102) can be achieved when the user (218) clicks on a mobilize option (444) in the Ul (440) facilitated by the vehicle-controlling platform (1 10). Clicking the mobilize option (444) represents the mobilization request received at the mobile device (104) from the user (218). Mobilization of the immobilized vehicle (102) via the first communication mode (1 12) is explained in the sequence flow diagram (500) of Figure 5, while via the second communication mode (1 14) is explained in the sequence flow diagram (600) of Figure 6. Figure 4F depicts an example representation of a Ul (450) showing a mobilization notification (452) confirming mobilization of the vehicle (102), in accordance with an embodiment of the present disclosure. The mobilization notification (452) represents either a positive responsive message (e.g., the first positive response message or the second positive response message) or a negative responsive message.

[0080] Figure 5 illustrates a sequence flow diagram (500) depicting a process of immobilizing the mobilized vehicle (102), according to an embodiment of the present disclosure. The sequence flow begins at step (502). At step (502), the immobilization request is input by the user (218) in thevehicle-controlling platform (1 10) of the mobile device (104), by enabling or disabling at least one option displayed on one of the Uls facilitated by the vehicle-controlling platform (1 10). At step (504), upon receiving the immobilization request from the user (218), the mobile device (104) transmits the third command to the remote server (106) via the first communication mode (1 12) to immobilize the mobilized vehicle (102). At step (506), in case the user (218) is logging in after being logged out before or if the user (218) is logging into the vehicle-controlling platform (1 10) for the first time, the remote server (106) checks whether the user (218) is the authorized user (218) or not. The authorized user (218) can proceed to the following steps of the process (500). The user (218) can be authorized using a unique user identity (ID) and associated password created with the vehiclecontrolling platform (1 10). For instance, the unique user ID can be a mobile number, an email address, a username, or the like.

[0081] At step (508), in response to receiving the third command, the remote server (106) generates the first unique code (318). It should be noted that the first unique code (318) is only generated during the immobilization process and the remote server (106) generates it to allow secured communication of the mobile device (104) with the vehicle controller (108) via the second communication mode (1 14) when the first communication mode (1 12) is unavailable. At step (510), the remote server (106) stores the first unique code (318) in the database (316) associated with the remote server (106). In some embodiments of the present disclosure, the remote server (106) can have one or more databases to store the first unique code (318) and also the current status information of the vehicle received from the vehicle controller (108). At step (512), upon generating the first unique code (318), the remote server (106) transmits, via the first communication mode (1 12), the first command along with the first unique code (318) to the vehicle controller (108). The first command is derived from the third command that is received from the mobile device (104). At step (514), the immobilization of the mobilized vehicle (102) is executed upon receiving the first command from the remote server (106).

[0082] At step (516), upon successful immobilization of the vehicle (102), the vehicle controller (108) transmits via the first communication mode (1 12), the third positive response message to the remote server (106). The third positive response message indicates successful immobilization of the vehicle (102). At step (518), upon receiving the third positive response message from the vehicle controller (108), the remote server (106) transmits, via the first communication mode (1 12), the current state of the vehicle (102) being immobilized along with the first unique code (318) to the mobile device (104). The current state of the vehicle (102) is displayed to the user (218) in the form of a notification (e.g., immobilization notification (432) of Figure 4D). Thus, during immobilization of the mobilized vehicle (102), the first unique code (318) is stored in the vehicle controller (108), the mobile device (104), and the remote server (106), and the same can be used for securely mobilizing the immobilized vehicle (102) via the second communication mode (1 14).

[0083] Figure 6 illustrates a sequence flow diagram (600) depicting a process of mobilizing the immobilized vehicle (102), via the first communication mode (1 12), according to anotherembodiment of the present disclosure. The sequence flow begins at step (602). At step (602), the mobilization request is initiated by the user (218) via the vehicle-controlling platform (1 10) installed on the mobile device (104). At step (604), upon receiving the mobilization request from the user (218), the mobile device (104) transmits a fourth command to the remote server (106) when the first communication mode (1 12) is available.

[0084] At step (606), the second command is transmitted by the remote server (106) to the vehicle controller (108), via the first communication mode (1 12). The first communication mode (1 12) is a secured mode of communication and if the first communication mode (1 12) is available, the remote server (106) can send the second command to the vehicle controller (108) of the vehicle (102) via the first communication mode (1 12). In such a scenario, the first unique code (318) is not necessary to validate the mobilization process. The validation of the first unique code (318) and the second unique code is necessary only when the second command is sent from the mobile device (104) via the second communication mode (1 14).

[0085] At step (608), the vehicle controller (108) receives, via the first communication mode (1 12), the second command to mobilize the vehicle (102) from the immobilized state. At step (610), the vehicle controller (108) upon successful mobilization of the vehicle (102), deletes the first unique code (318) at the remote server (106). At step (612), the vehicle controller (108) transmits via the first communication mode (1 12), the second positive response message to the remote server (106). At step (614), the remote server (106) deletes the first unique code (318) already stored in the remote server (106) during immobilization, upon receiving the second positive response message from the vehicle controller (108). The second positive response message indicates the successful mobilization of the vehicle (102). At step (616), the vehicle controller (108) transmits via the first communication mode (1 12), the current state of the vehicle (102) to the mobile device (104) via the first communication mode (1 12). The current state of the vehicle is displayed to the user (218) in the form of a notification (e.g., mobilization notification (452) of Figure 4F). It should be noted that the current state of the vehicle and the first unique code (318) for each transaction can be stored in the database (316) associated with the remote server (106). The remote server (106) can delete the first unique code (318) as soon as the vehicle (102) is mobilized.

[0086] Figure 7 illustrates a sequence flow diagram (700) depicting a process of mobilizing the immobilized vehicle (102), via the second communication mode (1 14) such as the local connectivity (e.g., BLE), according to another embodiment of the present disclosure. The sequence flow begins at step (702). At step (702), the mobile device (104) receives a mobilization request from the user (218), wherein the mobilization request is initiated by the user (218) via the vehicle-controlling platform (1 10) installed on the mobile device (104). At step (704), in order to control the vehicle (102), the mobile device (104) fetches the first unique code (318) via the first communication mode (1 12). To fetch the first unique code (318), the user (218) has to reach a place where the first communication mode (1 12) is available. Once the first unique code (318) is fetched in the mobile device (104), irrespective of the availability of the first communication mode (1 12), the mobile device(104) can send the second command to the vehicle controller (108) via the second communication mode (1 14).

[0087] It should be noted that to send the second command to the vehicle controller (108) via the second communication mode (1 14), the user (218) needs to be logged in to the vehicle-controlling platform (1 10). Once logged in, the user (218) can fetch the first unique code (318) from the remote server (106) via the first communication mode (1 12). Such a unique code (e.g., the second unique code) is sent along with the second command to the vehicle controller (108) to mobilize the immobilized vehicle (102). The user (218) will remain logged in and send the second command to the vehicle controller (108) even when the first communication mode (1 12) is unavailable. At step (706), the second command is transmitted by the mobile device (104) associated with the vehicle (102) to the vehicle controller (108). The second command is linked with the second unique code. The vehicle controller (108) receives, via the second communication mode (1 14), the second command to mobilize the vehicle (102) from the immobilized state, when the first communication mode (1 12) is unavailable.

[0088] At step (708), the vehicle controller (108) compares the second unique code received from the mobile device (104) with the first unique code (318) stored by the vehicle controller (108) at the time of the immobilization of the mobilized vehicle (102). At step (710), the vehicle controller (108) prevents the mobilization of the vehicle (102) when the second unique code mismatches with the first unique code (318). At step (712), the vehicle controller (108) sends via the first communication mode (1 12), the first negative response message to the remote server (106) when the second unique code mismatches with the first unique code (318). At step (714), the vehicle controller (108) also sends via the second communication mode (1 14), the first negative response message to the remote server (106) when the second unique code mismatches with the first unique code (318). In one embodiment of the present disclosure, the first negative response message is sent to the mobile device (104) via the first communication mode (1 12), when the first communication mode (1 12) is available.

[0089] At step (716), the vehicle controller (108) causes the vehicle (102) to be mobilized when the second unique code matches with the first unique code (318). At step (718), upon successful mobilization of the vehicle (102), the vehicle controller (108) deletes the first unique code (318). At step (720), the vehicle controller (108) transmits via the first communication mode (1 12), a first positive response message to the remote server (106) once the first communication mode (1 12) is available.

[0090] At step (722), the remote server (106) deletes the first unique code (318), upon receiving the first positive response message from the vehicle controller (108). The first positive response message indicates the successful mobilization of the vehicle (102). The first unique code (318) generated at the time of the immobilization is stored both at the vehicle controller (108) and the remote server (106). Thus, for one transaction, that is immobilization and its corresponding mobilization, the first unique code (318) is used for comparison with the second unique codereceived from the mobile device (104) via the second communication mode (1 14). Further, upon successful mobilization, the first unique code (318) is deleted in both the vehicle controller (108) and the remote server (106). The remote server (106) will generate a new first unique code again when a fresh immobilization request is initiated by the user (218) in the vehicle-controlling platform (1 10).

[0091] At step (724), the vehicle controller (108) transmits via the second communication mode (1 14), the current state of the vehicle (102) to the mobile device (104). The current state of the vehicle (102) indicates that the vehicle (102) is mobilized from the immobilized state. The mobile device (104) displays a notification (e.g., mobilization notification (452) of Figure 4F) on the mobile device (104) of the user (218). It should be noted that the sequence flow diagram (700) depicting the process of mobilizing the immobilized vehicle (102), via the second communication mode (1 14) is performed only when the second communication mode (1 14) is turned ON in the mobile device (104). If the second communication mode (1 14) is not turned ON, the vehicle-controlling platform (1 10) requests the user (218) to turn ON the second communication mode (1 14) to control the mobility of the vehicle (102) when the first communication mode (1 12) is unavailable.

[0092] Figure 8 illustrates a sequence flow diagram 800 depicting a process of mobilizing the immobilized vehicle (102) via the second communication mode (1 14) (e.g., the SMS connectivity via the SMS gateway, otherwise, also referred to as ‘SMS gateway’), according to another embodiment of the present disclosure. The sequence flow begins at step (802). At step (802), the mobile device (104) receives a mobilization request from the user (218), wherein the mobilization request is initiated by the user (218) via the vehicle-controlling platform (1 10) installed on the mobile device (104). At step (804), the remote server (106) receives, via the second communication mode (1 14), the fifth command linked with a unique user identifier (ID) when the remote server (106) is unavailable for direct communication. In response to receiving the fifth command, at step (806), the remote server (106) compares the unique user ID with a list of registered user IDs. The list of registered user IDs corresponds to users that are registered on a vehicle-controlling platform (1 10) installed on the mobile device (104). The remote server (106) successfully verifies the identity of the user (218) when the unique user ID matches with one of the list of registered user IDs.

[0093] At step (808), the remote server (106) transmits via the second communication mode (1 14), a second negative response message to the mobile device (104) upon unsuccessful verification of the identity of the user (218). This causes the vehicle (102) to continue to remain in the immobilized state. The second negative response message indicates to the user (218) of the vehicle (102) that the verification of the identity of the user (218) is unsuccessful. At step (810) upon successful verification of the identity of the user (218), the remote server (106) transmits to the vehicle controller (108) via the second communication mode (1 14), a wakeup message. At step (812), the remote server (106) via the second communication mode (1 14) sends the second command to the vehicle controller (108). The user (218) will remain logged in, and send the second command to the vehicle controller (108) even though the remote server (106) is unavailable for direct communication.The second command is linked with the second unique code. The vehicle controller (108) receives, via the second communication mode (1 14), the second command to mobilize the vehicle (102) from the immobilized state, when the remote server (106) is unavailable for direct communication.

[0094] At step (814), the vehicle controller (108) compares the second unique code received from the remote server (106) via the second communication mode (1 14) with the first unique code (318) stored by the vehicle controller (108) at the time of the immobilization of the mobilized vehicle (102). At step (816), the vehicle controller (108) causes the vehicle (102) to prevent mobilization when the second unique code mismatches with the first unique code (318). At step (818), the vehicle controller (108) sends, via the second communication mode (1 14), the first negative response message to the remote server (106) when the second unique code mismatches with the first unique code (318). The vehicle controller (108) also sends, via the second communication mode (1 14), the first negative response message to the mobile device (104) when the second unique code mismatches with the first unique code (318). In other words, at step (820), in response to receiving the first negative response message from the vehicle controller (108), the remote server (106) forwards it to the mobile device (104) via the second communication mode (1 14).

[0095] At step (822), the vehicle controller (108) causes the vehicle (102) to be mobilized from the immobilized state when the second unique code matches with the first unique code (318). At step (824), upon successful mobilization of the vehicle (102), the vehicle controller (108) deletes the first unique code (318). At step (826), the vehicle controller (108) transmits, via the second communication mode (1 14), a second positive response message to the remote server (106). At step (828), the remote server (106) transmits the second positive response message to the mobile device (104) via the second communication mode (1 14). At step (830), the remote server (106) deletes the first unique code (318), upon receiving the second positive response message from the vehicle controller (108). The second positive response message indicates the successful mobilization of the vehicle (102). The first unique code (318) generated at the time of the immobilization is stored both at the vehicle controller (108) and the remote server (106). Thus, for one transaction, that is immobilization and its corresponding mobilization, the first unique code (318) is used for comparison with the second unique code received from the mobile device (104) via the second communication mode (1 14). Further, upon successful mobilization, the first unique code (318) is deleted in both the vehicle controller (108) and the remote server (106). The remote server (106) will generate a new first unique code again when a fresh immobilization request is initiated by the user (218) in the vehicle-controlling platform (1 10).

[0096] In some embodiments of the disclosure, the vehicle controller (108) transmits, via the second communication mode (1 14), the current state of the vehicle (102) to the mobile device (104). The current state of the vehicle (102) indicates that the vehicle (102) is mobilized from the immobilized state. The mobile device (104) displays a notification (e.g., mobilization notification (452) of Figure 4F) on the mobile device (104) of the user (218). It should be noted that the sequence flow diagram (800) depicting the process of mobilizing the immobilized vehicle (102), via the secondcommunication mode (1 14) is performed only when the Subscriber Identity Module (SIM) is active in the mobile device (104). In this instance, the unique user ID can be a mobile number.

[0097] Figure 9 illustrates a sequence flow diagram (900) depicting a process of immobilizing the mobilized vehicle (102), according to some embodiments of the present disclosure. The sequence flow diagram (900) shows the immobilization of the vehicle (102) when the mobile device (104) is connected to the remote server (106) via the first communication mode (1 12), while the vehicle controller (108) is disconnected from the first communication mode (1 12). The sequence flow begins at step (902). At step (902), the immobilization request is input by the user (218) in the vehicle-controlling platform (1 10) of the mobile device (104). At step (904), upon receiving the immobilization request from the user (218), the mobile device (104) transmits the sixth command to the remote server (106) via the first communication mode (1 12) to immobilize the mobilized vehicle (102). At step (906), in case the user (218) is logging in after being logged out before or if the user (218) is logging into the vehicle-controlling platform (1 10) for the first time, the remote server (106) checks whether the user (218) is the authorized user or not. At step (908), in response to receiving the sixth command, the remote server (106) generates the first unique code (318). At step (910), the remote server (106) stores the first unique code (318) in a database associated with the remote server (106). In some embodiments of the present disclosure, the remote server (106) can have one or more databases to store the first unique code (318) and also the current status information of the vehicle (102) received from the vehicle controller (108). At step (912), upon generating the first unique code (318), the remote server (106) transmits, via the second communication mode (1 14) (e.g., SMS connectivity via the SMS gateway), the first command along with the first unique code (318) to the vehicle controller (108). At step (914), the immobilization of the mobilized vehicle (102) is executed upon receiving the first command from the remote server (106). At step (916), upon successful immobilization of the vehicle (102), the vehicle controller (108) transmits via the second communication mode (1 14) (e.g., SMS connectivity via the SMS gateway), the third positive response message to the remote server (106). At step (918), upon receiving the third positive response message from the vehicle controller (108), the remote server (106) transmits, via the first communication mode (1 12), the current state of the vehicle (102) being immobilized along with the first unique code (318) to the mobile device (104).

[0098] Figure 10 illustrates a sequence flow diagram (1000) depicting a process of immobilizing the mobilized vehicle (102), according to some embodiments of the present disclosure. The sequence flow diagram (1000) shows the immobilization of the vehicle (100) when the mobile device (104) and the vehicle controller (108) are disconnected from the first communication mode (1 12). The sequence flow begins at step (1002). At step (1002), the immobilization request is input by the user (218) in the vehicle-controlling platform (1 10) of the mobile device (104). At step (1004), upon receiving the immobilization request from the user (218), the mobile device (104) transmits the sixth command to the remote server (106) via the second communication mode (1 14) (e.g., SMS connectivity via the SMS gateway) to immobilize the mobilized vehicle (102). Steps (1006) to (1016) of Figure 10 are similar to steps (906) to (916) of Figure 9, respectively, therefore an explanationfor the same is not repeated herein for the sake of brevity. At step (1018), upon receiving the third positive response message from the vehicle controller (108), the remote server (106) transmits, via the second communication mode (1 14) (e.g., SMS connectivity via the SMS gateway), the current state of the vehicle (102) being immobilized along with the first unique code (318) to the mobile device (104). Thus, during immobilization of the mobilized vehicle (102), the first unique code (318) is stored in the vehicle controller (108), the mobile device (104), and the remote server (106), and the same can be used for securely mobilizing the immobilized vehicle (102) via the second communication mode (1 14) (e.g., SMS connectivity via the SMS gateway).

[0099] Figure 1 1 illustrates a sequence flow diagram (1 100) depicting a process of immobilizing the mobilized vehicle (102), according to some embodiments of the present disclosure. The sequence flow diagram (1 100) shows the immobilization of the vehicle (100) when the mobile device (104) and the vehicle controller (108) are disconnected from the first communication mode (1 12). The sequence flow begins at step (1 102). At step (1 102), the immobilization request is input by the user (218) in the vehicle-controlling platform (1 10) of the mobile device (104). At step (1 104), in response to receiving the immobilization request, the mobile device (104) generates the first unique code (318). At step (1 106), the mobile device (104) can have one or more internal storage units (not shown in Figures) to store the first unique code (318). At step (1 108), upon generating the first unique code (318), the mobile device (104) transmits, via the second communication mode (1 14) (e.g., BLE), the first command along with the first unique code (318) to the vehicle controller (108). At step (1 1 10), the immobilization of the mobilized vehicle (102) is executed upon receiving the first command from the mobile device (104). At step (1 1 12), upon successful immobilization of the vehicle (102), the vehicle controller (108) transmits via the second communication mode (1 14) (e.g., BLE), the third positive response message to the mobile device (104). The third positive response message indicates successful immobilization of the vehicle (102). At step (1 1 14), upon receiving the third positive response message from the vehicle controller (108), the mobile device (104) transmits, via the first communication mode (1 12), the current state of the vehicle (102) being immobilized along with the first unique code (318) to the remote server (106) once the mobile device (104) is connected to the first communication mode (1 12).

[0100] At step (1 1 16), the remote server (106) stores the first unique code (318) in the database associated with the remote server (106). In some embodiments of the present disclosure, the remote server (106) can have one or more databases to store the first unique code (318) and also the current status information of the vehicle received from the mobile device (104).

[0101] Figure 12 illustrates a sequence flow diagram (1200) depicting a process of immobilizing the mobilized vehicle (102), according to some embodiments of the present disclosure. The sequence flow diagram (1200) shows the immobilization of the vehicle (102) when the mobile device (104) is connected to the remote server (106) via the first communication mode (1 12), and the vehicle controller (108) is disconnected from the first communication mode (1 12). The sequence flow begins at step (1202). Steps (1202) to (1210) of Figure 12 are similar to steps (902) to (910) ofFigure 9, respectively, therefore an explanation for the same is not repeated herein for the sake of brevity. At step (1212), upon storing the first unique code (318), the remote server (106) transmits, via the first communication mode (1 12), the first unique code (318) to the mobile device (104). Steps (1214) to (1220) of Figure 12 are similar to steps (1 106) to (1 1 12) of Figure 1 1 , respectively, therefore an explanation for the same is not repeated herein for the sake of brevity. At step (1222), upon receiving the third positive response message from the vehicle controller (108), the mobile device (104) transmits, via the first communication mode (1 12), the current state of the vehicle (102) being immobilized along with the first unique code (318) to the remote server (106).

[0102] Figure 13 illustrates a flowchart representing a method (1300) for controlling the mobility of a vehicle (e.g., the vehicle (102)), in accordance with an embodiment of the present disclosure. The sequence flow begins at step (1302). At step (1302), the method (1300) includes determining, by a vehicle controller (e.g., the vehicle controller (108)) associated with the vehicle (102), connectivity of the vehicle controller (108) to a first communication mode (e.g., the first communication mode (1 12)).

[0103] At step 1304, the method (1300) includes receiving, by the vehicle controller (108) via the first communication mode (1 12), a first command to immobilize the vehicle (102) from a mobilized state, when the vehicle controller (108) is connected to the first communication mode (1 12). Herein, the first command is linked with a first unique code (e.g., the first unique code (318)). At step 1306, the method (1300) includes in response to receiving the first command, causing, by the vehicle controller (108), the vehicle (102) to be immobilized from the mobilized state.

[0104] At step 1308, the method (1300) includes upon successful immobilization of the vehicle (102), storing, by the vehicle controller (108), the first unique code (318) at the vehicle controller (108). At step 1310, the method (1300) includes receiving, by the vehicle controller (108) via a second communication mode (e.g., the second communication mode (1 14)), a second command to mobilize the vehicle (102) from an immobilized state, when the first communication mode (1 12) is unavailable. Herein, the second command is linked with a second unique code. At step 1312, the method (1300) includes in response to receiving the second command, comparing, by the vehicle controller (108), the second unique code with the first unique code (318). At step 1314, the method (1300) includes causing (812), by the vehicle controller (108), the vehicle (102) to mobilize when the second unique code matches with the first unique code (318).

[0105] It should be noted that the sequence of operations in each of the sequence flow diagrams (500, 600, 700, 800, 900, 1000, 1200, and 1300) may not be necessarily executed in the same order as they are presented. Further, one or more operations may be grouped and performed in the form of a single step, or one operation may have several sub-steps that may be performed in parallel or in a sequential manner. It is to be noted that to explain each of the sequence flow diagrams (500, 600, 700, 800, 900, 1000, 1200, and 1300), references may be made to elements described in Figure 1 to Figure 3. Various steps of the sequence flow have already been explained earlier in the description, therefore an explanation for the same is not repeated herein for the sake of brevity.

[0106] While few embodiments of the present disclosure have been described above, it is to be understood that the invention is not limited to the above embodiments and modifications may be appropriately made thereto within the scope of the invention. While considerable emphasis has been placed herein on the features of this invention, it will be appreciated that various modifications can be made and that many changes can be made in the preferred embodiments without departing from the principles of the invention. These and other modifications in the nature of the invention or the preferred embodiments will be apparent to those skilled in the art from the invention herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the invention and not as a limitation, i

Claims

Claims

1. A method (1300) for controlling a mobility of a vehicle (102), the method(1300) comprising: determining (1302), by a vehicle controller (108) associated with the vehicle (102), connectivity of the vehicle controller (108) to a first communication mode (1 12); receiving (1304), by the vehicle controller (108) via the first communication mode (112), a first command to immobilize the vehicle (102) from a mobilized state, when the vehicle controller (108) is connected to the first communication mode (1 12), wherein the first command is linked with a first unique code (318); in response to receiving the first command, causing (1306), by the vehicle controller (108), the vehicle (102) to be immobilized from the mobilized state; upon successful immobilization of the vehicle (102), storing (1308), by the vehicle controller (108), the first unique code (318) at the vehicle controller (108); receiving (1310), by the vehicle controller (108) via a second communication mode (1 14), a second command to mobilize the vehicle (102) from an immobilized state, when the first communication mode (1 12) is unavailable, wherein the second command is linked with a second unique code; in response to receiving the second command, comparing (1312), by the vehicle controller (108), the second unique code with the first unique code (318); and causing (1314), by the vehicle controller (108), the vehicle (102) to mobilize when the second unique code matches with the first unique code (318).

2. The method (1300) as claimed in claim 1 , wherein the immobilized state of the vehicle (102) disables at least one function of the vehicle (102), and the mobilized state of the vehicle (102) enables the disabled function of the vehicle (102).

3. The method (1300) as claimed in claim 1 , wherein the first communication mode (1 12) corresponds to an internet connectivity.

4. The method (1300) as claimed in claim 1 , wherein the second communication mode (1 14) corresponds to a local connectivity comprising one of a Wireless Local Area Network (WLAN), Near-Field Communication (NFC), and a Bluetooth Low Energy (BLE) channel.

5. The method (1300) as claimed in claim 1 , wherein the second communication mode (1 14) corresponds to a Short Message Service (SMS) connectivity via a SMS gateway.

6. The method (1300) as claimed in claim 1 , further comprising: upon successful mobilization of the vehicle (102), deleting, by the vehicle controller (108), the first unique code (318); transmitting, by the vehicle controller (108) via the second communication mode (1 14), a first positive response message to a mobile device (104) associated with the vehicle (102); and transmitting, by the vehicle controller (108) via the first communication mode (1 12), the first positive response message to a remote server (106) once the first communication mode (1 12) is available, wherein the remote server (106) deletes the first unique code (318), wherein the first positive response message is indicative of a successful mobilization of the vehicle (102), wherein the second communication mode (114) corresponds to a local connectivity.

7. The method (1300) as claimed in claim 1 , further comprising: upon successful mobilization of the vehicle (102), deleting, by the vehicle controller (108), the first unique code (318); and transmitting, by the vehicle controller (108) via the second communication mode (114), a first positive response message to a remote server (106), wherein in response to receiving the first positive response message, the remote server (106) is configured to transmit, via the second communication mode (1 14), an indication to a mobile device (104) associated with the vehicle (102) that mobilization is successful, wherein the second communication mode (1 14) corresponds to a SMS connectivity via a SMS gateway.

8. The method (1300) as claimed in claim 1 , further comprising: causing, by the vehicle controller (108), the vehicle (102) to continue to remain immobilized when the second unique code mismatches with the first unique code (318);transmitting, by the vehicle controller (108) via the second communication mode (1 14), a first negative response message to a mobile device (104) associated with the vehicle (102), wherein the second communication mode (1 14) corresponds to a local connectivity; and transmitting, by the vehicle controller (108) via the first communication mode (1 12), the first negative response message to a remote server (106) when the first communication mode (1 12) is available, wherein the first negative response message is indicative of an unsuccessful mobilization of the vehicle (102).

9. The method (1300) as claimed in claim 1 , further comprising: causing, by the vehicle controller (108), the vehicle (102) to continue to remain immobilized when the second unique code mismatches with the first unique code (318); and transmitting, by the vehicle controller (108) via the second communication mode (114), a first negative response message to a remote server (106), wherein in response to receiving the first negative response message, the remote server (106) is configured to transmit via the second communication mode (1 14), an indication to a mobile device (104) associated with the vehicle (102) that mobilization is unsuccessful, wherein the second communication mode (1 14) corresponds to a SMS connectivity via a SMS gateway.

10. The method (1300) as claimed in claim 1 , wherein receiving the first command via the first communication mode (1 12) comprises receiving the first command from a remote server (106), wherein the remote server (106) is configured to: receive, via the first communication mode (112), a third command from a mobile device (104) associated with the vehicle (102) when the mobile device (104) receives an immobilization request from a user (218) via a vehiclecontrolling platform (1 10) installed on the mobile device (104); in response to receiving the third command, generate and store the first unique code (318); andtransmit, via the first communication mode (1 12), the first command along with the first unique code (318) to the vehicle controller (108), wherein the first command is derived from the third command.

11. The method (1300) as claimed in claim 10, wherein the mobile device (104) receives via the first communication mode (1 12), the first unique code (318) to mobilize the vehicle (102) from the immobilized state, when the user (218) logs into the vehicle-controlling platform (110) once the first communication mode (1 12) is available.

12. The method (1300) as claimed in claim 1 , further comprising: receiving, by the vehicle controller (108) via the first communication mode (112), the second command to mobilize the vehicle (102) from the immobilized state, when the first communication mode (1 12) is available; in response to receiving the second command via the first communication mode (1 12), causing, by the vehicle controller (108), the vehicle (102) to mobilize; upon successful mobilization of the vehicle (102), deleting, by the vehicle controller (108), the first unique code (318); and transmitting, by the vehicle controller (108) via the first communication mode (1 12), a second positive response message to a remote server (106), wherein the second positive response message is indicative of a successful mobilization of the vehicle (102), wherein the remote server (106) deletes the first unique code (318) upon receiving the second positive response message from the vehicle controller (108).

13. The method (1300) as claimed in claim 12, wherein receiving the second command via the first communication mode (112) comprises receiving the second command from the remote server (106), wherein the remote server (106) is configured to: receive a fourth command from a mobile device (104) when a mobilization request is initiated by a user (218) via a vehicle-controlling platform (1 10) installed on the mobile device (104), when the first communication mode (1 12) is available; andtransmit the second command derived from the fourth command to the vehicle controller (108), to mobilize the vehicle (102) from the immobilized state, when the first communication mode (112) is available.

14. The method (1300) as claimed in claim 1 , wherein receiving, by the vehicle controller (108) via the second communication mode (1 14), the second command comprises receiving the second command from a mobile device (104) associated with the vehicle (102) when the second communication mode (1 14) corresponds to a local connectivity.

15. The method (1300) as claimed in claim 1 , wherein receiving, by the vehicle controller (108) via the second communication mode (1 14), the second command comprises receiving the second command upon successful verification of an identity of a user (218) at a remote server (106) when the second communication mode (1 14) corresponds to a SMS connectivity via a SMS gateway.

16. The method (1300) as claimed in claim 15, wherein for determining that the identity of the user (218) is successfully verified, the remote server (106) is configured to: receive, from a mobile device (104) associated with the vehicle (102) via the second communication mode (1 14), a fifth command when a mobilization request is initiated by a user (218) via a vehicle-controlling platform (110) installed on the mobile device (104), wherein the fifth command is linked with a unique user identifier (ID); in response to receiving the fifth command, compare the unique user ID with a list of registered user IDs, wherein the list of registered user IDs corresponds to users that are registered on a vehicle-controlling platform (1 10) installed on the mobile device (104); successfully verify the identity of the user (218) when the unique user ID matches with one of the list of registered user IDs; upon successful verification of the identity of the user (218), transmit to the vehicle controller (108) via the second communication mode (1 14), a wakeup message; andtransmit, to the vehicle controller (108), the second command derived from the fifth command to mobilize the vehicle (102) from the immobilized state.

17. The method (1300) as claimed in claim 15, further comprising: upon unsuccessful verification of the identity of the user (218), causing, by the vehicle controller (108), the vehicle (102) to continue to remain immobilized; and transmitting, by the vehicle controller (108) via the second communication mode (1 14), a second negative response message to the remote server (106), wherein the remote server (106) transmit the second negative response message via the second communication mode (1 14) to the mobile device (104), wherein the second negative response message indicates to the user (218) of the vehicle (102) that the verification of the identity of the user (218) is unsuccessful.

18. The method (1300) as claimed in claim 1 , further comprising: receiving, by the vehicle controller (108) via the second communication mode (114), the first command to immobilize the vehicle (102) from the mobilized state, when the vehicle controller (108) is disconnected from the first communication mode (1 12).

19. The method (1300) as claimed in claim 18, wherein receiving the first command via the second communication mode (1 14) comprises receiving the first command from a remote server (106) when a mobile device (104) associated with the vehicle (102) is connected to the first communication mode (1 12) and the second communication mode (114) corresponds to a SMS connectivity via a SMS gateway, wherein the remote server (106) is configured to: receive, via the first communication mode (1 12), a sixth command from the mobile device (104) when the mobile device (104) receives an immobilization request from a user (218) via a vehicle-controlling platform (1 10) installed on the mobile device (104);in response to receiving the sixth command, generate and store the first unique code (318) upon successful verification of an identity of the user (218) at the remote server (106); and transmit, via the second communication mode (1 14), the first command along with the first unique code (318) to the vehicle controller (108), wherein the first command is derived from the sixth command.

20. The method (1300) as claimed in claim 19, wherein receiving the first command via the second communication mode (1 14) comprises receiving the first command from the remote server (106) when the mobile device (104) is disconnected from the first communication mode (112), wherein the remote server (106) is configured to: receive, via the second communication mode (1 14), a sixth command from the mobile device (104) when the mobile device (104) receives the immobilization request from the user (218) via the vehicle-controlling platform (1 10) installed on the mobile device (104); in response to receiving the sixth command, generate and store the first unique code (318) upon successful verification of an identity of the user (218) at the remote server (106); and transmit, via the second communication mode (114), the first command along with the first unique code (318) to the vehicle controller (108), wherein the first command is derived from the sixth command.

21. The method (1300) as claimed in claim 18, wherein receiving the first command via the second communication mode (1 14) comprises receiving the first command from a mobile device (104) associated with the vehicle (102) when the mobile device (104) is disconnected from the first communication mode (1 12) and the second communication mode (1 14) corresponds to a local connectivity, wherein the mobile device (104) is configured to: generate and store the first unique code (318) in the mobile device (104) in response to an immobilization request from a user (218) via a vehiclecontrolling platform (110) installed on the mobile device (104);transmit the first command along with the first unique code (318) to the vehicle controller (108) via the second communication mode (1 14); and transmit, via the first communication mode (1 12), the first unique code (318) to a remote server (106) once the mobile device (104) is connected to the first communication mode (112).

22. The method (1300) as claimed in claim 21 , wherein receiving the first command via the second communication mode (1 14) comprises receiving the first command from the mobile device (104) when the mobile device (104) is connected to the first communication mode (1 12), wherein the remote server (106) is configured to: receive, via the first communication mode (1 12), a sixth command from the mobile device (104) when the mobile device (104) receives the immobilization request from the user (218) via the vehicle-controlling platform (1 10) installed on the mobile device (104); in response to receiving the sixth command, generate and store the first unique code (318) in the remote server (106); and transmit, via the first communication mode (1 12), the first command along with the first unique code (318) to the mobile device (104), wherein the first command is derived from the sixth command, wherein the mobile device (104) transmits the first command along with the first unique code (318) to the vehicle controller (108) via the second communication mode (1 14).

23. A vehicle (102), comprising: a vehicle controller (108), comprising: a communication interface (210); a memory (212) comprising executable instructions; and a processor (214) communicably coupled to the communication interface (210) and the memory (212), the processor (214) configured to cause the vehicle controller (108) to at least: determine connectivity of the vehicle controller (108) to a first communication mode (1 12);receive, via the first communication mode (1 12), a first command to immobilize the vehicle (102) from a mobilized state, when the vehicle controller (108) is connected to the first communication mode (1 12), wherein the first command is linked with a first unique code (318); cause, the vehicle (102) to be immobilized from the mobilized state in response to receiving the first command; upon successful immobilization of the vehicle (102), store the first unique code (318) in the memory (212); receive, via a second communication mode (1 14), a second command by the communication interface (210) to mobilize the vehicle (102) from an immobilized state, when the first communication mode (1 12) is unavailable, wherein the second command is linked with a second unique code; in response to receiving the second command, compare the second unique code with the first unique code (318); and cause the vehicle (102) to mobilize when the second unique code matches with the first unique code (318).

24. The vehicle (102) as claimed in claim 23, wherein the vehicle controller (102) is further caused at least to receive, via the second communication mode (1 14), the first command to immobilize the vehicle (102) from the mobilized state, when the vehicle controller (108) is disconnected from the first communication mode (1 12).

Images