DESC:METHOD AND SYSTEM FOR LOCATING LOST KEY OF VEHICLE
CROSS REFERENCE TO RELATED APPLICATIONS
The present application claims priority from Indian Provisional Patent Application No. 202421024542 filed on 27/03/2024, the entirety of which is incorporated herein by a reference.
TECHNICAL FIELD
The present disclosure generally relates to a keyfob of a vehicle. Particularly, the present disclosure relates to a vehicle system vehicle system for tracking a keyfob. Furthermore, the present disclosure relates to a method for tracking a keyfob for a vehicle.
BACKGROUND
Recently, the usage of vehicles has significantly increased in recent times due to urbanization, rising population, and the growing demand for personal mobility. With advancements in technology and infrastructure, vehicles have become an essential part of daily life for commuting, travel, and logistics. This surge in vehicle usage has led to a shift in transportation patterns, with more people relying on personal cars, ride-sharing services, and electric vehicles.
In modern vehicles, the keys serve as an essential component for securing access and enabling ignition or motor start. Traditionally, the mechanical keys are inserted into physical locks to unlock doors and start the vehicle through an ignition lock cylinder. Due to further advancements in automotive security, many vehicles now incorporate wireless key fobs that communicate electronically with the vehicle, allowing keyless entry and push-button start functionalities. Some systems even integrate both mechanical and wireless mechanisms to enhance convenience and reliability. Despite these advancements, a fundamental problem persists vehicle keys, whether mechanical or wireless, can be misplaced, dropped, or lost. Since the keys are small and frequently carried by the vehicle owners, the keys are prone to being misplaced in various environments, such as homes, offices, parking lots, or even within the vehicle itself. When the key is lost, the vehicle becomes inaccessible, causing frustration and potential delays. The problem is exacerbated when no spare key is available, requiring professional assistance to either retrieve a lost key, reprogram a new key, or replace locks altogether. The consequences of losing the vehicle key extend beyond inconvenience. In cases where a lost key remains unlocated, there is an inherent security risk, as unauthorized individuals may find and use the lost key to gain access to the vehicle. This raises concerns about vehicle theft, especially if the owner is unaware of the key’s location or unable to determine whether it has fallen into the wrong hands. Currently, some vehicle manufacturers offer mobile applications that can unlock and start the vehicle remotely, but such solutions may require an internet connection and are not universally available across all vehicle models.
Therefore, there exists a need of an improved system to overcome one or more problems associated as set forth above.
SUMMARY
An object of the present disclosure is to provide a vehicle system for tracking a keyfob.
Another object of the present disclosure is to provide a method for tracking a keyfob for a vehicle.
In accordance with first aspect of the present disclosure, there is provided a vehicle system for tracking a keyfob. The system comprises a vehicle control unit VCU configured to communicate with the keyfob having a unique identifier, a vehicle display screen communicatively coupled to the VCU. The VCU is configured to transmit vicinity requests to the keyfob at predetermined time intervals, detect a keyfob missing event upon failure to receive a vicinity response from the keyfob, store location data corresponding to the keyfob missing event, generate and display navigation instructions on the vehicle display screen to guide a user to the stored location data and perform a vicinity check upon arrival at the stored location data to determine if the keyfob is found.
The present disclosure provides the vehicle system for tracking the keyfob. The system as disclosed by present disclosure is advantageous in terms of enhanced user convenience, security, and operational efficiency. Beneficially, the system ensures continuous monitoring of the keyfob’s presence, thereby reducing the risk of misplacement. Beneficially, the system enables the users to quickly identify where the keyfob last detected which efficiently minimizes the search time. Additionally, the system ensures reliable connectivity and adaptability to different environments. Furthermore, the ability of the system to attempt Bluetooth Low Energy pairing and verify the keyfob’s unique identifier enhances security by preventing unauthorized access. Moreover, the system significantly allows for the remote storage and processing of keyfob location data, thereby enables the advanced analytics and potential remote access features. Overall, the system improves user experience, enhances vehicle security, and reduces the inconvenience associated with lost or misplaced keyfobs.
In accordance with second aspect of the present disclosure, there is provided a method for tracking a keyfob for a vehicle. The method comprising transmitting, by a vehicle control unit VCU of the vehicle, vicinity requests to the keyfob at predetermined time intervals, detecting, by the VCU, a keyfob missing event upon failure to receive a vicinity response from the keyfob, storing, by the VCU, location data corresponding to the keyfob missing event, generating and displaying, by the VCU, navigation instructions on a vehicle display screen to guide a user to the stored location data and performing, by the VCU, a vicinity check upon arrival at the stored location data to determine if the keyfob is found.
Additional aspects, advantages, features and objects of the present disclosure would be made apparent from the drawings and the detailed description of the illustrative embodiments constructed in conjunction with the appended claims that follow.
It will be appreciated that features of the present disclosure are susceptible to being combined in various combinations without departing from the scope of the present disclosure as defined by the appended claims.
BRIEF DESCRIPTION OF DRAWINGS
The summary above, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the present disclosure, exemplary constructions of the disclosure are shown in the drawings. However, the present disclosure is not limited to specific methods and instrumentalities disclosed herein. Moreover, those in the art will understand that the drawings are not to scale. Wherever possible, like elements have been indicated by identical numbers.
Embodiments of the present disclosure will now be described, by way of example only, with reference to the following diagrams wherein:
FIG. 1 illustrates a block diagram of a keyfob tracking system for a vehicle, in accordance with an aspect of the present disclosure.
FIG. 2 illustrates a flow chart of a method for tracking a keyfob for a vehicle, in accordance with another aspect of the present disclosure.
In the accompanying drawings, an underlined number is employed to represent an item over which the underlined number is positioned or an item to which the underlined number is adjacent. A non-underlined number relates to an item identified by a line linking the non-underlined number to the item. When a number is non-underlined and accompanied by an associated arrow, the non-underlined number is used to identify a general item at which the arrow is pointing.
DETAILED DESCRIPTION
The following detailed description illustrates embodiments of the present disclosure and ways in which they can be implemented. Although some modes of carrying out the present disclosure have been disclosed, those skilled in the art would recognise that other embodiments for carrying out or practising the present disclosure are also possible.
The description set forth below in connection with the appended drawings is intended as a description of certain embodiments of a vehicle system for tracking a keyfob and is not intended to represent the only forms that may be developed or utilised. The description sets forth the various structures and/or functions in connection with the illustrated embodiments; however, it is to be understood that the disclosed embodiments are merely exemplary of the disclosure that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimised to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.
While the disclosure is susceptible to various modifications and alternative forms, 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 disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.
The terms “comprise”, “comprises”, “comprising”, “include(s)”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, system 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 system. In other words, one or more elements in a system or apparatus preceded by “comprises... a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.
In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings and which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.
The present disclosure will be described herein below with reference to the accompanying drawings. In the following description, well known functions or constructions are not described in detail since they would obscure the description with unnecessary detail.
As used herein, the terms “vehicle” refers to any vehicle including but not limited to two-wheelers, three-wheelers, four-wheelers, and other automotive or non-automotive mobility systems, that incorporates a suspension system for absorbing shocks and vibrations during motion. The vehicle may be powered by internal combustion engines, electric motors, hybrid powertrains, or other propulsion systems, and may include land-based, off-road, or specialized transport applications.
As used herein, the term “keyfob tracking system” and “system” are used interchangeably and refer to a vehicle-integrated system configured to monitor, detect, and determine the location of a keyfob associated with a vehicle. The system typically comprises a vehicle control unit (VCU) that communicates with the keyfob using one or more wireless communication technologies, such as radio frequency (RF), low-frequency (LF), Bluetooth Low Energy (BLE), near-field communication (NFC), or ultra-wideband (UWB). The system is designed to detect a missing keyfob event upon loss of communication, store the last known location, and provide guidance to the user for retrieval.
As used herein, the term “keyfob” refers to a portable electronic device configured to communicate wirelessly with a vehicle control system to enable authentication, access control, and/or operational commands. The keyfob may include a unique identifier and be capable of transmitting and receiving signals using one or more communication protocols, such as radio frequency (RF), low frequency (LF), Bluetooth Low Energy (BLE), near field communication (NFC), or ultra-wideband (UWB).
As used herein, the terms “vehicle control unit” and “VCU” are used interchangeably and refer to an electronic control system configured to manage, monitor, and execute various functions within a vehicle. The VCU is communicatively coupled to one or more vehicle subsystems and external devices to facilitate real-time data exchange, processing, and control operations. Optionally, the data processing arrangement includes, but is not limited to, a microprocessor, a micro-controller, a complex instruction set computing (CISC) microprocessor, a reduced instruction set (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or any other type of processing circuit. Furthermore, the term “processor” may refer to one or more individual processors, processing devices and various elements associated with a processing device that may be shared by other processing devices. Furthermore, the data processing arrangement may comprise ARM Cortex-M series processors, such as the Cortex-M4 or Cortex-M7, or any similar processor designed to handle real-time tasks with high performance and low power consumption. Furthermore, the data processing arrangement may comprise custom and/or proprietary processors.
As used herein, the term “unique identifier” refers to a distinct data element assigned to an object, device, or entity to enable the singular identification within the system. The unique identifier may be a numeric, alphanumeric, or cryptographic code embedded in or associated with the keyfob to differentiate from other similar devices.
As used herein, the term “communicably coupled” refers to a bi-directional connection between the various components of the system. The bi-directional connection between the various components of the system enables exchange of data between two or more components of the system. Similarly, bi-directional connection between the system and other elements/modules enables exchange of data between system and the other elements/modules.
As used herein, the term “vehicle display screen” refers to a user interface device integrated into a vehicle, configured to visually present information to the driver or passengers. The display screen may be implemented as a touchscreen, LCD, LED, OLED, or any other visual output technology and may be positioned on the dashboard, centre console, instrument cluster, or other accessible locations within the vehicle.
As used herein, the term “vicinity requests” refers to periodic signals or communication messages transmitted by the Vehicle Control Unit (VCU) to the keyfob to determine presence within a predefined range. The vicinity requests may be transmitted using one or more wireless communication protocols, such as Radio Frequency (RF), Low Frequency (LF), Bluetooth Low Energy (BLE), Near Field Communication (NFC), or Ultra-Wideband (UWB).
As used herein, the term “predetermined time intervals” refers to specific, pre-defined durations between successive actions or events, as set by the system, algorithm, or user configuration. The predetermined time intervals may be fixed (e.g., every three seconds) or variable based on predefined conditions (e.g., dynamically adjusted based on battery level, signal strength, or system activity).
As used herein, the term “keyfob missing event” refers to a condition detected by the vehicle control unit (VCU) when the keyfob fails to respond to vicinity requests transmitted at predetermined time intervals. The keyfob missing event is triggered upon repeated unsuccessful communication attempts between the VCU and the keyfob, indicating that the keyfob is outside the vehicle's expected range or is otherwise unresponsive.
As used herein, the term “vicinity response” refers to a signal, message, or acknowledgment transmitted by the keyfob in response to the vicinity request from the vehicle control unit (VCU) within a defined communication range. The vicinity response may include authentication data, the unique identifier, or signal strength information to confirm the presence of the keyfob within the vehicle's proximity.
As used herein, the term “navigation instructions” refers to an electronic guidance data generated by the system to provide directional assistance to a user, wherein the instructions may include visual, auditory, or haptic cues indicating a route, path, or movement required to reach a target location. The navigation instructions may be dynamically updated based on real-time data, such as user position, environmental conditions, or proximity to the destination, and can be displayed on a screen, output through a speaker, or conveyed via a tactile feedback mechanism.
As used herein, the term “vicinity check” refers to a process performed by the system to determine the presence of the object, such as the keyfob, within the predefined range using wireless communication protocols. The vicinity check involves transmitting a signal from the vehicle control unit and evaluating the response from the keyfob to verify the proximity.
As used herein, the term “call-to-action notification” refers to a system-generated prompt or alert displayed on a user interface, such as a vehicle display screen or a mobile device, prompting the user to take a specific action. The notification is triggered based on predefined conditions or events, such as detecting a missing keyfob, and may include interactive elements that allow the user to initiate a response, such as starting navigation to the last known location of the keyfob. The notification serves to guide user behavior in response to system-detected events, enhancing usability and operational efficiency.
As used herein, the term “Bluetooth Low Energy” and “BLE” are used interchangeably and refer to a wireless communication technology designed for low-power, short-range data exchange between electronic devices. The BLE operates within the 2.4 GHz ISM (Industrial, Scientific, and Medical) band and utilizes frequency hopping to minimize interference while ensuring reliable connectivity.
As used herein, the term “keyfob found event” refers to a detected condition in which a vehicle control unit determines that a previously missing keyfob is within proximity and identifiable based on predefined authentication criteria. The event is triggered when the VCU successfully receives a response from the keyfob during a vicinity check, establishes a verified connection via Bluetooth Low Energy (BLE) pairing, or detects a valid unique identifier through another wireless communication protocol such as radio frequency (RF), low frequency (LF), near field communication (NFC), or ultra-wideband (UWB).
As used herein, the term “radio frequency” and “RF” are used interchangeably and refer to a wireless communication technology that utilizes electromagnetic waves within a predefined frequency spectrum to enable data transmission between electronic devices. The RF signals are used for various applications, including remote keyless entry, vehicle access systems, and short- or long-range communication between a vehicle and its keyfob.
As used herein, the term “near field communication” and “NFC” are used interchangeably and refer to a short-range wireless communication technology that enables data exchange between two NFC-enabled devices when the devices are in close proximity, typically within a few centimetres. The NFC operates at a frequency of 13.56 MHz and supports bidirectional communication for secure authentication, data transfer, and contactless transactions.
As used herein, the term “ultra-wideband” and “UWB” are used interchangeably and refer to a radio frequency communication technology that operates over a wide frequency spectrum, typically exceeding 500 MHz bandwidth, enabling precise distance measurement and secure, short-range wireless communication. The UWB transmits low-power pulses across a broad frequency range, allowing for high-precision localization with centimeter-level accuracy.
As used herein, the term “cloud storage” refers to a network-based data storage system comprising one or more remote servers configured to store, process, and manage data, wherein the data is accessible by a user device or computing system via a communication network. The cloud storage system provides scalable storage capacity, secure access control, and remote data retrieval, enabling real-time data synchronization and redundancy across multiple server locations.
As used herein, the term “keyfob location data” refers to information associated with the geographical or positional coordinates of a keyfob relative to a vehicle or a predefined reference point. The keyfob location data may include, but is not limited to, GPS coordinates, timestamped location records, signal strength indicators from wireless communication protocols and proximity metrics derived from vehicle sensors.
Figure 1 in accordance with an embodiment describes a keyfob tracking system 100 for a vehicle. The system 100 comprising a vehicle control unit VCU 102 configured to communicate with the keyfob having a unique identifier, a vehicle display screen 104 communicably coupled to the VCU 102. The VCU 102 is configured to transmit vicinity requests to the keyfob at predetermined time intervals, detect a keyfob missing event upon failure to receive a vicinity response from the keyfob, store location data corresponding to the keyfob missing event, generate and display navigation instructions on the vehicle display screen 104 to guide a user to the stored location data and perform a vicinity check upon arrival at the stored location data to determine if the keyfob is found.
The present disclosure discloses the keyfob tracking system 100 for the vehicle. The system 100 as disclosed by the present disclosure is advantageous in terms of enhanced automation, user convenience and reliability. Beneficially, by enabling the vehicle control unit 102 to periodically transmit vicinity requests to the keyfob, the system 100 ensures real-time monitoring of the keyfob presence without requiring manual intervention. Beneficially, the ability of the system 100 to detect a keyfob missing event upon failure to receive a response enhances the security by alerting the user immediately, thereby minimizing the risk of losing access to the vehicle. Furthermore, the VCU 102 stores the keyfob last known location upon detecting the keyfob absence and the stored data is then used to generate navigation instructions on the vehicle display screen 104 which allows the user to be guided back to the potential location of the lost keyfob, thereby reducing the search time and effort. Furthermore, the ability of the system 100 to push a call-to-action notification to initiate navigation adds a layer of proactive assistance which ensures that the users are immediately directed towards retrieving towards the keyfob. Beneficially, the incorporation of turn-by-turn navigation further refines the user experience by providing precise guidance which eliminates the guesswork. Also, the system 100 enhances the reliability by implementing a vicinity check upon arrival at the stored location, determining if the keyfob is present. The vicinity verification is achieved through Bluetooth Low Energy (BLE) pairing and unique identifier authentication, which ensures that the retrieved keyfob is indeed the correct one. Additionally, the system 100 leverages a cloud service for data storage and processing which provides a more scalable and persistent tracking mechanism.
In an embodiment, the VCU 102 is configured to transmit vicinity requests every three seconds. The periodic transmission ensures continuous monitoring of the keyfob presence within the vehicle's communication range. If the keyfob fails to respond within the specific time interval, the VCU 102 promptly detects the keyfob missing event and initiates appropriate tracking and navigation actions. The three-second interval is optimized to balance power efficiency and real-time responsiveness which ensures that the system 100 provides timely alerts while minimizing unnecessary energy consumption in both the keyfob and the VCU.
In an alternate embodiment, the VCU 102 is configured to transmit vicinity requests every two second interval. In an alternate embodiment, the VCU 102 is configured to transmit vicinity requests every second interval. In an alternate embodiment, the VCU 102 is configured to transmit vicinity requests as per the predefined time interval.
In an embodiment, the VCU 102 is configured to push a call-to-action notification to the vehicle display screen 104 for initiating navigation to the location of the keyfob missing event. The system 100 includes the VCU 102 configured to detect the keyfob missing event and assist the user in retrieving the keyfob efficiently. Upon detecting the missing event, the VCU 102 pushes the call-to-action notification to the vehicle display screen 104 which prompts the user to initiate navigation to the last known location of the keyfob. Beneficially, the call-to-action feature ensures that the user receives an immediate alert along with an interactive option to begin navigation which significantly helps to minimize the search time. Additionally, the system 100 enhances the convenience by automating the retrieval process, reducing the risk of misplaced keyfobs, and improving overall vehicle security.
In an embodiment, the VCU 102 is configured to provide turn-by-turn directions to the location of the keyfob missing event on the vehicle display screen 104. The VCU 102 continuously monitors the presence of the keyfob by transmitting vicinity requests at predetermined intervals. Upon detecting the keyfob missing event, the VCU stores the last known location data of the keyfob. To assist the user in retrieving the lost keyfob, the VCU 102 generates the turn-by-turn navigation instructions and displays the instructions on the vehicle display screen 104. Beneficially, the turn-by-turn navigation guidance significantly ensures that the user may efficiently reach the stored location, which further helps to reduce the search time and improve overall convenience.
In an embodiment, the VCU 102 is configured to attempt to pair with the keyfob over Bluetooth Low Energy upon arrival at the stored location data and detect the keyfob found event when either BLE pairing is successful and the keyfob unique identifier is verified, or when the vicinity check is successful. Upon arrival at the stored location data corresponding to the keyfob missing event, the VCU 102 initiates the attempt to pair with the keyfob over BLE. The pairing attempt allows the system 100 to establish a direct communication link with the keyfob, verifying the presence of the keyfob within the vicinity. To further ensure the authenticity of the detected keyfob, the VCU 102 performs the unique identifier verification upon successful BLE pairing. If the unique identifier of the keyfob matches the one registered with the vehicle, the system 100 confirms the keyfob found event.
In an embodiment, the keyfob is configured to communicate with the VCU 102 using at least one of radio frequency and low frequency communication, Bluetooth Low Energy and near field communication or ultra-wideband and near field communication. The keyfob may utilize Radio Frequency and Low Frequency communication to enable traditional proximity-based key detection and authentication. Additionally, the keyfob may establish a connection with the VCU 102 using BLE and NFC, enhancing the energy efficiency while enabling short-range wireless interaction. In another implementation, the keyfob supports UWB and NFC communication, ensures the precise location tracking with high accuracy and resistance to interference. Beneficially, by incorporating multiple communication protocols, the system 100 ensures enhanced reliability, improved security, and seamless keyfob detection, even in environments where one method might be obstructed or ineffective.
In an embodiment, the system 100 comprises a cloud service 106 communicably coupled to the VCU 102 for storing and processing keyfob location data. When the keyfob missing event may be detected, the VCU 102 transmits the last known location data to the cloud service, ensuring that the information may be persistently stored and accessible even if the vehicle may be powered off or out of communication range. The cloud service may further process the stored data to enhance tracking accuracy, provide historical location insights, and enable remote access through the vehicle display screen 104. Beneficially, the integration of the cloud storage ensures that the keyfob location remains retrievable even when the vehicle’s onboard systems may be unavailable, thereby improving the tracking reliability and user convenience.
In an embodiment, the keyfob tracking system 100 for the vehicle. The system 100 comprising the vehicle control unit VCU 102 configured to communicate with the keyfob having the unique identifier, the vehicle display screen 104 communicably coupled to the VCU 102. The VCU 102 is configured to transmit vicinity requests to the keyfob at predetermined time intervals, detect the keyfob missing event upon failure to receive the vicinity response from the keyfob, store location data corresponding to the keyfob missing event, generate and display navigation instructions on the vehicle display screen 104 to guide the user to the stored location data and perform the vicinity check upon arrival at the stored location data to determine if the keyfob is found. Furthermore, the VCU 102 is configured to transmit vicinity requests every three seconds. Furthermore, the VCU 102 is configured to push a call-to-action notification to the vehicle display screen 104 for initiating navigation to the location of the keyfob missing event. Furthermore, the VCU 102 is configured to provide turn-by-turn directions to the location of the keyfob missing event on the vehicle display screen 104. Furthermore, the VCU 102 is configured to attempt to pair with the keyfob over Bluetooth Low Energy upon arrival at the stored location data and detect the keyfob found event when either BLE pairing is successful and the keyfob unique identifier is verified, or when the vicinity check is successful. Furthermore, the keyfob is configured to communicate with the VCU 102 using the at least one of radio frequency and low frequency communication, Bluetooth Low Energy and near field communication or ultra-wideband and near field communication. Furthermore, the system 100 comprises the cloud service 106 communicably coupled to the VCU 102 for storing and processing keyfob location data.
Figure 2 describes a method 200 for tracking a keyfob for a vehicle. The method 200 starts at step 202 and completes at step 210. At step 202, the method 200 comprises transmitting, by a vehicle control unit 102 of the vehicle, vicinity requests to the keyfob at predetermined time intervals. At step 204, the method 200 comprises detecting, by the VCU 102, a keyfob missing event upon failure to receive a vicinity response from the keyfob. At step 206, the method 200 comprises storing, by the VCU 102, location data corresponding to the keyfob missing event. At step 208, the method 200 comprising generating and displaying, by the VCU 102, navigation instructions on a vehicle display screen 104 to guide a user to the stored location data. At step 210, the method 200 comprising performing, by the VCU 102, a vicinity check upon arrival at the stored location data to determine if the keyfob is found.
In an embodiment, transmitting vicinity requests comprises transmitting the vicinity requests every three seconds.
In an embodiment, the method 200 comprises pushing, by the VCU 102, a call-to-action notification to the vehicle display screen 104 for initiating navigation to the location of the keyfob missing event.
In an embodiment, the method 200 comprises providing, by the VCU 102, turn-by-turn directions to the location of the keyfob missing event on the vehicle display screen 104.
In an embodiment, the method 200 comprises attempting, by the VCU 102, to pair with the keyfob over Bluetooth Low Energy BLE upon arrival at the stored location data and detecting, by the VCU 102, a keyfob found event when either BLE pairing is successful and the keyfob unique identifier is verified, or when the vicinity check is successful.
In an embodiment, communicating with the keyfob comprises utilizing at least one of radio frequency and low frequency communication, Bluetooth Low Energy and near field communication or ultra-wideband and near field communication.
In an embodiment, the method 200 comprises communicating, by the VCU 102, with a cloud service 106 for storing and processing keyfob location data.
It would be appreciated that all the explanations and embodiments of the portable device 100 also applies mutatis-mutandis to the method 200.
In the description of the present invention, it is also to be noted that, unless otherwise explicitly specified or limited, the terms “disposed,” “mounted,” and “connected” are to be construed broadly, and may for example be fixedly connected, detachably connected, or integrally connected, either mechanically or electrically. They may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meaning of the above terms in the present invention can be understood in specific cases to those skilled in the art.
Modifications to embodiments and combination of different embodiments of the present disclosure described in the foregoing are possible without departing from the scope of the present disclosure as defined by the accompanying claims. Expressions such as “including”, “comprising”, “incorporating”, “have”, “is” used to describe and claim the present disclosure are intended to be construed in a non- exclusive manner, namely allowing for items, components or elements not explicitly described also to be present. Reference to the singular is also to be construed to relate to the plural where appropriate.
Although embodiments have been described with reference to a number of illustrative embodiments thereof, it should be understood that numerous other modifications and embodiments can be devised by those skilled in the art that will fall within the spirit and scope of the principles of this disclosure. More particularly, various variations and modifications are possible in the component parts and/or arrangements of the subject combination arrangement within the scope of the present disclosure, the drawings and the appended claims. In addition to variations and modifications in the component parts and/or arrangements, alternative uses will also be apparent to those skilled in the art.
,CLAIMS:WE CLAIM:
1. A keyfob tracking system (100) for a vehicle, wherein the system (100) comprising:
- a vehicle control unit VCU (102) configured to communicate with the keyfob having a unique identifier;
- a vehicle display screen (104) communicably coupled to the VCU (102);
wherein the VCU (102) is configured to:
- transmit vicinity requests to the keyfob at predetermined time intervals;
- detect a keyfob missing event upon failure to receive a vicinity response from the keyfob;
- store location data corresponding to the keyfob missing event;
- generate and display navigation instructions on the vehicle display screen (104) to guide a user to the stored location data; and
- perform a vicinity check upon arrival at the stored location data to determine if the keyfob is found.
2. The system (100) as claimed in claim 1, wherein the VCU (102) is configured to transmit vicinity requests every three seconds.
3. The system (100) as claimed in claim 1, wherein the VCU (102) is configured to push a call-to-action notification to the vehicle display screen (104) for initiating navigation to the location of the keyfob missing event.
4. The system (100) as claimed in claim 1, wherein the VCU (102) is configured to provide turn-by-turn directions to the location of the keyfob missing event on the vehicle display screen (104).
5. The system (100) as claimed in claim 1, wherein the VCU (102) is configured to:
- attempt to pair with the keyfob over Bluetooth Low Energy BLE upon arrival at the stored location data; and
- detect a keyfob found event when either BLE pairing is successful and the keyfob unique identifier is verified, or when the vicinity check is successful.
6. The system (100) as claimed in claim 1, wherein the keyfob is configured to communicate with the VCU (102) using at least one of:
- radio frequency RF and low frequency LF communication;
- Bluetooth Low Energy BLE and near field communication NFC; or
- ultra-wideband UWB and near field communication NFC.
7. The system (100) as claimed in claim 1, wherein the system (100) comprises a cloud service (106) communicably coupled to the VCU (102) for storing and processing keyfob location data.
8. A method (200) for tracking a keyfob for a vehicle, the method (200) comprising:
- transmitting, by a vehicle control unit VCU (102) of the vehicle, vicinity requests to the keyfob at predetermined time intervals;
- detecting, by the VCU (102), a keyfob missing event upon failure to receive a vicinity response from the keyfob;
- storing, by the VCU (102), location data corresponding to the keyfob missing event;
- generating and displaying, by the VCU (102), navigation instructions on a vehicle display screen (104) to guide a user to the stored location data; and
- performing, by the VCU (102), a vicinity check upon arrival at the stored location data to determine if the keyfob is found.
9. The method (200) as claimed in claim 8, wherein transmitting vicinity requests comprises transmitting the vicinity requests every three seconds.
10. The method (200) as claimed in claim 8, wherein the method (200) comprises pushing, by the VCU (102), a call-to-action notification to the vehicle display screen (104) for initiating navigation to the location of the keyfob missing event.
11. The method (200) as claimed in claim 8, wherein the method (200) comprises providing, by the VCU (102), turn-by-turn directions to the location of the keyfob missing event on the vehicle display screen (104).
12. The method (200) as claimed in claim 8, wherein the method (200) comprises:
- attempting, by the VCU (102), to pair with the keyfob over Bluetooth Low Energy BLE upon arrival at the stored location data; and
- detecting, by the VCU (102), a keyfob found event when either BLE pairing is successful and the keyfob unique identifier is verified, or when the vicinity check is successful.
13. The method (200) as claimed in claim 8, wherein communicating with the keyfob comprises utilizing at least one of:
- radio frequency RF and low frequency LF communication;
- Bluetooth Low Energy BLE and near field communication NFC; or
- ultra-wideband UWB and near field communication NFC.
14. The method (200) as claimed in claim 8, wherein the method (200) comprises communicating, by the VCU (102), with a cloud service (106) for storing and processing keyfob location data.