Redline Communications Inc. AN100UXA Manual De Usuario
User
AN-100U/UX Base Station
Manual
70-00058-01-04
Proprietary Redline Communications © 2010
Page 108 of 136
April 19, 2010
6.4.3 Non-Real-Time Polling Service (nrtPS)
The nrtPS service is next in priority after rtPS, and is designed for applications that send
variable sized packets and are not time-critical, but do require priority processing to
ensure delivery. Typical applications include interactive web-based applications and high
bandwidth FTP.
variable sized packets and are not time-critical, but do require priority processing to
ensure delivery. Typical applications include interactive web-based applications and high
bandwidth FTP.
Min. Reserved Rate: The required Committed Information Rate (CIR). The scheduler
attempts to allocate this minimum bandwidth in every wireless frame.
attempts to allocate this minimum bandwidth in every wireless frame.
Max. Sustained Rate: The required Peak Information Rate (PIR). Connection traffic is
capped at this rate, measured per connection over one-second intervals.
capped at this rate, measured per connection over one-second intervals.
Priority: Enter the relative priority to other nrtPS connections, where zero (0) is low and
seven (7) is high. Connections with the same priority are processed based on time of
creation, and connections not receiving bandwidth in a wireless frame received elevated
priority in subsequent passes until serviced.
seven (7) is high. Connections with the same priority are processed based on time of
creation, and connections not receiving bandwidth in a wireless frame received elevated
priority in subsequent passes until serviced.
6.4.4 Best Effort (BE)
The BE service is the lowest priority, and is designed for applications that send variable
sized packets, are not time-critical, and do not specifically require any guarantee of
delivery. Typical applications include web browsing, and low bandwidth FTP.
sized packets, are not time-critical, and do not specifically require any guarantee of
delivery. Typical applications include web browsing, and low bandwidth FTP.
BE connections receive bandwidth only after allocations are made to all eligible higher
priority connections. Under high traffic conditions, BE traffic may be delayed for an
extended periods. Note that connection queues do not have 'data aging' and all traffic
will be transmitted (unless connection is deleted).
priority connections. Under high traffic conditions, BE traffic may be delayed for an
extended periods. Note that connection queues do not have 'data aging' and all traffic
will be transmitted (unless connection is deleted).
Max. Sustained Rate: The required Peak Information Rate (PIR). Connection traffic is
capped at this rate, measured per connection over one-second intervals (see Metered
Throughput).
capped at this rate, measured per connection over one-second intervals (see Metered
Throughput).
Priority: Enter the relative priority to other BE connections, where 0 is low and 7 is high.
Connections with the same priority are processed based on time of creation, and
connections not receiving bandwidth in a wireless frame received elevated priority in
subsequent passes until serviced.
Connections with the same priority are processed based on time of creation, and
connections not receiving bandwidth in a wireless frame received elevated priority in
subsequent passes until serviced.
6.5
RedMAX Traffic Scheduler
6.5.1 Stage 1: Wireless Management
This stage allocates bandwidth for basic and primary CID connection activities.
6.5.2 Stage 2: CPE Management (Reserved)
This stage allocates the guaranteed minimum bandwidth (if required) for the secondary
management channel (SMC) traffic, including HTTP, FTP, SNMP, and TELNET traffic.
6.5.3 Stage 3: Service Flows
This stage allocates bandwidth for connections with packets queued for transmission
Stage 3. 1
Stage 3.1 assigns bandwidth to UGS, rtPS, and nrtPS connections with packets queued
for transmission. Pass 1 begins with the oldest active connection having the highest
priority level. For each connection, bandwidth is allocated to up to the current value of
the deficit counter, or to empty that connection queue (whichever is less).
for transmission. Pass 1 begins with the oldest active connection having the highest
priority level. For each connection, bandwidth is allocated to up to the current value of
the deficit counter, or to empty that connection queue (whichever is less).
Pass 1 continues based on descending age at the same priority level, and then with the
next lower priority level. Pass 1 ends when all UGS, rtPS, and nrtPS connections are
processed or all available bandwidth has been allocated.
next lower priority level. Pass 1 ends when all UGS, rtPS, and nrtPS connections are
processed or all available bandwidth has been allocated.