CN111935727B

CN111935727B - Communication exception handling method, master node, indoor distribution system and storage medium

Info

Publication number: CN111935727B
Application number: CN202010662370.7A
Authority: CN
Inventors: 宋松伟; 陈加轩
Original assignee: Spreadtrum Semiconductor Chengdu Co Ltd
Current assignee: Spreadtrum Semiconductor Chengdu Co Ltd
Priority date: 2020-07-10
Filing date: 2020-07-10
Publication date: 2023-01-31
Anticipated expiration: 2040-07-10
Also published as: CN111935727A; CN116016140A

Abstract

The embodiment of the invention provides a communication exception handling method, a main node, an indoor distribution system and a storage medium, wherein the communication exception handling method comprises the following steps: determining a slave node with abnormal communication behaviors based on a preset communication behavior matching condition; triggering an abnormal slave node release instruction, deleting handshake information of the slave node with the abnormal communication behavior, and releasing the node identification of the slave node with the abnormal communication behavior; sending a first re-handshake message to the slave node with abnormal communication behavior; waiting for receiving a second re-handshake message sent by the slave node having abnormal communication behavior in response to the first re-handshake message. The embodiment of the invention can process the abnormal communication behavior of the slave node in time and improve the stability and reliability of communication interaction between the master node and the slave node.

Description

Communication exception handling method, master node, indoor distribution system and storage medium

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a communication exception handling method, a main node, an indoor distribution system and a storage medium.

Background

In indoor environments such as large buildings, underground shopping malls, underground parking lots and the like, mobile communication signals are weak, blind areas and shadow areas of mobile communication are easily formed, and terminals such as mobile phones and the like using the mobile communication signals cannot be normally used. Currently, an indoor distribution system can be used for improving mobile communication signals in an indoor environment, and the mobile communication signals of a signal source (such as a base station) can be uniformly distributed at each corner indoors by using the indoor distribution system, so that ideal signal coverage is ensured in the indoor environment.

The indoor distribution system mainly comprises a main node and a plurality of slave nodes accessed to the main node, wherein the main node is connected with the information source and can send the mobile communication signals of the information source to the slave nodes, and therefore the slave nodes can process the received mobile communication signals and send the processed mobile communication signals to the air interface to complete the coverage of the mobile communication signals in the indoor environment.

In the operation process of an indoor distributed system, a master node can communicate with a plurality of slave nodes, various abnormal communication conditions may be generated, and the problem of abnormal system operation is caused.

Disclosure of Invention

In view of this, embodiments of the present invention provide a communication exception handling method, a master node, an indoor distribution system, and a storage medium, which can handle an exception communication behavior of a slave node in time, and improve stability and reliability of communication interaction between the master node and the slave node.

In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:

a communication exception handling method is applied to a master node, the master node establishes communication connection with a slave node through a handshake process, and the communication exception handling method comprises the following steps:

determining a slave node with abnormal communication behaviors based on a preset communication behavior matching condition;

triggering an abnormal slave node release instruction, deleting handshake information of the slave node with the abnormal communication behavior, and releasing the node identification of the slave node with the abnormal communication behavior;

sending a first re-handshake message to the slave node with abnormal communication behavior;

waiting for receiving a second re-handshake message sent by the slave node having abnormal communication behavior in response to the first re-handshake message.

The embodiment of the present invention further provides a communication exception handling method, which is applied to an indoor distribution system, where the indoor distribution system includes a master node and a slave node, the master node establishes a communication connection with the slave node through a handshake process, and the communication exception handling method includes:

the master node determines a slave node with abnormal communication behavior based on a preset communication behavior matching condition;

the master node triggers an abnormal slave node release instruction and deletes handshake information of the slave node with the abnormal communication behavior;

the master node sends a first re-handshake message to the slave node with abnormal communication behavior;

and the slave node with the abnormal communication behavior responds to the first re-handshake message sent by the master node, enters an access state, and sends a second re-handshake message to the master node to reinitiate a handshake process.

An embodiment of the present invention further provides a master node, including:

the handshake module is used for executing a handshake process to establish communication connection with the slave node;

the abnormal slave node detection module is used for determining the slave node with the abnormal communication behavior according to the preset communication behavior matching condition;

the abnormal slave node releasing module is used for deleting the handshake information of the slave node with the abnormal communication behavior according to a triggered abnormal slave node releasing instruction and releasing the node identification of the slave node with the abnormal communication behavior;

the message sending module is used for sending a first re-handshake message to the slave node with the abnormal communication behavior;

and the message receiving module is used for receiving a second re-handshake message sent by the slave node with abnormal communication behavior in response to the first re-handshake message.

The embodiment of the present invention further provides an indoor distribution system, including a master node and a slave node, where the master node establishes a communication connection with the slave node through a handshake process, where:

the master node is used for determining a slave node with abnormal communication behavior based on a preset communication behavior matching condition, triggering an abnormal slave node release instruction, deleting handshake information of the slave node with abnormal communication behavior, sending a first re-handshake message to the slave node with abnormal communication behavior, and waiting for receiving a second re-handshake message sent by the slave node with abnormal communication behavior in response to the first re-handshake message;

and the slave node is used for responding to the first re-handshake message sent by the master node and sending a second re-handshake message to the master node so as to reinitiate a handshake process.

An embodiment of the present invention further provides a master node, including: a memory storing one or more computer-executable instructions and a processor invoking the one or more computer-executable instructions to perform a communication exception handling method as described above.

The embodiment of the invention also provides an indoor distribution system, which comprises a plurality of slave nodes and the master node, wherein the master node establishes communication connection with the slave nodes through a handshake process.

An embodiment of the present invention further provides a storage medium, where the storage medium stores one or more computer-executable instructions, and the one or more computer-executable instructions are configured to execute the communication exception handling method described above.

According to the communication abnormity processing method provided by the embodiment of the invention, after the slave node with abnormal communication behaviors is determined according to the preset communication behavior matching condition, the abnormal slave node release instruction is triggered, the handshake information of the slave node with abnormal communication behaviors can be deleted, so that the node identification of the slave node with abnormal communication behaviors is released, the binding relationship between the node identification and the slave node with abnormal communication behaviors is removed, the master node and the slave node with abnormal communication behaviors are disconnected in communication, and a first re-handshake message is sent to the slave node with abnormal communication behaviors to request the slave node with abnormal communication behaviors to reinitiate a handshake flow, so that the slave node with abnormal communication behaviors can respond to the first re-handshake message, so that the slave node with abnormal communication behaviors can be re-accessed in the slave node with abnormal communication behaviors through the handshake flow, the normal communication behaviors of the slave node are ensured to be recovered, and therefore, by adopting the method, in the communication interaction process of the master node and the slave node, the problem of communication abnormity can be automatically detected and solved, manual troubleshooting is not needed, the troubleshooting efficiency is improved, the abnormal communication behaviors of the slave node are processed in time, and the stability and the reliability of the communication interaction between the master node and the slave node are ensured.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a block diagram of an indoor distribution system provided by an embodiment of the present invention;

fig. 2 is a diagram illustrating a communication status of an indoor distribution system according to an embodiment of the present invention;

fig. 3 is a flowchart of a communication exception handling method according to an embodiment of the present invention;

fig. 4 is a flowchart of another communication exception handling method according to an embodiment of the present invention;

fig. 5 is a flowchart of a communication exception handling method according to another embodiment of the present invention;

fig. 6 is a block diagram of a host node according to an embodiment of the present invention;

fig. 7 is a block diagram of another host node according to an embodiment of the present invention;

fig. 8 is a block diagram of another master node according to an embodiment of the present invention.

Detailed Description

Currently, the coverage of a 4G (fourth generation mobile communication technology) network, such as an LTE (Long Term Evolution) network, is relatively perfect. In urban application environments, due to the rapid increase of users and the increase of high-rise buildings, the telephone traffic density and the coverage requirement are continuously increased, and indoor distribution systems for improving mobile communication signals are generally deployed in indoor environments such as large buildings, underground shopping malls, underground parking lots and the like in order to avoid dead zones and shadow zones of mobile communication.

However, with the advance of 5G (fifth generation mobile communication technology) network construction, the wireless signal characteristics of the 5G network itself makes higher demands for coverage of mobile communication signals in indoor environments, and in the 5G network, an indoor distribution system may have more slave nodes and perform more complex wireless communication, so in the field of mobile communication signal improvement of indoor environments, how to fully utilize the existing indoor distribution system, reduce the cost of 5G network construction and maintenance, and improve the coverage of the 5G network in indoor environments becomes a major issue. In this problem, how to find and solve the communication abnormality is a problem that needs to be solved.

As shown in fig. 1, the indoor distribution system may include a master node 10 and a plurality of slave nodes 21 to 2N, where N is a natural number not less than 1.

The master node 10 is connected with the information source, and transmits the mobile communication signal of the information source to at least one of the slave nodes 21 to 2N, and at least one of the slave nodes 21 to 2N processes the received mobile communication signal and transmits the processed signal to the air interface, thereby completing the coverage of the mobile communication signal in the indoor environment.

In order to coordinate the work of the master node and the slave node, when the slave node requests to access the master node, the master node and the slave node need to perform a handshake flow, in order to identify different slave nodes in an indoor distribution system, the master node identifies and manages the slave nodes, and the handshake flow needs to be implemented based on node identification (such as a node number) of the slave node; at present, when the slave nodes are installed, non-conflicting fixed node identifiers are set for each slave node of an indoor distribution system, and the fixed node identifiers need to be manually set in the process, so that a handshake process is performed between a master node and the slave nodes based on the fixed node identifiers set in advance by the slave nodes.

And after the handshake process is completed, the master node and the slave node establish communication connection. Because the master node can communicate and interact with a plurality of slave nodes, various abnormal communication conditions can be generated, and the problem of abnormal system operation is caused, at the moment, abnormal communication equipment can be positioned and maintained only in a manual troubleshooting mode, in order to not influence the work of other normal nodes, the communication interaction between the abnormal communication nodes and the normal nodes cannot be stopped in the process of detecting the abnormal communication nodes, in addition, a large number of nodes existing in the 5G network environment can improve the complexity of manual troubleshooting, the workload is greatly increased, the troubleshooting efficiency is reduced, and the communication risk is improved.

In order to solve the above problem, embodiments of the present invention provide a communication exception handling scheme, which can automatically detect and solve the problem of communication exception during a communication interaction between a master node and a slave node, and does not need manual troubleshooting, thereby improving troubleshooting efficiency, handling an exception communication behavior of the slave node in time, and effectively ensuring stability and reliability of communication interaction between the master node and the slave node.

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.

In an alternative implementation, after the indoor distribution system completes the cell search, its communication status may be as illustrated in fig. 2, including:

the method comprises the following steps that (Init State), after an indoor distribution system is started and network searching is completed, a master node and a slave node enter an initialization State to complete necessary initialization operation;

the method comprises the following steps that a Master Boot State (Master Boot State) is adopted, a Master node enters the Master Boot State after initialization is completed, and the Master Boot State is mainly used for broadcasting and informing that the Master node is restarted after some restarting operations of the Master node under the condition that a slave node does not know are processed;

waiting for a downlink heartbeat State (Wait DL Heart State), and entering a downlink heartbeat waiting State after the slave node completes initialization so as to Wait for a heartbeat message of the master node;

the method comprises the following steps that (1) an access State (RACH State) is obtained, and in the State, a slave node requests to access a master node;

a Normal working State (Normal State), in which the master node broadcasts and sends a heartbeat message to the slave node and completes a handshake process; after finishing the handshake process in the access state, the slave node enters a normal working state; and after the master node and the slave node are in a normal working state, the indoor distribution system works normally.

As can be seen from the communication state illustrated in fig. 2, after receiving the heartbeat message of the master node, the slave node enters an access state and performs a handshake process with the master node, and when the handshake is successful, the slave node obtains the allocated node identifier and the master node establishes a communication connection with the slave node, the indoor distribution system enters a normal working state.

It should be noted that the heartbeat message of the master node is only an optional message form that triggers the slave node to enter the access state, and in the embodiment of the present invention, the slave node may also receive a master handshake message specific to the master node after initialization, so as to enter the access state, and the heartbeat message of the master node is only an optional form of the master handshake message, and the embodiment of the present invention does not limit other forms of the master handshake message.

In an optional implementation, in an embodiment of the present invention, the master node may detect a communication behavior of the slave node in a normal working state, and may perform communication exception handling after finding that the communication behavior of the slave node is abnormal, and optionally, fig. 3 shows a flowchart of a communication exception handling method provided in the embodiment of the present invention. After the master node establishes a communication connection with the slave node through the handshake process, the process of the communication exception handling method shown in fig. 3 may be executed, which specifically includes:

and S30, determining the slave node with the abnormal communication behavior based on the preset communication behavior matching condition.

Alternatively, in actual operation, a node close to the information source may be selected as the master node, and a node far from the information source may be selected as the slave node, and the indoor distribution system may include a plurality of master nodes and a plurality of slave nodes connected to the master nodes.

In an example, whether the distance between the node and the source is smaller than a distance threshold value can be determined through a preset distance threshold value, if so, the node can be used as a master node, otherwise, the node is used as a slave node.

In another example, X nodes with the smallest distance may be selected as the master node and the other nodes as the slave nodes by comparing the distance between each node and the source, where X is a natural number not less than 1.

Step S31, triggering an abnormal slave node release instruction, deleting the handshake information of the slave node with the abnormal communication behavior, and releasing the node identification of the slave node with the abnormal communication behavior.

In an example, when the master node and the slave node perform a handshake procedure, the master node may select a node identifier for the slave node, and if the selected node identifier is not occupied, the selected node identifier may be used as the available node identifier, and send a handshake confirmation message to the slave node, where the handshake confirmation message includes the available node identifier. In addition, the master node may further store, in a preset storage area, handshake information for performing a handshake process with the slave node, where the handshake information may include node identification record information of the slave node, and the node identification record information may record an available node identification currently selected by the master node as the slave node.

After triggering an abnormal slave node release instruction, the deleting handshake information of the slave node with the abnormal communication behavior, and releasing the node identification of the slave node with the abnormal communication behavior may specifically include: deleting the node identification record information of the slave node with the abnormal communication behavior, and setting the node identification of the slave node with the abnormal communication behavior as unoccupied. Therefore, when the master node selects the node identifier for other slave nodes, if the node identifier is selected, the node identifier can be allocated to other slave nodes as an available node identifier because the node identifier is set to be unoccupied.

For example, when the node identification a of the slave node a having abnormal communication behavior is set as a and the node identification a is set as unoccupied, the node identification a may be assigned to the slave node B as an available node identification when the master node performs handshake with the slave node B.

Therefore, whether the node identifier is available or not is determined according to the occupation state of the node identifier, so that the node identifier and the slave node are not fixedly bound, and flexible multiplexing of the node identifier is realized.

And step S32, sending a first re-handshake message to the slave node with the abnormal communication behavior.

And step S33, waiting for receiving a second re-handshake message sent by the slave node with abnormal communication behavior in response to the first re-handshake message.

In one example, the slave node sends a second re-handshake message to the master node in response to the first re-handshake message, thereby re-initiating the handshake flow with the master node. After receiving the second re-handshake message sent by the slave node with the abnormal communication behavior, the master node responds to the received second re-handshake message to re-select a node identifier for the slave node, and if the re-selected node identifier is not occupied, the re-selected node identifier can be used as the available node identifier, so that the available node identifier is re-successfully allocated to the slave node with the abnormal communication behavior, and a re-handshake confirmation message is sent to the slave node with the abnormal communication behavior.

Wherein the re-handshake confirmation message includes available node identification for re-successful allocation, the available node identification being used to reset the node identification of the slave node having abnormal communication behavior.

It is to be understood that the prefixes of "first," "second," etc., in the embodiments of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined in terms of "first," "second," etc. may explicitly or implicitly include one or more of that feature. Moreover, the terms "first," "second," and the like are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. And the terms so used are interchangeable under appropriate circumstances such that the embodiments of the specification described herein are capable of operation in other sequences than those illustrated or otherwise described herein.

By adopting the scheme, after the slave node with abnormal communication behaviors is determined according to the preset communication behavior matching condition, the abnormal slave node release instruction is triggered, the handshake information of the slave node with the abnormal communication behaviors can be deleted, so that the node identification of the slave node with the abnormal communication behaviors is released, the binding relationship between the node identification and the slave node with abnormal communication behaviors is released, the master node is disconnected from the slave node with the abnormal communication behaviors, a first re-handshake message is sent to the slave node with the abnormal communication behaviors to request the slave node with the abnormal communication behaviors to re-initiate a handshake flow, the slave node with the abnormal communication behaviors is waited to respond to the first re-handshake message, so that the slave node with the abnormal communication behaviors can be re-accessed through the handshake flow, the normal communication behaviors of the slave node are ensured to be recovered, therefore, in the communication interaction process of the master node and the slave node, the problem of communication abnormalities can be automatically detected and solved, manual troubleshooting is not needed, the efficiency is improved, the abnormal communication behaviors of the slave node are timely processed, and the stability and the reliability of the communication interaction between the master node and the slave node are effectively guaranteed.

In an optional implementation, the nodes perform communication interaction through communication behaviors such as a receiving behavior and a sending behavior, and in order to prevent the communication interaction of the master node and the slave node from conflicting, a time interval planning can be performed on the communication behaviors of the master node and the slave node, and a master node sending time interval, a master node receiving time interval, a slave node sending time interval and a slave node receiving time interval are set. The communication behavior period planning can be carried out through a preset communication behavior period planning or through a main node, and which communication behavior is carried out by the main node and the auxiliary node can be determined.

As an alternative example, the master node may perform the communication action period planning through a preset hyper frame number, where the hyper frame number is counted in a preset basic unit, for example, the preset basic unit may be milliseconds. The master node selects the bit information of the low M bits of the hyper frame number, can determine whether the master node and the slave node perform the receiving action or the sending action, selects the bit information of the high L bits of the hyper frame number to be matched with the stored handshake information, and can determine the slave node appointed by the master node receiving time period. Wherein M and L are both non-zero natural numbers. And when the master node and the slave node perform the handshake process, the hyper-frame number can be sent to the corresponding slave node for synchronization, so that the slave node and the master node have the same hyper-frame number. The slave node can determine the receiving action or the transmitting action by selecting the bit information of the lower M bits of the synchronous hyper-frame number. And selecting the bit information of the high L bits of the hyper frame number to be matched with the handshake information stored in the slave node, so as to determine whether the slave node performs the transmission action in the transmission period.

The node identifier record information in the handshake information may be matched with the bit information of the high L bits of the hyper frame number.

As an alternative example, the preset communication behavior time interval plan may set the communication behavior performed by each master node and each slave node in each time interval.

Optionally, the communication behavior time period plans of the master node and the slave node may overlap, for example, the master node sending time period and the slave node receiving time period overlap, at this time, the master node may send a master node message, and the slave node may receive the master node message; the master node reception period overlaps with the slave node transmission period, the slave node may transmit a slave node message, and the master node may receive the slave node message.

According to the communication behavior time interval plan, whether the communication behavior of the slave node is abnormal or not may be detected, and specifically, the slave node which is determined to have the abnormal communication behavior based on the preset communication behavior matching condition may include at least one of the following:

1) And in the receiving period of the master node, receiving no slave node message sent by the corresponding slave node, and determining that the slave node is a slave node with abnormal communication behavior.

Optionally, in the master node reception period, according to a preset communication behavior period plan or by performing the communication behavior period plan through the master node, a slave node expected to send a slave node message in the master node reception period and an expected slave node identifier may be determined. The slave node which is expected to send the slave node message in the master node receiving period may be a preset communication behavior period plan or a slave node designated by the master node, or may be any slave node which completes a handshake flow with the master node when the preset communication behavior period plan or the master node does not designate a slave node.

If the master node receives the time interval, the slave node message sent by the expected slave node is determined not to be received based on the expected node identification, and therefore the corresponding slave node is taken as the slave node with abnormal communication behavior.

In one example, in a master node transmission period, the master node transmits a master node message to a designated slave node, and in a preset master node reception period or a preset master node reception period, based on the node identification of the designated slave node, the master node determines that the slave node message transmitted by the designated slave node is not received, so that the slave node can be determined to be a slave node with abnormal communication behavior.

2) In a receiving period of the master node, receiving a slave node message sent by a slave node, checking the validity of information included in the slave node message, and determining that the slave node is a slave node with abnormal communication behavior after checking that error information exists in the slave node message.

Optionally, the slave node message may include a slave node identifier, and according to a preset communication behavior time period plan or by a master node performing the communication behavior time period plan, a slave node and an expected slave node identifier that the slave node message is sent in an expected master node receiving time period may be determined, if the slave node message sent by the slave node is received in the master node receiving time period, a node identifier included in the slave node message may be matched with the expected node identifier, and if the node identifier carried in the slave node message is not consistent with the expected node identifier, the slave node that sends the slave node message may be determined as a slave node having an abnormal communication behavior.

In one example, in a master node sending period, the master node sends a master node message to a designated slave node, and in a preset master node receiving period or periods, the master node receives a slave node message sent by a slave node, and may match a node identifier included in the slave node message with a node identifier of the designated slave node, and if the node identifiers do not match, it may be determined that the slave node sending the slave node message is a slave node having abnormal communication behavior.

In another example, during the master node sending period, the master node receives a slave node message sent by a slave node, may match a node identifier included in the slave node message with a recorded node identifier of the slave node, and if the node identifier does not match the recorded node identifier of the slave node, may determine that the slave node sending the slave node message is a slave node having an abnormal communication behavior.

Optionally, the slave node message may further include: the slave node message comprises a message header identifier, a message type identifier, message data and a message check identifier, so that at least one of the message header identifier, the message type identifier, the message data and the message check identifier included in the slave node message can be checked for validity.

In one example, it may be determined whether there is error information in the slave node message by determining whether a message header identification included in the slave node message matches a preset message header identification. Specifically, the preset message header identifier may be a character segment "01", i.e., a character segment "01" from the start position of the node message. If the message header identifier of the received slave node message is the character segment '02', judging that the message header identifier included in the slave node message is not matched with a preset message header identifier, and the slave node message has error information.

In another example, whether error information exists in the slave node message may be determined by determining whether a message type identifier included in the slave node message matches a preset message type identifier. Specifically, in order to be able to distinguish the types of the slave node messages, and thus determine the content contained in the slave node messages according to the types of the slave node messages, different types of messages can be distinguished by presetting the message type identifiers. And the content expected to be sent by the slave node can be determined according to the preset communication behavior time interval plan or the communication behavior time interval plan by the master node. If the content expected to be sent by the slave node corresponds to the message type identifier P in the receiving period of the master node according to the preset message type identifier, but the message type identifier included in the received slave node message is Q, it is determined that the message type identifier included in the slave node message is not matched with the preset message type identifier, and the slave node message has error information.

In yet another example, determining whether message data included in the slave node message matches an included message type identifier may determine whether error information is present in the slave node message. Specifically, the message data of the slave node message, that is, the message content transmitted from the slave node to the master node, may determine the content included in the slave node message according to the type of the slave node message, so that there is a one-to-one correspondence between the message data and the message type identifier, and the message data included in the slave node message corresponds to the message type identifier P, but the message type identifier included in the slave node message is Q, the message type identifier included in the slave node message is not matched with the preset message type identifier, and the slave node message has error information, and at least one of the two is error information.

In yet another example, it may be determined whether there is error information in the slave node message by checking a message check identifier included in the slave node message. Specifically, the message check identifier is checked to determine whether the received slave node message is complete and accurate, and if the check result is an error, the slave node message has error information.

Further, the message Check identifier may be a message Check bit such as CRC (Cyclic Redundancy Check). The master node verifies the slave node identification information through the information verification information carried in the slave node identification information, so that whether the received slave node identification information is complete and accurate is judged, and the safety and the accuracy of communication interaction are ensured.

3) In the master node receiving period, slave node messages sent by slave nodes with the same node identification are received, and the slave nodes with the same node identification are determined to be slave nodes with abnormal communication behaviors.

In one example, in the master node transmission period, the master node receives slave node messages transmitted by a plurality of slave nodes, and determines that the node identifications of the plurality of slave nodes are the same through the node identifications included in the slave node messages, and then the plurality of slave nodes can be used as slave nodes with abnormal communication behaviors.

4) And receiving a slave node message sent by a slave node in a non-master node receiving period, and determining that the slave node is a slave node with abnormal communication behavior.

In one example, during the master node transmission period, the master node receives a slave node message transmitted by a slave node, and then the slave node can be determined to be a slave node with abnormal communication behavior.

By adopting the method to detect the communication behavior of the slave node, the slave node with abnormal communication behavior can be automatically detected, the complicated process caused by manual troubleshooting is reduced, the slave node with abnormal communication behavior is found in time, and the troubleshooting positioning efficiency is improved.

In an alternative implementation, the master node may allocate an available node identifier to the slave node in the handshake flow, and record the available node identifier as the node identifier of the slave node after the slave node feeds back that the available node identifier is successfully set. However, in the case that a plurality of slave nodes perform handshake procedures simultaneously, it may happen that a plurality of slave nodes are assigned to the same available node identifier, resulting in repeated identification of communication objects, and the slave nodes that actually communicate cannot be accurately located by the node identifiers.

At present, the solutions that can be adopted are:

1) The fault of the equipment is eliminated in a manual fault elimination mode.

2) Modifications are made to existing indoor distribution systems, for example, adding Identity Document (ID) identification devices, adding communication channels, or using longer length ID sequences.

However, the above solutions all have drawbacks. If the first scheme is adopted, in order not to influence the work of other normal nodes, the communication interaction between the abnormal nodes and the normal nodes cannot be stopped in the process of detecting the distribution conflict of the node identifiers, and a large number of nodes existing in the 5G network environment can improve the complexity of manual troubleshooting, greatly increase the workload, reduce the troubleshooting efficiency and improve the communication risk.

If the second scheme is adopted, the hardware architecture of the indoor distribution system needs to be modified, and for the indoor distribution system with limited communication capacity, the limitations of communication rate, amplitude modulation technology, power-on handshake time and the like often exist, complex operations such as scrambling, spread spectrum and the like cannot be performed, and hardware modification is not convenient to implement.

In order to solve the above problem, after the slave node accesses the master node after completing the handshake process, the slave node may send a slave node message to the master node, where the slave node message includes a random node identifier randomly generated by the slave node and a node identifier set through the handshake process, and the master node obtains the random node identifier included in the slave node message and saves the random node identifier (i.e., saves the random node identifier initially reported by the slave node).

Therefore, when the slave node sends the slave node message, the slave node may report the used node identifier (that is, the node identifier allocated by the master node to the slave node in the handshake flow) and the random node identifier aperiodically, and determine whether the random node identifier included in the slave node message is the same as the recorded random node identifier by matching the random node identifier included in the slave node message with the previously recorded random node identifier, and when the matching result is different, the master node may request the corresponding slave node to perform the handshake flow again, thereby ensuring that the node identifiers used by the slave nodes are different.

The random node identifier may be in a form of a random sequence, such as a random number, and the number of bits of the random node identifier may be greater than the number of bits of the available node identifier, so as to reduce the probability of repetition of the random node identifier.

It is understood that "first" and "second" may be used to distinguish the handshake confirmation message sent by the master node from the handshake confirmation message sent by the slave node, for example, the handshake confirmation message sent by the master node is a first handshake confirmation message, and the handshake confirmation message sent by the slave node is a second handshake confirmation message.

By adopting the scheme, under the condition that a hardware architecture in an indoor distribution system is not changed, the software part is modified, the automatic detection of handshake node identification conflict can be realized, the method can be widely applied to various indoor distribution systems, the phenomenon that a plurality of slave nodes are distributed with the same handshake node identification can be found in time, the condition of communication disorder can be further avoided, and the stability and the reliability of communication interaction between the master node and the slave node can be improved.

In an optional implementation, if the slave node does not report a randomly generated random node identifier after completing the handshake flow, when determining whether the node identifier included in the slave node message is consistent with the recorded node identifier of the slave node, the slave node may determine whether the node identifier included in the slave node message matches an available node identifier allocated in the handshake flow, and when determining that the node identifier included in the slave node message does not match the available node identifier allocated in the handshake flow, the slave node is a slave node having an abnormal communication behavior.

In another optional implementation, if the slave node reports a randomly generated random node identifier after completing the handshake process, when determining whether the node identifier included in the slave node message is consistent with the recorded node identifier of the slave node, the determination may be made by determining whether the random node identifier included in the slave node message matches the random node identifier reported for the first time, and when determining that the random node identifier included in the slave node message does not match the random node identifier reported for the first time, the slave node is a slave node having an abnormal communication behavior.

By matching the random node identifier included in the slave node message with the random node identifier reported for the first time, the situation that a plurality of slave nodes use the same available node identifier as the node identifier can be avoided, and therefore the slave nodes of actual communication are accurately positioned through the random node identifier.

In an optional implementation, before the triggering exception releases the instruction from the node, the method may further include: determining that the number of times of abnormal communication behaviors of the slave node with the abnormal communication behaviors meets a preset number threshold.

Optionally, as shown in fig. 4, a flowchart of another communication exception handling method provided in the embodiment of the present invention may specifically include:

and S40, determining the slave node with abnormal communication behaviors based on the preset communication behavior matching conditions.

And S41, determining that the number of times of the abnormal communication behaviors of the slave nodes with the abnormal communication behaviors meets a preset number threshold, if so, continuing to the step S42, and if not, returning to the step S40.

Optionally, after it is determined that the abnormal communication behavior exists in the slave node, the number of times of existence of the abnormal communication behavior in the slave node may be accumulated or subtracted. The embodiment of the invention does not limit the calculation mode of the number of times of the abnormal communication behavior.

Step S42, triggering an abnormal slave node release instruction, deleting the handshake information of the slave node with the abnormal communication behavior, and releasing the node identification of the slave node with the abnormal communication behavior;

step S43, sending a first re-handshake message to the slave node with abnormal communication behavior;

and step S44, waiting for receiving a second re-handshake message sent by the slave node with abnormal communication behavior in response to the first re-handshake message.

By adopting the scheme, the frequency threshold value is set for the slave node, the misjudgment probability of the abnormal communication behavior of the slave node can be reduced, and the frequency of the master node and the slave node for carrying out the handshake process again is reduced.

In an optional implementation, if the abnormal communication behavior of the slave node is an accidental behavior, the number of times of the abnormal communication behavior of the slave node becomes redundant data, and therefore, the number of times of the abnormal communication behavior of the slave node may be reset, for example, in a master node reception period, a slave node message sent by the corresponding slave node is received, validity check is performed on information included in the slave node message, and after it is determined that no error information exists in the slave node message, the number of times of the abnormal communication behavior of the slave node is reset to an initial value.

As an alternative example, the master node may use a watchdog counter to count the number of abnormal communication behaviors (which may also be referred to as a watchdog operation) for detecting whether the communication behaviors of the slave node are normal and determining whether the slave node needs to perform the handshake again. When the master node receives a normal slave node message sent by the slave node once, the master node resets the value of the watchdog counter corresponding to the slave node to a fixed value N, where N is any natural number greater than 0, and for example, N may be equal to 4.

And when the master node determines that the slave node with abnormal communication behavior exists based on a preset communication behavior matching condition, performing an accumulative subtraction operation on the numerical value of the watchdog counter corresponding to the slave node, such as performing a subtraction operation of 1. And when the value of the corresponding watchdog counter is reduced to the preset frequency threshold, the watchdog counter is considered to be overtime, the subsequent steps are carried out, and when the value of the corresponding watchdog counter is reduced to the preset frequency threshold, the slave node with the abnormal communication behavior is continuously determined. The preset number threshold is an integer smaller than N, for example, the preset number threshold may be 0.

The watchdog counter can be realized through software simulation or a hardware circuit formed by components. The embodiment of the present invention does not specifically limit the implementation manner of the watchdog counter.

It should be noted that, in the above-mentioned scheme, the dog feeding operation may be performed only at the master node, and may not be performed at the slave node, so as to reduce communication overhead.

To facilitate those skilled in the art to understand and implement the embodiment of the present invention, according to the flowchart of the communication exception handling method illustrated in fig. 5, the communication interaction between the master node and the slave node may specifically include:

s50, the master node determines a slave node with abnormal communication behavior based on a preset communication behavior matching condition;

s51, the master node triggers an abnormal slave node release instruction and deletes handshake information of the slave node with the abnormal communication behavior;

step S52, the main node sends a first re-handshake message to the slave node with the abnormal communication behavior;

and step S53, the slave node with the abnormal communication behavior responds to the first re-handshake message sent by the master node, and sends a second re-handshake message to the master node so as to reinitiate a handshake process.

By adopting the scheme, after the master node determines the slave node with abnormal communication behavior according to the preset communication behavior matching condition, the master node can delete the handshake information of the slave node with abnormal communication behavior by triggering the abnormal slave node release instruction, so as to release the node identifier of the slave node with abnormal communication behavior, remove the binding relationship between the node identifier and the slave node with abnormal communication behavior, disconnect the communication connection between the master node and the slave node with abnormal communication behavior, and send the first re-handshake message to the slave node with abnormal communication behavior to request the slave node with abnormal communication behavior to re-initiate the handshake flow, wait for the slave node with abnormal communication behavior to respond to the first re-handshake message, so that the handshake can re-access the slave node with abnormal communication behavior through the flow, and ensure that the slave node recovers the normal communication behavior, therefore, in the communication interaction process between the master node and the slave node, the problem of communication abnormality can be automatically detected and solved, manual troubleshooting is not needed, the troubleshooting efficiency is improved, the abnormal communication behavior of the slave node is timely processed, and the stability and the reliability of the communication interaction between the slave node and the master node and the slave node are effectively guaranteed.

Further optionally, as shown in fig. 5, the communication interaction between the master node and the slave node may further include the following steps:

and S54, the master node, in response to the received second re-handshake message, if an available node identifier is successfully re-allocated to the slave node having the abnormal communication behavior, sends a re-handshake confirmation message to the slave node having the abnormal communication behavior, where the re-handshake message at least includes the successfully re-allocated available node identifier.

And S55, resetting the node identification of the slave node with the abnormal communication behavior based on the available node identification.

Alternatively, the abnormal communication behavior determined by the different matching conditions may be classified into a plurality of abnormal communication behavior levels by the degree of abnormal severity, for example, the abnormal communication behavior determined by the number of times the abnormal communication behavior exists is more severe than the abnormal communication behavior determined by matching the node identifier included in the slave node message with the node identifier of the designated slave node, and the level of the abnormal communication behavior determined by the number of times the abnormal communication behavior exists is higher than the level of the abnormal communication behavior determined by matching the node identifier included in the slave node message with the node identifier of the designated slave node.

Further, the abnormal communication behavior determined by the different matching conditions may correspond to the same abnormal communication behavior level, for example, the abnormal communication behavior level determined by the number of times of existence of the abnormal communication behavior is equal to the abnormal communication behavior level determined by matching the node identification included in the slave node message with the random node identification.

Optionally, different abnormal communication behavior levels and corresponding error codes may be set by software located on an upper layer of the master node.

Then, corresponding error codes can be set for the abnormal communication behavior levels, so that the abnormal communication behavior levels with different degrees of severity can be represented by different error codes.

Based on a preset abnormal communication behavior level, the master node can determine an abnormal communication behavior level corresponding to the slave node with the abnormal communication behavior; determining the abnormal communication behavior level corresponding to the slave node with the abnormal communication behavior based on a preset abnormal communication behavior level, and acquiring a corresponding error code based on the abnormal communication behavior level, wherein when the master node sends a first re-handshake message to the slave node with the abnormal communication behavior, the first re-handshake message contains the acquired error code. Optionally, the error code may be included in message data of the first re-handshake message.

After receiving the first re-handshake message, the slave node determines that an abnormal communication behavior exists, and according to an error code included in the first re-handshake message, the slave node may select a corresponding degree of communication abnormality recovery operation according to the level of the abnormal communication behavior characterized by the error code, for example, according to the level of the abnormal communication behavior characterized by the error code, from light to heavy, the following corresponding order of communication abnormality recovery operations may be selected:

1) Entering an access state and carrying out handshake again with the main node;

2) Searching the network again and entering an access state after receiving a heartbeat message sent by the main node, and performing handshake again with the main node;

3) Restarting, searching the network again, and entering an access state after receiving a heartbeat message sent by the main node, and performing handshake again with the main node;

4) And after factory settings are restored, restarting and searching the network again are carried out, and after a heartbeat message sent by the main node is received, the network enters an access state and carries out handshake again with the main node.

As an optional example, the slave node with the abnormal communication behavior responds to a first re-handshake message sent by the master node, and determines whether to perform network re-searching, restarting or factory setting restoration according to an error code included in the first re-handshake message; and after network searching, restarting or factory setting restoration is carried out again, or after the network searching, restarting or factory setting restoration is determined not to be carried out again, sending a second handshake message again to the main node to reinitiate a handshake process.

While various embodiments of the present invention have been described above, various alternatives described in the various embodiments can be combined and cross-referenced without conflict to extend the variety of possible embodiments that can be considered disclosed and disclosed in connection with the embodiments of the present invention.

The embodiment of the present invention further provides a master node corresponding to the above communication exception handling method, so that those skilled in the art can better understand and implement the embodiment of the present invention, and the detailed description is given below through specific embodiments with reference to the accompanying drawings.

Referring to an optional block diagram of a master node in the embodiment of the present invention shown in fig. 6, in this specification, the master node 60 may include:

the handshake module 61 is used for executing a handshake process to establish communication connection with the slave node;

the abnormal slave node detection module 62 is configured to determine a slave node having an abnormal communication behavior according to a preset communication behavior matching condition;

an abnormal slave node releasing module 63, configured to delete the handshake information of the slave node having the abnormal communication behavior according to a triggered abnormal slave node releasing instruction, and release the node identifier of the slave node having the abnormal communication behavior;

a message sending module 64, configured to send a first re-handshake message to the slave node having the abnormal communication behavior;

a message receiving module 65, configured to receive a second re-handshake message sent by the slave node having the abnormal communication behavior in response to the first re-handshake message.

By adopting the scheme, after the master node determines the slave node with abnormal communication behavior according to the preset communication behavior matching condition, the master node can delete the handshake information of the slave node with abnormal communication behavior by triggering the abnormal slave node release instruction, so as to release the node identifier of the slave node with abnormal communication behavior, remove the binding relationship between the node identifier and the slave node with abnormal communication behavior, disconnect the communication connection between the master node and the slave node with abnormal communication behavior, and send the first re-handshake message to the slave node with abnormal communication behavior to request the slave node with abnormal communication behavior to re-initiate a handshake flow, wait for the slave node with abnormal communication behavior to respond to the first re-handshake message, so that the slave node with abnormal communication behavior can be re-accessed through a handshake flow, and the normal communication behavior of the slave node is ensured to be recovered, therefore, in the communication interaction process between the master node and the slave node, the problem of communication abnormality can be automatically detected and solved, manual troubleshooting is not needed, the efficiency is improved, the abnormal communication behavior of the slave node is timely processed, and the stability and the reliability of the communication interaction between the master node and the slave node are effectively guaranteed.

Optionally, according to the communication behavior time interval plan, it may be detected whether the communication behavior of the slave node is abnormal, and the master node may determine the slave node having the abnormal communication behavior by using the manner described in the embodiment related to the communication abnormality processing method.

Optionally, as shown in fig. 7, the master node 60 may further include:

the number matching module 66 is configured to determine that the number of times of the abnormal communication behavior of the slave node having the abnormal communication behavior meets a preset number threshold before the command for releasing the abnormal slave node is triggered.

Optionally, the number matching module 66 is further configured to, in the master node reception period, receive a slave node message sent by a corresponding slave node, perform validity check on information included in the slave node message, and reset the number of times of existence of the abnormal communication behavior of the slave node to an initial value after determining that there is no error information in the slave node message.

Optionally, the handshake module 61 is further configured to respond to the received second handshake message, and send the available node identifier to the message sending module 64 if the available node identifier is successfully re-allocated to the slave node with the abnormal communication behavior;

the message sending module 64 is further configured to send a re-handshake confirmation message to the slave node with abnormal communication behavior, where the re-handshake confirmation message includes at least an available node identifier that is allocated successfully again, and the available node identifier is used to reset the node identifier of the slave node with abnormal communication behavior.

In practical applications, each module included in the master node may be implemented by using a corresponding hardware circuit, a corresponding device, a corresponding module, or the like. For example, the message sending module and the message receiving module, etc. may be implemented by respective buses, communication lines, transceiving devices, etc.; the handshake module and the abnormal node release module can be executed by data processing chips such as a single chip microcomputer and an FPGA, and the abnormal slave node detection module can be realized by a corresponding detection circuit, a detection device or a detection chip. The modules may be controlled by the same processing device, or may be executed by different processing devices, and the different processors may be distributed on the same hardware device, or may be distributed on different hardware devices.

The embodiment of the present invention further provides an indoor distribution system corresponding to the above communication exception handling method, and in order to enable those skilled in the art to better understand and implement the embodiment of the present invention, the following detailed description is provided by specific embodiments with reference to the accompanying drawings.

As shown in fig. 1, the indoor distribution system may include a master node 10 and a plurality of slave nodes 21 to 2N, where:

the master node 10 is configured to determine, based on a preset communication behavior matching condition, a slave node 2X with an abnormal communication behavior, where X is any integer from 1 to N, trigger an abnormal slave node release instruction, delete handshake information of the slave node 2X with the abnormal communication behavior, send a first re-handshake message to the slave node 2X with the abnormal communication behavior, request the slave node 2X with the abnormal communication behavior to re-initiate a handshake flow, and wait for receiving a second re-handshake message sent by the slave node 2X with the abnormal communication behavior in response to the first re-handshake message;

the slave node 2X is configured to send a second re-handshake message to the master node 10 in response to the first re-handshake message sent by the master node 10, so as to reinitiate a handshake flow.

It may be understood that the foregoing embodiments are merely examples, and the master node and the slave node having the abnormal communication behavior may be one or more slave nodes, and the master node may determine the slave node having the abnormal communication behavior by adopting the manner described in the related embodiments of the communication abnormality processing method, which may specifically refer to the related embodiments, and will not be described again.

An embodiment of the present invention further provides a master node, and as shown in fig. 8, the master node may include: a processor 81, a communication interface 82, a memory 83 and a communication bus 84;

in the embodiment of the present invention, the number of the processor 81, the communication interface 82, the memory 83, and the communication bus 84 is at least one, and the processor 81, the communication interface 82, and the memory 83 complete the communication with each other through the communication bus 84;

alternatively, the communication interface 82 may be an interface of a communication module for performing network communication;

alternatively, the processor 81 may be a CPU (central Processing Unit), a GPU (Graphics Processing Unit), an NPU (embedded neural network processor), an FPGA (Field Programmable Gate Array), a TPU (tensor Processing Unit), an AI chip, an ASIC (Application Specific Integrated Circuit), a baseband chip, or one or more Integrated circuits configured to implement the embodiments of the present invention.

The memory 83 may comprise a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

The memory 83 stores one or more computer-executable instructions, and the processor 81 calls the one or more computer-executable instructions to execute the abnormal communication processing method provided by the embodiment of the present invention.

The embodiment of the present invention further provides an indoor distribution system, which may include a plurality of slave nodes and the master node described in any of the above embodiments. Specifically, reference may be made to the foregoing embodiments, which are not described herein again.

An embodiment of the present invention further provides a storage medium, where the storage medium may store one or more computer-executable instructions, where the one or more computer-executable instructions may be configured to execute the abnormal communication processing method provided in any one of the foregoing embodiments of the present invention. Specifically, reference may be made to the foregoing embodiments, which are not described herein again.

Although the embodiments of the present invention have been disclosed, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. The communication exception handling method is characterized by being applied to a main node, wherein the main node establishes communication connection with a slave node through a handshake process, and the main node and the slave node are positioned in an indoor distribution system; when the master node and the slave node carry out handshake process, the master node selects a node identifier for the slave node, and if the selected node identifier is not occupied, the selected node identifier is used as an available node identifier;

the communication exception handling method comprises the following steps:

triggering an abnormal slave node release instruction, deleting handshake information of the slave node with the abnormal communication behavior, releasing the node identification of the slave node with the abnormal communication behavior, and setting the node identification of the slave node with the abnormal communication behavior as unoccupied;

waiting for receiving a second re-handshake message sent by the slave node with abnormal communication behavior in response to the first re-handshake message;

responding to the received second re-handshake message, if the available node identification is successfully re-distributed to the slave node with the abnormal communication behavior, sending a re-handshake confirmation message to the slave node with the abnormal communication behavior;

2. The communication exception handling method according to claim 1, further comprising, before the triggering exception releasing instruction from the node:

and determining that the number of times of the abnormal communication behaviors of the slave nodes with the abnormal communication behaviors meets a preset number threshold.

3. The communication exception handling method according to claim 2, further comprising:

in the master node receiving period, receiving a slave node message sent by a corresponding slave node, checking the validity of information included in the slave node message, and resetting the number of times of abnormal communication behavior of the slave node to an initial value after determining that no error information exists in the slave node message.

4. The communication exception handling method according to claim 2, wherein said deleting the handshake information of the slave node with the abnormal communication behavior and releasing the node identification of the slave node with the abnormal communication behavior comprises:

deleting the node identification record information of the slave node with the abnormal communication behavior, and setting the node identification of the slave node with the abnormal communication behavior as unoccupied.

5. The method according to claim 1, further comprising, before the sending the first re-handshake message to the slave node with abnormal communication behavior, the following steps:

determining the abnormal communication behavior level corresponding to the slave node with the abnormal communication behavior based on a preset abnormal communication behavior level;

and acquiring a corresponding error code based on the abnormal communication behavior level, and including the error code in the first re-handshake message.

6. The communication exception handling method is applied to an indoor distribution system, the indoor distribution system comprises a main node and a slave node, the main node establishes communication connection with the slave node through a handshake process, and the main node and the slave node are located in the indoor distribution system; when the master node and the slave node carry out handshake process, the master node selects a node identifier for the slave node, and if the selected node identifier is not occupied, the selected node identifier is used as an available node identifier;

the communication exception handling method comprises the following steps:

the master node triggers an abnormal slave node release instruction, deletes handshake information of the slave node with the abnormal communication behavior, and sets the node identification of the slave node with the abnormal communication behavior as unoccupied;

the slave node with the abnormal communication behavior responds to a first re-handshake message sent by a master node, and sends a second re-handshake message to the master node to reinitiate a handshake process;

the master node responds to the received second re-handshake message, if the available node identification is re-successfully allocated to the slave node with the abnormal communication behavior, a re-handshake confirmation message is sent to the slave node with the abnormal communication behavior, and the re-handshake message comprises the available node identification which is re-successfully allocated;

and the slave node with abnormal communication behavior resets the node identification based on the available node identification.

7. The communication exception handling method according to claim 6, wherein the slave node having the abnormal communication behavior sends a second re-handshake message to the master node in response to a first re-handshake message sent by the master node to re-initiate a handshake flow, including:

the slave node with the abnormal communication behavior responds to a first re-handshake message sent by the master node, and determines whether to perform network searching again, restart or restore factory settings according to an error code included in the first re-handshake message;

and after network searching, restarting or factory setting restoration is carried out again, or after the network searching, restarting or factory setting restoration is determined not to be carried out again, sending a second handshake message again to the main node to reinitiate a handshake process.

8. A master node is characterized in that the master node and slave nodes are positioned in an indoor distribution system; when the master node and the slave node carry out handshake process, the master node selects a node identifier for the slave node, and if the selected node identifier is not occupied, the selected node identifier is used as an available node identifier;

the master node includes:

the abnormal slave node releasing module is used for deleting the handshake information of the slave node with the abnormal communication behavior according to a triggered abnormal slave node releasing instruction, releasing the node identification of the slave node with the abnormal communication behavior, and setting the node identification of the slave node with the abnormal communication behavior as unoccupied;

a message receiving module, configured to receive a second re-handshake message sent by the slave node with abnormal communication behavior in response to the first re-handshake message;

the message sending module is further configured to, in response to the received second re-handshake message, send a re-handshake confirmation message to the slave node with the abnormal communication behavior if the available node identifier is re-successfully allocated to the slave node with the abnormal communication behavior, where the re-handshake message includes the available node identifier that is re-successfully allocated, so that the slave node with the abnormal communication behavior resets the node identifier based on the available node identifier.

9. An indoor distribution system is characterized by comprising a main node and a slave node, wherein the main node establishes communication connection with the slave node through a handshake process, when the main node and the slave node perform the handshake process, the main node selects a node identifier for the slave node, and if the selected node identifier is not occupied, the selected node identifier is used as an available node identifier; wherein:

the master node is used for determining the slave node with the abnormal communication behavior based on a preset communication behavior matching condition, triggering an abnormal slave node release instruction, deleting handshake information of the slave node with the abnormal communication behavior, releasing the node identification of the slave node with the abnormal communication behavior, and setting the node identification of the slave node with the abnormal communication behavior as unoccupied; sending a first re-handshake message to the slave node with abnormal communication behavior, and waiting for receiving a second re-handshake message sent by the slave node with abnormal communication behavior in response to the first re-handshake message; responding to the received second re-handshake message, if available node identifications are re-successfully allocated to the slave nodes with abnormal communication behaviors, sending a re-handshake confirmation message to the slave nodes with abnormal communication behaviors, wherein the re-handshake message comprises the available node identifications which are re-successfully allocated;

the slave node is used for responding to a first re-handshake message sent by the master node and sending a second re-handshake message to the master node so as to reinitiate a handshake process; and resetting the node identification based on the available node identification when the abnormal communication behavior exists.

10. A master node, comprising: a memory storing one or more computer-executable instructions and a processor invoking the one or more computer-executable instructions to perform the communication exception handling method of any of claims 1-5.

11. An indoor distribution system comprising a plurality of slave nodes and a master node according to claim 10, the master node establishing a communication connection with a slave node by means of a handshake procedure.

12. A storage medium storing one or more computer-executable instructions for performing the communication exception handling method of any one of claims 1 to 5.