Communication method, apparatus and vehicle

Abstract

A communication method, apparatus, and vehicle are disclosed. The method includes: a first slave node experiencing a first interruption determining a first uplink frame, the first uplink frame including a slave node identifier and first interruption slave node information, the slave node identifier indicating the slave node that initiated the first uplink frame, and the first interruption slave node information indicating that the first slave node experienced a first interruption (S801); the first slave node transmitting the first uplink frame (S802). Upon receiving the first uplink frame, the master node can determine that the first slave node initiated the interruption (S803), and then perform fault diagnosis and / or fault location based on the type of the first interruption. The technical solution of this application can be applied to the field of audio and video transmission, increasing the opportunity for slave nodes to report interruptions in audio and video systems, thereby improving the efficiency of slave node interrupt reporting.

Description

Communication methods, devices and vehicles Technical Field

[0001] This application relates to the field of audio and video transmission, and more specifically, to a communication method, apparatus, and vehicle. Background Technology

[0002] In a vehicle's wired audio-visual system, there is usually an audio-visual control device and multiple audio-visual devices. The audio-visual control device and the multiple audio-visual devices are usually connected in a daisy-chain network. The audio-visual control device sends the audio-visual data to be played to one or more audio-visual devices for playback through the audio-visual bus. The audio-visual devices transmit the audio-visual data they have collected to the audio-visual control device through the audio-visual bus.

[0003] When audio and video control equipment communicates with multiple audio and video devices in a daisy-chain network, how to quickly report the interruption to the audio and video control equipment when the audio and video devices experience interruptions such as transmission interruption, parameter interruption, or peripheral interruption becomes an urgent problem to be solved.

[0004] Summary of the Invention

[0005] This application provides a communication method, apparatus, and vehicle that can improve the speed at which nodes report interrupt information, thereby improving the efficiency of audio and video systems in resolving interrupt-related faults.

[0006] In a first aspect, a communication method is provided, which is applied to a slave node in an audio-visual system. For example, it can be executed by a chip or circuit of the slave node. The following description takes the execution of this method by a first slave node or the chip or circuit of the first slave node that has experienced a first interrupt as an example.

[0007] The method includes: determining a first uplink frame, the first uplink frame including a slave node identifier and first interrupted slave node information, the slave node identifier indicating the slave node that initiated the first uplink frame, and the first interrupted slave node information indicating that the first slave node has experienced a first interruption; and sending the first uplink frame.

[0008] In some implementations, if the slave node initiating the first uplink frame is not the first slave node, then the slave node identifier is not the identifier of the first slave node. The slave node initiating the first uplink frame (or the initiating slave node of the first uplink frame) refers to the source of the first uplink frame, that is, the slave node that initiates the composition and transmission of the uplink frame. The act of initiating the composition and transmission of the uplink frame by the slave node is called initiating the uplink frame. In one case, if the source of the first uplink frame is the first slave node, then the slave node identifier is the identifier of the first slave node, that is, the first uplink frame is determined to be the generated first uplink frame. In another case, if the source of the first uplink frame is a slave node of the downlink of the first slave node, then the first uplink frame is determined to include the first uplink frame obtained based on the uplink frame received from the downlink. During the transmission of the uplink frame, the data and / or control information in the uplink frame may change, but the frame number and frame type of the uplink frame remain unchanged. In the latter case, determining the first uplink frame includes: determining the first uplink frame based on the uplink frames received from the downlink, that is, without modifying the frame number and frame type of the received uplink frame, modifying the corresponding value of the field used to carry the information of the first interrupted slave node to obtain the first uplink frame. Here, the frame number indicates the order of the transmitted frames; for example, the frame number of the first discovery frame indicates the order or sequence of the first discovery frame among all transmitted frames. The frame number can start from 0 and increment cyclically for each frame. The frame type indicates whether the uplink frame is a configuration frame, a data frame, or a discovery frame.

[0009] It should be noted that the term "slave node interruption" in this application can be understood as: the slave node experiencing an interruption (e.g., the slave node being unable to perform normal data transmission); or, an interruption related to the slave node, such as an interruption between the slave node and the downlink slave node when the slave node is not the end slave node; or, an interruption affecting the slave node, such as an interruption in the communication bus of the audio / video system that may affect the stability of the audio / video system. In this case, the interruption is considered to affect the current slave node. The end slave node is the last slave node in the daisy chain of the audio / video system, which has no downlink or no other slave node in its downlink.

[0010] In the above technical solution, when the first slave node experiences an interruption, it can report interruption-related information to the master node in an uplink frame initiated by another slave node, or it can report interruption-related information in its own uplink frame. This increases the opportunities for slave nodes to report interruptions, thereby improving the speed at which slave nodes report interruption information. Furthermore, when the first slave node reports interruption-related information to the master node in an uplink frame initiated by another slave node, it does not change the information indicating the slave node that initiated the uplink frame (i.e., the slave node identifier). This ensures that interruption reporting does not affect the transmission control information of the slave node that initiated the uplink frame, and also helps to save signaling overhead during the interruption reporting process.

[0011] Secondly, a communication method is provided, which is applied to a slave node in an audio-visual system. For example, it can be executed by a chip or circuit of the slave node. The following description takes the execution of this method by a chip or circuit of the first slave node as an example.

[0012] The method includes: a first slave node experiencing a first interruption; the first slave node sending a first uplink frame, the first uplink frame including a slave node identifier and first interrupted slave node information, the slave node identifier indicating the slave node that initiated the first uplink frame, and the first interrupted slave node information indicating that the first slave node experienced a first interruption.

[0013] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the first interrupt slave node information includes the identifier of the first slave node.

[0014] In the above technical solution, when the first slave node reports interrupt-related information, the identifier of the first slave node is carried in the uplink frame, which helps the master node to quickly identify the slave node that initiated the interrupt, thereby improving the efficiency of clearing interrupt-related faults.

[0015] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the first uplink frame also includes information indicating the type of the first interrupt, which includes any of the following: cable fault, bus error, master node-related interrupt, general purpose input output (GPIO) interrupt, or mailbox interrupt.

[0016] In the above technical solution, when the first slave node reports interrupt-related information, the type of interrupt is indicated in the uplink frame, which helps the master node to quickly perform interrupt-related fault diagnosis and / or fault location, thereby improving the efficiency of clearing interrupt-related faults.

[0017] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method further includes: receiving a second uplink frame, the second uplink frame including a slave node identifier and second interrupted slave node information, the second interrupted slave node information being used to indicate information of the slave node that experienced the interruption; and sending a first uplink frame, including: sending the first uplink frame when the corresponding value of the second interrupted slave node information is a default value.

[0018] In the above technical solution, by not changing the information of the slave node that initiated the uplink frame (i.e., the slave node identifier) ​​in the first slave node, it can be ensured that the interruption reporting does not affect the transmission control information of the slave node that initiated the uplink frame, and it also helps to save signaling overhead in the interruption reporting process. Furthermore, the first interruption slave node information is only carried in the first uplink frame when the corresponding value of the second interruption slave node information is a default value, which can avoid affecting the interruption reporting of the slave node in the downlink of the first slave node.

[0019] In conjunction with the first aspect, in some implementations of the first aspect, the first interrupt slave node information and the second interrupt slave node information are associated with the same field to determine the first uplink frame, including: when the corresponding value of the second interrupt slave node information is a default value, adding the identifier of the first slave node as the corresponding value of the second interrupt slave node information to obtain the first uplink frame.

[0020] The first interrupt slave node information and the second interrupt slave node information are associated with the same field, which can be understood as: this field is used to carry the first interrupt slave node information, or this field is used to carry the second interrupt slave node information.

[0021] In conjunction with the second aspect, in some implementations of the second aspect, before sending the first uplink frame, the method further includes: when the corresponding value of the second interrupted slave node information is a default value, adding the identifier of the first slave node as the corresponding value of the second interrupted slave node information to obtain the first uplink frame.

[0022] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method further includes: receiving a second uplink frame, the second uplink frame including a slave node identifier, third interrupt slave node information and priority information, the third interrupt slave node information indicating that a second interrupt has occurred in the second slave node, and the priority information indicating the reporting priority of the second interrupt; sending a first uplink frame, including: sending the first uplink frame when the reporting priority of the second interrupt is lower than the reporting priority of the first interrupt.

[0023] In some possible implementations, a higher reporting priority indicates a higher degree of urgency of the interruption, requiring the exception to be resolved as soon as possible.

[0024] In the above technical solution, the interrupt-related information carried in the uplink frame can be determined according to the interrupt reporting priority. When there is no free field in the uplink frame received by the slave node to carry the interrupt information related to the first slave node, and the interrupt reporting priority of the first slave node is high, the interrupt information of the first slave node is used to cover the interrupt information with lower reporting priority. This helps to speed up the release speed of interrupts with higher reporting priority, thereby improving the reliability of the system where the first slave node is located.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the first interrupt slave node information and the third interrupt slave node information are associated with the same field to determine the first uplink frame, including: when the reporting priority of the second interrupt is lower than the reporting priority of the first interrupt, the identifier of the first slave node is used to replace the corresponding value of the third interrupt slave node information, and the corresponding value of the priority information is replaced with the reporting priority of the first interrupt to obtain the first uplink frame.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, before sending the first uplink frame, the method further includes: when the reporting priority of the second interrupt is lower than the reporting priority of the first interrupt, replacing the corresponding value of the third interrupt slave node information with the identifier of the first slave node, and replacing the corresponding value of the priority information with the reporting priority of the first interrupt, to obtain the first uplink frame.

[0027] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method further includes: receiving a third uplink frame, the third uplink frame including interrupted slave node information indicating that an interruption has occurred in a slave node in the downlink of the first slave node; sending the third uplink frame; or, replacing the corresponding value of the interrupted slave node information with the identifier of the first slave node to obtain a first uplink frame and sending the first uplink frame.

[0028] It should be noted that the third uplink frame does not include priority information. Determining the first uplink frame based on the third uplink frame can be understood as follows: when both a slave node closer to the master node and a slave node farther from the master node experience an interrupt, the former's interrupt reporting priority is higher than the latter's interrupt reporting priority.

[0029] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the first uplink frame also includes interrupt request information, which indicates that the first interrupt slave node information is valid.

[0030] The interrupt request information indicating that the first interrupt slave node information is valid can be understood as: the interrupt request information indicates that a slave node has initiated an interrupt.

[0031] In some implementations, the interrupt request information is a 1-bit information. A value of "0" indicates that no slave node initiated an interrupt, or that the slave node that initiated the uplink frame is not the slave node that initiated the interrupt. A value of "1" indicates that a slave node initiated an interrupt, and the corresponding value of the interrupt slave node information indicates the slave node that initiated the interrupt.

[0032] In the above technical solution, the interruption request information enables the slave or master node in the uplink of the first slave node to quickly determine whether a slave node has initiated an interruption. When the interruption request information indicates that no slave node has initiated an interruption, the relevant fields of the interrupted slave node information do not need to be parsed, which helps to reduce the processing complexity of the master node and / or slave node.

[0033] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the first uplink frame further includes fourth interrupt slave node information, the corresponding value of the fourth interrupt slave node information being a default value, or the corresponding value of the fourth interrupt slave node information being the identifier of the third slave node, or the fourth interrupt slave node information including uplink data.

[0034] The above technical solution enables different slave nodes to report interrupt-related information in one uplink frame, which increases the chance of slave nodes reporting interrupts, improves the efficiency of slave nodes reporting interrupts, and saves the signaling overhead required for interrupt information reporting.

[0035] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method further includes: receiving a fourth uplink frame, the fourth uplink frame including fifth interrupt slave node information and sixth interrupt slave node information, the fifth interrupt slave node information and the first interrupt slave node information being associated with the same field, and the sixth interrupt slave node information and the fourth interrupt slave node information being associated with the same field; and sending a first uplink frame, including: sending the first uplink frame when the corresponding value of the fifth interrupt slave node information is a default value.

[0036] In the above technical solution, when the uplink frame supports multiple slave nodes to report interrupt-related information simultaneously, if at least one of the fields used to carry interrupted slave node information has a default value, the first slave node reports the interrupt-related information in this uplink frame; otherwise, the first slave node suspends reporting the interrupt-related information. This can prevent the interrupt information reported by the slave node that experienced an interruption in the downlink from being overwritten, and helps to improve the efficiency of slave node reporting anomalies.

[0037] In conjunction with the first aspect, in some implementations of the first aspect, generating the first uplink frame includes: when the corresponding value of the fifth interrupt slave node information is a default value, adding the identifier of the first slave node as the corresponding value of the fifth interrupt slave node information to obtain the first uplink frame.

[0038] In conjunction with the second aspect, in some implementations of the second aspect, before sending the first uplink frame, the method further includes: when the corresponding value of the fifth interrupt slave node information is a default value, adding the identifier of the first slave node as the corresponding value of the fifth interrupt slave node information to obtain the first uplink frame.

[0039] In conjunction with the first or second aspect, in some implementations of the first or second aspect, the method further includes: receiving a first downlink frame, the first downlink frame including indication information indicating whether a field associated with the fourth interrupt slave node information is used to carry the identifier of the slave node that initiated the interrupt.

[0040] In the above technical solution, the field associated with the fourth interrupt slave node information indicated by the downlink frame is used to carry the identifier of the slave node that initiated the interrupt, or to carry uplink data, which helps to improve the utilization rate of each byte in the uplink frame.

[0041] In conjunction with the first aspect or the second aspect, in some implementations of the first aspect or the second aspect, the first uplink frame includes a first part and a second part, the first part is verified using first verification information, the second part is verified using second verification information, the slave node identifier is included in the first part, and the first interrupt slave node information is included in the second part.

[0042] In some implementations, the first part is used to carry control information related to the slave node that initiated the first uplink frame, and the second part is used to carry interrupt-related information.

[0043] In the above technical solution, the first part and the second part are verified using two verification information respectively. If the verification of one part fails, it will not affect the information transmission of the other part. Furthermore, if the second part does not carry interruption-related information, there is no need to perform verification-related operations on the second part, which helps to reduce the processing complexity of the slave node and / or master node.

[0044] In some implementations, the aforementioned uplink frames may also carry one or more data that the slave nodes need to transmit to the master node.

[0045] Thirdly, a communication method is provided, which is applied to a slave node in an audio-visual system. For example, it can be executed by the chip or circuit of the slave node. The following description takes the execution of this method by a fourth slave node or the chip or circuit of the fourth slave node as an example. The fourth slave node is not interrupted and is a slave node in the uplink of the first slave node.

[0046] The method includes: receiving a first uplink frame, the first uplink frame including a slave node identifier and first interrupted slave node information, the slave node identifier indicating the slave node that initiated the first uplink frame, and the first interrupted slave node information indicating that the first slave node has experienced a first interruption; and sending the first uplink frame.

[0047] In the above technical solution, the fourth slave node forwards the first uplink frame, thereby enabling the master node to quickly receive the first uplink frame and determine the slave node that experienced the interruption based on the first uplink frame.

[0048] In conjunction with the third aspect, in some implementations of the third aspect, the first interrupt slave node information includes the identifier of the first slave node.

[0049] In conjunction with the third aspect, in some implementations of the third aspect, the first uplink frame also includes information indicating the type of the first interrupt, which includes any of the following: cable fault, bus error, master node related interrupt, GPIO interrupt, or mailbox interrupt.

[0050] In conjunction with the third aspect, in some implementations of the third aspect, the first uplink frame also includes priority information, which indicates the reporting priority of the first interrupt.

[0051] In conjunction with the third aspect, in some implementations of the third aspect, the first uplink frame also includes interrupt request information, which indicates that the first interrupt slave node information is valid.

[0052] In conjunction with the third aspect, in some implementations of the third aspect, the first uplink frame also includes information about the fourth interrupt slave node, the corresponding value of which is a default value, or the corresponding value of which is the identifier of the third slave node, or the information about the fourth interrupt slave node includes uplink data.

[0053] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: receiving a first downlink frame, the first downlink frame including indication information, the indication information indicating whether a field associated with the fourth interrupt slave node information is used to carry the identifier of the slave node that initiated the interrupt.

[0054] Fourthly, a communication method is provided, which is applied to a slave node in an audio-visual system. For example, it can be executed by a chip or circuit of the slave node. The following description takes the execution of this method by a fifth slave node or the chip or circuit of the fifth slave node as an example. The fifth slave node is a slave node in the downlink of the first slave node.

[0055] The method includes: generating a second uplink frame, the second uplink frame including a slave node identifier and second interrupted slave node information, the slave node identifier indicating the slave node that initiated the second uplink frame, and the second interrupted slave node information indicating information about the slave node that experienced an interruption; and sending the second uplink frame.

[0056] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second interrupt slave node information includes the identifier of the second slave node.

[0057] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second uplink frame also includes information indicating the type of interrupt that occurred in the second slave node, the type of interrupt including any of the following: cable failure, bus error, master-related interrupt, GPIO interrupt, or mailbox interrupt.

[0058] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second uplink frame also includes priority information, which indicates the reporting priority of the interrupt that occurred in the second slave node.

[0059] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second uplink frame also includes interrupt request information, which indicates whether the second interrupt slave node information is valid or invalid.

[0060] Specifically, when the second interrupt slave node includes the identifier of the second slave node and the interrupt request information indicates that the information of the second interrupt slave node is invalid, it means that the second slave node has not been interrupted.

[0061] In conjunction with the fourth aspect, in some implementations of the fourth aspect, when the second uplink frame is initiated by the fifth slave node, the slave node identifier is the identifier of the fifth slave node.

[0062] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second uplink frame also includes information about a sixth interrupted slave node. The corresponding value of the sixth interrupted slave node information is a default value, or the corresponding value is an identifier of a slave node, or the sixth interrupted slave node information includes uplink data. Specifically, the identifier of the slave node included in the sixth interrupted slave node information can be the identifier of the downlink slave node of the fifth slave node, or, in the case of an interruption of the fifth slave node, the identifier of the slave node included in the sixth interrupted slave node information can also be the identifier of the fifth slave node.

[0063] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: receiving a first downlink frame, the first downlink frame including indication information indicating whether a field associated with the sixth interrupt slave node information is used to carry the identifier of the slave node that initiated the interrupt.

[0064] Fifthly, a communication method is provided, which is applied to the master node in an audio-visual system. For example, it can be executed by the chip or circuit of the master node. The following description takes the execution of this method by the master node or the chip or circuit of the master node as an example.

[0065] The method includes: receiving a first uplink frame, the first uplink frame including a slave node identifier and first interrupted slave node information, the slave node identifier indicating the slave node that initiated the first uplink frame, and the first interrupted slave node information indicating that the first slave node has experienced a first interruption; determining the first slave node that initiated the interruption based on the first uplink frame.

[0066] In the above technical solution, the master node can quickly identify the slave node that has experienced an interruption based on the first uplink frame, so as to handle the interruption-related faults and improve the efficiency of the audio and video system in resolving interruption-related faults.

[0067] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first interrupt slave node information includes the identifier of the first slave node.

[0068] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first uplink frame also includes information indicating the type of the first interrupt, which includes any of the following: cable fault, bus error, master node related interrupt, GPIO interrupt, or mailbox interrupt.

[0069] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: fault diagnosis and / or fault location based on the type of the first interrupt.

[0070] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: writing first information to a register of the type of the first interrupt corresponding to the first slave node, according to the type of the first interrupt, to indicate that the first slave node has no first interrupt.

[0071] In conjunction with the fifth aspect, in certain implementations of the fifth aspect, wherein the bus error includes an interruption caused by bus signal quality, fault diagnosis and / or fault location are performed according to the type of the first interrupt, including: when the type of the first interrupt is an interruption caused by bus signal quality, sending a second downlink frame, the second downlink frame being used for fault location.

[0072] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first uplink frame also includes priority information, which indicates the reporting priority of the first interrupt.

[0073] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first uplink frame also includes interrupt request information, which indicates that the first interrupt slave node information is valid.

[0074] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first uplink frame also includes information about the fourth interrupt slave node, the corresponding value of which is a default value, or the corresponding value of which is the identifier of the third slave node, or the information about the fourth interrupt slave node includes uplink data.

[0075] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: sending a first downlink frame, the first downlink frame including indication information indicating whether a field associated with the fourth interrupt slave node information is used to carry the identifier of the slave node that initiated the interrupt.

[0076] Sixthly, a data transmission structure is provided for information transmission between a master node and a slave node in an audio-visual system. The data transmission structure includes a first field and a second field. The first field is used to carry a slave node identifier, and the second field is used to carry interrupted slave node information. The slave node identifier indicates the slave node that initiated the data transmission structure, and the interrupted slave node information indicates the slave node that initiated the interruption.

[0077] In the above technical solution, by using the first field and the second field to indicate the slave node that initiates the data transmission structure and the slave node that initiates the interruption, it can be ensured that the interruption report does not affect the transmission control information of the slave node that initiates the uplink frame, and it also helps to save signaling overhead in the interruption reporting process.

[0078] In a seventh aspect, a data transmission structure is provided for information transmission between a master node and a slave node in an audio-visual system. The data transmission structure includes a slave node identifier and first interrupted slave node information. The slave node identifier indicates the slave node that initiated the first uplink frame, and the first interrupted slave node information indicates that the first slave node has experienced a first interruption.

[0079] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the data transmission structure includes a first field and a second field, wherein the first field is used to carry the slave node identifier and the second field is used to carry the interrupted slave node information.

[0080] In conjunction with aspect six or seven, in some implementations of aspect six or seven, the data transmission structure also includes a third field, which carries information indicating the type of interrupt, including any of the following: cable failure, bus error, master-node related interrupt, GPIO interrupt, or mailbox interrupt.

[0081] In conjunction with the sixth or seventh aspect, in some implementations of the sixth or seventh aspect, the data transmission structure also includes a fourth field that carries information indicating the reporting priority of the interrupt.

[0082] In some implementations, the fourth field also carries information indicating the level of the interruption, which indicates whether the interruption is in a normal or urgent state.

[0083] In conjunction with the sixth or seventh aspect, in some implementations of the sixth or seventh aspect, the data transmission structure further includes a fifth field that carries interruption request information indicating whether the corresponding value of the second field is valid.

[0084] In conjunction with the sixth or seventh aspect, in some implementations of the sixth or seventh aspect, the data transmission structure further includes a sixth field, which carries information about the type of the data transmission structure, including any of the following: discovery frame, configuration frame, or data frame.

[0085] In conjunction with the sixth or seventh aspect, in some implementations of the sixth or seventh aspect, the data transmission structure includes a first part and a second part, wherein the first part is verified using first verification information and the second part is verified using second verification information; the first field is contained in the first part and the second field is contained in the second part.

[0086] In some implementations, the first part also includes a sixth field, and the second part includes a third, fourth, and fifth field.

[0087] Eighthly, a data transmission structure is provided for information transmission between a master node and a slave node in an audio-visual system. The data transmission structure includes control information and interrupt information, wherein the control information is used to respond to downlink frames and the interrupt information is used for the slave node to initiate an interrupt.

[0088] In the above technical solution, by transmitting the information of the downlink response frame and the reported interrupt information simultaneously through the same data transmission structure, interrupt reporting can be completed at the same time as responding to the downlink frame. This helps to increase the opportunity for slave nodes to report interrupts, thereby improving the speed at which slave nodes report interrupt information, and also helps to save signaling overhead in the interrupt reporting process.

[0089] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the control information includes a slave node identifier, which is the identifier of the slave node that initiated the data transmission node.

[0090] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the interrupt information includes the identifier of the slave node that initiated the interrupt.

[0091] In conjunction with aspect eight, in some implementations of aspect eight, the interrupt information also includes an interrupt request, which indicates whether the interrupt information contains valid interrupt information. When the corresponding value of the interrupt request is 0, it indicates that there is no interrupt request, that is, no slave node initiated an interrupt; when the corresponding value of the interrupt request is 1, it indicates that there is an interrupt request, that is, the slave node corresponding to the identifier of the slave node that initiated the interrupt initiated the interrupt.

[0092] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the interrupt information also includes an interrupt type, which indicates the type of interrupt initiated by the slave node that initiated the interrupt. The interrupt type includes any of the following: cable fault, bus error, master node related interrupt, GPIO interrupt, or mailbox interrupt.

[0093] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the control information and interrupt information each correspond to independent verification information.

[0094] It should be noted that the data transmission structure in any of the implementations of the sixth to eighth aspects can be applied to the uplink frames in any of the implementations of the first to fifth aspects.

[0095] A ninth aspect provides a communication apparatus comprising a transceiver unit and a processing unit for performing a method as described in any of the possible implementations of the first to fourth aspects.

[0096] In a tenth aspect, a communication apparatus is provided, comprising a transceiver unit and a processing unit for performing the method as described in any possible implementation of the fifth aspect.

[0097] Eleventhly, a communication device is provided, the device comprising: a memory for storing a computer program; and a processor for executing the computer program stored in the memory, such that the device performs a method as described in any of the possible implementations of the first to fourth aspects.

[0098] In a twelfth aspect, a communication device is provided, comprising: a memory for storing a computer program; and a processor for executing the computer program stored in the memory, such that the device performs a method as described in any possible implementation of the fifth aspect.

[0099] In conjunction with aspects nine through twelfth, in certain implementations of any of aspects nine through twelfth, the communication device communicates with other communication devices based on the data transmission structure in any possible implementation of aspects six through eight.

[0100] In a thirteenth aspect, an audio-visual system is provided, which includes means as described in any possible implementation of the ninth aspect and as described in any possible implementation of the tenth aspect; or, the system includes means as described in any possible implementation of the eleventh aspect and as described in any possible implementation of the twelfth aspect.

[0101] In the fourteenth aspect, a vehicle is provided that includes the system as described in any possible implementation of the thirteenth aspect.

[0102] In a fifteenth aspect, a computer program product is provided, comprising: computer program code, which, when executed on a computer, causes the computer to perform a method in any of the possible implementations of the first to fifth aspects.

[0103] It should be noted that the above-mentioned computer program code can be stored in whole or in part on the first storage medium, wherein the first storage medium can be packaged together with the processor or packaged separately from the processor.

[0104] In a sixteenth aspect, a computer-readable medium is provided that stores instructions which, when executed by a processor, cause the processor to implement the method in any of the possible implementations of the first to fifth aspects.

[0105] In a seventeenth aspect, a chip is provided, the chip including circuitry for performing the methods in any of the possible implementations of the first to fifth aspects described above.

[0106] For the beneficial effects not described in detail in aspects three through seventeen, please refer to the description in aspect one, which will not be repeated here. Attached Figure Description

[0107] Figure 1 is a schematic block diagram of an audio-visual system provided in an embodiment of this application;

[0108] Figure 2 is another schematic block diagram of the audio and video system provided in the embodiments of this application;

[0109] Figure 3 is a schematic block diagram of the vehicle provided in an embodiment of this application;

[0110] Figure 4 is a schematic flowchart of the communication method provided in an embodiment of this application;

[0111] Figure 5 is a schematic diagram of the frame structure of the uplink frame provided in the embodiment of this application;

[0112] Figure 6 is another schematic diagram of the frame structure of the uplink frame provided in the embodiment of this application;

[0113] Figure 7 is a schematic diagram of the frame structure of the downlink frame provided in an embodiment of this application;

[0114] Figure 8 is a schematic diagram of a cable fault that interrupts the associated connection according to an embodiment of this application;

[0115] Figure 9 is another schematic flowchart of the communication method provided in the embodiments of this application;

[0116] Figure 10 is a schematic block diagram of a communication device provided in an embodiment of this application;

[0117] Figure 11 is another schematic block diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0118] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0119] Figure 1 shows a schematic diagram of the audio-visual system provided in an embodiment of this application. As shown in Figure 1, the audio-visual system 100 includes an audio-visual control device 110, an audio-visual device 120, an audio-visual device 130, and an audio-visual device 140. The audio-visual control device 110 includes a main controller 111 and a master node 112; the audio-visual device 120 includes an external device (hereinafter referred to as peripheral) 121 and a slave node 122; the audio-visual device 130 includes a peripheral 131 and a slave node 132; and the audio-visual device 140 includes a peripheral 141 and a slave node 142. The master node 112 is connected to the slave nodes 122, 132, and 142 via cables using a daisy-chain networking method. The slave nodes 122, 132, and 142 can be processors, transmission chips, or other devices in each audio-visual device, respectively. The peripherals 121, 131, and 141 can each include hardware functional modules such as audio-visual decoders, digital-to-analog converters, and analog-to-digital converters in each audio-visual device. The master node 112 is used for communication between the audio / video control device 110 and the audio / video devices 120 to 140. In one example, the master controller 111 sends the audio / video data that needs to be played by the audio / video device 140 to the peripheral device 141 of the audio / video device 140 in sequence through the master node 112, slave node 122, slave node 132, and slave node 142. The peripheral device 141 controls the playback of the audio / video data. In another example, the audio / video device 130 transmits the audio / video data collected by the peripheral device 131 to the master controller 111 in sequence through the slave node 132, slave node 122, and master node 112.

[0120] In this embodiment, the master node can be a logical unit that manages and controls resources for slave nodes within the link. The slave node can be a logical unit that receives resource management and control from the master node within the link.

[0121] In a link consisting of a master node and one or more slave nodes, a link in which a slave node transmits information to or towards the master node can be considered an uplink, and a link in which the slave node transmits information to a slave node farther from the master node can be considered a downlink. Furthermore, a link in which the master node transmits information to a slave node is also a downlink. In other words, a data transmission link from the master node to a slave node is a downlink, and a data transmission link from a slave node to the master node is an uplink. For example, slave node 132 can transmit data to slave node 142 via a downlink, and correspondingly, slave node 132 can also receive data from slave node 142 via an uplink. The master node can transmit data to slave nodes 122, 132, and 142 via downlinks, and slave nodes 122, 132, and 142 can transmit data to master node 112 via uplinks. Furthermore, the slave node in the downlink of slave node m is the slave node farther from the master node relative to slave node m in the daisy chain. If, during the discovery process, the identifiers assigned to slave nodes are sequentially increased, then the downlink slave nodes of slave node m are: slave nodes whose identifiers are greater than those of slave node m. Correspondingly, the uplink slave nodes of slave node m are: slave nodes in the daisy chain that are closer to the master node relative to slave node m; or, slave nodes whose identifiers are smaller than those of slave node m. Frames sent by the master or slave node through the downlink are downlink frames, and frames sent by the slave node through the uplink are uplink frames. Functionally, downlink frames can include downlink discovery frames, downlink configuration frames, downlink data frames, and downlink heartbeat frames; uplink frames can include uplink discovery response frames, uplink configuration response frames, and uplink data frames.

[0122] Figure 2 shows a schematic diagram of the distribution of the audio-visual system provided in this application embodiment in a vehicle. As shown in Figure 2, the audio-visual control device is connected to audio-visual devices 1 to 8 via a daisy-chain network. Audio-visual devices 1 and 3, 3 and 4, 4 and 7, 7 and 8, 8 and 6, 6 and 5, and 5 and 2 can be connected via an in-vehicle audio-visual bus. The audio and video control device may include the audio and video control device 110 shown in FIG1. ​​The audio and video devices 1 to 8 may include one or more of the audio and video devices 120, 130 and 140 shown in FIG1. ​​For example, audio and video device 1 may be the audio and video device 120 shown in FIG1, one or more of audio and video devices 3, 4, 7 and 8 may be the audio and video device 130 shown in FIG1, and one or more of audio and video devices 6, 5 and 2 may be the audio and video device 140 shown in FIG1.

[0123] For example, audio and video devices 1 to 8 may include, but are not limited to: a multimedia head unit, a speaker, a microphone (MIC), and an audio power amplifier (APM).

[0124] Figure 3 shows a functional schematic diagram of a vehicle provided in an embodiment of this application. As shown in Figure 3, the vehicle includes the audio-visual system 100 shown in Figure 1. When the audio-visual system 100 is installed in the vehicle, the audio-visual control device 110 can be installed in at least one of the following: cockpit domain controller (CDC); vehicle domain controller (VDC); and advanced driving domain controller (ADC), or mobile data center (MDC). The cockpit is comprised of several components: CDC (Cockpit Control Unit) and ICAS (Intelligent Cockpit Server). CDC is used to implement intelligent cockpit functions such as human-machine interaction. In practice, CDC may also be called other names, such as Media Graphics Unit (MGU), Intelligent Cockpit Server (ICAS3), or Cockpit Super Core (CSC). VDC (Vehicle Control Unit) is used to implement vehicle control functions. VDC can be seen as an integration of the powertrain domain, chassis domain, and body domain. In practice, VDC may also be called other names, such as Body Domain Controller (BDC), Vehicle Control Server (ICAS1), or Body Super Core (BSC). ADC (Action Control Unit) or MDC (Mechanical Control Unit) is used to implement perception, decision-making, and control functions related to intelligent driving. In practice, ADC or MDC may also be called other names, such as Special Equipment System (SAS), Intelligent Driving Server (ICAS2), or ADAS Super Core. ICAS stands for In-Car Application Server. Alternatively, the audio and video control device 110 can also be located in a central computing platform, for example, the central computing platform may include a vehicle central computer (VCC).

[0125] The main controller 111 and the main node 112 may each include one or more processors in the audio and video control device 110 shown in FIG3, such as processors 201 to 20n (n is a positive integer).

[0126] In other examples, the aforementioned main controller can be a vehicle infotainment system, and the peripheral device can be an audio system or microphone. Accordingly, the node connected to the main controller is the master node, and the node connected to the audio system or microphone is the slave node. The vehicle infotainment system establishes a communication connection with the audio system or microphone to achieve data interaction. Alternatively, the aforementioned main controller can also be a mobile phone, and the peripheral device can be a headset. Accordingly, the node connected to the control components within the mobile phone is the master node, and the node connected to the control components within the peripheral device is the slave node. The mobile phone and the headset establish a communication connection to achieve data interaction.

[0127] It should be understood that Figures 1 to 3 are merely illustrative examples. In actual implementation, the audio-visual system 100 may include more or fewer slave nodes, that is, the audio-visual system may include more or fewer audio-visual devices.

[0128] Figure 4 shows a schematic flowchart of the communication method provided in an embodiment of this application. This method 400 can be executed by the audio / video system 100 shown in Figure 1, or it can be applied to the audio / video system shown in Figure 2. Exemplarily, the master node can be the master node 112 in Figure 1, and the slave nodes 1 to 3 can be the slave nodes 122 to 142 in Figure 1, respectively. Specifically, this method 400 may include some or all of the steps in S401 to S414.

[0129] S401, the master node sends a downlink frame to slave node 1.

[0130] For example, the downlink frame can be a downlink frame used for data transmission.

[0131] In some implementations, the transmission frames (including downlink frames and uplink frames) involved in this application may include a synchronization field, a control field, and a data field. The synchronization field carries information for clock synchronization, the control field carries the transmission frame number, type, and related control information, and the data field carries relevant data to be sent to the slave or master node. In the following embodiments, unless otherwise specified, a downlink frame refers to the control field of the downlink frame, and an uplink frame refers to the control field of the uplink frame.

[0132] In some implementations, the downlink frame can be any of a discovery frame, a configuration frame, or a data frame. A discovery frame is used for discovering slave nodes, for example, the master node detecting a slave node and assigning it an identity (ID); a configuration frame is used to configure the slave node or its peripherals; and a data frame is used to transmit data to the slave node.

[0133] S402, a downlink frame is sent from node 1 to node 2.

[0134] In some implementations, node 1 can forward the downlink frames received in S401 to node 2, for example, it can forward one or more fields from the synchronization field, control field, and data field included in the downlink frames received in S401.

[0135] S403, Node 2 sends a downlink frame to Node 3.

[0136] In some implementations, node 2 can forward the downlink frame received in S402 to node 3, for example, it can forward at least one of one or more fields included in the downlink frame received in S402.

[0137] After receiving downlink frames, each slave node can send the data or information it wants to send to the master node back to the master node via uplink frames. If a slave node experiences an interruption, it can report the interruption information in the uplink frames transmitted to the master node.

[0138] For example, an uplink frame may also include a synchronization field, a control field, and a data field. The control field may include uplink frame control information and uplink frame interrupt information. The uplink frame control information is used by the slave node to respond to a downlink frame. For example, the uplink frame control information indicates whether the slave node has correctly received the control field information of a downlink frame, or it indicates relevant information about the slave node that initiated the uplink frame. The uplink frame interrupt information is used by the slave node to initiate an interrupt. In this application, the act of a slave node initiating an interrupt request through the uplink frame interrupt information in the uplink frame control field is called initiating an interrupt. The slave node that initiates the interrupt is called the interrupt-initiating slave node. The slave node initiating an interrupt should conform to the following rules:

[0139] 1) If the interrupt initiating slave node is also the uplink frame initiating slave node, then the interrupt is initiated at the same time as the uplink frame is initiated;

[0140] 2) If the interrupt initiating slave node is also the uplink frame response slave node, then the interrupt is initiated at the same time as the uplink frame response;

[0141] 3) If the interrupt initiating slave node is neither the uplink frame initiating slave node nor the uplink frame responding slave node, the interrupt initiating slave node should replace the uplink frame interrupt information part after receiving the uplink frame from the downstream port.

[0142] It is understandable that each slave node can initiate an uplink frame, and a slave node that experiences an interrupt can initiate an interrupt.

[0143] In implementation method one, each uplink frame includes at least field 1 (or identifier ID field) and field 2 (or interrupt ID field), as shown in Figure 5(a). Field 1 carries the identifier of the slave node that initiated the uplink frame, and field 2 carries the identifier of the slave node that initiated the interrupt. Field 1 is included in the uplink control information, and field 2 is included in the uplink interrupt information.

[0144] In implementation method two, in addition to the aforementioned fields 1 and 2, each uplink frame also includes an interrupt request field. The interrupt request field is used to indicate whether the information in field 2 is valid, as shown in Figure 5(b). For example, the interrupt request field can take the value "0" or "1". When the interrupt request field is "0", it means that the information in the interrupt ID field is invalid, that is, the slave node corresponding to the identifier carried by the interrupt ID field has not initiated an interrupt. When the interrupt request field is "1", it means that the information in the interrupt ID field is valid, that is, the slave node corresponding to the identifier carried by the interrupt ID field has initiated an interrupt.

[0145] In implementation method three, field 2 in each uplink frame may include subfield 1 and subfield 2. Subfield 1 and subfield 2 are respectively used to carry the identifier of a slave node that initiated the interrupt, as shown in Figure 5(e). In one example, subfield 1 is fixed to carry the identifier of the slave node that initiated the interrupt, while subfield 2 can be used to carry the identifier of the slave node that initiated the interrupt, or it can be used to carry specific uplink information. For example, the specific uplink information can be the uplink information of a specific slave node, such as the inter-integrated circuit (I2C) information reported by a specific slave node. Whether subfield 2 in the uplink frame is used to carry the identifier of the slave node that initiated the interrupt can be indicated by the master node through the downlink frame.

[0146] In some implementations, the interrupts involved in this application may include, but are not limited to: cable failure, bus error, master node related interrupt, GPIO interrupt, and mailbox interrupt. Each uplink frame may also include an interrupt type field, as shown in (c) and (d) of Figure 5, which indicates the type of interrupt initiated by the slave node as indicated by field 2.

[0147] To facilitate understanding of the aforementioned implementation methods one through three, the following description elaborates on each implementation method in conjunction with S404 through S413. Specifically, S404 through S406 and S410 through S411 can be considered as an elaboration of implementation method one, S404' through S406' can be considered as an elaboration of implementation method two, and S412 through S414 can be considered as an elaboration of implementation method three.

[0148] S404, Node 3 sends uplink frame 1 to Node 2.

[0149] In this context, slave node 3 is the initiating slave node of uplink frame 1. Therefore, field 1 (hereinafter referred to as the node ID field) in uplink frame 1 can carry the identifier of slave node 3. Furthermore, since slave node 3 did not experience an interruption, it does not need to initiate an interruption. Field 2 (hereinafter referred to as the interruption ID field) in uplink frame 1 can be the default value (or default), which indicates that no slave node initiated a report.

[0150] S405, Node 2 sends uplink frame 2 to Node 1.

[0151] Since no interruption occurred at node 2, node 2 does not need to change the information in the interrupt ID field of uplink frame 1.

[0152] In some implementations, slave node 2 can directly forward uplink frame 1 to slave node 1, that is, uplink frame 2 is the same as uplink frame 1, or uplink frame 2 and uplink frame 1 have the same control domain, or uplink frame 2 is a part of uplink frame 1.

[0153] In some other implementations, node 2 adds the data it wants to send to the master node to the data field of uplink frame 1 to obtain uplink frame 2.

[0154] S406, Node 1 sends uplink frame 3 to the master node.

[0155] Since an interruption occurred at node 1, and the interrupt ID field of uplink frame 2 is set to the default value, node 1 can add its own identifier to the interrupt ID field of uplink frame 2 to obtain uplink frame 3, and then send uplink frame 3.

[0156] In some implementations, uplink frame 1 and uplink frame 2 also include an interrupt type field. This interrupt type field carries information indicating the type of interrupt of slave node 1, and can also carry information indicating the reporting priority of the interrupt of slave node 1. Furthermore, the interrupt type field in uplink frame 1 and uplink frame 2 uses default values. Therefore, slave node 1, while adding its own identifier to the interrupt ID field of uplink frame 2, also adds an interrupt number indicating the interrupt type and / or information indicating the reporting priority of the interrupt to the interrupt type field of uplink frame 2, thus obtaining uplink frame 3, and then sending uplink frame 3.

[0157] S404', Node 3 sends uplink frame 1' to Node 2.

[0158] In this context, node 3 is the initiating slave node of uplink frame 1'. Therefore, the node ID field in uplink frame 1' can carry the identifier of slave node 3. Furthermore, since slave node 3 did not experience an interrupt, it does not need to initiate an interrupt, and the interrupt request field in uplink frame 1' takes the value "0". Additionally, the interrupt ID field in uplink frame 1' can be a default value, or it can carry the identifier of slave node 3 or another slave node.

[0159] S405', Node 2 sends uplink frame 2' to Node 1.

[0160] Since no interruption occurred at node 2, node 2 does not need to change the information in the interruption request field of uplink frame 1'.

[0161] In some implementations, slave node 2 can directly forward uplink frame 1' to slave node 1, that is, uplink frame 2' is the same as uplink frame 1', or uplink frame 2 and uplink frame 1 have the same control domain, or uplink frame 2' is a part of uplink frame 1'.

[0162] In some other implementations, node 2 adds the data it wants to send to the master node to the data field of uplink frame 1' to obtain uplink frame 2'.

[0163] In some other implementations, node 2 can add its own identifier to the interrupt ID field in uplink frame 1', or replace the identifier carried in the interrupt ID field of uplink frame 1' with its own identifier to obtain uplink frame 2'.

[0164] S406', Node 1 sends uplink frame 3' to the master node.

[0165] Since an interruption occurred at node 1, and the interruption indication field of uplink frame 2' is set to "0", node 1 can either add its own identifier to the interruption ID field of uplink frame 2', or replace the identifier in the interruption ID field of uplink frame 2' with its own identifier; and replace the value of the interruption indication field of uplink frame 2' with "1" to obtain uplink frame 3', and then send uplink frame 3'.

[0166] In some implementations, uplink frames 1' and 2' also include an interrupt type field. This interrupt type field carries information indicating the type of interrupt of slave node 1, and can also carry information indicating the reporting priority of the interrupt of slave node 1. Furthermore, the interrupt type field in uplink frames 1' and 2' uses default values. Therefore, slave node 1, while adding its own identifier to the interrupt ID field of uplink frame 2', also adds an interrupt number indicating the interrupt type and / or information indicating the reporting priority of the interrupt to the interrupt type field of uplink frame 2', resulting in uplink frame 3', which is then sent.

[0167] The specific implementations of S407 to S409 can be referred to the descriptions in S401 to S403 above, and will not be repeated here. For example, if slave node 1 and slave node 2 are interrupted during the execution of S407 to S409, then S410 to S411, or S412 to S414, can be executed.

[0168] S410, Node 2 sends uplink frame 4 to Node 1.

[0169] In this context, node 2 is the initiating slave node of uplink frame 4. Therefore, the node ID field in uplink frame 4 can carry the identifier of slave node 2. Furthermore, since slave node 2 experiences an interruption, it can initiate an interruption, meaning the interrupt ID field in uplink frame 4 can carry the identifier of slave node 2.

[0170] S411, Node 1 sends uplink frame 5 to the master node.

[0171] In some implementations, node 1 can directly forward uplink frame 4 to the master node, that is, uplink frame 5 is the same as uplink frame 4, or uplink frame 5 and uplink frame 4 have the same control domain, or uplink frame 5 is a part of uplink frame 4.

[0172] In some other implementations, node 1 adds the data it wants to send to the master node to the data field of uplink frame 4 to obtain uplink frame 5.

[0173] In some implementations, slave node 1 replaces the interrupt ID field of uplink frame 4 with the identifier of slave node 1 to obtain uplink frame 5, and sends uplink frame 5 to the master node.

[0174] In some implementations, uplink frame 4 also includes an interrupt type field. This interrupt type field carries information indicating the type of interrupt occurring in slave node 2, as well as information indicating the reporting priority of the interrupt occurring in slave node 2. If slave node 1 determines that the reporting priority of the interrupt occurring in slave node 2 is higher than or equal to its own interrupt reporting priority, it directly forwards uplink frame 4 to the master node. If slave node 1 determines that the reporting priority of the interrupt occurring in slave node 2 is lower than its own interrupt reporting priority, then slave node 1 replaces the interrupt ID field of uplink frame 4 with its own identifier, and replaces the interrupt type field of uplink frame 4 with the interrupt number corresponding to the interrupt type of slave node 1, as well as information indicating the reporting priority of the interrupt of slave node 1, thus obtaining uplink frame 5, which is then sent.

[0175] S412, Node 3 sends uplink frame 6 to Node 2.

[0176] Since Node 3 is the initiating slave node of uplink frame 6, the Node ID field in uplink frame 6 can carry the identifier of slave node 3. Furthermore, since slave node 3 did not experience an interruption, it does not need to initiate an interruption. The Interrupt ID1 and Interrupt ID2 fields in uplink frame 6 can be set to default values, indicating that no slave node initiated the reporting.

[0177] S413, Node 2 sends uplink frame 7 to Node 1.

[0178] For example, node 2 adds its own identifier to an interrupt ID field (e.g., interrupt ID1 field) in uplink frame 6 to obtain uplink frame 7, indicating that an interrupt has occurred in node 2.

[0179] S414, Node 1 sends uplink frame 8 to the master node.

[0180] For example, slave node 1 adds its own identifier to the remaining interrupt ID field (e.g., interrupt ID2 field) of uplink frame 7 to obtain uplink frame 8, indicating that both slave node 1 and slave node 2 have experienced interruptions.

[0181] In some implementations, the uplink frame control information included in this method 400 further includes a frame number and a frame type. The frame number indicates the sequence of the uplink frames, incrementing cyclically from 0 for each frame. The frame type indicates whether the uplink frame is a configuration frame, a data frame, or a discovery frame. When an uplink frame is initiated in response to a downlink frame, the frame number and frame type are the same as the frame number and frame type of the responding downlink frame.

[0182] In some implementations, the uplink frame also includes a frame acknowledgment field, which indicates whether the slave node has correctly received the information in the control field of the downlink frame. A frame acknowledgment value of 0 indicates that the information in the control field of the downlink frame has not been correctly received, while a value of 1 indicates that the information in the control field of the downlink frame has been correctly received. When the uplink frame is not used to respond to the downlink frame, the value of the frame acknowledgment field is configured to 0. For example, when the slave node determines that the verification has passed based on the verification information corresponding to the information in the control field, the slave node can determine that it has correctly obtained the information in the control field.

[0183] More specifically, Figure 6 shows another schematic diagram of an uplink frame provided in an embodiment of this application. As shown in Figure 6, the uplink frame includes 8 bytes. Specifically, the first byte is used to carry the frame number (4 bits) and frame type (3 bits). The second byte is used to carry the slave node identifier (6 bits) and frame acknowledgment information (1 bit), where the slave node identifier is the identifier of the slave node that initiated the uplink frame. The third byte is a reserved byte, or the third byte is used to carry data requested by the master node. The fourth and fifth bytes are used to carry verification information that verifies the first three bytes. The sixth byte is used to carry the identifier (6 bits) of the slave node that initiated the interrupt and interrupt request information (1 bit). The seventh byte is used to carry interrupt type information, and the eighth byte is used to carry verification information, which is used to verify the information in the sixth and seventh bytes. For example, the aforementioned verification information can be cyclic redundancy check (CRC) information, etc.

[0184] For example, in the 8-byte frame structure shown in Figure 6, the first 5 bytes can be regarded as the aforementioned uplink frame control information, and the last 3 bytes can be regarded as the aforementioned uplink frame interruption information.

[0185] In some implementations, the frame structure of the downlink frame involved in this application embodiment can be as shown in Figure 7, where the downlink frame includes 8 bytes. Specifically,

[0186] The downlink frame shown in Figure 7(a) is a downlink discovery frame. The first byte carries the frame number (4 bits) and frame type (3 bits), where the frame type can be a discovery frame, configuration frame, or data frame. The second byte carries the slave node identifier (6 bits), which can be an identifier assigned to the slave node or an identifier already assigned to it. The third byte carries the uplink frame response time, used by the slave node to calculate the time to initiate the uplink frame. The fifth and sixth bytes carry verification information to check the contents of the first three bytes. The last bit of the seventh byte is the frame validity field, carrying information indicating whether the discovery frame is valid. The eighth byte carries verification information to check the information in the sixth and seventh bytes. For example, the aforementioned verification information can be CRC information, etc.

[0187] The downlink frames shown in Figures 7(b) to (e) are downlink configuration frames. In Figure 7(b), the first byte carries the frame number (4 bits), frame type (3 bits), and operation object (1 bit). The operation object field indicates whether data is being written to the slave node's register or to the register of a peripheral connected to the slave node. The second byte carries the slave node identifier (6 bits). The third byte includes a mode field (1 bit), a read field (1 bit), and a write field (1 bit). The mode field indicates the number of bytes of data carried in the transmission frame; a read field value of 0 indicates an invalid read operation, and a read field value of 1 indicates a valid read operation. Similarly, a write field value of 0 indicates an invalid write operation, and a write field value of 1 indicates a valid write operation. The fourth byte carries the register address. The fifth byte carries the data written to the operation object. The sixth byte carries a state transition timer. The information in the state transition timer field is used to notify the slave node of state changes, such as notifying the slave node to transition from the initialization state to the data transmission state, or notifying the slave node to transition from the data transmission state to the sleep state. The seventh and eighth bytes are used to carry verification information. The difference between Figure 7(c) and Figure 7(b) is that the sixth byte is used to carry data written to the target device. The difference between Figure 7(d) and Figure 7(b) is that the first three bits of the fourth byte are used to carry I2C communication status indication information, which indicates the target status of the I2C communication between node n and peripheral m. The difference between Figure 7(e) and Figure 7(d) is that the sixth byte is used to carry data written to the target device.

[0188] In some implementations, the aforementioned interrupt types are represented by interrupt numbers, ranging from 0 to 255, as shown in Table 1 below. More specifically, the mailbox is used to store the communication status and related configuration information between slave nodes, or the mailbox is used to store the communication status and related configuration information between master nodes. Furthermore, GPIO includes eight pins, which can be GPIO0 to GPIO7, so GPIO interrupts can be refined into one or more interrupts from GPIO0 to GPIO7.

[0189] Table 1

[0190] The specific interrupt types corresponding to each interrupt number in Table 1 are shown in Table 2 below.

[0191] Table 2

[0192] It should be noted that the aforementioned interrupt numbers marked "reserved" can be understood as undefined numbers, for example, they could be used to indicate other interrupt types; interrupt numbers marked "user-defined" mean that for interrupt numbers 64 to 255, the user defines the corresponding interrupt type. The cables mentioned in Table 2 refer to communication cables between slave nodes, including positive and negative signal lines. The interrupts corresponding to interrupt numbers "16", "19", and "21" may be caused by a short circuit between the positive cable and the battery positive terminal or a short circuit between the negative cable and ground, degrading the bus signal quality. The master node can send a discovery frame to further locate the fault. To facilitate understanding of the interrupts caused by cable faults involved in this application, the cable faults are explained in detail below with reference to Figure 8. Slave node n and slave node n+1 shown in Figure 8 are the two nearest neighbor slave nodes, meaning there are no other slave nodes between these two slave nodes.

[0193] It should also be noted that in Table 2 above, P generally refers to the positive terminal, and N generally refers to the negative terminal. In BP or BN, B generally refers to the port connected to the downstream slave node; BP generally refers to the positive terminal (or positive signal line) connected to the downstream slave node, and BP generally refers to the negative terminal (or negative signal line) connected to the downstream slave node. Furthermore, interruption types can also include line faults related to the cable's A, AN, or AP terminals. The A terminal generally refers to the port connected to the upstream slave node, AP generally refers to the positive terminal connected to the upstream slave node, and AN generally refers to the negative terminal connected to the upstream slave node.

[0194] Upstream and downstream slave nodes can be understood as follows: in the downlink transmission direction, the node closer to the master node is considered an upstream slave node (e.g., slave node 122 in Figure 1), and the node farther from the master node is considered a downstream slave node (e.g., slave node 132 in Figure 1). It's important to understand that upstream and downstream slave nodes are relative concepts. For example, in Figure 1, slave node 132 can be understood as a downstream slave node of slave node 122, or as an upstream slave node of slave node 142. An upstream slave node of a slave node can also be called an uplink slave node of that slave node, and a downstream slave node of a slave node can also be called a downlink slave node of that slave node.

[0195] As shown in Figure 8(a), when the BN line and / or BP line between slave node n and slave node n+1 are open, the master node and slave node n can still communicate normally, but the communication between slave node n and slave node n+1 and the downlink of slave node n+1 is interrupted. In this case, slave node n can report the interruption number "3" in Report 2 to indicate that a related interruption has occurred.

[0196] As shown in Figure 8(b), in the case of a short circuit between the BN line and the BP line between slave node n and slave node n+1, the master node and slave node n can still communicate normally, but the communication between slave node n and slave node n+1 and the downlink of slave node n+1 is interrupted. In this case, slave node n can report the interruption number "2" in Report 2 to indicate that a related interruption has occurred.

[0197] As shown in Figure 8(c), bus communication stops when there is a short circuit between slave node n and slave node n+1, and between the BP line and the ground line. The bus includes the communication cables between the master and slave nodes, and the communication cables between slave nodes. That is, the aforementioned interrupt type field will not carry the interrupt number "0".

[0198] As shown in Figure 8(d), the bus can still communicate normally when the BN line and ground line between slave node n and slave node n+1 are short-circuited, but the location of the short circuit cannot be directly determined. In this case, any slave node can indicate the bus interruption by entering the interrupt number "6" in Report 2.

[0199] As shown in Figure 8(e), the bus can still communicate normally when the BP line and VBAT line between slave node n and slave node n+1 are short-circuited, but the location of the short circuit cannot be directly determined. In this case, any slave node can indicate the bus interruption by entering the interrupt number "7" in Report 2.

[0200] As shown in Figure 8(f), bus communication stops when there is a short circuit between slave node n and slave node n+1 and between the BN line and the VBAT line.

[0201] When a slave node experiences an interrupt, the corresponding bit in the register connected to the slave node, corresponding to the interrupt type, can be configured to 1 according to the interrupt type. After the master node receives an uplink frame, it can determine whether a slave node initiated an interrupt based on the interrupt ID field and / or the interrupt request field. Once it is determined that a slave node initiated an interrupt, and the master node clears the relevant interrupt, the master node can indicate to the slave node that the interrupt has been cleared or that there is no interrupt by writing data to the aforementioned relevant registers. For example, the aforementioned registers may include multiple interrupt pending flag registers. For instance, the multiple interrupt pending flag registers involved in this application can be as shown in Tables 3 to 8 below, where the meaning of each bit in the register is shown in the second column of each table.

[0202] Table 3 Interrupt Suspension Flag Register 1

[0203] Among them, cable fault interruptions 0 to 7 correspond one-to-one with interruption numbers 0 to 7 in Table 2.

[0204] Table 4 Interrupt Suspended Flag Register 2

[0205] Table 5 Interrupt Suspended Flag Register 3

[0206] Table 6 Interrupt Pending Flags Register 4

[0207] Table 7 Interrupt Pending Flags Register 4

[0208] Table 8 Interrupt Pending Flags Register 6

[0209] For example, in the absence of an interrupt, all bits of all interrupt pending registers associated with slave node n are 0. Taking the BN line and / or BP line between slave node n and slave node n+1 as an example, slave node n can report an interrupt with interrupt number "3". Furthermore, slave node n can configure register bit [3] of interrupt pending flag register 1 to 1. Further, when interrupt number "3" is cleared, the master node writes "1" to register bit [3] of interrupt pending flag register 1 to clear register bit [3]. For other interrupt types, the actions performed by the master node and slave node n on the interrupt pending register can be referred to the above description, and will not be repeated here.

[0210] In some implementations, when the master node determines that the interrupt number is "5", "6" or "7", the master node starts the diagnostic mode to locate the specific location where the interrupt occurred; when the master node determines that the interrupt number is "32", the master node determines that the discovery of the slave node that initiated the uplink frame indicated by the uplink frame has been completed, and can continue the discovery of downlink slave nodes of that slave node; when the master node determines that the interrupt number is any other interrupt number in Table 2 other than "5", "6", "7" and "32", the master node determines the location and type of the interrupt based on the interrupt number.

[0211] In some implementations, the slave node should have a mute function when in data transmission mode. If the slave node outputs audio or video, and detects a communication bus input interrupt or other interrupt, it should mute the audio or video before outputting it to the peripheral device to avoid howling or other interruption sounds. If the slave node is in sleep mode, it can mute the audio or video before outputting it to the peripheral device.

[0212] Figure 9 shows another schematic flowchart of the communication method provided in this application embodiment. This method 800 can be executed by the audio / video system 100 shown in Figure 1, or it can also be applied to the audio / video system shown in Figure 2. Exemplarily, the master node can be the master node 112 in Figure 1, and the first slave node can be any one of slave nodes 122 to 142 in Figure 1. The first slave node can be a slave node connected to the master node, or one or more slave nodes can be connected between the first slave node and the master node. The method 800 includes:

[0213] S801, the first slave node determines the first uplink frame. The first uplink frame includes a slave node identifier and first interrupted slave node information. The slave node identifier indicates the slave node that initiated the first uplink frame, and the first interrupted slave node information indicates that the first slave node has experienced a first interruption.

[0214] As an example, when the first slave node experiences an interrupt, the interruption can be reflected through the values ​​of its registers. Specifically, the interrupt status register (register address 0x28) indicates whether an interrupt has occurred in the associated master or slave node; the interrupt source register (register address 0x29) indicates the node number of the current interrupt and identifies whether the interrupt source is a master or slave node; and the interrupt type register (register address 0x2A) indicates the type of interrupt that has occurred, which conforms to the relevant interrupt type definitions in Tables 1 and 2. Specifically, the values ​​of register bits [7:0] correspond one-to-one with the interrupt numbers in Table 2. For example, a value of 00000000 indicates an interrupt corresponding to interrupt number "0"; another example is a value of 00000011, indicating an interrupt corresponding to interrupt number "3". The meanings of the values ​​of each bit in the interrupt status register, interrupt source register, and interrupt type register are shown in Tables 9 to 11, respectively.

[0215] For example, "the first slave node has experienced the first interrupt" can be represented as follows: the register bit [0] corresponding to the interrupt status register (register address 0x28) associated with the first slave node is set to 1 by the internal implementation of the first slave node; in addition, through the uplink frame interrupt information reporting, the master node obtains the interrupt status of the first slave node and sets the register bit [5:0] corresponding to the interrupt source register (register address 0x29) associated with the master node to the identifier of the first slave node, sets register bit [6] to 1, sets register bit [7] to 0, and sets the register bit [7:0] corresponding to the interrupt type register (register address 0x2A) associated with the master node to the interrupt type information in the uplink frame, which is used by the master controller to determine the interrupt status of the master node and slave node on the current high speed media transmission (HSMT) bus.

[0216] Table 9

[0217] Table 10

[0218] Table 11

[0219] For example, the slave node identifier may include the information carried by field 1 (i.e., the node ID field) in the foregoing embodiments, and the first interrupt slave node information may include the information carried by field 2 (i.e., the interrupt ID field) in the foregoing embodiments, or the information carried by a subfield of field 2 (such as subfield 1 or subfield 2) in the foregoing embodiments.

[0220] In some implementations, the first interrupt slave node information includes the identifier of the first slave node, and the first uplink frame also includes information indicating the type of the first interrupt, which includes any of the following: cable fault, bus error, master node related interrupt, GPIO interrupt, or mailbox interrupt.

[0221] For example, the information indicating the type of the first interrupt may include the information carried by the interrupt type field in the foregoing embodiments.

[0222] In one example, if the first slave node is the slave node that initiates the uplink frame, then the slave node identifier is the identifier of the first slave node. For example, if the first slave node is slave node 2 in method 400, then the first uplink frame can be uplink frame 4 in method 400.

[0223] In another example, if the first slave node is not the slave node that initiated the uplink frame, then the slave node identifier is the identifier of the slave node that initiated the uplink frame. For example, if the first slave node is slave node 2 in method 400, then the first uplink frame can be uplink frame 7 in method 400. As another example, if the first slave node is slave node 1 in method 400, then the first uplink frame can be uplink frame 3, uplink frame 3', or uplink frame 8 in method 400.

[0224] In conjunction with the latter example above, in some implementations, the method 800 further includes: receiving a second uplink frame, the second uplink frame including a slave node identifier and second interrupted slave node information, the second interrupted slave node information being used to indicate information about the slave node that experienced the interruption; and executing S802 when the corresponding value of the second interrupted slave node information is a default value.

[0225] Specifically, when the corresponding value of the second interrupt slave node information is the default value, the first slave node adds the identifier of the first slave node as the corresponding value of the second interrupt slave node information to obtain the first uplink frame. For example, if the second uplink frame is uplink frame 2 in method 400, then the second interrupt slave node information is the default value in the interrupt ID field.

[0226] In some implementations, the second uplink frame also includes interrupt request information, which indicates whether the second interrupt slave node information is valid or invalid. Furthermore, if the interrupt request information indicates that the second interrupt slave node information is invalid, step S802 is executed.

[0227] Specifically, when the interrupt request information in the second uplink frame indicates that the second interrupt slave node information is invalid, the first slave node replaces the corresponding value of the second interrupt slave node information with its own identifier and replaces the corresponding value of the interrupt request information with a valid value, thus obtaining the first uplink frame. In other words, the first uplink frame also includes interrupt request information, which indicates that the first interrupt slave node information is valid. For example, if the second uplink frame is uplink frame 2' in method 400, then the second interrupt slave node information is the corresponding value of the interrupt ID field in uplink frame 2', and the interrupt request information has a value of "0" in the interrupt request field. Correspondingly, the interrupt request information in the first uplink frame (such as uplink frame 3') has a value of "1" in the interrupt request field.

[0228] In conjunction with the latter example above, in some implementations, the method 800 further includes: receiving a second uplink frame, the second uplink frame including a slave node identifier, a third interrupt slave node information and priority information, the third interrupt slave node information indicating that a second interrupt has occurred in the second slave node, and the priority information indicating the reporting priority of the second interrupt; then, when the reporting priority of the second interrupt is lower than the reporting priority of the first interrupt, S802 is executed.

[0229] Specifically, when the reporting priority of the second interrupt is lower than that of the first interrupt, the corresponding value of the third interrupt slave node information is replaced with the identifier of the first slave node, and the corresponding value of the priority information is replaced with the reporting priority of the first interrupt to obtain the first uplink frame. For example, the priority information can be the information carried by the interrupt type field in method 400.

[0230] In some implementations, the first uplink frame also includes information about a fourth interrupt slave node. The corresponding value of the fourth interrupt slave node information is a default value, or the corresponding value of the fourth interrupt slave node information is the identifier of the third slave node, or the fourth interrupt slave node information includes uplink data. For example, the first uplink frame can be uplink frame 8 in method 400, the first interrupt slave node information can be the information carried in the interrupt ID2 field, and the fourth interrupt slave node information can be the information carried in the interrupt ID1 field.

[0231] In conjunction with the latter example above, in some implementations, the method 800 further includes: receiving a fourth uplink frame, the fourth uplink frame including fifth interrupt slave node information and sixth interrupt slave node information, the fifth interrupt slave node information and the first interrupt slave node information being associated with the same field, and the sixth interrupt slave node information and the fourth interrupt slave node information being associated with the same field; sending a first uplink frame, including: executing S802 when the corresponding value of the fifth interrupt slave node information is a default value.

[0232] Specifically, when the corresponding value of the fifth interrupt slave node information is the default value, the identifier of the first slave node is added as the corresponding value of the fifth interrupt slave node information to obtain the first uplink frame. For example, if the fourth uplink frame is uplink frame 7 in method 400, then the fifth interrupt slave node information and the sixth interrupt slave node information are the information carried by the interrupt ID2 field and the interrupt ID1 field, respectively.

[0233] In some implementations, if the aforementioned second or fourth uplink frame is sent by a slave node (such as a fifth slave node) of the downlink of the first slave node, then if the second or fourth uplink frame is initiated by the fifth slave node, the slave node identifier in the second or fourth uplink frame is the identifier of the fifth slave node.

[0234] S802, the first slave node sends the first uplink frame.

[0235] In some implementations, there are no other slave nodes between the first slave node and the master node, then S802 is: the first slave node sends the first uplink frame to the master node.

[0236] In some implementations, a fourth slave node is also included between the first slave node and the master node, and S802 is: the first slave node sends a first uplink frame to the fourth slave node. Further, if the fourth slave node does not need to initiate an interrupt, the fourth slave node receives the first uplink frame and sends the first uplink frame, for example, the fourth slave node sends the first uplink frame to the master node.

[0237] S803, the master node determines the first slave node to initiate an interrupt based on the first uplink frame.

[0238] In some implementations, after S803, the method further includes: the master node writes first information to the register of the type of the first interrupt corresponding to the first slave node, according to the type of the first interrupt, to indicate that the first slave node has no first interrupt.

[0239] For example, the register can be the interrupt suspension flag register in the aforementioned embodiment. Taking the first interrupt as interrupt number "3" as an example, the first information can be "1" written to the register bit [3] of the aforementioned interrupt suspension flag register 1. For more specific implementation, please refer to the description of the corresponding parts of Tables 3 to 8 above, which will not be repeated here.

[0240] In some implementations, the master node performs fault diagnosis and / or fault location based on the type of the first interrupt.

[0241] In some implementations, bus errors include interruptions caused by bus signal quality. The master node performs fault diagnosis and / or fault location based on the type of the first interrupt, including: when the type of the first interrupt is an interrupt caused by bus signal quality, the master node sends a second downlink frame, which is used for fault location.

[0242] The communication method provided in this application allows the first slave node to report interruption-related information to the master node in an uplink frame initiated by another slave node when an interruption occurs. Alternatively, the first slave node can also report interruption-related information in its own uplink frame. This increases the chances of the slave node reporting the interruption, thereby improving the speed at which the slave node reports interruption information. Furthermore, when the first slave node reports interruption-related information to the master node in an uplink frame initiated by another slave node, the information indicating the slave node that initiated the uplink frame (i.e., the slave node identifier) ​​is not changed. This ensures that the interruption reporting does not affect the transmission control information of the slave node that initiated the uplink frame, and also helps to save signaling overhead during the interruption reporting process.

[0243] This application embodiment also provides a data transmission structure for information transmission between a master node and a slave node in an audio-visual system. The data transmission structure includes a first field and a second field. The first field is used to carry a slave node identifier, and the second field is used to carry interrupted slave node information. The slave node identifier indicates the slave node that initiated the data transmission structure, and the interrupted slave node information indicates the slave node that initiated the interruption.

[0244] For example, the first field can be the node ID field in the aforementioned embodiments, such as the field corresponding to the first 6 bits of the second byte in Figure 6; the second field can be the interrupt ID field in the aforementioned embodiments, such as the field corresponding to the first 6 bits of the sixth byte in Figure 6.

[0245] In some implementations, the data transmission structure also includes a third field, which carries information indicating the type of interrupt. The interrupt type includes any of the following: cable failure, bus error, master node-related interrupt, GPIO interrupt, or mailbox interrupt.

[0246] For example, the third field can be the interrupt type field in the aforementioned embodiments, such as the field corresponding to the seventh byte in Figure 6.

[0247] In some implementations, the data transmission structure also includes a fourth field, which carries information indicating the reporting priority of the interrupt.

[0248] For example, the fourth field and the third field can be the same field, as shown in Figure 6, which corresponds to the seventh byte.

[0249] In some implementations, the fourth field also carries information indicating the level of the interruption, which indicates whether the interruption is in a normal or urgent state.

[0250] In some implementations, the data transmission structure also includes a fifth field, which carries interruption request information indicating whether the corresponding value of the second field is valid.

[0251] For example, the fifth field can be the interruption request field in the aforementioned embodiments, such as the field corresponding to the 7th bit of the sixth byte in Figure 6.

[0252] In some implementations, the data transmission structure also includes a sixth field, which carries information about the type of the data transmission structure, including any of the following: discovery frame, configuration frame, or data frame.

[0253] For example, the sixth field can be the frame type field in the foregoing embodiments, such as the field corresponding to the 5th to 7th bits of the first byte in Figure 6.

[0254] In some implementations, the data transmission structure includes a first part and a second part, wherein the first part is verified using first verification information, and the second part is verified using second verification information; a first field is contained in the first part, and a second field is contained in the second part. For example, the first part can be the aforementioned uplink frame control information, and the second part can be the aforementioned uplink frame interrupt information. Further, the first verification information can be the verification information carried by the fourth and fifth bytes as shown in Figure 6, and the second verification information can be the verification information carried by the eighth byte.

[0255] In some implementations, the first part also includes a sixth field, and the second part includes a third, fourth, and fifth field.

[0256] It is understood that the aforementioned data transmission structure can be the uplink frame in the aforementioned embodiments.

[0257] The communication method and the frame structure of the transmission frames involved in the communication process have been described in detail above. In the various embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be referenced mutually. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0258] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 1 to 9. The apparatus provided by the embodiments of this application will now be described in detail with reference to Figures 10 and 11. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0259] Figure 10 shows a schematic block diagram of a communication device 2000 provided in an embodiment of this application. The device 2000 may include units for executing the methods described in the foregoing embodiments. Furthermore, each unit in the device 2000 implements a corresponding process of the above method embodiments. The device 2000 includes a transceiver unit 2010, which can be used to implement corresponding data acquisition or transmission / reception functions. The device 2000 also includes a processing unit 2020, which can be used to implement corresponding processing functions.

[0260] Optionally, the device 2000 further includes a storage unit, which can be used to store instructions and / or data. The processing unit 2020 can read the instructions and / or data in the storage unit so that the device can perform the relevant actions in the aforementioned method embodiments.

[0261] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0262] It should also be understood that the device 2000 described herein is embodied in the form of a functional unit. The terms “module” or “unit” may refer to application-specific ASICs, electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memory for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components that support the described functions.

[0263] The apparatus in this embodiment has the function of implementing the corresponding steps in the aforementioned method. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit 2010 can be replaced by a transceiver, and other units, such as the processing unit, can be replaced by a processor, used to execute the relevant processing operations in each method embodiment.

[0264] For example, when the device 2000 is used to perform the steps performed by the slave node, the transceiver unit 2010 and the processing unit 2020 can be chips or circuits in the slave node; when the device 2000 is used to perform the steps performed by the master node, the transceiver unit 2010 and the processing unit 2020 can be chips or circuits in the master node.

[0265] In the specific implementation process, the units in the above devices can be fully or partially integrated together, or they can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SoC).

[0266] Figure 11 is another schematic block diagram of the communication device provided in an embodiment of this application. The device 2100 shown in Figure 11 may include a processor 2110, a transceiver 2120, and a memory 2130. The processor 2110, transceiver 2120, and memory 2130 are connected via internal connection paths. The memory 2130 is used to store instructions, and the processor 2110 is used to execute the instructions stored in the memory 2130 to implement the methods in the above embodiments. Optionally, the memory 2130 may be coupled to the processor 2110 via an interface or integrated with the processor 2110.

[0267] It should be noted that the transceiver 2120 mentioned above may include, but is not limited to, transceiver devices such as input / output interfaces, to realize communication between device 2100 and other devices or communication networks.

[0268] Memory 2130 can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes various forms such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0269] Transceiver 2120 uses transceiver devices, such as but not limited to transceivers, to enable communication between device 2100 and other devices or communication networks to receive / send data / information for implementing the methods in the above embodiments.

[0270] This application also provides an audio-visual system, which includes the device 2000 or device 2100 in the above embodiments.

[0271] This application also provides a vehicle that includes the audio-visual system described in the foregoing embodiments.

[0272] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to implement the methods described in the above embodiments of this application.

[0273] This application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to implement the methods described in the above embodiments of this application.

[0274] This application also provides a chip, including circuitry, for performing the methods described in the above embodiments of this application.

[0275] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0276] In the description of the embodiments of this application, unless otherwise stated, " / " means "or", for example, A / B can mean A or B; "and / or" in this document describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. In this application, "at least one" means one or more, and "more" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0277] The use of prefixes such as "first" and "second" in this application embodiment is solely for distinguishing different descriptive objects and does not limit the position, order, priority, quantity, or content of the described objects. The use of ordinal numbers and other prefixes to distinguish descriptive objects in this application embodiment does not constitute a limitation on the described objects. The description of the described objects is found in the claims or the context of the embodiments, and the use of such prefixes should not constitute unnecessary restrictions.

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

[0279] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions between the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0280] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0281] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0282] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations 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. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to the first slave node where the first interrupt occurs, the method includes: A first uplink frame is determined. The first uplink frame includes a slave node identifier and first interrupted slave node information. The slave node identifier indicates the slave node that initiated the first uplink frame, and the first interrupted slave node information indicates that the first slave node has experienced the first interruption. Send the first uplink frame.

2. The method according to claim 1, characterized in that, The first interrupt slave node information includes the identifier of the first slave node, and the first uplink frame also includes information indicating the type of the first interrupt. The type of the first interrupt includes any of the following: cable fault, bus error, master node related interrupt, general purpose input / output (GPIO) interrupt, or mailbox interrupt.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receive a second uplink frame, the second uplink frame including the slave node identifier and the second interrupted slave node information, the second interrupted slave node information being used to indicate the information of the slave node that has been interrupted; Sending the first uplink frame includes: When the corresponding value of the second interrupt slave node information is the default value, the first uplink frame is sent.

4. The method according to claim 3, characterized in that, The first interrupt slave node information and the second interrupt slave node information are associated with the same field. Determining the first uplink frame includes: When the corresponding value of the second interrupt slave node information is the default value, the identifier of the first slave node is added as the corresponding value of the second interrupt slave node information to obtain the first uplink frame.

5. The method according to claim 1 or 2, characterized in that, The method further includes: Receive a second uplink frame, the second uplink frame including the slave node identifier, the third interrupt slave node information and priority information, the third interrupt slave node information indicating that the second slave node has experienced a second interrupt, and the priority information indicating the reporting priority of the second interrupt; Sending the first uplink frame includes: When the reporting priority of the second interrupt is lower than that of the first interrupt, the first uplink frame is sent.

6. The method according to claim 5, characterized in that, The first interrupt slave node information and the third interrupt slave node information are associated with the same field. Determining the first uplink frame includes: When the reporting priority of the second interrupt is lower than that of the first interrupt, the corresponding value of the third interrupt slave node information is replaced by the identifier of the first slave node, and the corresponding value of the priority information is replaced by the reporting priority of the first interrupt to obtain the first uplink frame.

7. The method according to any one of claims 1 to 6, characterized in that, The first uplink frame also includes interrupt request information, which indicates that the first interrupt slave node information is valid.

8. The method according to claim 1 or 2, characterized in that, When the first uplink frame is initiated by the first slave node, the slave node identifier is the identifier of the first slave node.

9. The method according to any one of claims 1 to 8, characterized in that, The first uplink frame also includes fourth interrupt slave node information, wherein the corresponding value of the fourth interrupt slave node information is a default value, or the corresponding value of the fourth interrupt slave node information is the identifier of the third slave node, or the fourth interrupt slave node information includes uplink data.

10. The method according to claim 9, characterized in that, The method further includes: Receive a fourth uplink frame, the fourth uplink frame including fifth interrupt slave node information and sixth interrupt slave node information, the fifth interrupt slave node information and the first interrupt slave node information are associated with the same field, the sixth interrupt slave node information and the fourth interrupt slave node information are associated with the same field; Sending the first uplink frame includes: When the corresponding value of the fifth interrupt slave node information is the default value, the first uplink frame is sent.

11. The method according to claim 10, characterized in that, Determining the first uplink frame includes: When the corresponding value of the fifth interrupt slave node information is the default value, the identifier of the first slave node is added as the corresponding value of the fifth interrupt slave node information to obtain the first uplink frame.

12. The method according to any one of claims 9 to 11, characterized in that, The method further includes: A first downlink frame is received, the first downlink frame including indication information, the indication information indicating whether the field associated with the fourth interrupt slave node information is used to carry the identifier of the slave node that initiated the interrupt.

13. A communication device, characterized in that, The device, located at the first slave node where the first interrupt occurs, includes: The processing unit is configured to determine a first uplink frame, the first uplink frame including a slave node identifier and first interrupted slave node information, the slave node identifier indicating the slave node that initiated the first uplink frame, and the first interrupted slave node information indicating that the first slave node has experienced the first interruption; The transceiver unit is used to send the first uplink frame.

14. The apparatus according to claim 13, characterized in that, The first interrupt slave node information includes the identifier of the first slave node, and the first uplink frame also includes information indicating the type of the first interrupt. The type of the first interrupt includes any of the following: cable fault, bus error, master node related interrupt, general purpose input / output (GPIO) interrupt, or mailbox interrupt.

15. The apparatus according to claim 13 or 14, characterized in that, The transceiver unit is also used for: Receive a second uplink frame, the second uplink frame including the slave node identifier and the second interrupted slave node information, the second interrupted slave node information being used to indicate the information of the slave node that has been interrupted; When the corresponding value of the second interrupt slave node information is the default value, the first uplink frame is sent.

16. The apparatus according to claim 15, characterized in that, The first interrupt slave node information and the second interrupt slave node information are associated with the same field, and the processing unit is used to: When the corresponding value of the second interrupt slave node information is the default value, the identifier of the first slave node is added as the corresponding value of the second interrupt slave node information to obtain the first uplink frame.

17. The apparatus according to claim 13 or 14, characterized in that, The transceiver unit is also used for: Receive a second uplink frame, the second uplink frame including the slave node identifier, the third interrupt slave node information and priority information, the third interrupt slave node information indicating that the second slave node has experienced a second interrupt, and the priority information indicating the reporting priority of the second interrupt; When the reporting priority of the second interrupt is lower than that of the first interrupt, the first uplink frame is sent.

18. The apparatus according to claim 17, characterized in that, The first interrupt slave node information and the third interrupt slave node information are associated with the same field, and the processing unit is used to: When the reporting priority of the second interrupt is lower than that of the first interrupt, the corresponding value of the third interrupt slave node information is replaced by the identifier of the first slave node, and the corresponding value of the priority information is replaced by the reporting priority of the first interrupt to obtain the first uplink frame.

19. The apparatus according to any one of claims 13 to 18, characterized in that, The first uplink frame also includes interrupt request information, which indicates that the first interrupt slave node information is valid.

20. The apparatus according to claim 13 or 14, characterized in that, When the first uplink frame is initiated by the first slave node, the slave node identifier is the identifier of the first slave node.

21. The apparatus according to any one of claims 13 to 20, characterized in that, The first uplink frame also includes fourth interrupt slave node information, wherein the corresponding value of the fourth interrupt slave node information is a default value, or the corresponding value of the fourth interrupt slave node information is the identifier of the third slave node, or the fourth interrupt slave node information includes uplink data.

22. The apparatus according to claim 21, characterized in that, The transceiver unit is also used for: Receive a fourth uplink frame, the fourth uplink frame including fifth interrupt slave node information and sixth interrupt slave node information, the fifth interrupt slave node information and the first interrupt slave node information are associated with the same field, the sixth interrupt slave node information and the fourth interrupt slave node information are associated with the same field; When the corresponding value of the fifth interrupt slave node information is the default value, the first uplink frame is sent.

23. The apparatus according to claim 22, characterized in that, The processing unit is used for: When the corresponding value of the fifth interrupt slave node information is the default value, the identifier of the first slave node is added as the corresponding value of the fifth interrupt slave node information to obtain the first uplink frame.

24. The apparatus according to any one of claims 21 to 23, characterized in that, The transceiver unit is also used for: A first downlink frame is received, the first downlink frame including indication information, the indication information indicating whether the field associated with the fourth interrupt slave node information is used to carry the identifier of the slave node that initiated the interrupt.

25. A communication device, characterized in that, include: Memory, used to store computer programs; A processor for executing a computer program stored in the memory to cause the apparatus to perform the method as described in any one of claims 1 to 12.

26. A vehicle, characterized in that, Includes the apparatus as described in any one of claims 13 to 25.

27. A computer-readable storage medium, characterized in that, It stores instructions that, when executed by a processor, cause the processor to implement the method as described in any one of claims 1 to 12.

28. A chip, characterized in that, The chip includes circuitry for performing the method as described in any one of claims 1 to 12.

Images