Intelligent vehicle system and control logic for enabling vehicle charging using intelligent wireless connectivity
The intelligent wireless charging authorization of transportation in a Level 2 AC EVCS environment is achieved through encrypted wireless connectivity and location time inspection protocols, which solves the problem of smart charging on old charging stations, improves the safety and automation of the charging process, and reduces the New charging station demand.
Patent Information
- Application Number
- CN202311396277.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-10
- Filing Date
- 2023-10-25
- Publication Date
- 2024-11-12
AI Technical Summary
The prior art is difficult to implement intelligent and secure wireless charging authorization on charging stations that do not support digital programmable logic controllers, especially in a Level 2 AC EVCS environment that lacks PLC communication capabilities, making it difficult to automate the charging process of vehicles.
Using encrypted wireless connectivity over WiFi or SRC protocols, two-step bidirectional position and time check protocols and triangulation techniques are used to identify and verify the real-time location of the main vehicle, and identity detection and authentication are performed with encrypted unique ID embedded in wireless messages. , thereby achieving contactless charging authorization and operation.
It realizes intelligent and safe charging of transportation tools on old charging stations, extends the operating life of charging stations, reduces the demand for new charging stations, increases the number and types of charging characteristics of electric vehicles, and reduces the Cost and complexity.
Smart Images

Figure CN118928136A_ABST
Abstract
Description
[0001] introduce
[0002] The present disclosure generally relates to electrical systems for charging motor vehicles. More specifically, aspects of the present disclosure relate to systems and methods for governing vehicle charging using an alternating current (AC) power supply.
[0003] Current production motor vehicles, such as today's automobiles, are initially equipped with a powertrain that operates to propel the vehicle and power the vehicle's onboard electronics. For example, in automotive applications, the vehicle powertrain is typically represented by a prime mover that delivers drive torque to the vehicle's final drive system (e.g., differential, axle shaft, corner module, roadwheel, etc.) through an automated or manually shifted power transmission. Automobiles have historically been powered by reciprocating piston internal combustion engine (ICE) assemblies due to their ready availability and relatively low cost, light weight, and overall high efficiency. As some non-limiting examples, such engines include compression ignition (CI) diesel engines, spark ignition (SI) gasoline engines, two-stroke, four-stroke, and six-stroke frames, and rotary engines. Hybrid electric vehicles and all-electric vehicles (collectively referred to as "electric-drive vehicles"), on the other hand, utilize alternative power sources to propel the vehicle and thus minimize or eliminate reliance on fossil fuel-based engines for traction power.
[0004] A full electric vehicle (FEV) - colloquially known as an "electric vehicle" - is a type of electrically driven vehicle configuration that completely omits the internal combustion engine and accompanying peripheral components from the powertrain, instead relying on a rechargeable energy storage system (RESS) and traction motors for vehicle propulsion. In a battery-based FEV, the engine components, fuel supply system, and exhaust system of an ICE-based vehicle are replaced with a single or multiple traction motors, rechargeable battery cells, and battery cooling and charging hardware. In contrast, a hybrid electric vehicle (HEV) powertrain employs multiple traction power sources to propel the vehicle, most commonly operating an internal combustion engine component in conjunction with a battery-powered or fuel cell-powered traction motor. Since hybrid-electric vehicles are able to obtain their power from sources other than the engine, the HEV engine can be fully or partially shut down when the vehicle is propelled by (one or more) electric motors.
[0005] The high voltage (HV) electrical system governs the transfer of power between the traction motor and the rechargeable battery packs that supply the necessary power to operate many hybrid electric and all-electric powertrains. To provide the power capacity and energy density required to propel the vehicle at the desired speed for the desired range, contemporary traction battery packs group multiple battery cells (e.g., 8-16+ cells / stack) into individual battery modules (e.g., 10-40+ modules / pack) that are electrically interconnected to one another and mounted on the vehicle chassis, for example, via a battery pack housing or support tray. Located on the battery side of the HV electrical system is a front-end DC to DC power converter that is electrically connected to the battery pack(s) in order to increase the voltage level supplied to the main DC bus and the AC / DC power inverter module (PIM). Arranged across the positive and negative terminals of the main DC bus are high frequency bulk capacitors that provide electrical stability and store supplemental electrical energy. A dedicated electronic battery control module (EBCM) governs the operation of the battery pack(s) and traction motor(s) by operating in coordination with the powertrain control module (PCM) and the power electronics pack for each electric machine.
[0006] As hybrid and electric vehicles become more common, infrastructure is being developed and deployed to make the daily use of such vehicles feasible and convenient. There are many form factors for electric vehicle supply equipment (EVSE) for recharging electric drive vehicles, including residential electric vehicle charging stations (EVCS) purchased and operated by vehicle owners (e.g., installed in the owner's garage), publicly accessible EVCS provided by public utilities or private retailers (e.g., at municipal or commercial charging facilities), and advanced high-voltage fast charging stations used by manufacturers, dealers, and service stations. (e.g., OEM multi-coupler 360+kW DCFC supercharger). For example, plug-in hybrid and electric vehicles can be recharged by physically connecting the charging cable of the EVSE to the complementary charging port of the vehicle. In contrast, wireless AC charging systems use electromagnetic field (EMF) induction to provide vehicle charging capabilities without the need for charging cables and cable ports. In most countries, standardized conductive charger couplers are used to connect EVCS to the HV electrical system of the vehicle. Plug-in vehicles are equipped with a standardized charger inlet port for electrically pairing with a charger coupler and locking the coupler in place to prevent inadvertent or unwanted uncoupling. Summary of the invention
[0007] This article proposes a vehicle charging system with control logic using encrypted wireless connectivity to provide intelligent vehicle charging, a method for manufacturing such a system, and a method for operating such a system, as well as a wireless-enabled vehicle interoperable with such a system. As an illustration and not limitation, a system and method for enabling vehicle charging authorization using smart WiFi or SRC connectivity on a Level 2 ACEVCS is proposed. In order to provide intelligent charging capabilities across legacy charging stations that do not support digital programmable logic controller (PLC) communication (comm), an encrypted vendor extension is created for secure connectionless identity detection; a wireless comm handshake embedded with an encrypted vendor extension is used to implement contactless EV charging authorization. A two-step bidirectional location and time check protocol can be used to identify and triangulate the real-time location of the host vehicle. In tandem, the host vehicle and the EVCS can cooperatively exchange bidirectional data identification (ID) data using wireless comm and timestamps during vehicle approach and insertion / EMF coupling to identify the vehicle adjacent to the EVCS and establish different charger identities for the EVCS among multiple charging stations. For existing legacy charger installations in a shared parking environment, the self-diagnostic algorithm can selectively enable / disable EV charging authorization using customer / vehicle ID data. The smart charging protocol can selectively upgrade or downgrade the host vehicle's unique identification code, which is determined by the back-end (BO) vehicle service provider (e.g., or ) may be verified to identify and track the host vehicle relative to the EVCS from approach to insertion, for example using existing properties / capabilities of available wireless protocols.
[0008] Aspects of the present disclosure are directed to vehicle charging systems, system control logic, and memory stored instructions for enabling smart charging operations. In an example, a method for controlling charging operations of a host vehicle having a rechargeable battery pack, a wireless communication device, and a resident or remote controller or module or a network of controllers / modules (collectively, "controllers") is presented. The representative method includes, in any order and in any combination with any of the options and features disclosed above and below: retrieving, via a vehicle controller, a unique ID assigned to a host vehicle from a resident or remote memory device, for example; embedding, via the vehicle controller, the unique ID in a wireless message (e.g., a WiFi packet, a V2X DSRC beacon, etc.), for example, in response to approaching the EVCS, the embedding including encrypting the unique ID and inserting the unique ID into a dedicated extension frame within the wireless message (e.g., between a payload and a trailer frame or in one of the payload and trailer frames); broadcasting, via the vehicle controller, a wireless message with the embedded and encrypted unique ID from a wireless communication device to one or more EVCSs; transmitting, for example, from the EVCS controller to a back-end vehicle service provider (e.g., an “off-board” cloud computing host system) the encrypted unique ID parsed from the wireless message; and initiating, via the EVCS controller, one or more charging operations of a battery pack of the host vehicle with the EVCS, for example, in response to the BO vehicle service provider decrypting and authenticating the unique ID.
[0009] Aspects of the present disclosure are also directed to a computer-readable medium (CRM) for enabling smart charging operations of a motor vehicle. In an example, a non-transitory CRM stores instructions that can be executed by a controller of a host vehicle and / or a controller of an EVCS. These instructions, when executed, cause the controller to perform operations including: retrieving a unique ID assigned to the host vehicle from a memory device via a vehicle controller; in response to approaching the EVCS, embedding the unique ID in a wireless message via the vehicle controller, embedding including an encrypted unique ID and inserting the encrypted unique ID into a dedicated extended frame within the wireless message; broadcasting a wireless message from a wireless communication device to the EVCS via the vehicle controller, with the encrypted unique ID embedded in the wireless message; transmitting the encrypted unique ID parsed from the wireless message from the EVCS controller to a back-end vehicle service provider; and in response to the BO vehicle service provider decrypting and authenticating the unique ID, starting a charging operation for the rechargeable battery pack of the host vehicle through the EVCS via the EVCS controller.
[0010] Additional aspects of the present disclosure are directed to motor vehicles having an intelligent vehicle system for enabling intelligent vehicle charging. As used herein, the terms "vehicle" and "motor vehicle" can be interchangeably and synonymously used to refer to any relevant vehicle platform, such as passenger vehicles (ICE, HEV, FEV, fuel cell, fully and partially autonomous, etc.), commercial vehicles, industrial vehicles, tracked vehicles, off-road and all-terrain vehicles, motorcycles, agricultural equipment, boats, aircraft, etc. In an example, the vehicle charging network includes one or more main vehicles, each of which includes a vehicle body with a passenger compartment, a plurality of road wheels mounted to the vehicle body (e.g., via a corner module coupled to an integral or non-load-bearing chassis), and other standard original equipment. For electric drive applications, one or more electric traction motors operate alone (e.g., for FEV powertrains) or in combination with an internal combustion engine (e.g., for HEV powertrains) to selectively drive one or more road wheels to propel the vehicle. A traction battery pack including a plurality of battery cells is mounted on the vehicle and is operable to power the traction motor(s).
[0011] Continuing with the previous discussion, each master vehicle is also equipped with a vehicle controller (e.g., a single controller, a network of controllers, a resident / remote controller or module, etc.) that is programmed to access a resident or remote memory device to retrieve a unique ID assigned to that particular master vehicle. The vehicle controller then embeds the unique ID into a wireless message, including encrypting the unique ID and inserting the unique ID into a dedicated extended frame within the wireless message. The vehicle controller broadcasts the wireless message with the embedded ID from the resident wireless communication device of the master vehicle. The corresponding EVCS controller of each EVCS within the vicinity of the master vehicle can receive the broadcast message and concomitantly parse the encrypted unique ID from the wireless message. The EVCS controller then transmits the parsed and encrypted unique ID to the BO vehicle service provider for evaluation and charging authorization. When the BO vehicle service provider decrypts and authenticates the unique ID, the EVCS controller responsively starts the charging operation of the rechargeable battery pack of the master vehicle through the EVCS.
[0012] For any of the disclosed systems, methods, and CRMs, the EVCS controller may determine the charger-to-vehicle distance between the EVCS and the wireless communication device of the host vehicle using wireless positioning technology. The EVCS controller then transmits the charger-to-vehicle distance to the BO vehicle service provider. In this instance, the vehicle controller may determine the vehicle-to-charger distance between the host vehicle and the EVCS using one or more on-vehicle sensing devices of the host vehicle. The vehicle controller then transmits the vehicle-to-charger distance to the BO vehicle service provider, for example, via the EVCS. In this instance, the BO vehicle service provider may calculate the distance differential as the absolute value of the mathematical difference between the vehicle-to-charger distance and the charger-to-vehicle distance. The BO may then determine whether the calculated distance differential is less than a preset distance differential threshold; if so, the BO vehicle service provider may conclude that the unique ID is authentic and output an electronic notification indicating it to the EVCS controller.
[0013] For any of the disclosed systems, methods, and CRMs, a vehicle controller may determine a vehicle coupling timestamp and transmit the vehicle coupling timestamp to a BO vehicle service provider, for example, via an EVCS, indicating when the host vehicle was operably coupled to the EVCS to charge the vehicle's battery pack. Similarly, an EVCS controller may determine a charger coupling timestamp and transmit the charger coupling timestamp to a BO vehicle service provider, indicating when the host vehicle was operably coupled to the EVCS. In this instance, the BO may calculate the time difference as the absolute value of the mathematical difference between the vehicle output timestamp and the EVCS output timestamp. The BO may then determine whether the calculated time difference is less than a preset time difference threshold; if so, the BO vehicle service provider may conclude that the unique ID of the host vehicle is authentic and output an electronic notification indicating the same to the EVCS controller.
[0014] For any of the disclosed systems, methods, and CRMs, the vehicle controller may determine a vehicle geolocation data set indicating the real-time location of the host vehicle and transmit the vehicle geolocation data set to a BO vehicle service provider, for example, via the EVCS. Likewise, the EVCS controller may determine an EVCS geolocation data set indicating the real-time location of the EVCS and transmit the EVCS geolocation data set to the BO vehicle service provider. In this instance, the BO may determine whether the vehicle's geolocation data / real-time location is approximately equal to the EVCS's geolocation data / real-time location; if so, the BO vehicle service provider may conclude that the host vehicle's unique ID is authentic and output an electronic notification indicating the same to the EVCS controller.
[0015] For any of the disclosed systems, methods, and CRMs, when approaching the EVCS, the vehicle controller may responsively encrypt a unique shared message and embed it in a wireless message (e.g., within a dedicated extended frame of the encrypted unique ID). In this instance, the EVCS controller may use the unique shared message embedded in the wireless message to determine whether the host vehicle is within a predetermined proximity of the EVCS. As another option, the vehicle controller may determine whether the host vehicle is operably coupled to the EVCS for charging a rechargeable battery pack. In response to the host vehicle being operably coupled to the EVCS, the vehicle controller may append a vehicle geolocation data set indicating the real-time location of the host vehicle and a vehicle coupling timestamp indicating the time when the host vehicle was operably coupled to the EVCS to the wireless message. In this instance, the BO vehicle service provider may authenticate the unique ID based at least in part on the vehicle's geolocation data set and the vehicle's coupling timestamp.
[0016] For any of the disclosed systems, methods, and CRMs, the host vehicle may be operably coupled to the EVCS by manually inserting an electrical connector plug of the EVCS into a plug port of the host vehicle. As another option, the host vehicle may be operably coupled to the EVCS by aligning or otherwise pairing a wireless power transfer (WPT) receiving component (e.g., EMF coil) of the host vehicle with a WPT transmitter component (e.g., EMF pad) of the EVCS as described above. In yet another option, the wireless communication device may take a variety of different form factors, including a WiFi hotspot device and / or a short range communication (SRC) device. In this instance, the wireless message may have the nature of a network data packet and / or a fast charging communication handshake. While not limiting per se, the disclosed features may be particularly applicable to vehicle charging stations in the form of Level 2 AC EVCS, which are operable to output approximately 60 amps (A) or less and 240 volts (V) or less, and are characterized by a lack of PLC communications capabilities.
[0017] A method for controlling a charging operation of a host vehicle is disclosed, the host vehicle having a vehicle controller, a wireless communication device, and a rechargeable battery pack connectable to an electric vehicle charging station (EVCS) having an EVCS controller, the method comprising: retrieving a unique ID assigned to the host vehicle from a memory device via the vehicle controller; embedding the unique ID into a wireless message via the vehicle controller in response to approaching the EVCS, the embedding including an encrypted unique ID and inserting the encrypted unique ID into a dedicated extended frame within the wireless message; broadcasting a wireless message from the wireless communication device to the EVCS via the vehicle controller, the wireless message having the encrypted unique ID embedded in the wireless message; transmitting the encrypted unique ID parsed from the wireless message from the EVCS controller to a backend (BO) vehicle service provider; and starting a charging operation of the EVCS on the rechargeable battery pack of the host vehicle in response to the BO vehicle service provider decrypting and authenticating the unique ID via the EVCS controller.
[0018] The method further includes determining, via the EVCS controller, a charger-to-vehicle distance between the EVCS and the wireless communication device using wireless positioning technology; and transmitting, via the EVCS controller, the charger-to-vehicle distance to a BO vehicle service provider.
[0019] The method further includes determining, via the vehicle controller, a vehicle-to-charger distance between the host vehicle and the EVCS using an on-vehicle sensing device of the host vehicle; and transmitting, via the vehicle controller, the vehicle-to-charger distance to a BO vehicle service provider through the EVCS.
[0020] The method further includes: calculating the distance difference as the absolute value of the mathematical difference between the vehicle-to-charger distance and the charger-to-vehicle distance; and determining whether the distance difference is less than a preset distance difference threshold, wherein the BO vehicle service provider authenticates the unique ID based in part on the distance difference being less than the preset distance difference threshold.
[0021] The method further includes: transmitting a vehicle coupling timestamp via the vehicle controller to the BO vehicle service provider through the EVCS, at which the host vehicle is operably coupled to the EVCS to charge the rechargeable battery pack; and transmitting a charger coupling timestamp via the EVCS controller to the BO vehicle service provider, at which the host vehicle is operably coupled to the EVCS.
[0022] The method further includes: calculating the time difference as the absolute value of a mathematical difference between the vehicle coupling timestamp and the charger coupling timestamp; and determining whether the time difference is less than a preset time difference threshold, wherein the BO vehicle service provider authenticates the unique ID based in part on the time difference being less than the preset time difference threshold.
[0023] The method further includes: transmitting a vehicle geolocation dataset indicating the real-time location of the host vehicle to a BO vehicle service provider via the vehicle controller through the EVCS; transmitting an EVCS geolocation dataset indicating the real-time location of the EVCS to the BO vehicle service provider via the EVCS controller; and determining whether the vehicle geolocation dataset is substantially equal to the EVCS geolocation dataset, wherein the BO vehicle service provider authenticates the unique ID based in part on the vehicle geolocation dataset being approximately equal to the EVCS geolocation dataset.
[0024] The method further includes embedding, via the vehicle controller, a unique shared message in the wireless message in response to approaching the EVCS, and determining, via the EVCS controller, in response to receiving the unique shared message embedded in the wireless message, that the host vehicle is within a predetermined proximity of the EVCS.
[0025] The method further includes: determining, via a vehicle controller, that a host vehicle is operably coupled to an EVCS for charging a rechargeable battery pack; and appending, via the vehicle controller, a vehicle geolocation data set indicating a real-time location of the host vehicle and a vehicle coupling timestamp of the host vehicle being operably coupled to the EVCS to a wireless message in response to the host vehicle being operably coupled to the EVCS, wherein the BO vehicle service provider authenticates the unique ID based in part on the vehicle geolocation data set and the vehicle coupling timestamp.
[0026] In the method, operably coupling the host vehicle to the EVCS includes: inserting an electrical connector plug of the EVCS into a plug port of the host vehicle; and / or pairing a wireless power transfer (WPT) receiving component of the host vehicle with a WPT transmitter component of the EVCS.
[0027] In the method, the wireless communication device comprises a WiFi hotspot device and / or a short range communication (SRC) device, and wherein the wireless message comprises a network data packet and / or a fast charging communication handshake.
[0028] In the method, the EVCS is an alternating current (AC) charging station characterized by lack of programmable logic controller (PLC) communication capabilities and operable to output power at approximately 60 amperes (A) or less and 240 volts (V) or less.
[0029] A non-transitory computer-readable medium storing instructions executable by a host vehicle having a vehicle controller and / or an electric vehicle charging station (EVCS) having an EVCS controller is disclosed, the host vehicle including a wireless communication device and a rechargeable battery pack connectable to the EVCS, the instructions, when executed, causing the vehicle controller and / or the EVCS controller to perform operations including: retrieving a unique ID assigned to the host vehicle from a memory device via the vehicle controller; embedding the unique ID into a wireless message, including an encrypted unique ID and inserting the encrypted unique ID into a dedicated extended frame within the wireless message, via the vehicle controller in response to approaching the EVCS; broadcasting a wireless message from the wireless communication device to the EVCS, via the vehicle controller, the wireless message having the encrypted unique ID embedded in the wireless message; transmitting the encrypted unique ID parsed from the wireless message from the EVCS controller to a back-end (BO) vehicle service provider; and initiating a charging operation of the EVCS to the rechargeable battery pack of the host vehicle in response to the BO vehicle service provider decrypting and authenticating the unique ID, via the EVCS controller.
[0030] A vehicle charging network is disclosed, comprising: a host vehicle, including a vehicle controller, a wireless communication device and a rechargeable battery pack, the vehicle controller being programmed to: retrieve a unique ID assigned to the host vehicle from a memory device; embed the unique ID into a wireless message, the embedding including an encrypted unique ID and inserting the encrypted unique ID into a dedicated extended frame within the wireless message; and broadcast a wireless message from the wireless communication device, the wireless message having the encrypted unique ID embedded in the wireless message; and an electric vehicle charging station (EVCS), which is connectable to the rechargeable battery pack and includes an EVCS controller, the EVCS controller being programmed to: receive the broadcast wireless message, including parsing the encrypted unique ID from the wireless message; transmit the encrypted unique ID parsed from the wireless message to a backend (BO) vehicle service provider; and in response to the BO vehicle service provider decrypting and authenticating the unique ID, start the EVCS charging operation of the rechargeable battery pack of the host vehicle.
[0031] In the vehicle charging network, the EVCS controller is further programmed to: determine a charger-to-vehicle distance between the EVCS and a wireless communication device using wireless positioning technology; and transmit the charger-to-vehicle distance to a BO vehicle service provider.
[0032] In the vehicle charging network, the vehicle controller is further programmed to: determine a vehicle-to-charger distance between the host vehicle and the EVCS using an on-vehicle sensing device of the host vehicle; and transmit the vehicle-to-charger distance to the BO vehicle service provider via the EVCS.
[0033] In the vehicle charging network, a BO vehicle service provider: determines a distance difference as an absolute value of a mathematical difference between a vehicle-to-charger distance and a charger-to-vehicle distance; determines whether the distance difference is less than a preset distance difference threshold; and authenticates a unique ID based in part on the distance difference being less than the preset distance difference threshold.
[0034] In the vehicle charging network, the vehicle controller is further programmed to transmit a vehicle coupling timestamp to a BO vehicle service provider via the EVCS, at which the host vehicle is operably coupled to the EVCS for charging the rechargeable battery pack, and wherein the EVCS controller is further programmed to transmit a charger coupling timestamp to the BO vehicle service provider, at which the host vehicle is operably coupled to the EVCS.
[0035] In the vehicle charging network, a BO vehicle service provider: determines a time difference as an absolute value of a mathematical difference between a vehicle coupling timestamp and a charger coupling timestamp; determines whether the time difference is less than a preset time difference threshold; and authenticates a unique ID based in part on the time difference being less than the preset time difference threshold.
[0036] The vehicle charging network wherein the vehicle controller is further programmed to embed a unique sharing message in the wireless message, and wherein the EVCS controller is further programmed to determine that the host vehicle is within a predetermined proximity of the EVCS based on the received unique sharing message embedded in the wireless message.
[0037] The above summary of the invention does not represent every embodiment or every aspect of the present disclosure. On the contrary, the foregoing summary of the invention only provides an overview of some novel concepts and features set forth herein. When understood in conjunction with the accompanying drawings and the appended claims, the above-mentioned features and advantages of the present disclosure and other features and attendant advantages will be readily apparent from the following specific embodiments of the illustrated examples and representative modes of implementing the present disclosure. In addition, the present disclosure expressly includes any and all combinations and sub-combinations of the elements and features presented above and below. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] Figure 1 is a partially schematic side view of a representative motor vehicle having an electrified powertrain, a rechargeable battery pack, and a network of in-vehicle controllers, sensing devices, and communication devices for automated vehicle authorization and smart charging according to aspects of the present disclosure.
[0039] Figure 2 is a diagrammatic illustration of a representative vehicle charging network for automated vehicle authorization and smart charging using encrypted wireless connectivity in accordance with aspects of the present disclosure.
[0040] Figure 3 is a flow chart illustrating a representative smart vehicle charging algorithm for managing smart charging operations of a motor vehicle according to aspects of the disclosed concepts, which representative smart vehicle charging algorithm may correspond to instructions stored in a memory executable by a resident or remote controller, control logic circuit, programmable control unit, or other integrated circuit (IC) device or network of devices.
[0041] The present disclosure is subject to various modifications and alternative forms, and some representative embodiments of the present disclosure are shown by way of example in the accompanying drawings and will be described in detail herein. However, it should be understood that the novel aspects of the present disclosure are not limited to the specific forms illustrated in the drawings listed above. On the contrary, the present disclosure covers all modifications, equivalents, combinations, arrangements, groupings and substitutions that fall within the scope of the present disclosure, such as those contained in the appended claims. DETAILED DESCRIPTION
[0042] The present disclosure allows for many different forms of embodiments. Representative embodiments of the present disclosure are shown in the accompanying drawings and will be described in detail herein with the following understanding: These embodiments are provided as examples of the disclosed principles, rather than limitations on the broad aspects of the present disclosure. In this regard, elements and limitations that are described, for example, in the abstract, introduction, summary, illustrations, and specific embodiments, but not explicitly set forth in the claims, should not be incorporated into the claims individually or collectively by implication, inference, or otherwise. In addition, the reference to "first", "second", "third", etc. in the specification or claims is not used to establish serial or numerical limitations; unless otherwise specifically stated, these names may be used to easily reference similar features in the specification and drawings and to define between similar elements in the claims.
[0043] For purposes of this Detailed Description, unless otherwise stated: the singular includes the plural and vice versa; the words "and" and "or" shall be both conjunctive and disjunctive, the words "any" and "all" shall both mean "any and all," and each of the words "include," "comprise," "contain," "have," and the like shall mean "including without limitation." In addition, each of approximate words such as "approximately," "almost," "substantially," "generally," "approximately," and the like may be used herein to mean, for example, "at, close to, or nearly at," or "within 0-5% of," or "within acceptable manufacturing tolerances," or any logical combination thereof. Finally, directional adjectives and adverbs such as front, rear, inboard, outboard, starboard, port, vertical, horizontal, up, down, front, rear, left, right, and the like may be relative to a motor vehicle, such as a forward driving direction of a motor vehicle when the vehicle is operably oriented on a level driving surface.
[0044] Referring now to the drawings, wherein like reference numerals refer to like features throughout the several views, Figure 11 is a diagram showing a representative motor vehicle, generally designated 10, and depicted herein as a sedan-style electric drive vehicle for purposes of discussion. The illustrated vehicle 10 - also referred to herein simply as a "motor vehicle" or "vehicle" - is merely an exemplary application with which aspects of the present disclosure may be practiced. In the same manner, the present concepts may be integrated into Figure 2 The networked vehicle charging system 100 of the present disclosure should also be appreciated as a non-limiting implementation of the disclosed features. As such, it will be understood that aspects and features of the present disclosure can be applied to other vehicle powertrain designs, incorporated into any logically related type of motor vehicle and implemented as countless different vehicle charging system architectures. In addition, only selected components of the motor vehicle, vehicle charging equipment, and networked charging system are additionally described and illustrated in detail herein. However, the vehicles, EVSEs, and charging systems discussed below may include many additional and alternative features and other available peripheral components for implementing the various methods and functions of the present disclosure.
[0045] Figure 1 1 is a simplified illustration of an electric vehicle 10 docked at and operably coupled to an EVCS 20 of a vehicle charging system for recharging an onboard rechargeable energy storage system (RESS), which is represented in part by a high voltage direct current (DC) traction battery pack 14. The traction battery pack 14 may take on many suitable configurations, including lead-acid batteries, lithium-ion batteries, nickel-metal hydride batteries, or other suitable electric vehicle battery (EVB) arrays. To provide an operable coupling between the traction battery pack 14 and the EVCS 20 (also referred to herein as a "charging station"), the vehicle 10 may include a wireless power transfer (WPT) charging component 22, such as having an integrated induction coil mounted to the underside of the vehicle body 12 between the drive wheels 18. The charging component 22 serves as a wireless charging interface compatible with a WPT charging tray 24 of the vehicle charging station 20, such as containing an internal EMF coil or other wireless power transfer hardware. In the illustrated example, the wireless charging tray 24 is secured to the floor beneath the vehicle 10 and positioned according to a "target location" that can serve as a desired parking location for the purpose of efficient and effective wireless charging of the battery pack 14. As an example, Figure 1 The vehicle 10 is depicted parked in a manner to help ensure that the inductive charging component 22 is aligned with the wireless charging pad 24 in both the lateral and longitudinal directions (ie, proper fore-aft and starboard-port alignment) to complete an inductive charging event for the vehicle 10 .
[0046] The vehicle charging station 20 may employ any type of wired and wireless charging technology developed heretofore and hereafter, including, as some non-limiting examples, inductive charging, radio charging, capacitive charging, magneto-dynamic charging, and resonant charging. As for electromagnetic induction charging technology, Figure 1 The representative wireless charging pad 24 can be activated with an electric current to generate an alternating electromagnetic field close to the WPT charging component 22. The magnetic field in turn induces a current in the charging component 22 of the vehicle 10. The induced current can be filtered, stepped up / stepped down, and / or phase-shifted by the electrical modulation circuits (e.g., power inverter module (PIM), transformer, etc.) in the vehicle to charge the traction battery pack 14 or any other energy source (e.g., 12V lead-acid starting, lighting and ignition (SLI) battery, EV supercapacitor, etc.) of the vehicle 10. Although not limiting in itself, aspects of the present disclosure may be particularly suitable for use with plug-in or WPT type 2-level AC EVSE that is not equipped or programmed to perform digital PLC comm operations.
[0047] The traction battery pack 14 stores energy that can be used for propulsion via one or more electric traction motors 16 and, if desired, for operating other vehicle electrical hardware and auxiliary loads. The traction battery pack 14 is communicatively connected (wired or wireless) to a Figure 1 One or more vehicle controllers represented by an electronic control unit (ECU) 26 in the vehicle that regulate the operation of various vehicle systems and components. The ECU 26 is communicatively connected to the traction motor(s) 16 and the battery pack 14 to control, for example, the bidirectional transfer of energy between the battery pack 14 and each motor 16. For example, the battery pack 14 may provide a DC voltage, while the polyphase hairpin-wound permanent magnet (PM) design of the motor(s) 16 may operate using a three-phase AC current; in such an instance, the ECU 26 operates in conjunction with a traction power inverter module (TPIM) 50 to convert the DC voltage into a three-phase AC current for use by the motor(s) 16. In a regenerative charging mode in which the motor(s) 16 act as a motor generator unit (MGU), the ECU 26 may convert the three-phase AC voltage produced by the motor(s) 16 into a DC voltage compatible with the traction battery pack 14. Figure 1The ECU 26 is also shown communicating with the charging component 22, for example, to regulate the power supplied from the EVCS 20 to the battery pack 14, thereby helping to ensure compatible voltage and current levels. The ECU 26 can also interface with the charging station 20 to coordinate the rate and delivery of power to the vehicle 10.
[0048] Figure 1 The vehicle charging station 20 also provides wired charging via a "plug-in" electrical connector 32, which can be any of a variety of different commercially available connector types. As non-limiting examples, the electrical connector 32 can be a Society of Automotive Engineers (SAE) J1772 (Type 1) or J1772-2009 (Type 2) plug, a Combined Charging Standard (CCS) Type 1 or Type 2 plug, or an International Electrotechnical Commission (IEC) 62196-2 or 62196-3 plug. In addition, the connector 32 (also referred to herein as a "charger coupler") can provide single-phase and / or split-phase modes operating at 120 to 240 volts (V) with an alternating current (AC) rate at 40 to 60 amperes (A) peak current for Level 2 low-power vehicle charging. Connector 32 is shown connected to an unsupported EVCS kiosk 58 via HV power cable 56 , and connected via kiosk 58 to a public power utility grid (not visible).
[0049] Accessible on the exterior of the vehicle body 12 is a charger port 34 configured as an electrical inlet into which the electrical connector 32 may be plugged or otherwise mated. For DCFC plug-in charging applications, the charger port 34 may be, for example, a female quick-connect CCS1-compatible electrical outlet rated for DC150A and 850V. The charger port 34 may serve as a wired charging interface that enables a user to easily connect / disconnect the electric vehicle 10 to / from a readily available AC or DC source, such as a public utility power grid, via the charging station 20. Figure 1 The charging port 34 is not limited to any particular design and may be any type of inlet, port, connection, receptacle, plug, etc. that enables a conductive or other type of electrical connection. A hinged charging port door (CPD) 36 on the vehicle body 12 may be selectively opened and closed to access and cover the charging port 34, respectively.
[0050] As part of the vehicle charging process, the vehicle 10 and the EVCS 20 can monitor charging availability, power quality, and other related issues that may affect vehicle charging, either individually or in collaboration. According to the illustrated example, the vehicle ECU 26 can communicate with and receive sensor signals from a monitoring system, which can include a "resident" sensing device 28 on one or more vehicles of the vehicle 10 and / or a "remote" sensing device 30 on one or more non-vehicles of the vehicle charging station 20. In practice, the monitoring system can include a single sensor, or it can include a distributed sensor architecture in which a variety of sensors are packaged in locations similar to or alternative to those shown in the drawings. The CPD sensor 38 mounted by the charging port 34 can sense the door state of the CPD 36 - open or closed - and be polled or read by the vehicle's ECU 26 to determine the door state - open or closed. The lock button 40 used to physically attach and secure the electrical connector 32 to the charging port 34 may include an internal switch (eg, an SAE S3 type switch) that functions as a sensing device to detect whether the electrical connector 32 is operably connected to the charging port 34 .
[0051] Figure 1 A representative vehicle 10 may initially be equipped with a vehicle remote communications and information ("telematics") unit 42 that communicates wirelessly (e.g., via a cellular tower, base station, mobile switching center (MSC), etc.) with a remotely located or "off-vehicle" cloud computing system 44 (e.g., a back-end (BO) vehicle service provider). Serving as both a user input device and a vehicle output device, the telematics unit 42 may be equipped with an electronic video display device and a variety of input controls 46 (e.g., buttons, knobs, switches, track pads, keyboards, touch screens, etc.). The telematics unit may also operate as a human-machine interface (HMI), for example, enabling a user to communicate with the telematics unit 42 and other systems and system components of the vehicle 10. Optional peripheral hardware may include a microphone that provides a vehicle occupant with a means for inputting verbal or other auditory commands; the vehicle 10 may be equipped with an embedded voice processing unit programmed with a computer voice recognition software module.
[0052] Continue to refer Figure 1, the telematics unit 42 is an on-vehicle computing device that provides hybrid services both individually and through its communications with other networked devices. The telematics unit 42 may generally be comprised of one or more processors, each of which may be embodied as a discrete microprocessor, an application specific integrated circuit (ASIC), a dedicated control module, or the like. The vehicle 10 may provide centralized vehicle control via the ECU 26, which may be operably coupled to one or more electronic memory devices 48, each of which may take the form of a solid state drive (SSD) with a real-time clock (RTC), a hard disk drive (HDD), an IC device, a semiconductor memory (e.g., various types of RAM or ROM), or the like. Long range communication (LRC) capabilities with remote non-on-vehicle devices may be provided via one or more or all of a cellular chipset / component, a navigation and positioning component (e.g., a global positioning system (GPS) transceiver), or a wireless modem, all of which are collectively represented at 52. Short range communication (SRC) connectivity may be provided via a short range wireless communication device (e.g., The various comm devices described above may be provided by a unit or near field communication (NFC) transceiver), a dedicated short range communication (DSRC) component, and / or dual antennas, all of which are collectively represented at 54. The various comm devices described above may be configured to exchange data as part of a broadcast in a vehicle-to-vehicle (V2V) or vehicle-to-everything (V2X) communication system, such as a vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), vehicle-to-device (V2D), etc.
[0053] During a vehicle charging event, the owner, operator, or passenger of the vehicle (collectively, a "user") may park the vehicle 10 adjacent the EVCS kiosk 58, manually retrieve the charger coupler 32, and insert the charger coupler 32 into the charger port 34. While inserted, the user may press and then release the latch button 40 on the handle of the charger coupler 32 to raise and then lower a latch element that protrudes forwardly from the plug of the charger coupler 32. Doing so operatively couples the latch element with a complementary catch inside the charger port 34 to prevent the coupler 32 from being accidentally uncoupled from the port 34. By measuring the voltage across the adjacent pins of the coupler, the vehicle ECU 26 may determine the state of the S3 switch and, from that state, determine the presence of the charger coupler 32.
[0054] To provide intelligent vehicle charging authorization, for example, on a Level 2 AC EVCS without digital PLC comm capabilities, the systems and methods described herein use a wireless communication protocol with an encrypted vendor extension field that is embedded within a WiFi / SRC broadcast message for dynamic vehicle identification. Using the unique vehicle ID provided in the encrypted vendor extension, a two-way positioning routine maps real-time location and relative positioning between the host vehicle and the EVCS. A two-step two-way location and time check technique identifies and triangulates the real-time location of the host vehicle. Through the two-way exchange of ID data during vehicle approach and coupling, the system uses timestamps and wireless comm to identify the host vehicle approaching the EVCS and identifying the specific EVCS that the host vehicle intends to couple and charge. As used herein, the terms "EVCS" and "EVSE" can be used interchangeably and synonymously to refer to individual vehicle charging stations or devices, groups of charging stations or devices, commercial or other publicly accessible vehicle charging facilities containing one or more vehicle charging stations or devices, and the like.
[0055] In a more specific but non-limiting example, the host vehicle is assigned a unique ID (e.g., a media access control (MAC) address); upon arrival at the EVCS, the host dynamically encrypts the unique ID and inserts the unique ID into the broadcast WiFi frame as a vendor extension. Each EVCS at a municipal or commercial charging facility scans for these wirelessly transmitted beacons containing vendor extensions. Upon arrival at the charging facility, the EVCS will detect the presence of the host vehicle by receiving the vendor extension ID carried by the beacon. The EVCS transmits the encrypted unique ID to the central server of the charging facility; the server then determines the proximity of the host vehicle. When the vehicle operator is operably coupled (e.g., plugged in) to the charging station, the EVCS communicates with the BO computing host service to send: timestamps on the EVCS and on the vehicle at the charging coupling; and the distance from the host vehicle to the EVCS reported by both the vehicle and the charging station. Using this information, the BO server automates the identification of which motor vehicle is plugged into which charging station. Upon confirming that the correct vehicle ID corresponds to the EVCS ID, automated enabled charging ("autocharging") is initiated.
[0056] Smart charging features such as vehicle automatic charging, vehicle grid integration (VGI), residential / commercial demand response, etc. are enabled at charging stations that do not support PLC digital Comm, such as Level 2 low-power AC EVCS using analog pulse width modulation (PWM) power delivery. These smart charging features and related charging authorizations are enabled to determine which motor vehicle is connected to which charging station without using a hardline connection (e.g., a plug-in DC charging coupler with power line communication). Using encrypted wireless connectivity such as WiFi network protocols and short-range communication (SRC) technology, the disclosed system and method can provide contactless charging activation / payment on legacy chargers using analog PWM comm. Doing so helps extend the operational life expectancy of existing EVCS, accompanied by a reduction in the number of new charging stations deployed to support the daily use of electrified vehicles. Other incidental benefits may include enhancing the number and type of charging features available to vehicles on partner EVSEs. Eliminating the need for digital PLC comm capabilities for exchanging vehicle identification and charging parameters reduces the cost, complexity, and integration of new charging stations.
[0057] Figure 2 is a pictorial diagram of an example of a vehicle charging network and wireless communication system, generally designated 100, for automating vehicle authorization and smart charging using encrypted wireless connectivity. Although a single host vehicle 110 is depicted communicating with three plug-in type level 2 (L2) AC EVCS 120 and a cloud-based BO vehicle service provider 144 via the vehicle charging network 100, it is contemplated that any logically related number and type of vehicles may be operably interfaced with any logically related number and type of vehicle service entities and EVSEs that are appropriately equipped for wirelessly exchanging information and charging (one or more) vehicles. Additionally, although different in appearance, it is contemplated that the above description of Figure 1 Any features and options described for the motor vehicle 10, charging station 20, and BO computing system 44 may be incorporated individually and in any combination. Figure 2 The host vehicle 110, EVCS 120 and vehicle service provider 144, and vice versa. The illustrated EVCS can take a variety of forms, including a full-service or self-service charging station having a parking area with a plurality of docking points, each of which can be aligned with a corresponding charging station.
[0058] When the host vehicle 110 arrives at a vehicle charging facility 121 that provides a compatible EVSE, such as an L2 AC EVCS 120, the host vehicle 110 may establish a wireless connection with the EVCS 120 via an on-vehicle SRC device 154. At the same time, the host vehicle 110 may wirelessly connect with a BO vehicle service provider 144, either indirectly through a “piggyback” connection with the EVCS 120 and / or directly via an on-vehicle LRC device 152. Once connected, the host vehicle 110 may exchange charging-related data with the EVCS 120 and the BO 144 to quickly and efficiently authenticate the vehicle 110 and enable one or more available smart charging operations. According to the illustrated example, the host vehicle 110 can dynamically generate and transmit a vehicle wireless detection list ("V-List") 111, which can contain information such as a vehicle-specific unique ID (e.g., a MAC address) and a timestamp of event data (e.g., an RTC reading at the time of insertion) - both of which can be integrated as part of the data packet payload or as a packet extension frame. Additional information included in the V-List 111 can include, for example, proximity information of the individual EVSE to the host vehicle (e.g., detected by a hotspot device in the host's vehicle), calculated distance information (e.g., based on wireless signal strength), unique encoding / encryption data for broadcast encrypted wireless messages (e.g., WiFi packets, DSRC broadcast beacons, etc.), and insertion event timestamps (e.g., using control pilot state changes in the host vehicle). The data exchange can be adapted and scaled based on, for example, the desired level of accuracy, the user-selected level of security, the EVSE owner-selected level of authenticity, etc.
[0059] Once paired and actively exchanging data, the EVCS 120 may temporarily store the V-List 111, for example, in a resident buffer / cache memory or at a central EVSE facility server. In tandem, the EVCS 120 or vehicle charging facility 121 server may dynamically generate an EVSE wireless detection list ("E-List") 113, which may include proximity information of the EVSE or corresponding EVCS to the subject vehicle (e.g., detected by a resident EVCS hotspot); distance information based on signal strength; unique encoding / encryption information (e.g., for decrypting received WiFi beacons); charging port usage status of the subject EVCS (e.g., plug-in detection + timestamp). The EVCS 120 transmits the V-List 111 and the E-List 113 to a charging point operator (CPO) node 160, which may be generally responsible for operating the EVSE vehicle charging facility 121, by wire or wirelessly; the CPO node 160 may store the data in a resident server database 161. Using this information, the CPO node 160 may dynamically generate an EVSE configuration list ("C-List") 115, which may contain information such as EVSE configuration and installation data, parking data, and charging performance data. In a more specific but non-limiting example, the C-List 115 may also detail the total number of EVCSs at the EVSE, compatible charging port requirements, parking spaces and space layouts, and communication reference data such as WiFi performance metrics.
[0060] Continue to refer Figure 2, CPO node 160 can operate charging network hardware and infrastructure, manage back-end technology and supporting software, and manage the connection between chargers to deliver reliable and consistent EV charging. CPO node 160 can transmit V-List 111, E-List 113 and C-List 115 to e-Mobility (mobility) service provider and mobility operator (eMSP / MO) node 162, which can generally facilitate vehicle charging and payment services and enable access to a variety of charging points within the eMSP / MO network. In this capacity, eMSP / MO node 162 can operate as a middleware application for wirelessly exchanging data with a wireless-enabled portable computing device 164 of the vehicle owner, driver or passenger (collectively referred to as "user") of the main vehicle 110. eMSP / MO node 162 can also communicate with BO vehicle service provider 144, including software-defined vehicle background (SDV BO) node 145 and digital business technology and transformation (DBTT) node 147. According to the illustrated example, the SDV BO node 145 may provide cloud-based vehicle analysis and data collection services, while the DBTT node 147 may provide cloud-based business-to-business (B2B) services for enabling interoperability between multiple discrete business entities, such as the BO 144 and the eMSP 162.
[0061] Next reference Figure 3 According to aspects of the present disclosure, a flowchart for Figure 1 and Figure 2 Improved methods or control strategies for automated authorization of host vehicles such as automobiles 10 and 110 and activation of smart vehicle charging operations such as via EVCS 20 and 120 are provided. Figure 3 Some or all of the operations illustrated in and described in further detail below may represent algorithms corresponding to non-transitory processor-executable instructions stored, for example, in a primary or secondary or remote memory (e.g., Figure 1 (one or more) memory devices 48 and / or Figure 2 161) and, for example, by an electronic controller, a processing unit, a dedicated control module, a logic circuit or other module or device or a network of modules / devices (e.g., Figure 1 ECU 26 and / or Figure 2 BO server) to perform any or all of the above and below functions associated with the disclosed concepts. It should be appreciated that the order of execution of the illustrated operation blocks can be changed, additional operation blocks can be added, and some operations described herein can be modified, combined or eliminated.
[0062] Method 200 begins with Figure 3 START terminal block 201 of the present invention, wherein the memory stores processor executable instructions for a programmable controller or control module or similar suitable processor to call an initialization procedure for the vehicle charging control protocol. The routine may be executed in real time, near real time, continuously, systematically, occasionally and / or at regular time intervals, such as once every 10 or 100 milliseconds during regular and customary operation of the motor vehicle 10. As yet another option, the terminal block 201 may be initialized in response to a user command prompt (e.g., via a telematics input control), a resident vehicle controller prompt (e.g., from the ECU 26), or a broadcast prompt signal received from a centralized backend vehicle service system (e.g., from the EVCS 120 or the BO 144). As a non-limiting example, the method 200 may be automatically triggered in response to the detection of the EVCS 120 by the host vehicle 110 or upon receipt of a pairing handshake prompt received by the host vehicle 110 from the EVCS 120. Upon completion Figure 3 When some or all of the control operations presented in , method 200 may proceed to END terminal block 221 and terminate temporarily, or alternatively, may loop back to terminal block 201 and operate in a continuous loop.
[0063] Proceeding from terminal block 201 to unique ID data input block 203, method 200 provides a vehicle controller with memory stored processor executable instructions to access a resident or remote memory device to retrieve therefrom a unique ID assigned to the host vehicle. Figure 2 In an example of a MAC address, the host vehicle 110 is assigned a different, vehicle-specific alphanumeric code, such as a MAC address of a vehicle identification number (VIN) number; the unique ID can be stored in a readily accessible resident cache memory 48. The BO vehicle service provider 144 maintains a BO server database 163 with a repository of vehicle IDs, each associated with one or more selected smart vehicle charging operations they are authorized to perform. As an alternative to using a MAC address, the unique ID and associated attributes of the subject vehicle can be assigned or randomly assigned by the BO, for example based on an algorithm.
[0064] After retrieving the unique ID of the host vehicle at data input box 203, method 200 executes ID encryption predefined process box 205 and converts the ID (plain text) into a password or code (cipher text), which can help ensure confidentiality and prevent unauthorized access to the unique ID when transmitting to BO 144. As a non-limiting example, when Figure 2When the host vehicle 100 arrives at the vehicle charging facility 121, the vehicle controller (e.g., ECU 26) responsively encrypts the vehicle's unique ID and inserts it into a wireless message such as a WiFi data packet, a V2X DSRC beacon, etc. Vehicle data encryption and insertion (collectively referred to as "embedding") can be configured as part of the default vehicle broadcast process (e.g., not in response to the vehicle approaching the EVSE). In other words, by default, the broadcast message can always be "pre-filled" with encrypted information; the host vehicle does not need / wait to approach the EVSE / EVCS to embed the unique ID and related information.
[0065] The embedding process may encrypt the unique ID using a mutually agreed upon encryption process, such as a transport layer security (TLS) cryptographic protocol, a triple data encryption (DES) symmetric key block cipher, or a public key encryption scheme, and then insert the now encrypted unique ID into a dedicated extension frame (also referred to herein as a "vendor extension field") within the wireless message. For at least some implementations, a vehicle hotspot device (e.g., a 5G LTE mobile hotspot router) within the host vehicle encrypts the unique ID. A mutually agreed upon encryption process may be established between the BO vehicle service provider 144 and the charge point operator 160. Although the host vehicle may encrypt its unique ID and the EVCS / EVSE may identify and optionally parse the encrypted unique information to forward to the BO, it may be desirable for all decryption of the encrypted ID to be performed by the BO vehicle service provider (i.e., the EVCS 120 and EVSE 121 are pass-through devices that only forward vehicle information to the backend BO vehicle service provider 144 without decrypting or parsing the data).
[0066] After embedding the unique ID at the predefined process block 205, the method 200 proceeds to the encrypted ID data output block 207, where the host vehicle transmits the encrypted unique ID to the vehicle charging station and the vehicle service provider. For example, a vehicle controller (e.g., ECU 26) can broadcast a wireless message embedded with the encrypted unique ID (e.g., V-List111) from a wireless communication device (e.g., SRC device 54) to a charging station (e.g., one of the L2 ACEVCS120). The charging station in turn transmits the encrypted unique ID, for example, contained within or parsed from the wireless message, to the BO vehicle service provider 144. According to Figure 2In the illustrated example, the host vehicle 110 can use the LRC device 152 to transmit the V-List 111 directly to the BO vehicle service provider 144 via a cellular / satellite comm channel. For at least some desired implementations, the vehicle charging facility 121 and the EVCS 120 act as a middleware computing node through which the V-List 111 is transmitted to the BO 144, for example, as part of a vehicle-to-infrastructure (V2I) data exchange. As will be described in further detail below, the host vehicle can also generate other functional information and embed it into the wireless broadcast message (e.g., GPS-generated geolocation data, vehicle insertion timestamp, vehicle-to-charger distance and signal strength data, etc.). It may be desirable that the EVSE / EVCS is not enabled to extract and / or interpret any encrypted content information output from the host vehicle; for the EVSE and vehicle, identification monitors and other non-encrypted plaintext information will be considered to identify and operably connect to each other.
[0067] Before, during, or after transmitting the encrypted vehicle ID and accompanying data to the BO, the charging station and the host vehicle can evaluate whether they are within a predefined proximity of each other. Similarly, the BO can automatically respond to the receipt of encrypted vehicle data by evaluating whether the host vehicle is within a predefined proximity of the EVSE / EVCS. As shown, the EVSE 121 central server can establish that the host vehicle 110 is within approximately thirty (30) feet or less of the EVCS120 based on a unique shared "secret" message that is encrypted and inserted into a wireless broadcast message. For example, when the host vehicle 110 approaches the EVSE vehicle charging facility 121, it will repeatedly broadcast a wireless beacon with embedded vehicle data; one or more or all EVCS120 at the station 121 can receive and scan the beacon. The EVCS120 captures the frame within the beacon to identify the supplemental vehicle information, if any, that has been inserted into the dedicated frame extension. Once EVCS 120 verifies that the extension is populated (eg, with a unique shared message), it can then conclude that the identified vehicle is in proximity; EVCS 120 then forwards the extension bearer information to the BO for decryption and authorization.
[0068] Once the information embedded in the message is decrypted by the backend service, the BO can use the decrypted information to confirm the identity of the host vehicle and infer that the host vehicle is within proximity to be operably coupled to the charging station. This information also allows the BO to confirm that the host vehicle is actually within proximity of the station, because only that vehicle will send a beacon including the unique ID information to the station. The BO can then enter a delay loop to wait for a charging coupling event to occur (e.g., the operator of the vehicle 10 plugs the electrical connector 32 into the charger port 34). For example, the charging coupling data input box 209 confirms that the host vehicle 10, 110 is operably coupled to the EVCS 20, 120 via a plug-in connection, a WPT connection, or other suitable charging technology.
[0069] After receiving sufficient data indicating a paired charging coupling between the subject vehicle and the charging station, the backend BO can responsively use both a bidirectional location mapping evaluation (box 211) and a timestamp geolocation evaluation (box 213) to authenticate or reject (rebuff) the vehicle for smart charging. In the bidirectional location mapping process box 211, the vehicle-coupled EVCS 120 uses wireless positioning technology to derive the charger-to-vehicle (first) distance between the wireless communication device of the EVCS and the wireless communication device of the host vehicle. In an example, the paired charging station can calculate the message transmission time between the broadcast time when the host vehicle initially broadcasts the beacon and the reception time when the charging station receives the beacon. Using the calculated message transmission time and available message transmission speed information, the charging station can determine the real-time distance between the vehicle and the station when the beacon is sent. The EVCS or EVSE controller (e.g., Figure 1 The central EVCS controller 62) transmits the charger-to-vehicle distance to the BO vehicle service provider.
[0070] At process block 211, concurrently with the EVCS deriving and relaying the real-time distance between the charging station and the host vehicle, the host vehicle controller derives a vehicle-to-charger (second) distance between the host vehicle and the EVCS using, for example, one or more on-vehicle sensing devices of the host vehicle. By way of example and not limitation, the host vehicle 110 may employ forward and rear-facing high definition (HD) camera arrays, ultrasonic proximity sensors, and / or LiDAR and RADAR aiming and distance sensors to aim and locate the charging station. The host vehicle's controller transmits the vehicle-to-charger distance to the BO vehicle service provider, either directly or through the EVCS.
[0071] In parallel with process block 211, timestamp & geolocation process block 213 generates additional information that is evaluated by the BO prior to enabling a smart charging session, e.g., to increase the reliability of the authorization process. According to the illustrated example, the ECU 26 of the host vehicle communicates with the RTC and GPS transceiver on the vehicle to determine: (1) a vehicle coupling (first) timestamp identifying when the host vehicle was operably coupled to the EVCS to charge the vehicle's battery pack; and (2) a vehicle (first) geolocation data set indicating the real-time location of the host vehicle at the time of charging coupling. The host vehicle transmits the vehicle coupling timestamp and geolocation data to the BO vehicle service provider directly or through the EVCS. In the same manner, the EVCS / EVSE controller (e.g., Figure 1 The EVCS controller 62 of the EVCS determines: (1) a charger coupling (second) timestamp identifying when the host vehicle was operatively coupled to the EVCS; and (2) an EVCS (second) geolocation data set indicating the real-time location of the EVCS at the time of charger coupling. The EVCS transmits the charger coupling timestamp and geolocation data to the BO vehicle service provider, for example, via the CPO and eMSP / MO nodes 160 and 162.
[0072] After accumulating the vehicle-generated and charger-generated spatial and temporal information outputs at process blocks 211 and 213, method 200 proceeds to vehicle authentication decision block 215 to determine whether a smart charging session for the subject vehicle is authorized by comparing the geographic location, timestamp, and proximity data to corresponding preset thresholds. For example, Figure 2 The BO vehicle service provider 144 may perform a three-way authentication analysis to: (1) compare the relative proximity of the host vehicle and the charging station to each other at the time of charging coupling; (2) compare the real-time geographic locations of the host vehicle and the charging station at the time of charging coupling; and (3) compare the timestamps of the host vehicle and the charging station at the time of charging coupling. The first step of the analysis may include the BO 144 calculating the distance difference as the absolute value of the mathematical difference between the vehicle-to-charger distance and the charger-to-vehicle distance; the BO then determines whether the distance difference is less than a preset distance difference threshold. 1 A second step of the analysis may include the BO 144 calculating the time difference as the absolute value of the mathematical difference between the vehicle coupling timestamp and the charger coupling timestamp; the BO then determines whether the time difference is less than a preset time difference threshold. 2 A third step of the analysis may include the BO 144 determining whether the vehicle's geo-location data / real-time location is substantially equal to the EVCS's geo-location data / real-time location (eg, within approximately 1-3 meters). 3
[0073] ABS(distance(station to vehicle)-distance(vehicle to station))<distance threshold 1
[0074] &&
[0075] ABS (time on the vehicle - time on the station) < time threshold 2
[0076] &&
[0077] GPS (transportation) ~ = GPS (station) 3
[0078] Although not required per se, a true positive result may require all three steps in the aforementioned three-party authentication analysis to be true.
[0079] If automated vehicle authentication is denied (block 215=No), the method 200 may responsively execute an authentication denied process block 217 and transmit an electronic notification to the vehicle user indicating that the host vehicle was not automatically verified by the BO. For at least some implementations, the BO 144 may transmit an electronic notification to the CPO 160 that automated authentication of the host vehicle 110 has failed; the EVSE 121 central server and / or the EVCS 120 central controller may respond by temporarily denying some or all available smart charging operations to the host vehicle 110. At this point, the vehicle user may manually submit an electronic request to initiate vehicle charging, for example, via a wirelessly enabled portable computing device 164.
[0080] Conversely, if the automated vehicle authentication is approved (block 215=yes), the method 200 may responsively execute the authentication approved process block 219 and initiate one or more smart charging operations for the rechargeable battery pack of the host vehicle through the EVCS. In this example, the BO 144 may transmit an electronic notification of successful automated authentication of the host vehicle 110 to the CPO 160; the EVSE 121 central server and / or the EVCS 120 central controller may respond by activating one or more pre-approved smart charging operations associated with the host vehicle 110. An electronic notification may also be transmitted from the BO 144 to the user's wireless-enabled portable computing device 164 indicating that the host vehicle has been automatically authenticated for smart charging by the BO.
[0081] It is also within the scope of the present disclosure to apply the "access control" concepts described herein to public, semi-public, and private environments (e.g., no payment range / public charger / employee charger / hotel / paid parking) for authorized vehicles to charge on EVSE. For example, the backend BO service may be unavailable or unresponsive, or if desired, intentionally omitted from the network; in this instance, communication and authentication can be managed between the main vehicle and the EVSE / CPO (e.g., using wireless beacons embedded with shared "secret" data). As another option, the pairing of the vehicle and the EVSE can be by broadcasting wireless beacons from the EVCS / EVSE to the vehicle. The disclosed features can also enable access control for the use of Level 2 / Level 1 chargers in homes (inside or outside garages / apartments), hotels, parking lots, employee-only chargers, etc. for authorized vehicles. The disclosed features can also enable the ability to define parameters / security codes used in beacons using vehicle / mobile applications (apps). Another option can include EVSE broadcasting wireless messages that are received and processed by nearby vehicles. These EVSE / EVCS broadcast wireless messages may contain information such as cable diagnostic data, available power, charging current limit, charger health data, charging cable / plug faults, charging capabilities and other relevant information. Other embedded data may include identification related information and notification related information to the customer to guide him to use available / appropriate / working chargers (for example, if multiple chargers are present).
[0082] In some embodiments, aspects of the present disclosure can be implemented by computer executable instruction programs, such as program modules, commonly referred to as software applications or applications executed by any one of the controllers or controller variants described herein. In a non-limiting example, software can include routines, programs, objects, components, and data structures that perform specific tasks or implement specific data types. The software can form an interface that allows a computer to react according to an input source. The software can also collaborate with other code segments to initiate multiple tasks in response to data received in conjunction with a source receiving data. The software can be stored on any of a variety of storage media, such as CD-ROMs, disks, and semiconductor memories (e.g., various types of RAM or ROM).
[0083] In addition, aspects of the present disclosure can be practiced with a variety of computer systems and computer network configurations, including multiprocessor systems, microprocessor-based or programmable consumer electronic devices, minicomputers, mainframe computers, and the like. In addition, aspects of the present disclosure can be practiced in a distributed computing environment, where tasks are performed by resident and remote processing devices linked by a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices. Therefore, aspects of the present disclosure can be implemented in a computer system or other processing system in combination with various hardware, software, or a combination thereof.
[0084] Any method described herein may include machine-readable instructions for execution by (a) a processor, (b) a controller, and / or (c) any other suitable processing device. Any algorithm, software, control logic, protocol, or method disclosed herein may be embodied as software stored on a tangible medium, such as, for example, a flash memory, a solid-state drive (SSD) memory, a hard disk drive (HDD) memory, a CD-ROM, a digital versatile disk (DVD), or other memory device. The entire algorithm, control logic, protocol, or method and / or part thereof may alternatively be executed by a device other than a controller and / or embodied in firmware or dedicated hardware in a usable manner (e.g., implemented by an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable logic device (FPLD), discrete logic, etc.). In addition, although a specific algorithm may be described with reference to the flowchart and / or workflow diagram depicted herein, many other methods for implementing the example machine-readable instructions may be used alternatively.
[0085] Aspects of the present disclosure have been described in detail with reference to the illustrated embodiments; however, those skilled in the art will recognize that many modifications may be made thereto without departing from the scope of the present disclosure. The present disclosure is not limited to the precise configurations and compositions disclosed herein; any and all modifications, changes, and variations apparent from the foregoing description are within the scope of the present disclosure as defined by the appended claims. Furthermore, the present concept expressly includes any and all combinations and sub-combinations of the foregoing elements and features.
Claims
1. A method of controlling a charging operation of a host vehicle having a vehicle controller, a wireless communication device, and a rechargeable battery pack connectable to an electric vehicle charging station (EVCS) having an EVCS controller, the method include: retrieving, via the vehicle controller, from the memory device a unique ID assigned to the host vehicle; embedding, via the vehicle controller, the unique ID in a wireless message in response to approaching the EVCS, the embedding comprising encrypting the unique ID and inserting the encrypted unique ID into a dedicated extension frame within the wireless message; broadcasting a wireless message from the wireless communication device to the EVCS via the vehicle controller, the wireless message having an encrypted unique ID embedded in the wireless message; transmitting the encrypted unique ID parsed from the wireless message from the EVCS controller to a backend (BO) vehicle service provider; and In response to the BO vehicle service provider decrypting and authenticating the unique ID via the EVCS controller, a charging operation of the host vehicle's rechargeable battery pack is initiated by the EVCS.
2. The method according to claim 1, further comprising: include: Using wireless positioning technology, determining the charger-to-vehicle distance between the EVCS and the wireless communication device via the EVCS controller; and The charger-to-vehicle distance is transmitted to the BO vehicle service provider via the EVCS controller.
3. The method according to claim 2, further comprising: include: determining, via the vehicle controller, a vehicle-to-charger distance between the host vehicle and the EVCS using an on-vehicle sensing device of the host vehicle; and The vehicle-to-charger distance is transmitted to the BO vehicle service provider via the vehicle controller through the EVCS.
4. The method according to claim 3, further comprising: include: calculating the distance differential as the absolute value of the mathematical difference between the vehicle-to-charger distance and the charger-to-vehicle distance; and Determine whether the distance difference is less than a preset distance difference threshold, Wherein the BO transportation service provider authenticates the unique ID based in part on the distance difference being less than a preset distance difference threshold.
5. The method according to claim 1, further comprising: include: transmitting, via the vehicle controller, through the EVCS to the BO vehicle service provider a vehicle coupling timestamp at which the host vehicle was operatively coupled to the EVCS to charge the rechargeable battery pack; and A charger coupling timestamp is transmitted to the BO vehicle service provider via the EVCS controller, at which the host vehicle is operably coupled to the EVCS.
6. The method according to claim 5, further comprising: include: calculating the time difference as the absolute value of the mathematical difference between the vehicle coupling timestamp and the charger coupling timestamp; and Determine whether the time difference is less than a preset time difference threshold, Wherein the BO transportation service provider authenticates the unique ID based in part on the time difference being less than a preset time difference threshold.
7. The method according to claim 1, further comprising: include: transmitting, via the vehicle controller through the EVCS to the BO vehicle service provider, a vehicle geo-location data set indicating a real-time location of the host vehicle; transmitting, via the EVCS controller, to the BO transportation service provider an EVCS geographic location data set indicating a real-time location of the EVCS; and determining whether the vehicle geographic location dataset is substantially equal to the EVCS geographic location dataset, Wherein the BO vehicle service provider authenticates the unique ID based in part on the vehicle geolocation dataset being approximately equal to the EVCS geolocation dataset.
8. The method according to claim 1, further comprising: include: embedding a unique shared message in a wireless message via a vehicle controller in response to approaching the EVCS, and A determination is made, via the EVCS controller, in response to receiving the unique shared message embedded in the wireless message, that the host vehicle is within a predetermined proximity of the EVCS.
9. The method according to claim 1, further comprising: include: determining, via the vehicle controller, that the host vehicle is operably coupled to the EVCS for charging the rechargeable battery pack; and appending, via the vehicle controller, a vehicle geolocation data set indicating a real-time location of the host vehicle and a vehicle coupling timestamp of the operative coupling of the host vehicle to the EVCS to the wireless message in response to the host vehicle being operatively coupled to the EVCS, Wherein the BO vehicle service provider authenticates the unique ID based in part on the vehicle geolocation dataset and the vehicle coupling timestamp.
10. The method according to claim 9, in, Operably coupling the host vehicle to the EVCS includes: Inserting the electrical connector plug of the EVCS into the plug port of the host vehicle; and / or The wireless power transfer (WPT) receiving component of the host vehicle is paired with the WPT transmitter component of the EVCS.
