EasyMesh is receiving a lot of buzz for good reason. With the shift to online services for voice, video, transactions, and managing the home, almost every household is seeking to get the best out of their home Wi-Fi network. In recent years, many have adopted mesh network devices to fill the holes in Wi-Fi coverage throughout their homes. In the past three years, PC Magazine tested and ranked 10 mesh devices from well-known retail players such as Linksys, Netgear, Google, TP-Link, and Samsung. This creates a new challenge for internet service providers whose subscribers are defining their quality of experience based on their Wi-Fi performance. These various mesh devices are not interoperable, taking control and visibility away from the service providers making it hard to manage them or requiring them to lock themselves into a single mesh solution, which is far from ideal from customer acquisition and satisfaction standpoints. ASSIA plans to give you and your subscribers more flexibility and choice as the EasyMesh standard evolves through releases, and gains acceptance and wide adoption.
From Extenders to Mesh
For many years, the option was to add extenders throughout the home. These were inexpensive devices scattered throughout the house that repeat or “boost” the Wi-Fi signal from the gateway. With a mesh network, the access points connect directly, dynamically, using a backhaul network to as many other access points as possible and efficiently route data from and to client devices. Well-designed mesh networks dynamically self-organize and self-configure which helps with workload distribution, fault tolerance, and maintenance. Yet if mesh nodes are in the wrong location, or are not properly configured, these advantages will not materialize, and the service provider will likely get the service call.
Enter EasyMesh, a standard from the Wi-Fi Alliance©, which will allow Wi-Fi CERTIFIED EasyMesh™ devices to interoperate and be centrally controlled. EasyMesh R2 is now available with a richer set of features than the original version, and R3 will soon add even more features. About 75 devices are now Wi-Fi CERTIFIED EasyMesh™. So, should service providers get started supporting mesh networks now? We at ASSIA believe you should start now, and we have a path for you to do it.
The Wi-Fi Alliance first released its EasyMesh R1 specification for multi-access point (MAP) networks in June 2018. The purpose of this specification is to enable interoperability across a MAP controller and Wi-Fi access points (APs) from different vendors in a Wi-Fi network deployment comprising multiple APs. This specification defines the control protocol between Wi-Fi® APs using IEEE 1905.1 Ethernet messaging across the premises LAN, as well as the data objects necessary to enable onboarding, provisioning, control, and management of multiple APs. The specification also defines the mechanism to specify traffic routes between Wi-Fi access points within the multi-AP network. There is both a specification and a test plan with compliance testing.
Other features specified in EasyMesh R1 are;
- Access point and station 802.11 capabilities (n, ac, ax) and supported rates, channels, power, bandwidths, number of spatial streams, short GI support and bands among other things
- Backhaul (AP to the controller) 1905 topology, available MAC-layer throughput (up/down), percent link availability, and Received Channel Power Indicator (RCPI)
- Fronthaul (STA to AP) available MAC-layer throughput (up/down) and RCPI
- Unassociated STA MAC ID and Received Power (RCPI)
- Beacon reports from associated stations
- Station associations (client steering); control which AP an STA associates with
- Backhaul steering; backhaul STA to fronthaul AP
- Controller or AP can initiate steering
- Steering policy determines if RCPI based steering, or vendor-proprietary steering, is used. RCPI thresholds also set by steering policy
- Can do 802.11v steering if supported, otherwise by AP performing disassociation
Channel assignment and transmit power assignments
- Based on channel preference reports which list preferred channels, sent from APs to the controller
Set reporting policies for steering and metrics reporting
EasyMesh R2, which is now finalized, contains four key categories of features; traffic separation, security, spectrum optimization, and additional diagnostics.
- Classify traffic to prioritize for QoS; map QoS-classes in, out, and between AP interfaces
- Separate traffic from different networks
- Enhanced client steering, with Wi-Fi CERTIFIED Agile MultibandTM fast BSS transition
- Securely onboard and authenticate Multi-AP devices
- IEEE 1905 message encryption
- Increased DFS channel usage with coordinated Channel Availability Check (CAC)
- More support for WFA Data Elements
- Increased channel scans
- Client steering reports
- Additional backhaul diagnostics
EasyMesh Controller functionality is currently limited to running on devices in the LAN. ASSIA is extending this to encompass cloud-based remote management.
EasyMesh R3 is still in development, and is to contain the following new features:
- Services prioritization
- Wi-Fi 6 capabilities reporting1905
- Layer Security
- Wi-Fi EasyConnectTM DPP onboarding
- Multicast loop prevention
ASSIA CloudCheck and EasyMesh
The CloudCheck architecture and roadmap are well aligned with the EasyMesh specification. We are actively contributing to prplMesh with the prpl foundation to define a standard and interoperable network with all of our expertise in the field. CloudCheck currently has many proprietary algorithms and features for supporting multi-AP networks, and we are now working to implement EasyMesh and adopt the interfaces which will enable our current and new CloudCheck algorithms to work with other vendor’s multi-AP hardware. So our recommendation is that you get started with CloudCheck today and provide support for mesh networks. Then you will be well prepared to offer your subscribers support for a variety of mesh access points from different vendors in the future. We believe this will give you a competitive edge against the providers that are locking themselves into a single vendor’s mesh network hardware.