A heterogeneous data link interconnection and intercommunication method based on unified identification and multi-layer address mapping

Abstract

The application discloses a heterogeneous data chain interconnection and intercommunication method based on unified identification and multi-layer address mapping, which comprises the following steps: giving each network device a unified IP communication address based on a network layer, and each network device address HA only needs to establish a mapping with the IP to realize heterogeneous identification at the address layer; adding an ARP module in the network layer in a homogeneous data chain, directly establishing an ARP cache table by using a broadcast form existing in a wireless network and network perception information propagated in a single hop in the network; identifying different network areas by using an Area IP, and separating the network into multiple subnets; taking cross-area Area IP self-switching as a benchmark, realizing self-entry into a new subnet and establishing a connection with nodes in the new subnet, and keeping a communication connection during a node area changing process based on a home agent. The application can stably and reliably realize the interconnection and intercommunication of heterogeneous data chains.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method for interconnecting heterogeneous data links based on unified identification and multi-layer address mapping. Background Technology

[0002] With the improvement of network informatization, devices are gradually shifting from acquiring single information to integrating multiple information, and various sensor-equipped devices and their data links are flourishing. Although existing data link devices can still play a significant role in their respective networks, the complexity of information is different from the past. In the past, the independent operation of a single data link had limited information acquisition, but currently, no single data link can independently meet such diverse communication needs.

[0003] In the context of informatization, the performance of a single data link or device is no longer the decisive factor in network operation; the speed and quality of acquiring, integrating, and processing diverse information are becoming increasingly important. However, due to the siloed development of data links, there is a lack of direct interconnection between them, making it even more difficult to achieve information exchange and integration.

[0004] Thus, multi-data-link interconnection technology was born. This technology is designed to solve the problem of communication barriers between data links caused by differences in communication mechanisms and distance limitations. Through multi-data-link interconnection technology, all platforms can be united to form a unified whole with information advantages, greatly expanding the information capabilities of individual data links and achieving a "1+1>2" effect.

[0005] In the traditional model, the independent work of each data chain cannot meet the ever-increasing information needs of today's platform networks. The chains should evolve towards comprehensive, integrated operation, but the heterogeneity of the data chains hinders the network convergence process. This application primarily addresses the following issues:

[0006] (1) Breaking down barriers to interoperability of heterogeneous communication addresses. During their development and evolution, various data chains have not fully considered the need for cross-chain interoperability. The identity identifiers in different data chains vary in form, length, and even sometimes are identical. This makes it difficult for data chain devices to understand or distinguish the attributes of heterogeneous link nodes, even if they overcome differences in waveform systems and data formats. These differences in identity identifiers directly affect the process of interoperability between heterogeneous data chains.

[0007] (2) Solving the cross-chain addressing problem of heterogeneous data chains. Nodes performing heterogeneous cross-chain operations in the network carry devices with multiple data chains and receive multiple routing information. Isolated path selection will not only make it difficult for general nodes to obtain routing information, but also affect the node performing heterogeneous cross-chain operations to recognize the link affiliation and identity of the next hop target. Considering the mobility of nodes, it is not possible to delegate all business to certain nodes through static routing.

[0008] (3) Overcoming the difficulty of data link network node switching areas. Traditional flat networks cannot support the communication needs of nodes in large-scale scenarios, while clustered networks restrict the mobility of nodes to within the subnet, and relying solely on the gateway nodes in the clustered network cannot achieve full coverage of the signal in the node's moving area. In this case, nodes lack the means to clearly identify their own subnet, and also lack the method to join a new subnet and maintain communication with the network when moving across subnets. Summary of the Invention

[0009] Taking into full consideration the forward expansion to support newly developed equipment and large-scale node networking, this application proposes a heterogeneous data link interconnection method based on unified identification and multi-layer address mapping, which performs layered processing on data link devices, adding a network layer to all data link devices.

[0010] This application discloses a method for interconnecting heterogeneous data links based on unified identifiers and multi-layer address mapping, which includes:

[0011] Step 1: Based on the network layer, assign a unified IP communication address to each network device. Each network device address HA only needs to establish a mapping with the IP address to achieve heterogeneous identification at the address level.

[0012] Step 2: In a homogeneous data link, add an ARP module to the network layer. Utilize the broadcast format in the wireless network and the network awareness information propagated by a single hop in the network to directly establish an ARP cache table. That is, use packets that are transmitted with only one hop in the network to ensure that the source IP and source Area IP in the network layer header match the source HA in the MAC layer header. Alternatively, in a heterogeneous data link, the gateway node uses the interface connection relationship between the MAC layer and the network layer to establish ARP mapping.

[0013] Step 3: Identify different network areas using Area IP to divide the network into multiple subnets;

[0014] Step 4: Based on the cross-area IP self-switching, the node autonomously enters the new subnet and establishes a connection with the nodes in the new subnet, and maintains the communication connection during the node's area switching process based on the home agent.

[0015] Optionally, step 1 includes:

[0016] The network layer provides existing network devices with a new IP address, which serves as a unified identity for nodes within the network and is responsible for addressing operations within the network; the same network device can communicate using different IP addresses; the new IP address consists of M bits;

[0017] The original high availability (HA) of the network equipment is retained, and dynamic mapping with IP is completed through the ARP module;

[0018] The M-bit address pool is pre-planned, with all-1 addresses used as broadcast addresses, and the first N addresses are reserved for gateway nodes. At the same time, N addresses are used as Area IPs for the gateway nodes' jurisdiction, so that subnet nodes can identify their own subnet area affiliation.

[0019] Furthermore, in the homogeneous data link, an ARP module is added at the network layer. Utilizing the broadcast format present in the wireless network and the network-aware information propagated via single hops, an ARP cache table is directly established. This means that the source IP and source Area IP in the network layer header are matched with the source HA in the MAC layer header using packets transmitted via only one hop. This includes:

[0020] In proactive routing scenarios, nodes The data packet transmits its own network awareness information through messages. The data packet is encapsulated with a network layer header at the network layer. The network layer header includes the data packet type, source node IP, and destination node IP. The destination node IP is the Area IP. The destination HA in the MAC layer header is the broadcast address of the MAC layer. The message includes a MAC layer header, a network layer header, and network awareness information.

[0021] node The network sensing information emitted is directly received by the nodes Receive, or, node The network sensing information sent out is forwarded to the nodes through relay nodes. ,node After determining the type of the received data packet, it is used as a resource for establishing the ARP cache table. The source HA information in the MAC layer header and the IP information in the network layer header are extracted to establish the ARP cache table; Node and nodes For any node in the same subnet of the same data link, or, a node and nodes It refers to any node in different subnets of the same data chain.

[0022] Furthermore, in the heterogeneous data chain, the gateway node establishes an ARP mapping using the interface connection between the MAC layer and the network layer, including:

[0023] node and nodes Network awareness information is sent via messages using chains A and B respectively, with the destination HA in the MAC layer header being the broadcast address of its own link; Node The network interface in the ARP cache table is the number of the interface connecting the MAC layer and the network layer, used to distinguish data link types and ensure that the correct next-hop link is selected when forwarding data; the packet includes a MAC layer header, a network layer header, and network awareness information; the network layer header includes the packet type, source node IP, and source area IP; the MAC layer header includes the destination HA; node The ARP cache table includes the IP addresses of neighboring nodes, HA (High Availability), Area IP addresses, and network interfaces; Node and nodes They are located in the same subnet.

[0024] Further, step 3 includes:

[0025] Step 31: Upon receiving a network awareness message, a node determines whether it is a gateway node. If so, it directly receives the network awareness message; otherwise, it determines the subnet to which the source node belongs. If the source node is not a node in this subnet, the message is discarded. If the source node is a node in this subnet, its identity is determined. If the source node is the gateway node of this subnet, it only receives the path information related to the gateway node from the network awareness message and then discards the message. If the source node is not a gateway node, it receives the network awareness message.

[0026] Step 32: The gateway node integrates its multiple routing information and sends it in the form of MAC broadcast. The destination IP in the network layer header is set to the Area IP, that is, the Area IP of the gateway node is consistent with the IP. The data packet is identified as network-aware information to indicate that the data packet is the network-aware information of the area node corresponding to the Area IP.

[0027] Step 33: After receiving a data packet at the network layer, the node checks the type and destination address. If it finds that the data packet does not match its own area code, it discards the data packet. When a node discovers that the data packet matches its own area code, it selects to receive the data packet at the network layer and only obtains the path information about the gateway node from the network-aware message. Nodes and A node can be any node in the network;

[0028] Step 34: Following the same logic as step 33, traverse all nodes in the network to complete the clustering and segmentation of the nodes in the network, resulting in multiple subnets; different subnets in the multiple subnets communicate with each other through gateway nodes.

[0029] Furthermore, in the multiple subnets, the packet forwarding process includes:

[0030] Step 301: Starting from the received data packet, check the next-hop HA encapsulated in the MAC header of the data packet to determine whether the data packet should be processed by this node. If the next-hop HA does not match the HA of this node, discard the data packet.

[0031] Step 302: If the next-hop HA is the local node's HA, remove the MAC layer header of the data packet, upload the data packet to the network layer, check the destination IP in the network layer header, and determine whether forwarding is necessary; if the destination IP is the same as the local node's IP, then the local node is the destination node, remove the network layer header, upload the data packet to the application layer, and no longer forward the data packet.

[0032] Step 303: If the destination IP is different from the local node's IP, proceed with forwarding: query the routing table, and based on the destination IP information, forward the new next-hop IP to the ARP module, then proceed to step 304; if there is no route to the destination IP within the local node, determine the node's identity; if the node is a gateway node, discard the packet, and forwarding fails; if the node is a subnet node, forward the data packet to the gateway node, which then determines whether the destination node is reachable;

[0033] Step 304: The ARP module receives the next-hop IP information, queries the ARP cache table, and if there is no relevant IP-HA mapping information, the packet is discarded and forwarding fails.

[0034] Step 305: If the ARP cache table contains relevant IP-HA information, the next-hop HA address is refilled and sent to the matching MAC layer based on the next-hop network affiliation. The MAC layer re-encapsulates the MAC header, sends the data packet, and completes the forwarding.

[0035] Furthermore, the node, based on cross-area IP self-switching, autonomously enters a new subnet and establishes connections with nodes in that new subnet, including:

[0036] The node discovers that the gateway node in the current area is unreachable through routing information; records the current Area IP and sets it to 0; queries the node's ARP cache table; and counts the nodes in each area except the recorded area.

[0037] If there are no nodes in other areas, the Area IP remains unchanged, and the ARP cache table is periodically queried. If a path to the current area gateway is obtained again, the area switching operation ends. If there are nodes in other areas, the area with the most nodes is selected as the alternative area for switching. When the number of neighboring nodes in the alternative area exceeds the preset value, it indicates that the new area is congested. The area switching is reconsidered, and the area with the second most nodes is selected as the alternative area for switching.

[0038] If the new area meets the area switching requirements, the node switches its own Area IP to complete the area switching, deletes the original routing information, and gradually establishes new network relationships. The area switching requirements are related to the network connection reliability and network congestion level of the new area.

[0039] Furthermore, the method of maintaining the communication connection during the node switching process based on the home agent includes:

[0040] Step 41: Establish a forward temporary path for the node and complete the transmission of the proxy request message; the proxy request message includes the node's current area IP, serial number, and proxy duration; the serial number is used to identify the new and old proxy requests; the proxy duration is determined by the Xinxiang gateway node;

[0041] Step 42: Different identity nodes process the received proxy request messages.

[0042] Further, step 41 includes:

[0043] The node completes the autonomous area switch; it checks if the new gateway node information exists in the ARP cache table; if it exists, it directly establishes a temporary path to the gateway node; if it does not exist, it randomly selects a node from the nodes in the new area as the next hop to the new gateway node, thus establishing a temporary path to the gateway node; it fills the destination address field in the network layer header with the home address and sets the protocol field to proxy request, and fills the data field with the home address and proxy sequence number of the proxy request message. Then, it uses unicast at the network layer to send the proxy request message to the home gateway; if the ARP module finds that the protocol field is a proxy request message, it sets the next hop MAC address to the MAC layer broadcast address and sends it to the MAC layer for processing; the MAC layer sends the proxy request message in the form of a one-hop broadcast.

[0044] Further, step 42 includes:

[0045] The Xinxiang node establishes a temporary reverse path to the source node. With the help of packet forwarding, it establishes temporary path information of destination address and next-hop address at the network layer, establishes a "misaligned" mapping relationship between source IP and previous hop HA, and completes the reverse transmission of messages. The Xinxiang gateway node deletes the expired path information related to the source node and fills the Duration Time field in the proxy request packet with its own routing table. The node in the new area is the Xinxiang node.

[0046] The home node deletes the path information related to the source node. The home gateway node starts the proxy mode according to the proxy request message information. For subsequent messages whose destination address is the source node, it encapsulates another layer of header with the destination node being the Xinxiang gateway and sets the Protocol field to tunnel message.

[0047] Other non-gateway nodes directly discard proxy request messages, while other gateway nodes deploy proxies based on how the Xinxiang node and the hometown node handle proxy request messages.

[0048] Due to the adoption of the above technical solution, this application has the following advantages:

[0049] 1. Achieve unified network identity for heterogeneous data link devices, solve the problem of communication address identification and differentiation between heterogeneous data links, separate addressing and transmission, and complete the confirmation of data link ownership and selection of heterogeneous links for the next-hop node. Construct a clustered network to limit the flooding of network-aware information and provide support for large-scale network environments. Simultaneously, propose a mobility management scheme for node movement across subnets in the clustered network, enabling autonomous area switching operations and communication maintenance for nodes moving across subnets, ultimately achieving the goal of interconnection and interoperability of heterogeneous data links.

[0050] 2. Flexibility and simplicity. IP addresses are not strongly bound to data link devices and can be flexibly configured according to scenario requirements. At the same time, this solution liberates address identification from complex mapping relationships. Each device can autonomously and dynamically establish its own HA address and IP address mapping relationship, simplifying the planning process and paving the way for the addition of new networks in the future.

[0051] 3. Supports large-scale scenarios. By clustering the network, the flooding of network-sensing information is limited, effectively reducing channel congestion and supporting information transmission in large-scale scenarios. For small-scale scenarios, the network can also be built into a flat structure.

[0052] 4. High robustness. Although communication between heterogeneous nodes still relies on gateway nodes, each gateway node does not store unique information. Therefore, when a gateway node fails or is damaged, subnet nodes can react quickly and autonomously merge into other subnets to restore network communication. Attached Figure Description

[0053] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0054] Figure 1This is a schematic diagram of the hierarchical structure of a typical device node;

[0055] Figure 2 This is a schematic diagram of the hierarchical structure of a multi-chain gateway node;

[0056] Figure 3 Designed for IP-based network addresses;

[0057] Figure 4 For multi-chain gateway address allocation;

[0058] Figure 5 For node identity recognition;

[0059] Figure 6 This illustrates a network scenario where a node has not obtained the ARP cache table.

[0060] Figure 7 This is for a proactive routing scenario within a homogeneous subnet.

[0061] Figure 8 Establish ARP mappings for active routes within the same subnet of homogeneous data links;

[0062] Figure 9 Establish ARP mappings for different subnets of homogeneous data links;

[0063] Figure 10 To establish an ARP mapping for Layer 2 data forwarding based on relay nodes;

[0064] Figure 11 For proactive routing scenarios in heterogeneous data chains;

[0065] Figure 12 Establish ARP mappings for proactive routing in heterogeneous subnets;

[0066] Figure 13 To process network-aware messages;

[0067] Figure 14 Send network awareness information to the gateway node;

[0068] Figure 15 Process network-aware information for subnet nodes;

[0069] Figure 16 This describes the packet forwarding process under a clustered architecture.

[0070] Figure 17 Enables nodes to autonomously switch zones (subnet nodes discover gateway node paths);

[0071] Figure 18 Sending a proxy request message;

[0072] Figure 19 For proxy request messages;

[0073] Figure 20 For receiving proxy request messages;

[0074] Figure 21 This is triangular communication. Detailed Implementation

[0075] The present application will be further described in conjunction with the accompanying drawings and embodiments. The described embodiments are only some, not all, of the embodiments of the present application. All other embodiments obtained by those skilled in the art should fall within the protection scope of the embodiments of the present application.

[0076] This application proposes a heterogeneous data link interconnection method based on unified mapping and multi-layer address mapping. In a data link network environment, relying on a newly added network layer, a new network identity is established through address design, unifying the address format across the entire network and enabling homogenization of heterogeneous devices at the network layer. Simultaneously, the traditional Address Resolution Protocol (ARP) module is modified using wireless communication characteristics to dynamically establish a mapping relationship between network identity (IP) and device identity (HA), separating addressing and transmission functions. This module also facilitates the fusion of heterogeneous data link information at the network layer, enabling the differentiation of data link types through next-hop selection and access network interface number, achieving the effect of heterogeneous data link interconnection. Finally, by introducing regional IP, subnetting and mobility management are implemented, transforming the network from a flat structure suitable for small to medium scales to a clustered structure capable of supporting large-scale scenarios, while also supporting node movement across subnets.

[0077] This application provides an embodiment of a heterogeneous data link interconnection method based on unified mapping and multi-layer address mapping, which includes:

[0078] Step 1: Based on the network layer, assign a unified IP communication address to each network device. Each network device address HA only needs to establish a mapping with the IP address to achieve heterogeneous identification at the address level.

[0079] Step 2: In a homogeneous data link, add an ARP module to the network layer. Utilize the broadcast format in the wireless network and the network awareness information propagated by a single hop in the network to directly establish an ARP cache table. That is, use packets that are transmitted with only one hop in the network to ensure that the source IP and source Area IP in the network layer header match the source HA in the MAC layer header. Alternatively, in a heterogeneous data link, the gateway node uses the interface connection relationship between the MAC layer and the network layer to establish ARP mapping.

[0080] Step 3: Identify different network areas using Area IP to divide the network into multiple subnets;

[0081] Step 4: Based on the cross-area IP self-switching, the node autonomously enters the new subnet and establishes a connection with the nodes in the new subnet, and maintains the communication connection during the node's area switching process based on the home agent.

[0082] This application, based on the network layer, designs a unified end-to-end logical address (i.e., IP address) for the entire network, making the heterogeneous characteristics of each device transparent at the network layer. This solves the problem of heterogeneous devices being difficult to identify each other at the address level, enabling network layer transmission for heterogeneous devices. It also introduces the concept of Area IP, laying the foundation for subsequent network clustering. Building upon the ability of network devices to communicate at the network layer, an ARP module is added, eliminating traditional ARP query and response messages. Instead, network-aware information transmitted over one hop in the network is used to establish a dynamic mapping relationship between the newly added communication address (IP) and the device's inherent address (HA), breaking down the communication barrier between the network layer and the MAC layer, solving the problem of hop-by-hop data transmission, and truly achieving cross-chain data transmission. Taking a large-scale device scenario using active routing as a background, subnetting is implemented based on address design, effectively suppressing the propagation of flooded traffic in the network. Based on address mapping, data stored in the ARP module enables autonomous entry / exit of mobile nodes across subnets.

[0083] Figure 1 and Figure 2 In this layer, the network layer is added for ordinary nodes and multi-chain gateway nodes. It also adds the Address Resolution Protocol (ARP) function to realize the mapping between IP addresses and HA addresses, and is responsible for completing single-hop transmission in the network.

[0084] In existing technical solutions, the communication addresses of heterogeneous data chains do not fully consider the needs of cross-chain interconnection during design and evolution. Communication addresses are only readable and unique within the device's own network, leading to difficulties in reading and distinguishing addresses between heterogeneous devices. This application, relying on the network layer, assigns devices a unified IP communication address to solve the problem of identity recognition between heterogeneous devices. This application liberates address recognition from complex mapping relationships; each network device's HA only needs to establish a mapping with an IP address to achieve heterogeneous identification at the address level, simplifying the mapping relationship and paving the way for the addition of new chains. The network layer provides new IP addresses to existing network devices and uses them as a unified identity identifier for nodes in the network, responsible for addressing operations within the network; the same network device can use different IPs for communication; the new IP address consists of M bits.

[0085] The original high availability (HA) of the network equipment is retained, and dynamic mapping with IP is completed through the ARP module;

[0086] The M-bit address pool is pre-planned, with all-1 addresses used as broadcast addresses, and the first N addresses are reserved for gateway nodes. At the same time, N addresses are used as Area IPs for the gateway nodes' jurisdiction, so that subnet nodes can identify their own subnet area affiliation.

[0087] For example, see Figure 3 and Figure 4 The new IP address consists of 32 bits, such as 00001010 00000000000000000 00000001, denoted as 10.0.0.1. Unlike the strong binding between HA and devices, the IP can be flexibly allocated. In different task scenarios, the same device can use different IPs for communication. The original HA of the device is retained, and dynamic mapping with IP is completed through the ARP module, allowing it to be responsible for single-hop transmission in the network. The 32-bit address pool is pre-planned, with all-1 addresses as broadcast addresses, i.e., 255.255.255.255. The first 16,777,215 addresses (0.0.0.1 – 0.255.255.255) are reserved for gateway nodes. At the same time, these addresses are used as AreaIPs within the jurisdiction of the gateway nodes so that subnet nodes can identify their own subnet area affiliation. In particular, 0.0.0.0 is used as the Area IP address identifier for areas not included in the subnet.

[0088] See Figure 5 The identity of a node in the network is mainly composed of three parts: (1) IP, the network identity identifier of the node, used to answer the question "Who am I"; (2) Area IP, on the one hand, as the identifier of the subnet to which the node belongs, used in the cluster structure to answer the question "Where am I"; on the other hand, as the gateway identifier of the subnet to which the node belongs, used in the cluster structure to answer the question "How do I communicate with other subnets".

[0089] IP addresses solve the connectivity problem of heterogeneous data links at the network layer in their address design. However, in actual communication, information transmission is hop-by-hop, which requires the use of device HA information. Therefore, it is necessary to establish a resolution mapping relationship between IP and HA. This application uses an ARP module to dynamically establish the IP-HA mapping relationship. Unlike the ARP query mechanism in wired networks, this application utilizes the inherent broadcast form in wireless networks to fully leverage the network-aware information propagated in single-hop transmission, thereby directly establishing an ARP cache table and reducing unnecessary latency and network overhead. At the gateway node, the interface connection between the MAC layer and the network layer is used to confirm the network affiliation of neighboring nodes. The basic idea is to use the single-hop transmission of packets in the network to match the source IP in the network layer header with the source HA in the MAC layer header.

[0090] Optionally, in the homogeneous data link, an ARP module is added at the network layer. Utilizing the broadcast format present in the wireless network and the network-aware information propagated by a single hop, an ARP cache table is directly established. This means that the source IP and source Area IP in the network layer header are matched with the source HA in the MAC layer header using packets transmitted over only one hop. This includes:

[0091] In proactive routing scenarios, nodes The data packet transmits its own network awareness information through messages. The data packet is encapsulated with a network layer header at the network layer. The network layer header includes the data packet type, source node IP, and destination node IP. The destination node IP is the Area IP. The destination HA in the MAC layer header is the broadcast address of the MAC layer. The message includes a MAC layer header, a network layer header, and network awareness information.

[0092] node The network sensing information emitted is directly received by the nodes Receive, or, node The network sensing information sent out is forwarded to the nodes through relay nodes. ,node After determining the type of the received data packet, it is used as a resource for establishing the ARP cache table. The source HA information in the MAC layer header and the IP information in the network layer header are extracted to establish the ARP cache table; Node and nodes For any node in the same subnet of the same data link, or, a node and nodes It refers to any node in different subnets of the same data chain.

[0093] For example, see Figure 6 Taking a homogeneous subnet as an example, at the beginning of network establishment, nodes have not yet begun to interact. No information is available to establish an ARP cache table. In proactive routing scenarios, nodes need to periodically exchange network-aware messages, such as Hello packets. In this case, the broadcast characteristic of wireless transmission can be utilized to establish an ARP cache table using a packet transmitted over one hop.

[0094] like Figure 7 Middle node The system begins transmitting its own network awareness information. The data packet is encapsulated with a network layer header at the network layer. This header primarily contains information such as the data packet type, source node IP, and destination node IP. At this stage, the network awareness information does not need to be received by a specific node; rather, it is intended that all one-hop nodes within the same subnet can obtain this information. Therefore, the destination node IP is the Area IP. Similarly, the destination HA in the MAC layer header is the MAC layer broadcast address.

[0095] See Figure 8 ,node The network sensing information emitted is received by the nodes C receives, node After determining the packet type, it is used as a resource for establishing an ARP cache table. The source HA information in the MAC layer header and the IP information in the network layer header are extracted to establish the ARP cache table. Similarly.

[0096] In passive routing scenarios, nodes remain silent when there is no communication need, and the ARP cache table remains empty during this period. However, when data transmission is required and routing begins, they will still start "wireless broadcasting" just like in active routing. Therefore, it can be assumed that the process of establishing the ARP cache table is the same as that of active routing.

[0097] See Figure 9 Network-aware information between nodes in different subnets using the same data link is selectively processed by subsequent modules in the network layer. The ARP module is not sensitive to the destination IP information in the packet header, nor is it responsible for receiving the valid data portion of the packet. That is, the ARP module will perform a receive operation by default for any packet uploaded from the MAC layer. Therefore, subnet nodes can establish ARP mapping relationships with all nodes in their surrounding data link within a one-hop radius, as described in the aforementioned isomorphic subnet process.

[0098] This ARP mapping relationship between different subnets is mostly ineffective because nodes in different subnets are limited by the isolation of network-aware information and cannot establish a direct route. However, obtaining this information paves the way for subsequent node movement across subnets.

[0099] See Figure 10 For certain chains that rely on relay nodes to achieve forwarding functions, as long as the relay nodes interact with other nodes to exchange network-aware information, each node can still establish an ARP cache table according to the aforementioned process in the homogeneous subnet.

[0100] Optionally, in the heterogeneous data chain, the gateway node establishes an ARP mapping using the interface connection between the MAC layer and the network layer, including:

[0101] node and nodes Network awareness information is sent via messages using chains A and B respectively, with the destination HA in the MAC layer header being the broadcast address of its own link; Node The network interface in the ARP cache table is the number of the interface connecting the MAC layer and the network layer, used to distinguish data link types and ensure that the correct next-hop link is selected when forwarding data; the packet includes a MAC layer header, a network layer header, and network awareness information; the network layer header includes the packet type, source node IP, and source area IP; the MAC layer header includes the destination HA; node The ARP cache table includes the IP addresses of neighboring nodes, HA (High Availability), Area IP addresses, and network interfaces; Node and nodes They are located in the same subnet.

[0102] For example, in a heterogeneous data link, the gateway node needs to monitor the network interface used for data transmission and reception to ensure proper data link matching. Nodes are naturally isolated due to the heterogeneity of the links and do not directly access each other's information. Since ARP essentially obtains the IP-HA mapping relationship of a one-hop node, there is no need to establish such a mapping between heterogeneous nodes.

[0103] like Figure 11 As shown, node and nodes Network awareness information is sent via chains A and B respectively. The header entries are mostly consistent across similar scenarios, except that the destination HA in the MAC header is filled with the broadcast address of its own link. The network interface X in node G1's ARP cache table refers to the number of the interface connecting the MAC layer and the network layer, used to distinguish data chain types (e.g., interface number 1 for chain A, interface number 2 for chain B), ensuring that the correct next-hop link is selected during data forwarding.

[0104] like Figure 12 As shown, gateway node G1 receives data from node A. and B-chain nodes Network sensing information, combined with network slogans, will be used to identify nodes. and nodes The IP-HA mapping relationship is recorded in the table. And the nodes... and nodes Network-aware information is not shared and cannot be received.

[0105] When the number of nodes in a network is too large, a flat network structure will be unable to support the communication needs. In this case, the network needs to be segmented and clustered to isolate flooded information in the form of subnets. However, this isolation can cause subnet nodes to have a limited understanding of the overall network information, leading to connection loss when nodes leave the subnet's coverage area. This application uses Area IP in address design as the basis for segmenting the network to limit the propagation of flooded messages; simultaneously, it uses mobility management combined with address mapping to address the potential connection loss problem when nodes move.

[0106] In a large-scale node environment, subnet nodes incur significant network control overhead in order to acquire global information. Therefore, to prevent network channel resources in proactive routing from being occupied by network-aware information such as neighbor messages and routing information, appropriate network segmentation is necessary.

[0107] For passive routing, subnetting is meaningless for the following reasons:

[0108] (1) When there is no transmission demand, the nodes in the network are silent but not stationary, but the nodes do not have enough information to determine the subnet environment in which they are located;

[0109] (2) When data transmission is required, the means of obtaining the transmission path between source and destination nodes relies on network-wide flooding, and all nodes in the network should receive the transmission request and respond (forward or reply). This contradicts the idea of ​​subnetting to isolate network-aware information.

[0110] For proactive routing, different network areas are identified by Area IP. Nodes with different Area IPs belong to different subnets. Nodes use this attribute to identify their own subnet and reduce the propagation of network-aware messages in subnet areas by blocking routing information from nodes outside their own subnet, thereby saving network bandwidth resources.

[0111] Optionally, see Figures 13 to 15 Step 3 includes:

[0112] Step 31: Upon receiving a network awareness message, a node determines whether it is a gateway node. If so, it directly receives the network awareness message; otherwise, it determines the subnet to which the source node belongs. If the source node is not a node in this subnet, the message is discarded. If the source node is a node in this subnet, its identity is determined. If the source node is the gateway node of this subnet, it only receives the path information related to the gateway node from the network awareness message and then discards the message. If the source node is not a gateway node, it receives the network awareness message.

[0113] Step 32: The gateway node integrates its multiple (e.g., 10) routing information and sends them in the form of MAC broadcast. The destination IP in the network layer header is set to the Area IP, that is, the Area IP of the gateway node is consistent with the IP. The data packet is identified as network-aware information to indicate that the data packet is the network-aware information of the area node corresponding to the Area IP (e.g., 0.0.0.1).

[0114] Step 33: After receiving a data packet at the network layer, the node checks the type and destination address. If it finds that the data packet does not match its own area code, it discards the data packet. The node finds that the data packet matches its own area code and selects to receive the data packet at the network layer. However, since the source node is the gateway node, it only obtains the path information about the gateway node from the network-aware message. Nodes and A node can be any node in the network;

[0115] Step 34: Following the same logic as Step 33, traverse all nodes in the network to complete the clustering and segmentation of the nodes, resulting in multiple subnets. Communication between different subnets is achieved through gateway nodes. The network has completed the clustering and segmentation of nodes, with each subnet separated into "islands" by Area IP, and the gateway node acting as a "bridge" connecting these islands. In this clustered structure, only the "bridge" possesses global information, and only by relying on the gateway node can a determination be made regarding the reachability of the destination address.

[0116] Optionally, see Figure 16 In the multiple subnets, the packet forwarding process includes:

[0117] Step 301: Starting from the received data packet, check the next-hop HA encapsulated in the MAC header of the data packet to determine whether the data packet should be processed by this node. If the next-hop HA does not match the HA of this node, discard the data packet.

[0118] Step 302: If the next-hop HA is the local node's HA, remove the MAC layer header of the data packet, upload the data packet to the network layer, check the destination IP in the network layer header, and determine whether forwarding is necessary; if the destination IP is the same as the local node's IP, then the local node is the destination node, remove the network layer header, upload the data packet to the application layer, and no longer forward the data packet.

[0119] Step 303: If the destination IP is different from the local node's IP, proceed with forwarding: query the routing table, and based on the destination IP information, forward the new next-hop IP to the ARP module, then proceed to step 304; if there is no route to the destination IP within the local node, determine the node's identity; if the node is a gateway node, discard the packet, and forwarding fails; if the node is a subnet node, forward the data packet to the gateway node, which then determines whether the destination node is reachable;

[0120] Step 304: The ARP module receives the next-hop IP information, queries the ARP cache table, and if there is no relevant IP-HA mapping information, the packet is discarded and forwarding fails.

[0121] Step 305: If the ARP cache table contains relevant IP-HA information, the next-hop HA address is refilled and sent to the matching MAC layer based on the next-hop network affiliation. The MAC layer re-encapsulates the MAC header, sends the data packet, and completes the forwarding.

[0122] Based on the degree of node movement, nodes can be broadly categorized into three types: stationary nodes, intra-subnet mobile nodes, and cross-subnet mobile nodes. Stationary nodes and intra-subnet mobile nodes can achieve mobility support using the network's own protocols. However, cross-subnet mobile nodes require new mobility management methods to establish and restore the network after crossing subnets. This application uses cross-area IP self-handover as a basis to achieve autonomous entry / exit of cross-subnet mobile nodes into / out of subnets and the re-establishment of network relationships, and uses a home agent as support to improve communication maintenance during the node area change process.

[0123] With network segmentation, communication between subnet nodes and other subnets is tied to the gateway node, restricting the mobility of subnet nodes. When a subnet node moves beyond a certain range, it may lose a valid path to the gateway node, resulting in the node becoming disconnected throughout the network.

[0124] Therefore, a method is needed to ensure nodes rejoin the network. This application utilizes the stored information of the ARP module to enhance the node's Area IP awareness, quickly determine path connectivity, and autonomously switch areas to support node mobility. The choice to allow subnet nodes to autonomously determine their location and switch based on their Area IP, rather than switching IP addresses, is primarily based on the following considerations:

[0125] (1) In a data link environment, the gateway node signal cannot cover all areas, and there are multiple hops between the subnet node and the gateway node. That is, the subnet node cannot determine its own area by a certain message periodically broadcast by the gateway node.

[0126] (2) In a data link environment, nodes are not permanently reliable and each node faces the threat of failure or destruction. If a node changes its network identity by subnetting its IP address, it is equivalent to entrusting the mapping relationship between the old and new IP addresses to the original gateway node. If the original gateway node is offline at this time, no other node in the network will be able to complete the communication related to the old IP address.

[0127] Optionally, see Figure 17 The node, based on cross-area IP self-switching, autonomously enters a new subnet and establishes connections with nodes in that new subnet, including:

[0128] The node discovers that the gateway node in the current area is unreachable through routing information; records the current Area IP and sets it to 0; queries the node's ARP cache table; and counts the nodes in each area except the recorded area.

[0129] If there are no nodes in other areas, the Area IP remains unchanged, and the ARP cache table is periodically queried. If a path to the current area gateway is obtained again, the area switching operation ends. If there are nodes in other areas, the area with the most nodes is selected as the alternative area for switching. When the number of neighboring nodes in the alternative area exceeds the preset value, it indicates that the new area is congested. The area switching is reconsidered, and the area with the second most nodes is selected as the alternative area for switching.

[0130] If the new area meets the area switching requirements, the node switches its Area IP, completes the area switching, deletes the original routing information, and gradually establishes new network relationships. The area switching requirements are related to the network connection reliability and network congestion level of the new area. The node in the new area will be referred to as the Xinxiang node.

[0131] After the subnet node completes its autonomous handover, it can obtain the connection relationship with the Xinxiang node, establish a connection with the Xinxiang gateway node, and re-enter the network. However, communication interruptions may occur during the re-entry process.

[0132] Inter-region handover allows nodes to reconnect to the network. However, inter-region handover alone cannot provide sufficient support for maintaining communication. Ongoing communication will be interrupted due to the path change caused by the handover, and the speed of communication recovery depends on the distance / hop count between the communicating nodes and the frequency of network-aware message packets.

[0133] Therefore, a new protocol is needed to compensate for the communication interruptions caused by region switching. This application adopts a method where the home gateway node announces its own region switching information, and the gateway node constructs tunnel messages to support communication for the mobile node. The main reasons for using tunnel messages for communication before the cross-region node routing information has been fully disseminated are as follows:

[0134] (1) In a highly dynamic environment, the connection relationship between nodes changes rapidly, that is, the nodes through which the notification information and subsequent data transmission are not necessarily the same. Tunnel messages can simplify the problem of addressing cross-regional mobile nodes to addressing nodes that do not cross regions.

[0135] (2) In cases where multiple nodes enter a certain area for operation at the same time, relying solely on the gateway node to modify the destination IP to the Xinxiang Area IP in the original network layer header is not only non-standard, but also cannot be effectively forwarded after being delivered to the Xinxiang area.

[0136] (3) Tunnel messages will bring additional header overhead, so the gateway node that encapsulates the tunnel message can stop encapsulation after receiving the latest routing information of the cross-regional subnet node and forward the data as a normal message.

[0137] Optionally, maintaining the communication connection during the node switching process based on the home agent includes:

[0138] Step 41: Establish a forward temporary path for the node and complete the transmission of the proxy request message; the proxy request message includes the node's current area IP, serial number, and proxy duration; the serial number is used to identify the new and old proxy requests; the proxy duration is determined by the Xinxiang gateway node;

[0139] Step 42: Different identity nodes process the received proxy request messages.

[0140] Optionally, see Figure 18 Step 41 includes:

[0141] The node completes the autonomous area switch; it checks if the new gateway node information exists in the ARP cache table; if it exists, it directly establishes a temporary path to the gateway node; if it does not exist, it randomly selects a node from the nodes in the new area as the next hop to the new gateway node, thus establishing a temporary path to the gateway node; it fills the destination address field in the network layer header with the home address and sets the protocol field to proxy request; it fills the data field with the home address and proxy sequence number of the proxy request message, and then uses unicast at the network layer to send the proxy request message to the home gateway; Figure 19 In the sequence number, NewArea IP indicates the current area to which the node belongs; Serial Number, a sequence number that is used if a similar field exists in the routing protocol, otherwise a new one is created from scratch, used to identify the old and new proxy requests, and to avoid interference from outdated routing information on the path after the area switch; Duration Time, the proxy duration, is filled in by the Xinxiang gateway node. This indicates the proxy duration to avoid the overhead of using proxy packets when the latest path information of the node has been obtained; after the network layer information is filled in, it is handed over to the ARP module for processing. If the ARP module finds that the protocol field is a proxy request packet, it sets the next-hop MAC address as the MAC layer broadcast address and sends it to the MAC layer for processing; the MAC layer sends the proxy request packet in the form of a one-hop broadcast.

[0142] In this way, a forward temporary path is established for mobile nodes across subnets, and the proxy request message is sent.

[0143] See Figure 20 Different identity nodes handle proxy request messages differently:

[0144] The Xinxiang node establishes a temporary reverse path to the source node. With the help of packet forwarding, it establishes temporary path information between the destination address (source IP) and the next-hop address (source IP) at the network layer, and establishes a "misaligned" mapping relationship between the source IP and the previous hop HA to complete the reverse transmission of the message. The Xinxiang gateway node deletes the expired path information related to the source node and fills the Duration Time field in the proxy request message with its own routing table. The node in the new area is the Xinxiang node.

[0145] The home node deletes path information related to the source node to avoid loops. Based on the proxy request message information, the home gateway node initiates proxy mode, and for subsequent packets whose destination address is the source node, it encapsulates them with a header indicating the destination node is the Xinxiang gateway, and sets the Protocol field to tunnel packet.

[0146] Other non-gateway nodes directly discard proxy request packets. Other gateway nodes deploy proxies based on how the Xinxiang node and the hometown node handle proxy request packets, in order to reduce the probability of "triangular communication," such as... Figure 21 As shown.

[0147] This application achieves interconnection and interoperability of heterogeneous data link networks by modifying existing equipment and adding a network layer and ARP module.

[0148] Regarding addresses, the newly added IP address in the network layer serves as the node's identity identifier in the network, effectively solving the problems of difficulty in identification and differentiation between original HAs and avoiding the cumbersome conversion process between HAs. At the same time, the ARP module retains the original HA address of the device, reducing modifications to the device's MAC layer, and dynamically establishes an IP-HA mapping relationship, enabling HAs to still be used for one-hop data transmission.

[0149] In terms of routing, the gateway node serves as the aggregator of routing information for each data link, and the connection port between the ARP module and the MAC layer serves as the basis for link selection, thereby enabling the interconnection of routing information across the entire network and ensuring the possibility of cross-link transmission.

[0150] It is worth noting that the method in this application has poor backward compatibility, and modifying existing equipment may not be straightforward. However, the new addressing approach provided by this method can easily achieve subnetting, thereby enabling the construction of clustered networks to adapt to network environments with large-scale nodes. Furthermore, by utilizing the network layer header, functions such as network multicast and unified quality of service can be implemented.

[0151] Although subnetting can affect the mobility and self-organization of a network, this problem has been largely resolved with the introduction of new protocols, which also demonstrates the powerful scalability of IP-based methods.

[0152] The subnetting method proposed in this application addresses the problem that flat networks struggle to support communication needs with a large number of nodes. It employs Area IP for network clustering, isolating flooded information in the network in the form of subnets, thereby saving network bandwidth resources.

[0153] This application proposes a mobility management method that addresses the issues of node disconnection and identity recognition caused by long-distance movement of subnet nodes in clustered networks. It enhances the node's Area IP awareness by utilizing stored information mapped to its own address, enabling rapid path connectivity determination and autonomous area handover. This scheme maintains the network identity of mobile nodes across subnets and facilitates the autonomous entry / exit of subnets and the re-establishment of network relationships. Furthermore, it utilizes a home agent to improve communication maintenance during the node area handover process.

[0154] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and not to limit them. Although this application has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of this application. Any modifications or equivalent substitutions that do not depart from the spirit and scope of this application should be covered within the protection scope of the claims of this application.

Claims

1. A heterogeneous data link interconnection and intercommunication method based on unified identification and multi-layer address mapping, characterized in that, Comprise: Step 1: Relying on network layer, give each network device a unified IP communication address, each network device address HA only needs to establish mapping with IP to realize heterogeneous identification at address level; Step 2: In the homogeneous data chain, add ARP module in network layer, use the broadcast form existing in wireless network and the network perception information of single-hop propagation in network to directly establish ARP cache table, that is, use the message of only one-hop transmission in network to realize that the source IP and source Area IP of network layer header are matched with the source HA of MAC layer header, or in the heterogeneous data chain, the gateway node uses the interface connection relationship between MAC layer and network layer to establish ARP mapping; Step 3: Identify different network areas with Area IP, and divide the network into multiple subnets; Step 4: Nodes realize self-entry into new subnet and establish connection with nodes in the new subnet based on cross-area Area IP self-switching, and keep communication connection during node area change based on home agent; The step 1 comprises: The network layer provides new IP address for the original network device, and uses it as the unified identity of the node in the network, and is responsible for the addressing operation in the network; The same network device can use different IP for communication; The new IP address is composed of M bits; The original HA of the network device is reserved, and the dynamic mapping with IP is completed through ARP module; The address pool of M bits is pre-planned, the all-1 address is used as broadcast address, and the first N addresses are reserved for gateway node, and at the same time, the N addresses are used as Area IP of jurisdiction range of gateway node, for identifying the subnet area belonging of the subnet node; The step 2 comprises: In the active routing scenario, the node The packet transmits the self-network perception information, the data packet encapsulates a network layer header at the network layer, and the network layer header includes a data packet type, a source node IP, and a destination node IP; wherein the destination node IP is an Area IP; a destination HA of the MAC layer header is a broadcast address of the MAC layer; the message includes the MAC layer header, the network layer header, and the network perception information; node The network sensing information emitted is directly received by the nodes Receive, or, node The network sensing information sent out is forwarded to the nodes through relay nodes. ,node After determining the type of the received data packet, it is used as a resource for establishing the ARP cache table. The source HA information in the MAC layer header and the IP information in the network layer header are extracted to establish the ARP cache table; Node and nodes For any node in the same subnet of the same data link, or, a node and nodes Any node in different subnets of the same data chain; The step 3 comprises: Node and Node send network awareness information through message respectively in A chain and B chain, the destination HA in MAC layer header is the broadcast address of the own link; the network interface in the ARP cache table of Node is the number of the interface connecting MAC layer and network layer, to distinguish the data chain type and ensure the correct next hop link is selected when forwarding data; the message includes MAC layer header, network layer header and network awareness information; the network layer header includes data packet type, source node IP and source Area IP; the MAC layer header includes destination HA; the ARP cache table of Node includes the IP, HA, Area IP and network interface of the neighbor node; Node and Node are located in the same subnet; The step 4 comprises: The node realizes self-entry into new subnet and establishes connection with nodes in the new subnet based on cross-area Area IP self-switching, comprising: The node realizes self-entry into new subnet and establishes connection with nodes in the new subnet based on cross-area Area IP self-switching, comprising: The node realizes self-entry into new subnet and establishes connection with nodes in the new subnet based on cross-area Area IP self-switching, comprising: The node realizes self-entry into new subnet and establishes connection with nodes in the new subnet based on cross-area Area IP self-switching, comprising: The node realizes self-entry into new subnet and establishes connection with nodes in the new subnet based on cross-area Area IP self-switching, comprising: The node realizes self-entry into new subnet and establishes connection with nodes in the new subnet based on cross-area Area IP self-switching, comprising: The node realizes self-entry into new subnet and establishes connection with nodes in the new subnet based on cross-area Area IP self-switching, comprising: If the new area meets the area switching requirements, the node switches its Area IP, completes the area switching, deletes the original routing information, and gradually establishes new network relationships; the area switching requirements are related to network connection reliability and network congestion level of the new area.

2. The method of claim 1, wherein, The step 3 comprises: Step 31: the node receives the network awareness message, judges whether the node is a gateway node; if yes, the network awareness message is directly received; otherwise, the source node belongs to a subnet is judged; if the source node is not a node in the subnet, the packet is discarded; if the source node is a node in the subnet, the identity of the source node is judged; if the source node is a gateway node in the subnet, only the path information about the gateway node in the network awareness message is received, and then the packet is discarded; if the source node is not a gateway node, the network awareness message is received; Step 32: the gateway node integrates multiple routing information of the gateway node, and sends the multiple routing information in the form of MAC broadcast; a destination IP in a network layer header is set as an Area IP, that is, the Area IP of the gateway node is consistent with the IP, and the data packet is identified as network awareness information, so as to indicate that the data packet is network awareness information of a node in an area corresponding to the Area IP; Step 33: The node checks the type and destination address after receiving the data packet at the network layer, finds that the data packet does not match the area number of itself, and discards the data packet; The node finds that the data packet matches the area number of itself, selects to receive the data packet at the network layer, and only obtains the path information about the gateway node in the network awareness message; The node and The node is any node in the network; Step 34: according to step 33, all nodes in the network are traversed, the clustering cutting of the nodes in the network is completed, and multiple subnets are obtained; different subnets in the multiple subnets communicate through gateway nodes.

3. The method of claim 1, wherein, In the multiple subnets, a data packet forwarding process comprises: Step 301: taking receiving a data packet as a starting point, checking a next hop HA encapsulated in a MAC header of the data packet, judging whether the data packet is processed by the node, and if the next hop HA is inconsistent with a node HA, discarding the data packet; Step 302: if the next hop HA is the node HA, removing the MAC layer header of the data packet, uploading the data packet to a network layer, checking a destination IP in the network layer header, and judging whether forwarding is needed; if the destination IP is consistent with a node IP, the node is a destination node, the network layer header is removed, the data packet is uploaded to an application layer, and the data packet is not forwarded any more; Step 303: if the destination IP is inconsistent with the node IP, forwarding work is performed: a routing table is queried, a new next hop IP is transferred to an ARP module according to the destination IP information, and step 304 is transferred to; if there is no routing path leading to the destination IP in the node, the identity of the node is judged; if the node is a gateway node, the packet is discarded, and the forwarding fails; if the node is a subnet node, the data packet is forwarded to the gateway node, and whether the destination node is reachable is judged by the gateway node; Step 304: the ARP module receives the next hop IP information, queries an ARP cache table, and if there is no related IP-HA mapping information, the packet is discarded, and the forwarding fails; Step 305: there is related IP-HA information in the ARP cache table, a next hop HA address is refilled, the next hop network is sent to a matched MAC layer according to the next hop network, the MAC layer re-encapsulates a MAC header, the data packet is sent, and the forwarding is completed.

4. The method of claim 1, wherein, The communication connection in the node area switching process based on the home agent comprises: Step 41: a forward temporary path of the node is established, and sending of the proxy request message is completed; the proxy request message includes a new area IP of the node, a serial number, and a proxy time; the serial number is used for identification of new and old proxy requests; the proxy time is determined by the new home gateway node; Step 42: different identity nodes process the received proxy request message.

5. The method of claim 4, wherein, The step 41 comprises: The node completes autonomous area switching; it is determined whether new gateway node information exists in an ARP cache table; if the new gateway node information exists, a temporary path information to the gateway node is directly established; if the new gateway node information does not exist, a node is randomly selected from nodes in a new area as a next hop to the new gateway node, so as to realize temporary path construction to the gateway node; a home address is filled in a destination address field in a network layer header, a protocol field is set as a proxy request, a new home address and a proxy serial number are filled in a data field to fill the proxy request message, and then the proxy request message is sent to the home gateway by using unicast in the network layer; if the ARP module checks that the protocol field is the proxy request message, a next hop MAC address is set as a MAC layer broadcast address and is sent to the MAC layer for processing; the MAC layer sends the proxy request message in the form of one-hop broadcast.

6. The method of claim 4, wherein, The step 42 comprises: The new home node establishes a temporary reverse path to the source node, establishes temporary path information of a destination address and a next hop address in the network layer by means of message forwarding, establishes a "wrong position" mapping relationship of the source IP and the last hop HA, and completes reverse transmission of the message; the new home gateway node deletes expired path information of the source node and fills a Duration Time field in the proxy request message by using a routing table of the new home gateway node; the node in the new area is the new home node; The home node deletes path information related to the source node; the home gateway node starts a proxy mode according to the proxy request message, and encapsulates a layer of a header of a destination node as the new home gateway and sets a Protocol field as a tunnel message for a message received subsequently and having the destination address as the source node; Other non-gateway nodes directly discard the proxy request message, and other gateway nodes perform proxy deployment according to processing modes of the proxy request message by the new home node and the home node.

Images