Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-16] UL,DL services



That depends on your scheduler. It may, but doesn't have to.  The
scheduler may be very different from a vendor to vendor.  No guarantee
UL and DL service classes are exactly the same. Don't forget that the
concept of BW reservation in the DL doesn't exist. Hence the need to
implement UGS is not as strong.

Peretz Feder

On 7/7/2006 7:49 AM, Juliana Freitag wrote:

>Hello,
>
>   according to my understanding the service classes are also applicable 
>to downlink traffic, isn't it?
> 
>Thank you,
>Juliana.
>
>
>Two things to remember:
>
>1) UGS,rtps,nrtps,BE service class apply to the uplink only, not DL.
>2) Within each of these service classes, one may still assign different 
>service flow QoS attributes and different priorities.
>
>Per the above, you can see why it makes sense to have separate service 
>flows for the UL and DL. This doesn't preclude an implementation where 
>UL and DL service flow attributes are similar or even the same.
>
>Peretz Feder
>
>"Vasanth.Rajan" wrote:
>
>  
>
>>Hi all, Thanks for the prompt reply from the groups abt service 
>>flow,but still I have something to clear regarding this, I will list 
>>it below. a. Each service class defines a set of Qos parameters that 
>>can be associated with service flow.In 802.16 we have 4 std service 
>>class(UGS,rtps,nrtps,BE).So the BS will set Qos parameter for the 
>>above service flow(I am i right?).Separate service flows are required 
>>for uplink and downlink traffic, where each service flow is assigned a 
>>unique service level category and separate QoS settings.My question is 
>>why seperate service flows are required for uplink and downlink??(ie 
>>for same service class why we require seperate service flow for UL & 
>>DL) . If possible plz explain me with a practical example. Thanks in 
>>advanceVasanth
>>    
>>