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

Re: [STDS-802-16] DLFP and HFDD



Baraa,

If I remember correctly (and now all the details of standard are a big
mess in my head), then we had a comment that clarified this issue.
Anyway, the BS should avoid giving UL allocations to a specific SS,
which overlaps with DL PDUs to same SS.
Therefore, an SS receiving an UL allocation may assume that there is no
awaiting DL PDU during the same time period.

Regards,
Itzik.
-----Original Message-----
From: owner-stds-802-16@listserv.ieee.org
[mailto:owner-stds-802-16@listserv.ieee.org] On Behalf Of Al Dabagh,
Baraa
Sent: Friday, May 14, 2004 4:39 PM
To: STDS-802-16@listserv.ieee.org
Subject: [STDS-802-16] DLFP and HFDD

Folks,

   I have a question regarding the DLFP and DL/UL allocations (OFDM 256)
in an HFDD based system:

It seems to be possible that an UL allocation can be in conflict with
one of the DL allocation specified in the FCH (or the DLFP0 for a
particular SS. In the case were there is a conflict, should the SS
assume that there is no allocation for it in the DL burst specified by
the FCH (or the DLFP) and attempt not to decode it, or should the MAC on
the BS be smart enough to allocate on a per PDU level (rather than a
burst level)?

If the answer is the second option, then this assumes the SS will decode
a DL burst, extract the PDUs that belong to it from the burst, and if
there is an allocation on the UL overlapping then it should terminate
the DL burst decoding, and start transmitting data!! The same thing
applies for a broadcast or multicast CID specified in the DL MAP that
overlaps with an UL allocation.

Thanks

Baraa Al-Dabagh
BWD
Intel Corporation
baraa.al.dabagh@intel.com
Phone: 408-545-6078