Audio request execution method and device and vehicle terminal
Through the sorting and priority management of the audio request queue, the problem of confusing audio request execution logic in the vehicle terminal is solved, the accuracy and user experience of audio playback are improved, the processing process is simplified, and the system performance is improved.
Patent Information
- Application Number
- CN202411129231.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-11-12
AI Technical Summary
There is confusion in the execution logic of audio requests in the vehicle terminal, resulting in limited audio playback accuracy and user experience. Especially when multiple audio requests are concurrent, the prior art is difficult to process the status of each request instantly, and the amount of communication data is increased. and processing complexity.
Sorting and prioritizing management through the audio request queue, determining the execution timing of requests based on preset priorities, ensuring that important or urgent requests are prioritized, avoiding feedback on execution results or adding request identifiers, and optimizing the audio request processing process.
Improves the accuracy and user experience of audio playback, ensures that important requests or emergency requests are processed in a timely manner, simplifies processing processes, and improves system performance and response speed.
Smart Images

Figure CN118939229A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of vehicle audio playback, and in particular to an audio request execution method, device and vehicle terminal. Background Art
[0002] In the continuous evolution of modern automobile design, with the leap-forward improvement of automobile electronics and intelligence, the automobile instrument system has completely transformed, no longer limited to the traditional simple information display function, but transformed into a comprehensive information center integrating information display, human-computer interaction, driving assistance and entertainment control functions. The core driving force of this transformation lies in the efficient data interaction mechanism established between the instrument ECU (Microcontroller Unit) and the cockpit SOC (System on Chip), which ensures the real-time display of various vehicle status information, and greatly enhances the convenience and safety of driving by integrating advanced functions such as map navigation projection and driving assistance system feedback.
[0003] However, with the increasing complexity of vehicle functions, more stringent requirements are placed on the real-time and accuracy of information display and feedback. The importance of the audio feedback mechanism, as a key link to improve user experience, is self-evident. It must not only be able to quickly and accurately convey key information such as vehicle status changes and warning prompts, but also must achieve clear distinction and orderly processing when multiple audio requests are concurrent to prevent information confusion or omission. Unfortunately, when the instrument ECU sends multiple audio requests in a short period of time, the serial processing mode of the audio execution module and the time delay of its subsequent feedback make it difficult for the instrument ECU to instantly grasp the exact execution status of each audio request, which may cause the problem that the audio request cannot be effectively executed. In addition, although the recognition accuracy of the request can be improved to a certain extent by adding identifiers or timestamps to the audio request and its execution results, this approach also brings about the side effects of a sharp increase in the amount of communication data and an increase in processing complexity, which may ultimately drag down the overall performance and response speed of the system.
[0004] In summary, the lag problem when the cockpit SOC and the instrument ECU transmit audio information in the vehicle terminal leads to confusion in the execution logic of audio requests in some cases, which has become a bottleneck for audio playback accuracy and user experience. Summary of the invention
[0005] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.
[0006] In view of the above-mentioned shortcomings of the prior art, the present application discloses an audio request execution method, device and vehicle terminal to optimize the processing flow of audio requests, thereby improving the accuracy of audio playback.
[0007] The present application discloses an audio request execution method, comprising: obtaining an original audio request; storing the original audio request through an audio request queue, and sorting the original audio request according to a preset priority, wherein the original audio request includes a first request and a second request; executing the original audio request according to the audio request queue, wherein if the second request is executed when the first request is executed, determining the execution sequence of the first request and the second request according to the preset priority, so as to execute the first request and / or the second request according to the execution sequence.
[0008] In one embodiment of the present application, the original audio request is executed according to the audio request queue, including: taking the first original audio request in the audio request queue as the target request; in response to the target request, obtaining the audio playback duration corresponding to the target request; executing the target request, and counting the request execution duration corresponding to the target request; in response to the request execution duration being greater than or equal to the audio playback duration, taking the first original audio request in the audio queue as the new target request.
[0009] In one embodiment of the present application, in response to the request execution time being greater than or equal to the audio playback time, the first original audio request in the audio request team is used as a new target request, including: if a new original audio request is stored in the audio request queue, the first original audio request in the audio request team is used as the request to be compared; if the preset priority of the target request is higher than the preset priority of the request to be compared, then in response to the request execution time being greater than or equal to the audio playback time, the first original audio request in the audio request team is used as a new target request; if the preset priority of the target request is lower than or equal to the preset priority of the request to be compared, the request to be compared is used as the new target request.
[0010] In one embodiment of the present application, the execution timing of the first request and the second request is determined according to the preset priority, including at least one of the following: if the preset priority of the first request is higher than the preset priority of the second request, the first request and the second request are executed in sequence; if the preset priority of the first request is equal to the preset priority of the second request, the first request and the second request are executed according to the first timing or the second timing, wherein the first timing includes executing the first request and the second request in sequence, and the second timing includes playing the first request and the second request simultaneously; if the preset priority of the first request is lower than the preset priority of the second request, the second request and the first request are executed in sequence.
[0011] In one embodiment of the present application, the second request and the first request are executed in sequence, including: obtaining the playback interruption strategy corresponding to the first request, and controlling the request execution phase corresponding to the first request to enter the suspension phase or the stop phase according to the playback interruption strategy; controlling the request execution phase corresponding to the second request to be in the playback phase to play the audio file corresponding to the second request; if the request execution phase corresponding to the second request is in the stop phase, and the request execution phase corresponding to the first request is in the suspension phase, then controlling the request execution phase corresponding to the first request to enter the playback phase.
[0012] The present application discloses an audio request execution device, comprising: a first processor, connected to a second processor, the first processor being used to obtain an original audio request; storing the original audio request through an audio request queue, and sorting the original audio request according to a preset priority; sending the original audio request to the second processor according to the audio request queue, wherein the original audio request includes a first request and a second request; the second processor being used to receive the original audio request sent by the first processor and execute the original audio request, wherein if the second request is executed when the first request is executed, the execution timing of the first request and the second request is determined according to the preset priority, so as to execute the first request and / or the second request according to the execution timing.
[0013] In one embodiment of the present application, the audio request execution device is applied to a vehicle terminal, and the first processor includes an instrument MCU, which is further used to: collect instrument audio requests and use the collected instrument audio requests as original audio requests.
[0014] In one embodiment of the present application, the second processor includes a cockpit SOC, and the cockpit SOC is also used to: obtain the unit priorities corresponding to the vehicle ECU and the instrument MCU respectively, wherein the vehicle ECU is also used to send the ECU audio request to the cockpit SOC; determine the request to be executed from the original audio request and the ECU audio request, wherein the original audio request in the request to be executed is used as the third request, and the ECU audio request in the request to be executed is used as the fourth request; if the request to be executed includes both the third request and the fourth request, then the unit priority corresponding to the fourth request is compared according to the unit priority corresponding to the third request to obtain a priority comparison result, and the execution order of the third request and the fourth request is determined according to the priority comparison result.
[0015] In one embodiment of the present application, the first processor and the second processor are connected via SPI to implement data transmission via SPI.
[0016] The present application discloses a vehicle terminal, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the vehicle terminal executes the above method.
[0017] Beneficial effects of this application:
[0018] The original audio requests in the audio request queue are sorted according to the preset priority, and the original audio requests are executed according to the audio request queue. At the same time, if the second request is executed when the first request is executed, the execution timing of the first request and the second request is determined according to the preset priority. In this way, not only are the original audio requests executed in order according to the preset priority, but also the execution timing is determined according to the preset priority when executing multiple original audio requests. Multiple processing logics for executing audio requests according to priority are set, and there is no need for the audio request to feedback the execution result or add a request identifier after execution. The processing flow of the audio request is optimized. In particular, when processing multiple audio requests, it can ensure that important requests or urgent requests are given priority according to the preset priority, thereby improving the accuracy of audio playback and enhancing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 is a flowchart of an audio request execution method in an embodiment of the present invention;
[0020] Figure 2 is a schematic diagram of a method for executing a second request and a first request in an embodiment of the present application;
[0021] Figure 3 is a structural diagram of an audio request execution device in an embodiment of the present application;
[0022] Figure 4 is a schematic diagram of the structure of a vehicle terminal in an embodiment of the present application;
[0023] Figure 5 It is a flowchart of an audio request execution method for a vehicle terminal in an embodiment of the present application;
[0024] Figure 6 It is a schematic diagram of the structure of another vehicle terminal in an embodiment of the present invention. DETAILED DESCRIPTION
[0025] The following describes the embodiments of the present invention through specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and sub-samples in the embodiments can be combined with each other without conflict.
[0026] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.
[0027] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.
[0028] The terms "first", "second", etc. in the specification and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.
[0029] Unless otherwise stated, the term "plurality" means two or more.
[0030] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.
[0031] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.
[0032] Combination Figure 1 As shown, the embodiment of the present disclosure provides an audio request execution method, including:
[0033] Step S101, obtaining an original audio request;
[0034] Step S102, storing the original audio requests in an audio request queue, and sorting the original audio requests according to a preset priority;
[0035] The original audio request includes a first request and a second request;
[0036] Step S103, executing the original audio request according to the audio request queue;
[0037] Step S104, if the second request is executed when the first request is executed, determining the execution sequence of the first request and the second request according to the preset priority, so as to execute the first request and / or the second request according to the execution sequence.
[0038] The audio request execution method provided by the embodiment of the present disclosure is adopted, by sorting the original audio requests in the audio request queue according to the preset priority, executing the original audio requests according to the audio request queue, and at the same time, if the second request is executed when the first request is executed, the execution timing of the first request and the second request is determined according to the preset priority. In this way, not only the original audio requests are executed in order according to the preset priority, but also the execution timing is determined according to the preset priority when executing multiple original audio requests, and multiple processing logics are set to execute audio requests according to the priority. There is no need for the audio request to feedback the execution result or add a request identifier after execution, and the processing flow of the audio request is optimized. In particular, when processing multiple audio requests, it can ensure that important requests or urgent requests are given priority according to the preset priority, thereby improving the accuracy of audio playback and enhancing the user experience.
[0039] Optionally, executing the original audio request according to the audio request queue includes: taking the first original audio request in the audio request queue as the target request; in response to the target request, obtaining the audio playback duration corresponding to the target request; executing the target request, and counting the request execution duration corresponding to the target request; in response to the request execution duration being greater than or equal to the audio playback duration, taking the first original audio request in the audio queue as the new target request.
[0040] In some embodiments, if there are multiple original audio requests in the audio request queue, the audio playback duration corresponding to each original audio request is obtained; after the target request is sent to the audio execution module, the request sending duration of the target request is counted; if the request sending duration is greater than or equal to the request playback duration, it means that the currently sent target request has been executed, and the next original audio request is sent to the audio execution module as a new target request.
[0041] In some embodiments, during driving, the vehicle navigation system simultaneously receives multiple audio requests, including regular traffic reports, music playback requests, and an emergency turn prompt. These requests are added to the audio request queue in the order of receipt, but the emergency turn prompt needs to be played first; the request playback durations corresponding to the traffic report, music playback, and emergency turn prompt are obtained, wherein the request playback duration corresponding to the traffic report is 3s (seconds), the request playback duration corresponding to the music playback is 5s, and the request playback duration of the emergency turn prompt is 2s; according to the preset priority (emergency prompt>traffic report>music playback), the audio request queue is reordered into emergency turn prompt, regular traffic report, and music playback request; the emergency turn prompt is sent as a target request to the audio execution module, and the request sending duration is counted; when the request sending duration of the emergency turn prompt reaches 2 seconds, the audio acquisition module sends the next request (regular traffic report) as a new target request to the audio execution module; the remaining audio requests are processed according to the same process to ensure that each request is processed according to the preset priority.
[0042] In some embodiments, the first audio request collected is a thermal runaway fault with priority 1, which will be placed in the first position of the queue; the second audio request collected is an overspeed reminder sound with priority 10, which will be placed in the second position of the queue according to the priority; the third audio request collected is a gear shift reminder sound with priority 6, and the gear shift reminder sound is inserted in the second position, and the overspeed reminder sound originally in the second position will be arranged in the third position; then according to the playback time and valid status, the audio source ID number, channel number, action instruction code, playback interval time, and playback count data are sent to the SOC middleware in sequence. Because the final vehicle actually requires a sound playback strategy, the instrument sound request has different channel numbers, and multiple simultaneously valid audio source requests will be interrupted and mixed according to the channel number for the whole vehicle sound.
[0043] Optionally, in response to the request execution time being greater than or equal to the audio playback time, the first original audio request in the audio request queue is taken as the new target request, including: if a new original audio request is stored in the audio request queue, the first original audio request in the audio request queue is taken as the request to be compared; if the preset priority of the target request is higher than the preset priority of the request to be compared, then in response to the request execution time being greater than or equal to the audio playback time, the first original audio request in the audio request queue is taken as the new target request; if the preset priority of the target request is lower than or equal to the preset priority of the request to be compared, the request to be compared is taken as the new target request.
[0044] In some embodiments, the first audio request collected is a speeding reminder sound with a priority of 10, and the speeding reminder sound is placed first in the queue; the audio acquisition module sends the speeding reminder sound to the audio execution module; when the request sending duration of the speeding reminder sound does not meet the requested playback duration, the second audio request collected is a gear shift reminder sound with a priority of 6, and the gear shift reminder sound is placed first in the queue according to the priority; since the priority of the gear shift reminder sound is higher than the priority of the speeding reminder sound, the gear shift reminder sound is immediately sent to the audio execution module when the request sending duration of the speeding reminder sound does not meet the requested playback duration, to ensure that important requests or urgent requests are given priority.
[0045] Optionally, the execution sequence of the first request and the second request is determined according to a preset priority, including at least one of the following: if the preset priority of the first request is higher than the preset priority of the second request, the first request and the second request are executed in sequence; if the preset priority of the first request is equal to the preset priority of the second request, the first request and the second request are executed according to the first timing or the second timing, wherein the first timing includes executing the first request and the second request in sequence, and the second timing includes playing the first request and the second request simultaneously; if the preset priority of the first request is lower than the preset priority of the second request, the second request and the first request are executed in sequence.
[0046] In some embodiments, the first request and the second request are arbitrary original audio requests; during the execution of an original audio request, if a new original audio request is received, it is necessary to compare the executing original audio request and the new original audio request according to priority, and give priority to the audio request with a higher priority.
[0047] In some embodiments, if the preset priority of the first request is equal to the preset priority of the second request, the first request and the second request are provided with operations such as play, stop, and mix on the audio source and audio channel according to the preset processing strategies of the first request and the second request, thereby achieving sequential or simultaneous execution.
[0048] In some embodiments, if the preset priority of the first request is lower than the preset priority of the second request, the execution of the first request is interrupted, the second request is executed first, and then it is determined whether to continue to execute the first request according to the preset processing strategy of the first request.
[0049] Optionally, the audio execution module executes the second request and the first request in sequence in the following manner: obtaining the playback interruption strategy corresponding to the first request; controlling the request execution phase corresponding to the first request to enter the suspension phase or the stop phase according to the playback interruption strategy corresponding to the first request; controlling the request execution phase corresponding to the second request to be in the playback phase to play the audio file corresponding to the second request; if the request execution phase corresponding to the second request is in the stop phase, and the request execution phase corresponding to the first request is in the suspension phase, then controlling the request execution phase corresponding to the first request to enter the playback phase to play the audio file corresponding to the first request.
[0050] In some embodiments, the request execution phase includes an initialization phase (Init), a start phase (Start), a play phase (Playing), a pending phase (Pending) and a stop phase (Stop); the initialization phase includes that before the audio playback starts, the system needs to perform a series of preparations to ensure that the audio can be played smoothly, such as registering components, opening devices and allocating resources; the start phase includes that after the initialization is completed, the system enters the start phase and prepares to load the audio file and start playing, such as loading the audio file, decoding preparation and buffering processing; the play phase includes that after the audio file is loaded and the decoding preparation is completed, the system enters the play phase and starts playing the audio, such as decoding audio data, audio output and synchronization control; the pending phase includes that during the playback process, the user may request to pause the playback, at which time the system enters the pending phase and immediately stops the output of the audio data, but retains the current playback position and status information. The system usually keeps occupying resources such as audio files and decoders so that the user can resume playback at any time; the stop phase includes that when the audio finishes playing, the system enters the stop phase, completely stops the output of the audio data, and releases all resources related to audio playback.
[0051] Combination Figure 2As shown, an embodiment of the present disclosure provides a method for executing a second request and a first request, including: obtaining a first request and a second request, wherein the priority of the first request is lower than the priority of the second request; initializing the first request and the second request at the same time; if the first request has completed initialization, executing the first request, and the first request sequentially enters a start phase and a play phase; while playing the first request, if the second request has completed initialization, executing the second request, and the second request sequentially enters a start phase and a play phase, and when the second request enters the play phase, the first request enters a suspend phase; after the second request enters the stop phase, re-executing the first request, and the first request sequentially enters a start phase and a play phase until the first request is executed and enters the stop phase.
[0052] Optionally, the second request and the first request are executed in sequence, including: obtaining the playback interruption strategy corresponding to the first request, and controlling the request execution phase corresponding to the first request to enter the suspension phase or the stop phase according to the playback interruption strategy; controlling the request execution phase corresponding to the second request to be in the playback phase to play the audio file corresponding to the second request; if the request execution phase corresponding to the second request is in the stop phase, and the request execution phase corresponding to the first request is in the suspension phase, then controlling the request execution phase corresponding to the first request to enter the playback phase.
[0053] Combination Figure 3 As shown, an embodiment of the present disclosure provides an audio request execution device, including a first processor 301 and a second processor 302 .
[0054] The first processor 301 is connected to the second processor 302, and the first processor is used to obtain an original audio request; store the original audio request through an audio request queue, and sort the original audio request according to a preset priority; send the original audio request to the second processor according to the audio request queue, wherein the original audio request includes a first request and a second request.
[0055] The second processor 302 is used to receive the original audio request sent by the first processor and execute the original audio request. If the second request is executed when the first request is executed, the execution timing of the first request and the second request is determined according to a preset priority so as to execute the first request and / or the second request according to the execution timing.
[0056] The audio request execution device provided by the embodiment of the present disclosure is adopted, and the original audio requests in the audio request queue are sorted according to the preset priority, and the original audio requests are executed according to the audio request queue. At the same time, if the second request is executed when the first request is executed, the execution timing of the first request and the second request is determined according to the preset priority. In this way, not only the original audio requests are executed in order according to the preset priority, but also the execution timing is determined according to the preset priority when executing multiple original audio requests, and multiple processing logics for executing audio requests according to the priority are set, and there is no need for the audio request to feedback the execution result or add a request identifier after execution, so the processing flow of the audio request is optimized. In particular, when processing multiple audio requests, it can ensure that important requests or urgent requests are given priority according to the preset priority, thereby improving the accuracy of audio playback and enhancing the user experience.
[0057] Optionally, the audio request execution device is applied to a vehicle terminal.
[0058] Combination Figure 4 As shown, an embodiment of the present disclosure provides a vehicle terminal, including a first processor and a second processor, wherein the first processor includes an instrument MCU and the second processor includes a cockpit SOC.
[0059] In some embodiments, the instrument MCU is provided with a Chime module (audio acquisition module), wherein the audio acquisition module is used to collect the instrument audio requests corresponding to the instrument MCU, and use the instrument audio requests as original audio requests; store the acquired original audio requests through the audio request queue, and sort the original audio requests in the audio request queue according to the preset priority of each original audio request; pop out the original audio requests from the audio request queue in sequence, and send the popped-up original audio requests to the audio execution module.
[0060] Optionally, the instrument MCU is further used to collect instrument audio requests and use the collected instrument audio requests as original audio requests.
[0061] In some embodiments, the instrument MCU collects the instrument audio request in the following manner: obtaining the handshake status between the audio acquisition module and the middleware; if the handshake status is a successful handshake, collecting the instrument audio request corresponding to the instrument MCU, wherein the instrument audio request includes at least one of a pop-up audio request, an indicator light audio request, a CAN signal audio request, and an intelligent driving audio request.
[0062] In some embodiments, the audio acquisition module determines whether the handshake with the middleware is successful through the SPI protocol; if the handshake is successful, the instrument indicator light, instrument pop-up window, instrument CAN (Controller Area Network) signal and ADAS (Advanced Driver Assistance Systems) input information are traversed to collect the instrument audio requests therein; after each instrument audio request is collected, the collected instrument audio requests are arbitrated according to a preset priority to form an audio request queue according to the instrument audio requests sorted according to the preset priority; the instrument audio requests in the audio request queue are sent to the middleware in sequence through the SPI protocol.
[0063] In some embodiments, when the vehicle is started, the audio acquisition module attempts to establish a communication connection with the middleware through the SPI protocol. The handshake process includes sending a specific handshake signal and waiting for the response of the middleware. If a correct response is received from the middleware within a preset time, the handshake is judged to be successful and the next step is entered. Otherwise, the handshake is retried or an error is reported. After the handshake is successful, the audio acquisition module begins to traverse the data sources such as the dashboard, ADAS system, and CAN bus to collect audio requests, wherein audio requests related to instrument indicator lights (such as seat belt unfastened warnings) are collected from the dashboard, text-to-speech conversion requests (such as navigation instructions) in the instrument pop-up window are collected, emergency warning audio requests (such as collision warnings) are obtained from the ADAS system, and signals on the CAN bus are monitored and requests related to audio playback (such as speed limit reminders) are extracted. For each collected audio request, the audio acquisition module will arbitrate according to a preset priority rule. The priority rule is based on factors such as the urgency of the request, the importance of the source system, and user settings. For example, the emergency warning of the ADAS system usually has the highest priority, followed by safety-related requests from the dashboard, and finally the playback request of the entertainment system. According to the arbitration result, the audio requests are sorted from high to low according to priority to form an audio request queue. Through SPI (Serial The audio acquisition module sends the requests in the audio request queue to the middleware in sequence. During the sending process, the audio acquisition module tracks the sending status of each request to ensure that no request is missed or sent repeatedly. After receiving the request, the middleware will further process it and forward it to the audio execution module for playback.
[0064] In some embodiments, the cockpit SOC is provided with an Audio module (audio execution module), wherein the audio execution module is used to execute the received original audio request, wherein, if a second request is received when executing a first request, the execution timing of the first request and the second request is determined according to the preset priorities corresponding to the first request and the second request respectively, so as to execute the first request and the second request according to the execution timing.
[0065] Optionally, the cockpit SOC is also used to: obtain unit priorities corresponding to the vehicle ECU and the instrument MCU respectively, wherein the vehicle ECU is also used to send the ECU audio request to the cockpit SOC; determine the request to be executed from the original audio request and the ECU audio request, wherein the original audio request in the request to be executed is used as the third request, and the ECU audio request in the request to be executed is used as the fourth request; if the request to be executed includes both the third request and the fourth request, then compare the unit priority corresponding to the fourth request according to the unit priority corresponding to the third request to obtain a priority comparison result, and determine the execution order of the third request and the fourth request according to the priority comparison result.
[0066] In some embodiments, the audio execution module obtains the unit priorities corresponding to the vehicle ECU and the instrument MCU respectively from a predefined configuration or real-time query, wherein the unit priority corresponding to the instrument MCU is usually higher than the unit priority corresponding to the vehicle ECU; when the vehicle starts, the vehicle ECU, the instrument MCU and the middleware are all initialized and establish communication connections with each other; the instrument MCU collects the original audio request and sends it to the audio execution module through the middleware, for example, the emergency warning sound is sent to the audio execution module through the middleware; if the list of requests to be executed includes both the third request and the fourth request, the audio execution module will compare them according to the preset priority rules, specifically, it will compare the unit priority corresponding to the third request with the unit priority corresponding to the fourth request; since the priority of the instrument MCU is usually higher, the third request will be executed first; once the third request is executed, if there is no new request with a higher priority, the fourth request will continue to execute.
[0067] Optionally, the first processor and the second processor are connected via SPI to implement data transmission via SPI.
[0068] In some embodiments, the cockpit SOC is also provided with middleware, wherein the middleware is used to establish data communication between the instrument MCU and the cockpit SOC through the SPI protocol to receive the original audio request sent by the audio acquisition module and transmit the original audio request to the audio execution module.
[0069] In some embodiments, the middleware is further used to obtain an ECU audio request sent by the vehicle ECU, and send the ECU audio request to the audio execution module.
[0070] In some embodiments, the vehicle terminal also includes a playback module, wherein the playback module is configured to be triggered by the audio execution module and output sound through an amplifier or speaker in the cabin according to an audio file corresponding to the original audio request.
[0071] In some embodiments, the vehicle terminal also includes a fault collection module, which is used for at least one of the following: judging whether the original audio request collected by the audio acquisition module is correct according to a preset request format; judging whether the audio acquisition module sends the original audio request to the middleware through the request sending log corresponding to the audio acquisition module; judging whether the middleware receives the original audio request sent by the audio acquisition module; judging whether the middleware sends the original audio request to the audio execution module through the request sending log corresponding to the middleware; judging whether the parameters of the audio execution module when executing the original audio request are correct according to preset parameter thresholds.
[0072] In some embodiments, the fault collection module first parses and verifies the original audio request collected by the audio acquisition module according to a preset request format. If the request format is incorrect, such as missing necessary parameters or incorrect parameter format, the fault collection module will record the fault and notify the system administrator.
[0073] In some embodiments, the fault collection module checks the request sending log corresponding to the audio acquisition module, wherein if the log shows that the audio acquisition module does not send the original audio request to the middleware, or the time interval for sending the request is abnormal, the fault collection module will record the fault.
[0074] In some embodiments, the fault collection module communicates with the middleware to confirm whether the middleware successfully receives the original audio request sent by the audio acquisition module. If the middleware does not receive the request or the received request content is incomplete, the fault collection module will record the fault.
[0075] In some embodiments, the fault collection module checks the request sending log corresponding to the middleware, wherein if the log shows that the middleware does not send the original audio request to the audio execution module, or the time interval for sending the request is abnormal, the fault collection module will record the fault.
[0076] In some embodiments, the fault collection module verifies the parameters used by the audio execution module when executing the original audio request according to a preset parameter threshold. If the parameter exceeds the preset threshold, such as the volume is too loud, the pitch is too high or too low, etc., the fault collection module will record the fault and may trigger automatic adjustment or notify the system administrator to make manual adjustments.
[0077] In some embodiments, once the fault collection module detects any fault, it will immediately record the fault details, including the fault type, occurrence time and related modules; the system administrator will receive a fault notification and can conduct further investigation and processing based on the fault details; in some cases, the fault collection module can also trigger an automatic repair mechanism to try to automatically resolve certain types of faults.
[0078] In this way, compared with feeding back the execution result or adding a request identifier during the execution of the audio request, the processing logic of executing the audio request according to the priority is set in the audio acquisition module and the audio execution module respectively. By optimizing the audio execution process, the time for engineers to analyze faults is simplified, thereby improving maintenance efficiency.
[0079] Combination Figure 5 As shown, the embodiment of the present disclosure provides an audio request execution method for a vehicle terminal, including:
[0080] Step S501, the instrument MCU obtains the handshake status between the instrument MCU and the cockpit SOC;
[0081] Step S502, if the handshake status is successful, the instrument MCU traverses the instrument indicator light, instrument pop-up window, instrument CAN signal and ADAS to collect the instrument audio request;
[0082] Step S503, the instrument MCU stores the instrument audio requests through the audio request queue, and sorts the instrument audio requests in the audio request queue according to a preset priority;
[0083] Step S504, the instrument MCU sends an instrument audio request to the cockpit SOC;
[0084] Wherein, the instrument audio request is regarded as one of the original audio requests;
[0085] Step S505, the vehicle ECU sends an ECU audio request to the cockpit SOC;
[0086] Step S506, the cockpit SOC plays, stops, and mixes the received instrument audio requests and ECU audio requests in an orderly manner according to the priority;
[0087] Step S507: The cockpit SOC outputs audio in order according to the processed audio request.
[0088] The embodiment of the present disclosure also provides a vehicle terminal, including: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the vehicle terminal executes the above method.
[0089] Figure 6The structure diagram of the computer system of the vehicle terminal suitable for implementing the embodiment of the present application is shown. It should be noted that: Figure 6 The computer system 600 of the vehicle terminal shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0090] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 602 or the program loaded from the storage part 608 to the random access memory (RAM) 603, such as executing the method in the above embodiment. In the RAM 603, various programs and data required for system operation are also stored. The CPU 601, ROM 602 and RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.
[0091] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed so that a computer program read therefrom is installed into the storage section 608 as needed.
[0092] The vehicle terminal disclosed in this embodiment includes a processor, a memory, a transceiver and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication with each other. The memory is used to store computer programs, the communication interface is used to communicate, and the processor and the transceiver are used to run computer programs so that the vehicle terminal executes each step of the above method.
[0093] The above description and accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent possible changes only. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. Parts and subsamples of some embodiments may be included in or replace parts and subsamples of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of a stated sub-sample, whole, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other sub-samples, wholes, steps, operations, elements, components and / or groups of these. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.
[0094] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. Technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. Technicians can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.
[0095] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units can be only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some sub-samples can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement this embodiment. In addition, each functional unit in the embodiment of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.
[0096] The flowchart and block diagram in the accompanying drawings show the possible architecture, functions and operations of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.
Claims
1. An audio request execution method, It is characterized in that include: Get the original audio request; The original audio request is stored in an audio request queue, and the original audio request is sorted according to a preset priority, wherein the original audio request includes a first request and a second request; Execute the original audio request according to the audio request queue, wherein, if the second request is executed when the first request is executed, determine the execution timing of the first request and the second request according to the preset priority, so as to execute the first request and / or the second request according to the execution timing.
2. The audio request execution method according to claim 1, It is characterized in that Executing the original audio request according to the audio request queue includes: Taking the first original audio request in the audio request queue as the target request; In response to the target request, obtaining the audio playback duration corresponding to the target request; Execute the target request and count the request execution time corresponding to the target request; In response to the request execution duration being greater than or equal to the audio playback duration, the first original audio request in the audio queue is used as a new target request.
3. The audio request execution method according to claim 2, It is characterized in that In response to the request execution duration being greater than or equal to the audio playback duration, taking the first original audio request in the audio queue as a new target request, including: If a new original audio request is stored in the audio request queue, the first original audio request in the audio request queue is used as the request to be compared; If the preset priority of the target request is higher than the preset priority of the request to be compared, in response to the request execution duration being greater than or equal to the audio playback duration, the first original audio request in the audio request queue is used as the new target request; If the preset priority of the target request is lower than or equal to the preset priority of the request to be compared, the request to be compared is used as a new target request.
4. The audio request execution method according to any one of claims 1 to 3, It is characterized in that Determining the execution sequence of the first request and the second request according to the preset priority includes at least one of the following: If the preset priority of the first request is higher than the preset priority of the second request, executing the first request and the second request in sequence; If the preset priority of the first request is equal to the preset priority of the second request, executing the first request and the second request according to a first timing sequence or a second timing sequence, wherein the first timing sequence includes sequentially executing the first request and the second request, and the second timing sequence includes playing the first request and the second request simultaneously; If the preset priority of the first request is lower than the preset priority of the second request, the second request and the first request are executed in sequence.
5. The audio request execution method according to claim 4, It is characterized in that Executing the second request and the first request in sequence includes: Acquire a playback interruption policy corresponding to the first request, and control the request execution phase corresponding to the first request to enter a suspension phase or a stop phase according to the playback interruption policy; Controlling the request execution phase corresponding to the second request to be in the playing phase, so as to play the audio file corresponding to the second request; If the request execution phase corresponding to the second request is in the stop phase, and the request execution phase corresponding to the first request is in the suspend phase, the request execution phase corresponding to the first request is controlled to enter the play phase.
6. An audio request execution device, It is characterized in that include: A first processor, connected to the second processor, wherein the first processor is used to obtain an original audio request; The original audio request is stored in an audio request queue, and the original audio request is sorted according to a preset priority; the original audio request is sent to the second processor according to the audio request queue, wherein the original audio request includes a first request and a second request; The second processor is used to receive the original audio request sent by the first processor and execute the original audio request, wherein if the second request is executed when the first request is executed, the execution timing of the first request and the second request is determined according to the preset priority, so as to execute the first request and / or the second request according to the execution timing.
7. The audio request execution device according to claim 6, It is characterized in that The audio request execution device is applied to a vehicle terminal, the first processor includes an instrument MCU, and the instrument MCU is further used for: Collect the instrument audio request and use the collected instrument audio request as the original audio request.
8. The audio request execution device according to claim 7, It is characterized in that The second processor includes a cockpit SOC, and the cockpit SOC is further used for: Obtaining unit priorities corresponding to the vehicle ECU and the instrument MCU respectively, wherein the vehicle ECU is also used to send an ECU audio request to the cockpit SOC; Determining a request to be executed from the original audio request and the ECU audio request, wherein the original audio request in the request to be executed is used as a third request, and the ECU audio request in the request to be executed is used as a fourth request; If the requests to be executed include both the third request and the fourth request, the unit priority corresponding to the fourth request is compared with the unit priority corresponding to the third request to obtain a priority comparison result, and the execution order of the third request and the fourth request is determined according to the priority comparison result.
9. The audio request execution device according to any one of claims 6 to 8, It is characterized in that The first processor and the second processor are connected via SPI to achieve data transmission via SPI.
10. A vehicle terminal, It is characterized in that include: Processor and memory; The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the vehicle terminal executes the method according to any one of claims 1 to 5.
