Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0JEXCOUNTER  DB G @JJU_isACE@ @OO AAA B N N!O"A#M$O%A&O'A(N) N*"N+#,&A-A.'N/(A0)A1C2*A3-N4.A5A60G71B8D9F:2E;4A<5A=B>6A?C@8OA:OB=@C>AD?PE@BFAGCAHFNI@!@-HBAM3016AUG95@F AAzHH(FG(HH(d}HzA'dDFVD`p$_N^NuH&o>/*/$/"/" ABP EBP B0 g, S<Fn$0HSL<"ST A0 E0 B0LNuNVH0(. zYO/nH 06\ H0SunMonTueWedThuFriSatJanFebMarAprMayJunJulAugSepOctNovDec MF    8/30/2001@ BALLOTNUMBERCHANGE COMMENT DATE COMMENT NUMBER COMMENT TYPE COMMENTARY VERSION DOCNUMBER EXPORTDATE FIRST NAME LAST NAMEMEMBERSHIP TYPEREASONSECTION STARTING LINE NUMBER STARTING PAGE NUMBER              !ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]EPro 5.0F!2(M1,,./: AM PMYyTtNnFfNALL OTABSP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , } ABCDEFGHI J K L M NOPQRSTUVWXYZ[\]    !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFPBUUX  $,.YesNo/,  , : AM PM HelveticaGenevaArial  DHACommentary VersionB GA ExportDateB GA BallotNumberB GA DocNumberB GA First NameB GA Last NameB GAMembership TypeB GAComment NumberB G A Comment DateB G A Comment TypeB G AStarting Page NumberB G AStarting Line NumberB G ASectionB GAChangeB GAReasonB GACounter J'A1.3DIEEE 802.16ab-01/07`@A  DIEEE 802.16ab-01/01r1``,.YesNo/,  , : AM PMB   C  $,.YesNo/,  , : AM PMD   E  $,.YesNo/,  , : AM PMF   G  $,.YesNo/,  , : AM PMH   I  $,.YesNo/,  , : AM PM _ [COUNTERDECISION OF GROUP DOCNUMBEREDITOR'S ACTION ITEMSEDITOR'S ACTIONS EDITOR'S NOTEEDITOR'S QUESTION EXPORTDATE FIRST NAMEGROUP'S ACTION ITEMS GROUP'S NOTES LAST NAMEMEMBERSHIP TYPEREASONREASON FOR GROUP DECISIONREASON PROPOSEDRECOMMENDATION RESOLUTION BYRESOLUTION OF GROUPRESOLUTION PROPOSEDSECTION STARTING LINE NUMBER STARTING PAGE NUMBER               GA Resolution byB GARecommendationB GAResolution ProposedB GAReason ProposedB GAResolution of GroupB GADecision of GroupB GAReason for Group DecisionB GA Group's NotesB GAGroup's Action ItemsB GAEditor's ActionsB GA Editor's NoteB GAEditor's QuestionB GAEditor's Action ItemsB G B BCommentary VersionD ExportDateF BallotNumberH DocNumberJ First NameL Last NameNMembership TypePComment NumberR Comment DateT Comment TypeVStarting Page NumberXStarting Line NumberZSection\Change^Reason`Counterb Resolution bydRecommendationfResolution ProposedhReason ProposedjResolution of GrouplDecision of GroupnReason for Group Decisionp Group's NotesrGroup's Action ItemstEditor's Actionsv Editor's NotexEditor's QuestionzEditor's Action Items @BBAt  !"#$%&'()*+,-./0123456789tB%468        "$&( "$&(@J J   K  $,.YesNo/,  , : AM PML   M  $,.YesNo/,  , : AM PMN   O  $,.YesNo/,  , : AM PMP   Q  $,.YesNo/,  , : AM PMR   S  $,.YesNo/,  , : AM PMT    U  $,.YesNo/,  , : AM PMV   W  $,.YesNo/,  , : AM PMX   Y  $,.YesNo/,  , : AM PMZ   [  $,.YesNo/,  , : AM PM\   ]  $,.YesNo/,  , : AM PM^    _  $,.YesNo/,  , : AM PM`   a  $,.YesNo/,  , : AM PMb   c  $,.YesNo/,  , : AM PMd   e  $,.YesNo/,  , : AM PMf   g  $,.YesNo/,  , : AM PMh    i  $,.YesNo/,  , : AM PMj   k  $,.YesNo/,  , : AM PMl   m  $,.YesNo/,  , : AM PMn   o  $,.YesNo/,  , : AM PMp   q  $,.YesNo/,  , : AM PMr    s  $,.YesNo/,  , : AM PMt   u  $,.YesNo/,  , : AM PMv   w  $,.YesNo/,  , : AM PMx   y  $,.YesNo/,  , : AM PMz   B 2001/08/30EMikaFKasslinGMemberH234I 2001/08/27JTechnical, Non-bindingK18L12M1.4.1N[Replace the whole subclause 1.4.1 with subclause 1.4.1 as shown in 802164c-01_39, comment 1OfClarify the introductory subclause and make it more consistent with the rest of the mesh descriptions.B 2001/08/30ELeiFWangGMemberH235I 2001/08/27JTechnical, Non-bindingK23L20M6.2.2NNadd a subclause 6.2.2.1.3 as descirbed in the contribution 80216abc-01_19.doc.OLto efficiently support multiple MPDU concatenation in a single transmission.B 2001/08/30ESubbuF PonnuswamyGMemberH236I 2001/08/27J EditorialK28L17M 6.2.2.4.4.1.1NIDelete the portion of Figure 132 -??? that refers to "data grant pending"O4Data grant pending is no longer part of baseline MACB 2001/08/30EYigalFLeibaGMemberH237I 2001/08/28JTechnical, Non-bindingK29L7M 6.2.2.4.4.1.1NFMove table 145, so it refers to all PHY types, not just single carrier@ Q*,.02468 v        "$&(*,.02468        "$&( "$&( E()*+!,-./301F23*45967# 8 9: T 2 C     TU$U#D&6(S5 8H!:6G"JZ#L&Y$\l%^k&n~'p#} A('*:,B9<L>8KN^PB]`p bEo Br tF  $ % 3 2I @OcAt the moment there is no claim form any of the other PHY types that this table does not suit them.P2238B 2001/08/30ESubbuF PonnuswamyGMemberH238I 2001/08/27J 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-9B 2001/08/30ELeiFWangGMemberH239I 2001/08/27JTechnical, 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.B 2001/08/30ELeiFWangGMemberH240I 2001/08/27JTechnical, 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 sideB 2001/08/30EMikaFKasslinGMemberH241I 2001/08/27JTechnical, 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. B 2001/08/30EYigalFLeibaGMemberH242I 2001/08/28JTechnical, BindingK33L5M6.2.4NPInsert the contents of document 80216abc-01_22 to be the text under this sectionOSpecify an ARQ mechanismP2239 B 2001/08/30EVladimirFYanoverGMemberH243I 2001/08/27J 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 B 2001/08/30EMikaFKasslinGMemberH244I 2001/08/27JTechnical, Non-bindingK35L3M 6.2.2.4.33NpReplace 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 2OThere 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.  u B 2001/08/30EYigalFLeibaGMemberH245I 2001/08/28JTechnical, 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 B 2001/08/30EMikaFKasslinGMemberH246I 2001/08/27JTechnical, Non-bindingK37L11M 6.2.7.7.2!M NAdd 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 dayB 2001/08/30EMikaFKasslinGMemberH247I 2001/08/27JTechnical, Non-bindingK37L27M 6.2.7.7.2NInsert 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.B 2001/08/30EMikaFKasslinGMemberH248I 2001/08/27JTechnical, Non-bindingK37L31M 6.2.7.7.2.2 "NInsert 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.B 2001/08/30EYigalFLeibaGMemberH249I 2001/08/28JTechnical, 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.4P2241B 2001/08/30EMikaFKasslinGMemberH250I 2001/08/27J 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).B 2001/08/30EJung JeFSonGMemberH251I 2001/08/27J 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.P2207B 2001/08/30EYigalFLeibaGMemberH252I 2001/08/28JTechnical, BindingK51L17M 6.2.7.12.2"$ADelete 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 DIUCP2237B 2001/08/30EYigalFLeibaGMemberH253I 2001/08/28JTechnical, 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 typesP2242B 2001/08/30EMikaFKasslinGMemberH254I 2001/08/27JTechnical, Non-bindingK56L31#%MAfter 6.2.7.15N65A/1. Insert the text of the section 8.3.9.3.2.1 "Subcarrier-based polling using on-off keying" of the document 802.16abc-01/01 into the document 802.16abc-01/01r1as section 8.3.6.3.3.7 2. Insert the text from the document 802.16abc-01/02 into the of the document 802.16abc-01/01r1 as section 8.3.4.6 /AThis is to re-submit the comment #81 resolved at the Session #14 as "rejected' with "Recommendation to have sub-carrier polling approach submitted as a Joint TG 3-4 PHY contribution for consideration at Session #15". Aditional information: 1. The reson for the reject was that the corresponding feature is absent in PHY. 2. The PHY part of the document 01/01 contains the section 8.3.9.3.2.1 "Subcarrier-based polling using on-off keying" that figures the mentioned functionality. This sect=?5B>ion 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". 6B 2001/08/30EMikeFPaffGOtherH287I 2001/08/27JTechnical, 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.>@6AThe 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 ?A6Cmilliseconds, 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.7B 2001/08/30ENicoFvan WaesGMemberH288I 2001/08/27JTechnical, 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.P22188B 2001/08/30ENicoFvan WaesGMemberH289I 2001/08/27JTechnical, Non-bindingK167L14M 8.3.6.3.4.1.2N0replace N_subchannel = 53 with N_subchannel = 48@Bt8ON_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.P22209B 2001/08/30ENicoFvan WaesGMemberH290I 2001/08/27JTechnical, Non-bindingK167L45M 8.3.6.3.4.1.3N4Replace 1K example with 2K example in 80216abc-01_20O1K mode is gone.P2219:B 2001/08/30EMikeFPaffGOtherH291I 2001/08/27J 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"rAC:OIn 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.;B 2001/08/30EKi HoFChungGOtherH292I 2001/08/27J 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)B 2001/08/30ENicoFvan WaesGMemberH295I 2001/08/27JTechnical, Non-bindingK173L29M 8.3.6.3.4.4.1CE>AAdd 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. P2217?B 2001/08/30ENicoFvan WaesGMemberH296I 2001/08/27J 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.DFf?P2215@B 2001/08/30ENicoFvan WaesGMemberH297I 2001/08/27JTechnical, 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 EG@Bthe 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)FHm@A 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.  P2221AB 2001/08/30EYigalFLeibaGMemberH298I 2001/08/28JTechnical, 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.P2246BB 2001/08/30ENicoFvan WaesGMemberH299I 2001/08/27JTechnical, 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. P2222CB 2001/08/30ENicoFvan WaesGMemberH300I 2001/08/27JTechnical, Non-bindingK183L34M 8.3.6.4.2.3.2GICAfChange 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 | ---------------------------------------------------------------fP2223DB 2001/08/30ESeanFSonanderGMemberH301I 2001/08/27JTechnical, 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.EB 2001/08/30ENicoFvan WaesGMemberH302I 2001/08/27JTechnical, Non-bindingK206L44MA3NDelete clause A.3OJNot sure what antenna diversity/beamforming 101 is doing in this standard.P2224FB 2001/08/30EYigalFLeibaGMemberH303I 2001/08/28J EditorialK215L60MA.5HFN7Change 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