无线 easyMesh 技术官方文档翻译

Multi-AP Specification v2.0

© 2019 Wi-Fi Alliance. All Rights Reserved.

Used with the permission of Wi-Fi Alliance under the terms as stated in this document.

Page 106 of 113

19 Traffic Separation

19.1 Traffic Separation in Multi-AP Network

19.1.1 Traffic Separation Overview (Informative)

appropriate) prior to ingressing the Multi-AP network by means not defined in this specification and is expected to be

identified as belonging to an SSID.

A Multi-AP device is a layer-2 (Link Layer) logical device that can be embedded into a more complex physical device

(e.g., a router, or a gateway) that implements both a Multi-AP Agent as well as other, above layer-2, functionalities. Often

in this case, traffic generated outside of the network (e.g., ingressing thru the WAN interface) is classified by the

gateway/routing subsystem and tagged (if needed) before being forwarded to the Multi-AP device subsystem. The

abstract/logical interface between the Multi-AP subsystem and the rest of the device is considered a Multi-AP Logical

Ethernet Interface as per the definition in section 3.1.3 and the rules in section 19.1.3.

If Traffic Separation is not configured on a Multi-AP Agent that implements Profile-2, the Multi-AP Agent might behave in a

transparent manner to VLAN tags applied by other entities.

Controller that intends to use more VIDs than those supported on some of the Multi-AP Agents it manages, may re-

arrange the topology in such a way that traffic for all VIDs downstream of a Multi-AP Agent can be forwarded by such

Agent.

For each Ingress Packet, a Multi-AP Agent adds an 802.1Q C-TAG with a VLAN ID as specified in a Traffic Separation

Policy.

For each Egress Packet, a Multi-AP Agent removes any 802.1Q C-TAG.

For a packet to be transmitted on a Multi-AP Logical Ethernet Interface, if the VLAN ID in the 802.1Q C-TAG is set to one

of the Secondary VLAN IDs, a Multi-AP Agent maintains the 802.1Q C-TAG on those packets.

Multi-AP IEEE 1905.1 management frames are carried in the Primary Network.

A Default 802.1Q Settings TLV identifies a Primary VLAN ID for tagging packets on the Primary Network.

A Multi-AP Controller that reconfigures VLAN(s) in the entire Multi-AP Profile-2 Network Segment may reconfigure the

traffic separation policy on the Multi-AP Agents, starting from those at the very end of the data-plane tree topology and

finishing at the data-plane root. Failing to do so may result in the inability to deliver reconfiguration CMDUs to downstream

Multi-AP Agents due to Primary VLAN ID mismatch. During VLAN reconfiguration data traffic loss may occur.

Multi-AP Specification v2.0

© 2019 Wi-Fi Alliance. All Rights Reserved.

Used with the permission of Wi-Fi Alliance under the terms as stated in this document.

Page 107 of 113

Figure 5 shows an example network configuration with traffic separation enabled.

Figure 5. Example Network Configuration with Traffic Separation Enabled

19.1.1.1 Mixed backhaul and fronthaul (Informative)

processing. A Multi-AP Agent indicates its traffic separation capabilities to the Controller within the AP Radio Advanced

Capabilities TLV in the 1905 AP-Autoconfiguration WSC message. In a Multi-AP network where Traffic Separation is

enabled and a single SSID is used as both fronthaul and backhaul, a Controller that configures a Multi-AP Agent that has

reported Combined Front Back bit set to zero might achieve an equivalent topology by configuring this Multi-AP Agent

with two BSSs, one used exclusively as fronthaul and one used exclusively as backhaul, both bearing the same SSID and

credentials, on the same or on different radios, as permitted by the "Maximum number of BSSs" supported on each of the

Multi-AP Agent's radios.

In a Multi-AP network where Traffic Separation is enabled and both Profile-1 and Profile-2 Multi-AP Agents are expected

to associate with the backhaul BSS, a Controller that configures a Multi-AP Agent that has reported Combined Profile-1

and Profile-2 bit set to zero might achieve an equivalent topology by configuring this Multi-AP Agent with two backhaul