System and method for a key fob with extended range
The vehicle key fob system extends communication range by using a mobile device and remote server to relay commands, addressing the limitations of conventional key fobs and smartphone solutions, ensuring intuitive and efficient vehicle control.
Patent Information
- Application Number
- DE102016118359
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2015-09-30
- Filing Date
- 2016-09-28
- Publication Date
- 2024-12-19
- Estimated Expiration
- 2036-09-28
AI Technical Summary
Conventional remote keyless systems for vehicles have limited operating ranges, requiring users to be within a predetermined distance from the vehicle to issue commands and receive confirmation, which can be hindered by obstacles and location, and existing smartphone solutions are cumbersome with multiple steps for command entry.
A vehicle key fob system that extends communication range by using a mobile device and a remote server to relay commands, with a dedicated button on the key fob to initiate the extended transmission path, ensuring intuitive and convenient vehicle control.
The system provides an extended communication range beyond the typical limits of key fobs, maintaining the simplicity of physical button inputs while allowing commands to be sent via cellular, satellite, and wireless Ethernet networks, ensuring reliable and efficient vehicle control.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNICAL AREA
[0001] This application generally concerns keyless remote control of vehicle functions and, in particular, electronic key fob devices for controlling functions in a motor vehicle or other vehicle. BACKGROUND
[0002] Many vehicles feature a remote keyless entry (RCE) system to allow access to the vehicle or control of vehicle functions without the use of a traditional key or other mechanical device, or by otherwise making physical contact with the vehicle. Typically, remote keyless entry systems include a remote control with buttons or switches to allow control of vehicle functions. The remote control may be in the form of a separate, independent key fob or a key fob integrated into the vehicle key handle.
[0003] German patent application EP 1 216 900 B1 describes a vehicle key fob comprising a module for wireless communication with an associated mobile device, a dedicated input device for initiating a mobile communication mode, multiple input devices for commanding an associated vehicle to execute a user-selected function, and a processor designed to send a command signal to the mobile device for executing the user-selected function after receiving an input at the dedicated input device. Further relevant prior art relating to the background of the invention is provided in German patent applications EP 2 048 627 A2, DE 10 2008 039 156 A1, and DE 10 2012 111 316 A1.
[0004] Conventional remote keyless entry (RCE) systems typically feature a keyless remote entry (CRE) system to enable keyless remote control of the vehicle doors, including, for example, locking and unlocking the door locks or other electronic locks in the vehicle, opening and / or closing the trunk, tailgate, sliding doors, or other electronically operated doors. Typically, the key fob has a lock button to lock all vehicle doors and an unlock button to unlock one or more of the vehicle doors. In some cases, the key fob also has a button to release the trunk or tailgate. Many existing RCE systems are designed to control additional vehicle functions by entering a predefined key sequence.For example, pressing the unlock button once will only unlock the driver's side door, while pressing the unlock button twice will unlock all vehicle doors.
[0005] In some cases, the RKE system also allows the vehicle windows and / or roof to be opened and / or closed (e.g., glass sunroof, sunroof, convertible top, etc.). For example, the windows and / or roof can be opened by entering a predefined sequence of keystrokes on the key fob (e.g., holding the unlock button for a specified period). In other cases, the windows and / or roof can be automatically closed whenever the vehicle doors are locked using the key fob. Conventional remote keyless entry (RKI) systems may also include a keyless remote ignition (RKI) system to enable keyless remote starting of the vehicle's internal combustion engine. In these cases, the key fob has an ignition button for starting the internal combustion engine.Additionally, remote keyless entry systems typically feature a red panic button to activate the vehicle's alarm system.
[0006] One disadvantage of existing remote keyless entry systems is the limited operating range of the key fob or other remote control. Typically, the key fob must be within a predetermined distance (for example, 200 meters) of the vehicle to issue commands using the remote keyless system. Furthermore, the actual operating range of the key fob may be less than the predetermined distance due to various factors, including location, altitude, intervening structures, and obstructing obstacles. In cases where the key fob's operating range is less than the user's current distance from the vehicle, the user must move closer to use the key fob. The user may also need to move closer to the vehicle to receive confirmation that a requested action has been completed.For example, the vehicle may flash its headlights and / or sound its horn to confirm the completion of a locking command, but the user will not receive this confirmation if the vehicle is not within a visible and / or audible range.
[0007] One existing solution for extending the communication range of commercially available key fob systems involves a smartphone-enabled vehicle connectivity platform that uses Bluetooth or near-field communication (NFC) technology to create a communication path between the vehicle and a smartphone or other mobile device. This platform turns the mobile device into a virtual key fob, allowing users to control various vehicle features through a graphical user interface (GUI) presented on the mobile device, rather than entering similar commands into the physical key fob or using the ignition key. However, as is the case with many mobile applications, entering a command using the GUI may require several steps (i.e., icon selections) in addition to selecting the intended command.For example, the user may need to turn on, activate, and / or unlock the mobile device, open the appropriate application, and log in to a customer account before the GUI for entering vehicle commands is presented. In contrast, the key fob features dedicated buttons for quick, intuitive input of vehicle commands (for example, a lock button to lock doors, an unlock button to unlock one or more doors, etc.).
[0008] Accordingly, there is still a need in the field for a vehicle key fob device that has a greater communication range and enables quick and efficient input of vehicle commands. SUMMARY
[0009] The invention is intended to solve the aforementioned and other problems by providing systems and methods for extending the communication range of a vehicle key fob, which, among other things, (1) provides an extended-range transmission path via which vehicle commands entered by the user are sent from the key fob to a mobile device paired with the key fob, wherein the mobile device sends the command to a server which sends the command to the vehicle associated with the key fob, and (2) provides a dedicated button on the vehicle key fob for initializing the extended-range transmission path.
[0010] For example, one embodiment provides a vehicle key fob comprising: a module for wireless communication with an associated mobile device, a dedicated input device for initiating a mobile communication mode, multiple input devices for commanding an associated vehicle to perform a user-selected function, and a processor designed to send a command signal to the mobile device to perform the user-selected function upon receiving an input at the dedicated input device.
[0011] As will be clear, this disclosure is defined by the accompanying claims. The description summarizes aspects of the embodiments and should not be used to limit the claims. Other implementations are considered in accordance with the techniques described herein, as those skilled in the art will understand upon reviewing the following drawings and detailed description, and these implementations are intended to be within the scope of protection of this application. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] For a better understanding of the invention, reference is made to the embodiments illustrated in the following drawings. The components in the drawings are not necessarily to scale, and relevant elements may be omitted, or proportions may in some cases have been exaggerated to emphasize and clearly demonstrate the novel features described herein. Additionally, system components can be arranged in various ways, as is known in the field. Furthermore, in the drawings, the same reference numerals denote corresponding parts in the multiple views.
[0013] They show: Fig. 1. An example wireless system for increasing the communication range of a vehicle key fob according to certain embodiments, Fig. 2 a block diagram of an example computing device, which is contained in one or more components of the wireless system Fig. 1 is included, according to certain embodiments, Fig. 3. A flowchart with example operations performed using the system from Fig. 1 can be implemented according to certain embodiments, Fig. 4. A block diagram of an example vehicle computer system, which is installed in the vehicle. Fig. 1 is included, according to certain embodiments and Fig. 5 a flowchart of an exemplary method for increasing the communication range of a vehicle key fob according to certain embodiments. DETAILED DESCRIPTION AS AN EXAMPLE OF SERVANT EXECUTION FORMS
[0014] Although the invention can be implemented in various forms, some exemplary and non-limiting embodiments are shown in the drawings and are described below, it being understood that the present disclosure is to be regarded as illustrating the invention by way of example and is not intended to limit the invention to the specific embodiments explained.
[0015] In this application, the disjunctive form is intended to include the conjunctive form. The use of definite or indefinite articles is not intended to indicate cardinality. In particular, a reference to "the" object or "a" object is also intended to refer to one of possibly several such objects.
[0016] Fig. Figure 1 shows an example wireless system 100 designed to increase the operating range of a key fob device 102 for controlling various operations or functions of a vehicle 104 associated with the key fob device 102, according to embodiments.
[0017] Various components of the system 100 can be implemented using software executable by one or more servers or computers, such as a computing device 200 with a processor 202 and a memory 204, as in Fig. Figure 2 is shown, which is described in further detail below. For example, in Fig. Figure 3 illustrates an embodiment of a process 300 for increasing the communication range of a vehicle key fob device according to one or more principles of the invention. The process 300 can be implemented using the system 100 or, in particular, through interactions between different components of the system 100, facilitated by software running on one or more computer processors (not shown) associated with the components. In the following paragraphs, the process 300 is described in conjunction with a description of the various components of the system 100.
[0018] The vehicle key fob device 102 (hereinafter also referred to as the "key fob") is designed to provide a user with keyless remote control of various operations or functions of the vehicle 104, including locking or unlocking door locks or other electronic locks of the vehicle 104, opening and / or closing the trunk, tailgate, a sliding door or any other electronically operated door of the vehicle 104, opening and / or closing a window or the roof of the vehicle 104, starting the engine of the vehicle 104 and / or activating an alarm system of the vehicle 104, but not limited to these. The key fob device 102 can be pre-configured to allow direct control of these operations of the vehicle 104 by the vehicle manufacturer or an entity associated with it.It will be understood that other vehicle functions may be controllable by the key fob 102, and the present disclosure is intended to cover any and all of these key fob operations.
[0019] As in Fig. As shown in Figure 1, the key fob 102 has several vehicle input devices 106 (also referred to here as "vehicle buttons") that can be operated by the user to send operating commands to the vehicle 104. According to embodiments, each vehicle input device 106 can be assigned to at least one vehicle function. For example, according to the embodiment described, the vehicle input devices 106 include a door locking input device 106a for locking all vehicle doors, a door unlocking input device 106b for unlocking one or more of the vehicle doors, a trunk release input device 106c for releasing the trunk or tailgate, and a panic input device 106d for activating the vehicle alarm system.The vehicle input devices 106 can be of any type of input device, including buttons or pushbuttons, sliders, switches, knobs, dials and / or touch input devices, without limitation. According to the described embodiment, the vehicle input devices 106 are pushbuttons that can be selectively pressed by the user to activate the execution of the associated one or more vehicle functions.
[0020] According to embodiments, at least some vehicle functions are executed upon receipt of a single user input at the vehicle input device 106 for controlling the vehicle function, while other vehicle functions can be executed upon receipt of a specific sequence or combination of inputs at one or more of the vehicle input devices 106. These combination inputs can include, for example, sequential operation of two or more vehicle input devices 106 and / or repeated operation of a single vehicle input device 106, such as double-clicking the input device 106 or holding down the input device 106 for a predetermined period of time. For example, the trunk release input device 106c may need to be double-clicked or held down to release the trunk.In another example, a single click of the unlocking input device 106b can only unlock the driver's side door, while a double click of the unlocking input device 106b can unlock all vehicle doors.
[0021] As in Fig. As shown in Figure 1, the wireless system 100 further comprises a mobile device 108, which is paired with the key fob 102 by the vehicle 104 using known wireless pairing techniques, for example, by exchanging security codes stored in a memory (not shown) of the key fob 102. The mobile device 108 can communicate with the key fob 102 using Bluetooth, infrared, radio frequency identification (RFID), near field communication (NFC), or another short-range wireless communication technology.The mobile device 108 can be any type of portable electronic device, including, for example, a smartphone or other mobile phone, a tablet or tablet personal computer, a personal digital assistant (PDA), a smartwatch or other portable device and the like.
[0022] According to some embodiments, the mobile device 108 includes a software application 110 designed to transmit vehicle commands received from the key fob 102 to a remote server 112. The software application 110 (also referred to here as the "vehicle application") may be a mobile client developed and / or assigned to the vehicle manufacturer, and it may be specifically designed for the vehicle 104. In some cases, the vehicle application 110 is specifically designed for pairing the key fob 102 with the mobile device 108 and for extending the communication range of the key fob 102, as described in more detail below. In other cases, the vehicle application 110 also provides a graphical user interface for accessing a remote keyless entry system (CIS) of the vehicle 104.In other cases, the vehicle application 110 additionally provides diagnostic and / or operational information about the vehicle 104. According to embodiments, the entire vehicle application 110 or a part thereof can be stored in a memory (not shown) of the mobile device 108.
[0023] As in Fig. As shown in Figure 1, the remote server 112 can be communicatively coupled with the mobile device 108 and the vehicle control system (VCS) 114 of the vehicle 104 via a wireless communication network, such as a WiFi network or other wireless Ethernet, a cellular network, and / or a satellite. According to embodiments, the remote server 112 can be a cloud computing device or can be included in a cloud computing network, both of which can be controlled and / or assigned to the vehicle manufacturer. According to some embodiments, a secure wireless communication channel can be pre-established between the VCS 114 and the remote server 112 to enable direct communication between the vehicle 104 and the server 112 without requiring pairing or authorization prior to each key fob operation. The secure communication channel can be established by or under the supervision of the vehicle manufacturer.
[0024] The remote server 112 can include a vehicle database (not shown) for storing vehicle information received from the vehicle control system (VCS) 114 of the vehicle 104, as well as other information associated with the vehicle 104, including, for example, global positioning system (GPS) data for the vehicle 104 received from a GPS server, a charging profile for the vehicle 104, a key profile for each key associated with the vehicle 104, fuel economy and driving habits associated with each key, etc. According to some embodiments, part of the vehicle application 110 resides on the remote server 112. According to some embodiments, the remote server 112 supplies images and / or information for the implementation of the vehicle application 110 on the mobile device 108.The remote server 112 can also store one or more software applications designed to interact with the vehicle application 110 and the VCS 114, including receiving commands from the vehicle application 110 and sending them to the VCS 114, as explained in further detail below.
[0025] During normal operation, the key fob 102 must be within a predetermined distance d of the vehicle 104 to wirelessly transmit commands to the vehicle 104. For example, in some cases, the predetermined or manufacturer-specified distance d may be approximately 200 meters. As will be understood, the distance d may be affected by geographical, physical, and / or other factors, including, for example, the presence of significant obstacles between the key fob 102 and the vehicle 104. In such cases, the actual operating range of the key fob 102 may be less than the predetermined distance d. Furthermore, in some cases, the operating range of the key fob 102 may be less than the distance between the user and the vehicle 104.To address these and other concerns, the wireless system 100 is designed to extend the operating range of the key fob 102 beyond the specified distance d by providing an extended-range transmission path 115 (also referred to here as the "extended transmission path") that sends vehicle commands from the key fob 102 to the vehicle 104 via the mobile device 108 and the remote server 112.
[0026] In particular, the key fob 102 indicates, as in Fig. Figure 1 shows a mobile communication input device 116 designed to initiate the extended transmission path 115 between the key fob 102 and the vehicle 104 or a mobile communication mode of the system 100. According to embodiments, the mobile communication input device 116 is a dedicated input device to alert the mobile device 108 so that it expects a vehicle command from the key fob 102. In some cases, the mobile communication input device 116 may be located adjacent to the vehicle input devices 106 on the key fob 102, as shown in Figure 1. Fig. Figure 1 is shown. In other cases, the mobile connection input device 116 can be located on any other side of the key fob 102, including, for example, on the left, right, or rear of the key fob 102. According to the described embodiment, the mobile connection input device 116 (also referred to here as the "mobile button") is shown as a push button that can be pressed down to activate the mobile connection mode of the key fob 102. According to other embodiments, the mobile connection input device 116 can be any other type of input device, including, but not limited to, a switch, a button, a slider, or a dial.
[0027] According to some embodiments, the key fob 102 further comprises a biometric security device (not shown) for authenticating the user's biometric identification prior to activating the mobile connection or otherwise initializing the extended transmission path 115. For example, the biometric security device may include a fingerprint scanning device and a memory for storing one or more authorized fingerprints for comparison with a fingerprint scan. The biometric security device may be integrated into the mobile connection input device 116 or embedded at another location within the key fob 102.
[0028] With reference to Fig. Regarding step 3 and process 300, it should be noted that after the user selects the mobile button 116 in step 302, the key fob 102 sends an alert signal to the mobile device 108 in step 304 and may wait for one or more further commands from the user in step 306. In step 308, after receiving the alert signal, the mobile device 108 and / or the vehicle application 110 enters a command-waiting mode or otherwise waits for the key fob 102 to send a signal instructing the vehicle 104 to perform a specified operation. Before receiving the alert signal, the mobile device 108 may have been in a standby mode, as shown by step 310.The command anticipation mode can cause the mobile device 108 and / or the vehicle application 110 to automatically send a vehicle command received from the key fob 102 to the remote server 112 within a specified time period after the mobile button 116 has been selected.
[0029] As in Fig. As shown in Figure 3, a vehicle command can be entered into the key fob 102 in step 312 after the user selects one or more vehicle buttons 106. In step 314, the key fob 102 sends a command signal corresponding to the received vehicle command to the mobile device 108. In step 316, the mobile device 108 and / or the vehicle application 110 sends the command signal to the remote server 112. In step 318, the remote server 112 sends the received command signal to the vehicle control system (VCS) 114 of the vehicle 104. In step 320, a telematics control unit (TCU) of the VCS 114 receives the command signal, and in step 322, a suitable unit of the VCS 114 performs the action required by the command signal or executes the command in another way, thus completing the extended transmission path 115. After the command has been executed, the TCU of vehicle 104 sends a confirmation signal to the remote server 112 in step 324.In step 326, the remote server 112 forwards the confirmation signal to the mobile device 108, which in turn sends the confirmation signal to the key fob 102 in step 328 and returns to standby mode in step 330.
[0030] As in Fig. As shown in Figure 1, the key fob 102 has one or more output devices 117 for providing a visual, audible, and / or haptic output in response to certain inputs received by the key fob 102 and for indicating a current stage or step of the process 300. For example, an initial output can be provided after receiving a user selection from the mobile keypad 116 at the key fob 102 (e.g., step 302). A second output can be provided after receiving a user selection from one or more vehicle input devices 106 at the key fob 102 (e.g., step 312) and while the corresponding vehicle command is being sent to or executed by the vehicle 104 (e.g., steps 314–322).Furthermore, a third output can be provided after receiving confirmation from vehicle 104 that the vehicle command has been executed (for example, steps 324-328).
[0031] According to some embodiments, the one or more output devices 117 can be configured to provide a different visual output or visual indication depending on the input received at the key fob 102. In such cases, the output devices 117 can include light-emitting diodes (LEDs), each LED being configured to emit light of a different color to represent a different input.For example, according to the described embodiment, the key fob 102 comprises a first output device 117a that emits light of a first color (e.g., blue) in response to a user selection of the mobile keypad 116 (in step 332), a second output device 117b that emits light of a second color (e.g., yellow) in response to a user input of a vehicle command via at least one vehicle input device 106 (in step 334), and a third output device 117c that emits light of a third color (e.g., green) after receiving confirmation that the vehicle command has been executed (in step 336). As in . Fig. As shown in Figure 1, the key fob 102 may further have a fourth output device 117d which, after receiving a non-execution signal indicating that the vehicle command could not be executed and / or that the vehicle command could not be sent to the mobile device 108, emits light of a fourth color (for example, red).
[0032] In some cases, the lights with a third and a fourth color, for example, may remain activated only for a predetermined period to conserve energy. Similarly, in some cases, the light with the second color may remain activated until the confirmation or non-execution signal is received from the mobile device 108. To indicate that the wireless system 100 is processing the user command, the light with the second color may flash or blink on and off until the confirmation or non-execution signal is received.
[0033] According to some embodiments, the process 300 is further designed to include a timeout feature for the case where a vehicle command is not entered after receiving a user selection from the mobile keypad 116. In such cases, the key fob 102 switches off the light of the first color on the key fob 102 in step 338 if no command is received via the key fob 102 within a predetermined period. Likewise, the mobile device 108 returns to standby mode in step 340 if no command is received within a predetermined period.
[0034] According to other embodiments, the one or more output devices 117 comprise at least one haptic device (not shown) in the form of an actuator or an electromechanical motor that vibrates, buzzes, or otherwise provides a haptic cue or output in response to inputs received at the key fob 102. In some cases, the key fob 102 may have a single haptic device that outputs a different type of haptic cue or a combination of haptic cues for each type of input. For example, the haptic device may output a single buzz, two or more buzzes in rapid succession, two or more buzzes in delayed succession, or another combination of haptic cues.According to one embodiment, the one or more output devices 117 comprise at least one LED and at least one haptic device, and the output devices 117 can be designed to output at least one haptic cue, at least one visual cue, or a combination of both for each input received at the key fob 102.
[0035] According to one embodiment, one or more of the output devices 117 on the key fob 102 can be activated in response to an alarm signal issued by the vehicle 104, for example, in response to the activation of an alarm system of the vehicle 104 or another alarm on the vehicle 104. In these cases, the vehicle 104 can be configured to send the alarm signal to the key fob 102 via a reverse of the extended transmission path 115. In particular, the vehicle 104 can send the alarm signal to the server 112, which can then send the alarm signal to the mobile device 108, and the mobile device 108 can send the alarm signal to activate one or more of the output devices 117 on the key fob 102. The one or more output devices 117 can provide light and / or haptic outputs to warn the user of the triggered alarm.
[0036] Fig. Figure 4 shows an example of a vehicle computer system (VCS) 400, which, like the one in Fig. Figure 1 shows how the VCS 114 can be incorporated into the vehicle 104, according to embodiments. The VCS 400 comprises various electronic control units (ECUs) responsible for monitoring and controlling the electrical systems or subsystems of the vehicle 104, as described in more detail below. According to embodiments, the ECUs of the VCS 400 are connected by a vehicle bus 402 (such as a CAN bus) to transmit data to and from the various ECUs, and are also connected to other vehicle and / or auxiliary components that communicate with the VCS 400. Each ECU may, for example, have one or more inputs and outputs for collecting, receiving, and / or transmitting data, a memory for storing the data, and a processor for processing the data and / or generating new information based on it.
[0037] According to the described embodiment, the VCS 400 includes a body control module (BCM) 404 for controlling and monitoring various electronic auxiliary devices in the body of the vehicle 104. In some embodiments, the BCM 404 is an ECU that controls the doors of the vehicle 104, including locking, unlocking, opening, and / or closing them. In some embodiments, the BCM 404 also controls the electrically operated windows, the electrically operated roof (e.g., glass sunroof, sunroof, convertible top, etc.), and the interior lighting of the vehicle 104. The BCM 404 can also control other electronically driven components in the body of the vehicle 104, such as air conditioning units, electrically operated mirrors, and electrically operated seats.In cases where the BCM 404 only controls and monitors the doors of the vehicle 104, the BCM 404 can be referred to as the door control unit (DCU), as will be self-evident. The BCM 404 can be configured to implement vehicle commands received from the key fob 102 relating to the doors, windows, or other body components controlled by the BCM 404.
[0038] As in Fig. As shown in Figure 4, the VCS 400 can further comprise a powertrain control module (PCM) 406 for controlling and monitoring the internal combustion engine and transmission of the vehicle 104. According to some embodiments, the PCM 406 can be divided into two separate ECUs, in particular an internal combustion engine control unit and a transmission control unit. In any case, the PCM 406 can be configured to control the starting and stopping of the internal combustion engine of the vehicle 104, including receiving commands to start the internal combustion engine from the key fob 102.
[0039] As in Fig. As shown in Figure 4, the VCS 400 further comprises a telematics control unit (TCU) 408, which is an ECU to enable the vehicle 104 to connect to various wireless networks, such as GPS, WiFi, cellular, Bluetooth, NFC, RFID, satellite, and / or infrared. According to embodiments, the TCU 408 (also referred to as the "vehicle telematics unit") comprises a wireless communication module 410, which includes one or more antennas, radios, modems, receivers, and / or transmitters (not shown) for connecting to the various wireless networks. For example, the wireless communication module 410 may include a cellular communication unit (not shown) for wireless communication via a cellular network (e.g., GSM, GPRS, LTE, 3G, 4G, CDMA, etc.), an 802.11 network (e.g., WiFi), a WiMAX network, and / or a satellite network.The TCU 408 can also be designed to control the tracking of vehicle 104 using latitude and longitude values obtained from a GPS satellite.
[0040] In some embodiments, the TCU 408 receives external data, including vehicle commands, via the wireless communication module 410 and makes the external data available to a suitable ECU of the VCS 400. For example, if the TCU 408 receives a door locking command, it sends the command to the BCM 404 via the vehicle bus 402. Similarly, if the TCU 408 receives an internal combustion engine start command, it sends the command to the PCM 406 via the vehicle bus 402. In some embodiments, the TCU 408 also receives internal data from other ECUs of the VCS 400 or from a processor (not shown) of the VCS 400, with commands to send the internal data to the remote server 112 or to another component of the wireless system 100.
[0041] The Wireless Communication Module 410 can communicate wirelessly over two or more networks to ensure continuity of network access, for example, if one of the networks fails or is out of range. Furthermore, vehicle commands can be received at various receivers of the Wireless Communication Module 410, depending on the wireless communication technology used to transmit the command. For example, commands and / or data sent from the Key Fob 102 to the vehicle 104 can be received at a Bluetooth receiver (not shown) of the Wireless Communication Module 410. In another example, commands and / or data sent from the remote server 112 to the vehicle 104 can be received at a cellular or Wi-Fi receiver (not shown) of the Wireless Communication Module 410.Similarly, data can be sent from the TCU 408 to the key fob 102 using a Bluetooth transmitter (not shown) contained in the wireless communication module 410, and data can be sent from the TCU 408 to the remote server 112 using a cellular or WiFi transmitter (not shown) contained in the wireless communication module 410. According to embodiments, the VCS 400 can be transparent to the source of the vehicle command or the transmission path used to send the vehicle command to the vehicle 104. For example, the VCS 400 can treat vehicle commands received directly from the key fob 102 no differently than vehicle commands received via transmission path 115.
[0042] The VCS 400 may further include a remote keyless system (RCS) unit 412 for controlling and monitoring remote keyless interactions between the key fob 102 and the vehicle 104. The RCS unit 412 may include a keyless remote entry system and, in some cases, a keyless remote ignition system. In the latter case, the RCS unit 412 may also be referred to as a "passive entry passive start (PEPS) system." According to some embodiments, the RCS unit 412 is a separate, standalone ECU that is connected to the vehicle 104's BCM 404, PCM 406, TCU 408, and other ECUs 414 via the vehicle bus 402 to perform the RCS / PEPS operations.For example, the RKS unit 412 can receive vehicle commands from the key fob 102 via the TCU 408, process the commands to identify the appropriate ECU for executing the command, send the command to the identified ECU, and confirm the execution of the command. According to other embodiments, the RKS unit 412 can consist of several segments incorporated into different ECUs of the VCS 400, such as the BCM 404, the PCM 406, and / or the TCU 408, to process the RKS / PEPS commands received at each ECU. According to other embodiments, the RKS unit 412 can be contained within an ECU such as the TCU 408 to handle or process RKS / PEPS commands when received from the wireless communication module 410 of the TCU 408.
[0043] Fig. Figure 5 shows an exemplary method 500 for extending the communication range of a vehicle key fob device according to embodiments. The method 500 can be carried out by the vehicle key fob device, for example, the key fob 102 of the wireless system 100. Furthermore, the vehicle key fob device can interact with one or more components of the system 100 to perform the operations of the method 500. As shown in Fig. As shown in Figure 5, the procedure 500 begins in step 502, where the key fob detects a mobile connection input. According to embodiments, the mobile connection input can be entered by the user pressing a mobile connection input device on the key fob, such as the one shown in Figure 5. Fig. 1 Mobile connection key 116 shown. According to some embodiments, in method 500, a first output is further provided via the key fob in step 504 in response to the detection of the mobile connection input in step 502. The first output can be a visible, audible, and / or haptic indication provided by an output device of the key fob to indicate to the user of the key fob that the mobile connection input has been received. According to one embodiment, the first output is a light of a first color that is emitted after activation of the output device 117a (for example, a blue LED) of the key fob 102, as shown in Fig. Figure 1 is shown. In some cases, in procedure 500, the first output is also deactivated as soon as a predetermined time period has elapsed without any further command being received by the key fob's input devices.
[0044] According to some embodiments, in step 504, method 500 sends a command anticipation signal to a mobile device associated with the key fob, such as the one described in [reference to method 500]. Fig. 1 mobile device 108 shown. After receiving the command anticipation signal (also referred to here as the “alarm signal”), the mobile device can enter a corresponding command anticipation mode or otherwise prepare to receive a vehicle command from the key fob.
[0045] In step 508, the key fob recognizes a vehicle function input at one or more vehicle command input devices present on the key fob, for example, in the type described in Fig. 1 vehicle input devices 106 shown. The vehicle function input comprises a command for the vehicle to perform a desired operation or function, such as locking the vehicle doors, unlocking the trunk, starting the internal combustion engine, or any other normal key fob operation. According to some embodiments, after receiving the vehicle function input in step 510, the key fob provides a second output. The second output can be a visual, audible, and / or haptic cue provided by an output device of the key fob to indicate to the key fob user that the vehicle function input has been received. According to one embodiment, the second output is a light of a second color that illuminates after the output device 117b (for example, a yellow LED) of the key fob 102 is activated, as shown in Fig. 1 is shown, emitted.
[0046] In step 512, the key fob sends a vehicle command signal to the mobile device associated with the key fob for forwarding to the vehicle. The key fob then waits for confirmation that the vehicle command has been executed by the vehicle. The vehicle command signal includes the command associated with the vehicle function input entered by the user. For example, if the user has pressed the lock button 106a of key fob 102, the vehicle command signal contains a command to lock the vehicle doors. In another example, if the user has pressed the unlock button 106b of key fob 102 twice, the vehicle command signal contains a command to unlock all vehicle doors.
[0047] According to some embodiments, in step 514, the method 500 further receives a positive response (for example, a command acknowledgment signal) from the mobile device at the key fob, indicating that the vehicle command has been executed. The command acknowledgment signal can be provided to the mobile device by a remote server that is communicatively coupled to the vehicle, and the vehicle can be configured to provide the command acknowledgment signal to the remote server after it has determined that the vehicle command selected by the user has been executed on the vehicle. According to one embodiment, the remote server (for example, of the type of remote server 112) has a pre-established secure communication channel with a telematics control unit (TCU) of the vehicle (of the type, for example, the TCU 408 of vehicle 104) to enable the transmission of vehicle commands to the vehicle.
[0048] According to some embodiments, method 500 further provides a third output on the key fob in step 516, responding to the receipt of the positive response. The third output can be a visual, audible, and / or haptic indication provided by an output device of the key fob to confirm to the key fob user the receipt and completion of the vehicle command. According to one embodiment, the third output is a light of a third color, emitted after activation of the output device 117c (for example, a green LED) of the key fob 102, as shown in Fig. 1 is shown.
[0049] According to some embodiments, the method 500 also provides a fourth output (e.g., a red light) in response to receiving a negative response (e.g., a non-execution signal) from the mobile device, for example, if the requested vehicle command could not be executed or the command signal could not be sent via the transmission path 115. In some cases, the second output can be a flashing or blinking light (e.g., the yellow LED can be switched on and off sequentially) to indicate that the vehicle command has been sent to the mobile device and that the key fob is awaiting a response. The second output can continue to be provided while the wireless system 100 processes the command and until the key fob receives either the acknowledgment signal or the non-execution signal from the mobile device.
[0050] On Fig. Referring back to Section 2, it should be noted that an example computing device 200 is shown there for processing data or other inputs related to the wireless system 100, for recording and executing software used to enable the wireless system 100, the process 300 and / or the method 500, and / or for communicating with other components of the wireless system 100 according to embodiments. One or more instances of the computing device 200 can be used to implement any, some or all components in the system 100.According to some embodiments, sections of System 100 are implemented in software as an executable program and executed by one or more special-purpose or general-purpose digital computers such as mainframes, personal computers (desktop, laptop, or tablet computers), personal digital assistants, workstations, minicomputers, computer networks, virtual networks, internet cloud computing facilities, mobile phones or smartphones, tablets, or other handheld computing devices. In these cases, the computing device 200 may be a representative of a computer in which System 100 is located or partially located.
[0051] For example, the computing device 200 can represent a computer contained in the key fob 102 to receive vehicle command inputs and to communicate with the vehicle 104 and / or the mobile device 108.
[0052] Similarly, the computing device 200 can represent a computer contained in the mobile device 108 for storing, executing, and displaying the vehicle application 110 and for communicating with the key fob 102 and the remote server 112. As another example, the computing device 200 can represent a computer contained in the remote server 112 for connecting to the mobile device 108 and transmitting vehicle commands to the vehicle 104. Furthermore, the computing device 200 can represent a computer contained in the vehicle control system (VCS) 114 of the vehicle 104 for communicating with the key fob 102 and the remote server 112, receiving command signals from them, and processing and executing the received command signals.
[0053] As in Fig. As shown in Figure 2, the computing device 200 generally comprises a processor 202, a memory 204, and one or more input and / or output (I / O) devices 206 (or peripherals) that are communicatively coupled via a local interface 208. The processor 202 is a hardware device and can be a custom-made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors assigned to the computer 200, a semiconductor-based microprocessor (in the form of a microchip or a chipset), another type of microprocessor, or generally any device for executing software instructions.When the computing device 200 is operational, the processor 202 can be configured to execute software stored within the memory 204, to transfer data to and from the memory 204, and generally to control operations of the computing device 200 responsively to the software. The software can be read by the processor 202, buffered within the processor 202, or, typically, partially read by the processor 202, and then executed.
[0054] Memory 204 can be a computer-readable medium for storing software to implement System 100 and / or its components and to implement certain system transactions. For example, Memory 204 can be designed to store one or more separate programs (such as source code, executable program (object code), or script) that contain ordered lists of executable instructions for implementing logical functions related to System 100. Furthermore, the software can be written as (a) an object-oriented programming language that includes classes of data and methods, or (b) a procedural programming language that includes routines, subroutines, and / or functions, such as, but not limited to, C, C++, C#, Pascal, Basic, Fortran, Cobol, Perl, Java, Ada, Python, and Lua.Components of System 100 may also be written in a proprietary language designed to interact with these known languages. For the purposes of this document, a "computer-readable medium" may be any means capable of storing, transmitting, distributing, or transporting data objects for use by or in connection with Wireless System 100, and may even include paper with programming instructions printed on it.
[0055] In some cases, the software in memory 204 includes one or more applications 210 that are associated with the wireless system 100 and designed to implement the transmission path 115. For example, the one or more applications 210 in memory 204 of the mobile device 108 may include the entire vehicle application 110 or a part thereof. In another example, the one or more applications 210 in memory 204 of the key fob 102 include a mobile connection application for implementing the procedure 500 or, alternatively, for detecting a user selection of the mobile connection button 116 or for sending subsequently received vehicle commands to the mobile device 108.In some cases, the memory 204 of the key fob 102 can also store one or more security codes 212 that are uniquely assigned to the vehicle 104 and allow the key fob 102 to remotely command certain vehicle operations. In yet another example, the one or more applications 210 in the memory 204 of the server 112 comprise software designed to connect to the mobile device 108 and provide received vehicle commands to the telematics control unit (TCU) 408 or the vehicle control system (VCS) 114 / 400 of the vehicle 104.The memory 204 of the server 112 can also be used to implement one or more databases, such as a vehicle database 214, which is designed to store information related to the vehicle 104, including, for example, diagnostic information received from the TCU 408, GPS information received from a GPS satellite related to the vehicle 104, user account information relating to the vehicle application 110, and the like.
[0056] According to embodiments, the memory 204 comprises one or more or a combination of volatile memory elements (for example, random-access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and non-volatile memory elements (for example, ROM, hard disk drive, tape, CD-ROM, etc.). Furthermore, the memory 204 can incorporate electronic, magnetic, optical, and / or other types of storage media. In some cases, the memory 204 can have a distributed architecture, with different components located remotely but still accessed by the processor 202.
[0057] The local interface 208 can, for example, be one or more buses or other wired or wireless connections, as is known in the field, but without limitation thereto. The local interface 208 may include additional elements, omitted for the sake of simplicity, such as control devices, buffers (caches), drivers, repeaters, and receivers to enable communication. Furthermore, the local interface 208 may include address, control, and / or data links to enable appropriate communication between other computer components.
[0058] The I / O devices 206 may include interactive hardware located inside or outside the computing device 200 and connected wirelessly or by a connecting cable and / or I / O ports. The I / O devices 206 may include input devices 216, such as, but not limited to, input modules for programmable logic controllers (PLCs), a keyboard, a mouse, a scanner, a microphone, touchscreens, a stylus, radio frequency device readers, input hardware (such as keys, switches, sliders, knobs, dials, and the like, like the vehicle input devices 106 and the mobile input device 116), etc.Furthermore, the I / O devices 206 can also include output devices 218, for example, without limitation, output modules for PLCs, displays, haptic devices (e.g., actuators), lamps (e.g., LEDs, such as output devices 217), audio output devices (e.g., loudspeakers), etc.
[0059] The I / O devices 206 further include devices that communicate with both inputs and outputs, including, without limitation, a wireless communication module 220. The wireless communication module 220 has one or more antennas 222 designed to transmit and / or receive wireless signals to at least other components of the wireless system 100. The wireless communication module 220 further has one or more receivers, transmitters, and / or transmit-receivers (not shown) that are communicatively coupled to the one or more antennas 222 to process the received signals, provide the transmitted signals, or otherwise enable wireless communication with other components of the wireless system 100.The wireless communication module 220 can also include a modulator / demodulator (modem for accessing another device, system or network, such as another component within the wireless system 100), a bridge and / or a router.
[0060] The exact type of wireless communication technology incorporated into the wireless communication module 220 may depend on the computing device 200 and may include at least one short-range wireless communication technology (such as radio frequency (RF), Bluetooth, infrared, and / or NFC technology) and one long-range or broadband wireless communication technology (such as Wi-Fi, WiMAX, another wireless Ethernet, cellular, GPS, and / or satellite technology). In some cases, the wireless communication module 220 may have more than one antenna and corresponding transceiver to communicate over different wireless networks. For example, the mobile device 102 may use Bluetooth technology to communicate with the key fob 102 and Wi-Fi and / or cellular technology to communicate with the remote server 112.
[0061] In some cases, the Computing Device 200 may also include hardware for implementing one or more aspects of the techniques described herein. In such cases, the hardware uses one or a combination thereof of the following technologies, which are well-known in the field: one or more discrete logic circuits with logic gates for implementing logic functions from data signals, an application-specific integrated circuit (ASIC) with suitable combinational logic gates, one or more programmable gate arrays (PGAs), a field-programmable gate array (FPGA), etc.
[0062] Accordingly, the systems and methods described here can establish an increased communication range between a vehicle key fob device and the vehicle to which it is assigned by routing vehicle commands entered into the key fob via a transmission path that includes a mobile device securely paired with the key fob and a remote server securely paired with the vehicle's telematics system. More precisely, by establishing the transmission path 115, the key fob 102, together with the wireless system 100, can maintain the intuitiveness and convenience of a typical key fob (for example, in contrast to existing mobile application solutions) while also providing an increased communication range that is limited, for example, only by the range of cellular, satellite, and / or wireless Ethernet networks.
[0063] According to certain embodiments, the process descriptions or blocks in the figures can be in the manner of Fig. 3 and Fig. 5. Modules, segments, or sections of code represent one or more executable instructions for implementing specific logical functions or steps in the process. Any alternative implementations are included within the scope of protection of the embodiments described herein, whereby functions may be executed in a different order than that shown or discussed, including substantially simultaneous or reversed execution, depending on the functionality involved, as will be understood by those skilled in the art.
Claims
[1] Vehicle key fob (102) comprising: a module for wirelessly communicating with an associated mobile device (108), a dedicated input device (116) for initiating a mobile connection mode, a plurality of input devices (106) for commanding an associated vehicle (104) to perform a user-selected function, and a processor configured to send a command signal to the mobile device (108) to execute the function selected by the user upon receipt of an input at the dedicated input device (116), characterized by , that the vehicle key fob (102) comprises at least one output device (117) configured to provide a first output in response to receipt of the input at the dedicated input device (116). [2] The vehicle key fob (102) of claim 1, wherein the at least one output device (117) is further configured to provide a second output in response to the processor sending the command signal to the mobile device (108). [3] The vehicle key fob (102) of claim 1 or 2, wherein the at least one output device (117) is further configured to provide a third output in response to the processor receiving an acknowledgment signal indicating completion of the user-selected function. [4] Vehicle key fob (102) according to one of claims 1 to 3, wherein the at least one output device (117) includes a light-emitting diode. [5] The vehicle key fob (102) of any one of claims 1 to 4, wherein the at least one output device (117) includes a haptic device. [6] The vehicle key fob (102) of any one of claims 1 to 5, wherein the dedicated input device (116) and the plurality of input devices (106) are push buttons. [7] Wireless system (100) comprising: a vehicle key fob (102) configured to control a function of a vehicle (104) upon receipt of a first user input, and a mobile device (108) configured to receive a signal from the vehicle key fob (102) instructing the vehicle (104) to perform the function, the mobile device (108) further configured to send the signal to a remote server (112) communicating with the vehicle (104); wherein the vehicle key fob (102) has a plurality of input devices (106) for receiving the first user input and a dedicated input device (116) for receiving a second user input, wherein the vehicle key fob (102) is further configured to transmit the signal to the mobile device (108) in response to receiving the second user input prior to the first user input, characterized by , that the vehicle key fob (102) further comprises at least one output device (117) configured to provide a first output in response to receiving the first user input and to provide a second output in response to receiving the second user input. [8] The wireless system (100) of claim 7, wherein the vehicle (104) upon receiving the signal from the remote server (112) performs the function of sending an acknowledgment signal to the remote server (112), the remote server (112) sending the acknowledgment signal to the mobile device (108) for return to the vehicle key fob (102). [9] The wireless system (100) of claim 7, wherein the at least one output device (117) includes a light-emitting diode. [10] The wireless system (100) of any of claims 7 or 9, wherein the at least one output device (117) includes a haptic device. [11] The wireless system (100) of any one of claims 7 to 10, wherein the at least one output device (117) is further configured to provide a third output upon receipt of an acknowledgment signal indicating completion of the function. [12] A method for increasing a communication range of a vehicle key fob (102) for a vehicle (104), comprising: Detecting a first input for alerting a mobile device (108) associated with the vehicle key fob (102) on the vehicle key fob (102), subsequently recognizing a second input at one of a plurality of input devices (106) comprising a command to the vehicle (104) to perform a function on the vehicle key fob (102), and in response to the subsequent detection, sending the command to the mobile device (108) for forwarding to the vehicle (104), characterized by , that a first output is provided via the vehicle key fob (102) to indicate recognition of the first input, and a second output is provided via the vehicle key fob (102) to indicate recognition of the second input. [13] The method of claim 12, further comprising sending a command awaiting signal to the mobile device (108) after detecting the first input. [14] The method of claim 12, further comprising receiving an acknowledgment signal from the mobile device (108) upon completion of the function by the vehicle (104). [15] The method of claim 14, further comprising providing a third output via the vehicle key fob (102) to indicate receipt of the acknowledgment signal.
Citation Information
Patent Citations
Authorization recognition device for vehicle, and for use in authorization recognition system, has transponder communication device designed for recognizing authorization of transponder
DE102008039156A1
Control system for remote controlling function of vehicle, has control authority unit stored in mobile key unit for release of remote control that is available in mobile radio unit, and receiver unit provided with receiver interface
DE102012111316A1
Remote communication system for use with a vehicle and fob unit therefore
EP1216900B1
Fault tolerant vehicle communication and control apparatus
EP2048627A2
