Regional architecture audio system

Abstract

A regional audio system of a vehicle may include a microcontroller unit (MCU), a non-volatile memory device communicatively coupled with the MCU that stores audio files of different types of audio functions, and a digital signal processing (DSP) module communicatively coupled with the MCU. The DSP module may simultaneously process multiple types of audio functions through a layered architecture that integrates and preferentially processes different audio streams, including emergency calls, acoustic vehicle alarms, ringtones, and infotainment.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 652,601, filed May 28, 2024, entitled “ZONAL ARCHITECTURE AUDIO SYSTEM,” the entire contents of which are incorporated herein by reference. Background Technology

[0003] This application relates to a regional architecture for functionality and power distribution, and more specifically, to its audio system associated with an electric vehicle. Summary of the Invention

[0004] The subject matter disclosed in this invention provides an audio system implemented in a regional architecture. The audio system design disclosed in this invention can meet vehicle safety requirements while integrating the hardware or software used to implement the audio system. Attached Figure Description

[0005] Certain features of the subject matter are set forth in the appended claims. However, for illustrative purposes, several embodiments of the subject matter are illustrated in the following figures.

[0006] Figure 1A An exemplary top view of a vehicle having regional power distribution as described herein is illustrated.

[0007] Figure 1B An exemplary side view of a vehicle having regional power distribution as described herein is illustrated.

[0008] Figure 1C An exemplary block diagram of a system having regional power allocation as described herein is illustrated.

[0009] Figure 2 This is an exemplary schematic block diagram of an audio system.

[0010] Figure 3 This is an exemplary schematic block diagram of an audio system.

[0011] Figure 4 This is an exemplary schematic block diagram of an audio system.

[0012] Figure 5 This is an exemplary schematic block diagram of an audio system.

[0013] Figure 6 Exemplary methods associated with an audio system are illustrated. Detailed Implementation

[0014] The specific embodiments described below are intended to illustrate various configurations of the subject matter and are not intended to represent the only configuration in which the subject matter can be practiced. The accompanying drawings are incorporated herein and form part of the specific embodiments. The specific embodiments include particular details in order to provide a thorough understanding of the subject matter. However, those skilled in the art will clearly understand that the subject matter is not limited to the particular details set forth herein and can be practiced without these particular details. In some instances, well-known structures and components are shown in block diagram form to avoid confusion with the concepts of the subject matter.

[0015] The disclosed subject matter provides a regional architecture for power distribution and its circuit design, which allows for redundancy in power distribution, thus preventing failure of one or more power buses or electronic control units (ECUs). The ECU functions of the regional architecture can be based on geographical regions of the vehicle, such as the left front region, right front region, or rear region. Furthermore, audio functions can be integrated into a single regional controller, minimizing the number of audio components and the number of potential points of failure for audio functions. Audio functions can be implemented using a hierarchical architecture that allows for ASIL-rated redundancy and fault tolerance while prioritizing safety-related (e.g., emergency) audio events.

[0016] Figure 1A An exemplary top view of vehicle 300 is illustrated. As further described herein, vehicle 300 may include an electronic control unit (ECU) (e.g., ECU 10 and ECU 20) in the front portion 330 of vehicle 300, an ECU (e.g., ECU 30) in the rear portion 340 of vehicle 300, a DC-DC converter (DCDC) 50, a low-voltage (LV) battery 60 (e.g., a 12V battery), or a jump-start interface 17, etc.

[0017] Figure 1B An exemplary side view of vehicle 300 is illustrated. As shown, vehicle 300 may include one or more battery packs, such as a high-voltage (HV) battery pack 310 (e.g., 450V), which may be located near the central body portion 335 of vehicle 300. The HV battery pack 310 may be coupled to one or more electrical systems of vehicle 300 to provide power to the electrical systems. As further described herein, ECU 10, ECU 20, or ECU 30 may be communicatively connected to each other or have power distributed to each other, and the power or other operation of the electronic components of vehicle 300 may be functionally redundant.

[0018] In one or more embodiments, vehicle 300 may be an electric vehicle having one or more electric motors that use electricity from HV battery pack 310 to drive the wheels 302 of the vehicle. In one or more embodiments, vehicle 300 may also or alternatively include one or more chemically powered engines, such as gas-powered engines or fuel cell-powered motors. For example, the electric vehicle may be fully electric or partially electric (e.g., hybrid or plug-in hybrid). In various embodiments, vehicle 300 may be a fully autonomous vehicle capable of operating on roads without a human operator or driver, a partially autonomous vehicle capable of operating on some roads without a human operator or driver or capable of operating on roads under the supervision of a human operator, a driverless vehicle capable of operating on roads or other paths without any human occupants, or a human-operated (non-autonomous) vehicle configured for human operation.

[0019] exist Figure 1B In the example, vehicle 300 may be implemented as a truck (e.g., a pickup truck) with battery pack 310. As shown, HV battery pack 310 may include one or more battery modules 315, which may include one or more battery cells 320. However, this is merely illustrative, and in other specific embodiments, HV battery pack 310 may be provided without any battery modules 315 (e.g., in a cell-to-pack configuration).

[0020] like Figure 1B As shown, vehicle 300 may include a support structure, such as chassis 325 (e.g., frame, internal frame, or other support structure). Chassis 325 may support various components of vehicle 300. As shown, in some embodiments, chassis 325 may span the front portion 330 (e.g., hood or cover portion), central body portion 335, and rear portion 340 (e.g., luggage compartment, payload, or trunk portion) of vehicle 300. In one or more embodiments, HV battery pack 310 may be mounted on chassis 325 (e.g., within one or more of the front portion 330, central body portion 335, or rear portion 340). As shown, HV battery pack 310 may include one or more buses (e.g., one or more current collector elements) or be electrically coupled thereto. Figure 1B In the example, vehicle 300 includes a first busbar 345 and a second busbar 350, either or both of which may include conductive material to connect or otherwise electrically couple the battery module 315 or battery cell 320 to other electrical components of vehicle 300 to provide power to various systems or components of vehicle 300.

[0021] In other specific implementations, vehicle 300 may be implemented as another type of electric truck, electric delivery vehicle, electric motor vehicle, electric car, electric motorcycle, electric scooter, electric bus, electric passenger or commercial truck, hybrid vehicle or other means of transport, such as maritime or air transport, aircraft, helicopter, submarine, ship or drone, and / or any other mobile device having a battery pack 310 (e.g., which powers the propulsion or drive components of the mobile device).

[0022] Figure 1C An exemplary block diagram of a system 100 that may include multiple ECUs of a vehicle 300 is illustrated. An ECU is an embedded system that controls one or more electrical systems or subsystems in a vehicle. The positioning and connection of ECU 10, ECU 20, or ECU 30 can provide a degree of redundancy for failures that may be caused by a collision or other malfunction. The system 100 is designed to allow the vehicle 300 to operate safely for a period of time after a failure, such as being able to drive the vehicle 300 (e.g., steer, brake, or accelerate) to a safe location off the road or to operate the electronic control functions of the vehicle 300 (e.g., door locks), etc. As shown, ECU 10, ECU 20, and ECU 30 may be connected to a DC-DC converter 50 (also referred to herein as DC-DC bus 50) to operate DC-DC loads and to a low-voltage (LV) battery 60 (e.g., a 12V battery or LV battery bus 60) to operate LV battery loads. In the example, one or more ECUs (e.g., ECU 10) may include a fault isolation system 11. The fault isolation system 11 may include an isolating switch or a bidirectional switch 12. In some configurations, for safety reasons, only one ECU (e.g., ECU 10) may include a fault isolation system 11. As shown, ECU 10 may include a common bus 15, which may operate slightly differently from other buses (e.g., OR load bus 14) because the common bus allows bidirectional power flow to and from the LV battery 60, which may be a function of using the fault isolation system 11. The common bus (specific to ECU 10) allows bidirectional power flow, from the LV battery 60 to the DC-DC converter 50, or from the DC-DC converter 50 to the LV battery 60. The OR bus does not allow bidirectional power flow (it does not connect or isolate the LV battery 60 and DC-DC converter 50 networks). As another element of the shared property of both the common bus and the OR bus, in the event of a failure of either the DC-DC converter 50 or the LV battery 60, the common bus (or OR bus) will remain operational (e.g., will be available).

[0023] Continue to refer to Figure 1CEach ECU may have one or more dedicated functions that can be powered by DC-DC 50, LV battery 60, or LV DC-DC 41. ECU 10 is operable for Function 1, Function 2, and jump-start function. ECU 10 may be connected to jump-start interface 17 (e.g., wiring located in the rear portion 340 of vehicle 300). Jump-start interface 17 allows an external power source (e.g., a jump-start assembly) to be connected to ECU 10 to jump-start the vehicle's electronic functions, particularly when LV battery 60 is depleted. As further described herein, jump-start interface 17 may have multiple paths, including jump-start path 18 (e.g., to a microcontroller) and jump-start path 19 (e.g., to a two-way switch 12). Function 1 may include functions such as a first-line universal serial bus or Electronic Stability Program (ESP). Function 2 may include functions such as right door lock, passenger seat motor, right headlight, alarm module, in-vehicle infotainment (IVI), or front hood lock. In this example, function 1 of ECU 10 may be powered solely by DC-DC 50, while function 2 of ECU 10 may be powered by either DC-DC 50 (which may be the primary power source) or LV battery 60 (which may be the secondary power source), which may be referred to as common bus 15. ECU 10 may be located at the front right of vehicle 300, and thus can operate functions primarily for the right side of vehicle 300.

[0024] like Figure 1C As shown, ECU 20 can operate functions 3, 4, and 5. Function 3 may include functions such as front suspension valves or autonomous control modules. Function 4 may include functions such as steering angle sensors, front wiper motors, left door locks, left headlights, external near-field communication (NFC), or on-board diagnostics (OBD) ports. Function 5 may include functions such as electric power steering (EPAS), charging port doors, internal NFC, or electric power-assisted braking. In this example, function 3 of ECU 20 may be powered solely by DC-DC converter 50, and function 5 of ECU 20 may be powered solely by LV battery 60. Function 4 of ECU 20 may be powered by DC-DC converter 50 (which may be the primary power source) or LV battery 60 (which may be the secondary power source), which may be referred to as OR load 14 (also referred to herein as OR load bus 14). ECU 20 may be located at the front left of vehicle 300 and therefore can operate functions primarily for the left side of vehicle 300.

[0025] like Figure 1CAs shown, ECU 30 is operable for functions 6, 7, and 8. Function 6 may include functions such as license plate lights. Function 7 may include functions such as rear vehicle entry system sensors, power liftgate locks, trailer brakes, and rear right or left taillights. Function 8 may include functions such as right trailer brake lights or rear suspension valves. In this example, function 8 of ECU 30 may be powered solely by DC-DC converter 50, and function 6 of ECU 30 may be powered solely by LV battery 60. Function 7 of ECU 20 may be powered by DC-DC converter 50 (which may be the primary power source) or LV battery 60 (which may be the secondary power source). ECU 20 may be located at the front left of vehicle 300 and therefore operable functions primarily for the left side of vehicle 300.

[0026] Figure 1C The system 100 may include a battery management system (BMS) 40. The BMS 40 may be located in... Figure 1B The HV battery pack 310 is located at or near the LV DC-DC converter 41, which converts the HV DC to a lower voltage (such as 14V). The LV DC-DC converter 41 can help reduce the need for the LV battery 60 for certain operations, such as when the vehicle 300 is in standby mode (e.g., parked). It is anticipated that the functions disclosed herein (e.g., functions 1 through 8) can be controlled by other ECUs or powered by any of the listed power sources.

[0027] Figure 2An exemplary schematic block diagram of an audio system 200 that can be placed in a vehicle is illustrated. As shown, the audio system 200 may include multiple different modules for performing each type of audio processing, including modules 210, 220, 230, or 240. Each module may reside in an independent electronic control unit and have different functionalities, such as infotainment for module 210, an acoustic vehicle alarm system (AVAS) for module 220, a ringtone for module 230, or an emergency call for module 240. The AVAS may also include a horn. Module 210 may be an in-vehicle infotainment (IVI) system having multiple components dedicated to its operation, such as a microphone, a system-on-a-chip (SOC), an automotive audio bus (A2B) transceiver, digital signal processing (DSP) functionality, flash memory (e.g., a non-volatile memory device), a CAN transceiver (i.e., a controller area network (CAN bus)), a microcontroller unit, a digital signal processing block, an amplifier (amp), or a speaker. Module 220 may be an AVAS module having multiple components dedicated to its operation, such as a CAN transceiver, microcontroller unit, amplifier, or speaker. Module 230 may be a ringtone module using Ethernet and having multiple components dedicated to its operation, such as a system-on-chip, digital-to-analog converter (DAC), or amplifier. Module 240 may be a telematics control module using Ethernet and having multiple components dedicated to its operation, such as a system-on-chip, A2B, microphone, encoder / decoder (CODEC), amplifier, or speaker. The system 200, as disclosed in this invention, having various modules, may include multiple modules and components, and therefore may include multiple points of failure.

[0028] Figure 3 An example schematic block diagram of an audio system 400 is shown. For example... Figure 3 As shown, it can be Figure 2 Integrating some of these modules can reduce the number of components, reduce points of failure, or lower costs, etc. The regional architecture disclosed herein can integrate components and is therefore adaptable to the design of system 400, in which system 400 can be equipped with the ability to use (e.g.) Figures 1A to 1C The ECU 10 (as shown) is used to operate one or more functions (e.g., Figure 1C(Function 1 or Function 2). System 400 may include microphone 402, module 410 (or audio input block 410), module 420, or audio output block 430. Module 410 may include components associated with the audio input. Module 420 may include an MCU 421, flash memory block 422, DSP block 423, amplifier block 424, or AVAS amplifier block 425 communicatively connected to each other. MCU 421 may be connected to one or more blocks of module 420. DSP block 423 may process various signals associated with audio functions such as AVAS, ringing, emergency calls, or infotainment. In DSP block 423, a usable security layer exists (e.g., by using CRC). Flash memory block 422 may be a memory storage device for different audio functions such as AVAS, ringing, or infotainment. Flash memory block 422 may be logically separated from different audio functions, may be a physically different flash memory for each audio function, or may be an option with independent flash addresses. For each audio function, there may be one or more amplifiers, such as amplifier block 424 or AVAS amplifier block 425.

[0029] Figure 4 An example schematic block diagram of an audio system 450 is shown. System 450 may be similar to system 400, but may focus on different areas of module 420. As shown, module 420 may be connected to audio input block 410, vehicle network 415, audio output block 430, or audio feedback block 435. Audio input block 410 may include input from microphone 402. Vehicle network 415 may include CAN, Ethernet, or other networks. Audio feedback block 435 may be associated with canceling speaker feedback.

[0030] Continue to refer to Figure 4 As shown in the figure, module 420 may have a layered architecture for audio functions. The bootloader layer 441 and application layer 442 may be base layers that can be shared by all or some of the functions in the audio functions. As disclosed herein, DSP block 423 may be used to process signals associated with different audio functions, which may be processed simultaneously and may share different audio inputs 410, audio outputs 430, or vehicle network 415 (e.g., CAN transceiver). Audio functions such as AVAS, ringtones, or infotainment may have different functional blocks (e.g., partitioned) in DSP block 423 and may be configured to play using different channels.

[0031] Figure 5An example schematic block diagram illustrating the audio system flow based on the audio system architecture described in this paper is provided. In one example, the volume passed to IVI 405 may change. IVI 405 can send a message indicating the volume change via vehicle network 415 (e.g., CAN transceiver). MCU 421 can receive the message indicating the volume change and send it to DSP block 423. Firmware block 426 of DSP block 423 can determine the information to be sent to DSP signal chain 427, such as the appropriate audio file executable by the flash drive to obtain from flash memory 422 and the appropriate functions (e.g., control values) that may come from the CAN manager. DSP signal chain 427 can be the location of signal flow. DSP signal chain 427 can assist in weaving audio.

[0032] Continue to refer to Figure 5 The DSP signal chain block 427 processes values ​​received from the flash memory 422 and the CAN manager, and based on these received values, sends audio output with appropriate channels (e.g., 24 channels) to the audio processing block 429. Audio output can be fed back at the audio processing block 429 to eliminate acoustic feedback. The audio processing block 429 can send the audio output to a power amplifier (e.g., 4-16 channels each). Figure 5 System 460 may be similar to system 400 or system 450, but may focus on different areas of module 420.

[0033] Figure 6An exemplary method 380 associated with an audio system is illustrated. At step 381, a first message associated with audio manipulation (e.g., an audio control message) may be received. The audio may be associated with AVAS, ringtones, security, infotainment, etc. Audio manipulation may include adjustments to volume, adjustments to audio type, instructions to direct audio to different speakers (e.g., surround sound), etc. At step 382, ​​based on the first message, audio-related information to be sent (e.g., control information or data information) is determined. In one example, the audio-related information may include CAN-related control messages (e.g., control values) or audio files (e.g., .wav or Pulse Code Modulation (PCM)). The audio-related information may be sent to DSP signal chain 427. At step 383, based on the audio-related information, an audio output for audio processing block 429 is generated. At step 384, the audio output is processed by audio processing block 429. At step 385, the audio output processed by audio processing block 429 is transmitted. The audio output may be transmitted to an audio amplifier or a speaker. The audio output may be transmitted in conjunction with a haptic queue. Tactile queues in vehicles can include physical feedback that alerts occupants through touch-based sensations. Tactile queues can convey information via mechanical signals detectable by human touch. Examples of tactile queues include vibration patterns via the steering wheel, pulsating movements of the driver's or passenger's seat, tactile feedback from control surfaces or touchscreens, oscillating motions via pedals, rhythmic vibrations via seatbelts, or localized vibrating elements in armrests or other interior contact points. Tactile queues work in conjunction with audio alarms and visual warnings to form a comprehensive notification system. For example, safety warnings can be triggered by synchronized feedback via steering wheel vibrations, audible rings, and dashboard display indicators. Tactile queues can convey different types of information by varying the intensity, duration, pattern, or location of vibrations within the cabin. Tactile queues can provide additional sensory channels for communicating vehicle status, warnings, or other information to occupants.

[0034] The method disclosed in this invention can meet the Automotive Safety Integrity Level (ASIL), which may require combining alarms including visual, auditory, or tactile queues, with fewer components than some other audio configurations. Furthermore, safety-critical audio streams (e.g., ringtones) and non-safety-critical audio streams (e.g., in-vehicle infotainment) can be appropriately prioritized and directed to different audio outputs (e.g., rear speakers, center speakers, left speakers, right speakers, etc.).

[0035] The blocks disclosed in this invention can be further subdivided and are operable to perform different functions supported by a particular ECU. For example, a CAN transceiver may have multiple CAN operations, which may include platform CAN, front-of-vehicle CAN, or interface CAN (e.g., interface CAN may be connected to a vehicle interface module).

[0036] The methods, systems, or apparatuses disclosed herein may be incorporated into electric vehicles or other equipment. The circuit blocks disclosed herein may be distributed or combined with one or more ECUs or other devices. The methods, systems, or apparatuses disclosed herein may be incorporated into products such as various feature-specific or region-specific electronic control units (ECUs).

[0037] This document discloses methods, systems, and apparatuses for processing vehicle audio functions. An apparatus may include a microcontroller unit (MCU); a non-volatile storage device communicatively coupled to the MCU, wherein the non-volatile storage device may include multiple audio files associated with audio for various types of audio functions of the vehicle; and a digital signal processing (DSP) module communicatively coupled to the MCU, wherein the DSP module can process various types of audio functions associated with the vehicle. The apparatus may include an electronic control unit for an electric vehicle. The various types of audio functions may include audio associated with emergency calls, audio associated with an acoustic vehicle alarm system, audio associated with a ringtone, and audio associated with infotainment or audio associated with both emergency calls and acoustic vehicle alarm systems. The DSP module may include a firmware block; a DSP signal chain block; and an audio processing block, wherein the firmware block receives control values ​​from the microcontroller unit, and wherein the DSP signal chain block outputs audio signals through multiple channels. The various types of audio functions may be partitioned into different functional blocks within the DSP module and share a bootloader layer and an application layer. The DSP signal chain can transmit audio output based on values ​​received from non-volatile memory and the controller LAN manager. All combinations in this paragraph and those preceding paragraphs (including the removal or addition of steps) are conceived in a manner consistent with the other parts of the detailed description.

[0038] This document discloses methods, systems, and apparatuses for processing audio in a vehicle. A system may include a microcontroller unit; a digital signal processing (DSP) block communicatively coupled to the microcontroller unit; a flash memory block communicatively coupled to the DSP block, wherein the flash memory block may include multiple partitions for storing different types of audio function data; and multiple amplifiers communicatively coupled to the DSP block, wherein the DSP block processes audio signals based on different types of audio function data to output them concurrently through the multiple amplifiers. The different types of audio function data may include audio data for emergency calls; audio data for an acoustic vehicle alarm system (AVAS); audio data for a ringtone; or audio data for infotainment. The DSP block may include a firmware block; a DSP signal chain block; and an audio processing block, wherein the firmware block receives control values ​​from the microcontroller unit, and the DSP signal chain block outputs audio signals through multiple channels. The system may also include an audio input block communicatively coupled to the DSP block, wherein the audio input block may include a microphone. The system may include a bootloader layer and an application layer. All combinations in this paragraph and the paragraphs above (including the removal or addition of steps) are conceived in a manner consistent with the other parts of the detailed description.

[0039] A method may include receiving an audio control message at a microcontroller unit; retrieving audio data from a flash memory device based on the audio control message; processing the retrieved audio data via a digital signal processing (DSP) block; generating a multi-channel audio output signal based on the processed audio data; and routing the multi-channel audio output signal to multiple amplifiers for concurrent output. The audio data may correspond to audio of an emergency call, audio of an acoustic vehicle alarm system (AVAS), audio of a ringtone, or audio of infotainment. The method includes receiving audio input via a microphone and processing the audio input via the DSP block. Processing the retrieved audio data may include determining a control value based on the audio control message; configuring a DSP signal chain based on the control value; and generating a multi-channel audio output signal via the configured DSP signal chain. The method provides feedback cancellation for the multi-channel audio output signal, and routing the multi-channel audio output signal may include directing different types of audio to different amplifiers. All combinations in this paragraph and the preceding paragraphs (including the removal or addition of steps) are conceived in a manner consistent with the other parts of the detailed description.

[0040] A method, system, or apparatus for processing audio in a vehicle may receive an audio message; determine audio information to be retrieved based on the audio message; retrieve the determined audio information from a partitioned storage device; process the retrieved audio information via a digital signal processor (DSP); and output the processed audio signal via multiple amplifiers. The audio information may include audio data of an emergency call, audio data of an acoustic vehicle alarm system (AVAS), audio data of a bell, or audio data of infotainment. The operation may also include receiving audio input via a microphone and processing the received audio input via the DSP. Processing the retrieved audio information may include determining control values ​​based on the audio message; configuring a DSP signal chain based on the control values; and generating a processed audio signal via the configured DSP signal chain. The operation may also include providing feedback cancellation for the processed audio signal, and outputting the processed audio signal may include directing different types of audio to different amplifiers. All combinations in this paragraph and the preceding paragraphs (including the removal or addition of steps) are conceived in a manner consistent with the other parts of the detailed description.

[0041] As used herein, the phrase “at least one of” following a series of items, along with the terms “and” or “or” used to separate any items, modifies the entire list, not each member of the list (i.e., each item). The phrase “at least one of” does not require selection of at least one of each of the listed items; rather, it allows for the inclusion of meanings such as: at least one of any of these items, and / or at least one of any combination of these items, and / or at least one of each of these items. By way of example, the phrases “at least one of A, B, and C” or “at least one of A, B, or C” respectively refer to only A, only B, or only C; any combination of A, B, and C; and / or at least one of each of A, B, and C.

[0042] When a component is referred to herein as “connected” or “coupled” to another component, it should be understood that the component may be directly connected to that other component, or that there may be intermediate components between these components. Conversely, when a component is referred to herein as “directly connected” or “directly coupled” to another component, it should be understood that there are no intermediate components in the “direct” connection between these components. However, the presence of a direct connection does not preclude the possibility of other connections with intermediate components.

[0043] The predicates “constructed as,” “operable to,” and “programmed to” do not imply any particular tangible or intangible modification of the subject matter, but are intended to be used interchangeably. In one or more embodiments, a processor constructed to monitor and control operations or components may also mean that the processor is programmed to monitor and control operations or that the processor is operable to monitor and control operations. Similarly, a processor constructed to execute code can be interpreted as a processor programmed to execute code or operable to execute code.

[0044] Phrases such as "aspect," "that aspect," "on the other hand," "some aspects," "one or more aspects," "one embodiment," "that embodiment," "another embodiment," "some embodiments," "one or more embodiments," "an implementation scheme," "that implementation scheme," "another implementation scheme," "some implementation schemes," "one or more implementation schemes," "a construction," "that construction," "another construction," "some constructions," "one or more constructions," "the subject matter," "the disclosure," "this disclosure," and other variations thereof are for convenience and do not imply that the disclosure associated with such phrases is necessary for the subject matter or that such disclosure applies to all constructions of the subject matter. The disclosure associated with such phrases may apply to all constructions or one or more constructions. One or more examples of the disclosure associated with such phrases may be provided. Phrases such as "aspect" or "some aspects" may refer to one or more aspects, and vice versa, and this similarly applies to other foregoing phrases.

[0045] The various techniques described herein can be implemented using hardware, firmware, software, or, where appropriate, combinations thereof. Such hardware, firmware, and software can reside in devices located at various nodes of a communication network. These devices can operate individually or in combination with each other to implement the methods described herein. Furthermore, unless otherwise stated herein, the use of the word "or" is generally inclusive. The methods described herein can be implemented locally or remotely, or in a combination of local and remote systems, and are configured to perform functions that can be implemented using software, hardware, or combinations thereof in the aforementioned environments.

[0046] The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” or “example” is not necessarily to be construed as preferred or advantageous over other embodiments. Furthermore, with regard to the use of terms such as “comprising,” “having,” etc., in the specification or claims, such terms are intended to be inclusive in a manner similar to the term “including,” as interpreted when “including” is used as a transitional word in the claims.

[0047] All structural and functional equivalents of elements of the various aspects described throughout this disclosure that are known to or will later become known to a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to serve the public, whether or not such disclosure is expressly stated in the claims. No claim element should be construed under paragraph 6 of 35 U.S.SC § 112 unless the element is expressly stated using the phrase “means for…” or, in the case of a method claim, using the phrase “step for…”.

[0048] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein elements referred to in the singular are not intended to mean “one and only one,” but rather “one or more” unless specifically stated otherwise. Unless otherwise specifically stated, the term “some” refers to one or more. Male pronouns (e.g., his) include female and neutral pronouns (e.g., her and its), and vice versa. Titles and subheadings (if any) are used for convenience only and do not limit this disclosure.

Claims

1. An apparatus comprising: a microcontroller unit (MCU); a non-volatile storage device communicatively coupled with the MCU, wherein the non-volatile storage device comprises a plurality of audio files associated with a plurality of types of audio functions of a vehicle; and a digital signal processing (DSP) module communicatively coupled with the MCU, wherein the DSP module processes the plurality of types of audio functions associated with the vehicle.

2. The apparatus of claim 1, wherein the apparatus comprises an electronic control unit of an electric vehicle.

3. The apparatus of claim 1, wherein, the DSP module comprises: a firmware block; a DSP signal chain block; and an audio processing block.

4. The apparatus of claim 3, wherein, the firmware block receives control values from the microcontroller unit.

5. The apparatus of claim 3, wherein, the DSP signal chain block outputs audio signals through a plurality of channels.

6. The apparatus of claim 1, wherein, the plurality of types of audio functions are partitioned into different functional blocks in the DSP module.

7. The apparatus of claim 1, wherein, the plurality of types of audio functions share a bootloader layer and an application layer.

8. The apparatus of claim 1, wherein, the DSP signal chain block sends audio outputs based on values received from the non-volatile storage device and a controller area network manager.

9. The apparatus of claim 1, wherein, the plurality of types of audio functions comprises audio associated with emergency calls, audio associated with acoustic vehicle alerting systems, audio associated with chimes, and audio associated with infotainment.

10. The apparatus of claim 1, wherein, the plurality of types of audio functions comprises audio associated with emergency calls and audio associated with acoustic vehicle alerting systems.

11. A method comprising: receiving an audio-related message; determining audio-related information for processing based on the audio-related message; generating an audio output based on the audio-related information; processing the generated audio output; and transmitting the processed audio output. the audio-related information comprises audio files associated with one or more types of audio functions or controller area network related control messages associated with the one or more types of audio functions.

12. The method of claim 11, wherein, the one or more types of audio functions comprises audio of emergency calls, audio of acoustic vehicle alerting systems, audio of chimes, and audio of infotainment.

13. The method of claim 12, wherein, the audio-related information comprises an indication to adjust a volume, an indication to adjust an audio type, or an indication to direct audio to different speakers.

14. The method of claim 11, wherein, 15. An electric vehicle comprising: a processor; and a memory coupled with the processor, the memory comprising executable instructions that, when executed by the processor, cause the processor to implement operations comprising: receiving an audio message; determining audio information to retrieve based on the audio message; retrieving the audio information from a partitioned storage device; processing the audio information through a digital signal processor (DSP); and outputting processed audio information through a plurality of amplifiers. processing the audio information comprises:

16. The electric vehicle of claim 15, wherein, determining control values based on the audio message; configuring a DSP signal chain based on the control values; and generating the processed audio information through the configured DSP signal chain. the audio information comprises:

17. The electric vehicle of claim 15, wherein, audio data of emergency calls; ​ Audio data for an acoustic vehicle alerting system; Audio data for a chime; or Audio data for infotainment.

18. The electric vehicle of claim 15, wherein, The operations further include: receiving audio input through at least one microphone; and processing the received audio input through the DSP.

19. The electric vehicle of claim 15, wherein, The operations further include providing feedback cancellation for the processed audio information.

20. The electric vehicle of claim 15, wherein, Outputting the processed audio information includes directing different types of audio to different amplifiers.

Images