CN112105095B - EasyMesh network multi-Controller implementation method and system - Google Patents
EasyMesh network multi-Controller implementation method and system Download PDFInfo
- Publication number
- CN112105095B CN112105095B CN202010882184.4A CN202010882184A CN112105095B CN 112105095 B CN112105095 B CN 112105095B CN 202010882184 A CN202010882184 A CN 202010882184A CN 112105095 B CN112105095 B CN 112105095B
- Authority
- CN
- China
- Prior art keywords
- controller
- network
- easymesh
- domain
- assi
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/03—Protocol definition or specification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
Abstract
The invention discloses an easy mesh network multi-Controller implementation method, which comprises the following steps: in an EasyMesh network, expanding the role of the existing EasyMesh protocol Controller, and on the premise of the role of the existing Controller-AP, adding the role of the Assi-Controller-AP; the Controller-AP and the asi-Controller-AP have equal status, and respectively control the Agent-AP and the Station accessed to the own domain; establishing a special synchronous management channel with the same VLAN between the Controller-AP and the Assi-Controller-AP, wherein the special synchronous management channel is isolated from the data service; the entire multicontroller EasyMesh network has the same SSID and password. The technical scheme of the invention can greatly improve the flexibility of the EasyMesh network topology, reduce the problem of multistage cascade of the EasyMesh tree network, effectively improve and expand the exit path of the user and realize the load balance of Internet access of the user. The invention also provides a corresponding EasyMesh network multi-Controller system.
Description
Technical Field
The invention belongs to the technical field of wireless networking, and particularly relates to an easy mesh network multi-Controller implementation method and system.
Background
Various wireless terminals (such as computers, tablets, mobile phones, set-top boxes and other devices, hereinafter referred to as states) inside the home network access the home network through a user side WLAN interface of the router and wired terminals through a user side LAN interface of the router, and access an external network through a home gateway. A plurality of APs can exist in the same local area network at the same time, and wider wireless and wired coverage ranges are provided for families. Through distributed networking, the requirements of broadband internet access, video entertainment and the like of home users are met, and the problems of Wi-Fi full-house coverage, high-speed connection and seamless roaming are solved.
The current home wireless networking full coverage and seamless roaming are mainly realized by the MAP (Multiple Access Point) easy mesh technology. The EasyMesh protocol defines that only one Controller exists in an EasyMesh network, and the network topology is a tree structure. As shown in fig. 1, in some large house type villas or multi-storey house environments, a single Controller is very easy to form a multi-level cascade of EasyMesh tree networks. In the scenario of fig. 1, a WiFi signal path window propagates a WiFi signal propagation path: controller AP1 Agent AP2 Agent AP 3; the Controller AP1 Agent AP4 Agent AP5 forms a 3-stage cascade. When the cascade of the tree structure is more than 2-3 levels, the network bandwidth and the time delay performance are greatly reduced; this results in a poor user experience for Station in a multi-stage cascade.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides an easy mesh network multi-Controller implementation scheme, which expands the roles of easy mesh members and adds a multi-Controller implementation mechanism to the existing easy mesh protocol, so that the flexibility of the easy mesh network topology can be greatly improved, the problem of tree-shaped network multi-level cascade is reduced, the user experience can be greatly improved, and the easy mesh network can be expanded to adapt to more application scenes.
To achieve the above object, according to an aspect of the present invention, there is provided an EasyMesh network multicontroller implementation method, including:
in an EasyMesh network, expanding the role of the existing EasyMesh protocol Controller, and on the premise of the role of the existing Controller-AP, adding the role of the Assi-Controller-AP; the Controller-AP and the asi-Controller-AP have equal status, and respectively control the Agent-AP and the Station accessed to the own domain;
establishing a special synchronous management channel with the same VLAN between the Controller-AP and the Assi-Controller-AP, wherein the special synchronous management channel is isolated from the data service;
the entire multicontroller EasyMesh network has the same SSID and password.
In an embodiment of the present invention, the Controller role is managed by a multicast-based advertisement negotiation protocol: the controllers in the EasyMesh network are enabled through an out-of-band mechanism, the notification negotiation protocol notifies the controllers in a special synchronous management channel period, receives the notifications of other controllers to determine multiple controllers in the current EasyMesh network, and negotiates to determine that the management IP of each Controller is in the same network segment according to the notification information.
In one embodiment of the invention, the method further comprises an EasyMesh network Controller role discovery mechanism extension, and the Controller role discovery mechanism extension is realized by the following three tables:
responding AP-Autoconfiguration Search message flow expansion processing to a Controller of an original EasyMesh protocol, creating and maintaining a Controller domain table, an asi-Controller domain table and a Station table, and coordinating synchronous cooperation states among all Controller roles according to the tables; so as to control the actions of Agent-AP and Station in the response Controller domain and the Assi-Controller domain.
In one embodiment of the invention, the method further comprises a Controller domain, and the asi-Controller domain form member maintenance criteria: the member joining follows the first entering criterion, and the same member can only belong to a single domain in the same time period; member message processing follows domain-wide restrictions.
In one embodiment of the present invention, the method further comprises: when any Controller domain or the asi-Controller domain has Station access or roaming access, IP address pool synchronization is carried out through a special synchronous management channel, Controller-AP and asi-Controller-AP, and further synchronization of all network equipment ARP tables and FDB tables of the domain is completed.
In one embodiment of the present invention, the method further comprises: all the service flows of the Station accessed or roamed into any Controller domain or Assi-Controller domain are all uplink from the WAN port of the Controller-AP or Assi-Controller-AP to the local gateway for accessing Internet.
In an embodiment of the present invention, the establishing, between the Controller-AP and the asi-Controller-AP, a dedicated synchronization management channel related to the uplink gateway includes:
the Controller-AP and the Assi-Controller-AP are accessed to the same uplink gateway LAN side through wires;
the wired VLAN implementation of the special synchronous management channel is as follows: and establishing an uplink wired VLAN subinterface of the Controller-AP and the asi-Controller-AP, and establishing a VLAN subinterface with an uplink gateway LAN side which is correspondingly connected with a wire.
In an embodiment of the present invention, the establishing of the wireless dedicated synchronization management channel unrelated to the uplink gateway between the Controller-AP and the asi-Controller-AP includes:
the realization of the wireless VLAN of the special synchronous management channel comprises the following steps: a wireless VLAN sub-interface between a Controller-AP and an Assi-Controller-AP is created, one of which is used as ext _ AP and the other is used as ext _ sta.
In an embodiment of the present invention, the establishing of the wired dedicated synchronization management channel between the Controller-AP and the asi-Controller-AP, which is unrelated to the uplink gateway, includes:
the wired VLAN of the special synchronous management channel is realized as follows: and establishing wired VLAN sub-interfaces at the LAN sides of the Controller-AP and the asi-Controller-AP, and establishing a wired directly-connected VLAN special synchronous management channel.
In an embodiment of the present invention, the process of establishing the Controller role management and the dedicated synchronization management channel includes:
s801, enabling a Controller role function in an EasyMesh network through an out-of-band mechanism, and starting a multicast-based notification negotiation protocol;
s802, the notification negotiation protocol periodically notifies the Controller role existence message in a special synchronous management channel, wherein the message comprises a service set identifier SSID, a basic service set identifier BSSID, an operating time uptime and a management IP;
s803, receiving other Controller role announcements; to determine the existence of multiple Controller roles in the current EasyMesh network; and determining that the management IP of each Controller role is in the same network segment according to the notification information negotiation.
In an embodiment of the present invention, the EasyMesh network Controller discovery mechanism extension includes:
s901, the Controller role receives the AP-Autoconfiguration Search message;
s902, judging the condition of a multi-Controller EasyMesh network;
s903, a notification Controller-Cooperate module;
s904, the Controller-Cooperate module creates and maintains a Controller domain table, an asi-Controller domain table and a Station table, and coordinates a synchronous cooperation state among the Controller roles according to the tables; so as to control the actions of Agent-AP and Station in the response Controller domain and the Assi-Controller domain.
In an embodiment of the present invention, a process of synchronizing an FDB table, an ARP table, and a Controller IP address pool of each networking device in an EasyMesh network includes:
s1001, switching the Station access or roaming into any Controller domain or Assi-Controller domain;
s1002, informing a Controller-Cooperate of the role of the Controller-AP or the Assi-Controller-AP;
and S1003, the Controller-Cooperate module cooperates with the Controller-AP and the Assi-Controller-AP to carry out IP address pool synchronization through a special synchronous management channel, and further, the synchronization of the FDB table and the ARP table of all networking equipment in the home domain is completed.
According to another aspect of the present invention, there is also provided an EasyMesh network multicontroller system, comprising a Controller-AP, an asi-Controller-AP, an Agent-AP, and a Station, wherein:
in an EasyMesh network, expanding the role of the existing EasyMesh protocol Controller, and on the premise of the role of the existing Controller-AP, adding the role of the Assi-Controller-AP; the Controller-AP and the asi-Controller-AP have equal status, and respectively control the Agent-AP and the Station accessed to the own domain;
establishing a special synchronous management channel between the Controller-AP and the Assi-Controller-AP, wherein the special synchronous management channel is isolated from the data service;
the entire multicontroller EasyMesh network has the same SSID and password.
According to another aspect of the invention, the invention also provides an EasyMesh network multi-Controller system constructed by the EasyMesh network multi-Controller implementation method.
Generally, compared with the prior art, the technical scheme of the invention has the following beneficial effects:
(1) in the application scene of the home environment of a large-house villa or a multi-storey foreign house, the flexibility of the EasyMesh network topology can be greatly improved;
(2) in the application scene of the home environment of a large-house villa or a multi-layer ocean house, the problem of multistage cascade of an EasyMesh tree network can be reduced, and the user experience can be greatly improved;
(3) in the application scene of a large-dwelling house type home environment with multiple operators accessing, the exit path of a user can be effectively improved and expanded, and the load balance of Internet accessing of the user is realized.
Drawings
FIG. 1 is a schematic diagram of an actual application scenario of a single Controller in an easy mesh network in a large dwelling size in the prior art;
FIG. 2 is a diagram of an actual application scenario of EasyMesh network multicontroller in a large dwelling size according to an embodiment of the present invention;
FIG. 3 is an exemplary diagram of an actual application scenario of EasyMesh network multicontroller multi-operator egress network in a large-dwelling size according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an EasyMesh network multicontroller topology according to an embodiment of the present invention;
FIG. 5 is an illustration of a channel configuration of a wired path related to an uplink gateway for establishing a dedicated information management between a Controller-AP and an asi-Controller-AP according to an embodiment of the present invention;
FIG. 6 is an explanatory diagram of channel configuration of a wireless path, independent of an uplink gateway, for establishing a dedicated information management between a Controller-AP and an asi-Controller-AP according to an embodiment of the present invention;
FIG. 7 is an illustration of channel configuration of an independent wired path independent of an uplink gateway for establishing a dedicated information management between Controller-AP and Assi-Controller-AP according to an embodiment of the present invention;
FIG. 8 is a flow chart illustrating a Controller role management process in an embodiment of the present invention;
FIG. 9 is a schematic flow chart of an EasyMesh network Controller role discovery mechanism extension in the embodiment of the present invention;
FIG. 10 is a schematic diagram illustrating a flow of synchronizing the IP address pools of the FDB table, the ARP table and the Controller of each networking device in the embodiment of the present invention;
FIG. 11 is a diagram illustrating a Controller domain table, an Assi-Controller domain table, and a Station representation of a multi-Controller EasyMesh network in an embodiment of the present invention;
fig. 12 is a schematic structural diagram of an easy mesh network multi-Controller implementation system in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. In addition, the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
The technical problem to be solved by the invention is as follows: the current EasyMesh protocol defines that only one Controller exists in an EasyMesh network, and the network topology is a tree structure. In the home environment of some large-house villas or multi-storey foreign houses, a single Controller is easy to form the multistage cascade of the easy mesh tree network. When the cascade of the tree structure is more than 2-3 levels, the network bandwidth and the time delay performance are greatly reduced; this results in a poor user experience for Station in a multi-stage cascade.
In order to solve the technical problem, the invention adopts the following technical scheme:
as shown in fig. 2, expanding the role of the easy mesh member and adding a multi-Controller implementation mechanism to the existing easy mesh protocol can greatly improve the flexibility of the easy mesh network topology, reduce the problem of tree network multistage cascade, greatly improve the user experience, and expand the easy mesh network to adapt to more application scenarios. In fig. 3, a scenario is shown in which the extension supports that the Controller-AP and the asi-Controller-AP access to two different operator gateways respectively.
Example 1
As shown in FIG. 4, the present invention provides an easy mesh network multicontroller implementation scheme (the following easy mesh networking devices are Controller-AP, Assi-Controller-AP and Agent-AP respectively; the entire multicontroller easy mesh network has the same SSID and password, and Station can seamlessly roam based on 802.11k/v/r in multicontroller easy mesh network), including:
in an EasyMesh network, expanding the role of the existing EasyMesh protocol Controller, and on the premise of the role of the existing Controller-AP, adding the role of the Assi-Controller-AP; the Controller-AP and the asi-Controller-AP have equal status and respectively control the Agent-AP and the Station accessed to the own domain.
Further, a special synchronous management channel is established between the Controller-AP and the Assi-Controller-AP: the special synchronous management channel is isolated from data services (WiFi and uplink services) (for example, the special VLAN channel, VLANID 3210, is established on the LAN side of the uplink gateway by matching with the uplink gateway, and eth0:3210 logical interface (note: eth0 is the uplink interface of Controller-AP and Assi-Controller-AP) is added on the WAN side of the Controller-AP and Assi-Controller-AP and belongs to VLAN 3210); in addition, a wireless special synchronous management channel for special information management (interaction, cooperation and synchronization) between the Controller-AP and the asi-Controller-AP can be established based on an independent WiFi logical interface. For example, creating a wl0:3210WiFi logical interface, setting Controller-AP as ext _ AP and Assi-Controller-AP as ext _ sta; or establishing a wl0:3211WiFi logical interface, setting Controller-AP as ext _ sta and asi-Controller-AP as ext _ AP. 3210, 3211 are different VLANs; ext _ AP and ext _ sta are WiFi logical interfaces in AP and STATION modes; wl0 is the WLAN interface of Controller AP, Assi-Controller-AP; in this way, the Controller AP and the Assi-Controller-AP are directly connected wirelessly. The two different special synchronous management channels are a wired channel and a wireless channel; the former is a wired dedicated synchronization management channel (there are 2 kinds of wired dedicated synchronization channels, here, Controller upstream wired, which are applicable only under access to the same upstream gateway LAN side, and the latter is a wireless dedicated synchronization management channel, in addition, an inter-Controller LAN side wired connection, which is applicable to access to the same/different upstream gateway LAN sides).
Further management (announcement, discovery, negotiation) of Controller-AP, asi-Controller-AP roles, via multicast-based announcement negotiation protocol: a Controller (no matter the Controller-AP or the asi-Controller-AP) in the EasyMesh network is enabled through an out-of-band mechanism (UI and other modes, such as a web user interface or a key mode configuration enable), and a notification negotiation protocol periodically notifies the Controller on a special synchronous management channel and receives other Controller notifications; to determine that a plurality of controllers exist in the current EasyMesh network; and according to the notification information negotiation, determining that the management IP of each Controller is in the same network segment (the management IP of the Controller-AP and the administration-Controller-AP are configured to be in the same network segment through a notification negotiation protocol based on multicast), and specifically, determining the management IP by the Controller started first in the EasyMesh network (determined according to the uptime time), namely, the Controller started first informs other controllers of the IP address of the Controller, and the other controllers set the IP of the Controller to be in the same network segment with the Controller started first.
Further, the EasyMesh network Controller role discovery mechanism is extended, and the Controller role discovery mechanism is realized by the following three tables: under the condition that the network is determined to be a multi-Controller network, responding to the AP-Autoconfiguration Search message flow expansion processing to a Controller of the original EasyMesh protocol, adding a Controller-Cooperate module as a cooperative management module, creating and maintaining a Controller domain table, an asi-Controller domain table and a Station table, and cooperating with the synchronous cooperation state among the controllers according to the tables; so as to control the actions of Agent-AP and Station in the response Controller domain and the Assi-Controller domain. These three tables are available in both the Controller and the asi-Controller: a Controller domain table, an asi-Controller domain table, a Station table; controller, Assi-Controller are called home domain, neighborhood, relative to each other.
Further, the Controller field, the asi-Controller field, form the member maintenance criteria: the member joining follows the first entering criterion, and the same member can only belong to a single domain in the same time period; member message processing strictly follows domain-wide restrictions.
Furthermore, when any Controller domain or asi-Controller domain has Station access or roaming access, the IP Address pool synchronization is performed through the dedicated synchronization management channel, Controller-AP and asi-Controller-AP, and further synchronization of all networking devices ARP (Address Resolution Protocol) table and FDB (Forwarding Data Base) table in the cost domain is completed. It should be noted that, the management IPs of all Controller-APs and the management IPs of the asi-Controller-AP are in the same network segment, and the IP address pools of the Controller-AP and the asi-Controller-AP are also in the same network segment, but the network segment of the management IP and the network segment of the address pool are different network segments.
Furthermore, all the traffic flows of the Station accessed or roamed into any Controller or asi-Controller domain are all uplink from the WAN port of the Controller-AP or asi-Controller-AP to the local gateway for accessing Internet.
Example 2
The embodiment of the invention provides a method for establishing a special synchronous management channel related to an uplink gateway between a Controller-AP and an asi-Controller-AP, which comprises the following steps:
the Controller-AP and the Assi-Controller-AP are accessed to the same uplink gateway LAN side through wires;
the wired VLAN implementation of the special synchronous management channel is as follows: and establishing an uplink wired VLAN subinterface of the Controller-AP and the asi-Controller-AP, and establishing a VLAN subinterface with an uplink gateway LAN side which is correspondingly connected with a wire.
Specifically, as shown in fig. 5, a schematic diagram of establishing a dedicated synchronization management channel (wired mode) between a Controller-AP and an asi-Controller-AP in an embodiment of the present invention includes:
s501, if the wireless local area network (WAN) side wired special synchronous management channel scene is matched with the uplink gateway to share the Controller-AP and the asi-Controller-AP;
for example, according to the actual use scene, WAN side cables which determine the use of Controller-AP and asi-Controller-AP are configured through a web user interface to be used as synchronous channels;
s502, if yes, a special VLAN channel is established on the upstream gateway LAN side, and a VLANID is set (for example, the VLANID is set to 3210 in the embodiment of the invention); on WAN side of Controller-AP and Assi-Controller-AP, eth0:3210 logic interface is added, belonging to VLAN3210, the special synchronous management channel interface is isolated from data service;
s503, adding the LAN port (i.e. LAN1/LAN2 in the figure, belonging to br user side bridge) connected with Controller-AP and Assi-Controller-AP at the LAN side of the uplink gateway into the VLAN, and accessing the WAN port of Controller-AP and Assi-Controller-AP to the two data ports at the LAN side of the uplink gateway;
the management information of S504, Controller-AP, Assi-Controller-AP flows away eth0:3210 logical interface, the original data traffic is eth0, Untag on Controller-AP, Assi-Controller-AP, Untag on LAN side of up gateway, PVID is the same as VLANID of WAN port of up gateway (for example, in the present invention, PVID is 10, in this example, this PVID is 10, WAN port of up gateway VLANID is 10, so as to ensure that the original data traffic directly passes through Internet on WAN port of up gateway in up gateway, and goes up to Internet through WAN side of up gateway, keeping the channel of on-line traffic unchanged.
The PVID is a Port-base VLAN ID in english, and is a VLAN ID indicating a Port in network communication, one Port may belong to a plurality of VLANs, but only one PVID may exist, and when a data packet of an unog header is received, a VLAN number indicated by the PVID is marked, and the data packet processing is performed according to the VLAN.
A physical Port can only have one PVID, and when a physical Port has one PVID, it must have a VID equal to the PVID, and on this VID, it must be an unogged Port.
The PVID is used for adding a TAG mark to a data frame when the switch receives the data frame which can accept Untagged from the outside, and the PVID does not play any role when the switch forwards data inside.
Example 3
The embodiment of the invention provides a method for establishing a wireless special synchronous management channel irrelevant to an uplink gateway between a Controller-AP and an asi-Controller-AP, which comprises the following steps:
the realization of the wireless VLAN of the special synchronous management channel comprises the following steps: a wireless VLAN sub-interface between a Controller-AP and an Assi-Controller-AP is created, one of which is used as ext _ AP and the other is used as ext _ sta.
Specifically, as shown in fig. 6, a schematic diagram of establishing a dedicated synchronization management channel (wireless mode) between a Controller-AP and an asi-Controller-AP, which is unrelated to an uplink gateway in the embodiment of the present invention includes:
s601, if the wireless special synchronous management channel scene uses Controller-AP and Assi-Controller-AP;
for example, according to the actual usage scenario, the wireless dedicated synchronization management channel for determining the usage of Controller-AP and asi-Controller-AP is configured through the web user interface
S602, if yes, establishing a special synchronous management channel for special information management between controllers on the basis of an independent WiFi logical interface on a Controller-AP and an asi-Controller-AP;
the ext _ AP and ext _ sta are wifi logical interfaces in AP and STATION modes; either the Controller (state mode) connected asi-Controller (AP mode) is a VLAN (e.g., 3210) or the Controller (AP mode) passively connected asi-Controller (state mode) is another VLAN (e.g., 3211) but one of these cases is used.
Regarding the determination of ext _ AP and ext _ sta, the Controller may first detect whether there is ext _ AP in ext _ sta mode, and if there is no timeout, it indicates that there is no other AP, and then operates in ext _ AP mode.
The management information of S603, Controller-AP and Assi-Controller-AP flows to wl0:3210/wl0:3211(ext _ AP/ext _ sta) WiFi logical interface, and the dedicated synchronous management channel is isolated from data service;
s604, the logic channel and VLAN that the data service walk are eth0, Untag on Controller-AP, Assi-Controller-AP, Untag on LAN side of up gateway, PVID is 10, and go up to Internet through WAN side of up gateway, keep the service channel of surfing the Net unchanged.
In addition, this kind of dedicated synchronization channel establishment scheme is also applicable to fig. 7, when Controller-AP and asi-Controller-AP access different uplink gateway LAN sides through wire, wireless VLAN sub-interfaces between Controller-AP and asi-Controller-AP are created, one of them is used as ext _ AP and one is used as ext _ sta, implementing its dedicated synchronization management channel.
Example 4
The embodiment of the invention provides a method for establishing a wired special synchronous management channel irrelevant to an uplink gateway between a Controller-AP and an asi-Controller-AP, which comprises the following steps:
the Controller-AP and the Assi-Controller-AP access different uplink gateway LAN sides through wires:
the wired VLAN of the special synchronous management channel is realized as follows: and establishing wired VLAN sub-interfaces at the LAN sides of the Controller-AP and the asi-Controller-AP, and establishing a wired directly-connected VLAN special synchronous management channel.
Specifically, as shown in fig. 7, a schematic diagram of establishing a dedicated synchronization management channel (wired mode) between a Controller-AP and an asi-Controller-AP, which is not related to an uplink gateway, in an embodiment of the present invention is shown in fig. 7;
s701, if the scene is an independent wired synchronous channel scene between a Controller-AP and an Assi-Controller-AP;
for example, according to the actual usage scenario, an independent wired synchronization channel determining the usage of the AP is configured through a web user interface;
s702, if yes, an eth1:3210 logical interface is established on the LAN side of the Controller-AP and the Assi-Controller-AP, and belongs to the VLAN 3210;
the management information of S703, Controller-AP, Assi-Controller-AP flows away eth1:3210 logical interface, the special synchronous management channel is isolated from the data service;
s704, the logic channel and VLAN where the data service goes are eth0, Untag on Controller-AP, Assi-Controller-AP, Untag on LAN side of different operator gateway, and go up to Internet through WAN side of different operator gateway, keeping the channel of the service on Internet unchanged.
In addition, the establishment scheme of the special synchronous channel is also suitable for the figure 6, wherein Controller-AP and Assi-Controller-AP are connected through a LAN side wire, an eth1:3210 logical interface is additionally established, and belongs to the VLAN3210, so that the special synchronous management channel is realized.
Example 5
Fig. 8 is a schematic flowchart of a process of establishing a Controller management channel and a dedicated synchronization management channel in an embodiment of the present invention, as shown in fig. 8, including:
s801, enabling a Controller (no matter the Controller-AP or the asi-Controller-AP) in the EasyMesh network through an out-of-band mechanism (UI and other modes), and starting an announcement negotiation protocol based on multicast;
s802, periodically notifying a Controller existence message in a special synchronous management channel, wherein the message comprises a service set identifier SSID, a basic service set identifier BSSID, a running time uptime and a management IP;
s803, receiving other Controller announcements; to determine the presence of multiple controllers in the current EasyMesh network; and determining that the management IP of each Controller is in the same network segment according to the notification information negotiation;
s804, further, the Controller receives the existing information of other controllers, judges that the information is sent by a non-local machine, and requests to change the management IP if the uptime in the information is larger than the uptime of the local machine and the local machine does not negotiate to determine the management IP;
s805, further, after receiving the management IP message requested to be changed by the Controller, other controllers allocate a management IP of the same network segment to the Controller requesting to change the management IP in the response of the management IP message requested to be changed;
s806, after the Controller requesting to change the management IP receives the response of the message requesting to change the management IP, the Controller managing IP is modified according to the distribution IP given in the message.
Example 6
Fig. 9 is a schematic flow chart of an extension of the EasyMesh network Controller discovery mechanism in the embodiment of the present invention, as shown in fig. 9, including:
s901, Controller receives AP-Autoconfiguration Search message;
s902, judging the condition of a multi-Controller EasyMesh network;
s903, a notification Controller-Cooperate module;
s904, the Controller-Cooperate module creates and maintains a Controller domain table, an asi-Controller domain table and a Station table, and coordinates a synchronous cooperation state among the controllers according to the tables; so as to control the actions of Agent-AP and Station in the response Controller domain and the Assi-Controller domain.
The maintenance criteria of the Controller domain table and the Assi-Controller domain table are as follows: the member joining follows the first entering criterion, and the same member can only belong to a single domain in the same time period; member message processing strictly follows domain-wide restrictions.
Specifically, the method comprises the following steps:
1. in the case of a multiple Controller EasyMesh network being determined;
2. after receiving any request of Agent-AP and Station, Controller-AP and Assi-Controller-AP report Controller-Cooperate module to confirm whether member request of local domain is existed or not before response;
3. if the Controller-Cooperate module confirms that the Agent-AP or Station is in the local area table, directly responding to the local area Controller, and directly responding to the local area Controller for processing;
4. if the Controller-Cooperate module finds that the Agent-AP or the Station is not in the local area table, the opposite terminal Controller-Cooperate module is informed to search in the local area table at the same time, if the opposite terminal area is in the opposite terminal area, the opposite terminal area is used for processing, if the opposite terminal area responds that the member is not in the local area table, the Agent-AP or the Station is added into the local area table and is used for processing by the local area Controller; (if leaving or disassociating, Agent-AP or Station is deleted from the local domain table).
Example 7
Fig. 10 is a schematic flowchart of the synchronization process of the FDB table, the ARP table, and the Controller IP address pool of each networking device in the embodiment of the present invention, and as shown in fig. 10, the synchronization process includes:
s1001, switching the Station access or roaming into any Controller domain or Assi-Controller domain;
s1002, the Controller-AP or the Assi-Controller-AP informs the Controller-Cooperate module;
and S1003, the Controller-Cooperate module cooperates with the Controller-AP and the Assi-Controller-AP to carry out IP address pool synchronization through a special synchronous management channel, and further, the synchronization of the FDB table and the ARP table of all networking equipment in the home domain is completed.
The WAN side IP of the controllers accessing different uplink gateways is different; however, the IP of the LAN side of the Controller can be set as the management IP of the same network segment through the multicast-based advertisement negotiation protocol, and the IP address pool is in the same network segment.
If the Station access is under the Controller-AP domain, the IP is allocated by the Controller-AP through DHCP; if the Station access is under the Assi-Controller-AP domain, its IP is allocated by the Assi-Controller-AP through DHCP.
The management IP of the Controller-AP and the management IP of the Assi-Controller-AP are in the same network segment, and the address pools are also in the same network segment;
the purpose of the synchronous IP address pool is that in the whole EasyMesh network, the address pools of the Controller-AP and the asi-Controller-AP are consistent and cannot be repeatedly allocated, the situation that the IP is acquired again by the station which acquires the IP is avoided, and the seamless roaming experience is improved.
Example 8
Fig. 11 is a schematic diagram of a Controller domain table, an asi-Controller domain table and a Station table of a multi-Controller EasyMesh network in an embodiment of the present invention, as follows:
the Controller domain table and the Assi-Controller domain table comprise domain numbers, in-domain Agentid and Agent Mac lists;
the Station table comprises a Station Mac, Agentid associated with the Station Mac and a domain number of the Station Mac;
the Controller-Cooperate module creates and maintains a Controller domain table, an Assi-Controller domain table and a Station table, and coordinates a synchronous cooperation state among the controllers according to the tables; so as to control the actions of Agent-AP and Station in the response Controller domain and the Assi-Controller domain.
Example 9
As shown in fig. 12, the present invention provides an easy mesh network multi-Controller implementation system, which includes a Controller-AP, an asi-Controller-AP, an Agent-AP and a Station, wherein:
in an EasyMesh network, expanding the role of the existing EasyMesh protocol Controller, and on the premise of the role of the existing Controller-AP, adding the role of the Assi-Controller-AP; the Controller-AP and the asi-Controller-AP have equal status, and respectively control the Agent-AP and the Station accessed to the own domain;
establishing a special synchronous management channel between the Controller-AP and the Assi-Controller-AP, wherein the special synchronous management channel is isolated from the data service;
the entire multicontroller EasyMesh network has the same SSID and password.
Furthermore, the invention also provides an EasyMesh network multi-Controller system constructed according to the EasyMesh network multi-Controller implementation method.
In the present invention, although only the text-text example illustrates the scenarios of two controllers, namely Controller-AP and asi-Controller-AP, in practice, the mechanism principle of the present invention is also applicable to scenarios of more than two controllers (i.e. 1 Controller-AP, not less than 1 asi-Controller-AP). Generally, a Controller (determined according to uptime time) started first in the EasyMesh network is used as a Controller-AP, and an asi-Controller-AP is used as the Controller-AP.
It will be understood by those skilled in the art that the foregoing is only a preferred embodiment of the present invention, and is not intended to limit the invention, and that any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (14)
1. An easy mesh network multi-Controller implementation method is characterized by comprising the following steps:
in an EasyMesh network, expanding the role of the existing EasyMesh protocol Controller, and on the premise of the role of the existing Controller-AP, adding the role of the Assi-Controller-AP; the Controller-AP and the asi-Controller-AP have equal status, and respectively control the Agent-AP and the Station accessed to the own domain;
establishing a special synchronous management channel with the same VLAN between the Controller-AP and the Assi-Controller-AP, wherein the special synchronous management channel is isolated from the data service;
the entire multicontroller EasyMesh network has the same SSID and password.
2. The easy mesh network multicontroller implementation of claim 1, wherein the Controller role is managed by a multicast-based advertisement negotiation protocol: the controllers in the EasyMesh network are enabled through an out-of-band mechanism, the notification negotiation protocol notifies the controllers in a special synchronous management channel period, receives the notifications of other controllers to determine multiple controllers in the current EasyMesh network, and negotiates to determine that the management IP of each Controller is in the same network segment according to the notification information.
3. The easy mesh network multicontroller implementation method of claim 1 or 2, further comprising an easy mesh network Controller role discovery mechanism extension, wherein the Controller role discovery mechanism extension is implemented by three tables:
responding AP-Autoconfiguration Search message flow expansion processing to a Controller of an original EasyMesh protocol, creating and maintaining a Controller domain table, an asi-Controller domain table and a Station table, and coordinating synchronous cooperation states among all Controller roles according to the tables; so as to control the actions of Agent-AP and Station in the response Controller domain and the Assi-Controller domain.
4. The easy mesh network multicontroller implementation of claim 3, further comprising a Controller domain, asi-Controller domain form member maintenance criteria: the member joining follows the first entering criterion, and the same member can only belong to a single domain in the same time period; member message processing follows domain-wide restrictions.
5. The easy mesh network multicontroller implementation of claim 1 or 2, further comprising: when any Controller domain or the asi-Controller domain has Station access or roaming access, IP address pool synchronization is carried out through a special synchronous management channel, Controller-AP and asi-Controller-AP, and further synchronization of all network equipment ARP tables and FDB tables of the domain is completed.
6. The easy mesh network multicontroller implementation of claim 1 or 2, further comprising: all the service flows of the Station accessed or roamed into any Controller domain or Assi-Controller domain are all uplink from the WAN port of the Controller-AP or Assi-Controller-AP to the local gateway for accessing Internet.
7. The easy mesh network multicontroller implementation of claim 1 or 2, wherein establishing a dedicated synchronization management channel between said Controller-AP and asi-Controller-AP in connection with an upstream gateway comprises:
the Controller-AP and the Assi-Controller-AP are accessed to the same uplink gateway LAN side through wires;
the wired VLAN implementation of the special synchronous management channel is as follows: and establishing an uplink wired VLAN subinterface of the Controller-AP and the asi-Controller-AP, and establishing a VLAN subinterface with an uplink gateway LAN side which is correspondingly connected with a wire.
8. The easy mesh network multicontroller implementation of claim 1 or 2, wherein the establishment of a wireless dedicated synchronization management channel between Controller-AP and asi-Controller-AP independent of the upstream gateway comprises:
the realization of the wireless VLAN of the special synchronous management channel comprises the following steps: a wireless VLAN sub-interface between a Controller-AP and an Assi-Controller-AP is created, one of which is used as ext _ AP and the other is used as ext _ sta.
9. The easy mesh network multicontroller implementation of claim 1 or 2, wherein the establishment of a dedicated synchronization management channel between Controller-AP and asi-Controller-AP independent of upstream gateway, comprises:
the wired VLAN of the special synchronous management channel is realized as follows: and establishing wired VLAN sub-interfaces at the LAN sides of the Controller-AP and the asi-Controller-AP, and establishing a wired directly-connected VLAN special synchronous management channel.
10. The easy mesh network multicontroller implementation of claim 2, wherein the Controller role management and dedicated synchronization management channel establishment procedure comprises:
s801, enabling a Controller role function in an EasyMesh network through an out-of-band mechanism, and starting a multicast-based notification negotiation protocol;
s802, the notification negotiation protocol periodically notifies the Controller role existence message in a special synchronous management channel, wherein the message comprises a service set identifier SSID, a basic service set identifier BSSID, an operating time uptime and a management IP;
s803, receiving other Controller role announcements; to determine the existence of multiple Controller roles in the current EasyMesh network; and determining that the management IP of each Controller role is in the same network segment according to the notification information negotiation.
11. The easy mesh network multicontroller implementation of claim 3 wherein the easy mesh network Controller discovery mechanism extension comprises:
s901, the Controller role receives the AP-Autoconfiguration Search message;
s902, judging the condition of a multi-Controller EasyMesh network;
s903, a notification Controller-Cooperate module;
s904, the Controller-Cooperate module creates and maintains a Controller domain table, an asi-Controller domain table and a Station table, and coordinates a synchronous cooperation state among the Controller roles according to the tables; so as to control the actions of Agent-AP and Station in the response Controller domain and the Assi-Controller domain.
12. The easy mesh network multicontroller implementation method of claim 5 wherein the process of synchronizing the FDB table, the ARP table and the Controller IP address pool of each networking device in the easy mesh network comprises:
s1001, switching the Station access or roaming into any Controller domain or Assi-Controller domain;
s1002, informing a Controller-Cooperate of the role of the Controller-AP or the Assi-Controller-AP;
and S1003, the Controller-Cooperate module cooperates with the Controller-AP and the Assi-Controller-AP to carry out IP address pool synchronization through a special synchronous management channel, and further, the synchronization of the FDB table and the ARP table of all networking equipment in the home domain is completed.
13. An EasyMesh network multi-Controller system is characterized by comprising a Controller-AP, an asi-Controller-AP, an Agent-AP and a Station, wherein:
in an EasyMesh network, expanding the role of the existing EasyMesh protocol Controller, and on the premise of the role of the existing Controller-AP, adding the role of the Assi-Controller-AP; the Controller-AP and the asi-Controller-AP have equal status, and respectively control the Agent-AP and the Station accessed to the own domain;
establishing a special synchronous management channel between the Controller-AP and the Assi-Controller-AP, wherein the special synchronous management channel is isolated from the data service;
the entire multicontroller EasyMesh network has the same SSID and password.
14. An EasyMesh network multicontroller system constructed by the method of implementing an EasyMesh network multicontroller as claimed in any one of claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010882184.4A CN112105095B (en) | 2020-08-28 | 2020-08-28 | EasyMesh network multi-Controller implementation method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010882184.4A CN112105095B (en) | 2020-08-28 | 2020-08-28 | EasyMesh network multi-Controller implementation method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112105095A CN112105095A (en) | 2020-12-18 |
| CN112105095B true CN112105095B (en) | 2022-03-25 |
Family
ID=73758135
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010882184.4A Active CN112105095B (en) | 2020-08-28 | 2020-08-28 | EasyMesh network multi-Controller implementation method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112105095B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112954670A (en) * | 2021-01-28 | 2021-06-11 | 上海同耀通信技术有限公司 | Mesh distributed networking authentication system and testing method |
| CN114040463A (en) * | 2021-11-05 | 2022-02-11 | 深圳市联洲国际技术有限公司 | Networking method and device, computer readable storage medium and processor |
| CN114302433B (en) * | 2021-12-28 | 2023-09-01 | 深圳市创维软件有限公司 | Mesh networking method for multiple devices, device and readable storage medium |
| CN114710795B (en) * | 2022-06-06 | 2022-08-26 | 希诺麦田技术（深圳）有限公司 | ARP table optimization method, equipment and application of wireless ad hoc network |
| CN115103371B (en) * | 2022-06-21 | 2023-07-21 | 广州通则康威智能科技有限公司 | Networking method and system based on prplMesh application |
| CN114945192B (en) * | 2022-07-25 | 2023-11-10 | 深圳市亿联无限科技有限公司 | Easymesh network rapid networking method and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101640892A (en) * | 2009-08-21 | 2010-02-03 | 杭州华三通信技术有限公司 | Wireless network deployment method and wireless access point |
| CN105992262A (en) * | 2016-06-30 | 2016-10-05 | 西安电子科技大学 | Adaptive mode switching method for wireless Mesh network |
| CN108076682A (en) * | 2015-08-14 | 2018-05-25 | 飞利浦照明控股有限公司 | Mesh WLAN controller, wlan device and the operating method for WLAN supplies |
| CN108259283A (en) * | 2018-04-19 | 2018-07-06 | 深圳市银河风云网络系统股份有限公司 | Wireless device communication means and system based on wide area network Mesh technologies |
| WO2019101194A1 (en) * | 2017-11-24 | 2019-05-31 | 乐鑫信息科技（上海）股份有限公司 | Mesh network-based networking method and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8634342B2 (en) * | 2006-10-05 | 2014-01-21 | Cisco Technology, Inc. | Upgrading mesh access points in a wireless mesh network |
| WO2019055468A1 (en) * | 2017-09-12 | 2019-03-21 | D&M Holdings Inc. | A method and system for providing limited controller access to a mesh network of media rendering devices |
-
2020
- 2020-08-28 CN CN202010882184.4A patent/CN112105095B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101640892A (en) * | 2009-08-21 | 2010-02-03 | 杭州华三通信技术有限公司 | Wireless network deployment method and wireless access point |
| CN108076682A (en) * | 2015-08-14 | 2018-05-25 | 飞利浦照明控股有限公司 | Mesh WLAN controller, wlan device and the operating method for WLAN supplies |
| CN105992262A (en) * | 2016-06-30 | 2016-10-05 | 西安电子科技大学 | Adaptive mode switching method for wireless Mesh network |
| WO2019101194A1 (en) * | 2017-11-24 | 2019-05-31 | 乐鑫信息科技（上海）股份有限公司 | Mesh network-based networking method and system |
| CN108259283A (en) * | 2018-04-19 | 2018-07-06 | 深圳市银河风云网络系统股份有限公司 | Wireless device communication means and system based on wide area network Mesh technologies |
Non-Patent Citations (3)
| Title |
|---|
| EasyMesh最简单的入门级介绍;wangxinyu2011;《URL：https://blog.csdn.net/u012573878/article/details/104409787》;20200220;全文 * |
| Seamless Multimedia Streaming in Controller-Less Wireless Mesh Networks With Mobile Stations;Markus Thell et.al;《IEEE Xplore》;20200717;全文 * |
| 集中式无线Mesh网络架构及切换技术研究;蒋纬昌;《中国优秀硕士学位论文全文数据库（电子期刊）》;20180415;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112105095A (en) | 2020-12-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112105095B (en) | EasyMesh network multi-Controller implementation method and system | |
| US8503396B2 (en) | Network apparatus enabling roaming across subnets | |
| EP2874359B1 (en) | Extended ethernet fabric switches | |
| US9137641B2 (en) | Wireless communication system, base station, and terminal | |
| US7917146B2 (en) | Methods, apparatuses and systems facilitating client handoffs in wireless network systems | |
| US7561898B2 (en) | Apparatus and method for registering wireless terminals with access point through wireless network | |
| JP2005192187A (en) | Method for establishing channel between user agent and wireless lan access point in environment where a plurality of wireless lan access points are installed | |
| US8300578B2 (en) | System, apparatus and method for seamless roaming through the use of routing update messages | |
| CN109660442B (en) | Method and device for multicast replication in Overlay network | |
| US20170013452A1 (en) | Network re-convergence point | |
| US9590824B1 (en) | Signaling host move in dynamic fabric automation using multiprotocol BGP | |
| US8611358B2 (en) | Mobile network traffic management | |
| CN110445702B (en) | Message forwarding method and device | |
| EP4016932A1 (en) | Evpn and vpls coexistence method, apparatus, and system | |
| JP2016535956A (en) | Coverage hole detection and minimization in communication networks | |
| US11509494B2 (en) | Protocol independent multicast (PIM) designated router (DR) election | |
| WO2021057962A1 (en) | Tunnel configuration method, apparatus and system, and device and storage medium | |
| US20140269648A1 (en) | Distributed Network Layer Mobility for Unified Access Networks | |
| EP3866408A1 (en) | Method for determining df of multicast stream, device, and system | |
| CN107623636B (en) | User isolation method and switch | |
| CN106792821B (en) | Access control method and device based on virtual gateway | |
| US20150098457A1 (en) | Enabling internet protocol connectivity across multi-hop mobile wireless networks via a service oriented architecture | |
| CN113037883B (en) | Method and device for updating MAC address table entries | |
| US10674565B2 (en) | Communication method | |
| CN115623480A (en) | Self-organizing network system, method and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |