Charging prompting system for vehicle

Abstract

A charge prompt system for a vehicle includes a battery including a battery controller storing battery data and a speaker system. The charge cue system also includes an electronic control unit (ECU) communicatively coupled with the battery controller and the speaker system. The ECU includes data processing hardware configured with an auditory cue application and memory hardware storing charging parameters. The auditory cue application includes an auditory progress monitor configured as a function of the charging parameter and configured to project at least one cue at the speaker system in response to the battery data.

Description

[0001] introduction

[0002] The information provided in this section is for the purpose of presenting the general context of this disclosure. The work of the currently named inventors, to the extent described in this section, and in aspects that may not qualify as prior art at the time of filing, is neither expressly nor implicitly acknowledged as prior art to this disclosure. Technical Field

[0003] This disclosure generally relates to a charging reminder system for vehicles. Background Technology

[0004] Electric vehicles (EVs) operate by charging at various charging facilities. For example, users can charge their EVs at home chargers or utilize public chargers. Typically, users do not receive feedback regarding whether a charging connection has been established between the chosen public charger and the vehicle. Furthermore, users may not receive feedback on the level and status of the charging process. Therefore, there is a need to improve feedback regarding the charging process and progress at both public and private charging facilities. Summary of the Invention

[0005] In some aspects, a charging reminder system for a vehicle includes a battery and a charging port. The battery includes a battery controller for storing battery data, and the charging port includes sensors. The sensors are configured to capture connection data at the charging port. The charging reminder system also includes a speaker system and an electronic control unit (ECU) communicatively coupled to each of the battery controller, the charging port, and the speaker system. The ECU includes data processing hardware configured for an auditory reminder application and memory hardware for storing charging parameters based on the battery data and connection data. The auditory reminder application includes an auditory progress monitor configured as a function of the charging parameters and configured to project at least one reminder at the speaker system in response to the charging parameters.

[0006] In some examples, charging parameters may include at least one of connection status, authorization status, and charging status. A proximity sensor may be coupled to the vehicle body and configured to collect proximity data. The proximity sensor may be communicatively coupled to the ECU, and an auditory cue application may be configured to project at least one cue in response to proximity data and connection status. Optionally, an auditory progress monitor may include cue characteristics including at least one of volume, tone, pitch, and frequency. In some cases, the auditory progress monitor may be configured to change one or more of the cue characteristics in response to one or more of the charging parameters. In some configurations, the charging cue system may include a user device that communicates with the ECU and includes a mobile wallet. The mobile wallet may include an auditory cue application. Optionally, charging parameters may include a target charging level, and the auditory progress monitor may be configured to issue at least one cue in response to the battery's state of charge corresponding to the charging level.

[0007] In other aspects, the charging reminder system for a vehicle includes a battery and a speaker system, the battery including a battery controller that stores battery data. The charging reminder system also includes an electronic control unit (ECU) communicatively coupled to the battery controller and the speaker system. The ECU includes data processing hardware configured for an auditory cueing application and memory hardware storing charging parameters. The auditory cueing application includes an auditory progress monitor configured as a function of the charging parameters and configured to project at least one cue at the speaker system in response to battery data.

[0008] In some examples, charging parameters may include at least one of connection status, authorization status, and charging status. A proximity sensor may be coupled to the vehicle body and configured to collect proximity data. The proximity sensor may be communicatively coupled to the ECU, and an auditory cue application may be configured to project at least one cue in response to proximity data and connection status. Optionally, an auditory progress monitor may include cue characteristics including at least one of volume, tone, pitch, and frequency. In some cases, the auditory progress monitor may be configured to change one or more of the cue characteristics in response to one or more of the charging parameters. In some configurations, the user equipment may communicate with the ECU and may include a mobile wallet. The mobile wallet may include an auditory cue application. Optionally, charging parameters may include a target charging level, and the auditory progress monitor may be configured to issue at least one cue in response to the battery's state of charge corresponding to the charging level.

[0009] In another aspect, a computer-implemented method causes data processing hardware to perform operations when executed by data processing hardware. The operations include detecting a charger connection at a vehicle's charging port via a charging sensor, activating an auditory cueing application via an electronic control unit (ECU) in response to the detected connection, and executing an auditory progress monitor in response to the activated auditory cueing application. The operations also include issuing a connection cue from the executed auditory progress monitor, monitoring vehicle charging parameters via the auditory cueing application, and updating the auditory progress monitor via cue projection based on the charging parameters.

[0010] In some examples, the cue projection may be a function of charging parameters. Optionally, updating the auditory progress monitor may include issuing a charging cue based on the charging status of the charging parameters. In some cases, updating the auditory progress monitor may include issuing at least one cue at one or more locations in the vehicle's speaker system and user equipment. Attached Figure Description

[0011] The accompanying drawings described herein are for illustrative purposes only for the selected configurations and are not intended to limit the scope of this disclosure.

[0012] Figure 1 This is a schematic diagram of a charging reminder system according to this disclosure;

[0013] Figure 2 This is an exemplary block diagram of a charging reminder system according to the present disclosure, the charging reminder system including an electronic control unit (ECU), a battery controller, a port sensor, a proximity sensor, a speaker system, and a charging station coupled via a network communication;

[0014] Figure 3 This is another exemplary block diagram of a charging reminder system according to the present disclosure, which includes communication between an ECU, a charging station, and a user equipment;

[0015] Figure 4 This is an exemplary flowchart of a charging reminder system according to the present disclosure;

[0016] Figure 5 This is another exemplary block diagram of a charging reminder system according to the present disclosure, which includes different prompts from an auditory progress monitor;

[0017] Figure 6 This is another exemplary flowchart of a charging reminder system according to this disclosure; and

[0018] Figure 7 yes Figure 5 The following is a flowchart of the charging reminder system.

[0019] In all the accompanying drawings, the corresponding reference numerals denote the corresponding parts. Detailed Implementation

[0020] The example configuration will now be described more fully with reference to the accompanying drawings. The example configuration is provided so that this disclosure will be thorough and will fully communicate the scope of this disclosure to those skilled in the art. Specific details, such as examples of specific components, apparatus, and methods, are set forth to provide a thorough understanding of the configuration of this disclosure. It will be apparent to those skilled in the art that specific details are not required, the example configuration may be embodied in many different forms, and the specific details and example configuration should not be construed as limiting the scope of this disclosure.

[0021] The terminology used herein is for the purpose of describing a particular exemplary configuration only and is not intended to be limiting. As used herein, the singular articles “a,” “an,” and “the” may also be intended to include plural forms unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “including,” and “having” are inclusive and therefore specify the presence of features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. The method steps, processes, and operations described herein should not be construed as requiring them to be performed in the specific order discussed or shown, unless specifically identified as such. Additional or alternative steps may be employed.

[0022] When an element or layer is referred to as “on another element or layer,” “joined to,” “connected to,” “attached to,” or “linked to” another element or layer, it may be directly on, joined to, connected to, attached to, or linked to the other element or layer, or there may be intermediate elements or layers present. Conversely, when an element is referred to as “directly on another element or layer,” “directly joined to,” “directly connected to,” “directly attached to,” or “directly linked to” another element or layer, there may be no intermediate elements or layers present. Other terms used to describe relationships between elements should be interpreted in a similar manner (e.g., “between” vs. “directly between,” “adjacent” vs. “directly adjacent,” etc.). As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0023] The terms “first,” “second,” “third,” etc., may be used herein to describe various elements, components, regions, layers, and / or parts. These elements, components, regions, layers, and / or parts should not be limited by these terms. These terms may be used only to distinguish one element, component, region, layer, or part from another. Unless the context clearly indicates otherwise, terms such as “first,” “second,” and other numerical terms do not imply order or sequence. Therefore, without departing from the teachings of the example configuration, the first element, component, region, layer, or part discussed below may be referred to as the second element, component, region, layer, or part.

[0024] In this application, including the following definitions, the term "module" may be replaced by the term "circuit". The term "module" may refer to, be part of, or include the following: application-specific integrated circuit (ASIC); digital, analog, or mixed-signal analog / digital discrete circuit; digital, analog, or mixed-signal analog / digital integrated circuit; combinational logic circuit; field-programmable gate array (FPGA); processor (shared, dedicated, or grouped) that executes code; memory (shared, dedicated, or grouped) that stores code executed by the processor; other suitable hardware components that provide the described functionality; or combinations of some or all of the foregoing, such as in a system-on-a-chip.

[0025] The term "code" as used above can include software, firmware, and / or microcode, and can refer to programs, routines, functions, classes, and / or objects. The term "shared processor" includes a single processor that executes some or all of the code from multiple modules. The term "group processor" includes processors that, in combination with additional processors, execute some or all of the code from one or more modules. The term "shared memory" covers a single memory that stores some or all of the code from multiple modules. The term "group memory" includes memory that, in combination with additional memory, stores some or all of the code from one or more modules. The term "memory" can be a subset of the term "computer-readable medium." The term "computer-readable medium" does not include transient electrical and electromagnetic signals propagating through the medium and can therefore be considered tangible and non-transitory memory. Non-limiting examples of non-transitory memory include tangible computer-readable media, which include non-volatile memory, magnetic memory, and optical memory.

[0026] The apparatus and methods described in this application can be implemented, partially or entirely, by one or more computer programs executed by one or more processors. The computer program includes processor-executable instructions stored on at least one non-transitory tangible computer-readable medium. The computer program may also include and / or depend on stored data.

[0027] A software application (i.e., a software resource) can refer to computer software that enables a computing device to perform tasks. In some examples, a software application may be referred to as an "application," "app," or "program." Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and game applications.

[0028] Non-transitory memory can be a physical device used to temporarily or permanently store programs (e.g., instruction sequences) or data (e.g., program state information) for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used in firmware, such as boot programs). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase-change memory (PCM), and magnetic disks or magnetic tapes.

[0029] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and can be implemented using high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0030] Various implementations of the systems and techniques described herein can be implemented in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (Application-Specific Integrated Circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementations in one or more computer programs executable and / or interpretable on a programmable system, which includes at least one programmable processor, which may be dedicated or general-purpose, coupled to receive data and instructions from a storage system, at least one input device, and at least one output device, and to transmit data and instructions to the storage system, at least one input device, and at least one output device.

[0031] The processes and logical flows described in this specification can be executed by one or more programmable processors (also known as data processing hardware) that execute one or more computer programs to perform functions by manipulating input data and generating output. The processes and logical flows can also be executed by special-purpose logic circuitry (e.g., FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits). As an example, processors suitable for executing computer programs include both general-purpose and special-purpose microprocessors, as well as any one or more processors of any type of digital computer. Typically, the processor receives instructions and data from read-only memory or random access memory, or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or operatively coupled to receive data from or transfer data to, or both. However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD-ROMs and DVD-ROMs. Processors and memory may be supplemented by or incorporated into dedicated logic circuitry.

[0032] To provide interaction with a user, one or more aspects of this disclosure can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touchscreen) for displaying information to the user and optionally a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual, auditory, or tactile feedback; and input from the user can be received in any form, including sound, speech, or tactile input. Additionally, the computer can interact with the user by sending documents to and receiving documents from the device used by the user; for example, by sending a webpage to a web browser on the user's client device in response to a request received from a web browser.

[0033] refer to Figure 1-3The charging reminder system 10 for vehicle 100 includes an electronic control unit (ECU) 12 configured with an auditory cue application 14. In some examples, the auditory cue application 14 may be configured as part of a user device 200 communicatively coupled to vehicle 100 and may also be part of the charging reminder system 10. The charging reminder system 10 is configured to interconnect vehicle 100 and user device 200 with charging station 300. The ECU 12 of vehicle 100 may be communicatively coupled to user device 200 and charging station 300 via network 400. The charging reminder system 10 is configured to audibly assist the user in monitoring the various stages and progress associated with charging of vehicle 100. Therefore, vehicle 100 is contemplated as an electric vehicle (EV) 100 including battery 102. However, the auditory cue application 14 described herein may be modified for use with internal combustion engine (ICE) vehicle 100 and / or hybrid vehicle 100.

[0034] Battery 102 includes a battery controller 104 that collects battery data 106. Battery data 106 communicates with an ECU 12, which is part of a charging alert system 10. For example, battery data 106 may indicate the charging status 108 and may typically inform an auditory alert application 14 of the degree or level of charging required to achieve optimal battery performance, as described herein. Vehicle 100 also includes a charging port 109 equipped with a port sensor 110 configured to collect port data 112, which also communicates with the ECU 12, which is part of the charging alert system 10, as described herein. ECU 12 receives battery data 106 and port data 112 and updates charging parameters 20 accordingly.

[0035] Further reference Figure 1-3 The ECU 12 includes data processing hardware 16 configured to execute the auditory cue application 14 and memory hardware 18 storing charging parameters 20 of the charging reminder system 10. The memory hardware 18 communicates with the data processing hardware 16, enabling the auditory cue application 14 to utilize the charging parameters 20 stored by the memory hardware 18 during operation. For example, the auditory cue application 14 includes an auditory progress monitor 22 executed by the charging reminder system 10 based on the charging parameters 20. The auditory progress monitor 22 is designed to provide the user with auditory updates regarding the charging state 108 of the battery 102. The charging parameters 20 are used to update the auditory progress monitor 22 via cues 24 projected through the speaker system 114 of the vehicle 100 and / or user equipment 200.

[0036] For example, the speaker system 114 can be configured both inside the vehicle 100 and outside the vehicle 100. In some examples, the auditory progress monitor 22 can be projected via the speaker system 114 outside the vehicle 100, so that a user can approach the vehicle 100 and hear updates from the auditory progress monitor 22 based on cue 24. In some cases, the vehicle 100 is also configured with a proximity sensor 116 that captures proximity data 118 relative to the vehicle 100. For example, the proximity sensor 116 is positioned along the body 120 of the vehicle 100. The proximity data 118 captured by the proximity sensor 116 informs the charging alert system 10 whether the user is approaching or near the vehicle 100. Detecting a user's approach to the vehicle 100 can trigger the charging alert system 10 to activate the auditory progress monitor 22 to project cue 24. Thus, the auditory progress monitor 22 can selectively execute cue 24 based on the proximity data 118. Cue 24 can represent a charging stage 26 determined by charging parameters 20.

[0037] The auditory cue application 14 receives charging parameters 20 from memory hardware 18 to update the auditory progress monitor 22 to reflect charging stage 26. Charging stage 26 relates to the execution of charging the battery 102. In contrast, in addition to charging execution, the charging parameters 20 include status checks. For example, the charging parameters 20 reflect various stages of connecting to the charging station 300 and executing the charging process. The charging parameters 20 are configured to correspond to cue 24 issued by the auditory progress monitor 22, such that the cue 24 reflects different parameters of the charging parameters 20. For example, the cue 24 issued by the auditory progress monitor 22 may have different cue characteristics 28 set by the auditory cue application 14. In some cases, the user can customize the cue characteristics 28 to correspond to one or more of the charging parameters 20. Cue characteristics 28 include, but are not limited to, volume, tone, pitch, and frequency. In some instances, the auditory progress monitor 22 is configured to change one or more of the cue characteristics 28 in response to one or more of the charging parameters 20. The prompt 24 is designed to emit pleasant sounds from the speaker system 114 of the vehicle 100 and / or projected via the user equipment 200.

[0038] The cue feature 28 can be adjusted or otherwise modified by the user to customize the cue 24. For example, the user can customize the cue 24 to have a first cue feature 28 during a first charging phase 26 and a second cue feature 28 during a second charging phase 26. As the battery 102 is charging, the frequency 28 of the cue 24 emitted by the auditory progress monitor 22 can be increased. The increase in the frequency of the cue 24 indicates that the charging phase 26 is in progress and nearing completion. It is also conceivable that the auditory progress monitor 22 can emit multiple different cue 24 throughout the entire charging duration, corresponding to different charging parameters 20.

[0039] refer to Figure 2-4 Charging parameters 20 include connection status 30, authorization status 32, charging status 34, and in some examples, payment status. Charging parameters 20 are defined by one or more of battery data 106 and port data 112. For example, when port sensor 110 detects that vehicle 100 is connected to charging station 300, connection status 30 is updated with port data 112, and auditory progress monitor 22 can issue a prompt 24 with a prompting feature 28 corresponding to the connection status 30 of vehicle 100 and charging station 300. Charging prompt system 10 can then receive an authentication notification from charging station 300 to inform of the authorization status 32 of charging parameters 20. For example, charging station 300 may be a plug-in charging station, where charging phase 26 is initiated once vehicle 100 authorizes charging station 300. Once vehicle 100 has authenticated charging station 300, authorization status 32 is updated, indicated by the prompt from auditory progress monitor 22, and charging phase 26 can begin. Therefore, the auditory progress monitor 22 can provide auditory updates to the user by projecting a cue 24 in response to each of the connection state 30 and the authorization state 32.

[0040] Figure 4 The diagram illustrates an example flowchart of the auditory progress monitor 22. At point 500, the user connects vehicle 100 to charging station 300, and in response, the auditory progress monitor 22 issues a connection prompt 24a at point 502. Figure 5 Then, at 504, vehicle 100 authorizes charging station 300 to charge battery 102. Auditory progress monitor 22 can play a prompt 24 while the user waits for authorization to notify the user that authorization status 32 is in progress. Once authorized, at 506, auditory progress monitor 22 executes an authorization prompt 24b indicating that charging station 300 has been authorized, and charging can begin at 508.

[0041] At 510, the auditory progress monitor 22 can continuously issue charging cues 24c throughout the charging phase 26 to reflect the charging status 34. In other examples, the auditory progress monitor 22 can issue charging cues 24c in response to proximity data 118. For example, the auditory cue application 114 can receive proximity data 118 captured by the proximity sensor 116 indicating that the user is near or close to the vehicle 100. Thus, the proximity sensor 116 is communicatively coupled to the ECU 12, and the auditory cue application 14 is configured to project cues 24 in response to proximity data 118 and connection status 30. In response, the auditory progress monitor 22 can issue cues 24 to reflect the charging phase 26 and the corresponding charging status 34. Once the charging phase is complete, the auditory progress monitor 22 can issue a completion cue 24d at 512.

[0042] Therefore, the auditory progress monitor 22 can issue a prompt 24 based on the connection state 30, and can issue a subsequent prompt 24 in response to the authorization state 32 being confirmed. As mentioned above, the auditory progress monitor 22 can change the prompt characteristic 28 based on the charging parameter 20, since the charging parameter 20 generally corresponds to the charging stage 26. Therefore, each charging parameter 20 can be associated with a different prompt characteristic 28, which can be set by the user or programmed as part of the auditory prompting application 14.

[0043] In some examples, charging parameter 20 may include a target charging level 36 stored as part of charging state 34. For example, target charging level 36 may correspond to a battery percentage less than fully charged or charged to 100% (100%) or fully charged. Target charging level 36 can be set and adjusted by the user to a desired level. In some cases, the user may want to charge battery 102 to full charge to minimize stops along the route. In other instances, the user may want to stop the charging process at less than a full charge percentage to optimize the operational lifespan of battery 102. Target charging level 36 can be set and adjusted by the user via an audible cue application 14 communicatively coupled to charging parameter 20.

[0044] As described above, the auditory progress monitor 22 provides a prompt 24 associated with the charging state 34 and can adjust the prompt characteristics 28 based on the charging state 34. In some cases, the user may interrupt or stop charging. For example, the user may disconnect the vehicle 100 from the charging station 300 before reaching the target charging level 36 or being fully charged. In response, the auditory progress monitor 22 can then issue a prompt 24 with different prompt characteristics 28 to notify the user of the interrupted charging state 34. If the interruption is intentional, the user can reconnect the vehicle 100 or ignore the prompt 24. In some cases, the vehicle 100 may unintentionally disconnect from the charging station 300, so the prompt 24 can warn the user of the interruption of the charging stage 26. If the vehicle 100 completes charging, the auditory progress monitor 22 issues a prompt 24 corresponding to the completion of the charging stage 26. As described above, the prompt 24 associated with the charging stage 26 can be customized by the user, so the user can identify the charging stage 26 based on the prompt 24 issued by the auditory progress monitor 22.

[0045] Furthermore, different charging parameters 20 can be configured and associated with different prompts 24 having different prompt characteristics 28. For example, the prompt characteristic 28 of the prompt 24 associated with connection state 30 can be different from the prompt characteristic 28 of the prompt 24 associated with charging state 34. Customization of the prompts 24 with corresponding charging parameters 20 further helps the user monitor the charging progress using audio signals. The auditory progress monitor 22 advantageously helps the user monitor the charging stage 26 while freely leaving the vehicle 100 or performing alternative functions while waiting for charging to complete. Conversely, the user can listen to the corresponding prompts 24 to notify the user of the charging stage 26 via the auditory progress monitor 22.

[0046] refer to Figure 2-5 The auditory progress monitor 22 can be configured to emit a single cue 24 with changing cue characteristics 28 based on a charging phase 26. For example, the volume 28 of the cue 24 can increase as the charging phase 26 progresses. In other examples, the auditory progress monitor 22 can emit multiple cue 24s, each with different cue characteristics 28 corresponding to different stages of the charging phase 26, as generally mentioned above. For example, each cue 24 can have a different pitch 28 to reflect different stages of the charging phase 26. The user can identify the charging state 34 based on the auditory progress monitor 22 and the corresponding cue 24.

[0047] Refer again Figure 4 and 5 The charging prompt system 10 can include various stages or phases associated with the charging parameters 20, as described above, and it notifies the audible progress monitor 22. For example, when a user attaches the vehicle 100 to the charging station 300, the audible progress monitor 22 can issue a prompt 24 indicating whether the vehicle 100 is correctly attached to the charging station 300. If the vehicle 100 is correctly connected, the audible progress monitor 22 can issue a connection prompt 24a, and if there is an error in the connection between the vehicle 100 and the charging station 300, the audible progress monitor 22 can issue an error prompt 24e, which is different from the connection prompt 24a. Thus, the user can be warned to adjust or check the connection between the vehicle 100 and the charging station 300 via the audible error prompt 24e.

[0048] Furthermore, vehicle 100 can use the authorization process to verify charging station 300. Auditory progress monitor 22 can play authorization prompts 24b corresponding to the authentication process and issue authorization prompts 24b in response to confirmation of authorization status 32. Authorization prompts 24b provide feedback to the user on the progress of the ongoing authentication task and instruct the user to wait until authorization status 32 has been confirmed. Once authorization status 32 is confirmed, charging status 34 can be updated to project or execute charging prompts 24c corresponding to charging stage 26.

[0049] Therefore, the charging notification system 10 can issue a connection notification 24a via the audible progress monitor 22, which corresponds to the confirmation of connection status 30. Then, the charging notification system 10 can coordinate with the charging station 300 via the network 400 to authorize the vehicle 100 to the charging station 300, as reflected in the authorization status 32. The authorization status 32 can also reflect a potential payment between the user (i.e., via user equipment 200 or other payment methods) and the charging station 300. During the authorization process, the audible progress monitor 22 can play a pleasant looping notification 24 to indicate that the charging notification system 10 is in the authorization process. Once authenticated, the audible progress monitor 22 can issue an authorization notification 24b corresponding to positive authentication and a charging notification 24c corresponding to the start of charging phase 26.

[0050] The charging prompt 24c may have successive phases associated with charging phase 26, allowing the prompt characteristic 28f to change to reflect the new charging phase 26. Once the battery data 106 reflects the charge corresponding to the target charging level 36, the audible progress monitor 22 can issue a completion prompt 24d. As described above, the charging prompt 24c can be updated or modified throughout charging phase 26 by modifying or changing the prompt characteristic 28. Changes in the prompt characteristic 28 provide the user with audible updates on the charging progress and status. In some cases, the charging prompt 24c is configured to reflect charging phase 26 and station characteristic 302. Station characteristic 302 may include, for example, the power level 304 of charging station 300. The power level 304 may reflect the quality and type of charging provided by charging station 300. In some examples, the charging quality may correspond to the duration taken for charging station 300 to complete charging, and the charging type may reflect whether charging station 300 is configured as a fast charger.

[0051] Based on cue feature 28, cue 24 can provide feedback to the user regarding power level 304 and can also notify the user of any potential errors associated with charging station 300. Furthermore, the user can approach vehicle 100 when it is connected to charging station 300, and auditory cue application 14 can trigger auditory progress monitor 22 to project or otherwise issue cue 24 based on proximity data 118. The issued cue 24 can reflect station feature 302 by altering cue feature 28.

[0052] Once charging is complete, the auditory progress monitor 22 issues a completion prompt 24d, which may have different prompting features 28 indicating the completion of charging phase 26, as described above. If the user has set a target charging level 36, the auditory progress monitor 22 can issue a completion prompt 24d once the battery 102 is charged to the target charging level 36. The auditory prompt application 14 can also issue a reminder via a reminder prompt 24f that the target charging level 36 is less than full charge.

[0053] Refer again Figure 3-5 User device 200 may be equipped with an auditory cues application 14. For example, user device 200 may include a mobile wallet 202 configured with the auditory cues application 14. The mobile wallet 202 may be used to operate or otherwise navigate aspects of the operation of vehicle 100. The auditory cues application 14, as part of the mobile wallet 202, helps the user to project an auditory progress monitor 22 via user device 200 when the user may be away from vehicle 100. For example, the user may connect vehicle 100 to charging station 300 and leave vehicle 100 at charging station 300 while the user performs other activities. The auditory cues application 14 on user device 200 can help the user monitor the charging progress of vehicle 100 via auditory progress monitor 22, which projects cues 24 via user device 200.

[0054] Therefore, users can advantageously monitor the charging stage 26 while away from the vehicle 100. Furthermore, the auditory progress monitor 22 helps provide updates to the user via audible cues 24, freeing the user from having to monitor the user device 200 in other ways to obtain visual cues or updates that might be associated with other applications. In some examples, users can manually set the cue characteristics 28 of various cues 24 associated with different charging stages 26. By manually setting the cue characteristics 28 based on the corresponding charging stage 26, users can audibly track the charging stage 26 via auditory cues 24 using the auditory progress monitor 22.

[0055] Now for reference Figure 6 and 7 An exemplary flowchart of the charging notification system 10 is shown below. At 600, the charging notification system 10 is activated by the vehicle 100 connecting to the charging station 300. At 602, communication between the vehicle 100 and the charging station 300 is initiated, and at 604, the authorization process begins. At 606, the charging notification system 10 determines whether authorization exists between the charging station 300 and the vehicle 100. If no authorization exists, the charging notification system 10 executes an error message 24e at 608. If authorization exists, the charging notification system 10 executes an authorization message 24b at 610, and charging begins at 612.

[0056] At 614, the charging reminder system 10 monitors the charging progress via the auditory progress monitor 22, and at 616 determines whether charging is complete. If charging is not complete, the charging reminder system 10 determines at 618 whether an error has been detected. If no error is detected, the charging reminder system 10 continues to monitor the charging progress. If an error is detected, the charging reminder system determines at 620 and 622 whether there is power loss or whether charging was interrupted below the target charging level 36, and issues an error message 24e at 624. If charging is complete, the charging reminder system 10 determines at 626-630 whether charging was stopped by the user, completed to the target charging level 36, or completed to full charging, and executes a completion message 26d at 632.

[0057] Refer again Figure 1-7 The charging notification system 10 is configured to help users audibly monitor the charging stage 26 and connection status 30 of vehicle 100 relative to charging station 300. By projecting notifications 24 from the auditory progress monitor 22 via speaker system 114, users can audibly track the progress of each stage of vehicle 100's connection, authorization, and charging. Therefore, the auditory progress monitor 22 provides a convenient process through which users can continue other activities while monitoring the charging progress of vehicle 100. Furthermore, incorporating the auditory progress monitor 22 as part of the mobile wallet 202 on user device 200 via auditory notification application 14 maximizes the convenience associated with audible tracking and monitoring of the charging stage 26.

[0058] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of this disclosure. Therefore, other embodiments are within the scope of the appended claims.

[0059] The foregoing description is provided for illustrative and descriptive purposes. It is not intended to be exhaustive or limiting of this disclosure. Elements or features of a particular configuration are generally not limited to that particular configuration, but are interchangeable where applicable and can be used in selected configurations, even if not specifically shown or described. They can also be varied in many ways. Such variations should not be considered as departing from this disclosure, and all such modifications are intended to be included within the scope of this disclosure.

Claims

1. A charging reminder system for a vehicle, the charging reminder system comprising: A battery, the battery including a battery controller that stores battery data; loudspeaker system; as well as An electronic control unit (ECU) is communicatively coupled to the battery controller and the speaker system. The ECU includes data processing hardware configured for an auditory cues application and memory hardware storing charging parameters. The auditory cues application includes an auditory progress monitor configured as a function of the charging parameters and configured to project at least one cue at the speaker system in response to the battery data.

2. The charging reminder system according to claim 1, wherein, The charging parameters include at least one of connection status, authorization status, and charging status.

3. The charging reminder system of claim 2 further includes a proximity sensor coupled to the body of the vehicle and configured to collect proximity data.

4. The charging indication system according to claim 3, wherein, The proximity sensor is communicatively coupled to the ECU, and the auditory cue application is configured to project the at least one cue in response to the proximity data and the connection status.

5. The charging indication system according to claim 1, wherein, The auditory progress monitor includes cueing features, which include at least one of volume, pitch, tone, and frequency.

6. The charging prompting system of claim 5, wherein the auditory progress monitor is configured to change one or more of the prompting characteristics in response to one or more of the charging parameters.

7. The charging reminder system according to claim 1 further includes a user equipment, the user equipment communicating with the ECU and including a mobile wallet, the mobile wallet including the auditory reminder application.

8. The charging indication system according to claim 7, wherein, The charging parameters include a target charging level, and the auditory progress monitor is configured to issue the at least one prompt in response to the charging state of the battery corresponding to the charging level.

9. The charging reminder system according to claim 1 further includes a charging port, the charging port including a sensor configured to capture connection data at the charging port, and the memory hardware storing the charging parameters based on the connection data.

10. A vehicle equipped with a charging reminder system according to claim 1.

Images