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

[STDS-802-16] subcarrier, subchannel, slot, data region, segment, permutation zone, frame



Hi, Colleagues,

 

I have some questions when I am trying to implement the 802.16e Section 8.4:

 

1. In 802.16-2004 (and 16e) Section 8.4, the concepts of symbol, subcarrier, subchannel, carrier-set, bin, tile, slot, data region, burst, segment, permutation zone, frame, multiframe are used. It seems that some of them are not well defined/described, and the number of them is far more than other standards such as IS-2000, UMTS, IS-136 and GSM used. Is it possible to make this number smaller?

 

2. Question about Segment:

(2.1) Segment is vaguely defined in 8.4.3.2. According to 8.4.3.2, the justification of using this concept seems to be that it is used to deploy a single instance of MAC. Is this concept used in the MAC layer? If yes, its relation to the MAC layer should be clearly described. If not, then the concept might be merged into other concepts such as subchannel, data region, burst, et al.

(2.2) The concept of Segment is used in 8.4.6.1.1 for Preamble. Preamble is purely a PHY layer concept and has nothing to do with MAC layer. This seems to contradict against the definition of Segment in 8.4.3.2.

(2.3) The concept of Segment is used in 8.4.4.4 for FCH subchannel allocation. If the concept of subchannel is used here, why is it needed to use Segment?

(2.4) The word Segment is used again in 8.4.3.4 for totally different meaning.

 

3. It seems that the concepts of bin and tile are used but never defined.

 

Thanks for your help in advance.

 

Dr. Will Liew

Andrew Corp.

434-386-5212




------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]