Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0U:@ EX@COMMENTARY VERSIONREASON PROPOSED BA  @UJU_isACE@OE AAA N AN A!@"E#B$A%A&A'A(O)A*A+C,E-G.A/ M0!G1$J2&N3'4*A5A6+N7,A8-A9C:.A;0A<3N=4A>A?6H@7BADBFC8FD9BE;AFAJCK@OLBOMEANFAOGPPHBQARKASNJT @ nHBAM3016AUG95@O aulo od,,LetterPRIV''''\KhC0}BzA"@_'d     !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPBUUX  $,.YesNo/,  , : AM PMMArial MS Sans Serif !HIJKLMNOPQRSTT@ BALLOTNUMBERCHANGE COMMENT DATE COMMENT NUMBER COMMENT TYPE  LAST NAMEMEMBERSHIP TYPEDACommentary VersionB GA ExportDateB GA BallotNumberB GA DocNumberB GA First NameB GA Last NameB GAMembership TypeB GAComment Number@@?A Layout #1A Layout #1B$$$$ @BBB@ ABCDEFGX501"F23945D6738!9#!: T 9 C    " [Z%Z%D&7)Y7 8I!;@I"J[#M1[$\m%_$m&n'q0 A)!)*;-K;<M?BMN_QH_`q cKq Br uL  0 - : 9O4Data grant pending is no longer part of baseline MACB9/5/2001EYigalFLeibaGMemberH237I 8/28/2001JTechnical, Non-bindingK29L7M 6.2.2.4.4.1.1NFMove table 145, so it refers to all PHY types, not just single carrierOcAt the moment there is no claim form any of the other PHY types that this table does not suit them.P2238B9/5/2001ESubbuF PonnuswamyGMemberH238I 8/27/2001J EditorialK29L24M 6.2.2.4.4.1.1NDelete references to "If inferred length =0, then it is a Data Grant Burst Type Pending" Fix typos in "... Burst Type X", where X should correspond to the Data Grant Burst Type (last column for UIUC 4-9) Line 45: second column, it should be 12-14OGData grant pending is not part of baseline MAC Typos for UIUC types 4-9B9/5/2001ELeiFWangGMemberH239I 8/27/2001JTechnical, Non-bindingK30L42M6.2.3.2NNadd the subclause 6.2.3.2 as described in the contribution 80216abc-01_19.doc.OLto efficiently support multiple MPDU concatenation in a single transmission.B9/5/2001ELeiFWangGMemberH240I 8/27/2001JTechnical, Non-bindingK30L43M 6.2.3.4.2NPadd the subclause 6.2.3.4.2 as described in the contribution 80216abc-01_19.doc.ONto improve the efficiency of processing the packing MPDUs at the receiver sideB9/5/2001EMikaFKasslinGMemberH241I 8/27/2001JTechnical, Non-bindingK31L57M 6.2.7.6.1.1NZAdd a new clause 6.2.7.6.1.1.4 (including subclauses) as shown in 802164c-01_39, comment 3ONo such a clause exist, and one is needed. The given text describes the relevance of scheduling information in mesh mode, and defines the network synchronization mechanism. Further, it describes the frame structure of the mesh mode. B9/5/2001EVladimirFYanoverGMemberH242I 8/27/2001J EditorialK33L5M6.2.4 A1. Insert the content of the section 6.3 of the document IEEE 802.16abc-01/01 immediately after the title of the section "6.2.4 ARQ - 2-11 GHz Bands Only". 2. Replace the text of the section "Block Numbering Based Retransmission Scheme" with the text from the document "ARQ Changes for 802.16abc-01/01r1" by V.Yanover 3. Replace the Figures 1-4 under the title "Block Numbering Based Retransmission Scheme" with the Figures 1-4 of the document "ARQ Changes for 802.16abc-01/01r1" by V.YanovBer t AComments resolution and motions approved at the Session #14 did not request for deletion of the whole section 6.3 of the document IEEE 802.16abc-01/01. Nevertheless, this section has been deleted from the document and does not appear in 01/01r1. I cosider it as an editorial mistake, so the content of the section 6.3 of the document IEEE802.16abc-01/01 should be restored BEFORE doing any further changes in ARQ material. According to IEEE rules, the comments and motions are processed editorBmially IN THE SAME ORDER as they were resolved and approved. The document "ARQ Changes for 802.16abc-01/01r1" by V.Yanover referenced below contains the material that implements the comments resolved at the Session #14. This material should be processed after the recovery of the ARQ section, but before the comments submitted between Session #14 and Session #15. [ AThe Editor finds the motivation for priority treatment of this comment unwarranted (even though it will be the first comment dealt with due to natural ordering). The instructions to the sub-editor were to remove any and all material not agreed on by the required voting procedure. Although this, despite repeated prodding, has not been accomplished consistently (section 6.2.7.7.2 comes to mind), the removal of the material in question was consistent with those instructions. The current texBt represents the resolutions as shown in the minutes, whereas the minutes do not mention the acceptance of the material in quesiton.r B9/5/2001EYigalFLeibaGMemberH243I 8/28/2001JTechnical, BindingK33L5M6.2.4NPInsert the contents of document 80216abc-01_22 to be the text under this sectionOSpecify an ARQ mechanismP2239 B9/5/2001EMikaFKasslinGMemberH244I 8/27/2001JTechnical, Non-bindingK35L3M 6.2.2.4.33Y NpReplace the current clause 6.2.2.4.33 with clauses 6.2.2.4.33 - 6.2.2.4.37 as shown in 802164c-01_39, comment 2AThere is no such a description in the document and MAP/schedule message relevance is different in mesh mode from the one in TDD/FDD in P-MP.@A 33 B9/5/2001EYigalFLeibaGMemberH245I 8/28/2001JTechnical, BindingK37L3M6.2.7.7NDelete the entire section. Move the TLV listed under section 6.2.2.7.2.5 to belong to the RNG_REQ message. Move the TLV listed under sections 6.2.2.7.2.6 and 6.2.2.7.2.7 to belong to RNG_RSP message.  AThe procedure described in this section is mostly a repetition of the the current network entry process as described in section 6.2.9 of the current 802.16.1 standard draft (document IEEE P802.16/D4-2001). The purpose of dynamic frequency selection can be acheived using the existing network entry procedure, and the upgraded RNG_REQ and RNG_RSP MAC messages with the extra TLVs for dynamic frequency selection. Note also that DFS should apply equally to OFDM and OFDMA PHY.P2240 B9/5/2001EMikaFKasslinH246I 8/27/2001JTechnical, Non-bindingK37L11M 6.2.7.7.2NAdd the following sentece after the first one: "In some regulatory domains DFS is a mandatory functionality that is required to detect e.g. primary users of the band, and avoid usage of the frequencies occupied."OVRelate this text to the regulatory requirements that may apply to TG4 systems some dayB9/5/2001EMikaFKasslinGMemberH247I 8/27/2001JTechnical, Non-bindingK37L27M 6.2.7.7.2!NInsert a new subsection called e.g. "Primary User Detection" to describe mechanisms mandatory in some bands in some regulatory domains. OSame as in the previous comment. Further, the current DFS text discusses only co-existence and automatic network configuration issues. Let's make it possible to operate TG4 devices in Europe some day.B9/5/2001EMikaFKasslinGMemberH248I 8/27/2001JTechnical, Non-bindingK37L31M 6.2.7.7.2.2NInsert the following sentence at the end of the clause: "Further, in some regulatory domains one has to avoid channels occupied by primary users, no matter what is S/N level."O!Same as in the previous comments.B9/5/2001EYigalFLeibaGMemberH249I 8/28/2001JTechnical, BindingK39L18M6.2.7.8NDelete the headlines 6.2.7.8.1 and 6.2.7.8.2 and add after line 24 a sentence saying "Support of the messages and procedures under this section is optional for compliant BS and SS" "A4The issue interference mitigation should apply the same to OFDM and OFDMA. It is suggested to make support of provisions for interference mitigation optional because they place an implementation burden on both SS and BS, while the usability and efficiency of the proposed mechanisms requires further study.4P2241B9/5/2001EMikaFKasslinGMemberH250I 8/27/2001J EditorialK41L53M6.2.7.9N Delete the whole clause 6.2.7.9.OdSimilar text has been proposed to be inserted into a different part of the standard (see comment 3).B9/5/2001EJung JeFSonGMemberH251I 8/27/2001J EditorialK48L23M 6.2.7.11.2.3NI suggest to change add "with ranging codes randomly chosen from Secondary Ranging domain" after "... ranging process as done on the first entry" at the third pharagraph, clause 6.2.7.11.2.3 .OAfter Initial Ranging, Secondary Rangng Code should be used until ranging is successful since maintenance CID's should be transmitted only at the first ranging response.P2207!#B9/5/2001EYigalFLeibaGMemberH252I 8/28/2001JTechnical, BindingK51L17M 6.2.7.12.2ADelete sub-titles 6.2.7.12.1 and 6.2.7.12.2. Replace the the text under this section with the following: "When a power change for connection CID is needed, use UIUC 13 which will be defined as the fast-power-control UIUC. The structure in the MAP message will contain the following elements 1) CID - 16 bit 2) UIUC(=13) - 4 bit 3) Power control - 8 bit The power control field is an 8-bit signed integer expressing the change in power level (in dB units) that the SS should apply to coorrect B"it's current transmission power." OgThe power control belongs to the uplink MAP, also the suggested correction preserves the expansion DIUCP2237B9/5/2001EYigalFLeibaGMemberH253I 8/28/2001JTechnical, BindingK53L3M6.2.7.13N6Remove headlines 6.2.7.13.1, 6.2.7.13.2 and 6.2.7.13.3O\The adaptive antenna support (at least form the current text) seems to support all PHY typesP2242B9/5/2001"$EMikaFKasslinGMemberH254I 8/27/2001JTechnical, Non-bindingK56L31MAfter 6.2.7.15N3NContribution will be made governing this section. Accept rewritten section as contribution, with revamped equations and figures. Document with text/equations/figures native from Framemaker will be provided in addition to the contribution.A;Single Carrier Alamouti section needs reformatting within Framemaker. Equations were cut and pasted directly from Word, and therefore look terrible. Figures 213 and 214 have text which is too small to be read; therefore, figures need to be touched up. Text also needs to be more normative, rather than explicative.;P22354B9/5/2001EBrianFEidsonGMemberH279I 8/27/2001JTechnical, Non-bindingK137L3M8.3.=?4AAdd section headings (much text TBD) Section Heading: Ramp up/down Requirements Text: During ramp up and ramp down of burst power, the output power should be within TBD dB of the desired average power within TBD symbols. This settling time should factor into consideration transients due to the transmit filter impulse response. Subsection Heading: Spurious Emissions during burst On/Off transients Text: Each transmitter must control spurious emissions, prior to and during ramp up and durB ing and following ramp down, before and after a burst in a TDM/TDMA scheme. Spec TBD. Section Heading: Out of Band Spurious Emissions Text: Out of band spurious emissions should conform with Section 8.3.2, which describes regulatory spectral masks and bandwidths. >@4AYSection on System Performance Requirements does not contain power ramp up and settling time requirements, or average power level maintenance requirements during a burst. It also doesn't have any guidelines on Spurious emissions during ramp up, or references toon out of band spurious emissions (via spectral masks) for operation during a burst.YP22365B9/5/2001E AudehFMalikGMemberH280I 8/27/2001JTechnical, Non-bindingK137L34M 8.3.5.17.1.3NyInsertion of rows with other channel bandwidth options such as 125 kHz, 200 kHz, 400 kHz, etc... into Tables 164 and 166.AdNarrower channel bandwidths that those shown should be entered in Table 164 and in other tables in section 8.3.5.17. Field deployments have shown the RF advantage, among other things, of narrower channels is significant and these options should be included. Suggestion is down to 125 kHz, matching the smallest bandwidth allocation of Table 148 on page 61.dP22286B9/5/2001EJoriF ArrakoskiGMember?A6H281I 8/27/2001JTechnical, Non-bindingK142L1M8.3.6NfAdd a table including the most common set of used parameters and calculate the corresponding bitrates.OSince OFDM parameters, channel bandwidths and coding schemes are set there should be section with basic performance parameters like raw data throughput.7B9/5/2001ETalFKaitzH282I 8/27/2001JTechnical, Non-bindingK142L32M8.3.6.3AAdd the following text at 8.3.6.3 and in 8.3.6.4.2 Introduction The subcarrier based polling (SBP) mechanism allows several SS's to request bandwidth simultaneously. The mechanism uses OFDMA techniques to achieve a multiple access capability. In this approach every SS is assigned a distinct group of subcarriers. The SS requests bandwidth by energizing the subcarriers in the assigned group. When the BS detects the subcarrier polling request, it sends a unicast polling message to the addr@B7Bessed to the corresponding SS, at the earliest opportunity. The SBP transmission occurs in a well known part of the uplink transmission. To allow all the stations to be polled in single SBP period, this period may span several OFDM symbol times. To avoid fades, the subcarrier assignment is varied from poll to poll. The Subcarriers are arranged in a regular grid, and are transmitted with relative phases to insure very low PAPR ratio for each transmitted signal. This increases the immunityC of the mechanism to ATPC errors, by increasing the clipping margin in the receiver. Details The SBP mechanism operates as follows: Let NmaxSS denote the maximum number of SSs. Let Nsc denote the number of active subcarriers. Let us assume that NmaxSS is a multiple of NSC or is increased to be such. Let NSBP_SC denote the number of subcarriers assigned to every SS. The SBP period requires NmaxSS/ (Nsc/NSBP_SC) OFDM symbol periods. In each such symbol time, there are Nsc/NSBP_SC possibAC7Dle frequency grids, over which a station can transmit. At registration the BS assigns to each SS a number SSID in the range 0NmaxSS-1. With each multicast polling the BS broadcasts a random number in the same range. The SS uses these values to determine its time and frequency allocation by: a. Computing n= (R+SSID) mod NmaxSS b. Computing k= floor(n/ Nsc*NSBP_SC) to be the symbol number c. Computing l= n mod (Nsc/NSBP_SC) to be the grid number Since during SBP transmission only a fracEtion of subcarriers are energized, the overall transmitted power is divided between a smaller number of subcarriers, relative to the data transmission modes. Thus power concentration is possible. However to avoid interference to adjacent cells, the power concentration over the data mode should be no more then 12dB. The relative phases of the transmitted subcarriers is determined by the following sequences: For NSBP_SC=8 : { 1, 1, -1, 1} For NSBP_SC=8 : { 1, 1, -1, 1, 1, 1,1,-1} For NBD7FSBP_SC=16 : { 1, 1, -1, 1, 1 , 1 ,1 ,-1 ,1 , 1 , -1 , 1 , -1 , -1 ,-1 ,1} The values of NSBP_SC are given in the table below: FFT size NSBP_SC value 64 4 256 8 512 16  {AA . The subcarrier based polling mechanism was deleted from 01/01r1 draft. It appeared in section 8.3.9.3.2 of 01/01 draft where two alternative mechanisms were proposed for fast polling in unlicesned bands. These sections should be reinserted. B. Fast polling schemes are very advantegeous to licensed and unlicensed bands. They greatly improve the system efficency by allowing many users to request bandwidth simuletanously . Moreover the OFDM moudlation schemes can be simply exetended to Bsupport multiple access transmissions. In particular, one such technique is the Subcarrier Based Polling (SBP) technique described in the remedy section. Such mechanism should be added to the OFDM section of the licensed and unlicensed bands. 8B9/5/2001EManoneetCE8FSinghGMemberH283I 8/27/2001JTechnical, Non-bindingK152L59M 8.3.6.2.3.3NUChange r_1 to r_1* in Eq. 18. Change s_0 and s_1 in Eqs. 18 and 19 to s_0' and s_1'.OEq. 18 is wrong. s_0 and s_1 are already used to denote the transmitted signals. A prime or tilde should be used to denote that the LHS in (18) and (19) are estimates of these signals.9B9/5/2001EJoeFKwakGOtherH310I9/4/2001JTechnical, Non-bindingK153L45M 8.3.6.2.4A8.3.6.2.4 Physical layer ARQ This section defines the block sizes, timing and synchronization needed to support physical layer ARQ for OFDM Phy layers. 8.3.6.2.4.1 Physical layer ARQ timing and synchronization This section contains the detailed tables listing the PARQ block sizes and timing to operate with the various bandwidth/coding/modulation combinations which are compatible with OFDM physical layer. Tables are TBD. 8.3.6.2.4.2 Fast feedback channel modulation and coding This secDFv9Btion contains the detailed tables which define the uplink fast feedback channel burst modulation and coding for the defined PARQ block sizes compatible with TDD and FDD modes in the OFDM physical layer. Tables are TBD.OqNew section needed, to be placed after Almouti STC decoding section, to describe new physical layer ARQ for OFDM.P2255:B9/5/2001ENicoFvan WaesGMemberH284I 8/27/2001JTechnical, Non-bindingK154L57M 8.3.6.3.2.1.1NAdd: Preambles are not randomized.The seed value must be used to calculate the randomization bit,which is combined in an XOR with the first bit of data of each burst.The randomizer sequence is applied only to information bits.O.Clarification and consistency with 8.2.4.4.3 P2209;B9/5/2001ETalFKaitzGMemberH311I9/4/2001JTechnical, Non-bindingK155L59M 8.3.6.3.2.1.2N,Change the RS+CC scheme to CC only scheme. EG;AThe Physical layer of the OFDM air inteface specifies a conctenated FEC scheme. The FEC sheme is a concatenation of a outer Reed-Solomn (RS) code and an inner k=7 convoultional code (CC). The systems parameter are such that the block length is excatly equivalent to one OFDM symbol. The resulting blocks are smaller then those which are normally applied to such conctenated scheme. As a result the FEC scheme is not optimal. As was shown by several members of the FEC Ad-Hoc group, in maBny cases the concatenated scheme (RS+CC) performed the same as or worse then the a FEC with a CC only. This was most apparent in cases with low code rate and modulation and for packet error rates of 10^-2...10^-3. For higher modulations schemes and lower PER the RS+CC out perfromed the CC. It was suggeted that the performance of the RS+CC scheme can be improved by using soft output viterbi decoder. However it is judged to be too much complex.P2258ion was omitted by the editor of 01/01r1 document without any relevant comment resolution and without any explanation. So this omission should be considered as an editorial mistake and fixed editorially. After that there is no more reason to reject the section that describes the support of this useful feature in MAC.,[The Editor disagrees with the accusations leveled in point 2. The material in question was removed in accordance with resolution of comment 163 which reads "Section 8.3.9.3.2. shall be removed". >B9/5/2001EMikeFPaffGOtherH287I 8/27/2001JTechnical, Non-bindingK164L23M 8.3.6.3.4NOn page 164, line 24, add the following: Mode B - OFDMA is defined exclusively for continuous downstream as defined in 8.3.4.2.1.IK>AThe OFDMA modulation is not compatible with "Mode B Burst Downlink" as defined in 8.3.4.2.2. 1. There is no practical way for the subscriber to derive downlink timing, and start-of -frame information in Burst Downstream mode (8.3.4.3.1.2). If there were a dedicated preamable (one symbol of all pilots), a matched filter could be used to derive start-of-frame information. If there were symbol boundry continuity from one frame to the next, narrow band algorthms could be used to derive symBbol timing. Without either of these conditions, the subscriber has no practical way to identify the start-of-frame. 2. The long OFDMA symbol duration is inconsistent with the allowable frame time defined in Table 156 for Mode B Burst Downstream. For example, in OFDMA mode with 2048 Nfft, and cyclic redundancy of 1/8, in the 6 MHz channel, the symbol duration is 336 microseconds. Every message requires a minimum of 4 symbols, which is 1344 microseconds. If we select a frame time of 3 JL>Cmilliseconds, there is only time for one upstream burst of four symbols and one downstream burst of four symbols. This results in an excessive guard interval of 156 microseconds. It is not possible to select a longer frame that will support larger upstream and downstream bursts. To summarize, the coarseness of the OFDMA symbol duration results in inefficient bandwidth use when the frame size is restricted to multiples of 0.5 milliseconds up to 5 milliseconds.?B9/5/2001ENicoFvan WaesGMemberH288I 8/27/2001JTechnical, Non-bindingK165L41M 8.3.6.3.4.1.1N Remove step 3Ostep 4 uses P_s[ k_mod(N_elements)] + ..... hence the index into P_s[ ] never exceeds N_elements {P_s} = {PermutationBase_s}already starts of N_elements elements, so there is never any need for concatenation.P2218@B9/5/2001ENicoFvan WaesGMemberH289I 8/27/2001JTechnical, Non-bindingK167L14M 8.3.6.3.4.1.2N0replace N_subchannel = 53 with N_subchannel = 48KMn@ON_subchannel was defined in 8.3.6.3.4.1.1 (point 3 in the permutation algorithm) as the number of DATA carriers per channel. The number of carriers per symbol is 53 (N_groups), but the number of data carriers is only 48.P2220AB9/5/2001ENicoFvan WaesGMemberH290I 8/27/2001JTechnical, Non-bindingK167L45M 8.3.6.3.4.1.3N4Replace 1K example with 2K example in 80216abc-01_20O1K mode is gone.P2219BB9/5/2001EMikeFPaffGOtherH291I 8/27/2001J EditorialK169L8M 8.3.6.3.4.2.2Ar1. Table 180. Change column heading "Block Size (bytes)" to "Uncoded Block Size (bytes)" 2. Table 180 Add new column with heading "Coded Block Size (bytes)". Data should be 36, 36 72,72, 108, 108 3. Table 182 Change title to "Bit Interleaved Block Sizes" 4. Table 182 Change column heading " 144 Symbol Interleave" to " Coded Bits per Bit Interleaved Block"rLNBOIn this section, the word "Block" is used to mean three different things: 1. Uncoded Block 2. Coded Block 3. Bit Interleaved Block It is very difficult to understand the structure of the bit interleaver.CB9/5/2001EKi HoFChungGOtherH292I 8/27/2001J EditorialK170L22M 8.3.6.3.4.3.1OPRBS polynomial generator shall be changed to x^15+x^7+x^4+x+1 from x^15+x^7+x^4+1. In Figure 234, register 0 has to be deleted. PRBS polynomial generator of document 80216ab01-01r1 don't generate the PRBS sequence.[=Editor deleted register 0 (editor error in r1-draft creation)DB9/5/2001EJerryFKrinockGMemberH293I 8/27/2001JTechnical, Non-bindingK170L61MSeveral SectionsNThe number of active long ranging codes should be specified dynamically by the base station, and the default number should be set to one.O]See contribution titled "Comments on OFDMA Ranging Scheme described in IEEE 802.16ab-01/01r1"EB9/5/2001EMikeFPaffGOtherH294I 8/27/2001J EditorialK172L32M 8.3.6.3.4.4.1MOgEA1. Add the following sentences to section 8.3.6.3.4.4.1 Each encoded frame of downlink information is transmitted on one subchannel over a period of three consecutive symbols. A downstream frame consists of N symbols, where the first symbol contains the carrier group, PHY control and uplink map. The remaining N-1 symbols containing data are orgainized as an integer number of groups of three symbols. 2. Modify figure 236 to illustrate encoded frames occuring over three consecutive syBmbols. OThe description of the downlink OFDMA framing structure should reflect the fact that frames are transmitted in groups of 3 symbols. Figure 236 further confuses the description by appearing to illustrate frames as groups of two or four symbols.FB9/5/2001ENicoFvan WaesGMemberH295I 8/27/2001JTechnical, Non-bindingK173L29M 8.3.6.3.4.4.1NPFAAdd from 8.3.4.5.2.3: page 92 line 9 through 18: Figure 175 and " There are two alternatives to transmit the DL\UL MAP: * To take advantage of the option of forward power control, and robust transmission of frame control information, the transmission of the DL\UL MAP can be done by using 1-2 sub-channels for the duration of the whole frame while power boosting the used carriers. * To use the basic method of the OFDM case, but with size optimization. This means that the DL\UL MAPB shall be transmitted at the beginning of the frame, using all or part of the sub-channels. " and " The alternative used will be indicated in the in the first bit of the DL Frame Prefix ( see clause 8.3.4.5.2.3) "OEThis material is duplicate in PHY-MAC and PHY, consolidate in PHY. P2217GB9/5/2001ENicoFvan WaesGMemberH296I 8/27/2001J EditorialK173L62M 8.3.6.3.4.4.2NAdd Figure 172 as example here.OFNote: A separate comment to delete 172 from the PHY-MAC has been made.OQcGP2215HB9/5/2001ENicoFvan WaesGMemberH297I 8/27/2001JTechnical, Non-bindingK174L47M 8.3.6.3.5.2.1AReplace 8.3.6.3.5.2.1&2 with the following: ------------------------------------------- 8.3.6.3.5.2.1 Downlink The DL frame format is described in Figure 175. However, each carrier-group is assigned entirely to one system only on a per OFDM symbol basis. Hence, a sub-channel equals a carrier-group This in contrast to mode B, where the carriers in each carrier-group are assigned to multiple systems, and sub-channels consist of carriers from multiple carrier-groups. 8.3.6.3.5.2.2 Uplink In PRHBthe UL, an allocation may be a control or data allocation. Each allocation consists of one or more adjacent (in frequency) subchannels in an OFDM symbol, persistent over one or more OFDM symbols. A control allocation consists of one or more in time consequtive control subchannels. A data allocation consists, consequtive in time, of a preamble and data subchannels. --------------------------------------------- 8.3.6.3.5.2.3 should be handed to a clause-editor to be entirely rewritten. ItC needs substantial additional information on how to do this type of rotation in TDD, and it shouldn't use the word frame for allocations. How it will fit under the MAC etc.. (i.e. it needs definition on how this shifted superframe structure fits in with TX/RX boundaries)QSdHA Clarification and cleaning up of redundant material. If other comments are accepted, Figure 175 will have been moved to mode B (under Figure 236). I tried to stay away from using the word "frame" here, which seems to be confusing with the current concept of framing.  P2221IB9/5/2001EYigalFLeibaGMemberH298I 8/28/2001JTechnical, BindingK178L43M 8.3.6.4.2.1N(Change the occurences of '6uS' to '12uS'OYThe current specification contradicts with the channels listed in table 172, in page 150.P2246JB9/5/2001ENicoFvan WaesGMemberH299I 8/27/2001JTechnical, Non-bindingK181L26M 8.3.6.4.2.3.1NAdd footnote to "Europe" stating: Current applicable regulations do not allow this standard to be operated in the indicated band. P2222KB9/5/2001ENicoFvan WaesGMemberH300I 8/27/2001JTechnical, Non-bindingK183L34M 8.3.6.4.2.3.2RTKAfChange table 186 to read -------------------------------------------------------------- |20 | 9.5 | 10.5 | 19.5 | 29.5 | |10 | 4.5 | 5.5 | 9.5 | 14.5 | | (5) | 2.2 | 2.8 | 7.2 | 9.8 | ---------------------------------------------------------------fP2223LB9/5/2001ESeanFSonanderH301I 8/27/2001JTechnical, Non-bindingK188L9M 8.3.6.4.2.6NThe change suggested is the replacement of table 192 - Channel Coding schemes, with that in the submitted document 802164c-01_38.doc OAThe change of Table represents the views of the AD-HOC-FEC group.MB9/5/2001ENicoFvan WaesGMemberH312I9/4/2001JTechnical, BindingK199L1MA.2N3Replace A.2 with comment 1 text in 802164c-01_40. OrThe interference study needs to be more comprehensive, specifically if .16b is to be ever accepted outside the US.P2256NB9/5/2001ENicoFvan WaesGMemberH302I 8/27/2001S_NJTechnical, Non-bindingK206L44MA3NDelete clause A.3OJNot sure what antenna diversity/beamforming 101 is doing in this standard.P2224OB9/5/2001EYigalFLeibaGMemberH303I 8/28/2001J EditorialK215L60MA.5N7Change the section title to read 'FDD/TDD Co-existance'OCNothing in the section has anything to do with either OFDM or OFDMAP2247 @@@A Layout #1A Layout #1B$$$$@:A  $,.YesNo/,  , : AM PMB  C  $,.YesNo/,  , : AM PMD  E  $,.YesNo/,  , : AM PMF  G  $,.YesNo/,  , : AM PMH  I  $,.YesNo/,  , : AM PM