Method and system for activating a power source in a vehicle

Abstract

A system for a vehicle includes an input device configured to send an activation signal in response to an input for starting the vehicle. The system also includes a body controller programmed to send an activation signal in response to the input and the absence of a phone operated as a key to activate a power source within a cabin of the vehicle for a predefined time period since the last vehicle start.

Description

Technical Field

[0001] The present disclosure generally relates to a method and system for controlling activation of a power source within a vehicle cabin when the vehicle is in an off state. Background Art

[0002] With the development of wireless technology, mobile devices such as mobile phones can be used to replace traditional keys to unlock and start vehicles. The owner of the vehicle can install an application and an electronic or virtual key for the vehicle on his mobile phone and pair the mobile phone with the vehicle computer system. When the phone is near the vehicle, the phone is connected to the vehicle's computer system via a wireless connection (such as Bluetooth, Bluetooth Low Energy (BLE), NFC or other suitable phone-resident protocols), and the computer system verifies the paired encrypted key stored in the vehicle, where the encrypted key is stored in the mobile device via the application. After successful verification, the computer system can allow the owner to unlock and / or authorize the vehicle to accept a start command. Summary of the invention

[0003] In one or more illustrative embodiments, a system for a vehicle includes an input device configured to send an activation signal in response to an input for starting the vehicle. The system also includes a body controller programmed to send an activation signal in response to the input and the absence of a phone operating as a key, the presence of a passive key fob, an NFC card, or the entry of a keypad ignition code to activate a power source within a cabin of the vehicle for a predefined time period since the last vehicle start.

[0004] In one or more illustrative embodiments, a method includes receiving input for starting a vehicle, the vehicle being configured to start in the presence of a mobile device operating as a key but without detecting the presence of the mobile device, in the presence of entry of a passive key fob, an NFC card, or a keypad ignition code; sending an activation signal via an in-vehicle network in response to the input for starting the vehicle; and activating a power source for a predefined period.

[0005] In one or more illustrative embodiments, a system includes a processor programmed to, in response to receiving an input for starting a vehicle without detecting the presence of a mobile device operating as a key, present with entry of a passive key fob, NFC card, or keypad ignition code, send an activation signal to activate a power source within a cabin of a vehicle for a predefined time period since a last vehicle start, the vehicle identified according to a storage device being configured to start with the mobile device present.

[0006] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] For a better understanding of the invention and to show how it may be carried out, embodiments of the invention will now be described, by way of non-limiting example only, with reference to the accompanying drawings, in which:

[0008] Figure 1 An exemplary block topology of a vehicle system showing one embodiment of the present disclosure;

[0009] Figure 2 An exemplary flow chart showing a process for activating power supply of one embodiment of the present disclosure; and

[0010] Figure 3 An exemplary flow chart illustrating a process for activating a power supply of another embodiment of the present disclosure. DETAILED DESCRIPTION

[0011] As required, detailed embodiments of the present invention are disclosed herein; however, it should be understood that the disclosed embodiments are merely examples of the present invention that may be embodied in various forms and alternative forms. The drawings are not necessarily drawn to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, the specific structural and functional details disclosed herein should not be interpreted as limiting, but merely as a representative basis for teaching those skilled in the art to employ the present invention in various ways.

[0012] Embodiments of the present disclosure generally provide multiple circuits or other electrical devices. All references to circuits and other electrical devices and the functions provided by them are not intended to be limited to those shown and described herein. Although specific labels can be assigned to various circuits or other electrical devices, such circuits and other electrical devices can be combined and / or separated from each other in any way based on the specific type of electrical implementation required. It should be recognized that any circuit or other electrical device disclosed herein may include any number of microprocessors, integrated circuits, memory devices (e.g., flash memory, random access memory (RAM), read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or other suitable variations of the above) and software, which cooperate with each other to perform the operations disclosed herein. In addition, any one or more of the electrical devices can be configured to execute a computer program embodied in a non-temporary computer-readable medium programmed to perform any number of functions as disclosed.

[0013] Vehicles equipped with a passive entry passive start system use wireless detection of a key fob to unlock and authorize the start of the vehicle. In some embodiments, a mobile device such as a mobile phone can be used instead of a key fob to unlock and start the vehicle. However, if the battery of the mobile device is exhausted, the user may not be able to start the vehicle because the vehicle does not detect a valid key. In addition, the user cannot activate any power port (such as a USB port) in the vehicle cabin to recharge the battery because the vehicle computer system will not switch to accessory mode without a key. In this case, the driver will still be blocked when holding a valid key stored in the mobile device. The present disclosure particularly proposes a vehicle system and method for activating a power source in a vehicle when the vehicle is turned off. This can be done to allow the battery of the mobile device to be recharged, thereby allowing the vehicle to be started.

[0014] Figure 1 An exemplary diagram of a system 100 that can be used to activate a power source within a vehicle 102 is shown. The vehicle 102 may include various types of motor vehicles, crossover utility vehicles (CUVs), sport utility vehicles (SUVs), trucks, recreational vehicles (RVs), boats, airplanes, or other mobile machines for transporting people or goods. In many cases, the vehicle 102 may be powered by an internal combustion engine. As another possibility, the vehicle 102 may be a hybrid electric vehicle (HEV) powered by both an internal combustion engine and one or more electric motors, such as a series hybrid electric vehicle (SHEV), a parallel hybrid electric vehicle (PHEV), or a parallel / series hybrid electric vehicle (PSHEV), a boat, an airplane, or other mobile machine for transporting people or goods. It should be noted that the system 100 shown is only an example, and more, fewer, and / or differently positioned elements may be used.

[0015] The computing platform 104 may include one or more processors 106 configured to execute instructions, commands, and other routines that support the processes described herein. For example, the computing platform 104 may be configured to execute instructions of a vehicle application 110 to provide features such as navigation, accident reporting, satellite radio decoding, and hands-free calling. The instructions and other data may be maintained in a non-volatile manner using various types of computer-readable storage media 112. Computer-readable media 112 (also referred to as processor-readable media or storage devices) include any non-transitory media (e.g., tangible media) that participate in providing instructions or other data that can be read by the processor 106 of the computing platform 104. Computer-executable instructions may be compiled or interpreted according to a computer program created using a variety of programming languages ​​and / or technologies, including, but not limited to, the following in single or combined form: Java, C, C++, C#, Objective C, Fortran, Pascal, Java Script, Python, Perl, and PL / SQL.

[0016] The computing platform 104 may be configured to receive input from human machine interface (HMI) controls 136 configured to provide occupant interaction with the vehicle 102. For example, the computing platform 104 may interact with one or more buttons (not shown) or other HMI controls (e.g., a numeric or other keypad, steering wheel audio buttons, a push-to-talk button, dashboard controls, etc.) configured to invoke functions on the computing platform 104. The computing platform 104 may drive or otherwise communicate with one or more displays 138 configured to provide visual output to the vehicle occupants with the aid of a video controller 140. In some cases, the display 138 may be a touch screen that is also configured to receive user touch input via the video controller 140, while in other cases the display 138 may simply be a display without touch input capabilities.

[0017] The computing platform 104 may be configured to communicate with a mobile device 152 of a vehicle occupant. The mobile device 152 may be any of various types of portable computing devices capable of communicating with the computing platform 104, such as a mobile phone, a tablet computer, a smart watch, a laptop computer, a portable music player, or other device. In many examples, the computing platform 104 may include a wireless transceiver 150 (e.g., a Bluetooth module, a Zigbee transceiver, a Wi-Fi transceiver, an IrDA transceiver, an RFID transceiver, etc.) configured to communicate with a compatible wireless transceiver 154 of the mobile device 152. The wireless module may transmit data at a carrier frequency or a center frequency. The center frequency is an important aspect of a wireless system that affects interference immunity and bandwidth. For example, a typical remote keyless entry system operates at 902 MHz in the United States and at 868 MHz in Europe, while Wi-Fi and Bluetooth may operate at frequencies above 2 GHz.

[0018] The computing platform 104 may also be configured to communicate with the mobile device 152 via one or more data ports 116 controlled by the data port subsystem 114 through a wired connection 194. In one example, the wired connection 194 may be created via a cable connected between one of the data ports 116 and a device port 156 of the mobile device 152. When connected, the data port 116 may be configured to transfer data to and from the mobile device 152. The data port 116 may also be configured to supply power to the mobile device 152 via the cable connection 194 with the device port 156. The mobile device 152 may be configured to manage the device port 156 through the power management controller 162. The device port 156 may be any port that supports the power and / or data transaction protocol supported by the data port 116 of the vehicle 102. In some examples, the data port 116 and the device port 156 of the mobile device 152 may be any one of a USB Type A, USB Type B, USB Mini, USB Micro, and / or USB Type C port. In another example, the device port 156 may be port.

[0019] The computing platform 104 may also be configured to communicate with other components of the vehicle 102 via an in-vehicle network 142. As some examples, the in-vehicle network 142 may include, but is not limited to, one or more of a CAN, an Ethernet network, and MOST. The in-vehicle network 142 may allow the computing platform 104 to communicate with other vehicle systems such as one or more electronic control units (ECUs) 148. The ECUs 148 may include, but are not limited to: a body control module (BCM) 180; a powertrain control module (PCM) 182, which may be equipped with an anti-theft control module (ICM) 184; and a wireless accessory control module (WACM) 186.

[0020] The BCM 180 can be configured to connect to the computing platform 104 via the in-vehicle network 142 and monitor and control various electronic accessories in the body of the vehicle 102. As an example, the BCM 180 can be configured to control the central lock, power windows, power mirrors, and power port 188 of the vehicle 102. The power port 188 can include, for example, a 12-volt cigarette lighter socket or a USB port. Regardless of the port type, the power port 188 can be configured to supply power to the mobile device 152 directly via the device port 156 or via the use of a power adapter.

[0021] The PCM 182 may be configured to connect to the computing platform 104 via the in-vehicle network 142. The PCM 182 may monitor and control the operation of the engine and transmission, including the "start / off" or accessory (ACC) state of the vehicle 102. In the "start" state, the vehicle may be in a ready or power mode, and accessory functions such as a radio may be available. In the "off" state, the power capabilities of the vehicle 102 may be disconnected and unavailable without credentials. In the "ACC" state, accessories of the vehicle 102 may be available, but the power capabilities of the vehicle 102 may be disconnected and unavailable. The ICM 184 may be integrated into the PCM 182 and configured to verify a valid vehicle key to allow the vehicle to move from the "off" state to the "start" or "ACC" state. As an example, the ICM 184 may be configured to allow the engine fuel injection system to activate only after detecting a valid key inside the vehicle 102. Alternatively, the ICM 184 may be a separate component from the PCM 182 that is connected to the in-vehicle network 142 and configured to control starting of the vehicle 102. Alternatively, the ICM 184 may be integrated with the BCM 180.

[0022] PCM 182 can also be configured to control the vehicle's "on" or "off" state in response to input from a vehicle start / stop button 192 connected thereto. Alternatively, the start / stop button 192 can be connected to BCM 180 and configured to communicate with PCM 182 via the in-vehicle network 142.

[0023] The mobile device 152 storing a valid key 172 for the vehicle 102 may have been previously paired with the computing platform 104 of the vehicle 102. The computing platform 104 stores the pairing information in the paired device data in the storage device 112. When the driver enters the vehicle 102, the computing platform 104 can use the paired device data 160 to identify the mobile device 152. The mobile device 152 can automatically connect to the computing platform 104 via the wireless connection 196. The wireless connection can be, but is not limited to, a Bluetooth connection controlled by the Bluetooth module 134 and / or a WiFi connection controlled by the WiFi module 120. Alternatively or in addition, the paired device data 160 can be stored in the Bluetooth module 134 and / or the WiFi module 120. The mobile device 152 can launch the mobile application 170 stored in the storage device 168 and send the key 172 to the computing platform 104 via the wireless connection 196. The computing platform 104 can pass the key 172 to the ICM 184 via the in-vehicle network 142 for processing. If the ICM 184 recognizes that the key 172 is valid, it can generate a vehicle activation signal to the PCM 182 to permit the vehicle 102 to start. When the driver presses the start / stop button 192 to start the vehicle 102, the PCM 182, which has received the vehicle activation signal from the ICM 184, can start the vehicle 102. However, if the ICM 184 does not receive any valid key 172, it will not generate a vehicle activation signal, without which the PCM 182 will not be able to start the vehicle 102. As an example, the key 172 may be an encrypted code.

[0024] The WACM 186 may be configured to connect to the computing platform 104 via the in-vehicle network 142. The WACM 186 may control a wireless charger 190. The wireless charger 190 may allow wireless charging of a mobile device 152. When the vehicle 102 is in "ACC" or "start / run" mode, an occupant of the vehicle 102 (such as a driver) may use the HMI control 136 to turn on the wireless charger 190. If so, the computing platform 104 sends a power activation signal to the WACM 186 via the in-vehicle network 142. The WACM 186 may, in turn, turn on the wireless charger 190 in response to the power activation signal. This allows the occupant to wirelessly charge the mobile device 152 using the wireless charger 190 without physically connecting it to the computing platform 104 via the device port 156.

[0025] Figure 2An exemplary flow chart of a process 200 for activating a power source for a vehicle 102 is shown. At operation 202, the vehicle 102 detects a request to move the vehicle 102 from an "off / locked" mode to an "start" or "ACC" mode. In one example, a user may press the vehicle start / stop button 192, which may provide a button signal to the PCM 182. In another example, in the case of a BEV or PHEV vehicle 102, a user may connect the vehicle 102 for charging.

[0026] At operation 204, in response to the request, the PCM 182 determines whether there is a vehicle activation signal from the ICM 184. If a valid key 172 is detected and the ICM 184 generates a vehicle activation signal for the PCM 182, the process moves to operation 206, where the vehicle 102 transitions to a "start" or "ACC" mode. The valid key 172 can be a key stored to the mobile device 102, or an entry of a passive key fob, NFC card, or even a keypad ignition code. However, if the computing platform 104 does not detect a valid key 172 in the vehicle 102, the ICM 184 prevents the vehicle from starting and the process moves to operation 208.

[0027] At operation 208, the BCM 180 determines whether any mobile device 152 is assigned to the vehicle 102 for use as a key. In one possibility, the BCM 180 may query a Bluetooth Low Energy Module (BLEM) in communication with the BCM 180 to identify whether any mobile device 152 has been assigned to the vehicle 102 for use as a key. If the mobile device 152 has been assigned to the vehicle 102, as a possibility to transition the vehicle to "ACC" or "Start" but does not exist, control passes to operation 210. If not assigned, the process 200 ends.

[0028] At operation 210, the BCM 180 of the vehicle 102 activates the local power source and the remote power source. In one example, the BCM 180 may activate the power port 188 of the BCM 180. The BCM 180 may also send a power activation signal to the in-vehicle network 142. In response to the power activation signal, various other power sources within the cabin of the vehicle 102 may be turned on. In one example, the USB subsystem 114 of the computing platform 104 may receive the power activation signal via the in-vehicle network 142 and may activate the USB port 116. In another example, the WACM 186 may receive the power activation signal via the in-vehicle network 142 and may activate the wireless charger 190. It should be noted that other modules may also turn on the power in response to the power activation signal.

[0029] At operation 212, the vehicle 102 sets the timer to a time period for powering the power source. The timer can be implemented in various ways. In one example, the computing platform 104 can be configured to implement the timer. As an alternative example, the BCM 180 can be configured to implement the timer. The timer can be set to the length of time for charging the battery of the mobile device 152, thereby allowing the mobile device 152 to be turned on and connected to the computing platform 104 and initiate the key 172 to allow the ICM 182 to detect the key 172. In some examples, when the mobile device 152 is connected to the computing platform 104 via the USB port 116 via the wired connection 194, the key 172 can be sent to the computing platform 104 directly via the wired connection 194 without the need for the wireless connection 196. It should be noted that the time length of the timer does not need to be sufficient to fully charge the mobile device 152. The mobile device 152 only needs enough charge to turn on to send the key 172.

[0030] In one example, a predefined time period of fifteen minutes may be used. However, it should be noted that in some examples, the fifteen minute power budget lasts for the entire key-off cycle. For example, if power is used for five minutes during a key-off cycle and is turned off by the user, the subsequent time period used during the same key-off cycle may only be up to ten minutes.

[0031] At operation 214, the vehicle 102 identifies whether a predefined time period has elapsed. In response to the timer time having elapsed, control passes to operation 220 to disable the local power source and the remote power source. If the time has not elapsed, control passes to operation 214 to optionally determine whether any previously paired mobile devices 152 can now be detected. For example, once the mobile device 152 is charged enough to connect to the vehicle 102, charging is no longer required, so the power can be turned off to save vehicle battery power. If a previously paired mobile device 152 is detected, control passes to operation 218. If not detected, control passes to operation 218 to optionally determine whether the vehicle 102 has transitioned to a "start" or "ACC" mode. For example, another key device may have been brought into the vehicle 102 during the charging of the mobile device 152, in which case charging is no longer required.

[0032] At operation 220, the BCM 180 disables both the local power source and the remote power source. In one example, the BCM 180 generates a power disable signal and sends the power disable signal via the in-vehicle network 142. Alternatively, the power disable signal may be generated and sent by the computing platform 104. In one example, the USB subsystem 114 of the computing platform 104 may receive the power disable signal via the in-vehicle network 142 and may disable the USB port 116. In another example, the WACM 186 may receive the power disable signal via the in-vehicle network 142 and may disable the wireless charger 190. The process ends after operation 220.

[0033] Figure 3 An alternative exemplary flow chart of a process 300 for activating a power source for a vehicle 102 is shown. Compared to process 200, in process 300, the computing platform 104 monitors the state of charge of the battery of the vehicle 102. Based on the state of charge of the battery of the vehicle 102, an occupant may be provided with the option of extending a timer to continue providing power to the power source.

[0034] At operation 302 , the vehicle 102 detects a request to move the vehicle 102 from the “off / locked” mode to the “start” or “ACC” mode. In one example, the user may press the vehicle start / stop button 192 of the vehicle 102 , which may provide a button signal to the PCM 182 .

[0035] At operation 304, in response to the request to move to the "start" or "ACC" mode, the PCM 182 determines whether there is a vehicle activation signal from the ICM 184. If the computing platform 104 detects a valid key 172 and the ICM 184 generates a vehicle activation signal for the PCM 182, the process moves to operation 306, where the vehicle 102 transitions to the "start" or "ACC" mode. However, if the computing platform 104 does not detect a valid key 172 in the vehicle 102, the ICM 184 prevents the vehicle from starting and the process moves to operation 308.

[0036] At operation 308, the BCM 180 queries the computing platform 104 to identify whether the mobile device 152 having the key 172 is paired with the computing platform 104 of the vehicle 102. In one example, if the mobile device 152 was previously paired with the computing platform 104 via a Bluetooth connection, the pairing information of the mobile device 152 may be stored in the Bluetooth module 134. Additionally or alternatively, the pairing information may be stored in the WiFi module 120 and / or the storage device 112.

[0037] At operation 310, the BCM 180 determines whether there are any mobile devices 152 that have been previously paired with the computing platform 104. The BCM 180 may allow activation of the power source only if there is at least one previously paired mobile device 152 that may have a key 172 configured to start the vehicle 102. In other words, the power source may be activated only if there is a possibility that charging the mobile device 152 may help start the vehicle 102. If the BCM 180 determines that the computing platform 104 has information related to the mobile device 152 used as a key, control passes to operation 312. However, if the mobile device 152 has never been used as a key, charging of the mobile device 152 will not help start the vehicle 102. Therefore, if the BCM 180 determines that there is no such mobile device 152 that has been paired, the power source is not activated and the process 300 ends.

[0038] At operation 312, the BCM 180 determines whether the state of charge (SOC) of the battery of the vehicle 102 is sufficient to supply power to the power source. In one example, a threshold SOC can be set to allow the vehicle 102 to have power to perform one or more engine starts. The BCM 180 can determine the SOC based on the voltage of the battery when removed from any load. If it is determined that the SOC of the battery is below a threshold so that the power source can deplete the vehicle 102 to below the SOC threshold, the process 300 ends without activating any power source. If the BCM 180 determines that the SOC of the battery is above a threshold, control passes to operation 314.

[0039] At operation 314, the BCM 180 of the vehicle 102 activates the local power supply and the remote power supply. In one example, the BCM 180 can activate the power port 188 of the BCM 180. The BCM 180 can also send a power activation signal to the in-vehicle network 142. In response to the power activation signal, various other power sources within the cabin of the vehicle 102 can be turned on. In one example, the USB subsystem 114 of the computing platform 104 can receive the power activation signal through the in-vehicle network 142 and can activate the USB port 116. In another example, the WACM 186 can receive the power activation signal through the in-vehicle network 142 and can activate the wireless charger 190. It should be noted that other modules can also turn on the power in response to the power activation signal.

[0040] At operation 316, a timer of a predefined time period is set to start. The timer can be implemented in various ways. In one example, the computing platform 104 can be configured to implement the timer. As an alternative example, the BCM 180 can be configured to implement the timer. The timer can be set to the length of time for charging the battery of the mobile device 152, thereby allowing the mobile device 152 to be turned on and connected to the computing platform 104 and initiate the key 172, so as to allow the ICM 182 to detect the key 172. In some examples, when the mobile device 152 is connected to the computing platform 104 via the USB port 116 via the wired connection 194, the key 172 can be sent to the computing platform 104 directly via the wired connection 194 without the need for the wireless connection 196. It should be noted that the time length of the timer does not need to be sufficient to fully charge the mobile device 152. The mobile device 152 only needs enough charge to turn on to send the key 172. In one example, a predefined time period of fifteen minutes can be used.

[0041] At operation 318, the BCM 180 determines whether a subsequent input to extend the power time of the power source is received. In one example, when the battery of the mobile device 152 is deeply discharged, the mobile device 152 may need more than fifteen minutes to resume operation. If so, the BCM 180 can allow the user to extend the length of time for powering the power source in response to receiving subsequent inputs. In one example, the driver can press the start / stop button 192 again to extend the timer. (It should be noted that in other examples, this may not be allowed, and subsequent pushes may not allow the system to exceed the total power budget time.) In addition or alternatively, the driver can make subsequent inputs via the HMI controller 136 (for example, via pressing the extension button in the HMI screen). If such input is received, control is transferred to operation 320, where the timer is adjusted. In one example, the timer can be configured to extend a predefined time interval, such as five minutes for each subsequent input. Alternatively, the timer can be configured to reset to a predefined time period with each subsequent input, for example, extending back to a complete timer timeout period. As an example, the BCM 180 may only allow the driver to adjust the timer when nearing the end of the current timer. For example, subsequent input to the start / stop button will not increase the timer until it reaches the last minute of the countdown. (It should also be noted that in some examples, the power time and increase time can be set for the vehicle 102 in response to a settings update received via various mechanisms (such as via the mobile device 152, via WiFi, or via a connection to a remote server using the vehicle 102's embedded modem).

[0042] If no subsequent input is received at operation 318, control passes to operation 322. At operation 322, the BCM 180 determines whether the SOC of the vehicle battery is still sufficient to continue to supply power to the mobile device 152. In one example, the BCM 180 can compare the SOC with a second predefined threshold. It should be noted that the second threshold can be the same or different from the first threshold at operation 312. If the BCM 180 determines that the SOC of the battery is still sufficient to keep the power source activated, control passes to operation 324. If not, control passes to operation 326. At operation 324, the vehicle 102 identifies whether the predefined time period has passed. (In addition, a check for a previously paired mobile device 152 and / or a check for whether the vehicle 102 has transitioned to a "start" or "ACC" mode may optionally be performed, as discussed above with respect to process 200.) In response to the timer time lapse (or the location of the previously paired mobile device 152 or the transition of the vehicle 102 to a "start" or "ACC" mode), control passes to operation 326.

[0043] At operation 326, the BCM 180 deactivates all power supplies that it had previously turned on. In one example, the BCM 180 generates a power deactivation signal and sends the power deactivation signal via the in-vehicle network 142. Alternatively, the power deactivation signal may be generated and sent by the computing platform 104. In one example, the USB subsystem 114 of the computing platform 104 may receive the power deactivation signal via the in-vehicle network 142 and may deactivate the USB port 116. In another example, the WACM 186 may receive the power deactivation signal via the in-vehicle network 142 and may deactivate the wireless charger 190. The process ends at operation 328.

[0044] Variations of the systems and methods are possible.For example, the above-mentioned charging functions may be disabled for a vehicle 102 that is in a workshop or factory mode, such as during assembly or shipping to a dealer, or on a dealer lot prior to sale.

[0045] Computing devices such as computing platform 104 described herein generally include computer-executable instructions, which can be executed by one or more computing devices such as those listed above. The computer-executable instructions can be compiled or interpreted by a computer program created using a variety of programming languages ​​and / or technologies, including, alone or in combination, Java, PHP, and / or other programming languages. TM, C, C++, C#, Visual Basic, Java Script, Python, JavaScript, Perl, PL / SQL, etc. In general, a processor (e.g., a microprocessor) receives instructions, such as from a memory, a computer-readable medium, etc., and executes these instructions to perform one or more processes, including one or more of the processes described herein. The instructions and other data can be stored and transmitted using a variety of computer-readable media.

[0046] With respect to the processes, systems, methods, heuristics, etc. described herein, it should be understood that although the steps, etc. of such processes, etc. have been described as occurring in a particular order, such processes may be practiced with the steps performed in an order different from the order described herein. It should also be understood that certain steps may be performed simultaneously, other steps may be added, or certain steps described herein may be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating certain embodiments and should in no way be construed as limitations on the claims.

[0047] Therefore, it should be understood that the above description is intended to be illustrative rather than restrictive. After reading the above description, many embodiments and applications other than the examples provided will be apparent. The scope should not be determined with reference to the above description, but should be determined with reference to the complete scope of equivalent forms of the appended claims together with the rights granted by the claims. It is expected and intended that future developments will occur using the technology discussed herein, and the disclosed systems and methods will be incorporated into such future embodiments. In short, it should be understood that the present application is capable of modification and variation.

[0048] All terms used in the claims are intended to be given their broadest reasonable constructions and their ordinary meanings as understood by persons skilled in the art described herein unless an explicit indication to the contrary is given herein. In particular, use of singular articles such as "a," "an," "the," and "said" should be understood to refer to one or more of the indicated elements unless a claim recites an explicit limitation to the contrary.

[0049] An abstract of the disclosure is provided to allow the reader to quickly determine the nature of the technical disclosure. It should be understood that the abstract will not be used to interpret or limit the scope or meaning of the claims. In addition, in the aforementioned detailed description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure should not be interpreted as reflecting the following intention: the claimed embodiments require more features than the features explicitly set forth in each claim. On the contrary, as reflected in the following claims, the subject matter of the invention lies in fewer features than all the features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the detailed description, with each claim itself as a separately claimed subject matter.

[0050] Although exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the present invention. Rather, the words used in this specification are descriptive rather than restrictive words, and it should be understood that various changes can be made without departing from the spirit and scope of the present invention. In addition, the features of the various embodiments of implementation can be combined to form other embodiments of the present invention.

Claims

1. A system for a vehicle, the system comprising: a storage device configured to store pairing information of the mobile device; an input device configured to transmit a vehicle activation signal in response to an input for transitioning the vehicle to a start mode or an accessory mode; as well as a body controller programmed to, in response to the input and the absence of a valid key, perform the following operations: querying the storage device to identify whether pairing information of a mobile device is stored, the mobile device storing a key for shifting the vehicle to a start mode or an accessory mode, In response to determining that the storage device stores pairing information of the mobile device and the mobile device is not detected in the cabin of the vehicle, activating a power source in the cabin of the vehicle for a first predefined time period to allow the power source to charge the mobile device so that the mobile device sends a key for transitioning the vehicle to a start mode or an accessory mode.

2. The system of claim 1, wherein: The body controller is connected to an in-vehicle network, and the body controller is further programmed to send a power activation signal through the in-vehicle network.

3. The system of claim 2, further comprising a battery charge detector connected to a network in the vehicle, the battery charge detector being configured to determine a state of charge of a battery installed in the vehicle and configured to power the power source, wherein the body controller is configured to activate the power source in response to the state of charge of the battery being greater than a first threshold.

4. The system of claim 3, wherein: The battery charge detector is configured to monitor the state of charge of the battery in response to activation of the power source, and the body controller is configured to deactivate the power source in response to the state of charge of the battery being below a second threshold.

5. The system of claim 2, further comprising a wireless accessory controller connected to the in-vehicle network, the wireless accessory controller configured to activate a wireless charger in response to receiving the activation signal via the in-vehicle network.

6. The system of claim 1, wherein: The body controller is further configured to activate the power source for a second predefined time period in response to a subsequent activation signal sent from the input device.

7. The system of claim 6, wherein: The body controller is further configured to deactivate the power source in response to a sum of the first predefined time period and the second predefined time period reaching a maximum total power budget time that allows the power source to be activated during a key-off cycle.

8. The system of claim 1, wherein the presence of the valid key comprises the presence of a valid key code.

9. A method for activating a power source in a vehicle, the method comprising: storing pairing information of the mobile device in a storage device of the vehicle; receiving an input for transitioning the vehicle to a start mode or an accessory mode, the vehicle being configured to start in the presence of a mobile device operated as a key; In response to the input and the absence of a valid key, querying the storage device to identify whether pairing information of the mobile device is stored, the mobile device storing a key for transitioning the vehicle to a start mode or an accessory mode; as well as In response to determining that the storage device stores pairing information of the mobile device and the mobile device is not detected in the cabin of the vehicle, activating a power source in the cabin of the vehicle for a predefined time period to allow the power source to charge the mobile device so that the mobile device sends the key for transitioning the vehicle to the start mode or the accessory mode.

10. The method of claim 9, wherein: Activating the power supply also includes sending a power supply activation signal via the in-vehicle network.

11. The method of claim 9, further comprising deactivating the power source in response to expiration of the predefined time period.

12. The method of claim 9, further comprising activating the power source in response to at least one mobile key paired with the vehicle.

13. The method of claim 9, further comprising determining a state of charge of a battery of the vehicle, wherein the power source is activated in response to the state of charge being above a first threshold.

14. The method of claim 13, further comprising disabling the power source in response to the state of charge being below a second threshold.

15. The method of claim 9, further comprising activating the power supply for a second predefined time period in response to a subsequent activation signal.

16. The method of claim 9, wherein: The power source includes at least one of a universal serial bus port, a cigarette lighter socket, and a wireless charger.

17. The method of claim 9, further comprising: wirelessly connecting via a wireless transceiver to a mobile device having the key stored therein; verifying, by a processor, the key stored in the mobile device; as well as In response to successfully authenticating the key, the vehicle is started.

18. A system for activating a power source in a vehicle, the system comprising: A processor of a vehicle, the processor being programmed to, in response to receiving a key for shifting the vehicle to an accessory mode or a starter mode without detecting the presence of a mobile device or another valid key operating as a key, and based on determining that a storage device of the vehicle stores pairing information for the mobile device, send an activation signal to activate a power source within a cabin of the vehicle for a predefined period of time, thereby allowing the power source to charge the mobile device so that the mobile device sends the key for shifting the vehicle to the starter mode or the accessory mode.

19. The system of claim 18, wherein: The activation signal is sent via an in-vehicle network, and the system further includes a charger connected to the in-vehicle network, the charger being configured to activate the power source in response to receiving the activation signal via the in-vehicle network.

20. The system of claim 18, wherein: The processor is also programmed to, in response to detecting the presence of the mobile device or another valid key operating as the key, send a deactivation signal over an in-vehicle network to deactivate the power source.

Images