Tsunami MP-8100 Installation and Management Guide 70
a. Ethernet Priority (low=0, high=0) (this is the equivalent of the User Priority value in the TCI (Tag Control
Information) field of a VLAN tag)
17. 802.1p Voice
a. Ethernet Priority (ToS low=6, ToS high=6) (this is the equivalent of the User Priority value in the TCI (Tag Control
Information) field of a VLAN tag)
18. 802.1p Video
a. Ethernet Priority (ToS low=5, ToS high=5) (this is the equivalent of the User Priority value in the TCI (Tag Control
Information) field of a VLAN tag)
NOTE: Two different VoIP rule names have been defined for each direction of traffic, Uplink (UL) and Downlink (DL),
(index numbers 4 to 7). This has been done to distinguish the proprietary nature of the Cisco VoIP implementation as
opposed to the more standard Session Initiation Protocol (SIP) signaling found, for example, in the Vonage-type VoIP
service.
4.6.1.2 Service Flow Class (SFC)
A Service Flow class defines a set of parameters that determines how a stream of application data that matches a certain
classification profile will be handled. You can create up to 32 different SFCs, including 8 predefined SFCs. Also, you can
create, edit, and delete SFCs that contain the following parameters and values:
• Service flow name
• Scheduling type – Best Effort (BE); Real-Time Polling Service (RTPS)
• Service Flow Direction – Downlink (DL: traffic from BSU to SU); Uplink (UL: traffic from SU to BSU)
• Maximum sustained data rate (or Maximum Information Rate, MIR) – specified in units of 1 Kbps from 8 Kbps up to
the maximum rate specified in the license.
• Minimum reserved traffic rate (or Committed Information Rate, CIR) – specified in units of 1 Kbps from 0 Kbps up to
the maximum rate specified in the license.
• Maximum Latency – specified in increments of 5 ms steps from a minimum of 5 ms up to a maximum of 100 ms
• Tolerable Jitter – specified in increments of 5 ms steps from a minimum of 0 ms up to the Maximum Latency (in ms)
• Traffic priority – zero (0) to seven (7), 0 being the lowest, 7 being the highest
• Maximum number of data messages in a burst – one (1) to sixteen (16), which affects the percentage of the maximum
throughput of the system
• Entry Status – Enable, Disable, and Delete
NOTE: Note that traffic priority refers to the prioritization of this specific Service Flow.
The device tries to deliver the packets within the specified latency and jitter requirements, relative to the moment of receiving
the packets in the unit. For delay-sensitive traffic, the jitter must be equal to or less than the latency. A packet is buffered until
an interval of time equal to the difference between Latency and Jitter (Latency – Jitter) has elapsed. The device will attempt to
deliver the packet within a time window starting at (Latency – Jitter) until the maximum Latency time is reached. If the SFC’s
scheduling type is real-time polling (RTPS), and the packet is not delivered by that time, it will be discarded. This can lead to
loss of packets without reaching the maximum throughput of the wireless link. For example, when the packets arrive in bursts
on the Ethernet interface and the wireless interface is momentarily maxed out, then the packets at the “end” of the burst
may be timed out before they can be sent.
Users can set up their own traffic characteristics (MIR, CIR, latency, jitter, etc.) per service flow class to meet their unique
requirements. A good example is provided by the 8 predefined SFCs:
1. UL-Unlimited BE
To Next Page
Loading...