Methods, devices, equipment and storage media for restoring the whole vehicle audio link

Abstract

This application discloses a method, apparatus, device, and storage medium for restoring a vehicle audio link. The method includes: determining the fault type of each faulty slave node in at least one faulty slave node in the vehicle audio link; wherein the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus; determining a restoration method for the audio link based on the fault type of each faulty slave node; wherein the restoration method includes software initialization or power-on / off initialization performed on the slave node by the master node, the power-on / off initialization including performing the software initialization after power cycling; and restoring the audio link using the restoration method.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of vehicle technology, and in particular to a method, apparatus, device, and storage medium for restoring the audio link of a vehicle. Background Technology

[0002] Because the devices in the vehicle's audio link are connected in series, a failure in one device will render the entire audio link inoperable. Users experience numerous scenarios within the vehicle, frequently encountering faults such as signal interference and frame errors, and these faults are quite common. Once they occur, the entire audio link becomes inoperable. Therefore, a method for restoring the audio link is needed. Summary of the Invention

[0003] In view of this, embodiments of this application provide at least one method, apparatus, device, and storage medium for restoring the audio link of a vehicle.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] On one hand, embodiments of this application provide a method for restoring a vehicle audio link. The method includes: determining the fault type of each faulty slave node for at least one faulty slave node in the vehicle audio link; wherein the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus; determining a restoration method for the audio link based on the fault type of each faulty slave node; wherein the restoration method includes software initialization or power-on / off initialization performed on the slave node by the master node, the power-on / off initialization including performing the software initialization after power cycling; and restoring the audio link using the restoration method.

[0006] On the other hand, embodiments of this application provide a vehicle audio link recovery device, the device comprising: a first determining module, configured to determine the fault type of each faulty slave node in the vehicle audio link; wherein the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus; a second determining module, configured to determine a recovery method for the audio link based on the fault type of each faulty slave node; wherein the recovery method includes software initialization or power-on / off initialization performed on the slave node by the master node, the power-on / off initialization including performing the software initialization after power cycling; and a recovery module, configured to recover the audio link using the recovery method.

[0007] In another aspect, embodiments of this application provide a computer device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the program to implement some or all of the steps in the above-described method.

[0008] In another aspect, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements some or all of the steps in the above-described method.

[0009] In another aspect, embodiments of this application provide a computer program including computer-readable code, wherein when the computer-readable code is run in a computer device, a processor in the computer device performs some or all of the steps for implementing the above-described method.

[0010] In another aspect, embodiments of this application provide a computer program product, the computer program product including a non-transitory computer-readable storage medium storing a computer program, wherein when the computer program is read and executed by a computer, it implements some or all of the steps in the above method.

[0011] In this embodiment, firstly, for at least one faulty slave node in the vehicle audio link, the fault type of each faulty slave node is determined; wherein, the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus; secondly, based on the fault type of each faulty slave node, a recovery method for the audio link is determined; wherein, the recovery method includes software initialization or power-on / off initialization performed on the slave node by the master node, and power-on / off initialization includes software initialization after power-on / off; finally, the recovery method is used to restore the audio link.

[0012] As can be seen, in the embodiment of this application, in an audio link including a master node and at least one slave node, and each slave node is connected to the master node through a bus, the method for restoring the fault is determined according to the fault type of the faulty slave node, and the audio link is restored through the above-mentioned method for restoring the fault, thus solving the problem in the related technology that once a fault occurs in the audio link, the entire link cannot work.

[0013] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of this application. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0015] Figure 1A schematic diagram of the hardware connection relationship of an audio link (A2B link) provided for an embodiment of this application;

[0016] Figure 2 A schematic diagram illustrating the implementation process of a method for restoring the audio link of a vehicle, provided in an embodiment of this application;

[0017] Figure 3A A schematic diagram illustrating the implementation process of step S103 provided in an embodiment of this application;

[0018] Figure 3B A schematic diagram illustrating the implementation process of another step S103 provided in an embodiment of this application;

[0019] Figure 3C A schematic diagram illustrating the implementation process of another method for restoring the whole vehicle audio link provided in this application embodiment;

[0020] Figure 4 A software schematic diagram illustrating the implementation of a method provided in an embodiment of this application;

[0021] Figure 5A A schematic diagram illustrating the implementation of an initialization process provided in an embodiment of this application;

[0022] Figure 5B A schematic diagram illustrating the implementation process of determining a configuration file, provided in an embodiment of this application;

[0023] Figure 5C A schematic diagram illustrating the implementation process of a fault detection procedure provided in an embodiment of this application;

[0024] Figure 5D A schematic diagram illustrating the implementation process of an audio link recovery method corresponding to hot-plugging, provided in an embodiment of this application;

[0025] Figure 6 A schematic diagram of the composition structure of a vehicle audio link recovery device provided in an embodiment of this application;

[0026] Figure 7 This is a schematic diagram of the hardware entity of a computer device provided in an embodiment of this application. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0028] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0029] The terms “first / second / third” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first / second / third” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0030] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to limit the scope of this application.

[0031] The English abbreviations used in the embodiments of this application are explained below.

[0032] A2B: This is a communication transceiver launched by ADI (Analog Devices) that connects multiple audio devices via twisted-pair cables;

[0033] I2C: A simple, bidirectional, two-wire synchronous serial bus developed by Philips. It requires only two wires to transmit information between devices connected to the bus;

[0034] I2S: Inter-IC Sound bus, also known as the integrated circuit built-in audio bus;

[0035] AMP: Amplifier, external power amplifier;

[0036] MIC: Microphone.

[0037] Figure 1This diagram illustrates the hardware connection of an audio link (A2B link) according to an embodiment of this application. The A2B chip (A2B Master, also known as the master node) is powered by a system-on-chip (SOC) clock. When the microcontroller unit (MCU) detects a normal clock signal, it sends initialization data to the A2B chip via I2C. The A2B chip processes this initialization data to initialize each slave node (including AMP and MIC) of the A2B link. The A2B Master and slave nodes are connected via an A2B bus. The SOC sends multimedia (music, navigation, etc.) data to the A2B Master via I2S, and then the AMP plays the sound. Alternatively, the A2B bus transmits MIC data back to the SOC for voice data processing.

[0038] This application provides a method for restoring the audio link of a vehicle. Figure 2 As shown, the method includes the following steps S101 to S103:

[0039] Step S101: For at least one faulty slave node in the vehicle audio link, determine the fault type of each faulty slave node; wherein the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus;

[0040] Here, the master node is typically the first node in the audio link. The master node can provide clock signals, synchronization signals to slave nodes, and power slave nodes via a bus. In some embodiments, the master node can be a speaker unit in the audio link; the slave nodes can be audio devices in the audio link, such as power amplifiers, microphones, etc. In some embodiments, the audio link can be... Figure 1 The A2B link shown connects multiple audio devices via an A2B bus, enabling improved audio performance with fewer cables and providing a simpler and more convenient solution for audio design.

[0041] A faulty slave node is a node among the slave nodes that has a fault; that is, the solution provided in this application embodiment is based on the premise that the master node is normal. In the case of a faulty master node, the master node can be initialized first through the MCU, and after it is restored to normal, the solution provided in this application embodiment can be implemented.

[0042] In some embodiments, each slave node has a register, and in the event of a slave node failure, the fault register in each register displays the fault type, thereby obtaining the fault type of each failed slave node.

[0043] Step S102: Based on the fault type of each of the faulty slave nodes, determine the recovery method of the audio link; wherein, the recovery method includes software initialization or power-on / off initialization performed by the master node on the slave node, and the power-on / off initialization includes performing the software initialization after power-on / off;

[0044] Here, different recovery methods are used for different types of faults. Therefore, the recovery method can be determined according to the type of fault.

[0045] Software initialization refers to the initialization method implemented through software, where the master node initializes the slave nodes. Since each slave node in the audio link is connected to the master node via a bus, the configuration information of the audio link can be sent to the master node through software. Then, the master node transmits the configuration information of the audio link to the slave nodes, and finally, the slave nodes write the configuration information to complete the initialization.

[0046] When the audio link is an A2B link, the software initialization process can include: determining the audio link configuration information through the vehicle configuration, loading the audio link configuration information into the protocol stack in the MCU, and then sending the configuration information to the master node via I2C. After the master node transmits the information to the slave node, it is written to the device where the slave node is located, thus completing the initialization of the device where the slave node is located.

[0047] In some embodiments, the implementation of step S102 may include the following steps S1021 and S1022:

[0048] Step S1021: When the fault type of each of the fault slave nodes is a non-power fault, the determined recovery method includes the software initialization;

[0049] Here, non-power supply faults include signal interference, frame errors, etc. Since the faults are not serious, they can be eliminated through software initialization.

[0050] Step S1022: If the fault type of the at least one faulty slave node includes a power failure, the determined recovery method includes the power-on / off initialization.

[0051] Here, the power failure is quite severe and cannot be resolved through software initialization. Therefore, it is necessary to power the chip back on and off to restore it to its initial state before performing software initialization.

[0052] It should be noted that when a power failure occurs, there is usually only one faulty slave node because the link has been broken; however, when there is no power failure, there can be at least one faulty slave node, i.e., there can be multiple faulty slave nodes.

[0053] Step S103: Use the recovery method described above to restore the audio link.

[0054] In this embodiment, firstly, for at least one faulty slave node in the vehicle audio link, the fault type of each faulty slave node is determined; wherein, the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus; secondly, based on the fault type of each faulty slave node, a recovery method for the audio link is determined; wherein, the recovery method includes software initialization or power-on / off initialization performed on the slave node by the master node, and power-on / off initialization includes software initialization after power-on / off; finally, the recovery method is used to restore the audio link.

[0055] As can be seen, in the embodiment of this application, in an audio link including a master node and at least one slave node, and each slave node is connected to the master node through a bus, the method for restoring the fault is determined according to the fault type of the faulty slave node, and the audio link is restored through the above-mentioned method for restoring the fault, thus solving the problem in the related technology that once a fault occurs in the audio link, the entire link cannot work.

[0056] In cases where the recovery method includes software initialization, such as Figure 3A As shown, the implementation of step S103, "recovering the audio link using the recovery method", includes the following steps S1031a to S1034a:

[0057] Step S1031a: Periodically obtain the current number of nodes and the previous number of nodes found in the audio link;

[0058] Here, since each chip at a node has a corresponding product model register, the presence or absence of a node is determined by reading the product model from the register. If the product model is found in the register, it indicates that a node has been found; otherwise, it indicates that no node has been found.

[0059] The device periodically reads the product model from the register to ensure that all nodes are discovered. The current node count refers to the number of nodes discovered during the current read of the product model from the register. The previous node count refers to the number of nodes discovered during the previous read of the product model from the register.

[0060] Step S1032a: If the current number of nodes is greater than the previous number of nodes, the master node transmits the configuration information of the audio link to each currently discovered slave node;

[0061] If the current number of nodes is greater than the previous number of nodes, it indicates that new nodes have been discovered. Therefore, software initialization needs to continue; that is, software initialization is performed every time a new node is discovered. At this time, the master node transmits the audio link configuration information obtained through the protocol stack parsing to each of the currently discovered slave nodes.

[0062] In some embodiments, the method for determining configuration information may include the following steps S201 and S202:

[0063] Step S201: Obtain the microphone configuration and power amplifier version number in the audio link;

[0064] Here, the implementation of step S201 may include: obtaining the version number of the power amplifier in the audio link and the number of vehicle seats (5-seater or 6-seater) through the CAN signal, and then obtaining the microphone configuration through the number of vehicle seats, for example, 4 MICs for a 5-seater vehicle and 6 MICs for a 6-seater vehicle, thereby obtaining the microphone configuration and the version number of the power amplifier.

[0065] Step S202: Determine the configuration information of the audio link based on the microphone configuration and the power amplifier version number in the audio link.

[0066] Here, the configuration information differs depending on the microphone configuration and power amplifier version number. Therefore, by determining the configuration information through the microphone configuration and power amplifier version number, a single software package can be adapted to multiple vehicle models, thereby enhancing the adaptability of the solution provided in this application embodiment.

[0067] If the microphone configuration and power amplifier version number are not obtained within the timeout period, the default microphone configuration and power amplifier version number can be used.

[0068] Step S1033a: Based on the configuration information, initialize each of the discovered slave nodes;

[0069] Here, the implementation of step S1033a may include: after receiving the configuration information of the audio link from the slave node, the slave node writes the configuration information into the device where the slave node is located, thereby completing the initialization of the device where the slave node is located.

[0070] Step S1034a: If the current number of nodes is equal to the previous number of nodes, or if the current number of nodes is equal to the total number of nodes configured for the audio link, stop the software initialization so that each slave node currently discovered by the audio link can return to normal.

[0071] Here, the total number of nodes in the audio link configuration refers to the total number of devices in the initial configuration of the audio link.

[0072] When the current number of nodes equals the previous number of nodes, it indicates that no new nodes have been added.

[0073] When the current number of nodes equals the total number of nodes configured for the audio link, meaning all nodes of the audio link have been discovered, software initialization needs to be stopped in both of these scenarios.

[0074] It should be noted that software initialization immediately after power-on should stop when the current number of nodes equals the total number of nodes configured for the audio link. During normal use, if hot-plugging occurs, software initialization should stop when the current number of nodes equals the previous number of nodes.

[0075] In this embodiment, firstly, the current number of nodes and the previous number of nodes discovered in the audio link are periodically acquired. Then, based on the magnitude of the current number of nodes and the previous number of nodes, it is determined whether software initialization should be performed. If the current number of nodes is greater than the previous number of nodes, it indicates that new nodes have been discovered, and software initialization needs to continue. If the current number of nodes is equal to the previous number of nodes, or if the current number of nodes is equal to the total number of nodes configured in the audio link, it indicates that all nodes have been discovered, and software initialization stops. This provides a method for software initialization. This not only prevents nodes from going undiscovered but also provides a method for determining when to stop software initialization, ensuring that all nodes discovered in the audio link are initialized.

[0076] In the case where the recovery method includes power-on / off initialization, such as Figure 3B As shown, the implementation of step S103, "recovering the audio link using the recovery method", may include the following steps S1031b and S1032b:

[0077] Step S1031b: Power on and off the audio link again;

[0078] Powering on and off means first powering off the audio link and then powering it on.

[0079] Step S1032b: Use the software initialization method to restore the slave nodes before the faulty slave node in the audio link.

[0080] Here, the software initialization method can be found in steps S1031a to S1034a. Since power-on / off initialization corresponds to a power failure, and the audio link is disconnected during a power failure, after power-on / off, the slave nodes before the faulty slave node can obtain power because they are connected to the master node and can return to normal after re-initialization; however, the slave nodes after the faulty slave node cannot obtain power from the master node because the audio link is disconnected. Therefore, they cannot be detected during the node detection process in step S1031a and cannot complete the initialization and return to normal.

[0081] In this embodiment, since the power-on / off initialization corresponds to a power failure, and the power failure is a serious problem, it is necessary to power on and off again to restore the device to its initial state before software initialization, so as to restore the slave nodes before the faulty slave node to normal.

[0082] When the fault type of the faulty slave node is a power failure, the method further includes the following steps S104 and S105:

[0083] Step S104: Periodically read the fault status of the faulty slave node;

[0084] Here, the fault status can include both the absence of a fault and the presence of a fault.

[0085] Step S105: If the fault status of the faulty slave node indicates that there is no fault, the software initialization recovery method is used again to restore the slave node in the audio link.

[0086] Here, if the faulty slave node is not faulty, it is equivalent to reconnecting the audio link. In order for the slave nodes after the faulty slave node to also return to normal, software initialization is required.

[0087] In some embodiments, such as Figure 3C As shown, the method further includes the following steps S301 and S302:

[0088] Step S301: When the audio link is in normal working condition, obtain the number of second nodes found in the audio link;

[0089] Step S302: If the number of the second discovered nodes is less than the total number of nodes configured in the audio link, the software initialization recovery method is used to initialize the slave nodes in the audio link before the first disconnected slave node until they are restored to normal.

[0090] Here, the first disconnected slave node refers to the slave node closest to the master node. Since the audio link is in normal working order, the number of discovered second nodes is less than the total number of nodes configured for the audio link. This can accommodate hot-plugging of devices in the audio link, where one, two, or more devices can be hot-plugged. After hot-plugging, the link is effectively disconnected and the device cannot function properly. Initializing the audio link using the software initialization method described in steps S1031a to S1034a allows all slave nodes before the first disconnected slave node to return to normal operation.

[0091] In some embodiments, in the case of hot-plugging and reinstallation, the audio link can be re-software initialized to restore the link.

[0092] Most commercially available solutions for vehicle audio links initialize upon power-up and do not support hot-swapping. This means that if any device loses power during this period, the entire link becomes unusable. The solution provided in this application addresses this issue, making the entire link an adaptive link that automatically reinitializes after a device loses power, resulting in stronger and more stable device performance.

[0093] The following uses an A2B audio link as an example to illustrate the solution provided in the embodiments of this application.

[0094] When a device in the vehicle audio link malfunctions, the entire link becomes inoperable because it is connected in series. Since users encounter numerous in-vehicle scenarios with varying signal interference, this situation is highly likely to occur. This application was conceived based on this understanding. Upon detecting similar problems or unplugging / plugging of devices on the link, the link is immediately reinitialized, thus ensuring greater stability.

[0095] The principle is based on the A2B chip's registers. By periodically checking the A2B's fault register, faults throughout the entire link are detected. Upon a fault, the link is reinitialized according to its location, allowing fault-free sections to continue functioning normally. If signal interference causes link abnormalities, such as abnormal audio or noise, this can also be resolved through fault detection and subsequent reinitialization.

[0096] Figure 4 The illustration shows a software schematic of the method implementation provided in this application embodiment. The application layer comprises an A2B initialization module and an A2B main processing module. The A2B initialization module is responsible for the power-on and software initialization processes of the A2B chip, while the A2B main processing module is responsible for implementing the hot-plug function and the fault detection mechanism. The A2B protocol stack is provided by the chip manufacturer and needs to be ported to the system; the A2B configuration file is generated after configuration using tools provided by the manufacturer. The driver layer includes an I2C driver, which is an encapsulation of the I2C interface. The I2C driver includes read / write interfaces and an initialization interface, because the A2B configuration information is sent from the MCU to the A2B chip via I2C.

[0097] The process involves the application layer calling a function within the protocol stack. This function indexes the corresponding A2B configuration file and then calls the driver layer's I2C interface to send the command to the chip, completing the execution of initialization instructions.

[0098] Part 1: The current A2B initialization process (corresponding to the software initialization process after power-on) is as follows: First, the master node discovers devices, then proceeds to discover all slave devices sequentially. If an exception occurs during discovery, the process restarts. If all nodes are successfully discovered, the A2B configuration information is loaded into the protocol stack, and then written to the devices via I2C. This step is the actual initialization. If initialization encounters I2C errors or other issues, it restarts. If initialization succeeds without returning errors, a complete initialization process is finished.

[0099] The corresponding initialization process steps are as follows: Figure 5A As shown, the steps include S401 to S408 as follows:

[0100] Step S401: Starting from the master node, discover all nodes (i.e., the current number of nodes mentioned above);

[0101] Step S402: Determine whether all devices have been discovered (i.e., the current number of nodes is equal to the previous number of nodes, or the current number of nodes is equal to the total number of nodes configured for the audio link)? If yes, proceed to step S404; if no, proceed to step S403.

[0102] Step S403: If a problem is found, rediscover the problem (i.e., the current number of nodes is greater than the previous number of nodes);

[0103] Step S404: Load the A2B configuration information into the protocol stack;

[0104] Step S405: Initialize all devices;

[0105] Step S406: Determine if there is a problem with the initialization. If yes, proceed to step S407; if no, proceed to step S408.

[0106] Step S407: Initialization problem, re-initialize;

[0107] Step S408: End.

[0108] Part Two: Before initialization, detect the number of seats and the version number of the amplifier. Select the corresponding A2B configuration file according to different vehicle configurations. If the acquisition times out, use the default configuration.

[0109] The corresponding steps for determining the configuration file are as follows: Figure 5B As shown, the steps include S501 to S506 as follows:

[0110] Step S501: Was the number of seats successfully obtained? If yes, proceed to step S502; if no, proceed to step S503.

[0111] Step S502: Use the default MIC configuration;

[0112] Step S503: 5-seater vehicles use 4 microphones, and 6-seater vehicles use 6 microphones.

[0113] Step S504: Was the acquisition of the amplifier's AMP version number successful? If yes, proceed to step S506; if no, proceed to step S505.

[0114] Step S505: Use the default AMP configuration;

[0115] Step S506: Select the A2B configuration based on the AMP version number and MIC configuration;

[0116] Step S507: End.

[0117] Part Three: Periodically query the A2B fault register to determine whether it's a power supply fault (as mentioned above) or signal interference (as mentioned above, a non-power supply fault). Based on the fault type, choose between software initialization or a power-on / power-off initialization (as mentioned above). Power supply faults are more serious, so software initialization may not solve the problem; in this case, the chip must be powered on and off to restore it to its initial state. Faults other than power supply faults, such as interference or frame errors, are resolved through software initialization. If a power supply fault occurs, it's necessary to identify the node where the fault occurs. Depending on the number of faulty nodes, if an intermediate node has a power supply fault, the link before the faulty node is still normal. Therefore, after re-initialization, the link can still be used normally, and the initialized circuit can still function properly. In this case, the fault register needs to be read periodically. Once the fault is resolved, re-initialization is required to restore normal operation.

[0118] The corresponding fault detection process is as follows: Figure 5C As shown, the steps include S601 to S607 as follows:

[0119] Step S601: Periodically read the fault register of A2B;

[0120] Step S602: Determine if any node has a fault. If yes, proceed to step S604; if no, proceed to step S603.

[0121] Step S603: Periodically print logs indicating normal link operation;

[0122] Step S604: Determine the type of fault? If it is a power-related fault, proceed to step S606; if it is another fault, proceed to step S605.

[0123] Step S605: Execute the software initialization process and call the code's initialization function;

[0124] Step S606: Power on and off the chip again, and then execute the software initialization process;

[0125] Step S607: End.

[0126] Part Four: Hot-swapping, also known as hot-plugging, means that the device can continue to function normally after being plugged in or unplugged without interrupting power. Hot-plugging is achieved by periodically detecting whether a device has been unplugged and then immediately resetting the device. This method also requires the A2B chip to be powered by bus during the design phase. In other words, the power to the slave devices is provided by the bus and there is no external power supply. Once two slave devices are connected, the power supply is completed, and then the software can be initialized.

[0127] Each A2B chip has a corresponding product model register. This register is read to determine if an A2B node has been found, and so on, to determine the number of A2B nodes found. The total number of nodes is determined when configuring the audio link. The number of found nodes is compared with the preset total number. If all nodes are found, it means A2B has been fully discovered, which is normal. If not all nodes are found, it means there are still devices not connected to A2B. Initialization can restore the devices connected to the disconnected nodes. In this case, the product model register is periodically queried. If an increase in the number of devices is detected, A2B is reinitialized.

[0128] The audio link recovery method corresponding to hot-plugging is as follows: Figure 5D As shown, the steps include S701 to S705 as follows:

[0129] Step S701: Periodically read the product ID from the A2B register;

[0130] Step S702: Determine whether the number of discovered nodes is consistent with the preset total number of nodes (i.e., the total number of nodes configured in the above audio link). If yes, proceed to step S704; if no, proceed to step S703.

[0131] Step S703: Inconsistent reinitialization of the link (including both hot-plugging and reinstallation after hot-plugging);

[0132] Step S704: Print the log indicating that A2B is working correctly;

[0133] Step S705: End.

[0134] The advantages of this application's embodiments include: making the A2B link more stable, capable of self-recovery in the event of a fault, and preventing prolonged failure. It also enhances the flexibility of the A2B link, automatically identifying the number of available nodes when devices are plugged in or unplugged, and then customizing initialization accordingly. A single software package can adapt to multiple vehicle models; some vehicles lack external amplifiers or have different models, and four-seater and six-seater vehicles have different numbers of microphones. This application's embodiments can automatically adapt to these needs and switch between them at will. Modern automotive R&D and production follow a platform-based approach, requiring a single software package to adapt to multiple vehicle models, necessitating the software provided in this application's embodiments to be more flexible and adaptable. The solution provided in this application's embodiments solves the problem of adapting vehicle audio across different vehicles, providing excellent compatibility with low-end and high-end models, as well as five-seater and six-seater vehicles.

[0135] The embodiments of this application handle faults and interference, enabling the vehicle's audio link to self-repair. Furthermore, cabin sound has a significant impact on user experience and safety; the embodiments of this application also strengthen driving safety protection, minimizing the impact of uncontrollable faults on users.

[0136] Implementing hot-swapping functionality through the product model register is an important part of this application's embodiments. In related technologies, if a device loses power, it needs to be powered on again. This application's embodiments optimize the power-on process and solve the hot-swapping problem through a software adaptive method.

[0137] Based on the foregoing embodiments, this application provides a vehicle audio link restoration device. The device includes various modules and units included in each module, which can be implemented by a processor in a computer device; of course, it can also be implemented by specific logic circuits. In the implementation process, the processor can be a central processing unit (CPU), a microprocessor unit (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA), etc.

[0138] Figure 6 This is a schematic diagram of the composition structure of a vehicle audio link recovery device provided in an embodiment of this application, as shown below. Figure 6 As shown, the vehicle audio link recovery device 600 includes: a first determining module 610, a second determining module 620, and a recovery module 630, wherein:

[0139] The first determining module 610 is used to determine the fault type of each faulty slave node for at least one faulty slave node in the vehicle audio link; wherein the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus.

[0140] The second determining module 620 is used to determine the recovery method of the audio link based on the fault type of each of the faulty slave nodes; wherein the recovery method includes software initialization or power-on / off initialization performed by the master node on the slave node, and the power-on / off initialization includes performing the software initialization after power-on / off;

[0141] The recovery module 630 is used to recover the audio link using the recovery method.

[0142] In some embodiments, the second determining module 620 includes: a first determining submodule, configured to determine the recovery method including the software initialization when the fault type of each of the faulty slave nodes is a non-power fault; and a second determining submodule, configured to determine the recovery method including the power-on / off initialization when the fault type of the at least one faulty slave node includes a power fault.

[0143] In some embodiments, when the recovery method includes software initialization, the recovery module includes: an acquisition submodule, configured to periodically acquire the current number of nodes and the previous number of nodes found in the audio link; a transmission submodule, configured to transmit the configuration information of the audio link to each currently discovered slave node through the master node when the current number of nodes is greater than the previous number of nodes; an initialization submodule, configured to initialize each discovered slave node based on the configuration information; and a stop submodule, configured to stop the software initialization when the current number of nodes is equal to the previous number of nodes, or when the current number of nodes is equal to the total number of nodes configured in the audio link, so that each currently discovered slave node of the audio link returns to normal.

[0144] In some embodiments, when the recovery method includes power-on / off initialization, the recovery module includes: a power-on / off module for powering on / off the audio link; and a recovery submodule for recovering the slave nodes preceding the faulty slave node in the audio link using the software initialization method.

[0145] In some embodiments, when the fault type of the faulty slave node is a power failure, the apparatus further includes: a reading module for periodically reading the fault status of the faulty slave node; and a recovery module for re-applying the software-initialized recovery method to recover the slave node in the audio link when the fault status of the faulty slave node indicates that there is no fault.

[0146] In some embodiments, the apparatus further includes: a first acquisition module, configured to acquire the configuration of the microphone and the version number of the power amplifier in the audio link; and a third determination module, configured to determine the configuration information of the audio link based on the configuration of the microphone and the version number of the power amplifier in the audio link.

[0147] In some embodiments, the apparatus further includes: a second acquisition module, configured to acquire the number of second nodes found in the audio link when the audio link is in normal working condition; and a recovery module, configured to initialize the slave nodes in the audio link before the first disconnected slave node to normal working condition using the software initialization recovery method when the number of second nodes found is less than the total number of nodes configured in the audio link.

[0148] The descriptions of the apparatus embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. In some embodiments, the functions or modules included in the apparatus provided in this disclosure can be used to perform the methods described in the method embodiments above. For technical details not disclosed in the apparatus embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0149] It should be noted that, in the embodiments of this application, if the above-described method for restoring the whole vehicle audio link is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware, software, or firmware, or any combination of hardware, software, and firmware.

[0150] This application provides a computer device including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the program, it implements some or all of the steps in the above-described method.

[0151] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements some or all of the steps in the above-described method. The computer-readable storage medium can be transient or non-transient.

[0152] This application provides a computer program including computer-readable code, wherein when the computer-readable code is executed in a computer device, a processor in the computer device performs some or all of the steps in the above-described method.

[0153] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium; in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.

[0154] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between them, while their similarities or commonalities can be referred to interchangeably. The descriptions of the above embodiments of the device, storage medium, computer program, and computer program product are similar to the descriptions of the above method embodiments and have similar beneficial effects. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0155] It should be noted that, Figure 7 This is a schematic diagram of a hardware entity of a computer device in an embodiment of this application, such as... Figure 7 As shown, the hardware entity of the computer device 700 includes: a processor 701, a communication interface 702, and a memory 703, wherein:

[0156] Processor 701 typically controls the overall operation of computer device 700.

[0157] Communication interface 702 enables computer devices to communicate with other terminals or servers over a network.

[0158] The memory 703 is configured to store instructions and applications executable by the processor 701, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data, and video communication data) in the processor 701 and various modules in the computer device 700. It can be implemented using flash memory or random access memory (RAM). Data transfer between the processor 701, the communication interface 702, and the memory 703 can be performed via bus 704.

[0159] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply a sequential order of execution; the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0160] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0161] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0162] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0163] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0164] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0165] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, magnetic disks, or optical disks.

[0166] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A method for restoring the audio link of a vehicle, characterized in that, include: For at least one faulty slave node in the vehicle audio link, the fault type of each faulty slave node is determined based on the fault register in the register of the faulty slave node; wherein, the audio link includes a master node and at least one slave node, and each slave node is connected to the master node via a bus; When the fault type of each of the aforementioned faulty slave nodes is a non-power fault, the determined recovery method includes software initialization of the slave nodes by the master node; the software initialization includes: determining the current number of nodes found in the audio link based on the number of product models read from the registers corresponding to the slave nodes; periodically acquiring the current number of nodes found in the audio link and the previous number of nodes; when the current number of nodes is greater than the previous number of nodes, transmitting the configuration information of the audio link to each currently found slave node through the master node; initializing each found slave node based on the configuration information; and stopping the software initialization when the current number of nodes is equal to the previous number of nodes, or when the current number of nodes is equal to the total number of nodes configured for the audio link, so that each currently found slave node of the audio link returns to normal. In the case where the fault type of the at least one faulty slave node includes a power failure, the determined recovery method includes power-on / off initialization of the slave node by the master node; wherein, the power-on / off initialization includes performing the software initialization after power-on / off; the software initialization includes the slave node initializing based on the configuration information of the audio link; the configuration information is determined according to the vehicle configuration; The audio link is restored using the described recovery method.

2. The method according to claim 1, characterized in that, When the recovery method includes power-on / off initialization, the step of restoring the audio link using the recovery method includes: Power cycle the audio link; The software initialization method described above is used to restore the slave nodes preceding the faulty slave node in the audio link.

3. The method according to claim 2, characterized in that, In the case where the fault type of the faulty slave node is a power failure, the following is also included: Periodically read the fault status of the faulty slave node; If the fault status of the faulty slave node indicates that there is no fault, the software-initialized recovery method is used again to restore the slave node in the audio link.

4. The method according to claim 1, characterized in that, Also includes: Obtain the microphone configuration and power amplifier version number in the audio link; The configuration information of the audio link is determined based on the microphone configuration and the power amplifier version number in the audio link.

5. The method according to any one of claims 1 to 4, characterized in that, Also includes: When the audio link is in normal working condition, obtain the number of second nodes found in the audio link; If the number of the second discovered nodes is less than the total number of nodes configured in the audio link, the software initialization recovery method is used to initialize the slave nodes in the audio link before the first disconnected slave node until they are restored to normal.

6. A device for restoring the audio link of a vehicle, characterized in that, include: The first determining module is used to determine the fault type of each faulty slave node based on the fault register in the register of the faulty slave node for at least one faulty slave node in the vehicle audio link; wherein the audio link includes a master node and at least one slave node, and each slave node is connected to the master node through a bus; The second determining module is configured to, when the fault type of each of the faulty slave nodes is a non-power failure, determine the recovery method as including software initialization of the slave nodes by the master node; the software initialization includes: determining the current number of nodes found in the audio link based on the number of product models read from the registers corresponding to the slave nodes; periodically acquiring the current number of nodes found in the audio link and the previous number of nodes; when the current number of nodes is greater than the previous number of nodes, transmitting the configuration information of the audio link to each currently found slave node by the master node; initializing each found slave node based on the configuration information; stopping the software initialization when the current number of nodes is equal to the previous number of nodes, or when the current number of nodes is equal to the total number of nodes configured for the audio link, so that each currently found slave node of the audio link returns to normal; when the fault type of at least one faulty slave node includes a power failure, the determined recovery method includes power-on / off initialization of the slave node by the master node; wherein, the power-on / off initialization includes performing the software initialization after power-on / off; the software initialization includes the slave node initializing based on the configuration information of the audio link; the configuration information is determined according to the vehicle configuration; A recovery module is used to restore the audio link using the recovery method.

7. A computer device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 5.

Images