Description:TECHNICAL FIELD
[0001] The present disclosure relates to vehicle location tracking devices. In particular, the present disclosure relates to a system for tracking location of a vehicle in both horizontal and vertical spaces.

BACKGROUND
[0002] Generally, when a vehicle is parked in large, multistorey parking lots, locating the parked vehicle is challenging. Owners often end up searching on the wrong floors, leading to time wastage and an overall unpleasant experience. Conventionally, a find-my-vehicle feature typically relies on Global Positioning System (GPS) coordinates, which prove highly inaccurate in closed spaces or underground parking lots. Further, the find-my-vehicle feature currently operate solely in a x-y plane, i.e., the find-my-vehicle feature can only determine the horizontal location of the vehicles. An alternative approach to locate the remotely parked vehicle involves using vehicle lamps or horns triggered through a key fob, which is effective only within the key fob’s limited connectivity range. However, these approaches exhibit significant inaccuracies under covered parking circumstances.
[0003] One such prior art discloses a vehicle locating and alarm system that enables a user to remotely access the vehicle and, if required, activate an alarm system therein. This system also automatically calls one or more pre-programmed telephone numbers upon the occurrence of certain events, such as a collision or other emergency. Upon remotely accessing the vehicle by telephone or computer, the user is, upon entering a valid Personal Identification Number (PIN), supplied with the vehicle’s location, speed and a command option menu for alarm and deterrent device control.
[0004] One such prior art discloses an apparatus and a method of determining bearing and distance measurements between a mobile device and an object using Radio Frequency (RF) based measurements. The mobile device communicates with a control system in the object to determine the relative bearing between the mobile device and the object with respect to magnetic north and, optionally, the distance between the mobile device and the object. An indicator on the mobile device aid in directing the user of the mobile device toward the object as the mobile device is moved relative to the object. The mobile device can be a key fob and the object can be a vehicle.
[0005] One such prior art discloses a parking position guiding system. The parking position guiding system includes a display unit provided in an ignition key to display information. An air pressure sensor is incorporated in the ignition key for detecting an air pressure. An acceleration sensor is incorporated in the ignition key for detecting an acceleration. A geomagnetic sensor is embedded in the ignition key for detecting geomagnetism data. A control unit is built in the ignition key for calculating a change in the number of building floors, a moving distance, and a direction in which the driver has moved from the vehicle using the detection information of each of the sensors, and controlling the calculated information to be displayed through the display unit.
[0006] However, the prior art(s) captures the pressure reading at the time of locking the vehicle. The pressure reading may change due to atmospheric factors, time of day, temperature etc, thereby leading to inaccuracies in identifying the location of the vehicle. There is, therefore, a need for an improved system for locating the vehicle by overcoming the deficiencies in the prior art(s).

OBJECTS OF THE PRESENT DISCLOSURE
[0007] A general object of the present disclosure is to provide a system for locating a vehicle in both horizontal and vertical spaces.
[0008] An object of the present disclosure is to provide a system in which a hand-held device simultaneously communicates with a keyless fob device and a vehicle to improve vehicle locating tracing accuracy.
[0009] An object of the present disclosure is to provide a system that accurately estimates a vertical distance of a vehicle from a keyless fob device and/or a hand-held device.
[0010] Another object of the present disclosure is to provide a system that captures real-time atmospheric pressure readings from a vehicle and subsequently compares them with most recent live pressure readings from a keyless fob device to accurately locate the vehicle.

SUMMARY
[0011] Aspects of the present disclosure relate to vehicle location tracking devices. In particular, the present disclosure relates to a system for tracking location of a vehicle in both horizontal and vertical spaces.
[0012] In an aspect, the present disclosure describes a system for locating a vehicle. The system includes a keyless fob device communicatively connected to a vehicle. Each of the keyless fob device and the vehicle includes at least one altitude sensor such as a barometric pressure sensor for continuously measuring altitude of the vehicle. The system includes a hand-held device communicatively connected to the keyless fob device and the vehicle. The hand-held device is configured to provide real-time altitude of the vehicle to a user.
[0013] In an embodiment, the continuously measured altitude of the vehicle may be stored in a remote server.
[0014] In an embodiment, the keyless fob device may be communicatively connected to the vehicle via a wireless network, and the hand-held device may be communicatively connected to the keyless fob device and the vehicle via the wireless network.
[0015] In an embodiment, the at least one altitude sensor associated with the vehicle may be configured to measure a dynamic altitude when the vehicle is in motion, and a static altitude when the vehicle is stationary. The dynamic altitude and the static altitude may be stored in the remote server.
[0016] In an embodiment, the hand-held device may include a primary processor configured to compare the static altitude with the real-time altitude of the vehicle, and provide an updated altitude value of the vehicle.
[0017] In an embodiment, the keyless fob device may include a secondary processor configured to compare the static altitude with the real-time altitude of the vehicle, and provide the updated altitude value of the vehicle, when the hand-held device is inactive.
[0018] In an embodiment, the updated altitude value of the vehicle may be notified to the user, via the hand-held device or the keyless fob device, to indicate if the vehicle is located on at least one of a same level, an upper level, or a lower level.
[0019] In an embodiment, the vehicle may include a tertiary processor configured to determine a current location of the vehicle and the altitude of the vehicle, when the vehicle transitions from motion to stationary.
[0020] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.

BRIEF DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0022] FIG. 1 illustrates an example schematic view of an electric saddle type vehicle.
[0023] FIG. 2A illustrates a block diagram of a system for locating a vehicle, according to embodiments of the present disclosure.
[0024] FIG. 2B illustrates a schematic view of a keyless fob device included in the system as illustrated in FIG. 2A, according to embodiments of the present disclosure.
[0025] FIG. 3 illustrates a flow chart depicting an example scenario where a vehicle is locked without fob-in boot check, according to embodiments of the present disclosure.
[0026] FIG. 4 illustrates a flow chart depicting an example scenario where a vehicle is locked with fob-in boot check, according to embodiments of the present disclosure.
[0027] FIG. 5 illustrates a flow chart depicting an example scenario of locating a vehicle with a keyless fob device and a hand-held device, according to embodiments of the present disclosure.
[0028] FIG. 6 illustrates a flow chart depicting an example scenario of locating a vehicle with a keyless fob device, according to embodiments of the present disclosure.

DETAILED DESCRIPTION
[0029] For the purpose of promoting an understanding of the principles of the present disclosure, reference will now be made to the various embodiments and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the present disclosure is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the present disclosure as illustrated therein being contemplated as would normally occur to one skilled in the art to which the present disclosure relates.
[0030] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the present disclosure and are not intended to be restrictive thereof.
[0031] Whether or not a certain feature or element was limited to being used only once, it may still be referred to as “one or more features” or “one or more elements” or “at least one feature” or “at least one element.” Furthermore, the use of the terms “one or more” or “at least one” feature or element do not preclude there being none of that feature or element, unless otherwise specified by limiting language including, but not limited to, “there needs to be one or more…” or “one or more elements is required.
[0032] Reference is made herein to some “embodiments.” It should be understood that an embodiment is an example of a possible implementation of any features and/or elements of the present disclosure. Some embodiments have been described for the purpose of explaining one or more of the potential ways in which the specific features and/or elements of the proposed disclosure fulfil the requirements of uniqueness, utility, and non-obviousness.
[0033] Use of the phrases and/or terms including, but not limited to, “a first embodiment,” “a further embodiment,” “an alternate embodiment,” “one embodiment,” “an embodiment,” “multiple embodiments,” “some embodiments,” “other embodiments,” “further embodiment”, “furthermore embodiment”, “additional embodiment” or other variants thereof do not necessarily refer to the same embodiments. Unless otherwise specified, one or more particular features and/or elements described in connection with one or more embodiments may be found in one embodiment, or may be found in more than one embodiment, or may be found in all embodiments, or may be found in no embodiments. Although one or more features and/or elements may be described herein in the context of only a single embodiment, or in the context of more than one embodiment, or in the context of all embodiments, the features and/or elements may instead be provided separately or in any appropriate combination or not at all. Conversely, any features and/or elements described in the context of separate embodiments may alternatively be realized as existing together in the context of a single embodiment.
[0034] Any particular and all details set forth herein are used in the context of some embodiments and therefore should not necessarily be taken as limiting factors to the proposed disclosure. The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by “comprises... a” does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.
[0035] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings.
[0036] For the sake of clarity, the first digit of a reference numeral of each component of the present disclosure is indicative of the Figure number, in which the corresponding component is shown. For example, reference numerals starting with digit “1” are shown at least in Figure 1. Similarly, reference numerals starting with digit “2” are shown at least in Figure 2.
[0037] An Electric Vehicle (EV) or a battery powered vehicle including, and not limited to two-wheelers such as scooters, mopeds, motorbikes/motorcycles; three-wheelers such as auto-rickshaws, four-wheelers such as cars and other Light Commercial Vehicles (LCVs) and Heavy Commercial Vehicles (HCVs) primarily work on the principle of driving an electric motor using the power from the batteries provided in the EV. Furthermore, the EV may have at least one wheel which is electrically powered to traverse such a vehicle. The term ‘wheel’ may be referred to any ground-engaging member which allows traversal of the EV over a path. The types of EVs include Battery Electric Vehicle (BEV), Hybrid Electric Vehicle (HEV) and Range Extended Electric Vehicle. However, the subsequent paragraphs pertain to the different elements of the Battery Electric Vehicle (BEV).
[0038] In construction, as shown in FIG. 1, an EV (10) typically comprises a battery or battery pack (12) enclosed within a battery casing and includes a Battery Management System (BMS), an on-board charger (14), a Motor Controller Unit (MCU), an electric motor (16), and an electric transmission system (18). The primary function of the above-mentioned elements is detailed in the subsequent paragraphs: The battery of the EV (10) (also known as Electric Vehicle Battery (EVB) or traction battery) is re-chargeable in nature and is the primary source of energy required for the operation of the EV (10), wherein the battery (12) is typically charged using the electric current taken from the grid through a charging infrastructure (20). The battery (12) may be charged using Alternating Current (AC) or Direct Current (DC), wherein in case of AC input, the on-board charger (14) converts the AC signal to DC signal after which the DC signal is transmitted to the battery (12) via the BMS. However, in case of DC charging, the on-board charger (14) is bypassed, and the current is transmitted directly to the battery (12) via the BMS.
[0039] The battery (12) is made up of a plurality of cells which are grouped into a plurality of modules in a manner in which the temperature difference between the cells does not exceed 5 degrees Celsius. The terms “battery”, “cell”, and “battery cell” may be used interchangeably and may refer to any of a variety of different rechargeable cell compositions and configurations including, but not limited to, lithium-ion (e.g., lithium iron phosphate, lithium cobalt oxide, other lithium metal oxides, etc.), lithium-ion polymer, nickel metal hydride, nickel cadmium, nickel hydrogen, nickel-zinc, silver zinc, or other battery type/configuration. The term “battery pack” as used herein may be referred to multiple individual batteries enclosed within a single structure or multi-piece structure. The individual batteries may be electrically interconnected to achieve a desired voltage and capacity for a desired application. The Battery Management System (BMS) is an electronic system whose primary function is to ensure that the battery (12) is operating safely and efficiently. The BMS continuously monitors different parameters of the battery such as temperature, voltage, current, and so on, and communicates these parameters to the Electronic Control Unit (ECU) and the Motor Controller Unit (MCU) in the EV (10) using a plurality of protocols including and not limited to a Controller Area Network (CAN) bus protocol which facilitates the communication between the ECU/MCU and other peripheral elements of the EV (10) without the requirement of a host computer.
[0040] The MCU primarily controls/regulates the operation of the electric motor (16) based on the signal transmitted from the vehicle battery, wherein the primary functions of the MCU include starting of the electric motor (16), stopping the electric motor (16), controlling the speed of the electric motor (16), enabling the vehicle to move in the reverse direction and protect the electric motor (16) from premature wear and tear. The primary function of the electric motor (16) is to convert electrical energy into mechanical energy, wherein the converted mechanical energy is subsequently transferred to the transmission system of the EV (10) to facilitate movement of the EV (10). Additionally, the electric motor (16) also acts as a generator during regenerative braking (i.e., kinetic energy generated during vehicle braking/deceleration is converted into potential energy and stored in the battery of the EV). The types of motors generally employed in EVs (10) include, but are not limited to DC series motor, Brushless DC motor (also known as BLDC motors), Permanent Magnet Synchronous Motor (PMSM), Three Phase AC Induction Motors, and Switched Reluctance Motors (SRM).
[0041] The transmission system (18) of the EV (10) facilitates the transfer of the generated mechanical energy by the electric motor (16) to the wheels (22a, 22b) of the EV (10). Generally, the transmission systems (18) used in EVs (10) include single speed transmission system and multi-speed (i.e., two-speed) transmission system, wherein the single speed transmission system comprises a single gear pair whereby the EV (10) is maintained at a constant speed. However, the multi-speed/two-speed transmission system comprises a compound planetary gear system with a double pinion planetary gear set and a single pinion planetary gear set thereby resulting in two different gear ratios which facilitates higher torque and vehicle speed.
[0042] In one embodiment, all data pertaining to the EV (10) and/or charging infrastructure (20) are collected and processed using a remote server (known as cloud) (24), wherein the processed data is indicated to the rider/driver of the EV (10) through a display unit present in the dashboard (26) of the EV (10). In an embodiment, the display unit may be an interactive display unit. In another embodiment, the display unit may be a non-interactive display unit.
[0043] Embodiments explained herein relate to vehicle location tracking devices. In particular, the present disclosure relates to a system for tracking location of a vehicle in both horizontal and vertical spaces.
[0044] In an aspect, the present disclosure describes a system for locating a vehicle. The system includes a keyless fob device communicatively connected to a vehicle. Each of the keyless fob device and the vehicle includes at least one altitude sensor for continuously measuring altitude of the vehicle. The system includes a hand-held device communicatively connected to the keyless fob device and the vehicle. The hand-held device is configured to provide real-time altitude of the vehicle to a user.
[0045] Various embodiments of the present disclosure will be explained in detail with respect to FIGs. 2A-6.
[0046] FIG. 2A illustrates a block diagram of a system (100) for locating a vehicle (102), according to embodiments of the present disclosure.
[0047] With reference to FIG. 2A, the system (100) may include a keyless fob device (104) communicatively connected to the vehicle (102). The keyless fob device (104) may be communicatively connected to the vehicle (102) via a wireless network. In an embodiment, each of the keyless fob device (104) and the vehicle (102) may include at least one altitude sensor for continuously measuring altitude of the vehicle (102). The altitude sensor may be, for example a barometric pressure sensor. In an embodiment, the continuously measured altitude of the vehicle (102) may be stored in a remote server.
[0048] In an embodiment, the altitude sensor associated with the vehicle (102) may be configured to measure a dynamic altitude when the vehicle (102) is in motion. In an embodiment, the altitude sensor associated with the vehicle (102) may be configured to measure a static altitude when the vehicle (102) is stationary. In an embodiment, the dynamic altitude and the static altitude may be stored in the remote server.
[0049] In an embodiment, the system (100) may include a hand-held device (106). The hand-held device (106) may include, but not be limited to, a mobile device, a smartphone, virtual reality (VR) devices, augmented reality (AR) devices, wearable devices (smartwatch, smart ring), and so on. Additionally, input devices for receiving input from the user such as a touch pad, touch-enabled screen, electronic pen, and the like may be used. A person of ordinary skill in the art will appreciate that the hand-held device (106) may not be restricted to the mentioned devices and various other devices may be used.
[0050] The hand-held device (106) may be communicatively connected to the keyless fob device (104) and the vehicle (102). In an embodiment, the hand-held device (106) may be communicatively connected to the keyless fob device (104) and the vehicle (102) via the wireless network. In an embodiment, the hand-held device (106) may be communicatively connected to the vehicle (102) via a long-range communication network, for example, a Global System for Mobile Communications (GSM). In an embodiment, the hand-held device (106) may be connected to the keyless fob device (104) locally over a short-range communication network, for example, but are not limited to, Bluetooth (BLE), Long Range Wide Area Network (LoRa-WAN), Wireless Smart Ubiquitous Network (Wi-SUN), Ultra High Frequency Radio Frequency (UHF RF), Ultra-Wide Band (UWB) RF, and the like. In an embodiment, the hand-held device (106) may be simultaneously communicated with the keyless fob device (104) and the vehicle (102). The hand-held device (106) may be configured to provide real-time altitude of the vehicle (102) to a user.
[0051] In an embodiment, the hand-held device (106) may include a primary processor configured to compare the static altitude with the real-time altitude of the vehicle (102), and provide an updated altitude value of the vehicle (102) to the user.
[0052] In an embodiment, the keyless fob device (104) may include a secondary processor configured to compare the static altitude with the real-time altitude of the vehicle (102), and provide the updated altitude value of the vehicle (102) to the user, when the hand-held device (106) is inactive. The updated altitude value of the vehicle (102) may be notified to the user, via the hand-held device (106) or the keyless fob device (104), to indicate if the vehicle (102) is located on at least one of a same level, an upper level, or a lower level of a plurality of structures. The plurality of structures may include, without limitations, buildings, mountains, roads, etc. The building may be, for example, but are not limited to, multistorey building, multistorey parking lot, multistorey apartment, and the like.
[0053] In an embodiment, the vehicle (102) may include a tertiary processor and a sensor such as, but not limited to, a motion and barometric pressure sensor configured to determine a current state of the vehicle (102) and the altitude of the vehicle (102), when the vehicle (102) transitions from motion to stationary. The vehicle (102) may include navigation systems, for example, a Global Positioning System (GPS) for determining the current location of the vehicle (102).
[0054] FIG. 2B illustrates a schematic view of the keyless fob device (104) included in the system (100) as illustrated in FIG. 2A, according to embodiments of the present disclosure.
[0055] With reference to FIG. 2B, the keyless fob device (104) may include a plurality of control keys and indicators such as a location indicator (202). The plurality of control keys may include, but are not limited to, a find-my-vehicle button (204), a lock button (206a), an unlock button (206b), a boot-open button (208), and the like.
[0056] In an embodiment, the location indicator (202) may include one or more navigation indicators, for example, a downward indicator, an upward indicator, and a neutral indicator to indicate if the vehicle (102) is located on the lower level, or the upper level, or the same level of the structure, for example, building, respectively.
[0057] In an embodiment, the find-my-vehicle button (204) may be pressed to acquire latest altitude of the vehicle (102) from the hand-held device (106). The latest altitude of the vehicle (102) is sent by the vehicle (102) to the hand-held device (106).
[0058] In an embodiment, the lock button (206a) and the unlock button (206b) may be utilized for controlling a central locking system of the vehicle (102). In an embodiment, the boot-open button (208) may be utilized for remotely opening a trunk or a boot of the vehicle (102). When the boot-open button (208) is pressed, the keyless fob device (104) may transmit a signal to the vehicle (102) to release a latch on the boot, allowing the boot to be easily opened without using a physical key or an interior release mechanism.
[0059] FIG. 3 illustrates a flow chart (300) depicting an example scenario where the vehicle (102) is locked without fob-in boot check, according to embodiments of the present disclosure.
[0060] With reference to FIG. 3, at 302, considering a scenario where the vehicle (102) is locked by pressing the lock button (206a) on the keyless fob device (104). At 304, the vehicle (102) may read and record the altitude or barometric pressure of the vehicle (102) at the time of locking the vehicle (102). The altitude or barometric pressure of the vehicle (102) may be measured using the altitude sensor associated with the vehicle (102). At 306, the keyless fob device (104) may read and record the altitude or barometric pressure of the vehicle (102) through the altitude sensor associated with the keyless fob device (104).
[0061] At 308, considering the scenario where the vehicle (102) is locked and the keyless fob device (104) is carried away by the user. At 310, the vehicle (102) may read and store the altitude or barometric pressure value of the vehicle (102) at a fixed predefined interval of 5 minutes to 15 minutes. At 312, the change in the altitude or barometric pressure value may be sent to the keyless fob device (104) via the hand-held device (106) over a wireless communication network if the altitude or barometric pressure value increases more than a predetermined percentage.
[0062] FIG. 4 illustrates a flow chart (400) depicting an example scenario where the vehicle (102) is locked with fob-in boot check, according to embodiments of the present disclosure.
[0063] The system (100) may perform real-time altitude compensation between the vehicle (102) and the keyless fob device (104) using the hand-held device (106). The hand-held device (106) may be connected to the vehicle (102) over, for example, GSM, and connected to the keyless fob device (104) locally over, for example, BLE. Therefore, when an attempt to find the vehicle altitude is made by the user over the keyless fob device (104), the system (100) may trigger the hand-held device (106) to send an altitude capture request to the vehicle (102). The vehicle (102) may capture real-time altitude value from the altitude sensor associated with the vehicle (102) and share the real-time altitude value with the keyless fob device (104) via the hand-held device (106). The keyless fob device (104) may compare the real-time altitude value with the altitude value acquired from the vehicle (102), and accordingly indicate the location, i.e., either up or down, of the vehicle to the user via the location indicator (202) mounted on the keyless fob device (104).
[0064] With reference to FIG. 4, at 402, considering the scenario where the vehicle (102) is locked by pressing the lock button (206a) on the keyless fob device (104). At 404, the vehicle (102) may trigger a tuned Low Frequency (LF) antenna mounted in the boot of the vehicle (102), and determine if the keyless fob device (104) is available in the boot. At 406, if the keyless fob device (104) is available in the boot, the vehicle (102) may notify the user that the keyless fob device (104) is present in the boot via an indication on a dashboard.
[0065] At 408, if the keyless fob device (104) is not available in the boot, only then the vehicle is allowed to lock itself and then the vehicle (102) may read and record the altitude or barometric pressure of the vehicle (102) using the altitude sensor associated with the vehicle (102). At 410, the keyless fob device (104) may read and record the altitude or barometric pressure of the vehicle (102) through the altitude sensor associated with the keyless fob device (104).
[0066] At 412, considering the scenario where the vehicle (102) is locked and the keyless fob device (104) is carried away by the user. At 414, the vehicle (102) may read and store the altitude or barometric pressure value of the vehicle (102) at a fixed predefined interval of 5 minutes to 15 minutes. At 416, the change in the altitude or barometric pressure value may be sent to the keyless fob device (104) via the hand-held device (106) over mobile data, if the altitude or barometric pressure value increases more than a predetermined percentage.
[0067] FIG. 5 illustrates a flow chart (500) depicting an example scenario of locating the vehicle (102) with the keyless fob device (104) and the hand-held device (106), according to embodiments of the present disclosure.
[0068] With reference to FIG. 5, at 502, the find-my-vehicle button (204) may be pressed on the keyless fob device (104). At 504, the keyless fob device (104) may acquire the latest altitude or barometric pressure value of the vehicle (102) from the hand-held device (106). The hand-held device (106) may receive the latest altitude or barometric pressure value of the vehicle (102) from the vehicle (102). At 506, the keyless fob device (104) may determine that the latest altitude or barometric pressure value is available. At 508, the keyless fob device (104) may compare the latest altitude or barometric pressure value and the altitude or barometric pressure value received from the vehicle (102) to estimate the vertical distance between the vehicle (102) and the keyless fob device (104).
[0069] At 510, the keyless fob device (104) may determine a level difference between the vehicle (102) and the keyless fob device (104) based on the vertical distance between the vehicle (102) and the keyless fob device (104). Further, the level difference, i.e., the upper level or the lower level, may be indicated by the location indicator (202) on the keyless fob device (104) or on the hand-held device (106).
[0070] At 512, if the vehicle (102) and the keyless fob device (104) are on the same level of, for example, the building, indicator lamps on the vehicle (102) may be turned on over data wireless network infrastructure to indicate the location of the vehicle (102). At 514, the user may press the unlock button (206b) on the vehicle (102) and the vehicle (102) may trigger LF field. At 516, the keyless fob device (104) may detect if the LF field is within a predefined range, for example, 1-1.5 meter of the vehicle (102) and transmit a signal over the wireless network to the vehicle (102). At 518, the vehicle (102) may receive the signal over the wireless network and unlock itself after validation.
[0071] FIG. 6 illustrates a flow chart (600) depicting an example scenario of locating the vehicle (102) with the keyless fob device (104), according to embodiments of the present disclosure.
[0072] With reference to FIG. 6, at 602, the find-my-vehicle button (204) may be pressed on the keyless fob device (104). At 604, the keyless fob device (104) may retrieve the altitude or barometric pressure value obtained while locking the vehicle (102) using the lock button (206a). At 606, the keyless fob device (104) may compare the latest altitude or barometric pressure value and the retrieved altitude or barometric pressure value to estimate the vertical distance between the vehicle (102) and the keyless fob device (104).
[0073] At 608, the keyless fob device (104) may determine the level difference between the vehicle (102) and the keyless fob device (104) based on the vertical distance between the vehicle (102) and the keyless fob device (104). Further, the level difference, i.e., the upper level or the lower level, may be indicated by the location indicator (202) on the keyless fob device (104).
[0074] At 610, if the vehicle (102) and the keyless fob device (104) are on the same level , the indicator lamps on the vehicle (102) may be turned on over the wireless network to indicate the location of the vehicle (102). At 612, the user may press the unlock button (206b) on the vehicle (102) and the vehicle (102) may trigger the LF field. At 614, the keyless fob device (104) may detect if the LF field is within the predefined range, for example, 1-1.5 meter of the vehicle (102) and transmit the signal over the wireless network to the vehicle (102). At 616, the vehicle (102) may receive the signal over the wireless network and unlock itself after validation.
[0075] Furthermore, embodiments of the disclosed devices and systems may be readily implemented, fully or partially, in software using, for example, object or object-oriented software development environments that provide portable source code that can be used on a variety of computer platforms. Alternatively, embodiments of the disclosed methods, processes, modules, devices, systems, and computer program product can be implemented partially or fully in hardware using, for example, standard logic circuits or a very-large-scale integration (VLSI) design. Other hardware or software can be used to implement embodiments depending on the speed and/or efficiency requirements of the systems, the particular function, and/or particular software or hardware system, microprocessor, or microcomputer being utilized.
[0076] In this application, unless specifically stated otherwise, the use of the singular includes the plural and the use of “or” means “and/or.” Furthermore, use of the terms “including” or “having” is not limiting. Any range described herein will be understood to include the endpoints and all values between the endpoints. Features of the disclosed embodiments may be combined, rearranged, omitted, etc., within the scope of the invention to produce additional embodiments. Furthermore, certain features may sometimes be used to advantage without a corresponding use of other features.
[0077] While the foregoing describes various embodiments of the disclosure, other and further embodiments of the disclosure may be devised without departing from the basic scope thereof. The scope of the disclosure is determined by the claims that follow. The disclosure is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the present disclosure when combined with information and knowledge available to the person having ordinary skill in the art.

ADVANTAGES OF THE PRESENT DISCLOSURE
[0078] The present disclosure provides a system for efficiently locating a vehicle in both horizontal and vertical spaces.
[0079] The present disclosure provides a system in which a hand-held device simultaneously communicates with a keyless fob device and a vehicle to improve the accuracy of vehicle location tracking.
[0080] The present disclosure provides a system that accurately estimates a vertical distance of a vehicle from a keyless fob device and/or a hand-held device.
[0081] The present disclosure provides a system that captures real-time atmospheric pressure readings from a vehicle and subsequently compares them with most recent live pressure readings from a keyless fob device to accurately locate the vehicle.
[0082] The present disclosure minimizes time and effort required for accurately tracking the location of a stationary vehicle.

List of References:
System (100)
Vehicle (102)
Keyless Fob Device (104)
Hand-held Device (106)
Location Indicator (202)
Find-my-vehicle Button (204)
Lock Button (206a)
Unlock Button (206b)
Boot-open Button (208)
, Claims:1. A system (100) for locating a vehicle (102), comprising:
a keyless fob device (104) communicatively connected to a vehicle (102), wherein each of the keyless fob device (104) and the vehicle (102) comprises at least one altitude sensor for continuously measuring altitude of the vehicle (102); and
a hand-held device (106) communicatively connected to the keyless fob device (104) and the vehicle (102), wherein the hand-held device (106) is configured to provide real-time altitude of the vehicle (102) to a user.

2. The system (100) as claimed in claim 1, wherein the continuously measured altitude of the vehicle (102) is stored in a remote server.

3. The system (100) as claimed in claim 1, wherein the keyless fob device (104) is communicatively connected to the vehicle (102) via a wireless network, and wherein the hand-held device (106) is communicatively connected to the keyless fob device (104) and the vehicle (102) via the wireless network.

4. The system (100) as claimed in claim 1, wherein the at least one altitude sensor associated with the vehicle (102) is configured to measure a dynamic altitude when the vehicle (102) is in motion, and a static altitude when the vehicle (102) is stationary, and wherein the dynamic altitude and the static altitude are stored in a remote server.

5. The system (100) as claimed in claim 4, wherein the hand-held device (106) comprises a primary processor configured to compare the static altitude with the real-time altitude of the vehicle (102), and provide an updated altitude value of the vehicle (102).

6. The system (100) as claimed in claim 4, wherein the keyless fob device (104) comprises a secondary processor configured to compare the static altitude with the real-time altitude of the vehicle (102), and provide an updated altitude value of the vehicle (102), when the hand-held device (106) is inactive.

7. The system (100) as claimed in claim 5, wherein the updated altitude value of the vehicle (102) is notified to the user, via the hand-held device (106) or the keyless fob device (104), to indicate if the vehicle (102) is located on at least one of: a same level, an upper level, or a lower level.

8. The system (100) as claimed in claim 4, wherein the vehicle (102) comprises a sensor and a tertiary processor configured to determine a current location of the vehicle (102) and the altitude of the vehicle (102), when the vehicle (102) transitions from motion to stationary.