WO2025210644A1

WO2025210644A1 - Method and system for facilitating remote operations

Info

Publication number: WO2025210644A1
Application number: PCT/IN2024/051372
Authority: WO
Inventors: Mahesh Mohandasan; Gangiredla Naveen CHAKRI
Original assignee: TVS Motor Co Ltd
Current assignee: TVS Motor Co Ltd
Priority date: 2024-03-30
Filing date: 2024-07-24
Publication date: 2025-10-09
Anticipated expiration: 2026-09-30
Also published as: CN121263753A

Abstract

Disclosed is a method (200) for facilitating remote operations. The method (200) comprises detecting, by a processor, a connection between a first device (102) and a second device (104). The method (200) comprises determining, by the processor, a ride status of the first device (102). The method (200) 5 comprises enabling, by the processor, one or more remote operations from a plurality of remote operations associated with the first device (102) on the second device (104) based on the detected connectivity and the determined ride status. Herein, at least one of the one or more remote operations is executed on the first device (102) based on a reception of an input on the 10 second device (104).

Description

TITLE OF THE INVENTION

METHOD AND SYSTEM FOR FACILITATING REMOTE

OPERATIONS

TECHNICAL FIELD

[0001] The present subject matter generally relates to remote connectivity solutions. More particularly, but not exclusively to a method and a system for facilitating remote operations in connected devices.

BACKGROUND

[0002] In recent years, the automotive industry has witnessed a significant transformation driven by advancements in connectivity and digital technologies. With the proliferation of smart devices and the Internet of Things (loT), vehicles have evolved beyond mere modes of transportation to become sophisticated digital platforms capable of seamless integration with wearable devices.

[0003] The traditional concept of vehicular operations has expanded to encompass remote functionalities that enable users to interact with their vehicles from afar. This paradigm shift has been fuelled by the growing demand for enhanced user convenience, safety, and connectivity in the automotive landscape.

[0004] Traditional connectivity options between devices such as vehicles and wearable devices have been limited that restrict a range and reliability of communication, leading to potential disconnections and unreliable data exchange. Further, performing remote operations on vehicles often involves cumbersome processes and lacks intuitive user interfaces. Users may face difficulties navigating through complex menus or dealing with inconsistent response times, leading to frustration and inefficiency.

[0005] Moreover, existing solutions for remote vehicle management lack seamless integration with wearable devices. Users may encounter compatibility issues, inconsistent performance across different wearable platforms, and limited functionality, diminishing the overall user experience. Furthermore, increasing connectivity of vehicles and wearable devices raises significant security concerns regarding unauthorized access and data breaches. Thus, sensitive vehicle data and control functionalities may be vulnerable to exploitation by malicious actors.

[0006] Traditional remote vehicle management systems often lack contextawareness. Such oversight results in suboptimal user experiences and potential safety hazards, as remote operations may inadvertently interfere with ongoing vehicle operations or pose risks to occupants.

[0007] Therefore, there is a need in the art for a method and system for facilitating remote operations in connected devices which addresses at least the aforementioned problems and other problems of known art.

[0008] Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of described systems with some aspects of the present disclosure, as set forth in the remainder of the present application and with reference to the drawings.

SUMMARY OF THE INVENTION

[0009] According to embodiments illustrated herein, the present invention provides a method and a system for facilitating remote operations in connected devices. The method comprises detecting, by a processor, a connection between a first device and a second device. The method comprises determining, by the processor, a ride status of the first device. The method comprises enabling, by the processor, one or more remote operations from a plurality of remote operations associated with the first device on the second device based on the detected connectivity and the determined ride status. Herein, at least one of the one or more remote operations is executed on the first device based on a reception of an input on the second device.

[00010] According to another embodiment illustrated herein, the present invention provides a system for facilitating remote operations. The system comprises a first device and a second device associated with the first device. The system further comprised a processor configured to detect a connection between the first device and the second device. The processor is configured to determine a ride status of the first device. The processor is configured to enable one or more remote operations from a plurality of remote operations associated with the first device on the second device based on the detected connectivity and the determined ride status at least one of the one or more remote operations is executed on the first device based on a reception of an input on the second device.

[00011] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

[00012] The details are described with reference to an embodiment of a gasket for a component assembly along with the accompanying diagrams. The same numbers are used throughout the drawings to reference similar features and components.

[00013] Figure 1 exemplarily illustrates a system for facilitating remote operations, in accordance with an embodiment of the present disclosure.

[00014] Figure 2 exemplarily illustrates a flowchart of a method for facilitating remote operations, in accordance with an embodiment of the present disclosure.

[00015] Figure 3 exemplarily illustrates an interaction diagram for facilitating remote operations based on usage of a third device, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

[00016] Exemplary embodiments are described with reference to the accompanying drawings. Wherever convenient, the same reference numbers are used throughout the drawings to refer to the same or like parts. While examples and features of disclosed principles are described herein, modifications, adaptations, and other implementations are possible without departing from the scope of the disclosed embodiments. It is intended that the following detailed description be considered as exemplary only, with the true scope being indicated by the following claims.

[00017] The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the invention(s)” unless expressly specified otherwise. The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise. The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

[00018] The embodiments of the present invention will now be described in detail with reference to a method for facilitating remote operations. However, the present invention is not limited to the present embodiments. The present subject matter is further described with reference to accompanying figures. It should be noted that the description and figures merely illustrate principles of the present subject matter. Various arrangements may be devised that, although not explicitly described or shown herein, encompass the principles of the present subject matter. Moreover, all statements herein reciting principles, aspects, and examples of the present subject matter, as well as specific examples thereof, are intended to encompass equivalents thereof.

[00019] A person with ordinary skills in the art will appreciate that the systems, modules, and sub-modules have been illustrated and explained to serve as examples and should not be considered limiting in any manner. It will be further appreciated that the variants of the above disclosed system elements, modules, and other features and functions, or alternatives thereof, may be combined to create other different systems or applications.

[00020] The present subject matter is described using a method and a system for facilitating remote operations, whereas the claimed subject matter can be used in any other type of application employing above-mentioned a method and a system for facilitating remote operations, with required changes and without deviating from the scope of invention. Further, it is intended that the disclosure and examples given herein be considered as exemplary only.

[00021] An objective of the present invention is to provide a method for facilitating remote operations. The method comprises detecting, by a processor, a connection between a first device and a second device. The method further comprises determining, by the processor, a ride status of the first device. The method further comprises enabling, by the processor, one or more remote operations from a plurality of remote operations associated with the first device on the second device based on the detected connectivity and the determined ride status, wherein at least one of the one or more remote operations is executed on the first device based on a reception of an input on the second device.

[00022] Another objective of the present invention is to provide a system for facilitating remote operations. The system comprises a first device and a second device associated with the first device. The system further comprised a processor configured to detect a connection between the first device and the second device. The processor is configured to determine a ride status of the first device. The processor is configured to enable one or more remote operations from a plurality of remote operations associated with the first device on the second device based on the detected connectivity and the determined ride status at least one of the one or more remote operations is executed on the first device based on a reception of an input on the second device.

[00023] It may be appreciated that, traditional connectivity options between devices such as vehicles and wearable devices have been limited that restrict a range and reliability of communication, leading to potential disconnections and unreliable data exchange. Further, performing remote operations on vehicles often involves cumbersome processes and lacks intuitive user interfaces. Users may face difficulties navigating through complex menus or dealing with inconsistent response times, leading to frustration and inefficiency. Moreover, existing solutions for remote vehicle management lack seamless integration with wearable devices. Users may encounter compatibility issues, inconsistent performance across different wearable platforms, and limited functionality, diminishing the overall user experience. Furthermore, increasing connectivity of vehicles and wearable devices raises significant security concerns regarding unauthorized access and data breaches. Thus, sensitive vehicle data and control functionalities may be vulnerable to exploitation by malicious actors.

[00024] In order to mitigate the aforesaid issues, disclosed is a method and a system for facilitating remote operations. In an embodiment, the method comprises detecting, by a processor, a connection between a first device and a second device.

[00025] In an embodiment, the method comprises authenticating, by the processor, a user associated with the second device. In an example, the second device may receive a user identification (ID) number and a password as an input. The second device may compare the received user ID and password with a user ID and a password saved in a memory device. The processor may then authenticate a login based on the comparison. In an embodiment, the method comprises establishing, by the processor, the connection between the first device and the second device based on the authentication. Herein, the connection is established directly, through a cloud-based platform, or indirectly through a third device connected to the first device. For example, the first device and the second device may be equipped with a wireless technology such as Bluetooth low energy (BLE). The first device and the second device may be connected directly. In another example, a communication network such as a cloud-based platform may be used to connect the first device and the second device. Herein, both the first device and the second device may be connected to the cloud-based platform. The communication between the first device and the second device may be via the cloud-based platform. In another example, the first device and the second device may be connected to the third device. The communication between the first device and the second device may be via the third device. [00026] In an embodiment, the first device is a vehicle, the second device is a wearable device, and the third device is a computing device. The first device may be a two-wheeler, a three-wheeler, or a four-wheeler vehicle. The second device may be the wearable device such as, smart helmets, smart watches, smart bands, and the like. The third device may be the computing device, such as a smart phone, a palmtop, a computer, a laptop, and the like.

[00027] In an embodiment, if the connection between the first device and the second device is undetected then the plurality of remote operations is disabled. In an embodiment, the method comprises rendering, by the processor, connection status information on a display device associated with the second device. For example, a message “connection error” may rendered on a display device associated with the second device. Further, one or more user interface (UI) elements associated with the plurality of remote operations that is rendered on the display device associated with the second device may be disabled. The disablement may prevent the user from providing an input for selection of the one or more remote operations on the second device.

[00028] The method further comprises determining, by the processor, a ride status of the first device. In an embodiment, the ride status is at least one of: an ignition OFF state, an ignition ON state, a vehicle in motion state, a vehicle in stop state. The vehicle in motion state may correspond to a driving state. The vehicle stop state may correspond to the non-driving state.

[00029] The method further comprises enabling, by the processor, one or more remote operations from a plurality of remote operations associated with the first device on the second device based on the detected connectivity and the determined ride status. Herein, at least one of the one or more remote operations is executed on the first device based on a reception of an input on the second device.

[00030] In an embodiment, if the ride status is the ignition OFF state, then the enabled one or more operations is at least one of: lock vehicle, unlock vehicle, turn on air conditioner, open sunroof, close sunroof, vehicle status check, open petrol lid. If the ride status is the ignition ON state, then the enabled one or more operations is at least one of open trunk, open hood, lock vehicle, unlock vehicle, open sunroof, close sunroof. If the ride status is the vehicle in motion state, then the enabled one or more operations is at least one of: stop vehicle, lock vehicle, turn on air conditioner, open sunroof, close sunroof, valet mode. If the ride status is the vehicle in stop state, then the enabled one or more operations is at least one of: start vehicle, stop vehicle, lock vehicle, unlock vehicle, lock door, unlock door, locate vehicle, vehicle status check, turn on air conditioner, turn off air conditioner, vehicle diagnostic, vehicle charging, turn ON horn, turn on light, open sunroof, close sunroof.

[00031] In an embodiment, the method comprises disabling, by the processor, the one or more remote operations based on the ride state. If the ride status is the ignition OFF then the disabled one or more operations is at least one of: vehicle diagnostic, turn on air conditioner, turn off air conditioner, vehicle status check, valet mode, stop vehicle. If the ride status is the ignition ON state, then the disabled one or more operations is at least one of: open petrol lid, locate vehicle, start vehicle. If the ride status is the vehicle in motion state, then the disabled one or more operations is at least one of: start vehicle, open petrol lid, open doors, locate vehicle, unlock vehicle, vehicle diagnostic, vehicle charging. If the ride status is the vehicle in stop state, then the enabled one or more operations is at least one of: stop vehicle, valet mode. In an embodiment, the method comprises rendering, by the processor, the ride status on a display device associated with the second device.

[00032] In an embodiment, the method comprises determining, by the processor, a parking brake status. The one or more remote operations associated with the first device is enabled based on the determined brake status. Herein, if the parking brake status is on state then, the one or more remote operations that are enabled is: locking doors, unlocking doors, stopping engine, opening trunk, closing trunk, air conditioner control, activating or deactivating lights, activating or deactivating horns. Herein, if the parking brake status is a on state, then the one or more remote operations that are disabled is: valet mode, starting engine.

[00033] In an embodiment, the method comprises determining, by the processor, one or more health parameters associated with the user. Herein, the one or more remote operations associated with the first device is enabled based on the determined one or more health parameters. Herein, the one or more enabled remote operations is at least one of: cabin temperature control, valet mode, turn off vehicle. For example, in case the first device is a vehicle and a body temperature of the user of the vehicle is high, then a cabin temperature may be decreased based on the body temperature. Further, in case a heartbeat of the user is high, then the vehicle may move to the valet mode.

[00034] In an embodiment, the method comprises receiving, on the second device, an input associated with the execution of the one or more remote operations. The method comprises detecting, by the processor, the connectivity between the first device and the second device at a first time instant based on the received input. In case the connection between the first device and the second device is lost, then the one or more remote operations may be unexecuted on the first device. Further, an error stating such as, “connection failure” may be rendered on a display device associated with the second device.

[00035] The method comprises determining, by the processor, the ride status of the second device. Herein, the one or more remote operation is executed on the first device based on the detected connectivity and the detected ride status.

[00036] In another aspect of the invention, a system for facilitating remote operations is provided. The system comprises a first device and a second device associated with the first device. The system also comprises a processor configured to detect a connection between the first device and the second device. The processor is configured to determine a ride status of the first device. The processor is configured to enable one or more remote operations from a plurality of remote operations associated with the first device on the second device based on the detected connectivity and the determined ride status. Herein, at least one of the one or more remote operations is executed on the first device based on a reception of an input on the second device.

[00037] The processor is configured to authenticate a user associated with the second device. The processor is configured to establish, by the processor, the connection between the first device and the second device based on the authentication. Herein, the connection is established directly, through a cloud-based platform, or indirectly through a third device connected to the first device.

[00038] The processor is configured to render connection status information on a display device associated with the second device.

[00039] The processor is configured to disable the one or more remote operations based on the ride state. Herein, if the ride status is the ignition OFF then the disabled one or more operations is at least one of: vehicle diagnostic, turn on air conditioner, turn off air conditioner, vehicle status check, valet mode, stop vehicle. Herein, if the ride status is the ignition ON state, then the disabled one or more operations is at least one of: open petrol lid, locate vehicle, start vehicle. Herein, if the ride status is the vehicle in motion state, then the disabled one or more operations is at least one of: start vehicle, open petrol lid, open doors, locate vehicle, unlock vehicle, vehicle diagnostic, vehicle charging. Herein, if the ride status is the vehicle in stop state, then the enabled one or more operations is at least one of: stop vehicle, valet mode.

[00040] The processor is configured to render the ride status on a display device associated with the second device.

[00041] The processor is configured to determine a parking brake status, wherein the one or more remote operations associated with the first device is enabled based on the determined brake status. If the parking brake status is on state then, the one or more remote operations that are enabled is: locking doors, unlocking doors, stopping engine, opening trunk, closing trunk, air conditioner control, activating or deactivating lights, activating or deactivating horns. If the parking brake status is a on state, then the one or more remote operations that are disabled is: valet mode, starting engine.

[00042] The processor is configured to determine one or more health parameters associated with the user. Herein, the one or more remote operations associated with the first device is enabled based on the determined one or more health parameters. Herein, the one or more enabled remote operations is at least one of: cabin temperature control, valet mode, turn off vehicle.

[00043] The processor is configured to receive an input associated with the execution of the one or more remote operation. The processor is configured to detect the connectivity between the first device and the second device at a first time instant based on the received input. The processor is configured to determine the ride status of the second device. The one or more remote operation is executed on the first device based on the detected connectivity at the first time instant.

[00044] Figure 1 exemplarily illustrates a system (100) for facilitating remote operations, in accordance with an embodiment of the present disclosure. The system (100) comprises a first device (102), a second device (104) associated with the first device (102), and a third device 106. The system (100) further comprises a processor.

[00045] In an embodiment, the processor may be configured to authenticate a user associated with the second device (104). The processor may be configured to establishing, by the processor, the connection between the first device (102) and the second device (104) based on the authentication. Herein, the connection may be established directly, through a cloud-based platform (108), or indirectly through the third device (106) connected to the first device (102).

[00046] The processor is further configured to detect a connection between the first device (102) and the second device (104). The processor is further configured to determine a ride status of the first device (102). The processor is further configured to enable one or more remote operations from a plurality of remote operations associated with the first device (102) on the second device (104) based on the detected connectivity and the determined ride status. Herein, at least one of the one or more remote operations is executed on the first device ( 102) based on a reception of an input on the second device (104).

[00047] In an embodiment, the first device (102) is a vehicle, the second device (104) is a wearable device, and the third device (106) is a computing device. The first device (102) may be a two-wheeler, a three-wheeler, or a four-wheeler vehicle. The second device (104) may be the wearable device such as, smart helmets, smart watches, smart bands, and the like. The third device (106) may be the computing device, such as a smart phone, a palmtop, a computer, a laptop, and the like.

[00048] With reference to Figure 1, the first device (102) may be enabled with either Bluetooth Low Energy (BLE) and a telematics control unit (TCU) or both. As shown in the Figure 1, the second device (104) can be connected to the first device (102) through either of the three ways. It can be connected directly to the first device (102) via BLE, through cloud-based platform 108 for first device (102) enabled with TCU or through the third device (106) which in turn will be connected to the first device (102) via BLE or TCU.

[00049] Figure 2 exemplarily illustrates a flowchart of a method (200) for facilitating remote operations, in accordance with an embodiment of the present disclosure. The flowchart (200) begins at start and moves to step 202.

[00050] At 202, an operation of selecting a first application associated with the second device 104 may be executed. Herein, the user associated with the second device 104 may open the first application on the second device 104.

[00051] At 204, a request for a connection change update may be received from the first device 102. The first device may be the vehicle. The connection may be directly, or through a cloud-based platform 108, or indirectly through the third device (106) connected to the first device (102).

[00052] At 206, an operation of checking the connection may be executed. Herein, the processor may be configured to detect the connection between the first device (102) and the second device (104). In case the connection between the first device ( 102) and the second device (104) is undetected, the flowchart (200) moves to 208.

[00053] At 208, an operation of disabling remote operations and displaying a reason for the disablement may be executed. In an embodiment, if the connection between the first device (102) and the second device (104) is undetected then the plurality of operations is disabled. In an embodiment, the processor may be configured to render connection status information on a display device associated with the second device (104).

[00054] In case the connection between the first device (102) and the second device (104) is detected, the flowchart (200) moves from 206 to 210.

[00055] At 210, an operation of reception of ride status change from the first device 102 may be received. Herein, the first device 102 may be the vehicle.

[00056] At 212, an operation of checking a vehicle ride status may be executed. The processor may be configured to determine a ride status of the first device (102). In an embodiment, the ride status is at least one of: an ignition OFF state, an ignition ON state, a vehicle in motion state, a vehicle in stop state, driving state. In an embodiment, the ride status may be rendered on a display device associated with the second device 104.

[00057] At 214, an operation of enabling remote operations may be executed. The processor may be configured to enable one or more remote operations from a plurality of remote operations associated with the first device (102) on the second device (104) based on the detected connectivity and the determined ride status. Herein, at least one of the one or more remote operations is executed on the first device (102) based on a reception of an input on the second device (104).

[00058] In an embodiment, if the ride status is the ignition OFF then the enabled one or more operations is at least one of: lock vehicle, unlock vehicle, turn on air conditioner, open sun roof, close sun roof, vehicle status check, open petrol lid, and wherein if the ride status is the ignition ON then the enabled one or more operations is at least one of: open trunk, open hood, lock vehicle, unlock vehicle, open sun roof, close sun roof wherein if the ride status is the vehicle in motion state then the enabled one or more operations is at least one of: stop vehicle, lock vehicle, turn on air conditioner, open sun roof, close sun roof, valet mode, and wherein if the ride status is the vehicle in stop state then the enabled one or more operations is at least one of: stall vehicle, stop vehicle, lock vehicle, unlock vehicle, lock door, unlock door, locate vehicle, vehicle status check, turn on air conditioner, turn off air conditioner, vehicle diagnostic, vehicle charging, turn ON horn, turn on light, open sun roof, close sun roof.

[00059] At 216, remote operation may be selected on the second device (104). The processor may receive, on the second device (104), an input associated with the execution of the one or more remote operation.

[00060] At 218, an operation of confirming the connection may be executed. The processor may detect the connectivity between the first device (102) and the second device (104) at a first time instant based on the received input. In case the connectivity is undetected or lost, then the flowchart moves to the block 208. In case the connectivity is detected, then the flowchart moves to the block (220).

[00061] At 220, an operation of confirming the ride status may be executed. The processor may determine the ride status of the second device (104). In case the second device (104) is ridden then the flowchart moves to the block 208, else the flowchart moves to the block (222).

[00062] At 222, an operation of sending the one or more remote operation based on the received input to the first device (102) may be executed. The one or more remote operation is executed on the first device (102) based on the detected connectivity and the ride status at the first time instant.

[00063] At 224, an operation of determining whether the first device (102) has responded with an error may be executed. In case the first device (102) has not responded with an error, the flowchart (200) may move to an end. In case the first device (102) has responded with an error, the flowchart (200) may move to block (226). [00064] At 226, an operation of determining an error type may be executed. In case the error is due to a fact that the first device (102) is being ridden, then the flowchart (200) may move to block (208). In case the error is due to other reasons, then the flowchart (200) may move to block (228).

[00065] At 228, an operation of displaying error may be executed. Herein, the processor may be configured to render the error on the display device associated with the second device (104).

[00066] Figure 3 exemplarily illustrates an interaction diagram (300) for facilitating remote operations based on usage of a third device, in accordance with an embodiment of the present disclosure. The interaction diagram (300) includes the second device (104), the third device (106), a first application (appl) (302), a second application (app2) (304), a smart cluster (306), a server (308), and a user (310). The smart cluster (306) and the server (308) may be associated with first device (102).

[00067] At time instant ti, the first device (102) may be set to the pairing mode. In case, the first device (102) is a vehicle, then the user (310) may set the vehicle to the paring mode.

[00068] At time instant t2, the second application (app2) (304) may scan and initiate pairing with the smart cluster (306) of the first device (102) based on a first user input. Herein, the first user input may be received based on interaction of a user (310) with a user interface element associated with the second application (app2) (304).

[00069] At time instant t3, the second application (app2) (304) may initiate a pairing procedure with the smart cluster (306) of the first device (102).

[00070] At time instant U, the smart cluster (306) may accept and complete the pairing of the smart cluster (306) with the third device (106).

[00071] At time instant ts, the smart cluster (306) may notify the user (310) of the pairing completion based on a display of information associated with the pairing completion. In some cases, sound feedback may be provided based on the pairing completion on an audio device associated with the smart cluster (306).

[00072] At time instant t6, a second user input associated with an initiation of linking an original equipment manufacturer (OEM) service of the second device 104 with an OEM service of the first device (102) may be received by the user (310) on the second application (304).

[00073] At time instant t7, the linking the OEM service of the second device (104) with the OEM service of the first device (102) may be initiated.

[00074] At time instant ts, the OEM service of the second device (104) with the OEM service of the first device (102) may be linked.

[00075] At time instant t the second application (304) may issue a notification associated with information of linking the OEM service of the second device (104) with the OEM service of the first device (102). The notification may be read by the user (310).

[00076] At time instant tio, the first application (302) may be opened the second device (104).

[00077] At time instant tn, the second device (104) a request for obtaining vehicle information may be transmitted from the second device (104) to the second application (304) present on the third device (106).

[00078] At time instant ti2, the second application (304) present on the third device (106) may transmit a request for obtaining latest vehicle information to the CoPD 308.

[00079] At time instant ti3, the server (308) may transmit the latest vehicle information to the second application (304) present on the third device (106).

[00080] At time instant ti4, the user input for initiation of one or more remote operations may be received from the user on the second device (104).

[00081] At time instant tis, the second device (104) may send a command for the one or more remote operations to the second application (304) on the second device (104). [00082] At time instant tis, the second device (104) may send a command for the one or more remote operations to the second application (304) on the third device (106).

[00083] At time instant tie, the second application (304) on the third device (106) may transmit a command for the one or more remote operations to the smart cluster (306).

[00084] At time instant tn, the second application (304) on the third device (106) may receive a response for the command for the one or more remote operations from the smart cluster (306).

[00085] At time instant tis, the second application (304) on the third device (106) may transmit the received response for the command for the one or more remote operations to the second device (104).

[00086] In a scenario, a person named as “John” owns a modern connected vehicle equipped with Bluetooth Low Energy (BLE) and a telematics control unit (TCU). John also wears a smartwatch that seamlessly integrates with his vehicle's remote control functionalities through a dedicated mobile app. John starts by downloading and installing a mobile app associated with his vehicle on his smartphone. Upon launching the app, he is prompted to authenticate using his credentials. Once authenticated, the app detects John's vehicle nearby using BLE technology. The app establishes a secure connection with the vehicle, either directly via BLE or through the cloud-based platform, depending on the vehicle's configuration and network availability. With the connection established, John's smartwatch syncs with the mobile app, providing him with a simplified user interface on his wearable device. John can now access various remote control functionalities directly from his smartwatch, such as locking/unlocking doors, starting the engine, checking vehicle status, and adjusting climate control settings. Before executing any remote operation, the app checks the vehicle's ride status and other contextual parameters to ensure safety and optimal user experience. For instance, if the vehicle is in motion or the parking brake is engaged, certain remote operations may be disabled to prevent interference with ongoing driving activities or potential safety hazards. As John initiates remote operations from his smartwatch, he receives real-time feedback and status updates on his wearable device. If any errors or connectivity issues arise, the app promptly notifies John, guiding him on corrective actions and ensuring a seamless user experience.

[00087] In another scenario, a person named as “Michel” owns a 2023 model car equipped with advanced connectivity features, including BLE and a TCU. Michel also wears a smartwatch that integrates seamlessly with his car's remote control functionalities through a dedicated mobile app. Michel downloads the "MyCarConnect" mobile app from the app store and installs it on his smartphone. Upon launching the app, Michel logs in using his credentials. The app detects Michel's car nearby using BLE technology. It establishes a secure connection with the vehicle, either directly via BLE or through the cloud-based platform, depending on network availability.

Once connected, Michel's smartwatch syncs with the mobile app. The app provides a simplified user interface on the smartwatch, allowing Michel to access remote control functionalities easily. The smartwatch displays options such as "Lock Doors," "Unlock Doors," "Start Engine," "Climate Control," and "Vehicle Status." Before executing any remote operation, the app checks the vehicle's status and other parameters. For instance, if the car's ignition is OFF, Michel can choose to "Lock Doors," "Unlock Doors," "Check Vehicle Status," or "Start Engine." If the ignition is ON, the app allows operations like "Open Trunk," "Open Hood," "Lock Doors," "Unlock Doors," "Open Sunroof," and "Close Sunroof." If the vehicle is in motion, remote operations are limited for safety reasons. If the car is stopped, John can perform actions like "Start Engine," "Stop Engine," "Lock Doors," "Unlock Doors," "Lock Trunk," "Unlock Trunk," "Locate Vehicle," "Check Vehicle Status," "Turn On Air Conditioner," "Turn Off Air Conditioner," "Run Vehicle Diagnostics," "Charge Vehicle," "Turn On Hom," "Turn On Lights," "Open Sunroof," and "Close Sunroof." As Michel initiates remote operations from his smartwatch, he receives real-time feedback and status updates. For example, if he tries to unlock the doors while the vehicle is in motion, the app displays a warning message indicating that the operation is disabled for safety reasons. If there's a connectivity issue, the app alerts Michel and provides troubleshooting steps. The system is designed to accommodate future enhancements and integration with advanced features. For instance, Michel can tag his health data for ride events, such as panic breaking or speeding, to track his driving habits and receive personalized insights. The app may incorporate machine learning algorithms to analyze Michel's usage patterns and optimize remote control functionalities accordingly.

[00088] The proposed system and method may thus, offer a comprehensive solution for remote vehicle management and wearable technology integration, addressing the challenges and providing users with enhanced convenience, safety, and connectivity on the road.

[00089] The proposed system and method may provide seamless connectivity. The proposed system and method may leverage various communication technologies to establish seamless connectivity between vehicles and wearable devices. This ensures reliable communication and minimizes connectivity issues, enhancing the overall user experience.

[00090] The proposed system and method may intuitive user interface. The proposed system and method may offer users a convenient way to access and control various vehicle functionalities remotely by providing a simplified user interface on wearable devices. This intuitive interface reduces the complexity of interaction and enhances usability, especially while driving.

[00091] Further, unlike traditional remote control systems, the proposed system and method may consider contextual factors such as vehicle ride status, ignition state, and safety parameters before executing remote operations. This context-aware approach ensures that remote operations are performed safely and efficiently, minimizing the risk of accidents or errors.

[00092] The proposed system and method may provide users with real-time feedback and alerts regarding the status of remote operations, connectivity issues, and potential errors. This proactive feedback mechanism enables users to stay informed and take appropriate actions promptly, improving user trust and satisfaction.

[00093] Furthermore, with robust authentication mechanisms and secure communication protocols, the proposed system and method may mitigate security risks associated with unauthorized access and data breaches. This enhances the overall security posture of the system and protects sensitive vehicle data from malicious exploitation.

[00094] The proposed system and method may accommodate future enhancements and integration with advanced features, such as health data tagging and machine learning algorithms. This scalability ensures that the system remains adaptable to evolving user needs and technological advancements in the automotive industry.

[00095] The objectives of the claimed invention collectively aim to address the technical challenges associated with the remote operations and provide a comprehensive solution that enables efficient execution of the remote operations.

[00096] In light of the above-mentioned advantages and the technical advancements provided by the disclosed method and the system facilitating remote operations, the claimed steps as discussed above are not routine, conventional, or well understood in the art, as the claimed steps enable the following solutions to the existing problems in conventional technologies. Further, the claimed steps clearly bring an improvement in the functioning of the configuration itself as the claimed steps provide a technical solution to a technical problem.

[00097] A description of an embodiment with several components in communication with another does not imply that all such components are required, On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.

[00098] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter and is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present invention are intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

[00099] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope being indicated by the following claims.

[000100] While the present disclosure has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made, and equivalents may be substituted without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from its scope. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed, but that the present disclosure will include all embodiments falling within the scope of the appended claims.

Reference Numerals:

102- First device

104- Second device

106- Third device 108- Cloud-based platform

202- Method

302- First application

304- Second application

306- Smart cluster 308- Server

310- User

Claims

CLAIMS We Claim:

1. A method (200) for facilitating remote operations, the method (200) comprising: detecting, by a processor, a connection between a first device (102) and a second device (104); determining, by the processor, a ride status of the first device (102); and enabling, by the processor, one or more remote operations from a plurality of remote operations associated with the first device (102) on the second device (104) based on the detected connectivity and the determined ride status, wherein at least one of the one or more remote operations is executed on the first device (102) based on a reception of an input on the second device (104).

2. The method (200) for facilitating remote operations as claimed in claim 1, the method (200) comprising: authenticating, by the processor, a user associated with the second device (104); and establishing, by the processor, the connection between the first device (102) and the second device (104) based on the authentication, wherein the connection is established directly, through a cloud-based platform, or indirectly through a third device (106) connected to the first device (102).

3. The method (200) for facilitating remote operations as claimed in claim 1 , wherein if the connection between the first device (102) and the second device (104) is undetected then the plurality of operations is disabled.

4. The method (200) for facilitating remote operations as claimed in claim 3 comprising rendering, by the processor, connection status information on a display device associated with the second device (104).

5. The method (200) for facilitating remote operations as claimed in claim

1, wherein the ride status is at least one of: an ignition OFF state, an ignition ON state, a vehicle in motion state, a vehicle in stop state, driving state.

6. The method (200) for facilitating remote operations as claimed in claim

5. wherein if the ride status is the ignition OFF then the enabled one or more operations is at least one of: lock vehicle, unlock vehicle, turn on air conditioner, open sun roof, close sun roof, vehicle status check, open petrol lid, and wherein if the ride status is the ignition ON then the enabled one or more operations is at least one of: open trunk, open hood, lock vehicle, unlock vehicle, open sun roof, close sun roof wherein if the ride status is the vehicle in motion state then the enabled one or more operations is at least one of: stop vehicle, lock vehicle, turn on air conditioner, open sun roof, close sun roof, valet mode, and wherein if the ride status is the vehicle in stop state then the enabled one or more operations is at least one of: start vehicle, stop vehicle, lock vehicle, unlock vehicle, lock door, unlock door, locate vehicle, vehicle status check, turn on air conditioner, turn off air conditioner, vehicle diagnostic, vehicle charging, turn ON horn, turn on light, open sun roof, close sun roof.

7. The method (200) for facilitating remote operations as claimed in claim 5 comprising disabling, by the processor, the one or more remote operations based on the ride state, wherein if the ride status is the ignition OFF then the disabled one or more operations is at least one of: vehicle diagnostic, turn on air conditioner, turn off air conditioner, vehicle status check, valet mode, stop vehicle, wherein if the ride status is the ignition ON state, then the disabled one or more operations is at least one of: open petrol lid, locate vehicle, start vehicle, wherein if the ride status is the vehicle in motion state, then the disabled one or more operations is at least one of: stall vehicle, open petrol lid, open doors, locate vehicle, unlock vehicle, vehicle diagnostic, vehicle charging, and wherein if the ride status is the vehicle in stop state, then the enabled one or more operations is at least one of: stop vehicle, valet mode

8. The method (200) for facilitating remote operations as claimed in claim 5 comprising rendering, by the processor, the ride status on a display device associated with the second device 104.

9. The method (200) for facilitating remote operations as claimed in claim 1 comprising determining, by the processor, a parking brake status, wherein the one or more remote operations associated with the first device is enabled based on the determined brake status, wherein if the parking brake status is on state then, the one or more remote operations that are enabled is: locking doors, unlocking doors, stopping engine, opening trunk, closing trunk, air conditioner control, activating or deactivating lights, activating or deactivating horns, wherein if the parking brake status is a on state, then the one or more remote operations that are disabled is: valet mode, starting engine.

10. The method (200) for facilitating remote operations as claimed in claim 1 comprising determining, by the processor, one or more health parameters associated with the user, wherein the one or more remote operations associated with the first device (102) is enabled based on the determined one or more health parameters, wherein the one or more enabled remote operations is at least one of: cabin temperature control, valet mode, turn off vehicle.

11. The method (200) for facilitating remote operations as claimed in claim 1 comprising: receiving, on the second device (104), an input associated with the execution of the one or more remote operation; detecting, by the processor, the connectivity between the first device ( 102) and the second device (104) at a first time instant based on the received input; and determining, by the processor, the ride status of the second device (104), wherein the one or more remote operation is executed on the first device (102) based on the detected connectivity at the first time instant.

12. The method (200) for facilitating remote operations as claimed in claim 1, wherein the first device (102) is a vehicle, the second device (104) is a wearable device, and the third device (106) is a computing device.

13. The system (100) for facilitating remote operations, wherein the system (100) comprises: a first device (102) and a second device (104) associated with the first device (102); a processor configured to: detect a connection between the first device (102) and the second device (104); determine a ride status of the first device (102); and enable one or more remote operations from a plurality of remote operations associated with the first device (102) on the second device (104) based on the detected connectivity and the determined ride status, wherein at least one of the one or more remote operations is executed on the first device (102) based on a reception of an input on the second device (104).

14. The system (100) for facilitating remote operations as claimed in claim 13, wherein the processor is configured to: authenticate, by the processor, a user associated with the second device (104); and establish, by the processor, the connection between the first device (102) and the second device (104) based on the authentication, wherein the connection is established directly, through a cloud-based platform, or indirectly through a third device (106) connected to the first device (102).

15. The system (100) for facilitating remote operations as claimed in claim 13, wherein if the connection between the first device (102) and the second device (104) is undetected then the plurality of operations is disabled.