Ericsson EFN324, User Manual, Page: 43 / 176

Glossary
5.5 Quality of Service
When the same VLAN is used for traffic of different QoS requirement it is
possible to use flows to differentiate how the traffic will be handled within the
EFN. There will always be at least one flow created. If no flows are configured
manually, a default flow will be created that will handle all the traffic in the
specific VLAN.
The QoS model implemented on the EFN324 in R4.3 is based on four QoS­
Flows, configured at node level and one Flow per vlan. Frames are headed to
the proper flow on the basis of the
flow_selector
parameter of the
connect
command, which can assume the values p­bit, dscp, or none.
In the following is described the mapping in case of p­bit or dscp.
Flow 1 – flow id values pbits 0, 1 or dscp 0­15
Flow 2 – flow id values pbits 2, 3 or dscp 16­31
Flow 3 – flow id values pbits 4, 5 or dscp 32­47
Flow 4 – flow id values pbits 6, 7 or dscp 48­63
None is the default value; in this case, frames are headed to a unique
connection flow per vlan.
In case none is the flow selector, all frames headed to this flow will receive the
same handling, in other words there is no differentiation for the different CoS.
The following figure illustrates VLANs and Flow in the EFN between one
downlink port and the uplink port.