Re: [STDS-802-16] T16 Clarification
Absolutely. The standard is designed to allow function of mapping one or
more SFIDs (UL and/or DL agnostic) to any of the Active CIDs for the SS.
That includes the Basic and Primary CIDs. Typically, Service Flows with
attributes that require low latency would map to one of the higher priority
CIDs like Primary or even Basic. With less demanding Service Flows, like
Best Effort types, you would typically create a temporary CID for the SS to
map these Service Flows into, so as not to place low priority traffic into
high priority Primary and Basic CIDs. This method of allocating multiple
SFIDs to a limited number of CIDs permits more effective conservation of the
scarce CID management/allocation space.
Thanks,
Phil
----- Original Message -----
From: <mchion@ztesandiego.com>
To: <STDS-802-16@listserv.ieee.org>
Sent: Sunday, September 05, 2004 5:31 PM
Subject: Re: [STDS-802-16] T16 Clarification
> Phil,
>
> Since we are on this subject, does the standard (in your opinion) allows
> multiple DL SFIDs or multiple UL SFIDs map to one CID at one BS?
>
> Thanks.
>
> Mary
>
>
> Original Message:
> -----------------
> From: Phillip Barber pbarber@BROADBANDMOBILETECH.COM
> Date: Sun, 5 Sep 2004 11:03:55 -0500
> To: STDS-802-16@listserv.ieee.org
> Subject: Re: [STDS-802-16] T16 Clarification
>
>
> IEEE 802.16-2004, 6.3.14.2 Service flows, page 220, line 8 says 'a service
> flow is a MAC transport service that provides unidirectional transport of
> packets either to uplink packets transmitted by the SS or to downlink
> packets transmitted by the BS....' and line 18 says 'An SFID is assigned
to
> each existing service flow. The SFID serves as the principal identifier
for
> the service flow in the network. A service flow has at least an SFID and
an
> associated Direction.' So neither of these sentences say that the SFID
> must be unique and cannot be common between multiple service flows, though
> the language does indicate that the SFID must be to either a UL or DL
> service flow, not both. However, section 3. Definitions, page 10, line 52,
> '3.52 service flow identifier (SFID): A 32 bit quantity that uniquely
> identifies a service flow to both the subscriber station and base station
> (BS)...' is very specific and requires that the SFID be unique for that
> specific service flow. So the answer to your question is, NO, the SFID
> cannot be used for both the DL and UL of some similar service flows,
though
> they may share the same CID.
>
> Thanks,
> Phil
>
> ----- Original Message -----
> From: Eyal Verbin
> To: STDS-802-16@listserv.ieee.org
> Sent: Sunday, September 05, 2004 6:53 AM
> Subject: Re: [STDS-802-16] T16 Clarification
>
>
> The standard allows a situation in which a certain CID is used for a
> certain DL SFID and the same CID is used for another UL SFID. Does the
same
> approach apply for the SFID, i.e. can a certain SFID be used for UL and DL
> connection and be distinguished by the TLV type [145/146]
>
>
>
> Eyal
>
>
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>