User's Manual Part 1

Release8OverviewofCycloneNetworks

Issue2,November2007 Draft5forRegulatoryReview 85
Which set of these MIR parameters are applicable depends on the interactions of other
parameter values. These interactions are described under
Setting the Configuration
Source
on Page 295. Also, where the Configuration Source parameter setting in the AP
specifies that BAM values should be used, they are used only if Prizm is configured to
send the values that it stores for the MIR parameters.
MIR Data Entry Checking
Uplink and downlink MIR is enforced as shown in
Figure 20.
NOTE:
In these figures, entry refers to the setting in the data rate parameter, not the
burst allocation parameter.
uplink c ap enforced =
uplink entry x aggregate cap
f
or the
SM
u
p
link entr
y
+ downlink entr
y
downlink c a p enforc ed =
downlink entry x aggregate cap
f
or the
S
M
u
p
link entr
y
+ d ownlink entr
y
Figure 20: Uplink and downlink rate caps adjusted to apply aggregate cap
For example, in the Canopy SM, if you set the Sustained Uplink Data Rate parameter to
2,000 kbps and the Sustained Downlink Data Rate parameter to 10,000 kbps, then the
uplink and downlink MIR that will be enforced for the SM can be calculated as shown in
Figure 21.
uplink cap enforc ed =
2,000 kbps x 7,000 kbps
2,000 kb
p
s + 10,000 kb
p
s
= 1,167 kbp
s
downlink cap enforced =
10,000 kbps x 7,000 kbps
2,000 kb
p
s + 10,000 kb
p
s
= 5,833 kbp
s
Figure 21: Uplink and downlink rate cap adjustment example