Communication method, apparatus and system, and vehicle

Abstract

A communication method, apparatus and system, and a vehicle. The communication method can be applied to an audio system. The audio system comprises a master node, and a plurality of slave nodes including a first slave node, wherein upon determining that a first abnormality associated with the first slave node has occurred, the first slave node sends a first uplink frame within a first time period, the first uplink frame carrying first abnormality information, the first abnormality information indicating that the first abnormality has occurred, the first time period being determined on the basis of attributes of the first slave node, or the first time period being included in an abnormality reporting period of a first slave node group, the first slave node group comprising the first slave node, and when an abnormality occurs in at least one slave node in the first slave node group, the abnormality being reported within the abnormality reporting period. The technical solution of the present application can increase the opportunity of a slave node reporting an abnormality, thereby improving the efficiency of the slave node reporting the abnormality.

Description

Communication method, device, system and vehicle

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on August 31, 2023, with application number 202311125532.3 and invention name “Communication Methods, Devices, Systems and Vehicles”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of audio transmission, and more specifically, to a communication method, device, system and vehicle. Background Art

[0003] A vehicle's wired audio system typically includes an audio control device and multiple audio devices, which are typically connected in a daisy-chain configuration. The audio control device sends the audio data to be played to one or more audio devices via an audio bus, and the audio devices then transmit the collected audio data to the audio control device via the audio bus.

[0004] When an audio control device is connected to multiple audio devices in a daisy chain networking mode, when an abnormality occurs in an audio device, how to improve the efficiency of reporting the abnormality to the audio control device becomes an urgent problem to be solved.

[0005] Summary of the Invention

[0006] The present application provides a communication method, device, system and vehicle, which can increase the chance of reporting anomalies from a node, thereby improving the efficiency of reporting anomalies from the node.

[0007] In a first aspect, a communication method is provided, which is applied to a first slave node, and includes: determining that a first exception occurs, and the first exception is associated with the first slave node; sending a first uplink frame within a first time period, the first uplink frame carrying first exception information, the first exception information indicating that a first exception occurs, and the first time period is associated with the first slave node.

[0008] The first abnormality being associated with the first slave node may include at least one of the following: an abnormality occurs in the first slave node itself, or an abnormality occurs in an external device (referred to as a peripheral device) connected to the first slave node.

[0009] Exemplarily, the first time period is included in an uplink frame transmission cycle.

[0010] In some possible implementations, the first uplink frame may be in any of the following formats:

[0011] (1) The first uplink frame includes an abnormality indication field, which can be used to carry one or more abnormality information, each abnormality information indicating that an abnormality occurs in a slave node.

[0012] (2) The first uplink frame includes two or more abnormality indication fields, where each abnormality indication field can be used to carry one or more abnormality information, and each abnormality information indicates that an abnormality occurs in a slave node.

[0013] (3) The first uplink frame includes one or more exception indication fields, wherein each exception indication field may be used to carry one or more exception information, and each exception information indicates that an exception has occurred in a slave node. In addition, the first uplink frame also includes a first field, which may carry uplink information of a specific slave node, or the first field may be used to carry one or more exception information.

[0014] In the above technical solution, multiple slave nodes can report exceptions in different uplink frame transmission cycles, so that the exception information between slave nodes reporting exceptions in different cycles will not overlap each other, thereby reducing the probability of the information indicating the exception carried in the uplink frame being overwritten, thereby increasing the chance of the slave node reporting the exception and improving the efficiency of the slave node reporting the exception.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the business type of the first slave node, and the topological position of the first slave node.

[0016] In some possible implementations, multiple slave nodes with the same attribute can report exceptions in the same uplink frame transmission period, and slave nodes with different attributes cannot report exceptions in the same uplink frame transmission period.

[0017] In the above technical solution, slave nodes with different attributes can report exceptions in different uplink frame transmission cycles, so that the exception information between slave nodes with different attributes will not overlap each other, thereby increasing the chance of slave nodes reporting exceptions and improving the efficiency of slave nodes reporting exceptions.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the first time period is associated with the first slave node, including: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and when an exception occurs in at least one slave node in the first slave node group, the exception is reported within the exception reporting period.

[0019] In the above technical solution, multiple groups of slave node groups are pre-set, which can enable slave nodes of different slave node groups to report exceptions in different uplink frame transmission cycles, so that the exception information between slave nodes of different slave node groups will not overlap each other, thereby increasing the chance of slave nodes reporting exceptions and improving the efficiency of slave nodes reporting exceptions.

[0020] In combination with the first aspect, in certain implementations of the first aspect, before sending the first uplink frame within the first time period, the method also includes: receiving a second uplink frame carrying second exception information, the second exception information indicating that a second exception has occurred in the second slave node; sending the first uplink frame within the first time period, including: when the reporting priority of the first exception is higher than the reporting priority of the second exception, sending the first uplink frame within the first time period.

[0021] In some implementations, there is no idle field in the second uplink frame that can carry the first exception information. When the reporting priority of the first exception is higher than the reporting priority of the second exception, the first exception information is used to overwrite the second exception information to obtain the first uplink frame, and the first uplink frame is sent within the first time period.

[0022] In some possible implementations, a higher reporting priority of an exception indicates a higher urgency of the exception, and the exception needs to be resolved as quickly as possible.

[0023] In the above technical solution, the abnormal information carried in the uplink frame can be determined according to the reporting priority of the abnormality. When there is no idle field to carry the abnormal information in the uplink frame received from the slave node, and the abnormality reporting priority of the current slave node is higher, the abnormal information of the current slave node is used to overwrite the abnormal information with a lower reporting priority, which helps to speed up the resolution of abnormalities with a higher degree of urgency, thereby improving the reliability of the system where the first slave node is located.

[0024] In combination with the first aspect, in some implementations of the first aspect, the second slave node and the first slave node belong to the same slave node group.

[0025] In some possible implementations, the second slave node and the first slave node belonging to the same slave node group can be understood as: the second slave node and the first slave node can report abnormalities in the same uplink frame transmission period.

[0026] In combination with the first aspect, in some implementations of the first aspect, the first uplink frame includes a first abnormality indication field, and the first abnormality indication field carries first abnormality information.

[0027] In combination with the first aspect, in certain implementations of the first aspect, the first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries first exception information, and the third exception indication field is not occupied or the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node.

[0028] In the above technical solution, at least two slave nodes with the same attributes or at least two slave nodes in the same slave node group can report exceptions in one uplink frame, which can increase the chance of slave nodes reporting exceptions and improve the efficiency of slave nodes reporting exceptions.

[0029] In combination with the first aspect, in certain implementations of the first aspect, before sending the first uplink frame within the first time period, the method also includes: receiving a third uplink frame, the third uplink frame including a second exception indication field and a third exception indication field; sending the first uplink frame within the first time period, including: when the second exception indication field is not occupied and the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, sending the first uplink frame within the first time period; wherein the third exception indication field of the first uplink frame carries the third exception information.

[0030] In the above technical solution, the first slave node uses the unoccupied exception indication field to carry the first exception information, which can avoid other exception information from being overwritten, and helps to improve the efficiency of reporting exceptions from the slave node.

[0031] In combination with the first aspect, in some implementations of the first aspect, the third slave node and the first slave node belong to the same slave node group, or the third slave node and the first slave node belong to different node groups.

[0032] In combination with the first aspect, in certain implementations of the first aspect, when the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the first exception information, the value of the third exception indication field is a non-specific value.

[0033] Exemplarily, the third abnormality indication field indicates whether a slave node is abnormal through a character string. The specific value may be a value in which the character string is all "0", and the non-specific value may be a value in which the character string is not all "0".

[0034] In the above technical solution, by setting a specific value, the slave node can quickly determine the unoccupied exception indication field, thereby reducing the delay in sending the uplink frame indicating the slave node abnormality, which helps to improve the efficiency of abnormality reporting.

[0035] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: receiving a first downlink frame, the first downlink frame including an indication bit, the indication bit indicating that the first field in the uplink frame is used to carry information about an abnormality from the slave node, or indicating that the first field is used to carry uplink information of a specific slave node.

[0036] In some possible implementations, the first slave node receives the first downlink frame, intercepts the data that the master node wants to send to the first downlink frame from the first downlink frame, and forwards the first downlink frame, that is, the downlink frame sent by the first slave node to the downlink does not include the data sent by the master node to the first slave node.

[0037] In combination with the first aspect, in some implementations of the first aspect, the first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

[0038] In combination with the first aspect, in certain implementations of the first aspect, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0039] In the above technical solution, multiple bits of an abnormality indication field carry information about multiple slave nodes, which can support multiple slave nodes to report abnormalities simultaneously while occupying a small amount of uplink resources.

[0040] Exemplarily, the other slave nodes may include a fourth slave node.

[0041] In combination with the first aspect, in certain implementations of the first aspect, before sending the first uplink frame within the first time period, the method also includes: receiving a fourth uplink frame, the fourth uplink frame including a fourth exception indication field, the fourth exception indication field carrying fourth exception information, and the fourth exception information indicating that a fourth exception occurs at the fourth slave node; sending the first uplink frame within the first time period includes: sending the first uplink frame carrying the first exception information and the fourth exception information through the fourth exception indication field within the first time period.

[0042] In combination with the first aspect, in some implementations of the first aspect, the fourth slave node and the first slave node belong to the same slave node group.

[0043] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: receiving a fifth uplink frame, the fifth uplink frame carrying fifth exception information, the fifth exception information indicating that a fifth exception has occurred in the fifth slave node; when there is no idle field in the fifth uplink frame for carrying the first exception information, sending a sixth uplink frame, the sixth uplink frame carrying the fifth exception information.

[0044] Illustratively, the fifth uplink frame and the sixth uplink frame can only carry one piece of abnormal information.

[0045] In some possible implementations, when the first slave node receives the fifth uplink frame and there is no idle field in the fifth uplink frame for carrying the first exception information, the first slave node may add the data it wants to send to the master node to the fifth uplink frame to generate a sixth uplink frame, and send the sixth uplink frame, that is, the first slave node adds data to the fifth uplink frame sent to the uplink.

[0046] In the above technical solution, when the uplink frame already carries abnormal information, the first slave node suspends reporting the abnormality to avoid overwriting the abnormal information of its downlink slave node.

[0047] In combination with the first aspect, in certain implementations of the first aspect, the fifth uplink frame and the sixth uplink frame include at least one exception indication field and a second field, at least one exception indication field carries fifth exception information, the second field carries sixth exception information, and the sixth exception information indicates that a sixth exception occurs in the sixth slave node; or the second field is used to carry uplink information of a specific slave node.

[0048] Exemplarily, the second field and the first field may be the same field.

[0049] In the above technical solution, when there is no idle field in the uplink frame to carry the first abnormality information, the first slave node suspends reporting the abnormality to avoid overwriting the abnormality information of its downlink slave node.

[0050] In combination with the first aspect, in certain implementations of the first aspect, the fifth uplink frame and the sixth uplink frame include at least two exception indication fields, one of the at least two exception indication fields carries the fifth exception information, at least one of the remaining fields of the at least two exception indication fields is not occupied, and the sixth uplink frame is sent, including: when the fifth slave node and the first slave node belong to different slave node groups, the sixth uplink frame is sent.

[0051] In the above technical solution, when the first slave node receives abnormal information of slave nodes in different slave node groups, it means that the uplink frame transmission period at this time is not the abnormal reporting period of the slave node group where the first slave node is located. At this time, even if the uplink frame has unoccupied idle fields, the first slave node suspends reporting the abnormality to avoid overwriting the abnormal information of slave nodes in other slave node groups.

[0052] In combination with the first aspect, in some implementations of the first aspect, sending the fifth uplink frame includes: sending a sixth uplink frame within a second time period, where the second time period is associated with the fifth slave node.

[0053] Exemplarily, the second time period being associated with the fifth slave node may include: the second time period being determined based on the attributes of the fifth slave node; and / or the second time period being included in the abnormality reporting period of the second slave node group, the second slave node group including the fifth slave node, and when an abnormality occurs in at least one slave node in the second slave node group, the abnormality is reported within the abnormality reporting period.

[0054] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: determining that a seventh abnormality occurs in the first slave node; receiving a seventh uplink frame, the seventh uplink frame indicating that an eighth abnormality occurs in the sixth slave node; when the reporting priority of the seventh abnormality is lower than or equal to the reporting priority of the eighth abnormality, and there is no idle field in the seventh uplink frame for carrying information indicating the seventh abnormality, sending an eighth uplink frame within a third time period, the eighth uplink frame indicating the eighth abnormality, and the third time period is associated with the first slave node.

[0055] Exemplarily, the third time period being associated with the first slave node may include: the third time period being determined according to attributes of the first slave node; and / or the third time period being included in an abnormality reporting period of the first slave node group.

[0056] In the above technical solution, when the abnormalities indicated by the received uplink frames are all higher than or equal to the seventh abnormality of the first slave node, the first slave node suspends reporting abnormalities, which can speed up the resolution of abnormalities with higher urgency and help improve the reliability of the system where the first slave node is located.

[0057] In combination with the first aspect, in certain implementations of the first aspect, the first abnormality includes at least one of the following: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0058] In combination with the first aspect, in some implementations of the first aspect, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0059] In the above technical solution, the first exception information indicates the reporting priority of the first exception and / or the type of the first exception, which helps the master node to promptly resolve the exception and improve the efficiency of exception handling. In particular, when the master node receives information about multiple slave node exceptions, it can prioritize exceptions with higher reporting priorities based on the reporting priorities of each exception. When the exception information indicates the type of the first exception, the master node does not need to perform an exception query when receiving the exception information, and can directly resolve the exception.

[0060] It should be noted that the abnormal information in this application is equivalent to the information indicating the abnormality of the slave node, including but not limited to the first abnormal information, the second abnormal information, the third abnormal information, etc.

[0061] In some possible implementations, the first uplink frame further carries a check field for carrying check information of the check exception indication field, so as to increase the transmission reliability of the exception information.

[0062] In a second aspect, a communication method is provided, which is applied to a first slave node, and the method includes: determining that a first exception occurs, and the first exception is associated with the first slave node; sending a first uplink frame, the first uplink frame carries an exception indication field, the exception indication field is used to indicate whether an exception occurs in at least two slave nodes, and the exception indication field carries first exception information, and the first exception information indicates that a first exception occurs.

[0063] In the above technical solution, different slave nodes can report exceptions in one uplink frame, which can increase the chance of slave nodes reporting exceptions and improve the efficiency of slave nodes reporting exceptions.

[0064] It should be noted that the beneficial effects of the technical solutions in other implementation methods of the second aspect can be referred to the relevant description in the first aspect and will not be repeated here.

[0065] In combination with the second aspect, in certain implementations of the second aspect, the first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries first exception information, the third exception indication field is not occupied or the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node.

[0066] In combination with the second aspect, in certain implementations of the second aspect, before sending the first uplink frame, the method also includes: receiving a third uplink frame, the third uplink frame including a second exception indication field and a third exception indication field; sending the first uplink frame, including: when the second exception indication field carries second exception information indicating that a second exception has occurred in the second slave node, and the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, and when the reporting priority of the first exception is higher than the reporting priority of the second exception, sending the first uplink frame; or, when the second exception indication field is not occupied and the third exception indication field carries information indicating a third exception, sending the first uplink frame; wherein, the third exception indication field of the first uplink frame carries the third exception information.

[0067] In combination with the second aspect, in certain implementations of the second aspect, when the second exception indication field is not occupied, the value of the second exception indication field is a specific value; when the second exception indication field carries the first exception information or the second exception information, the value of the second exception indication field is a non-specific value.

[0068] In combination with the second aspect, in certain implementations of the second aspect, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0069] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: receiving a first downlink frame, the first downlink frame including an indication bit, the indication bit indicating that the first field in the uplink frame is used to carry information about an abnormality from the slave node, or indicating that the first field is used to carry uplink information of a specific slave node.

[0070] In combination with the second aspect, in some implementations of the second aspect, the first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

[0071] In combination with the second aspect, in certain implementations of the second aspect, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0072] In combination with the second aspect, in certain implementations of the second aspect, before sending the first uplink frame, the method also includes: receiving a fourth uplink frame, the fourth uplink frame including a fourth exception indication field, the fourth exception indication field carrying fourth exception information, and the fourth exception information indicating that a fourth exception occurs in the fourth slave node; sending the first uplink frame, including: sending the first uplink frame carrying the first exception information and the fourth exception information through the fourth exception indication field.

[0073] In combination with the second aspect, in some implementations of the second aspect, sending the first uplink frame includes: sending the first uplink frame within a first time period, where the first time period is associated with the first slave node.

[0074] In combination with the second aspect, in certain implementations of the second aspect, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the business type of the first slave node, and the topological position of the first slave node.

[0075] In combination with the second aspect, in certain implementations of the second aspect, the first time period is associated with the first slave node, including: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and when an exception occurs in at least one slave node in the first slave node group, the exception is reported within the exception reporting period.

[0076] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: receiving a fifth uplink frame, wherein all the exception indication fields in the fifth uplink frame used to indicate that an abnormality has occurred in the slave node are occupied; when there is no idle field in the fifth uplink frame for carrying the first abnormality information, sending a sixth uplink frame, and the sixth uplink frame carries the fifth abnormality information.

[0077] In combination with the second aspect, in some implementations of the second aspect, the reporting priority of the abnormality indicated by the fifth uplink frame is higher than or equal to the reporting priority of the first abnormality.

[0078] In combination with the second aspect, in certain implementations of the second aspect, the first abnormality includes at least one of the following: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0079] In a third aspect, a communication method is provided, which includes: receiving a first uplink frame within a first time period, the first uplink frame carrying first exception information, the first exception information indicating that a first exception has occurred, the first exception is associated with a first slave node, and the first time period is associated with the first slave node; determining that a first exception has occurred based on the first exception information.

[0080] In combination with the third aspect, in certain implementations of the third aspect, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the business type of the first slave node, and the topological position of the first slave node.

[0081] In combination with the third aspect, in certain implementations of the third aspect, the first time period is associated with the first slave node, including: the first time period is included in the abnormality reporting period of the first slave node group, the first slave node group includes the first slave node, and when an abnormality occurs in at least one slave node in the first slave node group, the abnormality is reported within the abnormality reporting period.

[0082] In combination with the third aspect, in certain implementations of the third aspect, receiving a first uplink frame within a first time period includes: when a second exception occurs at the second slave node and the reporting priority of the second exception is lower than the reporting priority of the first exception, receiving the first uplink frame within the first time period, and the first slave node and the second slave node belong to the same slave node group.

[0083] In combination with the third aspect, in certain implementations of the third aspect, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0084] In combination with the third aspect, in some implementations of the third aspect, the first uplink frame includes a first abnormality indication field, and the first abnormality indication field carries first abnormality information.

[0085] In combination with the third aspect, in certain implementations of the third aspect, the first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries first exception information, the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, or the third exception indication field is not occupied.

[0086] In combination with the third aspect, in some implementations of the third aspect, the third slave node and the first slave node belong to the same slave node group, or the third slave node and the first slave node belong to different node groups.

[0087] In combination with the third aspect, in certain implementations of the third aspect, when the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries third exception information, the value of the third exception indication field is a non-specific value.

[0088] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: sending a first downlink frame, the first downlink frame including an indication bit, the indication bit indicating that the first field in the uplink frame is used to carry information about an abnormality from the slave node, or indicating that the first field is used to carry uplink information of a specific slave node.

[0089] In combination with the third aspect, in certain implementations of the third aspect, the first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

[0090] In combination with the third aspect, in certain implementations of the third aspect, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0091] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: receiving a sixth uplink frame within a second time period, the sixth uplink frame carrying fifth exception information, the fifth exception information indicating that a fifth exception occurs in the fifth slave node, the second time period is associated with the fifth slave node, and the fifth slave node and the first slave node belong to different slave node groups.

[0092] In combination with the third aspect, in certain implementations of the third aspect, the first abnormality includes at least one of the following: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0093] In a fourth aspect, a communication method is provided, which includes: receiving a first uplink frame, the first uplink frame carrying an exception indication field, the exception indication field being used to indicate whether an exception has occurred in at least two slave nodes, and the exception indication field carrying first exception information, the first exception information indicating that a first exception has occurred, and the first exception is associated with the first slave node; determining that a first exception has occurred based on the first exception information.

[0094] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries first exception information, the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, or the third exception indication field is not occupied.

[0095] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the third exception information, the value of the third exception indication field is a non-specific value.

[0096] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0097] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method also includes: sending a first downlink frame, the first downlink frame including an indication bit, the indication bit indicating that the first field in the uplink frame is used to carry information about an abnormality from the slave node, or indicating that the first field is used to carry uplink information of a specific slave node.

[0098] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

[0099] In combination with the fourth aspect, in certain implementations of the fourth aspect, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0100] In combination with the fourth aspect, in some implementations of the fourth aspect, receiving the first uplink frame includes: receiving the first uplink frame within a first time period, where the first time period is associated with the first slave node.

[0101] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the business type of the first slave node, and the topological position of the first slave node.

[0102] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first time period is associated with the first slave node, including: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and when an exception occurs in at least one slave node in the first slave node group, the exception is reported within the exception reporting period.

[0103] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first abnormality includes at least one of the following: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0104] The beneficial effects of each technical solution in the third and fourth aspects can be referred to the relevant description in the first aspect and will not be repeated here.

[0105] In a fifth aspect, a communication device is provided, which includes a processing unit and a transceiver unit, and is used to execute the method in any possible implementation of the first aspect or the second aspect.

[0106] In a sixth aspect, a communication device is provided, which includes a transceiver unit and a processing unit, and is used to execute the method in any possible implementation of the third aspect or the fourth aspect.

[0107] In the seventh aspect, a communication device is provided, which includes: a memory for storing a computer program; and a processor for executing the computer program stored in the memory, so that the device performs a method in any possible implementation of the first aspect or the second aspect.

[0108] In an eighth 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, so that the device performs a method as in any possible implementation of the third aspect or the fourth aspect.

[0109] In the ninth aspect, a communication system is provided, which includes an apparatus as in any possible implementation of the fifth aspect and an apparatus as in any possible implementation of the sixth aspect; or, the system includes an apparatus as in any possible implementation of the seventh aspect and an apparatus as in any possible implementation of the eighth aspect.

[0110] In the tenth aspect, a vehicle is provided, comprising a system as in any possible implementation of the ninth aspect; or, the vehicle comprises an apparatus as in any possible implementation of the fifth aspect and an apparatus as in any possible implementation of the sixth aspect; or, the vehicle comprises an apparatus as in any possible implementation of the seventh aspect and an apparatus as in any possible implementation of the eighth aspect.

[0111] In the eleventh aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the method in any one of the possible implementations of the first to fourth aspects.

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

[0113] In the twelfth aspect, a computer-readable medium is provided, wherein the computer-readable medium stores instructions. When the instructions are executed by a processor, the processor implements the method in any possible implementation of the first to fourth aspects.

[0114] In a thirteenth aspect, a chip is provided, which includes a circuit for executing the method in any possible implementation of the first to fourth aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0115] FIG1 is a schematic block diagram of an audio system provided in an embodiment of the present application;

[0116] FIG2 is another schematic block diagram of an audio system provided in an embodiment of the present application;

[0117] FIG3 is a schematic block diagram of a vehicle provided in an embodiment of the present application;

[0118] FIG4 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0119] FIG5 is a schematic block diagram of an uplink frame provided in an embodiment of the present application;

[0120] FIG6 is another schematic block diagram of an uplink frame provided in an embodiment of the present application;

[0121] FIG7 is another schematic block diagram of an uplink frame provided in an embodiment of the present application;

[0122] FIG8 is another schematic block diagram of an uplink frame provided in an embodiment of the present application;

[0123] FIG9 is another schematic flow chart of the communication method provided in an embodiment of the present application;

[0124] FIG10 is another schematic flow chart of the communication method provided in an embodiment of the present application;

[0125] FIG11 is another schematic flow chart of the communication method provided in an embodiment of the present application;

[0126] FIG12 is another schematic flow chart of the communication method provided in an embodiment of the present application;

[0127] FIG13 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0128] FIG14 is another schematic block diagram of a communication device provided in an embodiment of the present application;

[0129] FIG15 is another schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0130] The technical solution in this application will be described below with reference to the accompanying drawings.

[0131] Fig. 1 shows the schematic diagram of the audio system provided by an embodiment of the present application. As shown in Figure 1, audio system 100 includes an audio control device 110, an audio device 120, an audio device 130, and an audio device 140. Wherein, the audio control device 110 includes a main controller 111 and a master node 112, the audio device 120 includes a processing module 121 and a slave node 122, the audio device 130 includes a processing module 131 and a slave node 132, and the audio device 140 includes a processing module 141 and a slave node 142. The master node 112 is connected to the slave nodes 122, 132, and 142 by cables based on a daisy chain networking mode. The slave nodes 122, 132, and 142 can be devices such as processors and transmission chips in each audio device respectively. The master node 112 is used for the audio control device 110 to communicate with the audio devices 120 to 140. In one example, the main controller 111 transmits audio data to be played by the audio device 140 sequentially through the master node 112, the slave node 122, the slave node 132, and the slave node 142. The processing module 141 controls the playback of the audio data. In another example, the audio data collected by the audio device 130 through the processing module 131 is transmitted to the main controller 111 sequentially through the slave node 132, the slave node 122, and the master node 112.

[0132] In a link consisting of a master node and multiple slave nodes, the link where a slave node transmits information to the master node or in the direction of the master node is called an uplink, the link where the slave node transmits information to a slave node farther away from the master node is called a downlink, and the link where the master node transmits information to a slave node is called a downlink. For example, slave node 132 is located on the uplink of slave node 142, and slave node 132 is located on the downlink of slave node 122; slave nodes 122, 132, and 142 are all located on the downlink of master node 112. Frames sent by a master node or a slave node in the downlink are called downlink frames, and frames sent by a slave node in the uplink are called uplink frames.

[0133] FIG2 is a schematic diagram showing the distribution of the audio system provided in a vehicle according to an embodiment of the present application. As shown in FIG2 , the audio control device is connected to audio devices 1 to 8 via a daisy chain networking method. Audio device 1 and audio device 3, audio device 3 and audio device 4, audio device 4 and audio device 7, audio device 7 and audio device 8, audio device 8 and audio device 6, audio device 6 and audio device 5, and audio device 5 and audio device 2 can be connected via a vehicle audio bus, respectively. The audio control device may include the audio control device 110 shown in FIG1 , and audio devices 1 to 8 may include one or more of the audio devices 120, 130, and 140 shown in FIG1 . For example, audio device 1 may be the audio device 120 shown in FIG1 , and one or more of the audio devices 3, 4, 7, and 8 may be the audio device 130 shown in FIG1 , and one or more of the audio devices 6, 5, and 2 may be the audio device 140 shown in FIG1 .

[0134] Exemplarily, the audio 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).

[0135] FIG3 shows a functional schematic diagram of a vehicle provided in an embodiment of the present application. As shown in FIG3 , the vehicle includes the audio system 100 shown in FIG1 . When the audio system 100 is set in a vehicle, the audio control device 110 may include any one of a vehicle domain controller (VDC), an advanced driving domain controller (ADC), and a cockpit domain controller (CDC). Alternatively, the audio control device 110 may also include, but is not limited to, an in-car application-server (ICAS) controller, a body domain controller (BDC), a special equipment system (SAS), a media graphics unit (MGU), a body super core (BSC), and an advanced driving assistant system super core (ADAS super core). Among them, the ICAS may include at least one of the following: a vehicle control server ICAS1, an intelligent driving server ICAS2, an intelligent cockpit server ICAS3, and an infotainment server ICAS4.

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

[0137] It should be understood that FIG. 1 to FIG. 3 are merely exemplary illustrations, and in actual implementation, the audio system 100 may include more or fewer slave nodes, that is, the audio system may include more or fewer audio devices.

[0138] In the current technical context, when an exception 1 occurs in a slave node (hereinafter referred to as slave node 1) in the audio system, the slave node 1 can carry information indicating the exception 1 in the uplink frame to report the exception 1 to the master node. However, when an exception (such as exception 2) also occurs in a slave node (hereinafter referred to as slave node 2) located in the uplink of the slave node, the information indicating exception 1 in the uplink frame may be overwritten by the information indicating exception 2, resulting in the failure of the slave node 1 to report the exception to the master node. In addition, after the slave node 2 reports the exception, before the exception of the slave node 2 is resolved, the slave node 2 may still carry information indicating exception 2 in subsequent uplink frames, and this information may still overwrite the information indicating the exception reported by the slave node located in the downlink of the slave node 2, resulting in the failure of other slave nodes located in the downlink of the slave node 2 to report the exception to the master node before the exception of the slave node 2 is resolved, resulting in low efficiency in reporting the exception by the slave node.

[0139] In view of this, embodiments of the present application provide a communication method, device, system, and vehicle that can determine the period for a slave node to report an anomaly based on the attributes of the slave node. If an anomaly occurs at a slave node but the reporting period has not yet expired, the slave node will not report the anomaly. In other words, by having multiple slave nodes in an audio system report anomalies in at least two different periods, the probability of the information indicating anomalies carried in the uplink frame being overwritten can be reduced, thereby increasing the chances of the slave node reporting the anomaly and improving the efficiency of the slave node's anomaly reporting.

[0140] It should be noted that the abnormality of the slave node involved in this application can be understood as an abnormality associated with the slave node, for example, it can include an abnormality of the slave node itself, or it can also include an abnormality of a peripheral device connected to the slave node.

[0141] The specific implementation of the communication method provided in the embodiment of the present application is described below in conjunction with Figures 4 to 12.

[0142] FIG4 shows a schematic flow chart of a communication method provided by an embodiment of the present application. This method 400 can be executed by the audio system 100 shown in FIG1 , or can also be applied to the audio system shown in FIG2 . For example, the master node can be the master node 112 in FIG1 , and the first slave node can be any one of the slave nodes 120 to 140 in FIG1 . 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. This method 400 includes:

[0143] S401: A first slave node determines that a first exception occurs.

[0144] Exemplarily, the first abnormality may include, but is not limited to: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0145] The peripherals may include external devices connected to the slave node, such as a MIC, a speaker, an APM, and the like.

[0146] Exemplarily, information transmission anomalies may include the inability to continue transmitting information due to reasons such as failure to check the check field included in the information; parameter anomalies may include the voltage, temperature and other parameters of the slave node exceeding the preset range; peripheral device anomalies may include abnormal peripheral device status or abnormality in the interface connecting the peripheral device and the slave node.

[0147] S402 : The first slave node sends a first uplink frame within a first time period. The first uplink frame carries first exception information. The first exception information indicates that a first exception occurs. The first time period is associated with the first slave node.

[0148] In some possible implementations, the first time period being associated with the first slave node can be understood as: the first time period being determined based on attributes of the first slave node. The attributes of the first slave node include, but are not limited to, an identifier of the first slave node, a service type of the first slave node, and a topological location of the first slave node.

[0149] Among them, the identifier of the first slave node can uniquely identify the identity of the first slave node; the topological position of the first slave node indicates the position of the first slave node in the daisy chain network; the service types of the slave node include but are not limited to: audio playback service, audio recognition service, audio acquisition service, and the service type of the first slave node can include at least one of the above service types.

[0150] For example, it is pre-set that slave nodes with the first type of attributes report exceptions in odd-numbered uplink frames, and slave nodes with the second type of attributes report exceptions in even-numbered uplink frames. The first type of attribute can be a first service type, such as an audio playback service, and the second type of attribute can be a second service type, such as an audio acquisition service; or, the first type of attribute can be a first topological position, such as an odd-numbered position in a daisy-chain network, and the second type of attribute can be a second topological position, such as an even-numbered position in a daisy-chain network. Taking the audio system shown in Figure 2 as an example, the odd-numbered positions in the daisy-chain network can be the positions of audio device 1, audio device 4, audio device 8, and audio device 5; and the even-numbered positions in the daisy-chain network can be the positions of audio device 3, audio device 7, audio device 6, and audio device 2. Exemplarily, the odd uplink frames and even uplink frames can be distinguished by the serial numbers of the uplink frames. For example, if the last digit of the serial number is odd, the uplink frame is an odd uplink frame; if the last digit of the serial number is even, the uplink frame is an even uplink frame.

[0151] If the first slave node is a slave node of the first type of attribute, the first time period can be determined based on the transmission period of the odd uplink frame. For example, the uplink frame currently transmitted from the slave node is an odd uplink frame. If the first slave node is the tail slave node, the first time period can be the time period between the first slave node receiving the odd downlink frame and sending the odd uplink frame, or the first time period can also be the time period between the first slave node receiving the odd downlink frame and the master node receiving the odd uplink frame; if the first slave node is not the tail slave node, the first time period can be the time period between the first slave node receiving the odd uplink frame from the slave node of the uplink and sending the odd uplink frame, or the first time period can be the time period between the first slave node receiving the odd uplink frame from the slave node of the uplink and the master node receiving the odd uplink frame. If the first slave node is a slave node of the second type of attribute, the way it determines the first time period is similar to the above and will not be repeated here.

[0152] It should be noted that the above division of slave nodes with the first type of attributes and slave nodes with the second type of attributes is merely exemplary. In the specific implementation process, slave nodes with more attributes may be set. When a slave node has more than two types of attributes, such as four types of attributes, the slave nodes with the four types of attributes may be pre-set to report exceptions in four types of uplink frames, respectively. The four types of uplink frames may be determined based on the sequence number of the uplink frame. For example, if a 2-bit binary code is used to represent the sequence number of the uplink frame, the four types of uplink frames may be uplink frames with sequence numbers 00, 01, 10, and 11, respectively.

[0153] In some possible implementations, the first time period is associated with the first slave node, which can also be understood as: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and each slave node in the first slave node group can report the exception within the exception reporting period.

[0154] Exemplarily, the first slave node group can be obtained by grouping according to the attributes of the slave nodes. For example, the slave nodes with the first type of attributes are determined as one group of slave node groups, and the slave nodes with the second type of attributes are determined as another group of slave node groups; or, the first slave node group can also be obtained by grouping in other ways.

[0155] Exemplarily, the abnormality reporting period of the first slave node group can be pre-set, for example, the transmission period of the uplink frame carrying a certain sequence number is pre-set as the abnormality reporting period of the first slave node group; or, the abnormality reporting period of the first slave node group can also be determined by other means.

[0156] In some possible implementations, the first exception information further indicates the reporting priority of the first exception and / or the type of the first exception. Exemplarily, the reporting priority of the first exception can indicate the urgency of the first exception, and the higher the reporting priority, the higher the urgency. Exemplarily, the type of the first exception can include but is not limited to the information transmission exception of the first slave node, the parameter exception of the first slave node, and the peripheral exception of the first slave node. By indicating the reporting priority of the first exception and / or the type of the first exception in the first exception information, it is helpful for the master node to promptly perform the abnormal processing and improve the efficiency of abnormal processing.

[0157] S403: The master node receives the first uplink frame and determines that a first abnormality occurs according to the first abnormality information.

[0158] In some possible implementations, after the master node determines that the first abnormality has occurred, the master node may carry information for resolving or repairing the first abnormality in a subsequently sent downlink frame.

[0159] In some possible implementations, before sending the first uplink frame within the first time period, the method further includes: receiving an uplink frame, and generating the first uplink frame according to information carried in the uplink frame.

[0160] The communication method provided in the embodiment of the present application can enable slave nodes with different attributes to report exceptions in different periods, so that the exception information between slave nodes with different attributes will not overlap with each other, thereby reducing the probability of the information indicating the exception carried in the uplink frame being overwritten, thereby increasing the chance of the slave node reporting the exception and improving the efficiency of the slave node reporting the exception.

[0161] In the embodiment of the present application, the structure of the uplink frame may include various forms. The structure of the uplink frame in the present application is described below with reference to FIG. 5 to FIG. 8 .

[0162] In one implementation, the structure of an uplink frame may be as shown in FIG5 , including an exception indication field and an other information field. The exception indication field may be used to carry one or more pieces of exception information, each piece of exception information indicating an exception has occurred in a slave node, and the other information field may be used to carry information other than the exception information, such as control information or service information.

[0163] In another implementation, the structure of the uplink frame can be as shown in Figure 6, including an exception indication field, such as an exception indication Bitmap field, which is used to carry exception information indicating that one or more slave nodes are abnormal. Exemplarily, the exception indication field can carry P bits, each of the P bits corresponds to a slave node, and P is an integer greater than or equal to 2. The value of each bit can be a first value (such as "1") or a second value (such as "0"). When a certain bit takes the first value, it indicates that the corresponding slave node has an abnormality; when a certain bit takes the second value, it indicates that the corresponding slave node has not an abnormality. For example, there are 6 slave nodes belonging to the first type of attributes. Taking the exception indication Bitmap field carrying 6 bits as an example, each of the 6 bits corresponds to a slave node of the first type of attributes. When the bit value is 0, it indicates that the slave node has no abnormality, and when the value is 1, it indicates that the slave node has an abnormality. If the exception indication Bitmap field takes the value of 000110, it means that the slave nodes corresponding to the 4th and 5th bits have an abnormality. The shaded portion shown in FIG6 may also carry information other than the abnormal information, such as control information or service information.

[0164] In some scenarios, when a bit among P bits takes the first value, the bit taking the first value can be regarded as an abnormal information; or, when a bit among P bits takes the first value, the P bits can be regarded as an abnormal information.

[0165] In another implementation, the structure of the uplink frame can be as shown in Figure 7, including two exception indication fields, such as exception indication field 1 and exception indication field 2. Exception indication field 1 and exception indication field 2 can be used to carry exception information of slave nodes of two different attributes, respectively, or exception indication field 1 and exception indication field 2 can be used to carry exception information of the same type of slave nodes. The uplink frame can also include a check information field for carrying information for checking the exception indication field, such as cyclic redundancy check (CRC), Hamming code, and other information. The shaded portion shown in Figure 7 can also carry information other than exception information, such as control information or service information.

[0166] In another implementation, the structure of the uplink frame can be as shown in Figure 8, including an abnormality indication field and a first field, such as abnormality indication field 1 and field 1, wherein the abnormality indication field 1 can be used to carry abnormal information indicating that one or more slave nodes are abnormal, and field 1 can be used to carry specific uplink information, which can include control information or business information, as shown in (a) in Figure 8; or, field 1 can also be used to carry abnormal information, as shown in (b) in Figure 8. Exemplarily, the specific uplink information can be the uplink information of a specific slave node, such as the internal integrated circuit (I2C) information reported by a specific slave node. Whether field 1 is used to carry specific uplink information or abnormal information can be indicated by the master node through the downlink frame. The shaded portion shown in Figure 8 can also carry information other than abnormal information, such as control information or business information.

[0167] In some possible implementations, the shaded portions shown in FIG. 5 to FIG. 8 also carry the sequence numbers of the uplink frames.

[0168] In some possible implementations, the implementations shown in FIG. 5 to FIG. 8 may be combined. For example, the exception indication field shown in FIG. 7 or FIG. 8 may be an exception indication Bitmap field to indicate that an exception has occurred in multiple slave nodes through multiple bits.

[0169] To facilitate understanding of the method 400 , an application scenario of the method 400 is introduced below in conjunction with FIG. 9 .

[0170] Figure 9 shows a schematic flow chart of a communication method provided in an embodiment of the present application. The method 500 can be executed by the audio system 100 shown in Figure 1, or can also be applied to the audio system shown in Figure 2. For example, the master node can be the master node 112 in Figure 1 above, and the slave nodes 1 to 3 can be the slave nodes 120 to 140 in Figure 1, respectively. Among them, slave node 1 and slave node 2 are slave nodes of the first type of attributes, and slave node 3 is a slave node of the second type of attributes; the slave nodes of the first type of attributes are pre-configured to report exceptions in odd uplink frames, and the slave nodes of the second type of attributes are pre-configured to report exceptions in even uplink frames. Specifically, as shown in (a) in Figure 9, the method 500 may include S501 to S512.

[0171] S501 , the master node sends an even-numbered downlink frame to slave node 1 .

[0172] S502 , slave node 1 sends an even-numbered downlink frame to slave node 2 .

[0173] In some possible implementations, when or after slave node 1 receives an even-numbered downlink frame, slave node 1 intercepts the data transmitted from the master node to slave node 1 from the even-numbered downlink frame, and sends the intercepted even-numbered downlink frame to slave node 2. In other words, the even-numbered downlink frame sent from slave node 1 to slave node 2 lacks at least the data transmitted from the master node to slave node 1 compared to the even-numbered downlink frame sent from the master node to slave node 1.

[0174] S503 , slave node 2 sends an even-numbered downlink frame to slave node 3 .

[0175] In some possible implementations, upon or after receiving the even-numbered downlink frame from slave node 2, slave node 2 intercepts the data transmitted from the master node to slave node 2 from the even-numbered downlink frame and sends the intercepted even-numbered downlink frame to slave node 3. That is, the even-numbered downlink frame sent from slave node 2 to slave node 3 lacks at least the data transmitted from the master node to slave node 2 compared to the even-numbered downlink frame sent from slave node 1 to slave node 2. S504: Slave node 3 sends uplink frame 1 to slave node 2, where uplink frame 1 indicates an abnormality in slave node 3.

[0176] Exemplarily, when slave node 3 determines that an abnormality occurs and receives an even downlink frame, an even uplink frame determined by the even downlink frame, such as uplink frame 1, may indicate that slave node 3 is abnormal.

[0177] S505 , slave node 2 sends an uplink frame 1 ′ to slave node 1 .

[0178] In some possible implementations, when or after slave node 2 receives uplink frame 1, slave node 2 appends the data it intends to send to the master node to uplink frame 1 to obtain uplink frame 1', and then transmits the data-appended uplink frame 1' to slave node 1. In other words, the uplink frame 1 sent by slave node 3 to slave node 2 lacks at least the data transmitted from slave node 2 to the master node, compared to the uplink frame 1' sent by slave node 2 to slave node 1.

[0179] S506, the slave node 1 sends an uplink frame 1 to the master node.

[0180] In some possible implementations, when or after slave node 1 receives the uplink frame 1', slave node 1 adds the data it wants to send to the master node to the uplink frame 1' to obtain the uplink frame 1", and sends the uplink frame 1" with the added data to the master node. That is, the uplink frame 1' sent by slave node 2 to slave node 1 lacks at least the data transmitted from slave node 1 to the master node, compared to the uplink frame 1" sent by slave node 1 to the master node.

[0181] It should be noted that if an abnormality occurs in both slave node 2 and slave node 3, since the uplink frames 1 to uplink frames 1" sent at this time are even uplink frames, slave node 3 belonging to the second type of attributes can report the abnormality through uplink frames 1 to uplink frames 1", while slave node 1 and slave node 2 belonging to the first type of attributes cannot report the abnormality through uplink frames 1 to uplink frames 1".

[0182] Therefore, slave node 1 and slave node 2 only forward upstream frames.

[0183] It should also be noted that the aforementioned "forwarding only uplink frames" is intended to restrict slave nodes 1 and 2 from modifying the abnormal information in the uplink frames. However, this does not preclude slave nodes 1 and 2 from adding and / or deleting content other than the abnormal information from the uplink frames, such as data that the slave nodes want to report to the master node. In other words, the uplink frames forwarded by slave node 1 (or slave node 2) may contain additional data from slave node 1 (or slave node 2) or other content other than the abnormal information, compared to the uplink frames it receives.

[0184] S507 , the master node sends an odd-numbered downlink frame to slave node 1 .

[0185] In some possible implementations, the master node may determine that an abnormality has occurred in the slave node 3 based on the uplink frame 1", and carry information 1 for resolving the abnormality of the slave node 3 in an odd-numbered downlink frame.

[0186] S508 , slave node 1 sends an odd-numbered downlink frame to slave node 2 .

[0187] S509 , slave node 2 sends an odd-numbered downlink frame to slave node 3 .

[0188] S510 , slave node 3 sends an uplink frame 2 to slave node 2 .

[0189] In some possible implementations, the slave node 3 processes its own abnormality according to the information 1 carried in the odd-numbered uplink frame.

[0190] Exemplarily, when an odd downlink frame is received from node 3 , an odd uplink frame, such as uplink frame 2 , may be determined and sent based on the odd downlink frame.

[0191] In one scenario, when slave node 3 sends uplink frame 2, its own abnormality has not yet been resolved. At this time, slave node 3 may still need to report the abnormality. However, because the currently sent uplink frame 2 is an odd-numbered uplink frame, slave node 3 is not allowed to report the abnormality through uplink frame 2.

[0192] S511 , slave node 2 sends an uplink frame 3 to slave node 1 , where the uplink frame 3 indicates that slave node 2 is abnormal.

[0193] Exemplarily, when slave node 2 determines that an abnormality has occurred and determines that the uplink frame currently received or to be sent is an odd-numbered uplink frame, the uplink frame to be sent, such as uplink frame 3, indicates that slave node 2 is abnormal.

[0194] It should be noted that uplink frame 2 and uplink frame 3 only represent different information carried in the uplink frames. Both uplink frame 2 and uplink frame 3 are odd-numbered uplink frames and have the same sequence number.

[0195] S512 , slave node 1 sends an uplink frame 3 ′ to the master node, where the uplink frame 3 ′ indicates that slave node 2 is abnormal.

[0196] Since no abnormality occurs in slave node 1, slave node 1 can only forward uplink frames.

[0197] Furthermore, the master node can determine that an abnormality has occurred in slave node 2 based on the uplink frame 3', and subsequently send a downlink frame carrying information 2 for resolving the abnormality of slave node 2. When slave node 2 receives the downlink frame, it can process its own abnormality based on the information 2 carried therein.

[0198] For the contents not described in detail in S507 to S512, please refer to the description in S501 to S506, which will not be repeated here.

[0199] For example, the structures of uplink frame 1, uplink frame 1', uplink frame 1", uplink frame 2, uplink frame 3 and uplink frame 3' can be shown in any one of Figures 5 to 8. Taking uplink frame 1 as an example, if the frame structure is as shown in Figure 5, the abnormality indication field can carry abnormal information indicating that the slave node 3 is abnormal, thereby indicating that the abnormality occurs in the slave node 3 through uplink frame 1; if the frame structure is as shown in Figure 6, the bit corresponding to the slave node 3 in the bit carried by the abnormality indication Bitmap field can be set to the first value, thereby indicating that the abnormality occurs in the slave node 3 through uplink frame 1; if the frame If the structure is as shown in FIG7 , then abnormality information indicating an abnormality in slave node 3 can be carried in abnormality indication field 1 or abnormality indication field 2, thereby indicating that an abnormality has occurred in slave node 3 through uplink frame 1. If the frame structure is as shown in FIG8 , then abnormality information indicating an abnormality in slave node 3 can be carried in abnormality indication field 1 or field 1, thereby indicating that an abnormality has occurred in slave node 3 through uplink frame 1. It should be noted that if it is determined through the downlink frame that field 1 shown in FIG8 is used to carry specific uplink information, then the abnormality information indicating an abnormality in slave node 3 can only be carried in abnormality indication field 1 shown in FIG8 .

[0200] As shown in (b) of Figure 9 , method 500 may further include S513 to S518, which may be performed before S501 or after S512. For example, at this time, both slave node 1 and slave node 2 belonging to the first type of attribute are abnormal.

[0201] S513 , the master node sends an odd-numbered downlink frame to slave node 1 .

[0202] S514 , slave node 1 sends an odd-numbered downlink frame to slave node 2 .

[0203] S515 , slave node 2 sends an odd-numbered downlink frame to slave node 3 .

[0204] S516 , slave node 3 sends uplink frame 4 to slave node 2 .

[0205] Exemplarily, when an odd downlink frame is received from node 3 , an odd uplink frame, such as uplink frame 4 , may be determined and sent based on the odd downlink frame.

[0206] S517 , slave node 2 sends an uplink frame 5 to slave node 1 , where the uplink frame 5 indicates that slave node 2 is abnormal.

[0207] Exemplarily, when slave node 2 determines that an abnormality has occurred and determines that the uplink frame currently received or to be sent is an odd-numbered uplink frame, the uplink frame to be sent, such as uplink frame 5, indicates that slave node 2 is abnormal.

[0208] S518 , slave node 1 sends an uplink frame 6 to the master node. Uplink frame 6 indicates that slave node 1 is abnormal, or indicates that slave node 1 and slave node 2 are abnormal.

[0209] In one example, when slave node 1 determines that an abnormality has occurred and receives uplink frame 5, it can add abnormality information indicating that slave node 1 is abnormal to uplink frame 5, and obtain and send uplink frame 6. At this time, uplink frame 6 indicates that slave node 1 and slave node 2 are abnormal.

[0210] In another example, when slave node 1 determines that an abnormality has occurred and receives an uplink frame 5, it is determined that there is no idle field in the uplink frame 5 for carrying abnormal information indicating the abnormality of the slave node, and the reporting priority of the abnormality of slave node 2 indicated by the uplink frame 5 is lower than the reporting priority of the abnormality of slave node 1, then slave node 2 sends an uplink frame 6 indicating the abnormality of slave node 1 to the master node.

[0211] The above-mentioned idle field may include an unoccupied exception indication field, that is, an exception indication field that does not carry any exception information; or, the above-mentioned idle field may also include an exception indication field that carries exception information but can still carry other exception information.

[0212] Exemplarily, the reporting priority of the exception can be pre-determined and aligned between multiple slave nodes, or the exception reporting priority can be indicated by the exception information carried in the uplink frame, so that when the slave node where the exception occurs receives the uplink frame carrying the exception information, it can determine which reporting priority has a higher one, the exception indicated by the exception information or the exception occurring in the slave node, based on the exception information.

[0213] S518', slave node 1 sends an uplink frame 5' to the master node, where the uplink frame 5' indicates that slave node 2 is abnormal.

[0214] Exemplarily, when slave node 1 determines that an abnormality has occurred and receives an uplink frame 5, and determines that there is no idle field in the uplink frame 5 for carrying abnormal information indicating an abnormality of the slave node, slave node 1 can add the data it wants to transmit to the master node to the uplink frame 5 to obtain an uplink frame 5', and send the uplink frame 5' to the master node. Alternatively, when slave node 1 determines that there is no idle field in the uplink frame 5 for carrying abnormal information indicating an abnormality of the slave node, and the reporting priority of the abnormality indicated by the uplink frame 5 is higher than or equal to the reporting priority of the abnormality of slave node 1, then slave node 1 sends an uplink frame 5' to the master node.

[0215] Among them, S518 and S518' can be executed alternatively.

[0216] For the contents not described in detail in S513 to S518, please refer to the description in S501 to S506 and will not be repeated here.

[0217] It should be noted that uplink frame 4, uplink frame 5, uplink frame 5' and uplink frame 6 only indicate that the information carried in the uplink frames may be different. Uplink frame 4, uplink frame 5 and uplink frame 6 are all odd-numbered uplink frames and have the same sequence number.

[0218] Exemplarily, the structures of uplink frame 4, uplink frame 5, and uplink frame 6 can be as shown in any one of Figures 5 to 8. Taking uplink frame 6 indicating that slave node 1 and slave node 2 are abnormal as an example, in one example, the abnormal information indicating that slave node 1 is abnormal and the abnormal information indicating that slave node 2 is abnormal can both be carried in the abnormal indication field shown in Figure 5. In another example, the abnormal information indicating that slave node 1 is abnormal and the abnormal information indicating that slave node 2 is abnormal can both be carried in the abnormal indication Bitmap field shown in Figure 6. In another example, the abnormal indication field 1 and the abnormal indication field 2 shown in Figure 7 can only carry one abnormal information respectively, then the abnormal information indicating that slave node 1 is abnormal can be carried in the abnormal indication field 1 shown in Figure 7, and the abnormal information indicating that slave node 2 is abnormal can be carried in the abnormal indication field 2 shown in Figure 7; or, the abnormal information indicating that slave node 1 is abnormal and the abnormal information indicating that slave node 2 is abnormal can both be carried in the abnormal indication field 1 shown in Figure 7, or the abnormal information indicating that slave node 1 is abnormal and the abnormal information indicating that slave node 2 is abnormal can both be carried in the abnormal indication field 2 shown in Figure 7. In another example, the abnormality information indicating the abnormality of slave node 1 can be carried in the abnormality indication field 1 shown in Figure 8, and the abnormality information indicating the abnormality of slave node 2 can be carried in the field 1 shown in Figure 8; or, the abnormality information indicating the abnormality of slave node 1 and the abnormality information indicating the abnormality of slave node 2 can both be carried in the abnormality indication field 1 shown in Figure 8.

[0219] In some scenarios, if the uplink frame 6 indicates that the slave node 1 or the slave node 2 is abnormal, the structure of the uplink frame 6 can refer to the above description of the structure of the uplink frame 1, and will not be repeated here.

[0220] It should be noted that the slave nodes of the first type of attributes shown in Figure 9 can also include more slave nodes, and the slave nodes of the second type of attributes can also include more slave nodes. Slave node 1 can be a slave node directly connected to the master node, or one or more slave nodes can be connected in sequence between slave node 1 and the master node. Slave node 3 can be a tail slave node, that is, the downlink of slave node 3 is no longer connected to a slave node; or, slave node 3 can also be an intermediate slave node, that is, the downlink of slave node 3 is also connected to at least one slave node. When slave node 3 is an intermediate slave node, slave node 3 will send downlink frames to the slave nodes of its downlink and receive uplink frames from the slave nodes of its downlink. In addition, one or more slave nodes may be connected in sequence between slave node 1 and slave node 2, and one or more slave nodes may be connected in sequence between slave node 2 and slave node 3.

[0221] In a specific implementation, slave node 1 can be a slave node directly connected to the master node, or one or more slave nodes can be sequentially connected between slave node 1 and the master node. Slave node 3 can be a tail slave node, meaning that the downlink of slave node 3 is no longer connected to a slave node; or, slave node 3 can be an intermediate slave node, meaning that the downlink of slave node 3 is also connected to at least one slave node. When slave node 3 is an intermediate slave node, slave node 3 will send a slave node discovery frame 2 to the slave node of its downlink. In addition, one or more slave nodes may be sequentially connected between slave node 1 and slave node 2, and one or more slave nodes may be sequentially connected between slave node 2 and slave node 3.

[0222] When method 400 is combined with method 500, slave nodes 1, 2, and 3 in method 500 can be considered as examples of the first slave node. When slave node 1 is the first slave node, uplink frame 5' and uplink frame 6 can be considered as examples of the first uplink frame; when slave node 2 is the first slave node, uplink frame 3 and uplink frame 5 can be considered as examples of the first uplink frame; and when slave node 3 is the first slave node, uplink frame 1 can be considered as an example of the first uplink frame.

[0223] Taking slave node 1 as the first slave node, the abnormality occurring in slave node 1 as the first abnormality, and uplink frame 6 indicating the abnormality of slave node 1 or indicating the abnormality of slave node 1 and slave node 2 as the first uplink frame as an example, S517 and S518 can be summarized as any one of the following (1) to (3):

[0224] (1) Before the first slave node sends the first uplink frame, it receives the second uplink frame carrying the second exception information, where the second exception information indicates that the second exception occurs in the second slave node; when the reporting priority of the first exception is higher than the reporting priority of the second exception, the first uplink frame is sent within the first time period.

[0225] Exemplarily, the second uplink frame includes a first abnormality indication field, which can only carry abnormal information indicating an abnormality of a slave node. The first abnormality information is used to overwrite the second abnormality information of the second uplink frame to obtain the first uplink frame and send it.

[0226] Among them, slave node 2 can be regarded as an example of a second slave node, uplink frame 5 can be regarded as an example of a second uplink frame, and the second abnormality can be the abnormality occurring in the above-mentioned slave node 2.

[0227] (2) Before the first slave node sends the first uplink frame, it receives a third uplink frame including a second exception indication field and a third exception indication field; when the second exception indication field is not occupied and the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, it sends the first uplink frame within a first time period; wherein, the first uplink frame carries the first exception information through the second exception indication field, and the first uplink frame also includes a third exception indication field carrying the third exception information.

[0228] Among them, slave node 2 can be regarded as an example of the third slave node, uplink frame 5 can be regarded as an example of the third uplink frame, the third exception can be the exception occurring in the above-mentioned slave node 2, and the second exception indication field and the third exception indication field can be the exception indication field 1 and the exception indication field 2 shown in Figure 7 respectively.

[0229] (3) Before the first slave node sends the first uplink frame, it receives a fourth uplink frame including a fourth exception indication field, where the fourth exception indication field carries fourth exception information, and the fourth exception information indicates that a fourth exception occurs at the fourth slave node; and within the first time period, it sends the first uplink frame carrying the first exception information and the fourth exception information through the fourth exception indication field.

[0230] Among them, slave node 2 can be regarded as an example of the fourth slave node, uplink frame 5 can be regarded as an example of the fourth uplink frame, the fourth exception can be the exception occurring in the above-mentioned slave node 2, and the fourth exception indication field can be the exception indication Bitmap field shown in Figure 6. When the exception indication field 1 shown in Figures 7 and 8 can carry multiple exception information, the fourth exception indication field can also be the exception indication field 1 shown in Figures 7 and 8.

[0231] Taking slave node 1 as the first slave node and uplink frame 5' as the first uplink frame as an example, S517 and S518' can be summarized as either (a) or (b):

[0232] (a) The first slave node receives a fifth uplink frame carrying fifth exception information, where the fifth exception information indicates that a fifth exception has occurred at the fifth slave node. When there is no free field in the fifth uplink frame for carrying the first exception information, the first slave node transmits a sixth uplink frame, where the sixth uplink frame carries the fifth exception information. Slave node 2 can be considered an example of the fifth slave node, uplink frame 5 can be considered an example of the fifth uplink frame, uplink frame 5' can be considered an example of the sixth uplink frame, and the fifth exception can be the exception that occurred at slave node 2.

[0233] In one implementation, the fifth uplink frame includes at least one exception indication field and a second field, at least one exception indication field carries fifth exception information, the second field carries sixth exception information, and the sixth exception information indicates that a sixth exception has occurred in the sixth slave node; or the second field is used to carry uplink information of a specific slave node. That is to say, when there is no idle field in the fifth uplink frame for carrying the first exception information, the first slave node directly forwards the fifth uplink frame. Among them, field 1 shown in Figure 8 can be regarded as an example of the second field, the exception indication field 1 shown in Figure 8 can be regarded as an example of at least one exception indication field, slave node 2 can be regarded as an example of the sixth slave node, and the sixth exception can be an exception that occurred in the above-mentioned slave node 2.

[0234] (b) The first slave node determines that a seventh anomaly has occurred; receives a seventh uplink frame, the seventh uplink frame indicating that an eighth anomaly has occurred at the sixth slave node; when the reporting priority of the seventh anomaly is lower than or equal to the reporting priority of the eighth anomaly, and there is no idle field in the seventh uplink frame for carrying information indicating the seventh anomaly, sends an eighth uplink frame within a third time period, the eighth uplink frame indicating the eighth anomaly, and the third time period is associated with the first slave node.

[0235] Among them, the seventh exception can be an exception occurring from node 1, slave node 2 can be regarded as an example of the sixth slave node, uplink frame 5 can be regarded as an example of the seventh uplink frame, uplink frame 5' can be regarded as an example of the eighth uplink frame, the eighth exception can be the above-mentioned exception occurring from node 2, and the third time period is included in the cycle of reporting exceptions from the first type of attributes. For example, the third time period can be the time period between receiving uplink frame 5 from node 1 and sending uplink frame 5'.

[0236] Taking slave node 2 as the first slave node and the exception occurring in slave node 2 as the first exception as an example, S504 and S505 can be summarized as: the first slave node receives the fifth uplink frame, the fifth uplink frame includes at least two exception indication fields, one of the at least two exception indication fields carries the fifth exception information, and at least one of the remaining fields of the at least two exception indication fields is not occupied. When the fifth slave node and the first slave node belong to different slave node groups, the sixth uplink frame is sent.

[0237] That the fifth slave node and the first slave node belong to different slave node groups can also be understood as: the fifth slave node and the first slave node have different attributes.

[0238] Among them, slave node 3 can be regarded as an example of the fifth slave node, uplink frame 1 can be regarded as an example of the fifth uplink frame, uplink frame 1' can be regarded as an example of the sixth uplink frame, the fifth exception can be the exception occurring in the above-mentioned slave node 3, and at least two exception indication fields can include the exception indication field 1 and the exception indication field 2 shown in Figure 7.

[0239] In some possible implementations, the slave nodes may not be divided according to their attributes, or the slave nodes may not be grouped. When a slave node determines that an abnormality has occurred, it may determine whether to report the abnormality based on the frame structure of the uplink frame and / or information carried in the received uplink frame.

[0240] FIG10 shows a schematic flow chart of a communication method provided by an embodiment of the present application. This method 400′ can be executed by the audio system 100 shown in FIG1 , or can also be applied to the audio system shown in FIG2 . For example, the master node can be the master node 112 in FIG1 , and the first slave node can be any one of the slave nodes 120 to 140 in FIG1 . 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 400′ includes:

[0241] S401 ′, the first slave node determines that a first exception occurs.

[0242] For example, the first exception may include the first exception described in method 400 .

[0243] S402', the first slave node sends a first uplink frame, the first uplink frame carries an exception indication field, the exception indication field is used to indicate whether at least two slave nodes send an exception, and the exception indication field carries first exception information, the first exception information indicates that a first exception occurs.

[0244] Exemplarily, the manner in which the first uplink frame carries the abnormality indication field, and the manner in which the first abnormality information is carried through the abnormality indication field, can be described in the corresponding parts of FIG. 5 to FIG. 8 , and will not be repeated here.

[0245] In some possible implementations, the method further includes: receiving an uplink frame, and generating a first uplink frame based on information carried in the uplink frame. For example, when an abnormality occurs in one or more slave nodes located in a downlink of the first slave node, and the uplink frame received by the first slave node carries abnormality information indicating the abnormality of the one or more slave nodes, the first slave node may determine whether to send the first uplink frame or forward the received uplink frame based on the received uplink frame.

[0246] S403': The master node receives the first uplink frame and determines that a first abnormality occurs according to the first abnormality information.

[0247] The communication method provided in the embodiment of the present application can enable slave nodes with different attributes to report exceptions in one uplink frame, increase the chances of slave nodes reporting exceptions, and improve the efficiency of slave nodes reporting exceptions.

[0248] To facilitate understanding of the method 400 ′, the application scenario of the method 400 ′ is introduced below with reference to FIG. 11 and FIG. 12 .

[0249] FIG11 shows a schematic flow chart of a communication method provided in an embodiment of the present application. This method 600 can be executed by the audio system 100 shown in FIG1 , or can also be applied to the audio system shown in FIG2 . For example, the master node can be the master node 112 in FIG1 , and the slave nodes 1 to 3 can be the slave nodes 120 to 140 in FIG1 , respectively. Specifically, the method 600 can include S601 to S612.

[0250] S601 , the master node sends a downlink frame 61 to slave node 1 .

[0251] S602 , slave node 1 sends a downlink frame 61 ′ to slave node 2 .

[0252] S603, slave node 2 sends a downlink frame 61" to slave node 3.

[0253] S604 , slave node 3 sends an uplink frame 61 to slave node 2 .

[0254] S605 , slave node 2 sends an uplink frame 61 ′ to slave node 1 .

[0255] S606, the slave node 1 sends an uplink frame 61" to the master node.

[0256] When no abnormality occurs in slave node 1, slave node 2, or slave node 3, S601 to S606 may be executed. When abnormality occurs in slave node 2 or slave node 3, S606 to S612 may be executed.

[0257] S607 , the master node sends a downlink frame 62 to the slave node 1 .

[0258] S608 , slave node 1 sends a downlink frame 62 ′ to slave node 2 .

[0259] S609, slave node 2 sends a downlink frame 62" to slave node 3.

[0260] S610 , slave node 3 sends an uplink frame 63 to slave node 2 , where the uplink frame 63 indicates that slave node 3 is abnormal.

[0261] S611 , slave node 2 sends an uplink frame 64 to slave node 1 , where the uplink frame 64 indicates that slave node 2 and slave node 3 are abnormal.

[0262] For example, the specific implementation of sending the uplink frame 64 from the node 2 may refer to the relevant description in S518 and will not be repeated here.

[0263] It should be noted that the uplink frame 63 and the uplink frame 64 only indicate that the information carried in the uplink frames may be different, and the sequence numbers of the two are the same.

[0264] S612 , slave node 1 sends an uplink frame 64 ′ to the master node. Uplink frame 64 ′ indicates that slave node 2 and slave node 3 are abnormal.

[0265] For example, the slave node 2 may be considered as an example of the first slave node in the method 400 ′, and the uplink frame 64 may be considered as an example of the first uplink frame in the method 400 ′.

[0266] Optionally, when an exception occurs in the slave node 2, after executing S608, S609'-S610' may be executed.

[0267] S609 ′, slave node 2 sends an uplink frame 62 to slave node 1 , where the uplink frame 62 indicates that slave node 2 is abnormal.

[0268] S610', slave node 1 sends an uplink frame 62' to the master node, and the uplink frame 62' indicates that slave node 2 is abnormal.

[0269] That is, in some implementations, the intermediate slave node may send an uplink frame to report the abnormality upon determining that an abnormality has occurred.

[0270] FIG12 shows a schematic flow chart of a communication method provided by an embodiment of the present application. This method 700 can be executed by the audio system 100 shown in FIG1 , or can also be applied to the audio system shown in FIG2 . For example, the master node can be the master node 112 in FIG1 , and slave nodes 1 to 3 can be slave nodes 120 to 140 in FIG1 , respectively. The structure of the uplink frame in method 700 is illustrated in FIG8 . Specifically, this method 700 can include steps S701 to S712 .

[0271] S701 , the master node sends a downlink frame 71 to slave node 1 , where the downlink frame 71 indicates that the first field of the uplink frame carries uplink information of a specific slave node.

[0272] Exemplarily, field 1 shown in FIG8 is an example of the first field.

[0273] S702 , slave node 1 sends a downlink frame 71 ′ to slave node 2 , where the downlink frame 71 ′ indicates that the first field of the uplink frame carries uplink information of a specific slave node.

[0274] S703 , slave node 2 sends a downlink frame 71 ″ to slave node 3 , where the downlink frame 71 ″ indicates that the first field of the uplink frame carries uplink information of a specific slave node.

[0275] S704 , slave node 3 sends an uplink frame 72 to slave node 2 , where the uplink frame 72 indicates that slave node 3 is abnormal.

[0276] Exemplarily, if the slave node 3 determines that an abnormality occurs, an uplink frame 72 is sent to indicate that the slave node 3 is abnormal.

[0277] S705 , slave node 2 sends an uplink frame 72 ′ to slave node 1 , where the uplink frame 72 ′ indicates that slave node 3 is abnormal.

[0278] Exemplarily, uplink frame 72 includes only one exception indication field, and the exception indication field can only carry one exception indication message. In some implementations, because the first field is indicated to carry uplink information of a specific slave node, even if slave node 2 determines that an exception has occurred, slave node 2 cannot add exception information indicating its own exception to uplink frame 72, and therefore, slave node 2 forwards uplink frame 72.

[0279] S706 , slave node 1 sends an uplink frame 72 ″ to the master node. Uplink frame 72 ″ indicates that slave node 3 is abnormal.

[0280] Optionally, when an exception occurs in the slave node 2, after executing S702, S703'-S704' may be executed.

[0281] S703 ′, slave node 2 sends an uplink frame 71 to slave node 1 , where the uplink frame 71 indicates that slave node 2 is abnormal.

[0282] S704', slave node 1 sends an uplink frame 71' to the master node, and the uplink frame 71' indicates that slave node 2 is abnormal.

[0283] For example, the manner in which uplink frames 71 and 72 indicate slave node abnormality can be described with reference to the above description of the frame structure of uplink frame 1, which will not be repeated here.

[0284] S707 , the master node sends a downlink frame 72 to the slave node 1 , where the downlink frame 72 indicates that the first field of the uplink frame does not carry uplink information of a specific slave node.

[0285] When the downlink frame 72 indicates that the first field of the uplink frame does not carry uplink information of a specific slave node, the first field may be used to carry information indicating an abnormality of the slave node.

[0286] S708 , slave node 1 sends a downlink frame 72 ′ to slave node 2 , where the downlink frame 72 ′ indicates that the first field of the uplink frame does not carry uplink information of a specific slave node.

[0287] S709 , slave node 2 sends a downlink frame 72 ″ to slave node 3 , where the downlink frame 72 ″ indicates that the first field of the uplink frame does not carry uplink information of a specific slave node.

[0288] S710 , slave node 3 sends an uplink frame 74 to slave node 2 , where the uplink frame 74 indicates that slave node 3 is abnormal.

[0289] Exemplarily, if the slave node 3 determines that an abnormality occurs, an uplink frame 74 is sent to indicate that the slave node 3 is abnormal.

[0290] S711 , slave node 2 sends an uplink frame 75 to slave node 1 , where uplink frame 75 indicates that slave node 1 and slave node 3 are abnormal.

[0291] For example, uplink frame 74 includes only one abnormality indication field, which can only carry one abnormality indication message. At this point, the abnormality indication field in uplink frame 74 already carries information indicating an abnormality in slave node 3. When slave node 2 determines that an abnormality has occurred, it can add information indicating its own abnormality to the first field of uplink frame 74 and generate and send uplink frame 75.

[0292] S712 , slave node 1 sends an uplink frame 75 ′ to the master node. Uplink frame 75 ′ indicates that slave node 1 and slave node 3 are abnormal.

[0293] Optionally, when an exception occurs in the slave node 2, after executing S708, S709'-S710' may be executed.

[0294] S709 ′, slave node 2 sends an uplink frame 73 to slave node 1 , where the uplink frame 73 indicates that slave node 2 is abnormal.

[0295] S704', slave node 1 sends an uplink frame 73' to the master node, and the uplink frame 73' indicates that slave node 2 is abnormal.

[0296] Exemplarily, the way in which uplink frame 73 and uplink frame 74 indicate slave node abnormality can refer to the description related to the frame structure of uplink frame 1 mentioned above; the way in which uplink frame 75 indicates slave node abnormality can refer to the description related to the frame structure of uplink frame 6 mentioned above and will not be repeated here.

[0297] It should be noted that the present application does not limit the execution order between S701 to S706 and S707 to S712. For example, S707 to S712 can be executed before S701 to S706.

[0298] It should also be noted that the limitation in the embodiments of the present application that the abnormality indication field can only carry abnormality information indicating an abnormality of one slave node is intended to ensure the clarity of the solution description. In actual implementation, the abnormality indication field in the embodiments of the present application is not limited to carrying abnormality information indicating an abnormality of only one slave node. Moreover, for the implementation method in which the abnormality indication field can carry abnormality information indicating abnormalities of multiple slave nodes, reference can be made to the description in the aforementioned embodiments, for example, the partial description of the frame structure of uplink frame 6 can be referred to above, and no further details will be given here.

[0299] The specific implementation manner in which the first slave node sends the first uplink frame or forwards the received uplink frame or downlink frame according to the received uplink frame, which is not described in detail in methods 600 and 700, can be referred to the description related to S517, S518 and S518' above and will not be repeated here.

[0300] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0301] The communication method provided in the embodiment of the present application is described in detail above with reference to Figures 1 to 12. The communication device provided in the embodiment of the present application will be described in detail below with reference to Figures 13 to 15. It should be understood that the description of the control device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment above, and for the sake of brevity, they will not be repeated here.

[0302] FIG13 shows a schematic block diagram of a communication device 2000 provided in an embodiment of the present application. The device 2000 may include units for executing the operations performed by the slave node in methods 400, 400′, 500, 600, and 700. Furthermore, each unit in the device 2000 is configured to implement a corresponding process in the above method embodiments.

[0303] Specifically, the device 2000 includes a processing unit 2010 and a transceiver unit 2020 .

[0304] When the device 2000 is applied to the method 400, the processing unit 2010 is used to determine that a first exception has occurred; the transceiver unit 2020 is used to send a first uplink frame within a first time period, the first uplink frame carries first exception information, the first exception information indicates that a first exception has occurred, and the first time period is associated with the first slave node.

[0305] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

[0306] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and when an exception occurs in at least one slave node in the first slave node group, the exception is reported within the exception reporting period.

[0307] In some possible implementations, before the transceiver unit 2020 sends the first uplink frame within the first time period, the transceiver unit 2020 is also used to: receive a second uplink frame carrying second exception information, where the second exception information indicates that a second exception has occurred at the second slave node; and send the first uplink frame within the first time period when the reporting priority of the first exception is higher than the reporting priority of the second exception.

[0308] In some possible implementations, the second slave node and the first slave node belong to the same slave node group.

[0309] In some possible implementations, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0310] In some possible implementations, the first uplink frame includes a first abnormality indication field, and the first abnormality indication field carries first abnormality information.

[0311] In some possible implementations, before the transceiver unit 2020 sends the first uplink frame within the first time period, the transceiver unit 2020 is also used to: receive a third uplink frame, the third uplink frame including a second exception indication field and a third exception indication field; when the second exception indication field is not occupied and the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, send the first uplink frame within the first time period; wherein the third exception indication field of the first uplink frame carries the third exception information.

[0312] In some possible implementations, the third slave node and the first slave node belong to the same slave node group, or the third slave node and the first slave node belong to different node groups.

[0313] In some possible implementations, when the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the first exception information, the value of the third exception indication field is a non-specific value.

[0314] In some possible implementations, the transceiver unit 2020 is used to: receive a first downlink frame, the first downlink frame including an indication bit, the indication bit indicating that the first field in the uplink frame is used to carry information about an abnormality in the slave node, or indicating that the first field is used to carry uplink information of a specific slave node.

[0315] Exemplarily, the downlink frames 71 and 72 in the method 700 may be regarded as some examples of the first downlink frame.

[0316] In some possible implementations, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0317] In some possible implementations, before the transceiver unit 2020 sends the first uplink frame within the first time period, the transceiver unit 2020 is also used to: receive a fourth uplink frame, the fourth uplink frame includes a fourth exception indication field, the fourth exception indication field carries fourth exception information, and the fourth exception information indicates that a fourth exception occurs in the fourth slave node; and send the first uplink frame carrying the first exception information and the fourth exception information through the fourth exception indication field within the first time period.

[0318] In some possible implementations, the fourth slave node and the first slave node belong to the same slave node group.

[0319] In some possible implementations, the transceiver unit 2020 is also used to: receive a fifth uplink frame, the fifth uplink frame carries fifth exception information, and the fifth exception information indicates that a fifth exception has occurred in the fifth slave node; when there is no idle field in the fifth uplink frame for carrying the first exception information, send a sixth uplink frame, and the sixth uplink frame carries the fifth exception information.

[0320] In some possible implementations, the fifth uplink frame and the sixth uplink frame include at least one exception indication field and a second field, at least one exception indication field carries fifth exception information, the second field carries sixth exception information, and the sixth exception information indicates that a sixth exception occurs in the sixth slave node; or the second field is used to carry uplink information of a specific slave node.

[0321] In some possible implementations, the fifth uplink frame and the sixth uplink frame include at least two exception indication fields, one of the at least two exception indication fields carries the fifth exception information, and at least one of the remaining fields of the at least two exception indication fields is not occupied. The transceiver unit 2020 is also used to: send the sixth uplink frame when the fifth slave node and the first slave node belong to different slave node groups.

[0322] In some possible implementations, the transceiver unit 2020 is further configured to: send a sixth uplink frame within a second time period, where the second time period is associated with the fifth slave node.

[0323] In some possible implementations, the processing unit 2010 is also used to: determine that a seventh abnormality has occurred in the first slave node; the transceiver unit 2020 is also used to: receive a seventh uplink frame, the seventh uplink frame indicating that an eighth abnormality has occurred in the sixth slave node; when the reporting priority of the seventh abnormality is lower than or equal to the reporting priority of the eighth abnormality, and there is no idle field in the seventh uplink frame for carrying information indicating the seventh abnormality, an eighth uplink frame is sent within a third time period, the eighth uplink frame indicates the eighth abnormality, and the third time period is associated with the first slave node.

[0324] In some possible implementations, the first abnormality includes at least one of the following: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0325] When the device 2000 is applied to the method 400', the processing unit 2010 is used to determine whether a first exception has occurred; the transceiver unit 2020 is used to send a first uplink frame, the first uplink frame carries an exception indication field, the exception indication field is used to indicate whether an exception has occurred in at least two slave nodes, and the exception indication field carries first exception information, the first exception information indicates that a first exception has occurred.

[0326] In some possible implementations, before the transceiver unit 2020 sends the first uplink frame, the transceiver unit 2020 is also used to: receive a third uplink frame, the third uplink frame including a second exception indication field and a third exception indication field; when the second exception indication field carries second exception information indicating that a second exception has occurred in the second slave node, and the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, and when the reporting priority of the first exception is higher than the reporting priority of the second exception, send the first uplink frame; or, when the second exception indication field is not occupied and the third exception indication field carries information indicating a third exception, send the first uplink frame; wherein, the third exception indication field of the first uplink frame carries the third exception information.

[0327] In some possible implementations, when the second exception indication field is not occupied, the value of the second exception indication field is a specific value; when the second exception indication field carries the first exception information or the second exception information, the value of the second exception indication field is a non-specific value.

[0328] In some possible implementations, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0329] In some possible implementations, the transceiver unit 2020 is also used to: receive a first downlink frame, the first downlink frame includes an indication bit, the indication bit indicates that the first field in the uplink frame is used to carry information about an abnormality from the slave node, or indicates that the first field is used to carry uplink information of a specific slave node.

[0330] In some possible implementations, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0331] In some possible implementations, before sending the first uplink frame, the transceiver unit 2020 is also used to: receive a fourth uplink frame, the fourth uplink frame includes a fourth exception indication field, the fourth exception indication field carries fourth exception information, and the fourth exception information indicates that a fourth exception has occurred in the fourth slave node; and send the first uplink frame carrying the first exception information and the fourth exception information through the fourth exception indication field.

[0332] In some possible implementations, the transceiver unit 2020 is further configured to: send a first uplink frame within a first time period, where the first time period is associated with the first slave node.

[0333] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

[0334] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and when an exception occurs in at least one slave node in the first slave node group, the exception is reported within the exception reporting period.

[0335] In some possible implementations, the transceiver unit 2020 is also used to: receive a fifth uplink frame, in which the exception indication fields used to indicate that an exception has occurred from the node are all occupied; when there is no idle field in the fifth uplink frame for carrying the first exception information, send a sixth uplink frame, and the sixth uplink frame carries the fifth exception information.

[0336] In some possible implementations, the reporting priority of the abnormality indicated by the fifth uplink frame is higher than or equal to the reporting priority of the first abnormality.

[0337] In some possible implementations, the first abnormality includes at least one of the following: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0338] FIG14 shows a schematic block diagram of a communication device 2100 provided in an embodiment of the present application. The device 2100 may include units for executing the operations performed by the master node in methods 400, 400′, 500, 600, and 700. Furthermore, each unit in the device 2100 is configured to implement a corresponding process in the above method embodiments.

[0339] Specifically, the device 2100 includes a transceiver unit 2110 and a processing unit 2120 .

[0340] When the device 2100 is applied to the method 400, the transceiver unit 2110 is used to receive a first uplink frame within a first time period, the first uplink frame carries first exception information, the first exception information indicates that a first exception has occurred, and the first time period is associated with the first slave node; the processing unit 2120 is used to determine that a first exception has occurred based on the first exception information.

[0341] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

[0342] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and when an exception occurs in at least one slave node in the first slave node group, the exception is reported within the exception reporting period.

[0343] In some possible implementations, the transceiver unit 2110 is used to: receive a first uplink frame within a first time period when a second exception occurs in the second slave node and the reporting priority of the second exception is lower than the reporting priority of the first exception, and the first slave node and the second slave node belong to the same slave node group.

[0344] In some possible implementations, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0345] In some possible implementations, the first uplink frame includes a first abnormality indication field, and the first abnormality indication field carries first abnormality information.

[0346] In some possible implementations, the first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries first exception information, the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, or the third exception indication field is not occupied.

[0347] In some possible implementations, the third slave node and the first slave node belong to the same slave node group, or the third slave node and the first slave node belong to different node groups.

[0348] In some possible implementations, when the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the third exception information, the value of the third exception indication field is a non-specific value.

[0349] In some possible implementations, the transceiver unit 2110 is also used to: send a first downlink frame, the first downlink frame includes an indication bit, the indication bit indicates that the first field in the uplink frame is used to carry information about an abnormality from the slave node, or indicates that the first field is used to carry uplink information of a specific slave node.

[0350] In some possible implementations, the first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

[0351] In some possible implementations, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0352] In some possible implementations, the transceiver unit 2110 is also used to: receive a sixth uplink frame within a second time period, the sixth uplink frame carries fifth exception information, the fifth exception information indicates that a fifth exception occurs in the fifth slave node, the second time period is associated with the fifth slave node, and the fifth slave node and the first slave node belong to different slave node groups.

[0353] In some possible implementations, the first abnormality includes at least one of the following: an information transmission abnormality of the first slave node, an abnormality of a parameter of the first slave node, and an abnormality of a peripheral device associated with the first slave node.

[0354] When the device 2100 is applied to the method 400', the transceiver unit 2110 is used to receive a first uplink frame, the first uplink frame carries an exception indication field, the exception indication field is used to indicate whether an exception occurs in at least two slave nodes, and the exception indication field carries first exception information, the first exception information indicates that a first exception occurs; the processing unit 2120 is used to determine that a first exception occurs based on the first exception information.

[0355] In some possible implementations, the first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries first exception information, the third exception indication field carries third exception information indicating that a third exception has occurred in the third slave node, or the third exception indication field is not occupied.

[0356] In some possible implementations, when the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the third exception information, the value of the third exception indication field is a non-specific value.

[0357] In some possible implementations, the first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

[0358] In some possible implementations, the transceiver unit 2110 is also used to: send a first downlink frame, the first downlink frame includes an indication bit, the indication bit indicates that the first field in the uplink frame is used to carry information about an abnormality from the slave node, or indicates that the first field is used to carry uplink information of a specific slave node.

[0359] In some possible implementations, the first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

[0360] In some possible implementations, the fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits corresponding to the at least one slave node in the P bits respectively take the first value, and the remaining bits in the P bits take the second value, and P is an integer greater than or equal to 2.

[0361] In some possible implementations, the transceiver unit 2110 is further configured to: receive a first uplink frame within a first time period, where the first time period is associated with the first slave node.

[0362] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is determined based on the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

[0363] In some possible implementations, the first time period is associated with the first slave node, including: the first time period is included in the exception reporting period of the first slave node group, the first slave node group includes the first slave node, and when an exception occurs in at least one slave node in the first slave node group, the exception is reported within the exception reporting period.

[0364] For example, the apparatus 2000 may be provided in any of the slave nodes 122, 132, and 142 shown in FIG1 . Alternatively, the apparatus 2000 may be provided in any of the audio devices 120 to 140 shown in FIG3 . The operations performed by the processing unit 2010 and the transceiver unit 2020 may be performed by a single processor, or by different processors. In a specific implementation, the one or more processors may be provided in the audio device; alternatively, the apparatus 2000 may be a chip provided in the audio device.

[0365] For example, the apparatus 2100 may be provided in the master node 112 shown in FIG1 . Alternatively, the apparatus 2100 may be provided in the audio device control device 110 shown in FIG3 . The operations performed by the transceiver unit 2110 and the processing unit 2120 may be performed by a single processor, or by different processors. In a specific implementation, the one or more processors may be provided in the audio control device; alternatively, the apparatus 2100 may be a chip provided in the audio control device.

[0366] In this application, a processor is a circuit with the ability to process signals. In one implementation, the processor can be a circuit with the ability to read and run instructions, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field programmable gate array (FPGA). In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, the processor can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0367] In a specific implementation process, the various units in the above apparatus may be fully or partially integrated together, or may also be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SoC).

[0368] Figure 15 is a schematic block diagram of a communication device provided in an embodiment of the present application. The communication device 2200 shown in Figure 15 may include: a processor 2210, a transceiver 2220, and a memory 2230. The processor 2210, the transceiver 2220, and the memory 2230 are connected via an internal connection path. The memory 2230 is used to store instructions, and the processor 2210 is used to execute the instructions stored in the memory 2230 to implement the methods in the above embodiments. Optionally, the memory 2230 can be coupled to the processor 2210 via an interface or integrated with the processor 2210.

[0369] It should be noted that the transceiver 2220 may include but is not limited to a transceiver device such as an input / output interface to implement communication between the device 2200 and other devices or a communication network.

[0370] The memory 2230 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).

[0371] The transceiver 2220 uses a transceiver device such as but not limited to a transceiver to implement communication between the device 2200 and other devices or communication networks to receive / send data / information used to implement the methods in the above embodiments.

[0372] An embodiment of the present application further provides a communication system, which includes apparatus 2000 and apparatus 2100 ; or the communication system includes apparatus 2200 .

[0373] An embodiment of the present application also provides a vehicle, which includes the above-mentioned device 2000 and device 2100, or the vehicle includes device 2200, or the vehicle also includes the above-mentioned communication system.

[0374] The vehicles involved in this application may include road vehicles, water vehicles, air vehicles, industrial equipment, agricultural equipment, or entertainment equipment, etc. The vehicle can be a vehicle in a broad sense, and can be a transportation vehicle (such as a commercial vehicle, a passenger car, a motorcycle, an air vehicle, a train, etc.), an industrial vehicle (such as a forklift, a trailer, a tractor, etc.), an engineering vehicle (such as an excavator, a bulldozer, a crane, etc.), agricultural equipment (such as a lawn mower, a harvester, etc.), amusement equipment, a toy vehicle, etc. The embodiments of this application do not specifically limit the type of vehicle.

[0375] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer implements the methods in the above embodiments of the present application.

[0376] An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the computer implements the methods in the above embodiments of the present application.

[0377] An embodiment of the present application also provides a chip, including a circuit, for executing the methods in the above embodiments of the present application.

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

[0379] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is a kind of association relationship that describes associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In this application, "at least one" refers to one or more, and "more than one" refers to two or more. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0380] In the embodiments of this application, prefixes such as "first" and "second" are used only to distinguish different description objects and have no limiting effect on the position, order, priority, quantity, or content of the described objects. The use of prefixes such as ordinal numbers in the embodiments of this application to distinguish description objects does not constitute a limitation on the described objects. For a statement of the described objects, please refer to the description in the context of the claims or embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

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

[0382] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0383] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0384] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0385] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: Applied to the first slave node, the method comprises: determining that a first exception occurs, the first exception being associated with the first slave node; A first uplink frame is sent within a first time period, the first uplink frame carries first exception information, the first exception information indicates that the first exception occurs, and the first time period is associated with the first slave node.

2. The method according to claim 1, characterized in that The first time period is associated with the first slave node, including: the first time period is determined according to the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

3. The method according to claim 1 or 2, characterized in that: The first time period is associated with the first slave node, including: the first time period is included in the abnormality reporting period of the first slave node group, the first slave node group includes the first slave node, and when an abnormality occurs to at least one slave node in the first slave node group, the abnormality is reported within the abnormality reporting period.

4. The method according to any one of claims 1 to 3, characterized in that Before sending the first uplink frame within the first time period, the method further includes: receiving a second uplink frame carrying second abnormal information, where the second abnormal information indicates that a second abnormality occurs in the second slave node; The sending of the first uplink frame within the first time period includes: When the reporting priority of the first exception is higher than the reporting priority of the second exception, the first uplink frame is sent within the first time period.

5. The method according to claim 4, characterized in that The second slave node and the first slave node belong to the same slave node group.

6. The method according to any one of claims 1 to 5, characterized in that The first uplink frame includes a first abnormality indication field, and the first abnormality indication field carries the first abnormality information.

7. The method according to any one of claims 1 to 3, characterized in that The first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries the first exception information, the third exception indication field is not occupied or the third exception indication field carries third exception information indicating that a third exception occurs in the third slave node.

8. The method according to claim 7, characterized in that Before sending the first uplink frame within the first time period, the method further includes: receiving a third uplink frame, wherein the third uplink frame includes the second abnormality indication field and the third abnormality indication field; The sending of the first uplink frame within the first time period includes: When the second abnormality indication field is not occupied and the third abnormality indication field carries the third abnormality information, sending the first uplink frame within the first time period; Among them, the third abnormality indication field of the first uplink frame carries the third abnormality information.

9. The method according to claim 7 or 8, characterized in that: The third slave node and the first slave node belong to the same slave node group, or the third slave node and the first slave node belong to different node groups.

10. The method according to any one of claims 7 to 9, characterized in that When the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the first exception information, the value of the third exception indication field is a non-specific value.

11. The method according to any one of claims 6 to 10, characterized in that The method further comprises: A first downlink frame is received, wherein the first downlink frame includes an indication bit, wherein the indication bit indicates that a first field in an uplink frame is used to carry information about an abnormal slave node, or indicates that the first field is used to carry uplink information of a specific slave node.

12. The method according to any one of claims 1 to 3, characterized in that The first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

13. The method according to claim 12, characterized in that The fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits of the P bits corresponding to the at least one slave node respectively take a first value, and the remaining bits of the P bits take a second value, and P is an integer greater than or equal to 2.

14. The method according to claim 12 or 13, characterized in that Before sending the first uplink frame within the first time period, the method further includes: receiving a fourth uplink frame, the fourth uplink frame including the fourth abnormality indication field, the fourth abnormality indication field carrying fourth abnormality information, the fourth abnormality information indicating that a fourth abnormality occurs in the fourth slave node; The sending of the first uplink frame within the first time period includes: The first uplink frame carrying the first abnormality information and the fourth abnormality information through the fourth abnormality indication field is sent within the first time period.

15. The method according to claim 14, characterized in that The fourth slave node and the first slave node belong to the same slave node group.

16. The method according to any one of claims 1 to 15, characterized in that The method further comprises: receiving a fifth uplink frame, the fifth uplink frame carrying fifth abnormality information, the fifth abnormality information indicating that a fifth abnormality occurs in the fifth slave node; When there is no idle field in the fifth uplink frame for carrying the first abnormality information, a sixth uplink frame is sent, and the sixth uplink frame carries the fifth abnormality information.

17. The method according to claim 16, characterized in that The fifth uplink frame and the sixth uplink frame include at least one exception indication field and a second field, the at least one exception indication field carries the fifth exception information, the second field carries sixth exception information, and the sixth exception information indicates that a sixth exception occurs in a sixth slave node; or the second field is used to carry uplink information of a specific slave node.

18. The method according to claim 16, characterized in that The fifth uplink frame and the sixth uplink frame include at least two abnormality indication fields, one of the at least two abnormality indication fields carries the fifth abnormality information, at least one of the remaining fields of the at least two abnormality indication fields is not occupied, and sending the sixth uplink frame includes: When the fifth slave node and the first slave node belong to different slave node groups, the sixth uplink frame is sent.

19. The method according to any one of claims 16 to 18, characterized in that The sending of the sixth uplink frame comprises: The sixth uplink frame is sent in a second time period, where the second time period is associated with the fifth slave node.

20. The method according to any one of claims 1 to 19, characterized in that The method further comprises: Determining that a seventh abnormality occurs in the first slave node; receiving a seventh uplink frame, wherein the seventh uplink frame indicates that an eighth abnormality occurs in the sixth slave node; When the reporting priority of the seventh exception is lower than or equal to the reporting priority of the eighth exception, and there is no idle field in the seventh uplink frame for carrying information indicating the seventh exception, an eighth uplink frame is sent within a third time period, the eighth uplink frame indicates the eighth exception, and the third time period is associated with the first slave node.

21. The method according to any one of claims 1 to 20, characterized in that The first anomaly includes at least one of the following: The information transmission of the first slave node is abnormal, the parameters of the first slave node are abnormal, and the peripheral device associated with the first slave node is abnormal.

22. The method according to any one of claims 1 to 21, characterized in that The first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

23. A communication method, characterized in that: Applied to the first slave node, the method comprises: determining that a first exception occurs, the first exception being associated with the first slave node; A first uplink frame is sent, wherein the first uplink frame carries an exception indication field, wherein the exception indication field is used to indicate whether an exception occurs in at least two slave nodes, and the exception indication field carries first exception information, wherein the first exception information indicates that the first exception occurs.

24. The method according to claim 23, characterized in that The first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries the first exception information, the third exception indication field is not occupied or the third exception indication field carries third exception information indicating that a third exception occurs in the third slave node.

25. The method according to claim 24, characterized in that Before sending the first uplink frame, the method further includes: receiving a third uplink frame, wherein the third uplink frame includes the second abnormality indication field and the third abnormality indication field; The sending of the first uplink frame comprises: When the second abnormality indication field carries second abnormality information indicating that a second abnormality occurs in the second slave node, and the third abnormality indication field carries the third abnormality information, and when the reporting priority of the first abnormality is higher than the reporting priority of the second abnormality, sending the first uplink frame; or, When the second abnormality indication field is not occupied and the third abnormality indication field carries the third abnormality information, sending the first uplink frame; Among them, the third abnormality indication field of the first uplink frame carries the third abnormality information.

26. The method according to claim 24 or 25, characterized in that When the second exception indication field is not occupied, the value of the second exception indication field is a specific value; when the second exception indication field carries the first exception information or the second exception information, the value of the second exception indication field is a non-specific value.

27. The method according to any one of claims 23 to 26, characterized in that The method further comprises: A first downlink frame is received, wherein the first downlink frame includes an indication bit, wherein the indication bit indicates that a first field in an uplink frame is used to carry information about an abnormal slave node, or indicates that the first field is used to carry uplink information of a specific slave node.

28. The method according to claim 23, characterized in that The first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

29. The method according to claim 28, characterized in that The fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits of the P bits corresponding to the at least one slave node respectively take a first value, and the remaining bits of the P bits take a second value, and P is an integer greater than or equal to 2.

30. The method according to claim 28 or 29, characterized in that Before sending the first uplink frame, the method further includes: receiving a fourth uplink frame, the fourth uplink frame comprising a fourth abnormality indication field, the fourth abnormality indication field carrying fourth abnormality information, the fourth abnormality information indicating that a fourth abnormality occurs in a fourth slave node; The sending of the first uplink frame comprises: The first uplink frame carrying the first abnormality information and the fourth abnormality information through the fourth abnormality indication field is sent.

31. The method according to any one of claims 23 to 30, characterized in that The sending of the first uplink frame comprises: The first uplink frame is sent in a first time period, where the first time period is associated with the first slave node.

32. The method according to claim 31, characterized in that The first time period is associated with the first slave node, including: the first time period is determined according to the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

33. The method according to claim 31 or 32, characterized in that The first time period is associated with the first slave node, including: the first time period is included in the abnormality reporting period of the first slave node group, the first slave node group includes the first slave node, and when an abnormality occurs to at least one slave node in the first slave node group, the abnormality is reported within the abnormality reporting period.

34. The method according to any one of claims 23 to 33, characterized in that The method further comprises: receiving a fifth uplink frame, wherein all abnormality indication fields in the fifth uplink frame for indicating that an abnormality has occurred in a slave node are occupied; When there is no idle field in the fifth uplink frame for carrying the first abnormality information, a sixth uplink frame is sent, and the sixth uplink frame carries the fifth abnormality information.

35. The method according to claim 34, characterized in that The reporting priority of the abnormality indicated by the fifth uplink frame is higher than or equal to the reporting priority of the first abnormality.

36. The method according to any one of claims 23 to 35, characterized in that The first anomaly includes at least one of the following: The information transmission of the first slave node is abnormal, the parameters of the first slave node are abnormal, and the peripheral device associated with the first slave node is abnormal.

37. The method according to any one of claims 23 to 36, characterized in that The first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

38. A communication method, characterized in that: include: receiving a first uplink frame within a first time period, the first uplink frame carrying first exception information, the first exception information indicating that a first exception occurs, the first exception is associated with a first slave node, and the first time period is associated with the first slave node; The occurrence of the first exception is determined according to the first exception information.

39. The method according to claim 38, characterized in that The first time period is associated with the first slave node, including: the first time period is determined according to the attributes of the first slave node, and the attributes include at least one of the following: the identification of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

40. The method according to claim 38 or 39, characterized in that The first time period is associated with the first slave node, including: the first time period is included in the abnormality reporting period of the first slave node group, the first slave node group includes the first slave node, and when an abnormality occurs to at least one slave node in the first slave node group, the abnormality is reported within the abnormality reporting period.

41. The method according to any one of claims 38 to 40, characterized in that The receiving a first uplink frame within a first time period includes: When a second exception occurs in the second slave node and the reporting priority of the second exception is lower than the reporting priority of the first exception, the first uplink frame is received within the first time period, and the first slave node and the second slave node belong to the same slave node group.

42. The method according to any one of claims 38 to 41, characterized in that The first uplink frame includes a first abnormality indication field, and the first abnormality indication field carries the first abnormality information.

43. The method according to any one of claims 38 to 40, characterized in that The first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries the first exception information, the third exception indication field carries third exception information indicating that a third exception occurs in a third slave node, or the third exception indication field is not occupied.

44. The method according to claim 43, characterized in that The third slave node and the first slave node belong to the same slave node group, or the third slave node and the first slave node belong to different node groups.

45. The method according to claim 43 or 44, characterized in that When the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the third exception information, the value of the third exception indication field is a non-specific value.

46. ​​The method according to any one of claims 42 to 45, characterized in that The method further comprises: A first downlink frame is sent, wherein the first downlink frame includes an indication bit, wherein the indication bit indicates that a first field in an uplink frame is used to carry information about an abnormal slave node, or indicates that the first field is used to carry uplink information of a specific slave node.

47. The method according to any one of claims 38 to 40, characterized in that The first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

48. The method according to claim 47, characterized in that The fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information that at least one slave node is abnormal, the bits of the P bits corresponding to the at least one slave node respectively take a first value, and the remaining bits of the P bits take a second value, and P is an integer greater than or equal to 2.

49. The method according to any one of claims 38 to 48, characterized in that The method further comprises: A sixth uplink frame is received within a second time period, the sixth uplink frame carrying fifth exception information, the fifth exception information indicating that a fifth exception occurs in a fifth slave node, the second time period is associated with the fifth slave node, and the fifth slave node and the first slave node belong to different slave node groups.

50. The method according to any one of claims 38 to 49, characterized in that The first anomaly includes at least one of the following: The information transmission of the first slave node is abnormal, the parameters of the first slave node are abnormal, and the peripheral device associated with the first slave node is abnormal.

51. The method according to any one of claims 38 to 50, characterized in that The first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

52. A communication method, characterized in that: include: Receive a first uplink frame, the first uplink frame carries an exception indication field, the exception indication field is used to indicate whether an exception occurs in at least two slave nodes, and the exception indication field carries first exception information, the first exception information indicates that a first exception occurs, and the first exception is associated with the first slave node; The occurrence of the first exception is determined according to the first exception information.

53. The method according to claim 52, characterized in that The first uplink frame includes a second exception indication field and a third exception indication field, the second exception indication field carries the first exception information, the third exception indication field carries third exception information indicating that a third exception occurs in a third slave node, or the third exception indication field is not occupied.

54. The method according to claim 53, characterized in that When the third exception indication field is not occupied, the value of the third exception indication field is a specific value; when the third exception indication field carries the third exception information, the value of the third exception indication field is a non-specific value.

55. The method according to any one of claims 52 to 54, characterized in that The method further comprises: A first downlink frame is sent, wherein the first downlink frame includes an indication bit, wherein the indication bit indicates that a first field in an uplink frame is used to carry information about an abnormal slave node, or indicates that the first field is used to carry uplink information of a specific slave node.

56. The method according to claim 52, characterized in that The first uplink frame includes a fourth abnormality indication field, the fourth abnormality indication field carries the first abnormality information, and the fourth abnormality indication field is also used to carry information about other slave node abnormalities.

57. The method according to claim 56, characterized in that The fourth abnormality indication field carries P bits, each of the P bits corresponds to a slave node; when the fourth abnormality indication field carries information about at least one abnormal slave node, the bits of the P bits corresponding to the at least one slave node respectively take a first value, and the remaining bits of the P bits take a second value, and P is an integer greater than or equal to 2.

58. The method according to any one of claims 52 to 57, characterized in that The receiving of the first uplink frame comprises: The first uplink frame is received within a first time period, where the first time period is associated with the first slave node.

59. The method according to claim 58, characterized in that The first time period is associated with the first slave node, including: the first time period is determined according to the attributes of the first slave node, and the attributes include at least one of the following: the identifier of the first slave node, the service type of the first slave node, and the topological position of the first slave node.

60. The method according to claim 58 or 59, characterized in that The first time period is associated with the first slave node, including: the first time period is included in the abnormality reporting period of the first slave node group, the first slave node group includes the first slave node, and when an abnormality occurs to at least one slave node in the first slave node group, the abnormality is reported within the abnormality reporting period.

61. The method according to any one of claims 52 to 60, characterized in that The first anomaly includes at least one of the following: The information transmission of the first slave node is abnormal, the parameters of the first slave node are abnormal, and the peripheral device associated with the first slave node is abnormal.

62. The method according to any one of claims 52 to 61, characterized in that The first exception information further indicates a reporting priority of the first exception and / or a type of the first exception.

63. A communication device, characterized in that: The device comprises a processing unit and a transceiver unit, and is used to execute the method according to any one of claims 1 to 37.

64. A communication device, characterized in that: The device comprises a transceiver unit and a processing unit, and is used to execute the method as claimed in any one of claims 38 to 62.

65. A communication device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute a computer program stored in the memory so that the control device performs the method as claimed in any one of claims 1 to 37.

66. A communication device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute a computer program stored in the memory so that the control device performs the method as claimed in any one of claims 38 to 62.

67. A communication system, characterized in that: Includes the device as described in claims 63 and 64; or, includes the device as described in claims 65 and 66.

68. A vehicle, characterized in that: Includes the apparatus as described in claims 63 and 64; or, includes the apparatus as described in claims 65 and 66; or, includes the system as described in claim 67.

69. A computer-readable storage medium, characterized in that Instructions are stored thereon, and when the instructions are executed by a processor, the processor implements the method according to any one of claims 1 to 62.

70. A chip, characterized in that: The chip comprises circuitry for performing the method of any one of claims 1 to 62.

Images