Address conflict detection method and device

Abstract

An address conflict detection method and apparatus, the method comprising: a first node sending a first message, the first message comprising a target network address field, an address type field and a target system identification field, the target network address field indicating a first network address, and the address type field indicating a second network address; the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of multiple address types; the target system identification field is used for indicating identification information of a node configured with the first network address; the first node receives a second message from the second node, and the second message indicates whether the first network address has the address conflict, by adopting the method, whether the address conflict exists in the network in the whole network range can be detected, and the source of the address conflict is prompted to a user in time, so that the user is helped to eliminate the address conflict configuration as soon as possible, and the user experience is improved. And the influence on the service is practically reduced.

Description

A method and device for detecting address conflict Technical Field

[0001] The present application relates to the field of communications, and in particular to an address conflict detection method and device. Background Art

[0002] Wireless communication is widely used in scenarios such as smart cars, smart homes, smart terminals, and smart manufacturing. Compared with wired communication, it can effectively reduce the length and weight of wire harnesses and reduce the number of connectors.

[0003] Wireless networks can often experience address conflicts due to incorrect networking or configuration. These conflicts can cause routing oscillations, service interruptions, and data traffic disruptions, significantly impacting user services. Therefore, researchers in this field are currently working to identify address conflicts and promptly notify users of the root cause, helping them quickly resolve conflicting configurations and minimizing the impact on their services.

[0004] Summary of the Invention

[0005] This application discloses an address conflict detection method and device, which can detect whether there is an address conflict in the entire network, and promptly prompt the user to the root cause of the address conflict, so as to help the user eliminate the address conflict configuration as soon as possible and effectively reduce the impact on the business.

[0006] In a first aspect, the present application provides an address conflict detection method, which includes: a first node sends a first message, the first message includes a target network address field, an address type field and a target system identification field, the target network address field indicates a first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address; the first node receives a second message from a second node, and the second message indicates whether there is an address conflict for the first network address.

[0007] The method can be applied to scenarios such as in-vehicle communications, smart homes, and battery management systems (BMS). In the in-vehicle communications scenario, the node that initiates network address detection or query in the first node network and any node other than the first node in the second node network can be, for example, a user terminal in the vehicle or a component in the user terminal (e.g., a board, line card, or chip). The user terminal can be, for example, a mobile phone, tablet computer, PDA, desktop computer, headset, speaker, wearable device, in-vehicle device, virtual reality device, augmented reality device, or a telematics box (T-Box). In the smart home scenario, the node that initiates network address detection or query in the first node network and any node other than the first node in the second node network can be, for example, a household appliance or a component in a household appliance. The household appliance can be, for example, a television, a robot vacuum, a printer, a projector, a user's mobile phone, a rice cooker, a speaker, a microphone, a wireless router, or a gateway, customer premises equipment (CPE), a wireless router, a user's mobile phone, or the like. In the BMS scenario, the node that initiates network address detection or query in the first node network, and any node in the second node network other than the first node, can be, for example, a battery monitoring unit (BMU), a battery control unit (BCU) or a BMU.

[0008] In the above method, the inclusion of the target network address field, the address type field, and the target system identifier field in the first message enables network-wide address conflict detection, thereby promptly notifying users of the source of the address conflict and helping them quickly eliminate the address conflict configuration, effectively minimizing the impact on their services. Furthermore, by including the address type field in the first message, address conflict detection for multiple address types can be implemented, enhancing diversity.

[0009] In a possible implementation, the multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

[0010] Among them, the Star Flash network address is a network layer short address, which can be 2 bytes (i.e. 16 bits) in length and can be used for addressing in the corresponding communication system. For example, for Star Flash communication technology, the Star Flash network address can be used for addressing within the Star Flash communication system. It can be understood that the Star Flash network address is another address type different from the IP address.

[0011] In another possible implementation, when the first message is a request message, the target system identification field has a default value or a default value. The request message is used to query whether there is an address conflict with the first network address. For example, when the first message is a request message, the target system identification field may have a default value, such as 0. For another example, when the first message is a request message, the target system identification field may have a default value.

[0012] In another possible implementation, the second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

[0013] In another possible implementation, when the second message is a response message, the target system identification field is identification information of the second node. The identification information of the second node is used to identify the second node and can be user-configured or obtained based on a device identification. The device identification can be a Layer 2 Identification (L2ID).

[0014] In another possible implementation, the first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field. The network address length field refers to the length of the target network address field or the source network address field, in bytes. For example, when the target network address or the source network address field is type 4 and occupies a maximum of 4 bytes, the address length indicated by the network address length field is 4. The source network address field is used to indicate the network address of the node initiating the detection or query, which can be a unicast address. The source system identification field is used to indicate the identification of the node initiating the detection or query.

[0015] In yet another possible implementation, at least one of the length of the target network address field and the length of the source network address field is variable.

[0016] In another possible implementation, if the first node has been configured with a second network address, the source network address field in the second message includes the second network address, where the second network address is different from the first network address. It will be appreciated that when the first node has been configured with the second network address, the second node can send the second message to the first node via unicast, thereby reducing signaling overhead.

[0017] In another possible implementation, if the first node is not configured with a network address other than the first network address, the source network address field in the second message is a default value or a default value. It is understood that when the first node is not configured with a network address other than the first network address, the second node may send the second message to the first node via a broadcast.

[0018] In another possible implementation, the address type field is indicated by N bits, and when the value of the N bits is a first value, the first address type is indicated, where N is a positive integer greater than 0. For example, when the first value is 0000001, it indicates that the first address type is a Star Flash network address; when the first value is 0000010, it indicates that the first address type is a custom address; when the first value is 0000100, it indicates that the first address type is an IPv4 address; and when the first value is 0000110, it indicates that the first address type is an IPv6 address.

[0019] In another possible implementation, the first message includes a frame header portion and a data portion, the data portion includes an address query protocol portion, and the address query protocol portion includes the target network address field, the address type field, and the target system identification field. The address query protocol portion may further include a network address length field, a source network address field, a source system identification field, or a reserved field.

[0020] In second aspect, the present application provides an address conflict detection method, the method comprising: a second node receives a first message, the first message including a target network address field, an address type field and a target system identification field, the target network address field indicates a first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address; the second node sends a second message to the first node, the second message indicating whether there is an address conflict for the first network address.

[0021] In the above method, the inclusion of the target network address field, the address type field, and the target system identifier field in the first message enables network-wide address conflict detection, thereby promptly notifying users of the source of the address conflict and helping them quickly eliminate the address conflict configuration, effectively minimizing the impact on their services. Furthermore, by including the address type field in the first message, address conflict detection for multiple address types can be implemented, enhancing diversity.

[0022] In a possible implementation, the multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

[0023] Among them, the Star Flash network address is a network layer short address, which can be 2 bytes (i.e. 16 bits) in length and can be used for addressing in the corresponding communication system. For example, for Star Flash communication technology, the Star Flash network address can be used for addressing within the Star Flash communication system. It can be understood that the Star Flash network address is another address type different from the IP address.

[0024] In another possible implementation, when the first message is a request message, the target system identification field has a default value or a default value. The request message is used to query whether there is an address conflict with the first network address. For example, when the first message is a request message, the target system identification field may have a default value, such as 0. For another example, when the first message is a request message, the target system identification field may have a default value.

[0025] In another possible implementation, the second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

[0026] In another possible implementation, when the second message is a response message, the target system identification field is identification information of the second node. The identification information of the second node is used to identify the second node and can be user-configured or obtained based on a device identification. The device identification can be a Layer 2 Identification (L2ID).

[0027] In another possible implementation, the first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field. The network address length field refers to the length of the target network address field or the source network address field, in bytes. For example, when the target network address or the source network address field is type 4 and occupies a maximum of 4 bytes, the address length indicated by the network address length field is 4. The source network address field is used to indicate the network address of the node initiating the detection or query, which can be a unicast address. The source system identification field is used to indicate the identification of the node initiating the detection or query.

[0028] In yet another possible implementation, at least one of the length of the target network address field and the length of the source network address field is variable.

[0029] In another possible implementation, if the first node has been configured with a second network address, the source network address field in the second message includes the second network address, where the second network address is different from the first network address. It will be appreciated that when the first node has been configured with the second network address, the second node can send the second message to the first node via unicast, thereby reducing signaling overhead.

[0030] In another possible implementation, if the first node is not configured with a network address other than the first network address, the source network address field in the second message is a default value or a default value. It is understood that when the first node is not configured with a network address other than the first network address, the second node may send the second message to the first node via a broadcast.

[0031] In another possible implementation, the address type field is indicated by N bits, and when the value of the N bits is a first value, the first address type is indicated, where N is a positive integer greater than 0. For example, when the first value is 0000001, it indicates that the first address type is a Star Flash network address; when the first value is 0000010, it indicates that the first address type is a custom address; when the first value is 0000100, it indicates that the first address type is an IPv4 address; and when the first value is 0000110, it indicates that the first address type is an IPv6 address.

[0032] In another possible implementation, the first message includes a frame header portion and a data portion, the data portion includes an address query protocol portion, and the address query protocol portion includes the target network address field, the address type field, and the target system identification field. The address query protocol portion may further include a network address length field, a source network address field, a source system identification field, or a reserved field.

[0033] In the third aspect, the present application provides an address conflict detection method, which includes: the first node receives a first message from the second node, the first message including the target network address and the network address of a third node; the third node is a neighbor of the second node, and the third node is a relay node for the first node and the second node; the first node stores a node network address mapping table; the node network address mapping table is used for address conflict detection; the first node determines whether there is an address conflict for the target network address based on the node network address mapping table; the node network address mapping table indicates the mapping relationship between the identification information of multiple nodes and the network addresses of the multiple nodes, wherein the multiple nodes include the second node and the third node; the first node sends a second message to the second node, the second message is used to indicate that there is no address conflict for the target network address, and the second message is a unicast message; or, the first node sends a third message to the second node through the third node, the third message is used to indicate that there is an address conflict for the target network address.

[0034] In the above method, the first node can send the second message to the second node via unicast, or send the third message to the third node via unicast. In this way, it can avoid broadcast messages from bringing more load to the network, thereby saving network overhead. Moreover, by storing a node network address mapping table in the first node, the first node can detect address conflicts across the entire network.

[0035] In a possible implementation manner, the second node is a terminal node.

[0036] In another possible implementation, the first node determines whether there is an address conflict for the target network address based on the node network address mapping table, including: the first node matches the target network address with the network address of the node in the node network address mapping table; if the match is successful, the first node determines that there is an address conflict for the target network address; if the match is not successful, the first node determines that there is no address conflict for the target network address.

[0037] In a fourth aspect, the present application provides an address conflict detection method, which includes: a second node sends a first message to a first node, the first message including a target network address and a network address of a third node; the third node is a neighbor of the second node, and the third node is a relay node for the first node and the second node; a node network address mapping table is stored in the first node; the node network address mapping table is used to determine whether there is an address conflict for the target network address; the node network address mapping table indicates a mapping relationship between identification information of multiple nodes and the network addresses of the multiple nodes, wherein the multiple nodes include the second node and the third node; the second node receives a second message from the first node, the second message is used to indicate that there is no address conflict for the target network address; the second message is a unicast message; or, the second node receives a third message from the third node, the third message is used to indicate that there is an address conflict for the target network address.

[0038] In the above method, the first node can send the second message to the second node via unicast, or send the third message to the third node via unicast. In this way, it can avoid broadcast messages from bringing more load to the network, thereby saving network overhead. Moreover, by storing a node network address mapping table in the first node, the first node can detect address conflicts across the entire network.

[0039] In a possible implementation manner, the second node is a terminal node.

[0040] In a fifth aspect, the present application provides an address conflict detection device, which includes: a communication unit and a processing unit, the communication unit being used to send a first message, the first message including a target network address field, an address type field and a target system identification field, the target network address field indicating a first network address, the address type field indicating a first address type corresponding to the first network address, the first address type belonging to one of multiple address types; the target system identification field being used to indicate identification information of a node configured with the first network address; the communication unit being further used to receive a second message from a second node, the second message indicating whether there is an address conflict for the first network address.

[0041] In a possible implementation, the multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

[0042] In another possible implementation, when the first message is a request message, the target system identification field is a default value or a default value. The request message is used to query whether there is an address conflict in the first network address.

[0043] In another possible implementation, the second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

[0044] In another possible implementation, when the second message is a response message, the target system identification field is identification information of the second node. In another possible implementation, the first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

[0045] In yet another possible implementation, at least one of the length of the target network address field and the length of the source network address field is variable.

[0046] In yet another possible implementation, if the first node has been configured with a second network address, the source network address field in the second message includes the second network address, where the second network address is different from the first network address.

[0047] In yet another possible implementation, if the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

[0048] In another possible implementation, the address type field is indicated by N bits, and when the value of the N bits is a first value, it indicates the first address type, where N is a positive integer greater than 0.

[0049] In another possible implementation, the first message includes a frame header part and a data part, the data part includes an address query protocol part, and the address query protocol part includes the target network address field, the address type field, and the target system identification field.

[0050] Regarding the technical effects brought about by the fifth aspect or possible implementation methods, reference may be made to the introduction to the technical effects of the first aspect or corresponding implementation methods.

[0051] In a sixth aspect, the present application provides an address conflict detection device, which includes: a communication unit and a processing unit, the communication unit being used to receive a first message, the first message including a target network address field, an address type field and a target system identification field, the target network address field indicating a first network address, the address type field indicating a first address type corresponding to the first network address, the first address type belonging to one of multiple address types; the target system identification field being used to indicate identification information of a node configured with the first network address; the communication unit being further used to send a second message to the first node, the second message indicating whether there is an address conflict for the first network address.

[0052] In a possible implementation, the multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

[0053] In another possible implementation, when the first message is a request message, the target system identification field is a default value or a default value. The request message is used to query whether there is an address conflict in the first network address.

[0054] In another possible implementation, the second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

[0055] In yet another possible implementation, when the second message is a response message, the target system identification field is identification information of the second node.

[0056] In yet another possible implementation, the first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

[0057] In yet another possible implementation, at least one of the length of the target network address field and the length of the source network address field is variable.

[0058] In yet another possible implementation, if the first node has been configured with a second network address, the source network address field in the second message includes the second network address, where the second network address is different from the first network address.

[0059] In yet another possible implementation, if the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

[0060] In another possible implementation, the address type field is indicated by N bits, and when the value of the N bits is a first value, it indicates the first address type, where N is a positive integer greater than 0.

[0061] In another possible implementation, the first message includes a frame header part and a data part, the data part includes an address query protocol part, and the address query protocol part includes the target network address field, the address type field, and the target system identification field.

[0062] Regarding the technical effects brought about by the sixth aspect or possible implementation methods, reference may be made to the introduction to the technical effects of the second aspect or corresponding implementation methods.

[0063] In the seventh aspect, the present application provides an address conflict detection device, which includes: a communication unit and a processing unit, the communication unit being used to receive a first message from a second node, the first message including a target network address and a network address of a third node; the third node being a neighbor of the second node, and the third node being a relay node for the device and the second node; a node network address mapping table being stored in the device; the node network address mapping table being used for address conflict detection; the processing unit being used to determine whether there is an address conflict for the target network address based on the node network address mapping table; the node network address mapping table indicating a mapping relationship between identification information of multiple nodes and the network addresses of the multiple nodes, wherein the multiple nodes include the second node and the third node; the communication unit being further used to send a second message to the second node, the second message being used to indicate that there is no address conflict for the target network address; the second message being a unicast message; or, the communication unit being further used to send a third message to the second node through the third node, the third message being used to indicate that there is an address conflict for the target network address.

[0064] In another possible implementation, the processing unit is used to match the target network address with the network address of the node in the node network address mapping table; the processing unit is also used to determine whether there is an address conflict in the target network address if the match is successful; the processing unit is also used to determine whether there is an address conflict in the target network address if the match is unsuccessful.

[0065] Regarding the technical effects brought about by the seventh aspect or possible implementation methods, reference may be made to the introduction to the technical effects of the third aspect or corresponding implementation methods.

[0066] In the eighth aspect, the present application provides an address conflict detection device, which includes: a communication unit and a processing unit, the communication unit being used to send a first message to a first node, the first message including a target network address and a network address of a third node; the third node is a neighbor of the device, and the third node is a relay node between the first node and the device; a node network address mapping table is stored in the first node; the node network address mapping table is used to determine whether there is an address conflict for the target network address; the node network address mapping table indicates a mapping relationship between identification information of multiple nodes and the network addresses of the multiple nodes, wherein the multiple nodes include the device and the third node; the communication unit is used to receive a second message from the first node, the second message is used to indicate that there is no address conflict for the target network address, and the second message is a unicast message; or, the communication unit is used to receive a third message from the third node, the third message is used to indicate that there is an address conflict for the target network address.

[0067] In a possible implementation manner, the device is a terminal node.

[0068] Regarding the technical effects brought about by the eighth aspect or possible implementation methods, please refer to the introduction to the technical effects of the fourth aspect or corresponding implementation methods.

[0069] In a ninth aspect, the present application provides an address conflict detection device, comprising at least one processor and a communication interface, wherein the communication interface is configured to provide information input and / or output to the at least one processor. The device is configured to implement the method of the first aspect or any possible embodiment of the first aspect.

[0070] In a tenth aspect, the present application provides an address conflict detection device, comprising at least one processor and a communication interface, wherein the communication interface is configured to provide information input and / or output to the at least one processor. The device is configured to implement the method of the second aspect or any possible embodiment of the second aspect.

[0071] In an eleventh aspect, the present application provides an address conflict detection device, comprising at least one processor and a communication interface, wherein the communication interface is configured to provide information input and / or output to the at least one processor. The device is configured to implement the method of the third aspect or any possible embodiment of the third aspect.

[0072] In a twelfth aspect, the present application provides an address conflict detection device, comprising at least one processor and a communication interface, wherein the communication interface is configured to provide information input and / or output to the at least one processor. The device is configured to implement the method of the fourth aspect or any possible embodiment of the fourth aspect.

[0073] In a thirteenth aspect, the present application provides a computer-readable storage medium comprising computer instructions, which, when executed by a processor, implement the method in any one of the above aspects or any possible implementation of any one of the aspects.

[0074] In a fourteenth aspect, the present application provides a computer program product that, when executed by a processor, implements the method described in any one of the aforementioned aspects or any possible implementation of any one of the aspects. The computer program product, for example, may be a software installation package. When the method provided in any one of the aforementioned aspects or any possible implementation of any one of the aspects is required, the computer program product may be downloaded and executed on a processor to implement the method described in any one of the aspects or any possible implementation of any one of the aspects.

[0075] In the fifteenth aspect, the present application provides a communication system, which includes a first device and a second device, wherein the first device is the device of the fifth aspect or any possible implementation of the fifth aspect, or the device of the seventh aspect or any possible implementation of the seventh aspect; the second device is the device of the sixth aspect or any possible implementation of the sixth aspect, or the device of the eighth aspect or any possible implementation of the eighth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] FIG1 is a schematic diagram of some communication system architectures provided by embodiments of the present application;

[0077] FIG2 is a schematic diagram of a smart home wireless communication scenario provided by an embodiment of the present application;

[0078] FIG3 is a flow chart of an address conflict detection method provided by an embodiment of the present application;

[0079] FIG4 is a schematic diagram of a scenario proposed in an embodiment of the present application;

[0080] FIG5 is a schematic diagram of another scenario proposed in an embodiment of the present application;

[0081] FIG6 is a flowchart of another address conflict detection method provided in an embodiment of the present application;

[0082] FIG7 is a schematic diagram of another scenario proposed in an embodiment of the present application;

[0083] FIG8 is a schematic diagram of another scenario proposed in an embodiment of the present application;

[0084] FIG9 is a schematic diagram of another scenario proposed in an embodiment of the present application;

[0085] FIG10 is a flowchart of another address conflict detection method provided in an embodiment of the present application;

[0086] FIG11 is a schematic diagram of another scenario provided in an embodiment of the present application;

[0087] FIG12 is a flowchart of another address conflict detection method provided in an embodiment of the present application;

[0088] FIG13 is a schematic diagram of another scenario provided by an embodiment of the present application;

[0089] FIG14 is a schematic structural diagram of an address conflict detection device provided in an embodiment of the present application;

[0090] FIG15 is a schematic structural diagram of an address conflict detection device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0091] The terms used in the embodiments of this application are for the purpose of describing specific embodiments only and are not intended to limit this application. Prefixes such as "first" and "second" are used in the specification and claims of this application only to distinguish different description objects and do not have any limiting effect on the position, order, priority, quantity or content of the described objects. The use of prefixes to distinguish description objects in the embodiments of this application does not constitute a limitation on the described objects. For the statement of the described objects, please refer to the description in the context of the claims or embodiments, and no unnecessary limitations should be constituted due to the use of such prefixes.

[0092] It should be noted that the descriptions used in the embodiments of the present application, such as "at least one of a1, a2, ..., or an" include any one of a1, a2, ..., and an existing alone, and any combination of any multiple of a1, a2, ..., and an, each of which can exist alone. For example, the description "at least one of a, b, or c" includes a alone, b alone, c alone, a combination of a and b, a combination of a and c, a combination of b and c, or a combination of a, b, and c.

[0093] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0094] Referring to FIG. 1 , FIG. 1 exemplarily shows schematic diagrams of three communication system architectures applicable to embodiments of the present application, such as shown in (a), (b) and (c) in FIG. 1 .

[0095] The communication domain includes multiple nodes, and there is a communication connection relationship (ie, communication link) between the nodes, and the nodes can exchange information through the communication link.

[0096] In one possible design, multiple nodes include at least one management node and at least one terminal node, where the management node can also be called a grant node (abbreviated as G node), the terminal node can also be called a terminal node (abbreviated as T node), and can also be simply referred to as a wireless end system (WES). The G node is used to send data scheduling information at the access layer of the communication system (for example, the Star Flash communication system), and the T node is used to receive data scheduling information at the access layer of the communication system and send corresponding data based on the received data scheduling information.

[0097] Figure 1 (a) shows a star-shaped single-hop topology. In Figure 1 (a), the communication domain 1 includes a node G and multiple nodes T (for example, T1, T2, ..., Tn), wherein the node G is the access point of each node T, the node G is the management node in the communication domain 1, and the node G can allocate an IP address to the node T. For example, the node G acts as a DHCP server to allocate an IP address to the node T, or the node G acts as an IP address allocation agent to request the DHCP server to allocate an IP address to the node T. In some possible embodiments, the communication domain 1 can be, for example, the Star Flash domain in the Star Flash communication system. In this case, the node G can also allocate a network address of the communication domain address type to the node T to achieve addressing within the Star Flash communication system. In Figure 1 (a), the communication between the node G and the node T can be a two-way unicast or a broadcast communication of G->T.

[0098] Optionally, the architecture shown in (a) of Figure 1 is applicable to in-vehicle communication scenarios. For example, in an in-vehicle communication scenario, node G can be a telematics box (T-Box), and node T can be a user terminal in the vehicle. The user terminal can be, for example, a mobile phone, tablet computer, PDA, desktop computer, headset, audio, wearable device, in-vehicle device, virtual reality device, augmented reality device, etc. T-BOX can also be called a remote in-vehicle terminal or an Internet of Vehicles communication terminal. T-BOX generally acts as a wireless gateway, providing a remote communication interface for the entire vehicle, and provides services including driving data collection, driving trajectory recording, vehicle fault monitoring, vehicle remote query and control, driving behavior analysis, and wireless hotspot sharing. For example, T-Box can send collected vehicle data (such as new energy vehicle drive motor data, vehicle data, battery data, status data, etc.) to the cloud platform, and can also forward control commands received from the cloud platform to the vehicle. T-Box can also establish a transmission channel with a mobile phone app via Bluetooth to realize controls such as door opening and locking, window control, air conditioning switch, and engine start and stop.

[0099] Figure 1(b) shows a tree-like multi-hop topology. In Figure 1(b), communication domain 2 includes nodes G1, G2, G3, G4, and nodes T1, T2, and T3. Node G1 is connected to nodes G2 and G3, respectively. Node G2 is also connected to nodes T1 and G4, respectively. Node G3 is also connected to nodes T3 and G4, respectively. Node G4 is also connected to node T2. It can be seen that node G1 is an access point to nodes G2 and G3, respectively. Node G2 is an access point to nodes T1 and G4, respectively. Node G3 is an access point to nodes T3 and G4, respectively. Node G4 is an access point to node T2. Node G1 is a management node within communication domain 2. That is, node G1 has an address allocation function and can allocate network addresses to other nodes within communication domain 2. If nodes G2, G3, and G4 have their own network addresses, nodes G2, G3, and G4 can have an address allocation proxy service function.

[0100] It can be understood that in this communication scenario, communication domain 2 includes multiple nodes G (respectively, nodes G1, G2, G3, and G4) and multiple nodes T (respectively, nodes T1, T2, and T3). Node G1 is the management node within communication domain 2, and nodes G2, G3, and G4 are communication nodes with dual identities. Taking node G2 as an example, for communication between node G2 and node T1, node G2 acts as a G node and node T1 acts as a T node. For communication between node G2 and node G1, node G1 acts as a G node and node G2 acts as a T node. Communication nodes with dual identities like G2 can be denoted as G2(T).

[0101] Optionally, the architecture shown in (b) of Figure 1 is applicable to smart home scenarios. Referring to Figure 2, Figure 2 is a schematic diagram of a smart home wireless communication scenario provided by an embodiment of the present application. In Figure 2, node G has IP capabilities, and node G includes gateway / customer premises equipment (CPE), sub-router, mobile phone and large screen, wherein the management node in the communication domain shown in Figure 2 can be a gateway / customer premises equipment (CPE), and the node G with dual identity can be a sub-router, mobile phone and large screen. The T nodes in Figure 2 include smart lights, air conditioners, printers, microphones and speakers, including both node G that supports IP, such as printers, and node G that does not support IP, such as smart lights, air conditioners, etc.

[0102] Figure 1(c) shows a tree-like three-layer multi-hop topology. In Figure 1(c), communication domain 3 includes nodes G1, G2, and G3, as well as nodes T1, T2, T3, and T4. Node G1 is connected to nodes G2 and G3, respectively, meaning that node G1 is the access point for nodes G2 and G3. Node G2 is connected to nodes T1 and T2, meaning that node G2 is the access point for nodes T1 and T2. Node G3 is connected to nodes T3 and T4, meaning that node G3 is the access point for nodes T3 and T4. Node G1 serves as the management node within communication domain 3. Node G1 can provide address allocation services, while nodes G2 and G3 can provide address allocation proxy services. In Figures 1(b) and 1(c), communication between node G and node T can be bidirectional unicast (T->G(T)->G) or broadcast (G->G(T)->T).

[0103] Optionally, the architecture shown in FIG1(c) is applicable to a battery management system (BMS). For example, in FIG1(c), node G1 may be a battery control unit (BCU) in the BMS, nodes T1, T2, T3, and T4 may be battery monitoring units (BMUs), and nodes G2 and G3 may be BMUs with address allocation proxy service functionality.

[0104] It should be noted that Figure 1 is only an exemplary architecture diagram and may also be an architecture diagram in other forms, for example, a tree-like four-layer (or more-layer) multi-hop topology. Although not shown in Figure 1, in addition to the functional entities shown in Figure 1, the communication system may also include other functional entities.

[0105] In another possible design, the multiple nodes may include at least one intermediate node and at least one address resolution node. The intermediate node may also be referred to as an intermediate node (abbreviated as I node), or as a wireless intermediate system (WIS), and the address resolution node may also be referred to as an address resolver node (abbreviated as A node). The I node is used to receive data scheduling information at the access layer of the communication system, and may also forward the data scheduling information to the T node. The A node is used to query the network address of any node (for example, the Star Flash network address), the connection relationship between the I node and the T node, etc. Among them, the I node and the T node can register their own network addresses with the A node and carry the node's identifier.

[0106] In another possible design, the multiple nodes may include at least one terminal node and at least one intermediate node, wherein the at least one intermediate node constitutes a backbone network, and each terminal node of the at least one terminal node accesses the network through an intermediate node of the at least one intermediate node.

[0107] In addition, the method provided in the embodiment of the present application can be applied to the communication system shown in Figure 1. Of course, the method provided in the embodiment of the present application can also be applied to other communication systems, and the embodiment of the present application is not limited to this.

[0108] Generally, wireless networks may experience address conflicts due to incorrect networking or configuration. Address conflicts can cause network routing oscillations, interruptions to network services or traffic, and other issues, significantly impacting user services. Therefore, how to detect address conflicts in a network and promptly notify users of the source of the conflict, thereby helping users quickly eliminate the conflicting configuration and effectively minimizing the impact on services, is a technical problem currently being addressed by those skilled in the art. To address these issues, the present application proposes the following solutions.

[0109] See Figure 3, which is a flow chart of an address conflict detection method provided by an embodiment of the present application. Optionally, the method can be implemented based on the aforementioned communication system, such as the communication system shown in Figure 1. The method includes but is not limited to the following steps:

[0110] S301: A first node sends a first message, and correspondingly, a second node receives the first message.

[0111] The first message is carried in a general layer broadcast protocol.

[0112] The first node may send a first message via broadcast. The first message includes a target network address field, an address type field, and a target system identifier field. The target network address field indicates a first network address, and the address type field indicates a first address type corresponding to the first network address, where the first address type belongs to one of multiple address types. The first network address may be a network address to be detected or queried, and may be a unicast address. The multiple address types may include at least two of the following: a Starflash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address. The Starflash network address may be type 1, occupying 2 bytes (i.e., 16 bits). The Starflash network address may be understood as an address used for routing defined within the Starflash network. It is a network layer short address, which may be 2 bytes (i.e., 16 bits) in length and may be used for addressing within the corresponding communication system. For example, with Starflash communication technology, the Starflash network address may be used for addressing within the Starflash communication system. It is understood that the Starflash network address is a different address type from the IP address. A custom address can be of type 2, occupying 1-16 bytes; an Internet Protocol version 4 (IPv4) address can be of type 4, occupying a maximum of 4 bytes; an Internet Protocol version 6 (IPv6) address can be of type 6, occupying a maximum of 16 bytes. The address type field can be indicated by N bits. When the value of the N bits is the first value, it indicates the first address type, where N is a positive integer greater than or equal to 0. For example, when the first value is 0000001, it indicates that the first address type is a Star Flash network address; when the first value is 0000010, it indicates that the first address type is a custom address; when the first value is 0000100, it indicates that the first address type is an IPv4 address; when the first value is 0000110, it indicates that the first address type is an IPv6 address.

[0113] The target system identification field is used to indicate the identification information of the node configured with the first network address. When the first message is a request message, the target system identification field is a default value or a default value, and the request message is used to query whether there is an address conflict with the first network address. For example, when the first message is a request message, the target system identification field can be a default value, such as 0. The target system identification field can be configured by the user or obtained based on the device identification; the device identification can refer to the media access layer identification, such as the Layer 2 Identification (L2ID); wherein the device identification is unique. When the target system identification field can be configured by the user, it can be changed.

[0114] Among them, the first message may also include a network address length field, a source network address field, a source system identification field or a reserved field. The network address length field refers to the length of the target network address field or the source network address field, in bytes. For example, when the target network address or source network address field is type 4, which occupies a maximum of 4 bytes, the address length indicated by the network address length field is 4. The source network address field is used to indicate the network address of the node that initiates the detection or query, which can be a unicast address, and the source system identification field is used to indicate the identifier of the node that initiates the detection or query. For example, the node that initiates the detection or query is the first node, and the first node has been configured with a network address of 1.1. Now a new first network address is configured, and the first network address is 100.1. Then the source network address field can be 1.1, and the source system identification field can be the identifier of the first node, for example, 1234.1234.1234. For another example, if the node initiating the detection or query is a first node, which has not been configured with a network address but is now configured with a first network address of 100.1, the source network address field may be a default value, such as 0, and the source system identifier field may be the identifier of the first node, such as 1234.1234.1234. At least one of the length of the target network address field and the length of the source network address field may be variable.

[0115] The first message may include a frame header portion and a data portion, the data portion including an address query protocol (AQP) portion, and the address query protocol portion including a target network address field, an address type field, and a target system identification field. The address query protocol portion may also include a network address length field, a source network address field, a source system identification field, or a reserved field. The first message is sent via broadcast, and the first message is carried in a general layer broadcast protocol. The destination address of the frame header portion of the first message may be a broadcast address, for example, 255.255.

[0116] In one example, as shown in Figure 4, Figure 4 is a schematic diagram of a scenario proposed in an embodiment of the present application. Assume that node S has been configured with a second network address of 1.1, and now a new first network address of 100.1 is configured. At this time, node S initiates address conflict detection or query to check whether there is a node in the network that has been configured with the first network address 100.1. Node S can broadcast and send a first message, which is used for address conflict detection or query, wherein the frame header part of the first message is shown in Table 1, and the data part of the first message is shown in Table 2. According to Table 1, it is obtained that: since node S has been configured with the second network address 1.1, the source address in the frame header part of the first message is 1.1, and since the first message is sent by broadcast, the destination address in the frame header part of the first message is 255.255. According to Table 2, it is obtained that: the target network address field indicates the first network address, which can refer to the network address to be detected or to be queried. Since the newly configured network address of node S is 100.1, the target network address field indicates that the first network address is 100.1. The address type field may refer to the first address type corresponding to the first network address, for example, the first address type may be a star flash network address. The target system identification field is used to indicate the identification information of the node configured with the first network address. Since it is necessary to query whether there is a conflict in the first network address at this time, the target system identification field may be a preset value, for example, 0. The source network address field is used to indicate the network address of the node initiating the detection or query, that is, the network address of node S, so the source network address field may be 1.1; the source system identification field is used to indicate the identification of the node initiating the detection or query, that is, the identification of node S, for example, the identification of node S is 1234.1234.1234. The network address length field is used to indicate the length of the target network address field or the source network address field, wherein the first network address indicated by the target network address field is 100.1, the source network address field may be 1.1, and the length indicated by the network address length field may be 2.

[0117] Table 1

[0118]

[0119] Table 2

[0120]

[0121] In another example, as shown in Figure 5, Figure 5 is a schematic diagram of a scenario proposed in an embodiment of the present application. Assume that node S needs to be configured with a first network address of 100.1, and the node S is not configured with any other network address except the first network address. At this time, node S initiates an address conflict detection or query to check whether there is a node in the network that has been configured with the first network address 100.1. Node S can broadcast a first message, which is used for address conflict detection or query, wherein the frame header portion of the first message is shown in Table 3, and the data portion of the first message is shown in Table 4. According to Table 3, it can be obtained that since node S is not configured with any other network address except the first network address, the source address in the frame header portion of the first message can be a default value or a default value, for example, the default value can be 0.0. Since the first message is sent by broadcast, the destination address of the frame header portion of the first message is 255.255. According to Table 4, the target network address field indicates the first network address, which can refer to the network address to be detected or queried. Since the first network address that node S needs to configure is 100.1, the target network address field indicates that the first network address is 100.1. The address type field can refer to the first address type corresponding to the first network address, for example, the first address type can be a Star Flash network address. The target system identifier field is used to indicate the identification information of the node configured with the first network address. Since it is necessary to query whether the first network address conflicts, the target system identifier field can be a preset value, for example, 0. The source network address field is used to indicate the network address of the node initiating the detection or query, that is, the network address of node S. Since node S is not configured with any network address other than the first network address, the source network address field can be a default value or a default value, for example, the default value can be 0.0. The source system identifier field is used to indicate the identifier of the node initiating the detection or query, that is, the identifier of node S. For example, the identifier of node S is 1234.1234.1234. The network address length field is used to indicate the length of the target network address field or the source network address field. The first network address indicated by the target network address field is 100.1, and the source network address field can be 0.0, then the length indicated by the network address length field can be 2.

[0122] Table 3

[0123]

[0124] Table 4

[0125]

[0126] S302: The second node sends a second message to the first node. Correspondingly, the first node receives the second message from the second node.

[0127] It should be noted that the second node can be any node in the network, and the first node is the node that initiates network address detection or query. Exemplarily, in (a) of Figure 1, the second node can be any node T or node G among nodes T1, T2, ..., Tn, and the first node can be a node that initiates network address detection or query other than the second node. In (b) of Figure 1, the second node can be any node among nodes T1, T2 and T3, or any node among G1, G2, G3 and G4, and the first node can be a node that initiates network address detection or query other than the second node. In (c) of Figure 1, the second node can be any node among nodes T1, T2, T3 and T4, or any node among G1, G2, and G3, and the first node can be a node that initiates network address detection or query other than the second node.

[0128] The second node may send the second message to the first node via unicast or broadcast. When the source address in the frame header of the first message is not a default value or a non-default value but a unicast address, the second node may send the second message via unicast. When the source address in the frame header of the first message is a default value or a default value, the second node may send the second message via broadcast. The second message indicates whether there is an address conflict with the first network address. In other words, when the source network address in the data portion of the first message is not a default value or a non-default value but a unicast address, the second node may send the second message via unicast. When the source network address in the data portion of the first message is a default value or a default value, the second node may send the second message via broadcast. When the second message is a response message, the target system identification field contains the identification information of the second node. This response message responds to a request to inquire whether there is an address conflict with the first network address.

[0129] The second message includes a target network address field, an address type field, and a target system identifier field. The target network address field indicates the first network address; the address type field indicates a first address type corresponding to the first network address, where the first address type is one of the multiple address types; and the target system identifier field indicates the identifier of the node configured with the first network address. For details, refer to the relevant description in step S301.

[0130] The second message may further include a network address length field, a source network address field, a source system identification field, or a reserved field. The network address length field refers to the length of the target network address field or the source network address field, in bytes. The source network address field is used to indicate the network address of the node initiating the detection or query, which may be a unicast address. The source system identification field is used to indicate the identification of the node initiating the detection or query. At least one of the length of the target network address field and the length of the source network address field is variable. For details, please refer to the relevant description in step S301.

[0131] The second message may include a frame header and a data portion. The data portion includes an AQP portion, which includes a target network address field, an address type field, and a target system identifier field. The AQP portion may also include a network address length field, a source network address field, a source system identifier field, or a reserved field. For details, refer to the relevant description in step S301.

[0132] Optionally, if the first node has been configured with a second network address, the source network address field in the second message includes the second network address, where the second network address is different from the first network address. This means that when the first node has been configured with the second network address, the source network address field in the first message includes the second network address, and accordingly, the source network address field in the second message includes the second network address. For example, if the first node has been configured with the second network address 1.1 and is now newly configured with the first network address, that is, the first network address is 100.1, the source network address field in the first message may be 1.1, and accordingly, the source network address field in the second message may be 1.1.

[0133] Optionally, if the first node is not configured with a network address other than the first network address, the source network address field in the second message is a default value or a default value, that is, it can be understood that when the first node is not configured with a network address other than the first network address, the source network address field in the first message includes a default value or a default value, and accordingly, the source network address field in the second message includes the default value or the default value. For another example, the node initiating the detection or query is the first node, and the first node is not configured with a network address other than the first network address, and is now configured with the first network address, that is, the first network address is 100.1. The source network address field in the first message can be a default value, such as 0, and accordingly, the source network address field in the second message can be the default value, such as 0.

[0134] In one example, as shown in Figure 4, Figure 4 is a schematic diagram of a scenario proposed in an embodiment of the present application. Assume that node S has been configured with a second network address of 1.1, and now a first network address of 100.1 is newly configured. At this time, node S initiates an address conflict detection or query to check whether there is a node in the network that has been configured with the first network address 100.1. Assume that the frame header portion of the first message is as shown in Table 1, and the data portion of the first message is as shown in Table 2. Assume that node T in the network has been configured with the first network address 100.1. After receiving the first message, T parses the first message and determines that the target network address field in the first message indicates that the first network address 100.1 is the same as its own network address. Then, node T can send a second message to node S in a unicast manner, wherein the frame header portion of the second message is as shown in Table 5, and the data portion of the second message is as shown in Table 6. According to Table 5, it is obtained that since node T has been configured with the first network address 100.1, the source address of the frame header portion of the second message is 100.1; since node S has been configured with the second network address 1.1, the destination address of the frame header portion of the second message is 1.1. According to Table 6, it can be seen that: According to Table 2, the target network address field of the data part in the first message indicates the first network address, which can refer to the network address to be detected or to be queried. Therefore, the target network address field of the data part in the second message indicates that the first network address is 100.1; the target system identification field indicates the identification of the node configured with the first network address, wherein node T has been configured with the first network address 100.1, and the target system identification field indicates the identification of node T, for example, 2222.2222.2222; According to the source network address field, source system identification field and network length field of the data part in the first message, it can be seen that the source network address field of the data part in the second message can be 1.1, the source system identification field can be 1234.1234.1234, and the length indicated by the network length field can be 2.

[0135] Form 5

[0136]

[0137] Table 6

[0138]

[0139] In another example, as shown in Figure 5, Figure 5 is a schematic diagram of a scenario proposed in an embodiment of the present application. Assume that node S needs to be configured with a first network address of 100.1, and the node S is not configured with any network address other than the first network address. At this time, node S initiates an address conflict detection or query to check whether there is a node in the network that has been configured with the first network address 100.1. Assume that the frame header portion of the first message is as shown in Table 3, and the data portion of the first message is as shown in Table 4. Assume that node T in the network has been configured with the network address 100.1. After T receives the first message, it parses the first message and determines that the target network address field in the first message indicates that the first network address 100.1 is the same as its own network address. Then, node T can send a second message to node S by broadcasting, wherein the frame header portion of the second message is as shown in Table 7, and the data portion of the second message is as shown in Table 8. According to Table 7, since node T has been configured with the first network address 100.1, the source address of the frame header of the second message is 100.1; since node S has not been configured with any network address other than the first network address, the destination address of the frame header of the second message is 255.255. According to Table 8, it can be seen from Table 4 that the target network address field of the data part in the first message indicates the first network address, which can refer to the network address to be detected or to be queried. Therefore, the target network address field of the data part in the second message indicates that the first network address is 100.1; the target system identification field indicates the identification of the node configured with the first network address, wherein node T has been configured with the first network address 100.1, and the target system identification field indicates the identification of node T, for example, 2222.2222.2222; according to the source network address field, source system identification field and network length field of the data part in the first message, it can be seen that the source network address field of the data part in the second message can be 0.0, the source system identification field can be 1234.1234.1234, and the length indicated by the network length field can be 2.

[0140] Form 7

[0141]

[0142] Form 8

[0143]

[0144] In the above method, the inclusion of the target network address field, the address type field, and the target system identifier field in the first message enables network-wide address conflict detection, thereby promptly notifying users of the source of the address conflict and helping them quickly eliminate the address conflict configuration, effectively minimizing the impact on their services. Furthermore, by including the address type field in the first message, address conflict detection for multiple address types can be implemented, enhancing diversity.

[0145] See Figure 6, which is a flow chart of another address conflict detection method provided by an embodiment of the present application. Optionally, the method can be implemented based on the aforementioned communication system, such as the communication system shown in Figure 1. The method includes but is not limited to the following steps:

[0146] S601: The second node sends a first message to the first node. Correspondingly, the first node receives the first message from the second node.

[0147] Wherein, the first message includes the target network address and the network address of the third node. Wherein, the target network address can be a star flash network address, and the network address of the third node can be a star flash network address. The third node is a neighbor of the second node, and the third node is a relay node for the first node and the second node. Wherein, the third node is a neighbor of the second node, which can be understood as, the third node and the second node are two directly connected nodes, and are each other's neighbor nodes. The third node is a neighbor of the first node, which can be understood as, the third node and the first node are two directly connected nodes, and are each other's neighbor nodes. The second node can send the first message to the first node in a unicast manner. It should be noted that the second node can be any node, for example, the second node can be a terminal node, and the first node is an address resolution node. Exemplarily, in (a) of Figure 1, the second node can be any node T or node G among nodes T1, T2, ..., Tn, the first node can be an address resolution node, and the third node is a relay node for the first node and the second node. In Figure 1(b), the second node may be any node among nodes T1, T2, and T3, or any node among G1, G2, G3, and G4, the first node may be an address resolution node, and the third node may be a relay node between the first and second nodes. In Figure 1(c), the second node may be any node among nodes T1, T2, T3, and T4, or any node among G1, G2, and G3, the first node may be an address resolution node, and the third node may be a relay node between the first and second nodes.

[0148] The first node stores a node network address mapping table, which is used for address conflict detection. It can be understood that the node network address mapping table is used to determine whether there is an address conflict in the target network address.

[0149] S602: The first node determines whether there is an address conflict in the target network address according to the node network address mapping table.

[0150] Among them, the node network address mapping table indicates the mapping relationship between the identification information of multiple nodes and the network addresses of multiple nodes, and the multiple nodes include the second node and the third node. It can be understood that the node network address mapping table includes the mapping relationship between the identification information of the second node and the network address of the second node, and the mapping relationship between the identification information of the third node and the network address of the third node. The identification of a node can correspond to multiple network addresses of the node. For example, the identification information of node 1 includes ID1, and node 1 includes two network addresses, namely address 1 and address 2.

[0151] Optionally, the first node determines whether there is an address conflict in the target network address according to the node network address mapping table in the following manner: the first node matches the target network address with the network address of the node in the node network address mapping table; if the match is successful, the first node determines that there is an address conflict in the target network address; if the match is not successful, the first node determines that there is no address conflict in the target network address.

[0152] In one example, for example, the target network address is 100.2, and the node network address mapping table is shown in Table 9. The first node matches 100.2 with the network address in the node network address mapping table, and determines that the network address of the node corresponding to the node identifier ID1 is 100.2, that is, the match is successful, then the first node determines that there is an address conflict in the target network address.

[0153] Form 9

[0154] Node identification Node network address ID1100.2ID12.1ID2102.1ID3105.1ID3110.2

[0155] S603: The first node sends a second message to the second node.

[0156] Wherein, the second message is used to indicate that there is no address conflict for the target network address. That is, it can be understood that when the first node determines that there is no address conflict for the target network address, the first node directly sends the second message to the second node, and the second message indicates that there is no address conflict for the target network address. Wherein, the first node directly sends the second message to the second node, the first node locally queries the forwarding table entry based on the target network address, and then forwards the second message to the second node, which is specifically embodied as follows: As shown in Figure 7, the three-layer message from the first node to the second node will not change, and the three-layer message includes the second message, but the two-layer message header from the first node to the third node is changed. After the message is transmitted to the third node, the two-layer message header from the second node to the third node is deleted, re-encapsulated as the two-layer message header from the third node to the second node, and transmitted to the second node.

[0157] S604: The first node sends a third message to the second node through the third node.

[0158] Among them, the third message is used to indicate that there is an address conflict in the target network address. That is, it can be understood that when the first node determines that there is a conflict in the target network address according to the node network address mapping table, the first node sends a third message to the third node by unicast according to the network address of the third node, and then the third node sends the third message to all neighbors except the first node. Correspondingly, the second node receives the third message from the third node and determines that there is an address conflict in the target network address. As shown in Figure 8, the first node sends the third message to the third node. After receiving the third message, the third node can copy the third message into two copies and send them to the second node and node C respectively.

[0159] The third message may be a General Message Packet Data Unit (GMP) message. The format of the GMP message is shown in Table 10. The variable length field in the GMP message may be used to indicate whether there is an address conflict with the target network address. For example, when the variable length field in the GMP message is 1, it indicates that there is an address conflict with the target network address.

[0160] Form 10

[0161]

[0162] In the above method, the first node sends the third message to the third node by unicast according to the network address of the third node, so that the third node forwards the third message to the second node, which can avoid the broadcast message from bringing too much load to the network. For example, as shown in Figure 9, the second node needs to configure the target network address as 1.1, the third node is the relay node of the first node and the second node, and the C node has been configured with the network address 1.1. After the first node detects that there is a conflict in the target network address, if the third message is sent according to the target network address 1.1, the C node will also receive the third message, thereby increasing the signaling overhead. Therefore, the third message is sent to the third node by unicast, so that the third node forwards the third message to the second node, thereby saving signaling overhead and avoiding the broadcast message from bringing too much load to the network.

[0163] In the above method, the first node can send the second message to the second node via unicast, or send the third message to the third node via unicast. In this way, it can avoid broadcast messages from bringing more load to the network, thereby saving network overhead. Moreover, by storing a node network address mapping table in the first node, the first node can detect address conflicts across the entire network.

[0164] See Figure 10, which is a flow chart of an address conflict detection method provided by an embodiment of the present application. Optionally, the method can be implemented based on the aforementioned communication system, such as the communication system shown in Figure 1. The method includes but is not limited to the following steps:

[0165] S1001: A second node sends a first message to a first node. Correspondingly, the first node receives the first message from the second node.

[0166] The first message includes the network address of the second node. Optionally, the network address of the second node may be a StarFlash network address. Optionally, the first message may be carried in a hello message, which is used to discover neighbors on a directly connected link and maintain neighbor relationships.

[0167] S1002: The first node determines whether there is an address conflict in the network address of the second node based on the network address of the second node and the network address of the third node.

[0168] Among them, the first node can be an I node, the second node can be a T node, and the third node can be a T node. The first node and the second node are neighbors, and the first node and the third node are neighbors. The first node and the second node are neighbors, and it can be understood that the first node and the second node are two directly connected nodes and are each other's neighbor nodes. The first node and the third node are neighbors, and it can be understood that the first node and the third node are two directly connected nodes and are each other's neighbor nodes. For example, as shown in Figure 11, the second node and the third node can be end nodes under the first node. The first node can establish neighbors with the second node and the third node through the wireless adjacency protocol (WAP).

[0169] The network address of the third node can be obtained in two ways: first, the first node stores the network address of the third node before receiving the network address from the second node; second, the first node receives the network address from the third node before or after receiving the network address from the second node. Optionally, the network address of the third node can be a Star Flash network address.

[0170] The first node determines whether there is a conflict in the network address of the second node based on the network address of the second node and the network address of the third node, specifically including the following: (1) If the network address of the second node is the same as the network address of the third node, the first node sends a second message to the second node and the third node. The second message is used to indicate that there is an address conflict in the network address of the second node. After receiving the second message, the second node and the third node can remind the user that there is an address conflict in the network address of the second node through alarms, logs, etc. Correspondingly, the user can resolve the address conflict by modifying the network address of the second node. (2) If the network address of the second node is different from the network address of the third node, it is determined that there is no address conflict.

[0171] In the above method, the first node determines whether there is an address conflict in the network address of the second node based on the network address of the second node and the network address of the third node, thereby enabling detection of address conflicts across the entire network.

[0172] See Figure 12, which is a flow chart of an address conflict detection method provided by an embodiment of the present application. Optionally, the method can be implemented based on the aforementioned communication system, such as the communication system shown in Figure 1. The method includes but is not limited to the following steps:

[0173] S1201: A first node receives a first message from a second node.

[0174] The first message includes the network address of the second node. Optionally, the network address of the second node may be a StarFlash network address. Optionally, the first message may be carried in a hello message, which is used to discover neighbors on a directly connected link and maintain neighbor relationships.

[0175] S1202: The first node determines whether there is an address conflict in the network address of the second node based on the network address of the second node and the network address of the first node.

[0176] As shown in FIG13(a), the first node may be an I-node, and the corresponding second node may be a T-node, which can be understood as the second node being an end node under the first node. Alternatively, as shown in FIG13(b), the first node may be an I-node, and the corresponding second node may be an I-node. The first node and the second node are neighbors, which can be understood as two directly connected nodes and are each other's neighbor nodes. The first node can establish a neighbor relationship with the second node via the Wireless Adjacency Protocol (WAP).

[0177] Optionally, the network address of the first node may be a Star Flash network address. The first node may determine whether there is an address conflict with the network address of the second node based on the network address of the second node and the network address of the first node, which may include the following two methods: a first method: if the network address of the second node is the same as the network address of the first node, then there is an address conflict with the network address of the second node; a second method: if the network address of the second node is different from the network address of the first node, then there is no address conflict with the network address of the second node.

[0178] In the above method, the first node determines whether there is an address conflict in the network address of the second node based on the network address of the second node and the network address of the first node, thereby enabling detection of address conflicts across the entire network.

[0179] Refer to Figure 14, which is a structural diagram of an address conflict detection device 1400 provided in an embodiment of the present application. The address conflict detection device 1400 includes: a communication unit 1401 and a processing unit 1402. The device 1400 can be implemented by hardware, software, or a combination of hardware and software.

[0180] The communication unit 1401 is used to send a first message, which includes a target network address field, an address type field and a target system identification field. The target network address field indicates a first network address, and the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address; the communication unit 1401 is also used to receive a second message from a second node, and the second message indicates whether there is an address conflict for the first network address.

[0181] In a possible implementation, the multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

[0182] In another possible implementation, when the first message is a request message, the target system identification field is a default value or a default value. The request message is used to query whether there is an address conflict in the first network address.

[0183] In another possible implementation, the second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

[0184] In another possible implementation, when the second message is a response message, the target system identification field is identification information of the second node. In another possible implementation, the first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

[0185] In yet another possible implementation, at least one of the length of the target network address field and the length of the source network address field is variable.

[0186] In yet another possible implementation, if the first node has been configured with a second network address, the source network address field in the second message includes the second network address, where the second network address is different from the first network address.

[0187] In yet another possible implementation, if the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

[0188] In another possible implementation, the address type field is indicated by N bits, and when the value of the N bits is a first value, it indicates the first address type, where N is a positive integer greater than 0.

[0189] In another possible implementation, the first message includes a frame header part and a data part, the data part includes an address query protocol part, and the address query protocol part includes the target network address field, the address type field, and the target system identification field.

[0190] It should be noted that the implementation and beneficial effects of each unit may also correspond to the corresponding description of the method embodiment shown in FIG3 .

[0191] Optionally, the detailed description of each unit in the address conflict detection device 1400 may also be as follows.

[0192] The communication unit 1401 is used to receive a first message, which includes a target network address field, an address type field and a target system identification field, wherein the target network address field indicates a first network address, and the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address; the communication unit 1401 is also used to send a second message to the first node, and the second message indicates whether there is an address conflict for the first network address.

[0193] In a possible implementation, the multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

[0194] In another possible implementation, when the first message is a request message, the target system identification field is a default value or a default value. The request message is used to query whether there is an address conflict in the first network address.

[0195] In another possible implementation, the second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates a first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

[0196] In another possible implementation, when the second message is a response message, the target system identification field is identification information of the second node. In another possible implementation, the first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

[0197] In yet another possible implementation, at least one of the length of the target network address field and the length of the source network address field is variable.

[0198] In yet another possible implementation, if the first node has been configured with a second network address, the source network address field in the second message includes the second network address, where the second network address is different from the first network address.

[0199] In yet another possible implementation, if the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

[0200] In another possible implementation, the address type field is indicated by N bits, and when the value of the N bits is a first value, it indicates the first address type, where N is a positive integer greater than 0.

[0201] In another possible implementation, the first message includes a frame header part and a data part, the data part includes an address query protocol part, and the address query protocol part includes the target network address field, the address type field, and the target system identification field.

[0202] It should be noted that the implementation and beneficial effects of each unit may also correspond to the corresponding description of the method embodiment shown in FIG3 .

[0203] Optionally, the detailed description of each unit in the address conflict detection device 1400 may also be as follows.

[0204] The communication unit 1401 is used to receive a first message from the second node, the first message including the target network address and the network address of a third node; the third node is a neighbor of the second node, and the third node is the device and is a relay node for the second node; a node network address mapping table is stored in the device; the processing unit 1402 is used to determine whether there is an address conflict for the target network address based on the node network address mapping table; the node network address mapping table indicates a mapping relationship between identification information of multiple nodes and the network addresses of the multiple nodes, wherein the multiple nodes include the second node and the third node; the communication unit 1401 is also used to send a second message to the second node, the second message is used to indicate that there is no address conflict for the target network address; the second message is a unicast message; or, the communication unit 1401 is also used to send a third message to the second node through the third node, the third message is used to indicate that there is an address conflict for the target network address.

[0205] In a possible implementation manner, the second node is a terminal node.

[0206] In another possible implementation, the processing unit 1402 is used to match the target network address with the network address of the node in the node network address mapping table; the processing unit 1402 is also used to determine that there is an address conflict in the target network address when the match is successful; the processing unit 1402 is also used to determine that there is no address conflict in the target network address when the match is unsuccessful.

[0207] It should be noted that the implementation and beneficial effects of each unit may also correspond to the corresponding description of the method embodiment shown in FIG6 .

[0208] Optionally, the detailed description of each unit in the address conflict detection device 1400 may also be as follows.

[0209] The communication unit 1401 is used to send a first message to the first node, the first message including the target network address and the network address of a third node; the third node is a neighbor of the device, and the third node is the first node and a relay node of the device; the first node stores a node network address mapping table; the node network address mapping table is used to determine whether there is an address conflict for the target network address; the node network address mapping table indicates the mapping relationship between the identification information of multiple nodes and the network addresses of the multiple nodes, wherein the multiple nodes include the device and the third node; the communication unit 1401 is used to receive a second message from the first node, the second message is used to indicate that there is no address conflict for the target network address, and the second message is a unicast message; or, the communication unit 1401 is used to receive a third message from the third node, the third message is used to indicate that there is an address conflict for the target network address.

[0210] In a possible implementation manner, the device is a terminal node.

[0211] It should be noted that the implementation and beneficial effects of each unit may also correspond to the corresponding description of the method embodiment shown in FIG6 .

[0212] Please refer to Figure 15, which shows an address conflict detection device 1500 provided in an embodiment of the present application. The address conflict detection device 1500 includes at least one processor 1501 and a communication interface 1503, and optionally also includes a memory 1502. The processor 1501, memory 1502, and communication interface 1503 are interconnected via a bus 1504. Optionally, the processor 1501 and memory 1502 may be integrated together.

[0213] Memory 1502 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM). Memory 1502 is used for storing computer programs and data. Communication interface 1503 is used to receive and send data.

[0214] The processor 1501 may be one or more central processing units (CPUs). When the processor 1501 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0215] The processor 1501 in the address conflict detection device 1500 is used to read the computer program code stored in the memory 1502 to implement the functions of the processing unit 1402 , and the communication interface 1503 is used to implement the functions of the communication unit 1401 .

[0216] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0217] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also exist in a base station or a terminal as discrete components.

[0218] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0219] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different 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.

[0220] In the description of this application, words such as "first", "second", "S601", or "S602" are only used to distinguish the description and facilitate the context. Different sequence numbers themselves do not have specific technical meanings and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying the order of execution of operations. The execution order of each process should be determined by its function and internal logic.

[0221] In this application, the term "and / or" simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. A and B can be singular or plural. Additionally, the character " / " in this document indicates that the related objects are in an "or" relationship.

[0222] In this application, "transmission" may include the following three situations: sending of data, receiving of data, or sending of data and receiving of data. In this application, "data" may include business data and / or signaling data.

[0223] In this application, the terms "comprise" or "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process / method comprising a series of steps, or a system / product / apparatus comprising a series of units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes / methods / products / apparatus.

[0224] In the description of this application, unless otherwise specified, the number of nouns refers to "singular or plural," that is, "one or more." "At least one" means one or more. "Including at least one of the following: A, B, C" means that it may include A, or include B, or include C, or include A and B, or include A and C, or include B and C, or include A, B, and C. A, B, and C can be single or plural.

Claims

1. A method for detecting an address conflict, characterized in that: The method comprises: The first node sends a first message, the first message including a target network address field, an address type field, and a target system identification field, the target network address field indicating a first network address, the address type field indicating a first address type corresponding to the first network address, the first address type being one of multiple address types; and the target system identification field being used to indicate identification information of a node configured with the first network address. The first node receives a second message from a second node, where the second message indicates whether there is an address conflict with the first network address.

2. The method according to claim 1, characterized in that The multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

3. The method according to claim 1 or 2, characterized in that When the first message is a request message, the target system identification field is a default value or a default value.

4. The method according to any one of claims 1 to 3, characterized in that The second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates the first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

5. The method according to claim 4, characterized in that When the second message is a response message, the target system identification field is identification information of the second node.

6. The method according to any one of claims 1 to 5, characterized in that The first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

7. The method according to claim 6, characterized in that At least one of the length of the destination network address field and the length of the source network address field is variable.

8. The method according to any one of claims 1 to 7, characterized in that If the first node has been configured with a second network address, the source network address field in the second message includes the second network address, wherein the second network address is different from the first network address.

9. The method according to any one of claims 1 to 7, characterized in that If the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

10. An address conflict detection method, characterized in that: The method comprises: The second node receives a first message, where the first message includes a target network address field, an address type field, and a target system identification field, wherein the target network address field indicates a first network address, the address type field indicates a first address type corresponding to the first network address, the first address type being one of multiple address types, and the target system identification field is used to indicate identification information of a node configured with the first network address. The second node sends a second message to the first node, where the second message indicates whether there is an address conflict with the first network address.

11. The method according to claim 10, characterized in that The multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

12. The method according to claim 10 or 11, characterized in that When the first message is a request message, the target system identification field is a default value or a default value.

13. The method according to any one of claims 10 to 12, characterized in that: The second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates the first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

14. The method according to claim 13, characterized in that When the second message is a response message, the target system identification field is identification information of the second node.

15. The method according to any one of claims 10 to 14, characterized in that: The first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

16. The method according to claim 15, characterized in that At least one of the length of the destination network address field and the length of the source network address field is variable.

17. The method according to any one of claims 10 to 16, characterized in that: If the first node has been configured with a second network address, the source network address field in the second message includes the second network address, wherein the second network address is different from the first network address.

18. The method according to any one of claims 10 to 16, characterized in that: If the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

19. An address conflict detection method, characterized in that: include: The first node receives a first message from the second node, the first message including a target network address and a network address of a third node; The third node is a neighbor of the second node, and the third node is a relay node for the first node and the second node; the first node stores a node network address mapping table; The first node determines whether there is an address conflict with the target network address according to the node network address mapping table; the node network address mapping table indicates a mapping relationship between identification information of multiple nodes and network addresses of the multiple nodes, wherein the multiple nodes include the second node and the third node; The first node sends a second message to the second node, where the second message is used to indicate that there is no address conflict with the target network address, and the second message is a unicast message; or The first node sends a third message to the second node through the third node, where the third message is used to indicate that an address conflict exists in the target network address.

20. The method according to claim 19, characterized in that The method further comprises: The second node is a terminal node.

21. The method according to claim 19 or 20, characterized in that The first node determines, according to the node network address mapping table, whether there is an address conflict with the target network address, including: The first node matches the target network address with the network address of the node in the node network address mapping table; If the match is successful, the first node determines that there is an address conflict in the target network address; If the match is unsuccessful, the first node determines that there is no address conflict with the target network address.

22. An address conflict detection method, characterized in that: include: The second node sends a first message to the first node, where the first message includes a target network address and a network address of a third node; The third node is a neighbor of the second node, and the third node is a relay node for the first node and the second node; the first node stores a node network address mapping table; the node network address mapping table is used to determine whether there is an address conflict with the target network address; the node network address mapping table indicates a mapping relationship between identification information of multiple nodes and network addresses of the multiple nodes, wherein the multiple nodes include the second node and the third node; The second node receives a second message from the first node, where the second message is used to indicate that there is no address conflict with the target network address, and the second message is a unicast message; or The second node receives a third message from the third node, where the third message is used to indicate that an address conflict exists in the target network address.

23. The method according to claim 22, characterized in that The method further comprises: The second node is a terminal node.

24. An address conflict detection device, characterized in that: include: Communication unit and processing unit, The communication unit is configured to send a first message, the first message including a target network address field, an address type field, and a target system identification field, the target network address field indicating a first network address, the address type field indicating a first address type corresponding to the first network address, the first address type being one of multiple address types; and the target system identification field indicating identification information of a node configured with the first network address; The communication unit is further configured to receive a second message from a second node, where the second message indicates whether there is an address conflict with the first network address.

25. The device according to claim 24, characterized in that The multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

26. The device according to claim 24 or 25, characterized in that When the first message is a request message, the target system identification field is a default value or a default value.

27. The device according to any one of claims 24 to 26, characterized in that The second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates the first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

28. The device according to claim 27, characterized in that When the second message is a response message, the target system identification field is identification information of the second node.

29. The device according to any one of claims 24 to 28, characterized in that The first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

30. The device according to claim 29, characterized in that At least one of the length of the destination network address field and the length of the source network address field is variable.

31. The device according to any one of claims 24 to 30, characterized in that If the first node has been configured with a second network address, the source network address field in the second message includes the second network address, wherein the second network address is different from the first network address.

32. The device according to any one of claims 24 to 30, characterized in that If the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

33. An address conflict detection device, characterized in that: include: Communication unit and processing unit, The communication unit is configured to receive a first message, the first message including a target network address field, an address type field, and a target system identification field, the target network address field indicating a first network address, the address type field indicating a first address type corresponding to the first network address, the first address type being one of multiple address types; and the target system identification field indicating identification information of a node configured with the first network address; The communication unit is further configured to send a second message to the first node, where the second message indicates whether there is an address conflict with the first network address.

34. The device according to claim 33, characterized in that The multiple address types include at least two of the following: a Star Flash network address, a custom address, an Internet Protocol version 4 (IPv4) address, or an Internet Protocol version 6 (IPv6) address.

35. The device according to claim 33 or 34, characterized in that When the first message is a request message, the target system identification field is a default value or a default value.

36. The device according to any one of claims 33 to 35, characterized in that The second message includes the target network address field, the address type field and the target system identification field, the target network address field indicates the first network address, the address type field indicates the first address type corresponding to the first network address, and the first address type belongs to one of the multiple address types; the target system identification field is used to indicate the identification information of the node configured with the first network address.

37. The device according to claim 36, characterized in that When the second message is a response message, the target system identification field is identification information of the second node.

38. The device according to any one of claims 33 to 37, characterized in that The first message or the second message further includes at least one of the following: a network address length field, a source network address field, a source system identification field, or a reserved field.

39. The device according to claim 38, characterized in that At least one of the length of the destination network address field and the length of the source network address field is variable.

40. The device according to any one of claims 33 to 39, characterized in that If the first node has been configured with a second network address, the source network address field in the second message includes the second network address, wherein the second network address is different from the first network address.

41. The device according to any one of claims 33 to 39, characterized in that If the first node is not configured with any network address other than the first network address, the source network address field in the second message is a default value or a default value.

42. An address conflict detection device, characterized in that: include: Communication unit and processing unit, The communication unit is configured to receive a first message from a second node, the first message including a target network address and a network address of a third node; the third node is a neighbor of the second node, and the third node is the device and a relay node of the second node; the device stores a node network address mapping table; the node network address mapping table is used for address conflict detection; The processing unit is configured to determine whether there is an address conflict for the target network address according to the node network address mapping table, wherein the node network address mapping table indicates a mapping relationship between identification information of a plurality of nodes and the network addresses of the plurality of nodes, wherein the plurality of nodes include the second node and the third node; The communication unit is further configured to send a second message to the second node, where the second message is configured to indicate that there is no address conflict with the target network address; the second message is a unicast message; or, The communication unit is further configured to send a third message to the second node through the third node, where the third message is configured to indicate that an address conflict exists in the target network address.

43. The device according to claim 42, characterized in that The second node is a terminal node.

44. The device according to claim 42 or 43, characterized in that The processing unit is configured to match the target network address with the network address of the node in the node network address mapping table; The processing unit is further configured to determine, if the match is successful, whether an address conflict exists in the target network address; The processing unit is further configured to determine, when no matching is successful, that no address conflict exists in the target network address.

45. An address conflict detection device, characterized in that: include: Communication unit and processing unit, The communication unit is configured to send a first message to the first node, wherein the first message includes a target network address and a network address of a third node; The third node is a neighbor of the device, and the third node is a relay node between the first node and the device; the first node stores a node network address mapping table; the node network address mapping table is used to determine whether there is an address conflict with the target network address; the node network address mapping table indicates a mapping relationship between identification information of multiple nodes and network addresses of the multiple nodes, wherein the multiple nodes include the device and the third node; The communication unit is further configured to receive a second message from the first node, where the second message is configured to indicate that there is no address conflict for the target network address, and the second message is a unicast message; or, The communication unit is further configured to receive a third message from the third node, where the third message is configured to indicate that an address conflict exists in the target network address.

46. ​​The device according to claim 45, characterized in that The device is a terminal node.

47. An address conflict detection device, characterized in that: The address conflict detection device includes at least one processor and a communication interface, The communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output for the processor; The at least one processor is configured to implement the method according to any one of claims 1 to 9.

48. An address conflict detection device, characterized in that: The address conflict detection device includes at least one processor and a communication interface, The communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output for the processor; The at least one processor is configured to implement the method according to any one of claims 10 to 18.

49. An address conflict detection device, characterized in that: The address conflict detection device includes at least one processor and a communication interface, The communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output for the processor; The at least one processor is configured to implement the method according to any one of claims 19 to 21.

50. An address conflict detection device, characterized in that: The address conflict detection device includes at least one processor and a communication interface, The communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output for the processor; The at least one processor is configured to implement the method according to any one of claims 21 to 24.

51. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, which, when executed on a processor, enable the method according to any one of claims 1 to 24 to be implemented.

Images