Vehicle with Extended Range Remote Key Fob

Abstract

The present disclosure provides "a vehicle with an extended-range remote control key fob". A vehicle includes an in-vehicle controller that is coupled to an external network transceiver and is configured to register a key fob and / or a mobile device configured as a key fob, the key fob and / or the mobile device including an authentication code and implementing remote control of the vehicle. The transceiver is configured to communicate autonomously with a remote server in response to a key fob signal received from the server, the key fob signal including the authentication code and a remote control command generated by the key fob and / or the mobile device configured as the key fob.

Description

Technical Field

[0001] The present disclosure relates to a vehicle that includes a paired or registered key fob remote control capability with extended wireless signal range through autonomous, remote web-based server and mobile phone communications. Background Art

[0002] Vehicle manufacturers have developed various types of in-vehicle and / or on-board computer processing systems that include vehicle controls, vehicle-to-vehicle and vehicle-to-infrastructure communication systems and related messaging capabilities; and various other vehicle-related applications. In addition, such vehicle systems are sometimes configured to enable remote control of various vehicle functions using a securely paired mobile key fob. Such mobile key fobs are typically configured as Bluetooth.TM. Low Energy (BLE) devices that must be within a predetermined range of a transceiver in the vehicle to operate.

[0003] While some improvements have been made to extend the distance and / or range over which such BLE devices can generate, transmit, and receive messages from vehicles, there are still some limitations that prevent consistent and uninterrupted BLE for extended range vehicle remote control capabilities. Some attempts have been made to utilize other types of mobile devices to implement remote vehicle control, such as smartphones, which have extended range communication capabilities. However, each such device requires user interaction between the mobile device and / or a vehicle application to facilitate remote control of the vehicle. Summary of the invention

[0004] Many types of personal, commercial, and industrial vehicles, including internal combustion engine and hybrid electric vehicles, plug-in hybrid electric vehicles, and battery electric vehicles, hereinafter collectively referred to as "vehicles", include several types of in-vehicle computing systems, controllers, interfaces, networks, communication capabilities, and applications. Such in-vehicle systems and applications enable vehicle operation and vehicle-to-vehicle and vehicle-to-infrastructure communications, as well as related communications and remote control capabilities via such contemplated communications systems using key fobs and other types of mobile devices.

[0005] The present disclosure relates to a vehicle, which includes at least one and / or one or more in-vehicle and / or on-board controllers, which are coupled to an external network transceiver. The controller is configured to register and / or "pair" a key fob with an authentication code to enable the key fob to remotely control the vehicle. The transceiver is configured to autonomously communicate with one or more remote servers, which communicate with an external network (such as the Internet); and may be one or more transceivers, each of which is configured for a specific communication protocol and capability, such as, for example, WiFi and cellular communications.

[0006] The controller is also configured to detect and respond to a key fob signal received from a remote server, the signal including an authentication code and a remote control command generated by the key fob. In response to the key fob signal, the controller is also arranged to modify the operation of at least one component of the vehicle according to the remote control command. In a further variation, the key fob is also configured to be paired and / or registered by an external mobile device via an authentication code, and is configured to generate a remote control command. In some adaptations, the mobile device may also be configured to communicate with the remote server. In addition, the mobile device is configured to respond to the remote control command and autonomously transmit the authentication code and the remote control command to the remote server.

[0007] In additional variations, the onboard controller is further configured to respond to a key fob signal from a remote server when the key fob is out of range of an onboard wireless vehicle transceiver configured with a communication signal range that is less than the communication signal range of the external network transceiver. In response to detecting that the key fob is within range of the onboard wireless vehicle transceiver, in other arrangements, the controller is further configured to interrupt communications with the remote server. The present disclosure also relates to modifications having a controller configured to respond to not detecting the key fob within the signal range of the onboard wireless vehicle transceiver and to respond by autonomously and periodically communicating with the remote server by the external network transceiver, monitoring and detecting remote control commands from the key fob.

[0008] The present disclosure includes a further modified controller configured to register a mobile device and, in response to not detecting a key fob within range of an onboard wireless vehicle transceiver while the mobile device is detected, the controller is configured to periodically and autonomously communicate with the mobile device by the wireless transceiver to detect remote control commands from the key fob.

[0009] In each such variation, the present disclosure contemplates a controller configured to monitor, detect, and respond to various remote control commands from the key fob, including (for purposes of example and not limitation) unlocking, locking, engine starting, cabin and / or seat temperature adjustment, security system arming / disarming, and driver preference commands, etc. In other arrangements, the controller is further adapted to register a mobile device and / or pair with a mobile device and an authentication code, and respond to key fob signals and remote control commands generated by the mobile device alone and independently of the key fob.

[0010] This overview of implementations and configurations of the vehicle and described components and systems introduces a series of exemplary implementations, configurations and arrangements in a simplified and less technically detailed arrangement, and these are further described in more detail in the following detailed description in conjunction with the accompanying description and drawings and the appended claims.

[0011] This Summary is not intended to identify key features or essential features of the claimed technology, nor is it intended to be used to help determine the scope of the claimed subject matter. The features, functions, capabilities, and advantages discussed herein may be implemented independently in various exemplary implementations, or may be combined in other exemplary implementations, as further described elsewhere herein, and may also be understood by those skilled in the relevant art with reference to the following description and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] A more complete understanding of exemplary implementations of the present disclosure may be obtained by referring to the detailed description and claims when considered in conjunction with the following drawings, wherein like reference numerals refer to similar or identical elements throughout the drawings. The drawings and annotations therein are provided to facilitate understanding of the present disclosure and do not limit the breadth, scope, scale, or applicability of the present disclosure. The drawings are not necessarily drawn to scale.

[0013] Figure 1 is a diagrammatic representation of the vehicle and its systems, controls, components, sensors, actuators, and methods of operation; and

[0014] Figure 2 Shows Figure 1 Certain aspects of the disclosure are depicted in , with components added, removed and / or rearranged for illustrative purposes. DETAILED DESCRIPTION

[0015] As required, detailed embodiments of the present invention are disclosed herein; however, it should be understood that the disclosed embodiments are merely exemplary of the present invention, which may be embodied in different 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 details 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 different ways.

[0016] As will be understood by those of ordinary skill in the art, the various features, components, and processes shown and described with reference to any one of the accompanying drawings may be combined with features, components, and processes shown in one or more other drawings to achieve embodiments that should be apparent to those skilled in the art but may not be explicitly shown or described. The combinations of features shown are representative embodiments of typical applications. However, various combinations and modifications of features consistent with the teachings of the present disclosure may be desired for particular applications or implementations, and they should be readily within the knowledge, skills, and capabilities of those working in the relevant technical field.

[0017] Referring now to the various drawings and illustrations and Figure 1 and Figure 2 , and specific reference Figure 1, shows a schematic diagram of a conventional petrochemical powered and / or hybrid electric vehicle 100, which vehicles, in other examples, may also include battery electric vehicles, plug-in hybrid electric vehicles, and combinations and modifications thereof, which are collectively referred to herein as "vehicles". Figure 1 Representative relationships between components of vehicle 100 are shown. The physical arrangement and orientation of the components within vehicle 100 and the functional and logical connections and relationships thereto may vary. Vehicle 100 includes a drivetrain 105 having a powertrain 110 that includes an internal combustion engine (CE) 115 and one or more of an electric motor or electric motor / generator / starter (EM) 120 that generates power and torque to propel vehicle 100.

[0018] The engine or CE 115 is a gasoline, diesel, biofuel, natural gas or alternative fuel powered combustion engine that produces output torque through front engine accessory devices in addition to other forms of electrical, cooling, heating, vacuum, pressure and hydraulic power. The EM 120 can be any of a variety of types of electric machines and can be, for example, a permanent magnet synchronous motor, a generator and an engine starter 120. The CE 115 and EM 120 are configured to propel the vehicle 100 via a drive shaft 125 and cooperate with various related components, which may further include a transmission, clutch, differential, braking system, wheels, etc.

[0019] The powertrain 110 and / or drive train 105 also include one or more batteries 130. One or more such batteries may be one or more higher voltage DC batteries 130 operating in the range of between about 48 and 600 volts, and sometimes between about 140 and 300 volts or more or less, which are used to store and supply power to the EM 120, and to capture and store energy during regenerative braking, as well as to power and store energy from other vehicle components and accessories. Other batteries may be low voltage DC batteries 130 operating in the range of between about 6 and 24 volts or more or less, which are used to store and supply power to other vehicle components and accessories.

[0020] like Figure 1 As shown, one or more batteries 130 are coupled to the engine 115, the EM 120, and the vehicle 100, respectively, through various mechanical and electrical interfaces and vehicle controllers, as described elsewhere herein. The high-voltage EM battery 130 is also coupled to the EM 120 through one or more of a powertrain control module (PCM), a motor control module (MCM), a battery control module (BCM), and / or power electronics 135, which are configured to convert and regulate direct current (DC) power provided by the high-voltage (HV) battery 130 to the EM 120.

[0021] The PCM / MCM / BCM / power electronics 135 is also configured to condition, invert, and transform the DC battery power into three-phase alternating current (AC), which is typically required to power the electric machine or EM 120. The PCM / MCM / BCM 135 / power electronics is also configured to charge the battery or batteries 130 where the EM 120 and / or front end accessory drive components generate energy; and receive power from, store power, and supply power to other vehicle components as needed.

[0022] Continue to refer Figure 1 , in addition to the PCM / MCM / BCM / power electronics 135, the vehicle 100 also includes one or more controllers and computing modules and systems that implement various vehicle capabilities. For example, the vehicle 100 may incorporate a body control module (BCM) that is a separate unit and / or may be incorporated as part of a vehicle system controller (VSC) 140 and a vehicle computing system (VCS) and controller 145 that communicate with the PCM / MCM / BCM 135 and other controllers.

[0023] For example, in some configurations, for purposes of example and not limitation, the VSC 140 and / or VCS 145 are and / or incorporate SYNC.TM., APPLINK.TM., MyFord Touch.TM. and / or open source SmartDeviceLink and / or OpenXC onboard and off-board vehicle computing systems, in-vehicle connectivity, infotainment, and communication systems and application programming interfaces (APIs) for communicating with and controlling off-vehicle and / or external devices.

[0024] For further example, but not for the purpose of limitation, at least one and / or one or more of the controllers such as the VSC 140 and the VCS 145 may incorporate and further be and / or include one or more accessory protocol interface modules (APIMs) and / or an integral or separate head unit that may be, include and / or incorporate an information and entertainment system (also referred to as an infotainment system and / or an audio / visual control module or ACM / AVCM). These modules include and / or may include a media player (MP3, Blu-Ray.TM., DVD, CD, cassette, etc.), a stereo, an FM / AM / satellite radio receiver, etc., as well as a human machine interface (HMI) and / or display unit as described elsewhere herein.

[0025] These contemplated components and systems are available from various sources and (for example purposes) are manufactured by and / or available from the SmartDeviceLink Consortium, the OpenXC Project, Ford Motor Company, and others (e.g., see SmartDeviceLink.com, openXCplatform.com, www.ford.com, U.S. Pat. Nos. 9,080,668, 9,042,824, 9,092,309, 9,141,583, 9,680,934, and others).

[0026] In further examples, SmartLinkDevice (SDL), OpenXC, and SYNC.TM.AppLink.TM. are examples, each enabling at least one and / or one or more of the controllers, such as the VSC 140 and VCS 145, to communicate remote procedure calls (RPCs) utilizing an application programming interface (API) that enables command and control of external or off-vehicle mobile devices and applications by utilizing an in-vehicle or on-board HMI, such as a graphical user interface (GUI) and other input and output devices, which also include hardware and software controls, buttons and / or switches, and steering wheel controls and buttons (SWC), instrument cluster and panel hardware and software buttons and switches, and other controls. Exemplary systems, such as SDL, OpenXC, and / or AppLink.TM. utilize the HMI of the vehicle 100, such as SWC and GUI, to make the functionality of the mobile device available and enabled, and may also include on-vehicle or in-vehicle automatic recognition and processing utilizing voice commands.

[0027] The controllers of the vehicle 100, such as the VSC 140 and the VCS 145, include and are coupled to one or more high-speed, medium-speed, and low-speed vehicle networks, including, among other things, a multiplexed broadcast controller area network (CAN) 150, as well as larger vehicle control systems and other vehicle networks that may and / or may not require a host processor, controller, and / or server, and as further examples, may also include other microprocessor-based controllers, as described elsewhere herein. The CAN 150 may also include network controllers and routers in addition to communication links between controllers, sensors, actuators, routers, in-vehicle systems and components and off-vehicle systems and components external to the vehicle 100.

[0028] Such a CAN 150 is known to those skilled in the art and is described in greater detail by various industry standards, including, among others, the Society of Automotive Engineers™ (SAE) J1939, entitled “Serial Control and Communications Heavy Duty Vehicle Network,” available from standards.sae.org, and the automotive information standard available from the International Organization for Standardization (ISO) 11898, entitled “Road vehicles-Controller area network (CAN),” and ISO 11519, entitled “Road vehicles-Low-speed serial data communication,” available from www.iso.org / ics / 43.040.15 / x / .

[0029] The CAN 150 contemplates a vehicle 100 having one, two, three, or more such networks operating at various low, medium, and high speeds, e.g., ranging from about 50 kilobits per second (Kbps) to about 500 Kbps or more. The CAN 150 may also include, incorporate, and / or communicate with internal, onboard, and external wired and wireless personal area networks (PANs), local area networks (LANs), wide area networks (WANs), peer-to-peer (P2P), vehicle-to-vehicle (V2V), and vehicle-to-infrastructure, infrastructure-to-vehicle (V2I, I2V) networks, etc., and as described and contemplated elsewhere herein.

[0030] In further examples, without limitation, the VSC 140, VCS 145 and / or other controllers, devices and processors may include, be coupled to, configured with and / or cooperate with one or more integrally included, embedded and / or independently disposed two-way communication, navigation and other systems, controllers and / or sensors, such as a vehicle-to-vehicle communication system (V2V) 155, and a vehicle-to-road infrastructure-to-vehicle communication system (V2I) 160, a lidar / sonar (light and / or sound detection and ranging) and / or camera road proximity imaging and obstacle sensor system 165, a GPS or global positioning system 170, and a navigation and moving map display and sensor system 175, and the like.

[0031] The VCS 145 may cooperate in parallel, serial, and distributed fashion with the VSC 140 and such steering wheel controls and buttons, and other controllers, subsystems, and internal and external systems to manage and control the vehicle 100, external devices, and such other controllers, and / or actuators in response to sensor and communication signals, data, parameters, and other information that is identified by, established by, transmitted to, and received from these vehicle systems, controllers, and components, and other off-vehicle systems that are external and / or remote to the vehicle 100.

[0032] Such bidirectional V2V 155 and V2I 160 (also sometimes collectively referred to herein as V2X) communication controllers and systems utilize various industry protocols, standards, and / or messaging formats available in the United States and other countries to enable peer-to-peer, vehicle-to-vehicle, and vehicle-to-infrastructure point-to-point and similar types of networking and communications. These protocols, standards, and / or messaging formats are used to implement various aspects of the present disclosure and are known to those having relevant technical knowledge.

[0033] Many international standards organizations are also involved in the technology space and have produced various V2X resources, such as the SAE telematics and related standards J2945 and J2735: “On-Board System Requirements for V2V Safety Communications Standard,” SAE J2945 / 1_201603, standards.sae.org / j2945 / 1_201603 / , and “Dedicated Short Range Communications (DSRC) Message Set Dictionary Standard,” SAE J2735_201603, standards.sae.org / j2735_201603, and others available at topics.sae.org / telematics / standards / automotive.

[0034] The SAE J2735 standard describes, defines, and specifies the messages and data elements that make up a message / dialog specifically for use by vehicles, infrastructure, and other off-vehicle applications that utilize 5.9 gigahertz (GHz) DSRC using a Wireless Access in Vehicular Environment (WAVE) communication system. Such WAVE communications and related systems are described in more detail in various reports established by and available from the Institute of Electrical and Electronics Engineers (IEEE) as described below. See, for example, standards.ieee.org, and more specifically, IEEE Standard 1609, entitled "Guide for Wireless Access in Vehicular Environments (WAVE) Architecture," available from standards.ieee.org / develop / wg / 1609_WG.html.

[0035] The IEEE 1609WAVE standard implements and defines an architecture and a set of standardized communication services and interfaces that enable secure V2V and V2I wireless communications. These standards enable a range of transportation and navigation applications, including vehicle safety, automatic toll collection, enhanced navigation, and traffic management. The IEEE 1609Wave capabilities are used in conjunction with other capabilities for various aspects of network and communication standards and architectures, including those managed by the IEEE 802 Local Area Network and Metropolitan Area Network (LAN / MAN) Standards Committee, which can be found at www.ieee802.org, as well as standards.ieee.org.

[0036] IEEE Standard 802.11 supports the software and firmware communication services of IEEE 1609 and implements data link media access control (MAC) and physical layer (PHY) capabilities, such as wireless local area network (WLAN) data communications in various frequency bands. The 802.11 standard is titled "IEEE Standard for Information Technology - Telecommunications and Information Exchange between Systems - Local and Metropolitan Area Networks - Specific Requirements Part 11: Wireless Local Area Network Media Access Control (MAC) and Physical Layer (PHY) Specifications" and is available at ieeeexplore.ieee.org / document / 7792308.

[0037] Although shown herein as discrete individual controllers for purposes of illustration, the PCM / MCM / BCM 135, VSC 140, and VCS 145, as well as other intended controllers, subsystems, and systems, can control, be controlled by, transmit signals between, and exchange data with other controllers and other sensors, actuators, and components that are part of larger vehicle and control systems, external control systems, and internal and external networks, components, subsystems, and systems.

[0038] The capabilities and configurations described in conjunction with any particular microprocessor-based controller as contemplated herein may also be embodied in one or more other controllers and distributed across more than one controller, such that multiple controllers may individually, collaboratively, in combination, and cooperatively enable any such capabilities and configurations. Thus, the recitation of "a controller" or "the controller" is intended to refer to such controllers, components, subsystems, and systems, both in the singular and in the plural, and individually, collectively, and in various suitable collaborative and distributed combinations.

[0039] In addition, communication via CAN 150 and other internal and external PANs, LANs and / or WANs is intended to include responding, sharing, transmitting and receiving commands, signals, data, embedded data in signals, control logic, and information between controllers, and sensors, actuators, controls, and vehicle systems and components. The controller communicates with one or more controller-based input / output (I / O) interfaces, which can be implemented as a single integrated interface that enables communication of raw data and signals, and / or signal conditioning, processing and / or conversion, short circuit protection, circuit isolation, and similar capabilities. Alternatively, one or more dedicated hardware or firmware devices, controllers, and systems on a chip can be used to pre-condition and pre-process specific signals during communication and before and after transmission.

[0040] In further illustration, the PCM / MCM / BCM 135, VSC 140, VCS 145, CAN 150, and other controllers may include one or more microprocessors or central processing units (CPUs) in communication with various types of computer-readable storage devices or media. Computer-readable storage devices or media may include volatile and non-volatile storage devices in read-only memory (ROM), random access memory (RAM), and non-volatile or keep-alive memory (NVRAM or KAM). NVRAM or KAM are persistent or non-volatile memories that may be used to store various commands, executable control logic and instructions, and code, data, constants, parameters, and variables required to operate the vehicle and systems when the vehicle and systems and the controllers and CPUs are not powered on or powered off.

[0041] The computer readable storage device or medium may be implemented using any of a number of known persistent and non-persistent memory devices, such as PROM (Programmable Read Only Memory), EPROM (Electronic PROM), EEPROM (Electrically Erasable PROM), Hard Disk Drive (HDD), Solid State Drive (SSD), Flash Memory, or any other electrical, magnetic, optical, or combination memory device capable of storing and transmitting data. Each of such devices, components, processors, microprocessors, controllers, microcontrollers, memories, storage devices, and / or media may further include, comprise, and / or be embedded with one or more Basic Input and Output Systems (BIOS), operating systems, application programming interfaces (APIs) (with, enabling, and / or implementing Remote Procedure Calls (RPCs)) and related firmware, microcode, software, logic instructions, commands, etc., which enable programming, customization, coding, and configuration, and which may be embedded and / or contained in at least one of one or more such devices and / or distributed on one or more such devices, among other capabilities.

[0042] In this arrangement, the VSC 140 and VCS 145 cooperatively manage and control vehicle components and other controllers, sensors and actuators, including, for example, but not limited to, the PCM / MCM / BCM 135, and / or various other devices. For example, the controller can establish two-way communications with such internal and external sources and transmit control commands, logic and instructions, and codes, data, information and signals to and / or from the engine 115, EM 120, battery 130 and PCM / MCM / BCM / power electronics 135 and other internal and external components, devices, subsystems and systems. The controller can also control and communicate with other vehicle components known to those skilled in the art, even if not shown in the figures.

[0043] Figure 1 The embodiment of the vehicle 100 in FIG. 1 also depicts exemplary sensors and actuators in communication with a wired and / or wireless vehicle network and CAN 150 (PAN, LAN) that can bidirectionally transmit and receive data, commands, and / or signals to and from the VSC 140, VCS 145, and other controllers. Such control commands, logic and instructions, as well as code, data, information, signals, settings, and parameters (including driver preferred settings and preferences) can be captured and stored in and transferred from the repository of driver controls, preferences, and profiles 180 and other controllers' memory and data storage devices.

[0044] As shown in the various figures (including Figure 1 and Figure 2), signals and data (including, for example, commands, information, settings, parameters, control logic and executable instructions, and other signals and data) may also include other signals (OS) 185, and control or command signals (CS) 190 received from and sent to and between controllers and vehicle components and systems via wired and / or wireless data and signaling connections. OS 185 and CS 190, as well as other signals, associated control logic and executable instructions, parameters, and data, may and / or may be predicted, generated, established, received, transmitted, to and from, and between any of the vehicle controllers, sensors, actuators, components, and internal, external, and remote systems.

[0045] Any and / or all of these signals may be raw analog or digital signals and data, or pre-conditioned, pre-processed, combined and / or derived data and signals generated in response to other signals, and may encode, embed, represent voltages, currents, capacitances, inductances, impedances and digital data representations thereof, and digital information, and may be represented by voltages, currents, capacitances, inductances, impedances and digital data representations thereof, and digital information, the digital information encoding, embedding and / or otherwise representing such signals, data and analog, digital and multimedia information.

[0046] The various contemplated controllers, sensors, actuators and other vehicle components may communicate and operate on the described signals, commands, control instructions and logic, as well as data and information. Figure 1 The diagrams illustrate exemplary command and control processes, control logic and instructions, and operating strategies, which may be implemented using one or more computing, communication, and processing technologies, which may include real-time, event-driven, interrupt-driven, multi-tasking, multi-threading, and combinations thereof.

[0047] The steps and functions shown may be performed, transmitted, and executed in the sequence depicted, as well as in parallel, repeatedly, in a modified sequence, and in some cases may be combined with other processes and / or omitted. Commands, control logic, and instructions may be executed in one or more of the described microprocessor-based controllers, in external controllers and systems, and may be primarily embodied in hardware, software, virtualized hardware, firmware, virtualized hardware / software / firmware, and combinations thereof.

[0048] Figure 1An exemplary configuration and block topology of the VCS 145 and its intended controllers, devices, components, subsystems and / or systems for the vehicle 100 is also schematically depicted for purposes of continued explanation and not for purposes of limitation. The present disclosure relates to an HMI including hardware and software switches and controls (HSCs), which further relates to, incorporates and includes buttons and / or switches, and steering wheel controls and buttons (SWCs), instrument cluster and panel hardware and software buttons and switches, and GUI display software switches and controls, among other controls.

[0049] In further exemplary arrangements, various controllers (such as, for example, the VCS 145) include and / or in some arrangements may include at least one and / or one or more human machine interface (HMI) / graphical user interface and visual display (GUI, HMI) 200, which may be located in the cabin of the vehicle 100. The HMI / GUI 200 may also be coupled and cooperate with automatic speech recognition and speech synthesis subsystems and additional hardware and software controls, buttons and / or switches that are incorporated into, included and / or displayed on, around and / or as part of the HMI / GUI 200 and instrument clusters and panels of the vehicle 100.

[0050] Such controls, buttons and / or switches may be integrated with the HMI / GUI 200 and other vehicle devices and systems, which may include, for further example and illustration, a steering wheel and related components, a vehicle dashboard and instrument cluster, etc. For further example purposes and without limitation, the VCS 145 may include and / or incorporate persistent memory and / or storage devices HDD, SSD, ROM 205, and non-persistent or persistent RAM / NVRAM / EPROM 210, and / or similarly configured persistent and non-persistent memory and storage components.

[0051] In an illustrative but non-limiting example, the VCS 145 and / or other controllers also include, incorporate and / or couple to one or more vehicle-based bi-directional data inputs, outputs and / or communications and related devices and components that are capable of communicating with the user, driver and passengers of the vehicle 100 and external adjacent and remote devices, networks (CAN 150, PAN, LAN, WAN) and / or systems. The phrases "vehicle-based" and "onboard" refer to devices, subsystems, systems and components that are integrated into, incorporated around, and coupled to the vehicle 100 and its various controllers, subsystems, systems, devices and / or components. Conversely, the phrase "off-vehicle" refers to and contemplates that such controllers, subsystems, systems, devices and / or components are located outside of and / or remote from the vehicle 100.

[0052] For further examples, the VCS 145, GUI 200, and other controllers of the vehicle 100 may include, incorporate, pair with, synchronize with, and / or couple with: vehicle-based multimedia devices 215; auxiliary inputs 220 and analog / digital (A / D) circuits 225; universal serial bus port (USB) 230; near field communication transceiver (NFC) 235; wireless router and / or transceiver (WRT) 240, such as "Bluetooth.TM." and Bluetooth.TM. Low Energy (BLE) devices that implement wireless personal area networks and wireless local area networks (WPAN, WLAN) or "WiFi" IEEE 802.11 and 803.11 communication standards); and / or analog and digital cellular network modems and transceivers (CMT) 245, which utilize voice / audio and data coding and the following technologies, including, for example, those managed by the International Telecommunication Union (ITU) as International Mobile Telecommunications (IMT) standards, which are commonly referred to as Global System for Mobile Communications (GSM), GSM Enhanced Data Evolution (EDGE), Universal Mobile Telecommunications System (UMTS), 2G, 3G, 4G, 5G, Long Term Evolution (LTE), Code, Space, Frequency, Polarization and / or Time Division Multiple Access (CDMA, SDMA, FDMA, PDMA, TDMA), and similar and related protocols, coding, technologies, networks and services.

[0053] Such expected on-vehicle and off-vehicle devices and components are configured to implement bidirectional wired and wireless communications between components and systems of the vehicle 100, the CAN 150 and other external devices and systems, and PANs, LANs, and WANs, among other devices and components. The A / D circuit 225 is configured to implement analog-to-digital and digital-to-analog signal conversion. Among other devices and components, the auxiliary input 220 and the USB 230 can also implement wired and wireless Ethernet, on-board diagnostics (OBD, OBD II), free space optical communications (such as infrared (IR) data association (IrDA) and non-standardized consumer IR data communication protocols, IEEE1394 (FireWire.TM. (Apple Corp.), LINK.TM. (Sony), Lynx.TM. (Texas Instruments)), EIA (Electronic Industries Association) serial protocol, IEEE 1284 (Centronics port protocol), S / PDIF (Sony / Philips digital interconnect format) and USB-IF (USB Developer Forum) and similar data protocols, signaling and communication capabilities in some configurations).

[0054] The auxiliary input 220 and A / D circuit 225, USB 230, NFC 235, WRT 240 and / or CMT 245 are coupled to, integrated with and / or may include the following components: integrating amplifiers, signal conversion and / or signal modulation circuits, which are configured to attenuate, convert, amplify and / or transmit signals, and are also configured to receive various analog and / or digital input signals, data and / or information, which are processed and conditioned and transmitted to various wired and wireless networks and controllers and transmitted between them.

[0055] Such contemplated wired and wireless networks and controllers include, for example, but not limited to, CAN 150, VCS 145, and other controllers and networks of vehicle 100. Auxiliary input 220, A / D circuit 225, USB 230, NFC 235, WRT 240, and / or CMT 245 and associated hardware, software, and / or circuitry are compatible and configured to at least receive, transmit, and / or communicate at least one and / or one or more of various wired and wireless signals, signaling, data communications, and / or data streams (WS), as well as data such as navigation, audio and / or visual and / or multimedia signals, commands, control logic, instructions, information, software, programming, and similar and related data and information forms.

[0056] Additionally, it is contemplated that one or more input and output data communications, audio and / or visual devices are integrated with, coupled to and / or connectable to the auxiliary input 220, A / D circuitry 225, USB 230, NFC 235, WRT 240 and / or CMT 245, as well as other contemplated controllers and wired and wireless networks within the vehicle 100 and in some cases external to the vehicle 100. For example, the one or more input and output devices include a microphone 250, a voice processing and recognition device and subsystem 255, a speaker 260, an additional display 265, a camera 270, a nomadic and mobile device (NMD) 275 and / or a key fob (such as a remote and / or keyless car starter and keyless entry device 280, etc.), each of which includes at least one and / or one or more integrated signaling and communication antennas and / or transceivers (ATs).

[0057] Such input and output devices are and / or may be selectable, connectable, synchronized, paired and / or actuatable with an input selector, which may be any HSC; and may also include, incorporate and / or be integrated with and / or be part of: GUI 200 and intended hardware and software SWCs, controls, buttons and / or switches. As already noted, such HSC may be hardware or software or a combination thereof, and may be configured using one or more predetermined, default and adjustable factory and / or driver controls, profiles and / or preferences 180.

[0058] Contemplated microphone 250, speech processing and recognition devices and subsystems 255, speakers 260, additional displays 265, cameras 270, NMD 275 and / or other portable auxiliary devices may also include, for example but not limited to: cellular phones, mobile phones, smart phones, satellite phones and modems and communication devices, tablet computers, personal digital assistants, personal media players, key fob security and data storage devices, personal health devices, laptop computers, portable wireless cameras, headphones and headsets (which may include microphones, wired and wireless microphones, portable NFC speakers and stereo devices and players), portable GPS and GNSS devices, and similar devices and components (each of which may include an integrated transceiver and antenna AT, wired and plug-in connectors DC and related components for wired and wireless multimedia and data communication signals WS).

[0059] Such intended input, output and / or communication devices, components, subsystems and systems on the vehicle 100 are and / or can be configured to communicate bidirectionally with external near and far nomadic, portable and / or mobile devices 275, networks and systems (V2X) via wired and wireless data connections (DC) and wired and wireless signals and signaling and data communications and flows WS, which systems may include, for example, road and infrastructure communication systems (V2I) such as hotspots and wireless access points (HS / WAP), nano- and micro- and conventional cellular access points and towers (CT), external routers (XR) and related and accessible external and remote networks, systems and servers.

[0060] Continue to refer to the figures (including Figure 1 and Figure 2), those with knowledge in the relevant technical field will understand that the present disclosure contemplates that the vehicle 100 includes at least one and / or one or more in-vehicle and / or on-board controllers, such as VSC 140, VCS 145, and other controllers coupled to an in-vehicle or on-board transceiver AT, such as those described in conjunction with USB 230, and a local short-range transceiver, such as NFC 235, WRT 240 (including expected wireless WiFi and Bluetooth.TM. and Bluetooth.TM. Low Energy or BLE transceivers) and / or a longer range cellular transceiver (such as CMT 245). The controllers 140, 145 and transceiver AT are configured to detect WS and connect to nearby or proximal or distal wired and wireless network devices with WS within range, as well as third-party, off-vehicle, external devices, such as nomadic, portable and / or mobile or nomadic mobile devices 275, and one or more key fobs 280 (KFOB, Figure 1 ).

[0061] The vehicle 100 also includes various controllers that are configured via one or more local shorter range transceivers to securely register, pair and / or couple at least one of such key fobs 280 via at least one and / or one or more electronic security tokens, authentication codes (AC) 285 and / or similar such secure communication codes, which enable the controller to identify such devices and enhance communication security between the devices. Each manufacturer of the intended vehicle 100 typically includes one or more key fobs 280 pre-registered with each such vehicle manufactured, and also incorporates various procedures for registering and / or pairing such key fobs 280 with controllers, systems, devices and / or components of the vehicle 100. The controller is also configured to communicate with the vehicle 100 via an external network ( Figure 1 ) autonomously communicates with a remote server via one or more longer range cellular transceivers to monitor and detect signals WS received from the key fob 280 via the remote server and an external network, the signals including AC 285 and remote control commands (RCC) 290.

[0062] In response to a key fob signal received from a remote server (including AC 285 and RCC 290), the onboard controller in other variations of the vehicle 100 is configured to autonomously modify the operation of at least one component of the vehicle 100 according to RCC 290. The controller of the vehicle 100 according to the present disclosure continuously monitors, detects and responds to such RCC 290 and AC 285 without user interaction, so that autonomous capabilities are enabled. Such operation of at least one component, part and / or system of the vehicle 100 includes, but is not limited to (for example purposes): adjusting the components and systems of the vehicle 100 according to one or more driver preferences that can be stored in the repository 180 and associated with the key fob 280, AC 285 and / or RCC 290. For purposes of example and not limitation, such RCC 290 includes commands to lock or unlock a door or trunk of the vehicle 100, start or shut down the engine 115 and / or EM 120, charge the battery 130, adjust the cabin temperature of the vehicle 100 based on driver preferences stored in the repository 180, adjust passenger seat temperature or position, arm or disarm the security system, and adjust at least one of one or more other components, systems and / or devices of the vehicle 100 (such as an infotainment system), etc.

[0063] In other variations, the key fob is also registered on and / or paired with a mobile device, such as NMD 275, by and utilizing an authentication code. The mobile device 275 is also configured to monitor, detect, and autonomously respond to a registered and / or paired key fob 280 without any required user interaction with the mobile device 275. Thus, once such an NMD 275 has registered and paired with a key fob 280, the mobile device 275 autonomously responds to the remote server and transmits the AC 285 and RCC 290 to the remote server without requiring or requiring the user to unlock, interact with, and / or respond to the mobile device 275 and / or key fob 280 in any way.

[0064] In this manner, such NMD 275 autonomously extends the range of the key fob 280 beyond the nominal range of such devices by utilizing the cellular, WiFi, and / or other communication capabilities of the mobile device 275. By way of further example and not limitation, many such key fobs 280 are BLE devices that utilize a relatively low power transmitter designed for use over short distances that communicates with a transceiver of the vehicle 100, such as a Bluetooth.TM. configured WRT 240, which in combination achieve a radio communication range in free air with no obstructions of between about 1 to 30 meters or so. Obstructions (such as buildings, walls, vehicle doors, etc.) can greatly reduce such distances. Therefore, the innovation of the present disclosure that achieves an extension of the range of the radio communication distance of the key fob 280 by autonomously utilizing such mobile devices and NMD 275 is an important advantage.

[0065] According to the present disclosure, the controller of the vehicle 100 is configured to autonomously monitor, detect and respond to such AC 285 and RCC 290 that may originate from the key fob 280 via the NMD 275 and the remote server. In other examples and variations, the in-vehicle and / or on-board controller of the vehicle 100 is also configured to respond to the wireless signal WS from the remote server of the key fob 280 when the key fob 280 is beyond the radio communication distance range of the on-board wireless vehicle transceiver and / or is outside the said range. When the controller of the vehicle 100 does not detect the key fob 280 within the range of the vehicle wireless transceiver WRT 240, the controller in some arrangements of the present disclosure is also configured to autonomously and periodically communicate with the remote server through the cellular external network transceiver CMT 245 to detect one or more of AC 285 and RCC 290 from the key fob 280.

[0066] Such in-vehicle wireless transceivers include, for example, but not limited to, WRT 240 or other transceivers, which are typically configured as Bluetooth.TM. and / or WiFi devices and are configured for vehicle area or personal area networks (VAN, PAN), and whose communication signal range distance may be only up to about 100 meters without obstacles. The radio communication range of such wireless vehicle transceivers WRT240 is substantially smaller than the cellular external network transceiver of the vehicle 100, such as CMT245, for example, which typically has a larger radio communication distance range of more than 5 kilometers and up to 35 kilometers.

[0067] Conversely, the onboard controller is further configured in other modifications to respond to detecting a registered and / or paired key fob 280 within the radio communication range of the onboard wireless vehicle transceiver WRT240 and interrupt communication with the remote server so that communication is enabled directly between the key fob 280 and the vehicle 100. Additional configurations include an onboard controller configured to respond to not detecting a key fob 280 within the radio communication range of the onboard wireless vehicle transceiver WRT 240 but detecting a mobile device or NMD 275, to periodically and autonomously communicate with the mobile device 275 via the wireless transceiver WRT 240 to detect one or more of AC 285 and / or RCC 290 from the key fob 280.

[0068] The present disclosure also contemplates a controller of the vehicle configured to respond to a mobile device or NMD 275 configured as a standalone and / or separate KFOB-NMD 275 and configured to generate a key fob signal WS including AC 285 and / or RCC 290. In this arrangement, the present disclosure involves the KFOB-NMD 275 pairing with the key fob 280 and / or registering the key fob 280 to receive and store both the AC 285 and various possible RCCs 290 that were enabled by the original equipment key fob 280. Furthermore, such a KFOB-mobile device 275 can then be used independently of the key fob 275 to generate AC 285 and / or RCC 290 from the communication and transmit it to a remote server and / or directly to the transceiver WRT 240 of the vehicle 100. As with the other adaptations, the controller of the vehicle 100 also monitors, detects and responds to the key fob 280 and / or NMD, i.e., any one of the key fob or KFOB-NMD 275 being within and out of range of the vehicle transceiver WRT 240, and switches between monitoring the key fob signal WS directly from the key fob 280, NMD 275, KFOB-NMD 275 and / or a remote server.

[0069] Each of the variations, arrangements and modifications of the present disclosure also includes those which can be further described by continuing to refer to Figure 1 As well as the methods of operation which can now be further understood with reference to 2. For purposes of further example and not limitation, such methods include utilizing the described controller, transceiver and related components, devices and systems (which are also generally referred to herein collectively and / or in combination as controller 300 ( Figure 2 )) is a method for controlling a vehicle 100. Starting from step 305, the method further includes, at step 310, registering the key fob 280 with one or more controllers 300 and / or NMD 275 of the vehicle 100 via the AC 285.

[0070] The method for controlling the vehicle 100 further includes, at step 315, autonomously detecting by the in-vehicle controller 300 whether the NMD 275 configured as the key fob 280 and / or the key fob 280 is within the radio communication range of the wireless transceiver WRT 240 of the vehicle 100. If the key fob 280 and / or the NMD, i.e., the key fob 275 (KFOB-NMD, Figure 2 ), then in step 320, the method of the controller 300 of the vehicle 100 includes autonomously and periodically communicating with a remote server via the cellular external network transceiver CMT 245 to monitor and detect signals from such KFOB-NMD 275 and / or key fob 280.

[0071] At step 325 of the intended method of the controller 300 and the vehicle 100, monitoring and detecting the key fob signal WS received from the remote server, and further detecting whether the signal WS includes one or more and / or at least one of the AC 285 and / or the RCC 290. If not, the method returns control to the start step 305. Otherwise, the method of the controller 300 also includes: at step 330, autonomously modifying the operation of at least one component of the vehicle 100 according to the RCC 290. As with other configurations described elsewhere herein, including, for example, but not limited to, modifying the operation with the following commands: unlocking and locking the doors or trunk, starting or shutting down the engine 115 or the EM 120, charging one or more batteries 130, adjusting the cabin temperature according to the driver's preferences stored in the repository 180, adjusting the passenger seat temperature or position, arming or disarming the security system, and adjusting at least one of other components, systems and / or devices (such as the infotainment system) of the vehicle 100, etc.

[0072] 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, 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 various embodiments can be combined to form other embodiments of the present invention.

Claims

1. A vehicle, comprising: a vehicle-mounted controller coupled to an external network transceiver and configured to: register a key fob via an authentication code, communicate autonomously with a remote server, and in response to a key fob signal received from the remote server including the authentication code and a remote control command, autonomously modify the operation of at least one component of the vehicle according to the remote control command, wherein a mobile device is enabled by the key fob to pair with the key fob, and the vehicle-mounted controller is further configured to register the mobile device with the authentication code, and the mobile device is configured as the key fob and configured to generate the key fob signal including the remote control command and transmit it to the vehicle via Bluetooth, WiFi or the remote server.

2. The vehicle according to claim 1, comprising: the key fob is further configured to be registered by a mobile device via the authentication code and configured to generate the remote control command, the mobile device is further configured to communicate with the remote server and further configured to: in response to the remote control command, autonomously transmit the authentication code and the remote control command to the remote server.

3. The vehicle according to claim 1, comprising: the vehicle-mounted controller is further configured to, when the key fob is outside the range of a vehicle-mounted wireless vehicle transceiver configured with a communication signal range smaller than that of the external network transceiver, respond to the key fob signal from the remote server.

4. The vehicle according to claim 1, comprising: the vehicle-mounted controller is further configured to: in response to detecting the key fob within the range of a vehicle-mounted wireless vehicle transceiver configured with a communication signal range smaller than that of the external network transceiver, interrupt communication with the remote server.

5. The vehicle according to claim 1, comprising: the vehicle-mounted controller is further configured to: in response to not detecting the key fob within the range of a vehicle-mounted wireless vehicle transceiver configured with a communication signal range smaller than that of the external network transceiver, communicate autonomously and periodically with the remote server via the external network transceiver to detect the remote control command from the key fob.

6. The vehicle according to claim 1, comprising: the vehicle-mounted controller is further configured to: in response to not detecting the key fob within the range of a vehicle-mounted wireless vehicle transceiver configured with a communication signal range smaller than that of the external network transceiver and detecting the mobile device, communicate periodically and autonomously with the mobile device via the vehicle-mounted wireless vehicle transceiver to detect the remote control command from the key fob.

7. The vehicle according to claim 1, comprising: the vehicle-mounted controller is further configured to: in response to not detecting the mobile device acting as the key fob within the range of a vehicle-mounted wireless vehicle transceiver configured with a communication signal range smaller than that of the external network transceiver, communicate periodically and autonomously with the remote server via the external network transceiver to detect the remote control command from the mobile device acting as the key fob.

8. The vehicle according to claim 1, comprising: The remote control command includes at least one of unlocking, locking, engine starting, cabin temperature adjustment, arming / disarming the security system, and driver preference commands.

9. A vehicle, comprising: A controller coupled to a local transceiver and a cellular transceiver and configured to: Register a key fob by the local transceiver with an authentication code, Autonomously communicate with a remote server via the cellular transceiver, and In response to a key fob signal received from the remote server including the authentication code and a remote control command, Autonomously modify the operation of at least one component of the vehicle according to the remote control command, wherein a mobile device is enabled by the key fob to pair with the key fob, and the controller is further configured to register the mobile device with the authentication code, and the mobile device is configured as the key fob and configured to generate the key fob signal including the remote control command and send it to the vehicle via Bluetooth, WiFi, or the remote server.

10. The vehicle according to claim 9, comprising: The key fob is configured to be registered by a mobile device with the authentication code and configured to generate the remote control command, The mobile device is further configured to communicate with the remote server and further configured to: In response to the remote control command, Autonomously transmit the authentication code and the remote control command to the remote server.

11. The vehicle according to claim 9, comprising: The controller is further configured to: In response to not detecting the key fob within the range of the local transceiver and detecting the mobile device, Autonomously and periodically communicate with the mobile device via the local transceiver to detect the remote control command from the key fob.

12. The vehicle according to claim 9, comprising: The controller is further configured to: In response to not detecting the mobile device acting as the key fob within the range of the local transceiver, Autonomously and periodically communicate with the remote server via the cellular transceiver to detect the remote control command from the mobile device acting as the key fob.

13. A method for controlling a vehicle, comprising: Via an in-vehicle controller coupled to an external network transceiver: Register a key fob with an authentication code, Autonomously communicate with a remote server via the external network transceiver, and In response to a key fob signal received from the remote server including the authentication code and a remote control command, Autonomously modify the operation of at least one component of the vehicle according to the remote control command, wherein a mobile device is enabled by the key fob to pair with the key fob, and the in-vehicle controller is further configured to register the mobile device with the authentication code, and the mobile device is configured as the key fob and configured to generate the key fob signal including the remote control command and send it to the vehicle via Bluetooth, WiFi, or the remote server.

14. The method according to claim 13, comprising: The key fob is configured to be registered by the mobile device using the authentication code and is configured to generate the remote control command, The mobile device is further configured to communicate with the remote server, in response to the remote control command, autonomously transmit the authentication code and the remote control command to the remote server.

15. The method according to claim 13, further comprising: by the vehicle-mounted controller, in response to not detecting the key fob within the range of the vehicle-mounted wireless transceiver coupled to the vehicle-mounted controller and detecting the mobile device, autonomously and periodically communicate with the mobile device through the vehicle-mounted wireless transceiver to detect the remote control command from the key fob.

16. The method according to claim 13, further comprising: by the vehicle-mounted controller, in response to not detecting the mobile device as the key fob within the range of the vehicle-mounted wireless transceiver coupled to the vehicle-mounted controller, autonomously and periodically communicate with the remote server through the external network transceiver to detect the remote control command from the mobile device as the key fob.

Images