Professional Documents
Culture Documents
Technology Whitepaper
Issue 1.1
Date 2017-04-10
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Abstract:
The agile distributed Wi-Fi makes innovation on the traditional AC + AP architecture. It
introduces the new idea of central AP and reallocates functions of the traditional AC and AP
to the AC, central AP, and remote radio units (RUs). This document describes what is agile
distributed Wi-Fi and how is it implemented.
Contents
Figures
Figure 2-3 Service model when the central AP functions as a Fat AP ............................................................... 5
Figure 2-4 AP online process .......................................................................................................................... 7
Figure 2-5 Process of acquiring configurations for RUs ................................................................................... 7
Figure 2-6 Online process of RUs ................................................................................................................... 8
Figure 2-7 STA online process in 802.1x authentication mode ......................................................................... 9
Figure 2-8 STA roaming on the same central AP............................................................................................. 11
Figure 5-4 Application of the agile distributed Wi-Fi in the wireless campuses................................................18
1 Background
With the popularization of smart terminals and tablets, the demands for Wi-Fi networks are
increasing explosively. As predicated by related institutions, Wi-Fi data traffic will exceed the
wired data traffic by 2019. Explosive Wi-Fi growth brings increase in user access and
roaming requirements. In addition, diversified application scenarios pose various
requirements on Wi-Fi functions and performance. The traditional AC + AP architecture
somehow cannot meet requirements of these scenarios. Under the AC + AP architecture,
association and reassociation request packets of users are all sent to the AC for processing.
When a large number of users connect to the network or roam, it will be a heavy burden for
the AC to process packets of these users. The AC performance will become a bottleneck.
However, if these packets are processed locally on each AP, the APs will be heavily burdened
too. In scenarios with a high density of rooms, such as the school (student dormitories), hotel
(guest rooms), or hospital (wards), signals are usually led to each room through remote
antennas connected to the APs to ensure signal coverage in each room. However, the distance
between the antenna and AP is limited in this solution (a larger distance means larger signal
attenuation). Additionally, multiple rooms share one AP, causing performance bottleneck.
To cope with the challenges brought by the expanding network scale and frequent application
upgrades, Huawei launches the agile distributed Wi-Fi solution which is composed of the AC,
central AP, and RUs, as shown in the preceding figure. The agile distributed Wi-Fi solution
innovatively decomposes the traditional AP into two independent devices: the central AP and
RU, and redistributes the service module on the AC, central AP, and RU. Such innovative
architecture reduces the burden on the traditional AC and AP, improves the network
performance and large-scale networking capability, and solves the problems of limited
AP-antenna distance due to signal attenuation and performance bottleneck in radio sharing
among multiple rooms in scenarios with a high density of rooms, such as the school
(dormitories), hotel (guest rooms), and hospital (wards). In addition, the layered and modular
architecture creates infinite possibilities in feature innovation and continuous performance
improvement.
2 Implementation
The following figure shows the typical networking diagram of the agile distributed Wi-Fi.
To ensure sufficient flexibility to adapt to different application scenarios, the central AP can
work as a Fat AP or Fit AP. When the central AP works in Fat AP mode, no AC is required.
The central AP completes networking by itself. The central AP can manage and configure
RUs, more applicable to Small to Medium-sized Business (SMB) with a few APs (in Fat AP
mode, the maximum number of RUs managed by the central AP depends on the model of the
central AP). In Fit AP mode, the central AP needs to complete networking with the AC, more
applicable to campuses with large-scale AP deployment.
The central AP does not provide radios regardless of whether it works in Fit AP or Fat AP
mode and needs to use RUs to receive and transmit radio signals. The RU is actually a remote
radio module separated from the traditional AP and can connect to the central AP directly
through the network cable or through a PoE switch. In both connection modes, a Layer 2
network must be deployed between the RU and central AP because the RU needs to discover
the central AP in broadcast mode.
− AC
Services related to WLAN components, such as AP management and user
management are deployed on the AC. When the AC serves as a service gateway,
NAC and DHCP can also be configured on the AC. In addition, service forwarding
functions are deployed on the AC.
In the three-layer architecture, the central AP plays a key role. On one hand, the central
AP helps the AC process some services and offloads service processing requirements of
the AC, reducing the burden on the AC. On the other hand, the forwarding, spectrum
analysis, and statistics collection functions are transferred to the central AP. The RU
therefore undertakes only the radio processing task, releasing some of the processing
capability. The central AP also manages the RUs. Although the network architecture is
composed of three layers, it can still be managed as a two-layer flat architecture. The
central AP provides a platform for collaboration between RUs, setting the stage for
innovation of advanced features. Generally, introduction of the central AP improves the
overall network capability (including the networking capability and innovation capability)
while does not increase management complexity.
2. The central AP works as a Fat AP (two-layer architecture).
When the central AP is a Fat AP, the agile distributed architecture is a two-layer
architecture, containing only the central AP and RU. The following figure shows the
service model.
The two-layer agile distributed Wi-Fi no longer depends on the AC. The Fat central AP
functions as an AC and implements self-networking and self-management. The central
AP can serve as a service gateway and provides users with related functions. The central
AP integrates switch ports and provides PoE capability. In addition, the central AP
reserves the capability for abundant service evolution.
The two-layer agile distributed Wi-Fi architecture is suitable for small office and home
office (SOHO), SMB, and multiple- branch networking scenarios.
Since the RU acquires its configuration from the central AP, the central AP needs to
acquire both its configuration and configurations of its managed RUs from the AC.
Figure 2-5 shows how the RUs acquire configurations.
(1) Based on each AP group, the AC maintains a list of central APs in the AP group.
When the central AP goes online, the AC delivers all AP-Group configurations used
by the central AP. When the RUs go online, the AC delivers specific configurations
of the RUs.
(2) Upon receiving the AP-Group and RU-specific configurations, the central AP saves
the configuration first and delivers RU-specific and AP-Group configurations to
RUs based on the AP groups to which the RUs belong.
2. Online process of RUs
The RU communicates with the central AP through the CAPWAP tunnel. After the RU
completes registration on the central AP, the central AP reports the RU information to the
AC. Figure 2-6 shows the online process of RUs, which can be simply described as
follows:
(1) The RU broadcasts Discovery Request packets to discover the central AP; therefore,
the RU and central AP must be connected through a Layer 2 network and apply for
IP addresses of the same network segment.
(2) After the central AP establishes a CAPWAP link with the RU and the central AP
reports RU information to the AC, the AC then implements MAC address or SN
authentication on the RU. The AC delivers the RU-specific configurations to the
central AP.
(3) The AC returns the authentication result to the central AP. If the authentication fails,
the central AP disconnects the RU. If the authentication succeeds, the central AP
further checks whether the RU version expires.
(4) If the RU version expires, the central AP starts the software upgrade process. After
the upgrade is complete, the RU restarts and reenters the central AP discovery
process. If the RU version does not expire, the RU obtains configuration from the
central AP.
The CAPWAP tunnel between the RU and central AP includes the control tunnel and
data tunnel. The control tunnel mainly carries control information, including the
configurations. The data tunnel mainly carries data information. The CAPWAP control
tunnel between the central AP and RU supports Datagram Transport Layer Security
(DTLS) PSK encryption. The PSK can be configured using commands on the AC or RU.
The DTLS PSK configured on the AC can be delivered to the central AP. The central AP
then allocates the DTLS PSK to each RU.
The preceding descriptions about the online process of RUs are based on the scenario
where the central AP is a Fit AP. Actually, when the central AP is a Fat AP, the online
process of RUs is the same, but the AC is not an independent device but a module in the
central AP.
The association control here involves STA control during association (going online),
disassociation (going offline), and reassociation (roaming). Association is part of the
STA online process. Figure 2-7 shows the STA online process in 802.1x authentication
mode. As shown in the figure, the association request is processed on the central AP but
not sent to the AC for processing, and the central AP reports the processing result to the
AC. However, certain conditions must be met to enable the central AP to directly reply to
the association request. The following describes how to control STA association (going
online) on the agile distributed Wi-Fi based on the STA online process.
(1) The STA sends an Assoc request to the RU. The RU sends the request to the central
AP.
(2) The central AP searches the local user table for the user entry. If the user entry is
found, the central AP processes the Assoc request according to the roaming process.
If the user entry is not found, the central AP continuously processes the Assoc
request according to the online process.
(3) The central AP checks whether it can directly reply to the Assoc request. If neither
load balancing nor STA blacklist is configured, the central AP can directly reply to
the Assoc request. Otherwise, the central AP reports the Assoc request to the AC.
(4) In addition to basic information of the STA, the Assoc request message reported to
the AC carries the following information:
Whether an Assoc response message is replied
Whether key negotiation is completed
Whether services are provisioned
Duration from the time when the Assoc request is received to the current time
(5) After the central AP replies an Assoc response message, the AC implements
authentication on the STA and delivers PMK and authorization information to the
central AP. After receiving the delivered information, the central AP negotiates the
key with the STA to provision services.
(6) The AC periodically synchronizes user data with the central AP. The central AP can
report STA information received from multiple RUs to the AC at one time. The
reported STA information includes the RU that the STA currently associates with.
2. STA roaming
When the STA roams between RUs connected to the same central AP (at Layer 2 or
Layer 3), the roaming message is directly processed on the central AP but does not need
to be sent to the AC for processing. The central AP only needs to report the roaming
event.
(1) The STA initiates an Assoc/Reassoc request. After receiving the request, the RU
sends it to the central AP.
(2) The central AP searches the local user table for the user entry. If the user entry is not
found, the central AP processes the Assoc/Reassoc request according to the online
process. If the user entry is found, the central AP continuously processes the
Assoc/Reassoc request according to the roaming process and verifies the SSID. If
802.1x authentication is configured, the PMK also needs to be verified. If the SSID
and PMK pass the verification, the STA is considered roaming within the same
central AP, and the central AP directly replies an Assoc/Reassoc response and
negotiates the unicast and multicast key information based on the PMK.
(3) The central AP reports the user roaming event to the AC. The reported message
carries the RU that the STA newly associates and basic information such as the
radio and VAP, as well as the duration from when the user roams to the current time.
3 Customer Benefits
requirements on the AC, reducing the burden on the AC. On the other hand, the functions
of traditional APs, such as data forwarding, spectrum analysis, and data collection are
migrated to the central AP. The RUs only process radio signals, which releases the
processing capability of the RUs. The agile distributed Wi-Fi solution improves the
large-scale networking capability and wireless performance. Take the concurrent
roaming processing capability of the WLAN network as an example. Suppose 80% of
the roaming events occur within the central AP, the WLAN using the traditional AC + Fit
AP architecture can process 120 roaming events per second, and the WLAN using the
AC + Central AP + RU architecture can process 400 roaming events per second. The
roaming processing capability increases by three times.
2. Reduced number of managed nodes and simplified management
The central AP manages RUs. Even if the network has a three-layer architecture, it is still
managed as a two-layer flat architecture. In this architecture, the AC only needs to
manage the central AP. The AD9430DN-24 can manage 24 RUs by default and 48 RUs
through a switch. The number of the managed nodes in the agile distributed Wi-Fi
architecture is less than 5% (1/24 = 4.17%) of the traditional architecture under which
the AC needs to manage all APs. The management complexity is greatly reduced.
3. Innovative solutions of various kinds
The modular, layered agile distributed architecture makes it possible to implement
various functions and features, which also creates favorable conditions for innovative
solutions.
In scenarios with a high density of rooms, such as the school (dormitories), hotel (guest
rooms), and hospital (wards), the RUs used in the agile distributed Wi-Fi can be directly
mounted to a wall plate, wall, or ceiling in rooms, ensuring full signal coverage without
attenuation. Since RUs are independent radio units, they do not need to share radios,
preventing hidden STA problems and performance deterioration of air interfaces. The
agile distributed Wi-Fi solution has coverage and capacity advantages over the indoor
settled, distributed, and smart distributed solutions. Compared with the wall plate
coverage solution, this solution manages a smaller number of nodes, requires fewer
licenses, and has a higher large-scale networking capability.
4. Abundant service evolution capabilities
The agile distributed Wi-Fi uses a modular and layered architecture. The central AP can
implement RU collaboration without manual intervention, providing support for
innovation of related features. The central AP also offloads some responsibilities of the
AC and RUs, saving the processing capabilities needed for feature innovation or
evolution.
The central AP also retains abundant service evolution capabilities, including
cloud-based management, deep packet inspection (DPI), firewall, VPN, and IoT module
management.
4 Product Specifications
Huawei has released two models of central APs and RUs for the agile distributed Wi-Fi
solution in V200R006C20. Currently, the other AP models do not support the agile distributed
Wi-Fi architecture. The AC models that support the agile distributed Wi-Fi architecture
include the ACU2, AC6605, AC6005, and AC6003.
1. Specifications of the central AP
2. Specifications of RUs
3. Specifications of the AC
5 Typical Application
The agile distributed Wi-Fi architecture is newly launched by Huawei. This architecture
features high networking capability, coverage performance, and evolution capability,
applicable to venues with a high density of rooms, as well as SMB, wireless medical service,
and campus scenarios.
Advantages:
Advantages:
Large-power AP and high-specification indoor distributed components, wide coverage
Easy-to-deploy APs, low cabling and construction costs
range for each AP, comprehensive and even signal coverage
Disadvantages:
Signal coverage based on existing feeder resources of carriers, reducing costs
The signal attenuation is large, and signal quality in rooms cannot be guaranteed.
Disadvantages:
The signal attenuation is small on corridors, but there are severe interference between
High costs for building a new feeder system, high requirements on the customer's
APs. The overall performance is low.
engineering capability, difficult to implement
Single spatial stream with low bandwidth, low air interface performance due to radio
sharing and hidden STA problems
Advantages: Advantages:
Signals led into rooms through remote antennas, good signal coverage inside rooms Indoor deployment of wall plate APs, large capacity of air interfaces, optimal coverage
Lower costs than using the existing feeder system, easy to implement performance
Disadvantages: Easy to install into 86-type boxes, low costs for scenarios deployed with cables indoors
Using a large number of feeders, higher costs than using digital lines, limited coverage Disadvantages:
rooms due to feeder attenuation Higher cabling and construction costs than the smart distributed solution for scenarios
Low air interface performance due to radio sharing and hidden STA problems where new cables need to be deployed
Requiring a large number of APs and licenses, high requirements on the AC
processing capability, limited network scale
In the agile distributed Wi-Fi solution, RUs can be directly deployed indoors. They can be
mounted to a wall plate, wall, or ceiling in rooms, ensuring that signals are led into each room
without penetration loss. Since RUs are independent radio units, they do not need to share
radios, preventing hidden STA problems and performance deterioration of air interfaces. The
agile distributed Wi-Fi solution has coverage and capacity advantages over the indoor settled,
distributed, and smart distributed solutions. Compared with the wall plate coverage solution,
this solution manages a smaller number of nodes, requires fewer licenses, and has higher
large-scale networking capability.
5.2 SMB
SMBs are those enterprises with a small scale and limited personnel and capital. These
enterprises have a small network, do not have professional O&M personnel, and require
"all-in-one" devices (low costs).
Huawei's agile distributed Wi-Fi solution that uses the central AP working in Fat AP mode
meets the preceding requirements. Under this architecture, the networking does not depend on
independent ACs. The Fat central AP functions as the AC and supports self-networking and
self-management. The Fat central AP can serve as a service gateway to provide gateway
functions for users. The central AP supports switch ports and provides PoE capability. It also
retains abundant service evolution capabilities oriented at SMBs, including cloud-based
management, DPI, SVN, and firewall.
Figure 5-3 Application of the agile distributed Wi-Fi in the wireless medical services
5.4 Campus
Figure 5-4 Application of the agile distributed Wi-Fi in the wireless campuses
The agile distributed Wi-Fi can also be used in common campus scenarios, which can
improve the large-scale networking capability and wireless performance. On one hand, the
central AP takes over some of the AC's services and offloads service processing requirements
on the AC, reducing the burden on the AC. On the other hand, the functions of traditional APs,
such as data forwarding, spectrum analysis, and data collection are migrated to the central AP.
The RUs only process radio signals, which releases the processing capability of the RUs. The
central AP can replace the access switch to provide PoE power and service forwarding
capability.