VEHICLE ARCHITECTURES, DEVICES AND CONTROL ALGORITHMS FOR MANAGING WIRELESS VEHICLE CHARGING

Abstract

Disclosed are control algorithms and system architectures for managing wireless vehicle charging, including vehicles with rechargeable battery packs, wireless charging capabilities, and control logic for governing such charging. A method is disclosed for managing charging of an electrical storage unit of a motor vehicle at a wireless vehicle charging station. The method includes: receiving a sensor signal indicating detection of an obstruction within a predetermined proximity of the vehicle charging station; determining whether the detected obstruction is living or lifeless; initiating, via a vehicle controller responsive to the detected obstruction being a living object, a first remedial action strategy that commands the vehicle to generate a visual or audible cue to drive away the living object; and, initiating, via the vehicle controller responsive to the detected obstruction being a lifeless object, a second remedial action strategy that commands the motor vehicle to move and thereby avoid contact with the object.

Claims

1. A method for managing charging of an electrical storage unit of a motor vehicle at a wireless vehicle charging station, the method comprising: receiving, via a vehicle controller from a sensor, a signal indicative of detection of an obstruction within a predetermined proximity of the wireless vehicle charging station; determining, via the vehicle controller, whether the detected obstruction is a living object or a lifeless object; initiating, via the vehicle controller responsive to a determination that the detected obstruction is a living object, a first remedial action strategy including commanding the motor vehicle to generate a visual or audible cue configured to drive away the living object; and initiating, via the vehicle controller responsive to a determination that the detected obstruction is a lifeless object, a second remedial action strategy including directing the motor vehicle to reposition such that the motor vehicle avoids contact with the lifeless object.

2. The method of claim 1, wherein the motor vehicle includes a sound-generating component, and wherein the first remedial action strategy includes commanding the sound-generating component to output the audible cue configured to drive away the living object.

3. The method of claim 1, wherein the motor vehicle includes a light-generating component, and wherein the first remedial action strategy includes commanding the light-generating component to output the visual cue configured to drive away the living object.

4. The method of claim 1, wherein the motor vehicle has autonomous driving capabilities, and wherein the first remedial action strategy includes autonomously rerouting the motor vehicle to evade the living object.

5. The method of claim 1, wherein the motor vehicle has autonomous driving capabilities, and wherein the second remedial action strategy includes autonomously repositioning the motor vehicle to a new location or a new position.

6. The method of claim 1, wherein the motor vehicle includes a light-generating and sound-generating components, wherein the lifeless object is a second motor vehicle, and wherein the second remedial action strategy includes commanding the light-generating component to output a visual prompt and/or commanding the sound-generating component to output an audible prompt, both configured to prompt the second motor vehicle to move.

7. The method of claim 1, further comprising: receiving, via the vehicle controller, a signal indicating that charging of the electrical storage unit has commenced; and continuously monitoring the predetermined proximity of the wireless vehicle charging station for the obstruction during charging of the electrical storage unit.

8. The method of claim 1, further comprising, upon completion of the first or second remedial action strategy, initiating a retry strategy, the retry strategy including a repeated loop of: communicating, via the vehicle controller with the sensor, to determine if the obstruction is still within the predetermined proximity of the wireless vehicle charging station; responsive to a determination that the obstruction is still within the predetermined proximity, re-executing a corresponding one of the initiating operations; and responsive to a determination that the obstruction is not within the predetermined proximity, concluding the retry strategy.

9. The method of claim 8, wherein the retry strategy further includes: determining, prior to the re-executing of the corresponding initiating operation, if a predetermined time period has expired or a maximum number of cycles of the repeated loop has been completed; and responsive to a determination that the predetermined time period has expired or the maximum number of cycles have been completed, concluding the retry strategy.

10. The method of claim 1, further comprising transmitting, via the vehicle controller to a user, a user prompt with an indication of the detected obstruction and a request for approval to initiate the first or the second remedial action strategy.

11. The method of claim 1, further comprising receiving, via the vehicle controller from a user input device of a user, one or more user parameters modifying the first remedial action strategy or the second remedial action strategy, or both.

12. The method of claim 1, further comprising: receiving, via the vehicle controller, an indication that charging of the electrical storage unit has commenced; and terminating, via the vehicle controller responsive to receiving the signal indicative of detection of the obstruction, the charging of the electrical storage unit.

13. The method of claim 1, wherein the motor vehicle includes a vehicle body, and wherein the vehicle controller and the sensor are resident to the vehicle body.

14. An electric motor vehicle comprising: a vehicle body; a traction battery back attached to the vehicle body; a wireless charging receiver component electrically coupled to the traction battery back and configured to operably couple with a wireless vehicle charging station; and a vehicle controller attached to the vehicle body and programmed to: receive, from a sensor, a signal indicative of detection of an obstruction within a predetermined proximity of the wireless vehicle charging station; determine whether the detected obstruction is a living object or a lifeless object; responsive to a determination that the detected obstruction is a living object, initiate a first remedial action strategy including commanding the motor vehicle to generate a visual or audible cue configured to drive away the living object; and responsive to a determination that the detected obstruction is a lifeless object, initiate a second remedial action strategy including commanding the motor vehicle to reposition such that the motor vehicle avoids contact with the lifeless object.

15. A non-transitory, computer readable medium storing instructions for execution by an onboard vehicle controller of a motor vehicle, the motor vehicle having an electrical storage unit electrically coupled to a wireless charging receiver component configured to operably couple with a wireless vehicle charging station, the instructions causing the vehicle controller to perform steps comprising: receiving, from a sensor, a signal indicative of detection of an obstruction within a predetermined proximity of the wireless vehicle charging station; determining whether the detected obstruction is a living object or a lifeless object; initiating, responsive to a determination that the detected obstruction is a living object, a first remedial action strategy including commanding the motor vehicle to generate a visual or audible cue configured to drive away the living object; and initiating, responsive to a determination that the detected obstruction is a lifeless object, a second remedial action strategy including commanding the motor vehicle to reposition such that the motor vehicle avoids contact with the lifeless object.

16. The non-transitory, computer readable medium of claim 15, wherein the motor vehicle includes a sound-generating component and a light-generating component, and wherein the first remedial action strategy includes commanding the sound-generating component to output the audible cue and/or commanding the light-generating component to output the visual cue, both of which are configured to drive away the living object.

17. The non-transitory, computer readable medium of claim 15, wherein the motor vehicle has autonomous driving capabilities, and wherein the first remedial action strategy includes autonomously rerouting the motor vehicle to evade the living object.

18. The non-transitory, computer readable medium of claim 15, wherein the motor vehicle has autonomous driving capabilities, and wherein the second remedial action strategy includes autonomously repositioning the motor vehicle to a new location or a new position.

19. The non-transitory, computer readable medium of claim 15, wherein the motor vehicle includes a light-generating component and a sound-generating component, wherein the lifeless object is a second motor vehicle, and wherein the second remedial action strategy includes commanding the light-generating component to output a visual prompt and/or commanding the sound-generating component to output an audible prompt, both of which are configured to prompt the second motor vehicle to move.

20. The non-transitory, computer readable medium of claim 15, further comprising instructions causing the vehicle controller to, upon completion of the first or second remedial action strategy, initiate a retry strategy, the retry strategy including a repeated loop of: communicating with the sensor to determine if the obstruction is still within the predetermined proximity of the wireless vehicle charging station; responsive to a determination that the obstruction is still within the predetermined proximity, re-executing a corresponding one of the initiating operations; and responsive to a determination that the obstruction is not within the predetermined proximity, concluding the retry strategy.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG. 1 is a schematic side-view illustration of a representative motor vehicle operably coupled to a representative wireless vehicle charging station in accordance with aspects of the present disclosure.

[0015] FIG. 2 is a flowchart for an object intrusion protocol for wireless electric vehicle charging that may correspond to instructions executed by onboard control-logic circuitry, programmable electronic control unit, or other computer-based device of a motor vehicle in accord with aspects of the disclosed concepts.

[0016] FIG. 3 is a flowchart for a living foreign obstruction remediation protocol that may correspond to instructions executed by onboard control-logic circuitry, programmable electronic control unit, or other computer-based device of a motor vehicle in accord with aspects of the disclosed concepts.

[0017] FIG. 4 is a flowchart for a non-living foreign obstruction remediation protocol that may correspond to instructions executed by onboard control-logic circuitry, programmable electronic control unit, or other computer-based device of a motor vehicle in accord with aspects of the disclosed concepts.

[0018] The present disclosure is susceptible to various modifications and alternative forms, and some representative embodiments have been shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the novel aspects of this disclosure are not limited to the particular forms illustrated in the appended drawings. Rather, the disclosure is to cover all modifications, equivalents, combinations, subcombinations, permutations, groupings, and alternatives falling within the scope and spirit of the disclosure as defined by the appended claims.

DETAILED DESCRIPTION

[0019] This disclosure is susceptible of embodiment in many different forms. There are shown in the drawings and will herein be described in detail representative embodiments of the disclosure with the understanding that these representative embodiments are to be considered an exemplification of the principles of the disclosure and are not intended to limit the broad aspects of the disclosure to the embodiments illustrated. To that extent, elements and limitations that are disclosed, for example, in the Abstract, Summary, and Detailed Description sections, but not explicitly set forth in the claims, should not be incorporated into the claims, singly or collectively, by implication, inference or otherwise. For purposes of the present detailed description, unless specifically disclaimed: the singular includes the plural and vice versa; the words and and or shall be both conjunctive and disjunctive; the word all means any and all; the word any means any and all; and the words including and comprising and having mean including without limitation. Moreover, words of approximation, such as about, almost, substantially, approximately, and the like, may be used herein in the sense of at, near, or nearly at, or within 3-5% of, or within acceptable manufacturing tolerances, or any logical combination thereof, for example.

[0020] Aspects of the present disclosure are directed to an Electric Vehicle Communications Controller (EVCC) programmed to execute remedial action strategies for vehicles equipped with an onboard wireless (inductive) charging system. When a vehicle is actively charging with a Wireless Electric Vehicle Supply Equipment (WEVSE), the wireless system monitors (continuously, sporadically, systematically, on-demand, etc.) for wireless power quality issues, such as alignment/misalignment, foreign object (living and non-living) intrusion, faulty grid power, etc. In some instances, this verification may need to be performed continuously during active charging as well as upon re-initialization of a delayed charge as circumstances may have changed. In the event that conditions have been compromised, the EVCC will attempt remedy any detected living obstruction (e.g., a stray or wild animal, distracted pedestrian, other driver, etc.) via automated visual and/or audible cues designed to induce the obstruction to move. If the vehicle has autonomous capabilities, a remedial action strategy may include repositioning and/or relocating the vehicle to avoid inadvertent contact with either a living or a non-living foreign object. Optional features include outputting a notification to a driver or occupant with notice of the obstruction and options, e.g., to proceed with recommended/default remedial action(s), set one or more system parameters, deviate and proceed, delay charging event, or terminate the charging event.

[0021] On detection of intrusion of a living object, the EVCC may execute a method to deter, and then commence charging once the living object is no longer sensed. As an example, the EVCC may automatically respond to the intrusion of a living object by invoking an audible and/or visual prompt from originally equipped vehicle components that create light and sound. This can be a single source or a combination of sources, such as: sound a Pedestrian Friendly Alert Function (PFAF) horn; output cue from a radio/stereo component; start or rev the engine or motor; start or rev in-vehicle fans and/or pumps, flash front or rear lamps, etc. Responsive to continued detection of a living or non-living foreign object that the EVCC was unable to remedy with a preliminary mitigating action, the EVCC can invoke a retry strategy with remedial actions. The amount of times a retry strategy can be implemented may be restricted by a system default threshold or by a user-set parameter. If desired, the EVCC will prompt the customer, e.g., via an in-vehicle telematics unit, an electronic communication, or a mobile device notification, for approval of any proposed remedial action, retry strategy, etc., and will input new charge preferences. Disclosed features help to mitigate issues related to unwanted object intrusion prior to, during and after wireless charging events. Other attendant benefits may include ensuring maximum wireless power transfer for attended and unattended vehicles.

[0022] Referring now to the drawings, wherein like reference numbers refer to like features throughout the several views, there is shown in FIG. 1 a schematic illustration of a representative automobile, which is designated generally at 10 and portrayed herein for purposes of discussion as a four-door, electric-drive (full or hybrid) vehicle. Packaged within a vehicle body 12 of the automobile 10, e.g., within a passenger compartment, a trunk compartment, or a dedicated battery compartment, is a traction battery pack 14 that is electrically coupled to and powers one or more electric motor-generators 16 that operate to turn wheels 18 and thereby propel the vehicle 10. The illustrated automobile 10also referred to herein as motor vehicle or vehicle for shortis merely an exemplary application with which many aspects and features of this disclosure may be practiced. In the same vein, implementation of the present concepts via the specific electric vehicle supply equipment (EVSE) architecture illustrated in FIG. 1 should also be appreciated as an exemplary application of the concepts and features disclosed herein. As such, it will be understood that aspects and features of this disclosure may be applied to other types of EVSE, and implemented for any logically relevant type of motor vehicle. Moreover, only select components of the vehicle 10 have been shown and will be described in additional detail herein. Nevertheless, the motor vehicles and EVSE architectures discussed herein can include numerous additional and alternative features, and other well-known peripheral components, for example, for carrying out the various methods and functions of this disclosure. Lastly, the drawings presented herein are not necessarily to scale and are provided purely for instructional purposes. Thus, the specific and relative dimensions shown in the drawings are not to be construed as limiting.

[0023] FIG. 1 is a simplified illustration of the electric drive vehicle 10 docked at and operably coupled to a wireless charging station 20 for recharging an onboard rechargeable energy source, such as a high-voltage direct current (DC) traction battery pack 14 with an array of lead-acid, lithium-ion, or other applicable type of rechargeable electric vehicle batteries (EVB). To provide this operable coupling, the vehicle 10 may include an inductive charging component 22, e.g., with an integrated induction coil, that is onboard the vehicle 10. This inductive charging component 22 is compatible with a wireless charging pad or platform 24, e.g., with an EMF coil, of the wireless charging station 20. In the illustrated example, the wireless charging pad/platform 24 is located on the ground or floor of the wireless charging station 20, and is positioned in accordance with a target location that serves as a desired parking location, e.g., for purposes of efficient and effective wireless charging of the vehicle 10. In particular, FIG. 1 depicts the vehicle 10 parked in a location that helps to ensure the inductive charging component 22 is substantially or completely aligned in both lateral and longitudinal dimensions with the wireless charging pad 24. Put another way, the vehicle 10 in FIG. 1 is considered to be in proper fore-aft alignment and in proper starboard-port alignment with a designated target location.

[0024] The wireless charging station 20 may employ any heretofore and hereinafter developed type of wireless charging technology, including inductive charging, radio charging, and resonance charging, as some non-limiting examples. In accordance with electromagnetic induction charging technology, the representative wireless charging pad 24 of FIG. 1 can be activated with electric current to generate an alternating electromagnetic field proximate the inductive charging component 22. The generated magnetic field, in turn, induces an electric current in the inductive charging component 22 of the vehicle 10. This induced current is used to charge the traction battery pack 14 or other energy source (e.g., standard 12V lead-acid starting, lighting, and ignition (SLI) battery) of the electric drive vehicle 10. As mentioned previously, the optimal wireless charging performance may be obtained when the inductive charging component 22 is properly aligned with the wireless charging pad 24.

[0025] Traction battery pack 14 stores energy that can be used for propulsion by the electric machine(s) 16 and for operating other vehicle electrical systems. The traction battery pack 14 is communicatively connected (wired or wirelessly) to one or more vehicle controllers, represented herein by electronic control unit (ECU) 26, that regulates the operation of onboard vehicle components. Contactors controlled by the ECU 26, for example, may isolate the traction battery pack 14 from other components when opened, and connect the traction battery pack 14 to other components when closed. The ECU 26 is also communicatively connected to the electric motor-generator(s) 16 to control, for example, bi-directional transfer of energy between the traction battery pack 14 and motor-generator(s) 16. For instance, traction battery pack 14 may provide a DC voltage while the motor-generator(s) 16 may operate using a three-phase AC current; in such an instance, ECU 26 converts the DC voltage to a three-phase AC current for use by the motor-generator(s) 16. In a regenerative mode where the electric machine(s) 16 act as generators, the ECU 26 may convert three-phase AC current from the motor-generator(s) 16 to DC voltage compatible with the traction battery pack 14. The representative ECU 26 is also shown communicating with charging component 22, for example, to condition the power supplied from the wireless charging station 20 to the battery pack 14 to help ensure proper voltage and current levels. The ECU 26 may also interface with the charging station 20, for example, to coordinate the delivery of power to the vehicle 10.

[0026] As part of the wireless charging process, the electric drive vehicle 10 monitors wireless power quality and related issues that may affect charging. According to the illustrated example, the vehicle ECU 26 of FIG. 1 communicates with and receives sensor signals from a monitoring system, which may comprise one or more onboard resident sensing devices 28 of the vehicle 10 and/or one or more off-board remote sensing devices 30 of the wireless charging station 20. In practice, this monitoring system may include a single sensor, or it may include a distributed sensor architecture with an assortment of sensors packaged at similar or alternative locations to that shown in the drawings. These sensing devices are operable, independently or through cooperative operation, to detect the intrusion of living and non-living foreign objects (also referred to herein as obstructions), among other things. By way of non-limiting example, the resident sensor 28 many take on many different forms, including an infrared sensor (e.g., a DC 5V 0-2 meter adjustable infrared beam proximity sensor), and the remote sensor 30 many take on many different forms, including an ultrasonic sensor (e.g., SU, UK and TU series round-body reflective ultrasonic proximity sensors). There are numerous other types of sensing devices that can also be used, including, for example, thermal sensing devices, such as passive thermal infrared sensors, optical sensing devices, such as light- and laser-based sensors, acoustic sensing devices, such as surface acoustic wave (SAW) and ultrasonic sensors, capacitive sensing devices, such as capacitive-based proximity sensors, etc.

[0027] FIG. 2 illustrates a series of representative operations for executing an object intrusion protocol for wireless electric vehicle charging. In this regard, FIG. 3 illustrates a series of representative operations for executing a living foreign obstruction remediation protocol for wireless electric vehicle charging. Conversely, FIG. 4 illustrates a series of representative operations for executing a non-living foreign obstruction remediation protocol for wireless electric vehicle charging. Some or all of the operations portrayed in FIGS. 2-4 and described herein can be representative of algorithms or methods 200, 300 and 400, respectively, that correspond to processor-executable instructions that can be stored, for example, in main or auxiliary or remote memory, and executed, for example, by an ECU, a CPU, a dedicated IC device, an on-board or remote control logic circuit, or a network of devices, to perform any or all of the above and/or below described functions associated with the disclosed concepts.

[0028] Turning first to FIG. 2, the object intrusion protocol 200 starts at block 201 with receiving a wireless quality alert, which may originate with either sensor 28, 30 generating a proximity intrusion signal responsive to an unexpected foreign obstruction being detected within a predetermined proximity (e.g., within a 10-15 meter diameter perimeter) of the wireless vehicle charging station 20. Prior to, contemporaneous with, or after receiving the foregoing proximity intrusion sensor signal from one or both sensors, the vehicle ECU 26 may communicate with the wireless vehicle charging station 20 to initiate pre-charging procedures, e.g., confirming the charging station is available and operating properly, receiving instructions for properly docking the vehicle, confirming proper alignment and compatibility between the inductive charging component 22 and wireless charging pad 24, etc. Once pre-charging procedures have been complete and the vehicle 10 is operably mated with the charging station 20, the ECU 26 will receive a signal, e.g., from the wireless charging station 20 or the onboard charging component 22, indicating that charging of the traction battery pack 14 has commenced. For at least some preferred embodiments, vehicle ECU 26 will continuously track wireless charging quality, including monitoring the proximity of the wireless vehicle charging station 20 for intrusion of an obstruction, during wireless charging of the battery pack 14. Optionally, if the vehicle controller 26 receives a sensor signal indicating intrusion of a foreign obstruction during a charging event, charging of the electrical storage unit 14 may be terminated or temporarily paused while the system attempts to remedy the situation.

[0029] At decision block 203, the vehicle ECU 26 determines if the detected obstruction is a living object, such as a stray pet, squirrel, wandering pedestrian, bird, another driver or any other living entity that may interfere with a wireless charging event. This may be accomplished by any known means, including using laser trip wires, infrared sensing devices capable of detecting body heat, pressure-sensitive pads, thermal sensors, etc. If the method 200 determines that the obstruction is a living object (Block 203=Y), the method 200 continues to the living foreign obstruction remediation protocol 300 of FIG. 3, as indicated with the circled A in FIGS. 2 and 3. Conversely, if it is determined that the detected obstruction is not living (Block 203=N), the method 200 continues to decision block 205 where the vehicle ECU 26 determines if the detected obstruction is a non-living or lifeless object, such as another automobile, a parked bicycle or motorcycle, tree branch, garbage can, debris, or other inanimate object. This determination may be accomplished with any of the known sensing means disclosed herein. If the method 200 determines that the obstruction is a non-living object (Block 205=Y), the method 200 continues to the non-living foreign obstruction remediation protocol 400 of FIG. 4, as indicated with the circled C in FIG. 2. Conversely, if it is determined that the detected obstruction is not a non-living object or, what's more likely, that the foreign object is no longer an obstruction (Block 205=N), the object intrusion protocol 200 concludes at block 207.

[0030] When it is determined that a detected obstruction is a living object, the living foreign obstruction remediation protocol 300 illustrated in FIG. 3 is initiated via the vehicle ECU 26. This protocol 300, or select portions thereof, may be considered an automated first remedial action strategy designed to ameliorate the undesirable intrusion of foreign objects that may impede or otherwise affect wireless charging. At decision block 301, the foreign obstruction remediation protocol 300 may optionally decide whether or not to alert a customer (e.g., a driver or occupant or attendant) via electronic transmission notifying of the detected intrusion of the living object. This transmission may include a user prompt with an indication of the presence, type, size, etc., of the detected obstruction, and a request for a user input to approve the initiation of the first remedial action strategy. At block 303, the ECU 26 receives, e.g., from a touchscreen video display of an in-vehicle telematics center console unit or a handheld cellular-enabled smartphone, a user input to proceed with current or default settings, one or more user-desired parameters that modify one or more parts of the first remedial action strategy, or a user input overriding or otherwise disengaging the protocol 300. If a customer notification is not sent (i.e., decision block 301 is omitted or disengaged) or a user response is not received (Block 301=N), the method 300 proceeds to block 305 and default remedial action settings are implemented.

[0031] Living foreign obstruction remediation protocol 300 of FIG. 3 continues to blocks 307-311 to generate an automated vehicle response to the detected obstruction in an attempt to remove or circumvent the living object. This automated response may include, as some non-limiting examples, commanding the motor vehicle to generate a visual cue and/or an audible cue that is/are designed to drive away the living object. Another optional or alternative automated response may include resituating or otherwise moving the vehicle to avoid vehicle interaction with the living obstruction. As one example, the motor vehicle 10 includes numerous sound-generating components, such as horns, fans, pumps, speaker components, telematics and/or infotainment components, motor, engine, etc. In this instance, the first remedial action strategy includes, at block 307, determining an audible response, if any, and commanding one or more of these sound-generating components to output an audible cue designed to drive away the living object. In the same vein, the motor vehicle 10 includes various light-generating components that provide interior and exterior illumination for the vehicle operator, such as headlight and taillight assemblies, daylight running lamps (DRL), center high-mounted safety lamps (CHMSL), etc. The method 300 continues to block 309 to determine a visual response, if any, and commanding one or more light-generating components to output a visual cue designed to drive away the living object.

[0032] An intended application of at least some of the disclosed features and concepts may include motor vehicles that have autonomous driving capabilities. As user herein, a motor vehicle with autonomous driving capabilitiesalso known as autonomous vehicles or self-driving vehiclesincludes Society of Automotive Engineer (SAE) classified Level 2 Partial Automation vehicles (automated vehicle control of steering, acceleration and deceleration with driver physically disengaged from steering wheel and pedals), SAE classified Level 5 Full Automation vehicles (full-time performance by automated driving system of all aspects of dynamic driving under all roadway and environmental conditions), and any variation therebetween. If the vehicle 10 is equipped with autonomous driving capabilities, the living foreign obstruction remediation protocol 300 may include autonomously repositioning the motor vehicle to evade any detected living objects at block 311. The aforementioned repositioning may include rerouting the vehicle to a different charging station or rearranging the vehicle at the current charging station. Completing this particular operation may require the ECU 26 communicate with the wireless charging station 20 to ascertain the design of the charging station 20, the layout and traffic of the surrounding area, the availability/compatibility of neighboring charging stations, etc.

[0033] Upon completion of the remedial actions 307 and/or 309 and/or 311, protocol 300 may optionally initiate a retry strategy to assess whether or not the first remedial action strategy was successful in resolving the incursion of a living foreign object and, if not, whether or not to implement further procedures to address the presence of the living object. By way of example, and not limitation, protocol 300 may require the vehicle ECU 26 communicate with one or more of the sensors 28, 30 to determine, at decision block 313, if the obstruction has been removed (e.g., is no longer within the predetermined proximity of the wireless vehicle charging station 20). If it is determined that the obstruction is no longer present or the situation has otherwise been rectified (Block 313=Y), the method 300 continues back to protocol 200 of FIG. 2, as indicated with the circled B in FIGS. 2 and 3, and then protocol 300 terminates.

[0034] Responsive to a determination that the obstruction is still present or the situation has otherwise not been resolved (Block 313=N), protocol 300 moves to decision block 315 to determine whether or not to loop back to remedial actions 307, 309 and/or 311. This may require first determining, at block 315, if a predetermined time period has expired since the protocol 300 was first initiated (e.g., a timeout event has occurred) and/or if a maximum number of cycles (e.g., a default of three attempts) of the repeated loop illustrated in FIG. 3 has been completed. If the predetermined time period has expired or the maximum number of cycles has been completed (Block 315=Y), the retry strategy is terminated and the method 300 continues back to protocol 200 of FIG. 2, as indicated with the circled B in FIG. 3. However, if the determination at decision block 315 is negative (Block 315=N), protocol 300 will re-execute blocks 307-315 in a continuous loop until block 313 or block 315 results in a positive determination.

[0035] When it is determined that a detected obstruction is a non-living object, the non-living foreign obstruction remediation protocol 400 illustrated in FIG. 4 is initiated via the vehicle ECU 26. This protocol 400, or select portions thereof, may be considered an automated second remedial action strategy designed to ameliorate the undesirable intrusion of foreign objects that may impede or otherwise affect wireless charging. Similar to the living foreign obstruction remediation protocol 300 of FIG. 3, protocol 400 of FIG. 4 may begin at decision block 401 with determining whether or not to alert a user, e.g., via electronic transmission, of the detected intrusion of the non-living object. In this regard, protocol 400 of FIG. 4 may include any of the options and features discussed above with respect to the protocol 300 of FIG. 3, and vice versa, unless otherwise explicitly disclaimed. At block 403, the ECU 26 receives a user input to proceed with current or default settings, one or more user inputs with user-desired parameters that modify one or more portions of the second remedial action strategy, or a user input overriding or otherwise disengaging the protocol 400. If a customer notification is not sent (i.e., decision block 401 is omitted or disengaged) or a user response is not received (Block 401=N), the method 400 proceeds to block 405 and default remedial action settings are implemented.

[0036] With continuing reference to FIG. 4, non-living foreign obstruction remediation protocol 400 continues to blocks 407 and 409 to generate an automated vehicle response to the detected obstruction in an attempt to resolve the situation. This automated response may include, as some non-limiting examples, commanding the motor vehicle to generate a visual cue and/or an audible cue that is/are designed to drive away the living object. Another optional or alternative automated response may include resituating or otherwise moving the vehicle to avoid vehicle interaction with the living obstruction. As one example, the second remedial action strategy includes, at block 407, determining an audible and/or visual response, if any, and commanding one or more of the noise-generating and/or sound-generating components to output an audible cue designed to cause the non-living object to be moved. For instance, if the non-living object is an automobile that is obstructing the path of the vehicle 10, the audible/visible cue generated at block 407 may be designed to warn the automobile's operator/on-board controller to move the automobile. If the vehicle 10 is equipped with autonomous driving capabilities, the non-living foreign obstruction remediation protocol 400 may include autonomously repositioning, relocating, rerouting, etc., the motor vehicle to evade any detected obstruction at block 409.

[0037] Upon completion of the remedial actions 407 and/or 409, protocol 400 of FIG. 4 may optionally initiate a retry strategy to assess whether or not the second remedial action strategy was successful in resolving the incursion of a non-living foreign object and, if not, whether or not to implement further procedures to address the presence of the living object. By way of example, and not limitation, protocol 400 may require the vehicle ECU 26 communicate with one or more of the sensors 28, 30 to determine, at decision block 411, if the obstruction has been removed (e.g., is no longer within the predetermined proximity of the wireless vehicle charging station 20). If the obstruction is no longer present or the situation has been rectified (Block 411=Y), the method 400 continues back to protocol 200 of FIG. 2, as indicated with the circled D in FIGS. 2 and 4, and protocol 400 terminates. Responsive to the obstruction still being present or the situation not being resolved (Block 411=N), protocol 400 moves to decision block 413 to determine whether or not to loop back to remedial actions 407 and/or 409. At block 413, the ECU 26 may first determine if a timeout event has occurred or if a maximum number of cycles of the loop illustrated in FIG. 4 has been completed. If the timeout event has occurred or the maximum number of cycles has been completed (Block 413=Y), the retry strategy is terminated and the method 400 continues back to protocol 200 of FIG. 2. However, if the determination at decision block 413 is negative (Block 413=N), protocol 400 will re-execute blocks 407-413 in a continuous loop until block 411 or block 413 results in a positive determination.

[0038] Aspects of this disclosure may be implemented, in some embodiments, through a computer-executable program of instructions, such as program modules, generally referred to as software applications or application programs executed by an onboard vehicle computer. The software may include, in non-limiting examples, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. The software may form an interface to allow a computer to react according to a source of input. The software may also cooperate with other code segments to initiate a variety of tasks in response to data received in conjunction with the source of the received data. The software may be stored on any of a variety of memory media, such as CD-ROM, magnetic disk, bubble memory, and semiconductor memory (e.g., various types of RAM or ROM).

[0039] Moreover, aspects of the present disclosure may be practiced with a variety of computer-system and computer-network configurations, including multiprocessor systems, microprocessor-based or programmable-consumer electronics, minicomputers, mainframe computers, and the like. In addition, aspects of the present disclosure may be practiced in distributed-computing environments where tasks are performed by remote-processing devices that are linked through a communications network. In a distributed-computing environment, program modules may be located in both local and remote computer-storage media including memory storage devices. Aspects of the present disclosure may therefore, be implemented in connection with various hardware, software or a combination thereof, in a computer system or other processing system.

[0040] Any of the methods 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, or method disclosed herein may be embodied in software stored on a tangible medium such as, for example, a flash memory, a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), or other memory devices, but persons of ordinary skill in the art will readily appreciate that the entire algorithm and/or parts thereof could alternatively be executed by a device other than a controller and/or embodied in firmware or dedicated hardware in a well-known manner (e.g., it may be implemented by an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable logic device (FPLD), discrete logic, etc.). Further, although specific algorithms are described with reference to flowcharts depicted herein, persons of ordinary skill in the art will readily appreciate that many other methods of implementing the example machine readable instructions may alternatively be used.

[0041] While aspects of the present disclosure have been described in detail with reference to the illustrated embodiments, 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 construction and compositions disclosed herein; any and all modifications, changes, and variations apparent from the foregoing descriptions are within the scope of the disclosure as defined in the appended claims. Moreover, the present concepts expressly include any and all combinations and subcombinations of the preceding elements and features.