CN101621449B - Methods and device for terminal access and proxy update in mesh network - Google Patents

Abstract

The embodiment of the present invention relates to the mesh network communication field, and provides a terminal access method and an agent update method in the mesh network, as well as a mesh gateway, a mesh access point, an address translation device and a mesh network system. By configuring a unified IP address for all terminals in the mesh network, the MAP does not need to reconfigure the IP address for the terminal during the process of terminal access, handover, and agent update, which saves the DHCP process and eliminates the need for The problem of increased switching delay caused by reconfiguring the IP address reduces the switching delay and improves the service performance of the network.

Description

Method and device for terminal access and agent update in mesh network

technical field

The invention relates to the field of mesh network communication, in particular to a terminal access method and an agent update method in the mesh network, as well as a mesh gateway, a mesh access point, an address translation device and a mesh network system.

Background technique

Wireless mesh network (WMN, wireless mesh network) is a new network structure based on multi-hop routing and peer-to-peer network technology. Self-healing, self-balancing.

In the mesh (mesh network) network, the routing problem is an important research topic. The currently used routing includes routing based on the IP (Internet Protocol, Internet Protocol) layer, and also based on the MAC (Media Access Control, media access control) layer. routing. 802.11 is a MAC and PHY layer (physical layer) protocol family. The 802.11s mesh network working group, as a working group for researching WiFi mesh, uses a routing protocol based on the MAC layer. The logo also reflects the location information of the terminal. In mesh networks, mobility is an important requirement. The goal of mobility is that the MN (Mobile Node, mobile node) can attach to a new AP (access point, access point) when moving, and the ongoing communication can be seamlessly routed to the new AP. Since the WiFi mesh network is based on multi-hop routing at the MAC layer, when the terminal is switched from one AP of the mesh network to another AP during the movement, the IP subnet where the MN is located may change, while in the prior art , when the IP subnet where the MN is located changes due to the handover of the MN, the MN needs to execute the DHCP (Dynamic Host Configuration Protocol, Dynamic Host Configuration Protocol) interaction process that occurs above the MAC layer, and communicate with the DHCP server on the gateway side of the mesh network , and re-allocate the subnet IP address for the terminal.

In the prior art, when the IP subnet where the MN is located changes, the interaction above the MAC layer (such as the DHCP process) requires the MN to communicate with the mesh network gateway side to perform related operations, and this interaction process is based on multiple If the jump lasts for a long time, it will lead to a long switching delay and low network performance.

Contents of the invention

Embodiments of the present invention provide a method for terminal access and an agent update method in a mesh network on the one hand, and provide a mesh gateway, a mesh access point, an address translation device, and a mesh network system on the other hand, enabling the terminal When a change occurs, there is no need for DHCP interaction, and no need to re-allocate IP addresses for terminals, which reduces access and handover delays and improves network performance.

A method for terminal access in a mesh network provided by an embodiment of the present invention includes:

The mesh access point establishes an association with the access terminal;

The mesh access point receives the first message sent by the terminal, where the first message includes a terminal address and a port number of the terminal;

The mesh access point sends a second message to the terminal, where the second message includes a network-wide unified IP address, for the terminal to use the network-wide unified IP address to communicate with an external network.

In the method for updating a mesh network agent provided by the embodiment of the present invention, the terminals in the network are configured with a unified IP address for the entire network, including:

The target mesh access point receives a first message, wherein the first message includes a terminal address and a port number of the terminal, and the target mesh access point is a mesh access point to which the terminal will switch;

The target mesh access point carries the terminal address and the port number of the terminal in the first message in a proxy update message, and sends a proxy update message to the gateway; wherein, the proxy update message is used for the gateway to perform proxy renew.

A mesh gateway node provided by an embodiment of the present invention includes:

The receiving module is configured to receive an agent update message sent by the mesh access point; wherein, the agent update message includes the MAC address of the terminal and the port number of the terminal, and the terminal is configured as a unified IP address throughout the network;

An agent information module, configured to save the corresponding relationship between the terminal and the mesh access point as the agent information of the terminal according to the agent update message received by the receiving module;

A sending module, configured to send an agent update success message to the mesh access point after the agent information module saves the agent information of the terminal.

A mesh access point provided by an embodiment of the present invention includes:

A receiving module, configured to receive a first message, wherein the first message includes the MAC address of the terminal and the port number of the terminal, and the terminal is configured as a unified IP address throughout the network;

A processing module, configured to construct a proxy update message according to the first message received by the receiving module, where the proxy update message includes the MAC address of the terminal and the port number of the terminal;

The sending module is configured to send the proxy update message constructed by the processing module to the gateway; wherein the proxy update message is used for the gateway to perform proxy update.

An address translation device provided by an embodiment of the present invention includes:

A receiving module, configured to receive an address registration message sent by the gateway; wherein the address registration message includes the MAC address of the terminal and the port number of the terminal, and the terminal is configured as a unified IP address for the entire network;

The address translation module is used to allocate a gateway port number to the terminal according to the address registration message received by the receiving module, and establish an address translation relationship between the MAC address of the terminal, the port number of the terminal, the IP address of the gateway, and the gateway port number ;

A sending module, configured to send an address registration success message to the gateway.

In a mesh network system provided by an embodiment of the present invention, terminals in the network are configured with a unified IP address for the entire network, including:

The mesh access point is configured to receive a first message, wherein the first message includes the MAC address of the terminal and the port number of the terminal; construct an agent update message according to the received first message, wherein the agent update The message includes the MAC address of the terminal and the port number of the terminal; sending the constructed proxy update message to the gateway;

a gateway, configured to receive an agent update message sent by the mesh access point, wherein the agent update message includes the MAC address of the terminal and the port number of the terminal; according to the received agent update message, store the terminal and the mesh The corresponding relationship of the access point is the agent information of the terminal; sending an agent update success message to the mesh access point.

The invention proposes an IP address allocation and mobility management scheme in the mesh network, and the terminals and mesh nodes in the mesh network can use the same IP address to access the external network. Since a unified IP address is configured for all terminals in the mesh network, the terminal has a unique and unified IP address in the entire mesh network. When the terminal moves in the mesh network or the agent is updated, there is no switching from a subnet In the case of another subnet, MAP does not need to reconfigure the IP address for the terminal, which saves the DHCP process, eliminates the problem of increased switching delay caused by reconfiguring the IP address, reduces the switching delay, and improves network services. performance.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

FIG. 1 is a flow chart of a terminal initial access method according to Embodiment 1 of the present invention;

FIG. 2 is a flow chart of a method for quickly switching terminals according to Embodiment 2 of the present invention;

FIG. 3 is a flowchart of a method for quickly switching terminals across gateways according to Embodiment 3 of the present invention;

FIG. 4 is a flow chart of a terminal common switching method according to Embodiment 4 of the present invention;

FIG. 5 is a flow chart of a method for common switching between terminals across gateways according to Embodiment 5 of the present invention;

6 is a schematic diagram of a mesh network system according to Embodiment 6 of the present invention;

FIG. 7 is a structural diagram of a MAP device according to Embodiment 6 of the present invention;

FIG. 8 is a structural diagram of a gateway device according to Embodiment 6 of the present invention;

FIG. 9 is a schematic diagram of a mesh network system according to Embodiment 7 of the present invention;

FIG. 10 is a structural diagram of a MAP according to Embodiment 7 of the present invention;

FIG. 11 is a structural diagram of a gateway according to Embodiment 7 of the present invention;

FIG. 12 is a structural diagram of an address translation device according to Embodiment 7 of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Embodiment one

As shown in Figure 1, the embodiment of the present invention provides a method for initial access of a terminal in a mesh network, the method comprising:

Step 101, the terminal (terminal) establishes an association with a MAP (mesh access point, mesh access point), establishes a communication link between the terminal and the MAP, and completes access authentication; wherein, the communication link may not involve three layers ( IP layer), only the second layer (MAC layer) link;

The association can be established in any of the following two ways: (1) The terminal actively broadcasts a probe request (probe request), and each MAP in the network sends a probe response (prober response) after receiving the probe request, and the probe response can include , MAP’s MAC address, ESSID, SSPN, QoS capability, IP address of the GW behind the MAP, etc., the terminal selects a network according to the information contained in the inquiry response, for example, selects a MAP as an access point based on signal strength, QoS capability matching, etc. point; (2) the beacon (beacon) frame sent by the receiving network of the terminal; wherein, the beacon frame may include the MAC address of the MAP, ESSID, SSPN, QoS capability, the IP address of the GW at the MAP backend, etc., After that, the terminal performs network selection according to the information contained in the beacon frame;

Step 102, the terminal sends a DHCP discovery (DHCP discover) message to the MAP where the connection is established, and initiates a DHCP process; the DHCP discover message includes <terminal MAC address: terminal port>, and the terminal port (port) communicates between the terminal and the external network When used, it can be determined by the terminal itself, and one is randomly determined from the ports of the terminal itself;

Step 103, MAP sends a DHCP offer (DHCP offer) message to the terminal, and the unified IP address in the mesh network is configured to the terminal;

As a DHCP server (DHCP server), MAP carries the unified IP address of the whole network in the DHCP offer message and sends it to the terminal, and can further set the lease period of this IP address as permanent; the unified IP address of the whole network can be pre-configured in MAP;

Step 104, the terminal receives the DHCP offer message, and sets its own IP address as the unified IP address of the whole network according to the unified IP address of the whole network;

Step 105, after the MAP returns the DHCP offer message to the terminal, the DHCP process ends, the MAP triggers the agent update process, and the MAP sends an agent update message to the home gateway (gateway, GW), and registers the agent information of the terminal in the home gateway of the terminal; Wherein, the home gateway is a gateway selected by the MAP for the terminal, and the MAP records the home gateway information, and at the same time registers the corresponding relationship between <terminal MAC address: terminal port> and the MAC address of the MAP, that is, proxy information;

Step 106, the home gateway of the terminal receives the agent update message sent by the MAP, and after updating the agent information of the terminal in its own agent information table, sends an address registration message to an AT (address translation, address translation) device; wherein, the AT device is a logical The functional entity can be an independent physical entity, or it can be located in a gateway or other equipment as a functional module of the gateway or other equipment;

Step 107, the AT device receives the address registration message, assigns a gateway Port to the registered terminal, establishes the corresponding relationship between <terminal MAC address: terminal port> and <gateway node IP address: gateway port>, and sets <terminal MAC address The corresponding relationship between address: terminal port> and <IP address of gateway node: gateway port> is added to the conversion relationship table; among them, the conversion relationship table is used to record <MAC address of terminal: terminal port> and <IP address of gateway node: gateway port> conversion relationship, and can be used for each device to query; at the same time, since the terminal is accessing the mesh network for the first time, the AT device can also determine a HA (home agent, home agent) for the terminal, and carry the address of the HA in the In the registration success message;

Step 108, the AT device sends a registration success message (OK) to the home gateway of the terminal to confirm that the address translation message is registered successfully; the registration success message includes the address of the home agent HA of the terminal;

Step 109, the home gateway sends an agent update success message (OK) to the MAP; the agent update success message includes the address of the home agent HA of the terminal, and the MAP can further store the address of the home agent HA of the terminal as the access point for the initial access of the terminal. address;

Step 110, after the terminal completes the configuration of the IP address, it can communicate normally, and the subsequent address conversion relationship registration operation is transparent to the terminal.

In this embodiment, the AT device is a logical functional entity, which may be located in other devices. For example, when the AT device is located in the home gateway as a module of the home gateway, the address registration message and registration success message in the process are primitives in the module, not actual message messages, and at this time the AT device and the home gateway can communicate with each other. share the same MAC address. In the following embodiments, referring to the process of this embodiment, those skilled in the art can easily think of the specific implementation of each embodiment when the AT device is used as an independent entity, or as a module on a gateway or other devices, Therefore, no matter whether the AT device is on the same physical entity as the home gateway or not, it is within the protection scope of the present invention.

In this embodiment, when the terminal accesses the network, the MAP carries the uniform IP address of the entire network in the DHCP offer message and configures it for the terminal, and then the terminal uses this IP address to communicate with the external network. The network is unified, so the terminal does not redistribute the IP address during the switching process, thereby eliminating the problem of increased switching delay caused by reconfiguring the IP address, reducing the switching delay, and improving the service performance of the network .

Embodiment two

As shown in Figure 2, the embodiment of the present invention provides a method for fast switching of terminals in a mesh network. In this embodiment, the terminal switches from OMAP (old MAP, former MAP) to NMAP (new MAP, new MAP). Both NMAP and OMAP have a route to the home gateway of the terminal, wherein the home gateway is a mesh node used to save the proxy information of the terminal, and the fast switching method includes:

Step 201, OMAP triggers switching, and sends a network scanning request (request) message for scanning adjacent networks to the terminal;

Among them, as the terminal moves, OMAP triggers switching according to the current status information of the terminal and the local trigger strategy;

The local trigger strategy of OMAP can include: the device can no longer serve the terminal due to reasons such as maintenance, upgrade, power failure, etc.; Low-priority user services, etc.; other possible trigger conditions include requests from other mesh devices that require terminal switching;

The status information of the terminal can be regularly reported by the terminal to the OMAP, and the reported terminal status information can include: Throughput (unit kbps), packet error rate (Packet error rate), packet transmission delay (minimum value, maximum value, average value, delay jitter) (Packet transfer delay (min, max, average, jitter)), packet loss rate (packet loss rate);

Step 202, after receiving the network scanning request, the terminal sends a probe request (probe request) message to each MAP in the adjacent network;

Step 203, the MAP that receives the probe request sent by the terminal returns a probe response (probe response) message to the terminal; wherein, the probe response message can carry the MAC address, ESSID, SSPN, QoS capability, and the MAP backend of this MAP. The IP address of the gateway where the route exists, etc.;

Step 204, using each MAP returning the inquiry response message as a candidate MAP of the terminal, the terminal reports the information of each MAP carried in the inquiry response message returned by each candidate MAP to the OMAP through a network scan response (response) message;

Step 205, OMAP receives the network scan response, according to the MAC address of each candidate MAP and the IP address of the gateway of each candidate MAP back end, query the information of the candidate MAP to the reachable gateway of any candidate MAP back end; Wherein, the candidate MAP and the subsequent There is a reachable route to the gateway at the end, and a candidate MAP can be reachable to multiple gateways at the same time. When there is a home gateway of the terminal among these reachable gateways, it is preferred to query the information of the candidate MAP from the home network of the terminal, because the terminal When initially accessing the mesh network, first register the corresponding information with its home gateway, and query the information of candidate MAPs from the terminal's home gateway, so that in the subsequent handover, try to switch to the candidate MAP that has a route to the terminal's home gateway , so that the handover of the terminal can be made as far as possible without crossing the home gateway. Since the handover across the home gateway requires more interaction and longer time, it is prioritized to query the information of candidate MAPs from the home network of the terminal, which can reduce the handover delay as a whole. ;

Step 206, each gateway sends a query response to the OMAP, and returns the information of the candidate MAP; wherein, the information of the candidate MAP may include: the switching type supported by the MAP, the throughput supported by the MAP, the packet error rate, the supported QoS, security, etc.;

Step 207, OMAP performs network selection according to the information of the queried candidate MAP, and selects the selected MAP as the target MAP, that is, NMAP; wherein, the strategy adopted during network selection may be: in the case of meeting the normal communication of the terminal, preferentially select There is a candidate MAP for the route to the home gateway of the terminal as the target MAP;

Step 208, OMAP sends an application resource query message to the terminal, querying the resources to be applied for by the terminal to switch to the new network;

Step 209, the terminal returns an application resource response message, reporting the resource it needs to apply for when switching to the new network;

Step 210, OMAP sends a quick handover request to NMAP according to the resource application response, the handover request carries resource information to be applied by the terminal and <terminal MAC address: port>, where the <terminal MAC address: terminal port> can be It is stored by OMAP when the terminal accesses, for details, refer to step 102 in Embodiment 1; in order to notify NMAP of the address of the home agent HA of the terminal, OMAP can further carry the address of the home agent HA of the terminal in the fast handover request;

Step 211: After receiving the fast handover request, NMAP performs resource reservation according to the resource information requested by the terminal in the fast handover request; NMAP can further obtain the address of the home agent HA of the terminal carried in the fast handover request, and save the The address of the home agent HA of the terminal;

Step 212, NMAP performs agent update at the same time, and sends an agent update request message to the home gateway of the terminal; the agent update request carries the corresponding relationship between <terminal MAC address: terminal port> and the NMAP address, or further includes the terminal's home agent HA the address of;

Step 213, after the home gateway receives the proxy update request message sent by the NMAP, it updates the saved terminal proxy information, and replaces the terminal's original proxy information (correspondence between <terminal MAC address: terminal port> and the OMAP address) with the new Proxy information (correspondence between <terminal MAC address: terminal port> and NMAP address);

Step 214, the home gateway agent is updated, and sends an agent update success message to NMAP;

Step 215, NMAP resource reservation is successful, and after receiving the proxy update success message sent by the home gateway, return a fast switching response to OMAP; wherein, the sequence of resource reservation (step 211) and proxy update (step 212～step 214) The order is not specifically limited, the two can be performed at the same time, or either operation is performed first, and then the other operation is performed;

Step 216: After receiving the fast handover response, the OMAP sends a handover start message to the terminal;

Step 217, OMAP forwards the data sent to the terminal to NMAP at the same time, and can be further sent to the terminal by NMAP after the terminal is associated with NMAP;

Step 218, after the terminal receives the handover start message, it disconnects from the OMAP;

Step 219, the terminal establishes an association with NMAP at the same time, establishes a communication link between the terminal and the MAP, and completes the authentication; wherein, the communication link may not involve the third layer (IP layer), but only the second layer (MAC layer) link , used for messages interacting between the terminal and NMAP after transmission;

Step 220, the terminal sends a handover completion request to NMAP through the established association;

Step 221, after receiving the handover completion request, NMAP sends a resource release request to OMAP;

Step 222, when OMAP receives the resource release request, if there is no packet sent to the terminal in its forwarding queue, then release the resources occupied by the terminal in OMAP, stop data forwarding, if its forwarding queue also has packets sent to the terminal, After sending these packets to NMAP, release the resources occupied by the terminal in OMAP, and stop data forwarding;

Step 223, OMAP returns a resource release response to NMAP;

Step 224, NMAP returns a handover completion response to the terminal;

Step 225, after the terminal completes the handover from OMAP to NMAP, it can perform normal communication according to the prior art.

In this embodiment, if there is a direct communication link between OMAP and NMAP, OMAP and NMAP can communicate directly; if there is no direct communication link between OMAP and NMAP, then use the second layer in the mesh between OMAP and NMAP The routing mechanism communicates with each other based on the MAC addresses of both parties.

In this embodiment, OMAP and NMAP correspond to the home gateway of the same terminal. When the terminal moves in the mesh network, its associated MAP changes, but NMAP has a home gateway route to the terminal. At this time, the terminal's The home gateway does not change.

In this embodiment, when the terminal is switching, the original MAP carries <terminal MAC address: terminal port> in the fast handover request and sends it to the new MAP, and the new MAP saves the <terminal MAC address: terminal port>, and then can According to the <terminal MAC address: terminal port>, the terminal communicates with the external network through the terminal's home gateway. During the switching process of the terminal (step 216 to step 224), the MAP does not need to reconfigure the IP address for the terminal, and the terminal directly uses the whole network The unified IP keeps the IP address of the terminal unchanged before and after switching, thereby eliminating the problem of increased switching delay caused by reconfiguring the IP address, reducing the switching delay, and improving network service performance. And, because before terminal and OMAP disconnect data communication (step 218), NMAP has finished proxy update operation (step 212～step 214), further reduces the time of data communication disconnection, reduces switching delay, improves service performance of the network.

Embodiment three

The mobile handover method in Embodiment 2 does not involve the change of the home gateway of the terminal. When the terminal performs mobile handover across home gateways, the terminal switches from OMAP to NMAP during the movement process in the mesh network, but the NMAP does not exist to the mobile handover method. For the route of the original home gateway (old GW, OGW) of the terminal, NMAP needs to re-register a new home gateway (new GW, NGW) for the terminal. As shown in Figure 3, this embodiment provides a cross-gateway network for terminals in a mesh network. The method of fast switching, the method includes:

Step 301, OMAP triggers switching, and sends a network scanning request (request) message for scanning adjacent networks to the terminal;

Among them, as the terminal moves, OMAP triggers switching according to the current status information of the terminal and the local trigger strategy;

The local trigger strategy of OMAP can include: the device can no longer serve the terminal due to reasons such as maintenance, upgrade, power failure, etc.; Low-priority user services, etc.; other possible trigger conditions include requests from other mesh devices that require terminal switching;

The status information of the terminal can be regularly reported by the terminal to the OMAP, and the reported terminal status information can include: Throughput (unit kbps), packet error rate (Packet error rate), packet transmission delay (minimum value, maximum value, average value, delay jitter) (Packet transfer delay (min, max, average, jitter)), packet loss rate (packet loss rate);

Step 302, after receiving the network scanning request, the terminal sends a probe request (probe request) message to each MAP in the adjacent network;

Step 303, the MAP that receives the probe request sent by the terminal returns a probe response (probe response) message to the terminal; wherein, the probe response message can carry, the MAC address, ESSID, SSPN, QoS capability of the MAP, the backend of the MAP The IP address of the gateway where the route exists, etc.;

Step 304, using each MAP returning the query response message as a candidate MAP of the terminal, the terminal reports the information of each MAP carried in the query response message returned by each candidate MAP to the OMAP through a network scan response (response) message;

Step 305, OMAP receives the network scanning response, according to the MAC address of each candidate MAP and the IP address of the gateway of each candidate MAP back end, query the information of the candidate MAP to the reachable gateway of any candidate MAP back end; Wherein, the candidate MAP and the subsequent There is a reachable route to the gateway at the end, and a candidate MAP can be reachable to multiple gateways at the same time. When there is no home gateway of the terminal among these reachable gateways, query these reachable gateways through the original home gateway OGW of the terminal. Candidate MAP information;

Step 306, each gateway sends a query response to the OMAP, and returns the information of the candidate MAP; wherein, the information of the candidate MAP may include: the switching type supported by the MAP, the throughput supported by the MAP, the packet error rate, the supported QoS, security, etc.;

Step 307, the OMAP performs network selection according to the information of the candidate MAPs inquired, and takes the selected MAP as the target MAP, that is, the NMAP; wherein, the selected NMAP may not have a reachable mesh route to the home gateway of the terminal;

Step 308, OMAP sends an application resource query message to the terminal, querying the resources that the terminal needs to apply for when switching to the new network;

Step 309, the terminal returns an application resource response message, reporting the resource it needs to apply for when switching to the new network;

Step 310, OMAP sends a fast switching request to NMAP according to the resource application response, the switching request carries the resource information to be applied by the terminal and <terminal MAC address: terminal port>, wherein the <terminal MAC address: terminal port> It may be saved by OMAP when the terminal accesses, for details, refer to step 102 in Embodiment 1; in order to notify NMAP of the address of the home agent HA of the terminal, OMAP may further carry the address of the home agent HA of the terminal in the fast handover request ;

Step 311: After receiving the fast handover request, NMAP performs resource reservation according to the resource information requested by the terminal in the fast handover request; NMAP can further obtain the address of the home agent HA of the terminal carried in the fast handover request, and save the The address of the home agent HA of the terminal;

Step 312, NMAP performs proxy update at the same time, because NMAP does not have a reachable route to the original home gateway OGW of the terminal, so NMAP selects a new home gateway NGW for the terminal, and sends a proxy update request message to the new home gateway; proxy update request carry the corresponding relationship between <terminal MAC address: terminal port> and the NMAP address, or further include the address of the home agent HA of the terminal;

Step 313, after the new home gateway receives the proxy update request message sent by NMAP, update the proxy information of the terminal, and add the proxy information of the terminal in its own proxy information table (the correspondence between <the MAC address of the terminal: terminal port> and the NMAP address relation);

Step 314, when the new home gateway updates the proxy table, there is no proxy information of the terminal in the proxy table, so the new home gateway registers the address translation relationship for the terminal at the same time, according to <terminal MAC address: terminal in the proxy update message port> allocates a new home gateway port for the terminal, and establishes the corresponding relationship between <terminal MAC address: terminal port> and <new home gateway node IP address: new home gateway port> on the new home gateway, and assigns <terminal The corresponding relationship between MAC address: terminal port> and <IP address of the new home gateway node: new home gateway port> is added to the conversion relationship table; at this time, the new home gateway includes the address translation function, that is, the AT device is a module of the new home gateway ;

Step 315, after the agent update of the new home gateway is completed, an agent update success message is sent to NMAP;

Step 316, NMAP resource reservation is successful, and after receiving the proxy update success message sent by the new home gateway, return a fast switching response to OMAP; wherein, resource reservation (step 311) and proxy update (step 312～step 314) There is no specific limitation on the sequence, the two can be performed at the same time, or either operation is performed first, and then the other operation is performed later;

Step 317. After receiving the fast handover response, OMAP sends a handover start message to the terminal;

Step 318, OMAP forwards the data sent to the terminal to NMAP at the same time, and after the terminal is associated with NMAP, NMAP can further send it to the terminal;

Step 319, after receiving the switching start message, the terminal disconnects from the OMAP;

Step 320, the terminal establishes an association with NMAP at the same time, establishes a communication link between the terminal and the MAP, and completes the authentication; wherein, the communication link may not involve the third layer (IP layer), but only the second layer (MAC layer) link , used for messages interacting between the terminal and NMAP after transmission;

Step 321, the terminal sends a handover completion request to NMAP through the established association;

Step 322, after receiving the handover completion request, NMAP sends a resource release request to OMAP;

Step 323, when OMAP receives the resource release request, if there is no packet sent to the terminal in its forwarding queue, then release the resource occupied by the terminal in OMAP, stop data forwarding, if its forwarding queue also has packets sent to the terminal, After sending these packets to NMAP, release the resources occupied by the terminal in OMAP, and stop data forwarding;

Step 324, OMAP sends a proxy update delete message to the original home gateway of the terminal before switching;

Step 325, after the original home gateway receives the agent update and delete message, it deletes the previously stored agent information of the terminal,

Step 326, the original home gateway sends an address deletion message to the original AT device before the terminal handover;

Step 327: After the original AT device deletes the saved conversion relationship between <terminal MAC address: terminal port> and <original home gateway node IP address: original home gateway port>, it sends an address deletion success message to the original home gateway;

Step 328, the original home gateway sends an agent update and deletion success message to the OMAP;

Step 329, OMAP returns a resource release response to NMAP;

Step 330, NMAP returns a handover completion response to the terminal;

Step 331, after the terminal finishes switching from OMAP to NMAP, it can perform normal communication according to the existing technology;

Step 332, after the new home gateway address registration in step 314 is successful, the new home gateway initiates the banding up process of Mobile IP to the HA (home agent, home agent) in the mesh, according to the home agent HA of the terminal carried in the agent update message address, the new home gateway sends a BU (banding up, binding update) message to the HA, and the banding up message needs to carry the IP address of the original home gateway, the original home gateway port assigned to the terminal, and the IP of the new home gateway Address, new home gateway port information assigned to the terminal;

Step 333, the HA receives the BU message, and saves the corresponding relationship between <original home gateway IP: original home gateway port> and <new home gateway IP: new home gateway port>;

Step 334, HA returns confirmation (back) message to new home gateway;

Step 335. Afterwards, the HA receives the data packet sent to <original home gateway IP: original home gateway port> and forwards it to <new home gateway IP: new home gateway port>, so as to realize the packet sent to <original home gateway IP : The message of the original home gateway port> is forwarded to <new home gateway IP: new home gateway port>;

Among them, when the AT device establishes the address translation relationship, since the gateway may not have an IP address, the IP address of the AT device itself and the port number port can be used to establish the address translation relationship. At this time, the banding up message carries <original AT device IP: original AT device port> and <new AT device IP: new AT device port>, so as to forward the message sent to <original AT device IP: original AT device port> to <new AT device IP: new AT device port> >, to ensure that the terminal can correctly receive the data packets sent from the external network to the terminal.

In this embodiment, because the home gateway of the terminal corresponding to OMAP and NMAP changes, there is a situation that OMAP and NMAP cannot communicate directly at the second layer. At this time, the communication between OMAP and NMAP is based on the intercommunication of the IP layer. Take NMAP as an example: the source IP address uses the IP address of OMAP. This IP address is the unified IP address of the mesh network. When the data packet passes through the OGW, this IP address will be changed to the OGW address, and the source port is set based on the AT mechanism. It is the Port registered in OGW for OMAP, that is, according to the conversion relationship between <OMAP MAC address: port> and <gateway node IP address: gateway port> saved in the AT device, the <OMAP MAC address in the data packet: port> is converted to the corresponding <IP address of the gateway node: gateway port>; the destination IP address uses the IP address of the NGW, and the destination port is set to the port registered in the NGW by NMAP based on the AT mechanism. Sending a message from NMAP to OMAP is similar and will not be repeated here.

In this embodiment, when the terminal is switching, the original MAP carries <terminal MAC address: terminal port> in the fast handover request and sends it to the new MAP, and the new MAP saves the <terminal MAC address: terminal port>, and then can According to the <terminal MAC address: terminal port>, the terminal communicates with the external network through the new home gateway of the terminal. During the handover process (step 216-step 220), the MAP does not need to reconfigure the IP address for the terminal, and the terminal directly adopts the full The unified IP of the network makes the IP address of the terminal unchanged before and after switching, thereby eliminating the problem of increased switching delay caused by reconfiguring the IP address, reducing the switching delay, and improving the service performance of the network. And, before the terminal and OMAP disconnect data communication (step 319), NMAP has finished proxy updating and address translation relationship establishment (step 312～step 315), further reduces the time of data communication disconnection, reduces handover Delay improves the service performance of the network. In addition, since the new MAP and the original MAP belong to different gateways, the new MAP further establishes the address translation relationship of the terminal on the new home gateway, and performs a banding up process with the HA to ensure that the switched terminal can correctly send and receive information related to the external network. packets, to communicate with the external network.

Embodiment four

As shown in accompanying drawing 4, the embodiment of the present invention provides a kind of method that the terminal generally switches in the mesh network, in this embodiment, the terminal switches from OMAP (old MAP, former MAP) to NMAP (new MAP, new MAP), Both NMAP and OMAP have a route to the home gateway of the terminal, wherein the home gateway is a mesh node used to save the proxy information of the terminal. The common switching method includes:

Step 401, OMAP triggers switching, and sends a network scanning request (request) message for scanning adjacent networks to the terminal;

Among them, as the terminal moves, OMAP triggers switching according to the current status information of the terminal and the local trigger strategy;

The local trigger strategy of OMAP can include: the device can no longer serve the terminal due to reasons such as maintenance, upgrade, power failure, etc.; Low-priority user services, etc.; other possible trigger conditions include requests from other mesh devices that require terminal switching;

The status information of the terminal can be regularly reported by the terminal to the OMAP, and the reported terminal status information can include: Throughput (unit kbps), packet error rate (Packet error rate), packet transmission delay (minimum value, maximum value, average value, delay jitter) (Packet transfer delay (min, max, average, jitter)), packet loss rate (packet loss rate);

Step 402, after receiving the network scanning request, the terminal sends a probe request (probe request) message to each MAP in the adjacent network;

Step 403, the MAP that receives the probe request sent by the terminal returns a probe response (probe response) message to the terminal; wherein, the probe response message can carry, the MAC address, ESSID, SSPN, QoS capability of the MAP, the backend of the MAP The IP address of the gateway where the route exists, etc.;

Step 404, using each MAP returning the query response message as a candidate MAP of the terminal, the terminal reports the information of each MAP carried in the query response message returned by each candidate MAP to the OMAP through a network scan response (response) message;

Step 405, OMAP receives the network scanning response, according to the MAC address of each candidate MAP and the IP address of the gateway of each candidate MAP back end, query the information of the candidate MAP to the reachable gateway of the back end of any candidate MAP; Wherein, the candidate MAP and the subsequent There is a reachable route to the gateway at the end, and a candidate MAP can be reachable to multiple gateways at the same time. When there is a home gateway of the terminal among these reachable gateways, priority is given to querying the information of the candidate MAP from the home network of the terminal;

Step 406, each gateway sends query response to OMAP, returns the information of candidate MAP; Wherein, the information of candidate MAP can comprise: the switching type that MAP supports, the throughput that MAP supports, packet error rate, the QoS that supports, security etc.;

Step 407, OMAP performs network selection according to the information of the queried candidate MAP, and takes the selected MAP as the target MAP, that is, NMAP; wherein, the strategy adopted during network selection may be: in the case of meeting the normal communication of the terminal, preferentially select There is a candidate MAP for the route to the home gateway of the terminal as the target MAP;

Step 408, OMAP sends an application resource query message to the terminal, querying the resources to be applied for by the terminal to switch to the new network;

Step 409, the terminal returns an application resource response message, reporting the resources it needs to apply for when switching to the new network;

Step 410, OMAP sends a handover request to NMAP according to the resource application response, and the handover request carries the resource information to be applied by the terminal; in order to notify NMAP of the address of the home agent HA of the terminal, OMAP can further carry the home of the terminal in the handover request Address of proxy HA;

Step 411: After receiving the handover request, NMAP performs resource reservation according to the resource information requested by the terminal in the handover request; NMAP can further obtain the address of the home agent HA of the terminal carried in the handover request, and save the terminal's home Address of proxy HA;

Step 412, after the NMAP resource reservation is successful, return a switching response to the OMAP;

Step 413, after receiving the handover response, the OMAP sends a handover start message to the terminal;

Step 414, OMAP forwards the data sent to the terminal to NMAP at the same time, and after the terminal is associated with NMAP, NMAP can further send it to the terminal;

Step 415, after receiving the switching start message, the terminal disconnects from the OMAP;

Step 416, the terminal establishes an association with the NMAP at the same time, establishes a communication link between the terminal and the MAP, and completes the authentication; wherein, the communication link may not involve the third layer (IP layer), but only the second layer (MAC layer) link , used for messages interacting between the terminal and NMAP after transmission;

Step 417, the terminal sends a handover completion request to NMAP through the established association; the handover completion request includes <terminal MAC address: terminal port>;

Step 418, NMAP performs proxy update after receiving the handover completion request, and sends a proxy update request message to the home gateway of the terminal; the proxy update request carries the corresponding relationship between <terminal MAC address: terminal port> and the NMAP address, or further Including the address of the home agent HA of the terminal;

Step 419, after the home gateway receives the agent update request message sent by the NMAP, it updates the saved terminal agent information, and replaces the terminal's original agent information (correspondence between <terminal MAC address: terminal port> and the OMAP address) with the new Proxy information (correspondence between <terminal MAC address: terminal port> and NMAP address);

Step 420, the home gateway agent is updated, and sends an agent update success message to NMAP;

Step 421, NMAP sends a resource release request to OMAP after receiving the proxy update success message sent by the home gateway;

Step 422, when OMAP receives the resource release request, if there is no packet sent to the terminal in its forwarding queue, then release the resource occupied by the terminal in OMAP, stop data forwarding, if its forwarding queue also has packets sent to the terminal, After sending these packets to NMAP, release the resources occupied by the terminal in OMAP, and stop data forwarding;

Step 423, OMAP returns a resource release response to NMAP;

Step 424, NMAP returns a handover completion response to the terminal;

Step 425, after the terminal completes the handover from OMAP to NMAP, it can perform normal communication according to the prior art.

In this embodiment, if there is a direct communication link between OMAP and NMAP, OMAP and NMAP can communicate directly; if there is no direct communication link between OMAP and NMAP, then use the second layer in the mesh between OMAP and NMAP The routing mechanism communicates with each other based on the MAC addresses of both parties.

In this embodiment, when the terminal is switching, the original MAP carries <terminal MAC address: terminal port> in the switching request and sends it to the new MAP, and the new MAP saves the <terminal MAC address: terminal port>. The <terminal MAC address: terminal port> communicates with the external network through the terminal's home gateway. During the switching process (step 415 to step 424) of the terminal, the MAP does not need to reconfigure the IP address for the terminal, and the terminal directly uses the unified IP, so that the IP address of the terminal remains unchanged before and after switching, thereby eliminating the problem of increased switching delay caused by reconfiguring the IP address, reducing the switching delay, and improving network service performance.

Embodiment five

The mobile handover method in Embodiment 4 does not involve the change of the home gateway of the terminal. When the terminal performs mobile handover across the home gateway, the terminal switches from OMAP to NMAP during the movement process in the mesh network, but the NMAP does not exist to the mobile handover method. For the route of the original home gateway (old GW, OGW) of the terminal, NMAP needs to re-register a new home gateway (new GW, NGW) for the terminal. As shown in Figure 5, this embodiment provides a cross-gateway network for terminals in a mesh network. The general switching method, the method includes:

Step 501, OMAP triggers switching, and sends a network scanning request (request) message for scanning adjacent networks to the terminal;

Among them, as the terminal moves, OMAP triggers switching according to the current status information of the terminal and the local trigger strategy;

The local trigger strategy of OMAP can include: the device can no longer serve the terminal due to reasons such as maintenance, upgrade, power failure, etc.; Low-priority user services, etc.; other possible trigger conditions include requests from other mesh devices that require terminal switching;

The status information of the terminal can be regularly reported by the terminal to the OMAP, and the reported terminal status information can include: Throughput (unit kbps), packet error rate (Packet error rate), packet transmission delay (minimum value, maximum value, average value, delay jitter) (Packet transfer delay (min, max, average, jitter)), packet loss rate (packet loss rate);

Step 502, after receiving the network scanning request, the terminal sends a probe request (probe request) message to each MAP in the adjacent network;

Step 503, the MAP that receives the probe request sent by the terminal returns a probe response (probe response) message to the terminal; wherein, the probe response message can carry the MAC address, ESSID, SSPN, QoS capability, and the MAP backend of the MAP. The IP address of the gateway where the route exists, etc.;

Step 504, using each MAP returning the query response message as a candidate MAP of the terminal, the terminal reports the information of each MAP carried in the query response message returned by each candidate MAP to the OMAP through a network scan response (response) message;

Step 505, OMAP receives the network scanning response, according to the MAC address of each candidate MAP and the IP address of the gateway of each candidate MAP back end, query the information of the candidate MAP to the reachable gateway of any candidate MAP back end; Wherein, the candidate MAP and the subsequent There is a reachable route to the gateway at the end, and a candidate MAP can be reachable to multiple gateways at the same time. When there is no home gateway of the terminal among these reachable gateways, query these reachable gateways through the original home gateway OGW of the terminal. Candidate MAP information;

Step 506, each gateway sends query response to OMAP, returns the information of candidate MAP; Wherein, the information of candidate MAP can include: the switching type that MAP supports, the throughput that MAP supports, packet error rate, the QoS that supports, security etc.;

Step 507, the OMAP performs network selection according to the information of the candidate MAP inquired, and takes the selected MAP as the target MAP, that is, the NMAP; wherein, the selected NMAP may not have a reachable mesh route to the home gateway of the terminal;

Step 508, OMAP sends an application resource query message to the terminal, querying the resource to be applied for by the terminal switching to the new network;

Step 509, the terminal returns an application resource response message, reporting the resources it needs to apply for when switching to the new network;

Step 510, OMAP sends a handover request to NMAP according to the resource application response, and the handover request carries the resource information to be applied by the terminal; in order to notify NMAP of the address of the terminal's home agent HA, OMAP may further carry the terminal's home agent in the handover request Address of proxy HA;

Step 511: After receiving the handover request, NMAP performs resource reservation according to the resource information requested by the terminal in the handover request; NMAP can further obtain the address of the home agent HA of the terminal carried in the handover request, and save the terminal's HA address. The address of the home agent HA;

Step 512, after NMAP resource reservation is successful, return a handover response to OMAP;

Step 513, after receiving the handover response, the OMAP sends a handover start message to the terminal;

Step 514, OMAP forwards the data sent to the terminal to NMAP at the same time, and after the terminal is associated with NMAP, NMAP can further send it to the terminal;

Step 515, after receiving the switching start message, the terminal disconnects from the OMAP;

Step 516, the terminal establishes an association with NMAP at the same time, establishes a communication link between the terminal and the MAP, and completes the authentication; wherein, the communication link may not involve the third layer (IP layer), but only the second layer (MAC layer) link , used for messages interacting between the terminal and NMAP after transmission;

Step 517, the terminal sends a handover completion request to NMAP through the established association; the handover completion request includes <terminal MAC address: terminal port>;

Step 518: NMAP performs proxy update after receiving the handover completion request, because NMAP does not have a reachable route to the original home gateway OGW of the terminal, so NMAP selects a new home gateway NGW for the terminal, and sends a proxy update to the new home gateway Request message; the agent update request carries the corresponding relationship between <terminal MAC address: terminal port> and the NMAP address, or further includes the address of the home agent HA of the terminal;

Step 519, after the new home gateway receives the agent update request message sent by NMAP, it updates the agent information of the terminal, and adds the agent information of the terminal in its own agent information table (the correspondence between <the MAC address of the terminal: terminal port> and the NMAP address relation);

Step 520, when the new home gateway updates the proxy table, there is no proxy information of the terminal in the proxy table, so the new home gateway registers the address translation relationship for the terminal at the same time, according to <terminal MAC address: terminal in the proxy update message port> allocates a new home gateway port for the terminal, and establishes the corresponding relationship between <terminal MAC address: terminal port> and <new home gateway node IP address: new home gateway port> on the new home gateway, and assigns <terminal The corresponding relationship between MAC address: terminal port> and <IP address of the new home gateway node: new home gateway port> is added to the conversion relationship table; at this time, the new home gateway includes the address translation function, that is, the AT device is a module of the new home gateway ;

Step 521, after the new home gateway proxy is updated, a proxy update success message is sent to NMAP;

Step 522: After receiving the proxy update success message sent by the home gateway, the NMAP sends a resource release request to the OMAP;

Step 523, when OMAP receives the resource release request, if there is no grouping sent to the terminal in its forwarding queue, then release the resources occupied by the terminal in OMAP, stop data forwarding, if its forwarding queue also has packets sent to the terminal, After sending these packets to NMAP, release the resources occupied by the terminal in OMAP, and stop data forwarding;

Step 524, OMAP sends a proxy update delete message to the original home gateway OGW of the terminal before the handover;

Step 525: After receiving the agent update and delete message, the original home gateway deletes the previously saved terminal agent information;

Step 526, the original home gateway sends an address deletion message to the original AT device before the terminal handover;

Step 527: After the original AT device deletes the saved conversion relationship between <terminal MAC address: terminal port> and <original home gateway node IP address: original home gateway port>, it sends an address deletion success message to the original home gateway;

Step 528, the original home gateway sends an agent update and deletion success message to the OMAP;

Step 529, OMAP returns a resource release response to NMAP;

Step 530, NMAP returns a handover completion response to the terminal;

Step 531, after the terminal finishes switching from OMAP to NMAP, it can perform normal communication according to the existing technology;

Step 532: After the new home gateway address registration in step 520 is successful, the new home gateway initiates the banding up process of Mobile IP to the HA (home agent, home agent) in the mesh, according to the home agent HA of the terminal carried in the agent update message address, the new home gateway sends a BU (banding up, binding update) message to the HA, and the banding up message needs to carry the IP address of the original home gateway, the original home gateway port assigned to the terminal, and the IP of the new home gateway Address, new home gateway port information assigned to the terminal;

Step 533, the HA receives the BU message, and saves the corresponding relationship between <original home gateway IP: original home gateway port> and <new home gateway IP: new home gateway port>;

Step 534, HA returns confirmation (back) message to new home gateway;

Step 535. Afterwards, the HA receives the data packet sent to <original home gateway IP: original home gateway port> and forwards it to <new home gateway IP: new home gateway port>, so as to realize the packet sent to <original home gateway IP : The message of the original home gateway port> is forwarded to <new home gateway IP: new home gateway port>;

Among them, when the AT device establishes the address translation relationship, since the gateway may not have an IP address, the IP address of the AT device itself and the port number port can be used to establish the address translation relationship. At this time, the banding up message carries <original AT device IP: original AT device port> and <new AT device IP: new AT device port>, so as to forward the message sent to <original AT device IP: original AT device port> to <new AT device IP: new AT device port> >, to ensure that the terminal can correctly receive the data packets sent from the external network to the terminal.

In this embodiment, because the home gateway of the terminal corresponding to OMAP and NMAP changes, there is a situation that OMAP and NMAP cannot communicate directly at the second layer. At this time, the communication between OMAP and NMAP is based on the intercommunication of the IP layer. Take NMAP as an example: the source IP address uses the IP address of OMAP. This IP address is the unified IP address of the mesh network. When the data packet passes through the OGW, this IP address will be changed to the OGW address, and the source port is set based on the AT mechanism. It is the Port registered in OGW for OMAP, that is, according to the conversion relationship between <OMAP MAC address: port> and <gateway node IP address: gateway port> saved in the AT device, the <OMAP MAC address in the data packet: port> is converted to the corresponding <IP address of the gateway node: gateway port>; the destination IP address uses the IP address of the NGW, and the destination port is set to the port registered in the NGW by NMAP based on the AT mechanism. Sending a message from NMAP to OMAP is similar and will not be repeated here.

In this embodiment, when the terminal is switching, the original MAP carries <terminal MAC address: terminal port> in the switching request and sends it to the new MAP, and the new MAP saves the <terminal MAC address: terminal port>. The <terminal MAC address: terminal port> communicates with the external network through the new home gateway of the terminal. During the switching process (step 216-step 220) of the terminal, the MAP does not need to reconfigure the IP address for the terminal, and the terminal directly uses the whole network The unified IP keeps the IP address of the terminal unchanged before and after switching, thereby eliminating the problem of increased switching delay caused by reconfiguring the IP address, reducing the switching delay, and improving network service performance. Moreover, since the new MAP and the original MAP belong to different gateways, the new MAP further establishes the address translation relationship of the terminal on the new home gateway, and performs a banding up process with the HA to ensure that the switched terminal can correctly send and receive messages related to the external network. packets, to communicate with the external network.

Embodiment six

As shown in accompanying drawing 6, present embodiment provides a kind of mesh network system, and this system comprises: STA61 (station, terminal equipment) with wireless access function, MP62 (meshpoint, mesh point) and MAP63 ( Mesh access point, mesh access point), the interface device GW64 (gateway, gateway) between the mesh network and the Internet and other networks, and the HA65 (home agent, home agent) used to support the MIP (mobile IP, mobile IP) protocol in the mesh network ).

The terminal STA61 accesses the mesh network through the mesh access point MAP63 to communicate. When the terminal needs to communicate with devices outside the mesh network, the gateway GW64 forwards the data exchange between the terminal STA61 and the devices outside the mesh network.

The functional modules of the MAP63 device are described in Figure 7, and the MAP63 includes:

A receiving module 71, configured to receive data packets from STA, GW, other MAP or MP devices;

Sending module 72, for sending the data packet sent to STA, GW, other MAP or MP equipment;

MAC processing module 73, for the packet received according to receiving module 71, if it is DHCP (Dynamic Host Configuration Protocol, dynamic host configuration protocol) related packet, it is sent to IP address assignment module 74; If it is ARP (Address Resolution Protocol, Address Resolution Protocol) relevant data packets, send it to ARP processing module 75; If it is other data packets, then judge whether data packets are sent to this equipment, if not, then send it according to the route information of MAC To the sending module, if it is sent to this equipment, then the MAC processing module 73 sends the data packet to the corresponding processing module for processing; the MAC processing module 73 receives the data packet sent by the IP address assignment module 74, the ARP processing module 75, according to The routing information of MAC sends it to sending module 72 to send out;

The IP address distribution module 74 is used to receive the DHCP-related data packets sent by the MAC processing module 73, configure the default unified IP address of the entire mesh network that is preset for the corresponding DHCP response message, and send the DHCP response message To the MAC processing module 73; when the received DHCP-related packet is a request from the terminal to find a DHCPDiscover message of the DHCP server, send the DHCP offer information to the MAC processing module 73, and further send the terminal via the sending module 72 by the MAC processing module 73 , the DHCP offer includes a unified IP address for the entire network, and its lease period is permanently valid;

The ARP processing module 75 is configured to receive the ARP request packet sent by the MAC processing module 73 , resolve the IP address of the ARP request into the MAC address of the GW, and send the ARP response to the MAC processing module 73 .

The functional modules of the gateway device 64 are as shown in Figure 8, and the gateway 64 includes:

The second receiving module 81 is configured to receive data packets from STA, GW, other MAP or MP devices;

The second sending module 82 is used to send data packets sent to STA, GW, other MAP or MP devices;

The second MAC processing module 83 is used to receive the data packet sent by the second receiving module 81, if it is to register or delete the data packet of the conversion relationship between <terminal MAC address: port> and <gateway node IP address: port> , then the packet is sent to the address translation module 84; for other packets, it is sent to the IP processing module 85; the packet sent by the address translation module 84 and the IP processing module 85 is sent to the second sending module 82 ;

The address conversion module 84 is used to receive the data packet sent by the MAC processing module 83 to register or delete the conversion relationship between <terminal MAC address: port> and <gateway node's IP address: port>, and return to the corresponding packet after corresponding processing The confirmation message is given to the MAC processing module 83; the receiving IP processing module 85 inquires about the request of the conversion relationship between <the MAC address of the terminal: port> and <the IP address of the gateway node: port>, and responds to the IP processing module 85 according to the query result; receiving MAC processing module 83 deletes <terminal's MAC address: port> and <gateway node's IP address: port> request of conversion relation, returns corresponding confirmation message to MAC processing module 83 after deleting; Save and maintain all to this gateway equipment Registered conversion relationship between <terminal MAC address: port> and <gateway node IP address: port>; when receiving the registered conversion relationship between <terminal MAC address: port> and <gateway node IP address: port> When a request is made, assign a port of the gateway to the registered terminal, add the conversion relationship between <terminal MAC address: port> and <gateway node IP address: port> into the conversion relationship table, and return the result of the addition; when the query is received When requesting the conversion relationship between <terminal MAC address: port> and <gateway node IP address: port>, query the conversion relationship table and return the corresponding query result; when receiving the request to delete <terminal MAC address: port> and < IP address of the gateway node: When requesting the conversion relationship of port>, delete the corresponding entry in the conversion relationship table and return the deleted result; support Mobile IP protocol;

The IP processing module 85 is used to receive the packet sent by the MAC processing module 83, and inquires the conversion relationship between the corresponding <terminal MAC address: port> and <the gateway node's IP address: port> to the address translation module 81, according to the query The result is sent back to the MAC processing module 83 after making corresponding processing; Wherein, corresponding processing can be, receive the data packet that is sent by the MAC processing module 83, if the source IP address of data packet is the unified IP address of mesh whole network, then According to the <source MAC address of data packet: port> to address conversion module 84 inquiry <terminal MAC address: port> and <the IP address of gateway node: port> conversion relation, source IP address and port according to the result of inquiry Change it to the IP address and port of the device itself (that is, the gateway node), and send it to the destination device, or, if the destination address of the data packet is the IP address of the device itself, then according to the <destination IP address: port> information of the data packet to the address The conversion module 84 inquires about the conversion relationship between <the MAC address of the terminal: port> and <the IP address of the gateway node: port>, changes the destination IP address and port into the unified IP address and port of the whole network according to the result of the query, and The destination MAC address is set to the queried terminal MAC address and sent to the destination terminal.

Embodiment seven

This embodiment provides a mesh network system, as shown in Figure 9, the system includes: a terminal 91 for initial access, a terminal 96 switched from MAP95 to MAP92, mesh access points MAP92, MAP95, gateway 93, address translation device 94;

Terminal 91 is used to send a DHCP discovery (DHCP discover) message to MAP92, which carries the address of terminal 91 and the port number (expressed with port1) of terminal 91 in the DHCP discovery message; receives the DHCP carrying the uniform IP address of the mesh network sent by MAP92 Provide (DHCP offer) message;

MAP92 is used to receive the DHCP discovery message sent by the terminal 91, and send a DHCP offer message to the terminal 92, wherein the DHCP offer message carries the unified IP address of the mesh network; and sends an agent update message to the gateway 93, wherein the agent update message carries The address of terminal 91, the port number port1, and the address of MAP92;

Gateway 93 is used to receive the agent update message sent by MAP92, save the agent information of the terminal (the correspondence between <the address of terminal 91: port1> and the address of MAP92) in the agent information table, and return the agent update success message to MAP92 ; Send an address registration message to the address conversion device 94, the address registration message carries <address of the terminal 91: port1>;

The address conversion device 94 is used to receive the address registration message sent by the gateway 93, and distributes a port number port2 for the terminal 91. The port number port2 belongs to the IP address of the gateway 93 or the address conversion device 94, and establishes the address of the terminal 91: port1 > Address translation relationship with <IP address of gateway 93: port2> (or <IP address of address translation device 94: port2>); return address registration success message to gateway 93.

Wherein, as shown in FIG. 10 , MAP92 may include: a first receiving module 921, configured to receive a DHCP discovery message sent by terminal 91 or a fast switching request sent by other MAP95 or a switching completion request sent by terminal 96, wherein the DHCP discovery message The message includes the MAC address of the terminal 91 and the port number port1 of the terminal 91, and the fast switching request includes the MAC address of the terminal 96 and the port number port6 of the terminal 96 which will be switched from other MAP95 to the MAP92, and the switching completion request includes the port number port6 of the terminal 96. The MAC address and the port number port6 of the terminal 96; the first processing module 922 is configured to construct a DHCP offer message and an agent update message according to the DHCP discovery message received by the first receiving module 921, wherein the DHCP offer message includes a network-wide unified IP address, the proxy update message includes the MAC address of the terminal 91, the port number port1 of the terminal 91 and the MAC address of the MAP92; the first sending module 923 is used to send the DHCP provided by the first processing module 922 to the terminal 91 and provide a message to the terminal 91. The gateway 93 sends the proxy update message constructed by the first processing module 922 . The first processing module 922 may further include: a DHCP unit 9221, configured to construct a DHCP offer message and an agent update message according to the DHCP discovery message received by the first receiving module 921, and trigger the first sending module 923 to send the constructed DHCP offer message and An agent update message, wherein the agent update message includes the MAC address of the terminal 91, the port number port1 of the terminal 91, and the MAC address of the MAP92; the fast switching unit 9222 is configured to construct a proxy according to the fast switching request received by the first receiving module 921 An update message, wherein the proxy update message includes the MAC address of the terminal 96, the port number port6 of the terminal 96, and the MAC address of the MAP92. Alternatively, the first processing module 922 may further include: a DHCP unit 9221 configured to construct a DHCP offer message and an agent update message according to the DHCP discovery message received by the first receiving module 921, and trigger the first sending module 923 to send the constructed DHCP offer message. message and an agent update message, wherein the agent update message includes the MAC address of the terminal 91, the port number port1 of the terminal 91, and the MAC address of the MAP92; the switching completion unit 9223 is configured to receive the switching completion request according to the first receiving module 921, A proxy update message is constructed, wherein the proxy update message includes the MAC address of the terminal 96, the port number port6 of the terminal 96, and the MAC address of the MAP92.

Wherein, as shown in FIG. 11 , the gateway 93 may include: a second receiving module 931, configured to receive the agent update message sent by the MAP92; an agent information module 932, configured to receive the agent update message according to the second receiving module 931, in the agent The corresponding relationship between <the MAC address of the terminal 91: port1> (or <the MAC address of the terminal 96: port6>) and the MAC address of the MAP92 is stored in the information table; the second sending module 933 is used to send the address registration to the address translation device 94 message, the address registration message includes <MAC address of the terminal 91: port1> (or <MAC address of the terminal 96: port6>), or, send an agent update success message to the first receiving module 921. The proxy update module 932 may further include: a proxy table unit 9321 for storing proxy information; an update judging unit 9322 for judging whether there is proxy information of the terminal 91 in the stored proxy information according to the proxy information stored in the proxy table unit 9321 , if the proxy information of the terminal 91 already exists, then the original proxy information of the terminal 91 in the proxy table unit 9321 is replaced by <the MAC address of the terminal 91: port1> (or < The MAC address of terminal 96: port6>) and the corresponding relationship of the MAC address of MAP92, and trigger the second sending module 933 to send agent update success message to the first receiving module 921, if there is no agent information of terminal 91, then in agent table The proxy information of the terminal 91 is added in the unit 9321, that is, <the MAC address of the terminal 91: port1> (or <the MAC address of the terminal 96: port6>) and the MAC address of the MAP92 in the proxy update message newly received by the second receiving module 931 and trigger the second sending module 933 to send a proxy update success message to the first receiving module 921 and send an address registration message to the address translation device 94 .

Wherein, as shown in FIG. 12 , the address conversion device 94 may include: a third receiving module 941, configured to receive the address registration message sent by the gateway 93; an address conversion module 942, configured to receive the address registration message according to the third receiving module 941 , establish address translation between <the MAC address of the terminal 91: port1> (or <the MAC address of the terminal 96: port6>) and <the IP address of the gateway 93: port2> (or <the IP address of the address translation device 94: port2>) relationship, and save the established address translation relationship in the address translation relationship table; the third sending module 943 is configured to send an address registration success message to the second receiving module 931 .

In the system of this embodiment, the home agent HA97 may further be included, which is used to receive the BU (banding up, binding update) message sent by the address translation device 94, and the BU message carries the IP address of the original home gateway of the switching terminal 96 , the original home gateway port assigned to the terminal 96, and the IP address of the new home gateway of the terminal 96, the new home gateway port information assigned to the terminal 96, <the original home gateway IP of the terminal 96: the original home gateway port of the terminal 96> For the corresponding relationship with <the new home gateway IP of the terminal 96:the new home gateway port of the terminal 96>, a confirmation message is returned to the address translation device 94 .

In this embodiment, when the terminal is switching, the original MAP carries <terminal MAC address: terminal port> in the fast handover request and sends it to the new MAP, and the new MAP saves the <terminal MAC address: terminal port>, and then can According to the <terminal MAC address: terminal port>, the terminal communicates with the external network through the new home gateway of the terminal. During the handover process (step 216-step 220), the MAP does not need to reconfigure the IP address for the terminal, and the terminal directly adopts the full The unified IP of the network makes the IP address of the terminal unchanged before and after switching, thereby eliminating the problem of increased switching delay caused by reconfiguring the IP address, reducing the switching delay, and improving the service performance of the network. Moreover, since the new MAP and the original MAP belong to different gateways, the new MAP further establishes the address translation relationship of the terminal on the new home gateway, and performs a banding up process with the HA to ensure that the switched terminal can correctly send and receive messages related to the external network. packets, to communicate with the external network.

In this embodiment, the address translation device 94 is a logical entity, and may be specifically implemented as a module of the gateway 93 .

In this embodiment, when the terminal accesses the network, the MAP carries the uniform IP address of the entire network in the DHCP offer message and configures it for the terminal, and then the terminal uses this IP address to communicate with the external network. The network is unified, so the terminal does not need to redistribute the IP address during the switching process, thereby eliminating the problem of increased switching delay caused by reconfiguring the IP address, reducing the switching delay, and improving the service performance of the network.

In each embodiment of the present invention, since the terminal is configured with a unified IP of the entire network, the terminal does not need to reset the IP of the terminal when switching in the mesh network, which reduces the switching delay and improves the service performance of the network. Above all, the technical solution of each embodiment of the present invention can be well compatible with the existing network, greatly reducing the cost of network upgrade.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented through computer programs to instruct related hardware, and the programs can be stored in a computer-readable storage medium. During execution, it may include the processes of the embodiments of the above-mentioned methods. Wherein, the storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM) or a random access memory (Random Access Memory, RAM), etc.

In a word, the above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (18)

1. A method for terminal access in a mesh network, characterized in that, comprising: The mesh access point establishes an association with the access terminal; The mesh access point receives the first message sent by the terminal, where the first message includes a terminal address and a port number of the terminal; The mesh access point sends a second message to the terminal, where the second message includes a network-wide unified IP address, for the terminal to use the network-wide unified IP address to communicate with an external network. 2. The method according to claim 1, wherein the first message is a DHCP discovery message, the second message is a DHCP provision message, and the mesh access point receives the DHCP discovery message , carrying the unified IP address of the entire network in the DHCP offer message and returning it to the terminal. 3. The method according to claim 1 or 2, wherein the association is a MAC communication link, and the terminal address is the MAC address of the terminal, and the method further comprises: The mesh access point obtains the MAC address of the terminal and the port number of the terminal in the first message; Select a gateway for the terminal as the home gateway of the terminal; sending a proxy update message to the home gateway, where the proxy update message includes the MAC address of the terminal and the port number of the terminal. 4. The method of claim 3, further comprising: The home gateway saves the proxy information of the terminal according to the proxy update message, where the proxy information is the corresponding relationship between the terminal and the mesh node; The home gateway assigns a gateway port number to the terminal, and establishes an address translation correspondence, wherein the address translation correspondence is the corresponding translation between the terminal's MAC address and the terminal's port number, and the gateway's IP address and gateway port number relation. 5. a method for mesh network agent update, it is characterized in that, the terminal in the network is configured as the unified IP address of the whole network, and described method comprises: The target mesh access point receives a first message, wherein the first message includes a terminal address and a port number of the terminal, and the target mesh access point is a mesh access point to which the terminal will switch; The target mesh access point carries the terminal address and the port number of the terminal in the first message in a proxy update message, and sends a proxy update message to the gateway; wherein, the proxy update message is used for the gateway to perform proxy renew. 6. The method according to claim 5, wherein the terminal address is a MAC address of the terminal, and the IP address of the terminal is a unified IP address of the entire network. 7. The method according to claim 6, wherein the first message is a fast handover request message sent by the original mesh access point before the terminal handover, and the handover request message includes the terminal's MAC address, The port number of the terminal and the resource information to be applied for when the terminal is switched, the method also includes: The target mesh access point performs resource reservation according to the resource information that the terminal needs to apply for when switching. 8. The method according to claim 6, wherein the first message is a handover completion request message sent by the terminal, and the handover completion request message includes the MAC address of the terminal and the port number of the terminal, and in the Before the target mesh access point receives the first message, the method further includes: The target mesh access point establishes an association with the terminal, and the association is a MAC layer communication link for transmitting the handover completion request message. 9. The method according to claim 7 or 8, further comprising: If both the target mesh access point after the terminal is switched and the original mesh access point before the switch have reachable routes to the same gateway, the gateway updates the proxy information of the terminal according to the proxy update message, and transfers the The corresponding relationship between the terminal and the original mesh access node is replaced by the corresponding relationship between the terminal and the target mesh access node; or, If the target mesh access point after the terminal is switched and the original mesh access point before the switch do not have a reachable route to the same gateway, the gateway updates the proxy information of the terminal according to the proxy update message, and saves all The corresponding relationship between the terminal and the target mesh access node, and assign a gateway port number to the terminal, and establish an address translation correspondence, wherein the address translation correspondence is the MAC address of the terminal and the port number of the terminal and The corresponding conversion relationship between the IP address of the gateway and the port number of the gateway. 10. The method of claim 9, further comprising: The original mesh access point before the handover determines a candidate mesh access point as the target mesh access point according to the candidate mesh access point information collected by the terminal; wherein, the original mesh access point preferably selects , and the candidate mesh access point that has a reachable route to the same gateway as the original mesh access point is the target access point. 11. A mesh gateway node, characterized in that the node comprises: The receiving module is configured to receive an agent update message sent by the mesh access point; wherein, the agent update message includes the MAC address of the terminal and the port number of the terminal, and the terminal is configured as a unified IP address throughout the network; An agent information module, configured to save the corresponding relationship between the terminal and the mesh access point as the agent information of the terminal according to the agent update message received by the receiving module; A sending module, configured to send an agent update success message to the mesh access point after the agent information module saves the agent information of the terminal. 12. The node according to claim 11, wherein the agent information module comprises: Proxy table unit, used to store proxy information; The update judging unit is used for judging whether there is proxy information of the terminal in the previously saved proxy information according to the proxy information stored in the proxy table unit, and if the proxy information of the terminal already exists, the proxy table unit is updated to The original proxy information of the terminal is replaced with the corresponding relationship between the terminal and the mesh access point. If there is no proxy information of the terminal, add the terminal and the mesh access point in the proxy table. Correspondence between entry points. 13. The node according to claim 12, wherein the node further comprises: The address translation module is configured to assign a gateway port number to the terminal and establish an address translation correspondence when the update judging unit judges that the proxy information of the terminal does not exist in the previously stored proxy information, wherein, The address translation correspondence is a correspondence translation relationship between the MAC address of the terminal and the port number of the terminal, and the IP address of the gateway and the port number of the gateway. 14. A mesh access point, characterized in that the access point comprises: A receiving module, configured to receive a first message, wherein the first message includes the MAC address of the terminal and the port number of the terminal, and the terminal is configured as a unified IP address throughout the network; A processing module, configured to construct a proxy update message according to the first message received by the receiving module, where the proxy update message includes the MAC address of the terminal and the port number of the terminal; The sending module is configured to send the proxy update message constructed by the processing module to the gateway; wherein the proxy update message is used for the gateway to perform proxy update. 15. The access point according to claim 14, wherein the processing module comprises: The first message processing unit is configured to construct a DHCP offer message and an agent update message if the first message received by the receiving module is a DHCP discovery message sent by the terminal; wherein, the DHCP offer message includes a unified network-wide IP address; The second message processing unit is configured to if the first message received by the receiving module is a fast handover request sent by another mesh access point, or if the first message received by the receiving module is a handover completion sent by the terminal When requested, the build agent updates the message; The sending module is further configured to send a DHCP offer message to the terminal, and the DHCP offer message is used for the terminal to communicate with an external network using a unified IP address of the whole network. 16. A mesh network system is characterized in that, the terminal in the network is configured as a unified IP address of the whole network, and the system comprises: The mesh access point is configured to receive a first message, wherein the first message includes the MAC address of the terminal and the port number of the terminal; construct an agent update message according to the received first message, wherein the agent update The message includes the MAC address of the terminal and the port number of the terminal; sending the constructed proxy update message to the gateway; a gateway, configured to receive an agent update message sent by the mesh access point, wherein the agent update message includes the MAC address of the terminal and the port number of the terminal; according to the received agent update message, store the terminal and the mesh The corresponding relationship of the access point is the agent information of the terminal; sending an agent update success message to the mesh access point. 17. The system of claim 16, further comprising: The address translation device is configured to receive the address registration message sent by the gateway, wherein the address registration message includes the MAC address of the terminal and the port number of the terminal; according to the received address registration message, allocate a gateway port number to The terminal establishes an address translation relationship between the MAC address of the terminal, the port number of the terminal, the IP address of the gateway, and the port number of the gateway; and sends an address registration success message to the gateway. 18. The system of claim 16, wherein the gateway comprises: A receiving module, configured to receive an agent update message sent by the mesh access point; An agent information module, configured to save the corresponding relationship between the terminal and the mesh access point as the agent information of the terminal according to the agent update message received by the receiving module; The address translation module is configured to assign a gateway port number to the terminal according to the agent update message received by the receiving module, and establish an address translation correspondence, wherein the address translation correspondence is the MAC address of the terminal and the port of the terminal number, the corresponding conversion relationship between the IP address of the gateway and the port number of the gateway; A sending module, configured to send an agent update success message to the mesh access point after the agent information module saves the agent information of the terminal.

Images