System for keyless valet parking

Abstract

A method and apparatus for a keyless entry system are disclosed. An example vehicle includes a proxy dongle, a base configured to connect to the proxy dongle; and a proxy manager. The proxy manager enables the proxy dongle to authorize keyless entry and keyless ignition when (a) the proxy dongle is removed from the base while the ignition of the vehicle is on, and (b) an authorization password is provided via an infotainment host unit.

Description

Technical Field

[0001] The present disclosure generally relates to keyless entry for vehicles and, more particularly, to systems for keyless entry. Background Art

[0002] An increasing number of vehicles are being manufactured to use keyless entry systems, which assist a driver in unlocking and starting the vehicle without a key. Passive Entry Passive Start (PEPS) systems use key fobs. In such systems, when the key fob is near the vehicle, the vehicle prepares the doors to unlock when the door handle is touched. Additionally, when the key fob is inside the vehicle, the vehicle can enable a push-button ignition. A Phone as a Key (PaaK) system is similar, which uses the driver's phone in addition to replacing a dedicated key fob and connects to an application executed on the phone to determine when to unlock the doors and enable the ignition. Summary of the Invention

[0003] The appended claims define the application. The present disclosure outlines aspects of the embodiments and should not be used to limit the claims. Other embodiments are contemplated in accordance with the techniques described herein, which will be apparent to those of ordinary skill in the art after studying the following drawings and detailed description, and these embodiments are intended to be within the scope of this application.

[0004] Exemplary embodiments of a system for keyless entry are disclosed. An example vehicle includes a proxy dongle, a base configured to connect to the proxy dongle; and a proxy manager. The proxy manager enables the proxy dongle to authorize keyless entry and keyless ignition when (a) the proxy dongle is removed from the base while the vehicle ignition is on and (b) an authorization password is provided through an infotainment host unit.

[0005] An exemplary method includes: enabling a proxy dongle associated with a vehicle to operate a keyless entry and keyless ignition system when (a) the proxy dongle is removed from the base while the ignition of the vehicle is on; and (b) an authorization password is provided through an infotainment host unit. Additionally, the exemplary method includes, after enabling the proxy dongle, disabling the proxy dongle when (a) the proxy dongle is docked in the base, (b) an input to end the proxy mode is received via the infotainment host unit, and (c) an authorized mobile device is present.

[0006] According to the present invention, a vehicle is provided, comprising:

[0007] A proxy dongle;

[0008] A base configured to connect to the proxy dongle; and

[0009] A processor that executes instructions to enable a proxy dongle to authorize keyless entry and keyless ignition when the proxy dongle is removed from a pedestal while the vehicle's ignition is on and an authorization password is provided through an infotainment host unit.

[0010] According to one embodiment of the present invention, the proxy dongle includes a wireless communication module, a button, and a connector.

[0011] According to one embodiment of the present invention, the pedestal includes a port that engages with the connector of the proxy dongle when the proxy dongle docks with the pedestal, and wherein, when the proxy dongle is docked, the proxy dongle is communicatively and electrically connected to the vehicle.

[0012] According to one embodiment of the present invention, the pedestal is recessed into a panel of the vehicle.

[0013] According to one embodiment of the present invention, the processor is configured to provide a temporary authorization code to the proxy dongle for a limited period of time to authorize keyless entry and keyless ignition in order to enable the proxy dongle.

[0014] According to one embodiment of the present invention, the processor is configured to instruct a subsystem of the vehicle to enter a proxy mode after enabling the proxy dongle, and the proxy mode disables or restricts the functions of the subsystem.

[0015] According to one embodiment of the present invention, the processor is configured to disable the proxy dongle after enabling it when the proxy dongle is docked in the pedestal, an input to end the proxy mode is received via the infotainment host unit, and there is an authorized mobile device.

[0016] According to one embodiment of the present invention, the processor is configured to instruct a subsystem of the vehicle to exit the proxy mode after disabling the proxy dongle.

[0017] According to one embodiment of the present invention, the processor is configured to enable keyless ignition when the proxy dongle is enabled and the proxy dongle is docked in the pedestal.

[0018] According to the present invention, there is provided a method comprising:

[0019] Using a processor to enable a proxy dongle associated with a vehicle to operate a keyless entry and keyless ignition system when the proxy dongle is engaged with a pedestal and the vehicle's ignition is on while an authorization password is provided through an infotainment host unit;

[0020] When the proxy dongle is enabled, disabling the proxy dongle in the following cases:

[0021] The proxy dongle is docked on the pedestal,

[0022] An input to end the proxy mode is received through the infotainment host unit, and

[0023] There is an authorized mobile device.

[0024] According to an embodiment of the present invention, the proxy dongle is not a mobile phone or a key card.

[0025] According to an embodiment of the present invention, enabling the proxy dongle includes providing the proxy dongle with a temporary authorization code for authorizing a keyless entry and keyless ignition system, and the temporary authorization code is valid for a limited period of time.

[0026] According to an embodiment of the present invention, after enabling the proxy dongle, it includes instructing a subsystem of the vehicle to enter a proxy mode, and the proxy mode disables or restricts the functions of the subsystem.

[0027] According to an embodiment of the present invention, the method includes, after disabling the proxy dongle, instructing the subsystem of the vehicle to exit the proxy mode.

[0028] According to an embodiment of the present invention, the method includes enabling keyless ignition when the proxy dongle is enabled and docked in the base. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] To better understand the present invention, reference can be made to the embodiments shown in the following drawings. The components in the drawings are not necessarily drawn to scale, and related elements may be omitted, or in some cases the scale may have been enlarged to emphasize and clearly show the novel features described herein. Additionally, the system components may be arranged differently as known in the art. Further, in the drawings, the same reference numerals in several views denote the same parts.

[0030] Figure 1A 、 1B and 1C show a vehicle having a proxy dongle operating in accordance with the teachings of the present disclosure;

[0031] Figure 2 shows the proxy dongle of FIG. 1;

[0032] Figure 3 shows the proxy dongle of FIG. 1 connected to the vehicle of FIG. 1;

[0033] Figure 4 is a block diagram of the electronic components of the vehicle of FIG. 1;

[0034] Figure 5 is a flowchart of a method for activating and using the proxy dongle of FIG. 1 that can be implemented by Figure 4 the electronic components. DETAILED DESCRIPTION

[0035] Although the present invention may be embodied in various forms, some exemplary and non - limiting embodiments are shown in the drawings and will be described hereinafter. It should be understood that the present disclosure should be considered as an example of the present invention and is not intended to limit the present invention to the specific embodiments illustrated.

[0036] People use valet parking for various reasons. For example, in highly congested areas or dedicated parking lots, valet parking allows vehicles to be parked in a secure area, which can use space more efficiently compared to automatic parking. Additionally, valet parking can help control traffic flow. Typically, a driver hands his / her keys to a valet, who then parks the vehicle. However, while keyless entry systems such as Phone as a Key (Paak) are becoming increasingly common, drivers do not relinquish control of their phones.

[0037] As described below, a valet dongle is connected to the vehicle and provides temporary keyless entry and keyless ignition when the valet dongle is removed, without the driver relinquishing control of their phone. The valet dongle provides limited access to the vehicle to a temporary driver such as a valet. Additionally, when the dongle is used to start the vehicle's ignition, the vehicle can impose restrictions on the vehicle's control (such as speed limits, distance limits, infotainment system limits, etc.). The valet dongle is a device that connects to a port in the vehicle (such as a universal serial bus port, etc.). In some examples, the dongle is embedded in a panel of the vehicle (such as the vehicle's center console). In some such examples, the panel may have a compartment with a door to hide the valet dongle when not in use. The dongle includes a personal area wireless communication module (such as Bluetooth Low Energy (BLE), etc.) to communicate with the vehicle. In some examples, the dongle also includes a button that, when pressed, causes the dongle to send a message to the vehicle to provide an alert to the vehicle (such as a flash signal, horn honk, etc.) to notify the valet dongle holder at the vehicle's location.

[0038] The proxy dongle disconnects when the vehicle's ignition is turned off. At this time, the infotainment system prompts the driver to enter a password (such as a numeric or alphanumeric string, etc.) to authenticate that the driver is authorized to enable the proxy dongle. If the password is correct, the vehicle enables the proxy dongle. In some examples, the vehicle provides a temporary authentication code to the proxy dongle to authorize the proxy dongle to activate the keyless entry and keyless start functions for a limited number of uses. For example, the authentication code is only valid until the proxy dongle is disabled, and the authentication code cannot be used again to access the keyless entry and keyless start functions when the proxy dongle is disabled. When enabled, the proxy dongle acts as a wireless key to provide the valet with access to the vehicle's keyless entry function. The proxy dongle enables the keyless start function when connected to the corresponding port in the vehicle. The dongle is disabled when it is connected to the corresponding port of the vehicle, the driver indicates (such as through the infotainment system) to disable the proxy dongle, and the mobile device that authorizes access to the keyless entry and keyless start functions is near the vehicle.

[0039] Figure 1A , 1B Figures 1A, 1B, 1C illustrate a vehicle 100 having a proxy dongle 102 operating in accordance with the teachings of the present disclosure. The vehicle 100 can be a standard gasoline-powered vehicle, a hybrid vehicle, an electric vehicle, a fuel cell vehicle, and / or any other type of motor vehicle. The vehicle 100 includes components related to mobility, such as a powertrain having an engine, a transmission, a suspension, a drive shaft, and / or wheels, etc. The vehicle 100 can be non-autonomous or semi-autonomous (e.g., some conventional power functions are controlled by the vehicle 100). In the illustrated example, the vehicle 100 includes a communication module 104, an infotainment host unit (IHU) 106, a proxy dongle base 108, and a phone as a key (PaaK) unit 110.

[0040] The communication module 104 includes one or more wireless network interfaces to enable communication with a mobile device 112 (such as a smartphone, a smartwatch, a tablet, etc.) to facilitate keyless entry and keyless ignition using the mobile device 112. The communication module 104 also includes hardware (such as a processor, a memory, a storage device, an antenna, etc.) and software for controlling the wireless network interfaces (including personal area networks (such as Bluetooth Bluetooth Low Energy, ZigBee Z-Wave etc.) and / or wireless local area networks (including IEEE (Institute of Electrical and Electronics Engineers) 802.11a / b / g / n / ac or others) etc.).

[0041] The infotainment host unit 106 provides an interface between the vehicle 100 and a user (such as the owner 114, the valet 116, etc.). The infotainment host unit 106 includes digital and / or analog interfaces (such as input devices and output devices) to receive input from the user and display information. The input device may include, for example, a control knob, a dashboard, a digital camera for image capture and / or visual command recognition, a touch screen, an audio input device (such as a cabin microphone), a button, or a touchpad. The output device may include an instrument cluster output (such as a dial, a lighting device), an actuator, and / or a speaker. The infotainment unit, as one of the input and / or output devices, enables the center console display 118 (such as a liquid crystal display (“LCD”), an organic light emitting diode (“OLED”) display, a flat panel display, a solid state display, etc.) to display messages to the driver and receive input from the driver. In addition, the infotainment host unit 106 includes hardware (such as a processor or a controller, a memory, a storage device, etc.) and software (such as an operating system, etc.) for an infotainment system (such as of Ford Motor Company Toyota Motor Corporation of General Motors Company of etc.). In addition, the infotainment host unit 106 displays the infotainment system on, for example, the center console display 118.

[0042] As disclosed in more detail below in connection with the following Figure 3 the proxy dongle base 108 provides space for storing the proxy dongle 102. In some examples, the proxy dongle base 108 is recessed into a panel of the vehicle 100 (such as the center console, the overhead console, the door, or the dashboard, etc.). When the proxy dongle 102 is connected to a communication port in the proxy dongle base 108 (such as the communication port 306 of the following Figure 3 ), (a) it is communicatively connected to the PaaK unit 110, and (b) it is electrically connected to the power bus of the vehicle 100 to charge the battery of the proxy dongle 102. In some examples, the proxy dongle base 108 includes a removable cover to hide and / or protect the proxy dongle 102 during docking.

[0043] The PaaK unit 110 (sometimes referred to herein as the "key phone unit") facilitates the execution of the PaaK application on the mobile device 112 to control the functions of the vehicle 100 as if the mobile device were a key fob. The PaaK unit 110 broadcasts (sometimes referred to as "polling") from time to time via the communication module 104 to determine whether any paired mobile devices 112 are present near the vehicle 100. The PaaK unit 110 is communicatively connected to the paired mobile device 112. The PaaK unit 110 and the mobile device 112 establish a connection according to a specific wireless network protocol (such as Bluetooth Low Energy protocol version 4.0 and subsequent revisions maintained by the Bluetooth Special Interest Group, etc.). The PaaK unit 110 receives commands from the PaaK application on the mobile device 112 for forwarding to the body control unit (such as for keyless entry, etc.) and / or the powertrain control unit (such as for keyless ignition, etc.).

[0044] The PaaK unit 110 interrogates the mobile device 112 via the established connection to determine whether the PaaK application executed on the mobile device 112 is authorized to access the keyless entry and / or keyless start functions of the vehicle 100. In some examples, the PaaK unit 110 and the PaaK application exchange one or more authorization tokens. Additionally, in some examples, the PaaK application may prompt the user to enter a password and / or enter biometrics (such as a fingerprint) as part of generating an authorization token to send to the PaaK unit 110. For example, the authorization token generated by the PaaK application may be based on the authorization token received from the PaaK unit 110, a unique value stored by the PaaK application, and a value based on the password and / or biometric input (such as a hash value, etc.). Once authorized, the PaaK unit 110 receives key fob commands (such as unlocking the doors, opening the trunk, arming and disarming the alarm, etc.) from the PaaK application executed on the paired mobile device 112 via the connection.

[0045] The PaaK unit 110 interacts with a Passive Entry Passive Start (PEPS) system. The PEPS system (a) unlocks the doors when a human hand is detected on or near the door handle (such as via a touch sensor, via an infrared sensor, etc.), and / or (b) disables the anti-theft device and starts the engine during keyless ignition (such as by pressing the ignition button, etc.) when an authorized device (such as the mobile device 112 executing the PaaK application) is within the area around the vehicle 100.

[0046] In the example shown, the PaaK unit 110 also includes a proxy manager 120. The proxy manager 120 provides access to the PEPS system to the proxy dongle 102 when the proxy dongle 102 is enabled. When the proxy dongle 102 is enabled, the PaaK unit 110 provides the functionality of the PEPS system to the proxy dongle 102. In some examples, the functionality provided to the proxy dongle 102 may be restricted compared to the access rights provided to the paired mobile device 112.

[0047] The proxy manager 120 enables the proxy dongle 102 when the user indicates to activate the proxy system (e.g., by selecting an option provided on the central console display 118, the proxy dongle 102 is disconnected when the vehicle ignition is turned on, etc.). In some examples, when the proxy dongle 102 is engaged with the proxy dongle base 108 and then the proxy dongle 102 is removed from the proxy dongle base 108, the proxy dongle 102 is activated by entering a password into the infotainment system. In some examples, when the proxy dongle 102 is removed from the proxy dongle base 108 when the ignition of the vehicle 100 is turned off, the proxy manager 120 does not enable the proxy dongle 102. In some examples, the proxy manager 120 enables the proxy dongle 102 only when the authorized mobile device 112 is detected by the PaaK unit 110. In Figure 1A this case, to enable the proxy dongle 102, the proxy manager 120 prompts the owner to enter a password (such as a numeric or alphanumeric string, etc.) via the infotainment host unit 106 to authenticate that the driver has authorized the enabling of the proxy dongle 102. When the password is correct, the proxy manager 120 enables the proxy dongle 102. In some examples, to enable the proxy dongle 102, the proxy manager 120 provides a temporary authentication code to the proxy dongle 102. When the PaaK unit 110 queries the proxy dongle 102 to determine whether the proxy dongle 102 is authorized to access the keyless entry and / or keyless start function of the vehicle 100, the proxy dongle 102 uses the temporary authentication code to generate an authentication token. The temporary authentication code is configured such that when the temporary authentication code is no longer valid, the authentication token generated based on the temporary authentication code will no longer effectively provide access to the keyless entry and / or keyless start function of the vehicle 100. In some examples, the proxy manager 120 disables the temporary authentication code after the proxy dongle 102 has been used to access the vehicle 100 a threshold number of times and / or after the proxy dongle 102 is connected to the proxy dongle base 108.

[0048] The proxy dongle 102, when enabled, acts like a keyless entry key fob. For example, when the proxy dongle is within a threshold distance (such as 5 feet, 10 feet, 20 feet, etc.) of the vehicle 100, the PaaK unit 110 can instruct the body control module to prepare the doors to unlock. In some examples, the proxy manager 120 enables keyless ignition when the proxy dongle 102 is enabled and docked in the proxy dongle base 108.

[0049] As Figure 1B shown, the proxy manager 120 prompts the driver to exit the proxy mode via the infotainment host unit 106 when the proxy dongle 102 is enabled and docked in the proxy dongle base 108. As Figure 1C shown, the proxy manager 120 deactivates the proxy dongle 102 when: (a) the driver 114 instructs via the infotainment host unit 106 to exit the proxy mode, (b) the proxy dongle 102 is docked in the proxy dongle base 108, and (c) the proxy manager 120 detects via the communication module 104 the presence of an authorized mobile device 112 or key fob and / or a key inserted into the ignition.

[0050] In some examples, when the proxy dongle 102 is enabled, the proxy manager 120 imposes restrictions on the operation of the vehicle 100. In some examples, the proxy manager 120 instructs the powertrain control unit to limit the speed and / or acceleration of the vehicle 100 while enabling the proxy dongle 102. Additionally or alternatively, in some examples, the proxy manager 120 instructs the infotainment host unit 106 to disable the sound system while enabling the proxy dongle 102. In some examples, the proxy manager 120 instructs the infotainment host unit 106 to disable the infotainment system while enabling the proxy dongle 102.

[0051] Figure 2The proxy dongle 102 of FIG. 1 is shown. In the example shown, the proxy dongle 102 includes a PAN (Personal Area Network) module 202 and an input device 204, a connector 206, and a proxy PaaK unit 208. The PAN module 202 includes hardware (such as a processor, memory, storage device, antenna, etc.) and software for controlling interaction with a personal area network (such as Bluetooth, Bluetooth Low Energy, ZigBee, Z-Wave, etc.), which interacts with the communication module 104 of the vehicle 100. The PAN module 202 is wirelessly communicatively connected to the communication module 104 to facilitate interaction between the proxy dongle 102 and the PaaK unit 110 of the vehicle 100. The input device 204 is a physical, capacitive, or virtual button that, when pressed, causes the proxy dongle 102 to send a signal to the vehicle 100 to provide an indication (such as a horn honk, a flash signal, etc.) for identifying the vehicle 100. The connector 206 provides an interface for electrical and / or communicative connection to the vehicle 100 through a corresponding port (such as the communication port 306 below) of the proxy dongle base 108. In some examples, the connector 206 is a male universal serial bus (USB) connector. Figure 3 The communication port 306) of the vehicle 100.

[0052] The proxy PaaK unit 208 interacts with the PaaK unit 110 of the vehicle 100 via the PAN module 202 to act as a key fob to access the keyless entry and keyless ignition functions of the vehicle 100. The proxy PaaK unit 208 calculates and provides an authentication token authorized for the proxy dongle 102 used by the PaaK unit 110 of the vehicle 100. In the example shown, the proxy PaaK unit 208 includes a processor or controller 210 and a memory 212. The processor or controller 210 can be any suitable processing device or a set of processing devices, such as but not limited to: a microprocessor, a microcontroller-based platform, a suitable integrated circuit, one or more field programmable gate arrays (FPGAs), and / or one or more application specific integrated circuits (ASICs). The memory 212 can be a volatile memory (such as RAM (Random Access Memory), which can include non-volatile RAM, magnetic RAM, ferroelectric RAM, and any other suitable form); a non-volatile memory (such as disk memory, flash memory, EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), non-volatile solid state memory, etc.), a non-changeable memory (such as EPROM), a read-only memory, and / or a secure memory (sometimes referred to as "cryptomemory").

[0053] Figure 3 Shows the proxy dongle 102 of FIG. 1 connected to the vehicle 100 of FIG. 1 via the proxy dongle base 108. In the illustrated example, a panel 302 (such as a center console, an overhead console, a driver-side door, a dashboard, etc.) of the vehicle 100 defines a cavity 304 configured to receive the proxy dongle 102. In some examples, the cavity 304 is sized such that the proxy dongle 102 is located within the cavity 304 and thus is below the plane of the panel 302. The proxy dongle base 108 also includes a communication port 306. The communication port 306 is configured to engage a corresponding connector 206 of the proxy dongle 102. In some examples, the communication port 306 is a female USB connector. When the connector 206 of the proxy dongle 102 engages the communication port 306, the proxy dongle 102 is electrically connected to the power bus of the vehicle 100 to charge the battery of the proxy dongle 102 and / or communicatively connected to the PaaK unit 110 of the vehicle 100. In some examples, the proxy dongle base 108 includes a removable cover to hide the proxy dongle 102 when the proxy dongle 102 is connected to the communication port 306.

[0054] Figure 4 Is a block diagram of the electronic component 400 of the vehicle 100 of FIG. 1. In the illustrated example, the electronic component 400 includes a communication module 104, an infotainment host unit 106, a PaaK unit 110, a communication port 306, and a vehicle data bus 402.

[0055] The PaaK unit 110 includes a processor or controller 404 and a memory 406. In the illustrated example, the PaaK unit 110 is configured to include a proxy manager 120. The processor or controller 404 can be any suitable processing device or collection of processing devices, such as but not limited to: a microprocessor, a microcontroller-based platform, a suitable integrated circuit, one or more field programmable gate arrays (FPGAs), and / or one or more application specific integrated circuits (ASICs). The memory 406 can be a volatile memory (such as RAM, which can include non-volatile RAM, magnetic RAM, ferroelectric RAM, and any other suitable form); a non-volatile memory (such as disk memory, flash memory, EPROM, EEPROM, non-volatile solid state memory, etc.), a non-alterable memory (such as EPROM), a read-only memory, a secure memory, and / or a mass storage device (such as a hard disk drive, a solid state drive, etc.). In some examples, the memory 406 includes multiple memories, particularly volatile memory and non-volatile memory.

[0056] The memory 406 is a computer-readable medium on which a set or multiple sets of instructions, such as software for operating the methods of the present disclosure, can be embedded. These instructions can embody one or more of the methods or logics described herein. In a particular embodiment, the instructions can reside, in whole or at least in part, within any one or more of the memory 406, the computer-readable medium, and / or the processor 404 during the execution of the instructions.

[0057] The terms "non-transitory computer-readable medium" and "tangible computer-readable medium" should be understood to include a single medium or multiple media, such as a centralized or distributed database, and / or associated caches and servers that store a set or multiple sets of instructions. The terms "non-transitory computer-readable medium" and "tangible computer-readable medium" also include any tangible medium that is capable of storing, encoding, or carrying a set of instructions for execution by a processor or causing a system to perform any one or more of the methods or operations disclosed herein. As used herein, the term "tangible computer-readable medium" is expressly defined to include any type of computer-readable storage device and / or storage disk and to exclude propagated signals.

[0058] The vehicle data bus 402 communicatively connects the communication module 104, the infotainment host unit 106, and the PaaK unit 110. In some examples, the vehicle data bus 402 includes one or more data buses. The vehicle data bus 402 can be implemented according to the Controller Area Network (CAN) bus protocol defined by the International Organization for Standardization (ISO) 11898-1, the Media Oriented Systems Transport (MOST) bus protocol, the CAN Flexible Data (CAN-FD) bus protocol (ISO 11898-7), and / or the K-line bus protocol (ISO 9141 and ISO 14230-1) and / or the Ethernet ( TM ) bus protocol IEEE (Institute of Electrical and Electronics Engineers) 802.3 (since 2002), etc.

[0059] Figure 5 is a flowchart of an example method for activating and using the proxy dongle 102 of FIG. 1, which can be implemented by Figure 4 the electronic component 400. Initially, at block 502, the proxy manager 120 waits until the proxy dongle 102 is not connected to the proxy dongle base 108. At block 504, the proxy manager 120 determines whether the ignition of the vehicle 100 is off. The proxy manager 120 determines the status of the ignition from the powertrain control module. When the ignition is off, the method continues at block 510. When the ignition is on, the method continues at block 506.

[0060] At block 506, the proxy manager 120 prompts the driver 114 to enter a password via the central console display 118 of the infotainment host unit 106. At block 508, the proxy manager 120 determines whether the entered password matches the authorized password in the memory (such as the memory 406 above). When the password is authorized, the method proceeds to block 512. Otherwise, when the entered password is not the authorized password, the method proceeds to block 510. Optionally, in some examples, the proxy manager 120 prompts the driver 114 to enter a password via the central console display 118 when the proxy dongle 104 is connected to the proxy dongle base 108, and then enables the proxy dongle 104 until the proxy dongle 104 is removed from the proxy dongle base 108 when the password is authorized. At block 510, the proxy manager 120 sends an alert to the mobile device 112 via the communication module 104. Figure 4 At block 512, the proxy manager 120 enables the proxy dongle 102. Enabling the proxy dongle 102 includes instructing the PaaK unit 110 to perform keyless entry and keyless ignition functions in response to the presence of the proxy dongle 102. In some examples, enabling the proxy dongle 102 includes providing the proxy dongle 102 with a temporary authorization code for authenticating the proxy dongle 102 with the PaaK unit 110. At block 514, the proxy manager 120 sets the vehicle 100's subsystems (such as the powertrain module, the infotainment host unit 106, etc.) into proxy mode. In proxy mode, certain functions of these subsystems are restricted and / or disabled. For example, the infotainment host unit 106 can disable the infotainment system and / or the sound system, and the powertrain control module can limit the speed and / or acceleration of the vehicle 100.

[0061] At block 516, the proxy manager 120 determines whether the proxy dongle 102 is within the authorized keyless entry range (such as 1 foot, 2 feet, 5 feet, etc.) of the vehicle 100 in response to a trigger from the door handle. In some examples, the keyless entry range of the proxy dongle 102 is less than that of the authorized mobile device 112. For example, the authorized mobile device 112 can be pre-authorized for keyless entry within a range of 20 feet, and the proxy dongle 102 can be pre-authorized for keyless entry within a range of 5 feet. When the proxy dongle 102 is within the keyless entry range, at block 518, the proxy manager 120 activates keyless entry. At block 520, the proxy manager 120 determines whether the proxy dongle 102 is connected to the proxy dongle base 108. When the proxy dongle 102 is connected to the proxy dongle base 108, the method proceeds to block 524. Otherwise, when the proxy dongle 102 is not connected to the proxy dongle base 108, the method returns to block 516.

[0062] ​

[0063] At block 524, the proxy manager 120 authorizes keyless ignition. At block 526, the proxy manager 120 determines whether the user (e.g., driver 114) has indicated an exit from the proxy mode (e.g., by pressing a physical or virtual button on the infotainment host unit 106, etc.). When the user has indicated an exit from the proxy mode, the method proceeds to block 528. When the user has not indicated an exit from the proxy mode, the method returns to block 516. At block 526, the proxy manager 120 determines via the communication module 104 whether the authorized mobile device 112 is in the vicinity of the vehicle 100 (e.g., within 5 feet, inside, etc.). When the authorized mobile device 112 is not in the vicinity of the vehicle 100, the method returns to block 516. Otherwise, when the authorized mobile device 112 is in the vicinity of the vehicle 100, the method proceeds to block 530. At block 530, the proxy manager 120 instructs the subsystems of the vehicle 100 to exit the proxy mode. At block 532, the proxy manager 120 disables the proxy dongle 102. The proxy manager 120 instructs the Paak unit 110 not to authorize the keyless entry and keyless ignition functions based on the proxy dongle 102 in order to disable the proxy dongle 102. In some examples, the proxy manager 120 disables the temporary authorization codes stored in the proxy dongle 102.

[0064] Figure 5 The flowchart of represents machine-readable instructions stored in a memory (e.g., Figure 4 memory 406) that, when executed by a processor (such as Figure 4 processor 404), cause the vehicle 100 to implement one or more programs of the example proxy manager 120 of FIGS. 1 and 4. Additionally, although the example programs are described with reference to the Figure 5 flowcharts shown, many other methods for implementing the example proxy manager 120 may alternatively be used. For example, the order of execution of the blocks may be changed, and / or some of the described blocks may be changed, eliminated, or combined.

[0065] In this application, the use of a conjunctive is intended to include a connective. The use of a definite or indefinite article is not intended to indicate cardinality. Specifically, reference to "the" object or "a" object and "an" object is also intended to denote one of a possible plurality of such objects. Further, the connective "or" may be used to convey features that exist concurrently rather than mutually exclusive alternatives. In other words, the connective "or" should be understood to include "and / or". As used herein, the terms "module" and "unit" refer to hardware, typically associated with a sensor, that has circuitry providing communication, control, and / or monitoring capabilities. "Modules" and "units" may also include firmware executed on the circuitry. The terms "comprise", "comprising", and "comprised of" are inclusive and have the same scope as "include", "including", and "included of", respectively.

[0066] The above-described embodiments, particularly any "preferred" embodiment, are possible examples of implementations and are presented solely to clarify the principles of the invention. Many variations and modifications may be made to the above-described embodiments without departing from the spirit and principles of the technology described herein. All modifications are intended to be included within the scope of this disclosure and be protected by the appended claims.

Claims

1. A vehicle, comprising: A proxy dongle; A base configured to connect to the proxy dongle; and A processor that executes instructions to: remind a driver to provide an authorization password through an infotainment host unit when the proxy dongle is connected to the base while the ignition of the vehicle is on, and when the password is authorized, enable the proxy dongle to authorize keyless entry and keyless ignition until the proxy dongle is removed from the base.

2. The vehicle according to claim 1, wherein the proxy dongle includes a wireless communication module, a button, and a connector.

3. The vehicle according to claim 1 or 2, wherein the base includes a port that engages with a connector of the proxy dongle when the proxy dongle docks with the base, and wherein, When the proxy dongle is docked, the proxy dongle is communicatively and electrically connected to the vehicle.

4. The vehicle according to claim 1 or 2, wherein the base is recessed into a panel of the vehicle.

5. The vehicle according to claim 1 or 2, wherein the processor is configured to provide a temporary authorization code to the proxy dongle for authorizing the keyless entry and the keyless ignition for a limited period of time in order to enable the proxy dongle.

6. The vehicle according to claim 1 or 2, wherein the processor is configured to instruct a subsystem of the vehicle to enter a proxy mode after enabling the proxy dongle, the proxy mode disabling or restricting the functions of the subsystem.

7. The vehicle according to claim 1 or 2, wherein the processor is configured to disable the proxy dongle after enabling it when the proxy dongle is docked in the base, an input to end the proxy mode is received via the infotainment host unit, and there is an authorized mobile device.

8. The vehicle according to claim 7, wherein the processor is configured to instruct the subsystem of the vehicle to exit the proxy mode after disabling the proxy dongle.

9. The vehicle according to claim 1 or 2, wherein the processor is configured to enable the keyless ignition when the proxy dongle is enabled and the proxy dongle is docked in the base.

10. A method for keyless proxy parking, comprising: Using a processor to enable a proxy dongle associated with a vehicle to operate a keyless entry and keyless ignition system when an authorization password is provided through an infotainment host unit while the proxy dongle is engaged with a base and the ignition of the vehicle is on; After enabling the proxy dongle, disabling the proxy dongle in the following cases: The proxy dongle is removed from the base, An input to end the proxy mode is received through the infotainment host unit, and There is an authorized mobile device.

11. The method according to claim 10, wherein the proxy dongle is not a mobile phone or a key card.

12. The method according to claim 10, wherein enabling the proxy dongle includes providing a temporary authorization code to the proxy dongle for authorizing the keyless entry and the keyless ignition system, the temporary authorization code being valid for a limited period of time.

13. The method according to claim 10, including instructing a subsystem of the vehicle to enter the proxy mode after enabling the proxy dongle, the proxy mode disabling or restricting the functions of the subsystem.

14. The method according to claim 13, comprising, after disabling the proxy dongle, instructing the subsystem of the vehicle to exit the proxy mode.

15. The method according to claim 10, comprising enabling the keyless ignition when the proxy dongle is enabled and docked in the base.

Images