Doc.: IEEE 802.11-06/1305r5 Submission October 2006 Tomoya Yamaura (Sony)Slide 1 Comments...

October 2006

Tomoya Yamaura (Sony)

Slide 1

doc.: IEEE 802.11-06/1305r5

Submission

Comments Categorization without Assignee in BF&A ad hoc

Notice: This document has been prepared to assist IEEE 802.11. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.

Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.11.

Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <[email protected]> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <[email protected]>.

Date: 2006-10-24

Name Company Address Phone email Tomoya YAMAURA

Sony Corporation

6-7-35 Kitashinagawa, Shinagawa-ku Tokyo, 1410001 Japan

+81-3-6409-3201

[email protected]

Authors:

October 2006


Slide 2

doc.: IEEE 802.11-06/1305r5

Submission

Abstract

Beamforming & adaptation ad hoc under TGn is resolving assigned comments from LB#84.

We still have comments which don’t have assignee(s).

In this submission, I categorize these comments and imply how to proceed them from now on.

[Updated to incorporate our progress at Portland]

October 2006


Slide 3

doc.: IEEE 802.11-06/1305r5

Submission

Major categories

• We have 4 major categories– “Deferred” and “No assignee”

– “Rejected” at BF&A ad hoc, but not yet moved to approve at TGn

– “Accepted” at BF&A ad hoc, but not yet moved to approve at TGn

– “Counter” at BF&A ad hoc, but not yet moved to approve at TGn

• And each would be further categorized as shown in following slides– I would suggest how to resolve them.

October 2006


Slide 4

doc.: IEEE 802.11-06/1305r5

Submission

“Deferred” and “No assignee”

• In 06/0675r42, we have 15 comments in this category

• From the next slide, I categorize them into several groups

• Remained groups are group-1 and group-2

October 2006


Slide 5

doc.: IEEE 802.11-06/1305r5

Submission

Group-1 : Reducing modes of TxBF

• This would be strongly controversial issue– Before asking submission of resolutions, we would have

discussion within BF&A ad hoc.• It would be better to have some slides showing Pros & Cons.

– Tomoya submitted 06/1356r0 for this purpose (no resolution provided).

– After having some level of consensus, we would ask volunteer to submit resolutions. (= No immediate assignment is required)

• CID#s in this group– 261, 503, 710, 3505, 3872, 7237, 7417, 7418, 8050, 8141, 8195,

12035, 12053, 5121

– Please note that each comment suggest different resolution. Detail would be shown in following slide.

October 2006


Slide 6

doc.: IEEE 802.11-06/1305r5

Submission

Group-1 : Reducing modes of TxBF (Cont’d)

•261 : remove CSI FB and Uncompressed V FB•503 : remove implicit TxBF•710 : choose one, or remove all•3505 : remove two of the three of explicit TxBF•3872 : choose one TxBF mode•7237 : justify, or remove two of the three of explicit TxBF•7417 : remove Uncompressed V FB•7418 : remove Compressed V FB•8050 : remove two of the three from explicit TxBF•8141 : remove Compressed V FB, and possibly one more explicit FB•8195 : remove Compressed V FB•12035 : Remove TxBF until we could define smaller set of TxBF•12053 : Remove TxBF until we could define smaller set of TxBF•5121 : Make one TxBF method a subset of the other to have interop

October 2006


Slide 7

doc.: IEEE 802.11-06/1305r5

Submission

Group-2 : Reducing types of Sounding

• This would be strongly controversial issue– Before asking submission of resolutions, we would have discussion

within BF&A ad hoc.• It would be better to have some slides showing Pros & Cons.

– After having some level of consensus, we would ask volunteer to submit resolution. (= No immediate assignment is required)

• CID#s in this group– 8142

October 2006


Slide 8

doc.: IEEE 802.11-06/1305r5

Submission

Group-3 : Table vs Figure• CID#2253, 2273, 2297, 2323, 2345 say;

– The frame formats would be much better shown as a Figure than a table.– Change to a Figure showing sizes of each field, and a short paragraph below with

the information currently in the "Value" column.– General ad hoc rejected similar comments. Adrian suggests that we do the same

for these. Adrian will look up the relevant CIDs

• Adrian reported this issue in 06/0910r0– It includes straw poll and motion.– Other CID#s related to this; CID#2231(Frame format, 06/0717r22), 2245 (Frame

format, 06/0717r22), 2237(MAC, 06/690r23), and 2353(where?) are also related to this issue.

• Suggested resolution from BF & A ad hoc (unanimously agreed)– Reject– Reason: The table format is used in the baseline. TGn Will be following the

general format of the Baseline., as approved by the general ad hoc

Done

October 2006


Slide 9

doc.: IEEE 802.11-06/1305r5

Submission

Group-4 : Terminology• CID#6790, 878, 4776, 3992 say;

– Use unified term for beamformer/beamformee, or other terms.

• Adrian also reported this issue in 06/0910r0

• BTW, CID#472 also related to this issue.– But it was approved to reject by TGn…

• Resolution accepted using 06/1302r3, at Melbourne

Resolved

October 2006


Slide 10

doc.: IEEE 802.11-06/1305r5

Submission

Group-5 : PLME interface• CID#2645, 2674, 2682, 2696, 2709, 2714, 3087 mention

this– MFB, CSI, Steering matrix, Reciprocity Correction, etc…– Assaf presented 06/1382r2

• Suggested resolution from BF & A ad hoc (unanimously agreed)– Countered as per 06/1382r2

• I found one typo that CHAN_MAT should not be (Y, N), but (N, Y) to match with CHAN_MAT_TYPE.– We should re-visit and resolve them quickly at Dallas

Done, but…

October 2006


Slide 11

doc.: IEEE 802.11-06/1305r5

Submission

Group-6 : Independent PHY-MAC• CID#2637, 2663, 2670 mention this

– Adrian and Assaf submitted 06/1315r1 to the PHY group. Adrian will consider whether these CIDs can be included

• Adrian also reported this issue in 06/0910r0

• Suggested resolution from BF & A ad hoc (unanimously agreed)– CID#2637 : reject

– CID#2663 : Defer (assign to John K to include this in the future version of 06/0593)

– CID#2670 : counter (assign to John K to include this in the future version of 06/0593)

Done

October 2006


Slide 12

doc.: IEEE 802.11-06/1305r5

Submission

Group-7 : Subcarrier grouping at CSI/Steering matrix feedback

• CID#2291, 12098(already approved), 12100(already approved) mention this– I think comment would be clear enough to prepare resolution.

– Joonsuk provided 06/1379r2

• Suggested resolution from BF & A ad hoc (unanimously agreed)– CID#2291: counter as per 06/1379r2

Done

October 2006


Slide 13

doc.: IEEE 802.11-06/1305r5

Submission

Group-8 : Others (1)

• CID#834, 1418(Withdrawn), 2170, 7126, 7129, 7132, 7273, 7371, 7919, 7598– Some of them is not so clear to prepare resolution.

– So, we should reach commenter to ask more input at first.

– JWK contacted commenters to ask for additional input

• Suggested resolution from BF & A ad hoc (unanimously agreed) – CID#834, 2170: reject

– CID#7132, 7273: Counter

– CID#7126, 7129, 7598: Defer and assigned to Darren

– CID#7371: Defer and assigned to Tomoya

– CID#7919: Defer and assigned to Shravan.

Done

October 2006


Slide 14

doc.: IEEE 802.11-06/1305r5

Submission

“Rejected” at BF&A ad hoc, but not yet moved to approve at TGn

• In 06/0675r42, we have now 4 comments in this category.– And these should be moved to be accepted at Dallas

• 8140, 8143, 8196 (Group-12)

• 10076 (it had an assignee, and we decided to recommend rejection)

• From the next slide, I categorize them into several groups.

October 2006


Slide 15

doc.: IEEE 802.11-06/1305r5

Submission

Group-9 : Link Adaptation

• CID#7274 says– Remove Link adaptation using CSI explicit FB (9.19.4)

• This may be controversial issue– Before asking submission of resolutions, we would have

discussion within BF&A ad hoc.• It would be better to have some slides showing Pros & Cons.

– After having some level of consensus, we would ask volunteer to submit resolutions. (= No immediate assignment is required)

• This was accepted at Melbourne– Resolved with CID#1420, 7652

Resolved

October 2006


Slide 16

doc.: IEEE 802.11-06/1305r5

Submission

Group-10 : TBD for IE

• CID#986, 1237, 1239, 1241, 1243, 10168, 10169, 10170, 10171, 10172, 10173 mention this issue– Replace TBD with Information Element ID from ANA

• I suggest to transfer them to the TGn technical editor– Technical editor has a responsibility to handle this.

• No submission required from BF&A ad hoc

No more work at BF ad hoc

October 2006


Slide 17

doc.: IEEE 802.11-06/1305r5

Submission

Group-11 : Qk per RA

• CID#968, 1073, 4161 mention this issue– Same Qk per RA, but may be different for other Qk

• Suggested procedure– In 06/0675r40, these CIDs are assigned to Joonsuk.

– But Resn Status seems “R” without reasons.

• We re-classify them;– Defer and assigned to Joonsuk

October 2006


Slide 18

doc.: IEEE 802.11-06/1305r5

Submission

Group-12 : Performance requirement for TxBF

• CID#8140, 8143, 8196 mention this issue– Minimum performance requirement for the CSI FB

– Minimum performance requirement the sounding measurement (for cal)

– Quality measure of CSI FB and specify how to choose Nb

• Suggested resolution from BF & A ad hoc (unanimously agreed)– Reject

Done

October 2006


Slide 19

doc.: IEEE 802.11-06/1305r5

Submission

Group-13 : TxBF Mandatory vs optional

• CID#10323, 10324, 10325 mention this issue– 10323 : transmission of beamformed PPDUs shall be mandatory for

HT-APs, optional for others

– 10324 : reception of beamformed PPDUs shall be mandatory for all STAs

– 10325 : Calibration procedure shall be mandatory for HT-APs, optional for others

• CID#10327 would be resolved simultaneously.– ZLF (maybe Tx and Rx) shall be mandatory for all STAs.

• Resolutions for these CIDs are approved in the motion 62

Resolved

October 2006


Slide 20

doc.: IEEE 802.11-06/1305r5

Submission

Group-14 : Others

• CID#3979, 3983 : padding at CSI/V feedback– I suggest to conceptually accept it in the spreadsheet.

– Defer and assigned to Assaf

• CID#2269 : move procedural from clause 7 to clause 9– We conceptually agreed

– Defer and assigned to Tomoya (now, covered by 1411r2)

October 2006


Slide 21

doc.: IEEE 802.11-06/1305r5

Submission

“Accepted” at BF&A ad hoc, but not yet moved to approve at TGn

• Because, it may conflict with other resolutions

• In 06/0675r42, we have 1 comments in this category.


October 2006


Slide 22

doc.: IEEE 802.11-06/1305r5

Submission

Group-15 : They would be resolved in 06/0886

• CID#s in this group– 1436, 1437, 1653, 2164, 2165, 2298, 2324, 2325, 3977, 4786,

7822

• CID# 1436, 1653, 2164, 2165, 2298, 2324, 2325, 4786, 7822 are approved in motion#57

• CID#3977 is in main tab of 06/0675r42– Suggested resolution from BF & A ad hoc (unanimously agreed)

• Counter: resolved in D1.05

• CID#1437 seems vanished from 06/0675r35– This was withdrawn

Done

October 2006


Slide 23

doc.: IEEE 802.11-06/1305r5

Submission

Group-16 : Need motion to approve

• CID#s in this group– 984, 985, 2265, 2275, 2278, 2300(fixed in D1.02), 7131, 8029, 12099

• Suggested resolution from BF & A ad hoc (unanimously agreed)– CID#2265, 2275, 2278, 2300, 7131, 8029, 12099: Counter.

– CID#984, 985: Defer and assigned to Joonsuk

Done

October 2006


Slide 24

doc.: IEEE 802.11-06/1305r5

Submission

Group-17 : other (CID#11887)

• This was removed from the motion at San Diego• Because editor requested to have definition of staggered sounding

and staggered PPDU.

• Similar resolution for similar comment is accepted by editorial ad hoc and it has been included in D1.02.– Definition has not been included in D1.02, but please refer to group-20.

• So, we may not need additional action on this CID#.– I suggest that this CID#11887 would be transferred to editorial, and

editorial team would decide this as “accepted” or “duplicate”.

• We have submission of 06/1134r1 addressing this issue• Suggested resolution from BF & A ad hoc (unanimously agreed)

– Counter Done

October 2006


Slide 25

doc.: IEEE 802.11-06/1305r5

Submission

“Counter” at BF&A ad hoc, but not yet moved to approve at TGn

• Because, it may conflict with other resolutions

• In 06/0675r42, we have 26 comments in this category.– Plus 18 comments that are addressed in previous slides.


October 2006


Slide 26

doc.: IEEE 802.11-06/1305r5

Submission

Group-18 : They would be resolved in 06/0886

• CID#s in this group– 2282, 2299, 2305

• Just to confirm that BF&A ad hoc would recommend to accept 06/0886

• If it would have enough supports there, we would move to approve 06/0886 at TGn– With or without other resolutions

• CID#2282, 2299, 2305 are approved in motion#57

Resolved

October 2006


Slide 27

doc.: IEEE 802.11-06/1305r5

Submission

Group-19 : Need motion to approve

• CID#s in this group– 4790, 8030

• I checked and there would be no conflict with other resolutions, at least within BF&A ad hoc

• And there seems no controversial item– At San Diego, we had opinion that the resolution for CID#8030 is not

enough, and we removed this from the motion. But Resolution column seems having enough resolution…Need discussion.

– I would encourage you to check them by yourself.

• Suggested resolution from BF & A ad hoc (unanimously agreed)– CID#4790: Counter

– CID#8030: Counter

Done

October 2006


Slide 28

doc.: IEEE 802.11-06/1305r5

Submission

Group-20 :Covered by 06/1134r2

• CID#s in this group– 264, 5075

• Now, we have submission of 06/1134r2– However, similar comment (CID#11906) was discussed in general

ad hoc, and they prepared resolution. This was approved by TGn at San Diego. So, the next revision would includes resolution, i.e., definitions, for these two CID#.

• Resolution using 06/1309r3 for CID#5075 was approved in motion#60.

• Suggested resolution from BF & A ad hoc (unanimously agreed)– CID#264 : Counter Done

October 2006


Slide 29

doc.: IEEE 802.11-06/1305r5

Submission

Group-21 :Other (7140)

• This comment relates calibration.

• I recommend to change this from “C” to “D”.

• I suggest it would be resolved with 7661, 6797, 7278 in submission from Yuichi & Sanjiv.

• Suggested resolution from BF & A ad hoc (unanimously agreed) – Defer and assigned to Tomoya

• Covered by 06/1411r2

October 2006


Slide 30

doc.: IEEE 802.11-06/1305r5

Submission

Remained CIDs (1)

• CID#661 (Nst in Reciprocity correction)– Defer and assigned to Tomoya

• Covered by 1411r2

• CID#945, 4142 (Q_steer at Spatial Mapping section)– Defer and assigned to Joonsuk

• Covered by 06/1334r4

• CID#7103 (How to know N_tx at receiver)– Defer and assigned to John K

• CID#7891 (Link adaptation)– Assigned to Darren, and resolution is”Counter”.

• CID#7919 (Reciprocity correction vector)– Defer and assigned to Shravan

October 2006


Slide 31

doc.: IEEE 802.11-06/1305r5

Submission

Remained CIDs (2)

• CID#8070 (regular sounding)– Defer and assigned to John K

• CID#10285 (Qk also would be updated, and might be different from original one)– Defer and assigned to Joonsuk

• CID#11460 (Subcarrier grouping)– Suggested resolution from BF & A ad hoc (unanimously agreed)

• Counter as per 1379r2

• CID#11911 (Add conditional mandatory of transmitting sounding PPDU under implicit TxBF receive capability, in PICS)– Suggested resolution from BF & A ad hoc (unanimously agreed)

• Accept

• CID#11958 (definition of two types of CSD)– Suggested resolution from BF & A ad hoc (unanimously agreed)

• Accept

Done

Done

Done

October 2006


Slide 32

doc.: IEEE 802.11-06/1305r5

Submission

Appendix- Waiting submission- Submitted, but not reviewed yet- Reviewed, under discussion

October 2006


Slide 33

doc.: IEEE 802.11-06/1305r5

Submission

Waiting submissions from Assignees[as of 2006/10/23]

• Assaf : 3086, 3395, 3979, 3983, 10880

• Darren : 7126, 7129

• Gal & Vinko & Joonsuk : 11985, 11987

• John K : 2680, 11893, 11905, 3967, 3973, 3974, 7103

• Marc : 693 ?

• Matthew : 1131 (re-assigned)

• Shravan : 722, 2258, 3812, 4637, 10075, 7906, 7919

• Vinko : 976, 980, 4752

October 2006


Slide 34

doc.: IEEE 802.11-06/1305r5

Submission

Submitted but not reviewed yet [as of 2006/10/23]

• 06/1335r4 (Joonsuk): CID# 968, 969, 1073, 4161, 11959, 947, 948, 949, 950, 951, 952, 954, 1072, 4144, 10286, 973, 974, 975– Related presentation is 06/1032r4

– Need update to include; 4142, 945, 10285, 3991

• 06/1338r2 (Joonsuk): CID#984, 985– Old version was reviewed.

– Grouping issues were resolved, and SNR issues (984 and 985) were remained.

• 06/1597r1 (Assaf): CID#3961

October 2006


Slide 35

doc.: IEEE 802.11-06/1305r5

Submission

Reviewed, and settled [as of 2006/10/23]

• 06/0589r1 (John K): CID# 260, 3503, 7416, 8025, 10078, 11895, 11896, 11897, 12192, 3991 [Done]– Resolution in this document is accepted by this ad hoc

• 06/1134r3 (Irina) : CID# 264, 7213, 11887[Done-20061017]

• 06/1083r0 (Hongyuan): CID# 3996 [Done]

• 06/1355r0 (Solomon): CID# 3764, 10312, 10313, 2716 [Done]

• 06/1382r0 (Assaf): CID# 2645, 2674, 2682, 2696, 2709, 2714, 3087 [Done]

• 06/0823r0 (Tomoya) : CID# 10076 [Done]

• 06/1601r1 (Andy): CID#2348, 5119

October 2006


Slide 36

doc.: IEEE 802.11-06/1305r5

Submission

Reviewed and under discussion [as of 2006/10/23]

• 06/0573r0 (Vincenzo): CID# 7357• 06/0593r5 (JohnK): CID# 6794, 6795, 6796, 2675, 4524, 7277, 48,

7836, 11890, 3971(partly), 10071(partly), 10072(partly), 12000(partly)– Need update to include CID#2663, 2670, 8070(partly)

• 06/0594r1 (JohnK): CID# 11899, 11898– 06/1079r0 provide simulated results on this

• 06/0893r0 (Solomon): CID# 11983, 10287, 11988(already resolved), 3976(already resolved)

• 06/0939r1 (Tomoya): CID# 10074 • 06/1070r0 (Seigo): CID# 720. {Seigo is reconsidering}

– 06/0938r0 is also related to this submission.• 06/1411r2 (Tomoya): CID# 6797, 7140, 7278, 7661, 661, 2269

– Need update to include CID#7371• 06/1356r0 (Tomoya): CID# 261, 503, 710, 3505, 5121, 3872, 7237, 7417, 7418,

8050, 8141, 8195, 12035, 12053 [No resolution provided]

Doc.: IEEE 802.11-06/1305r5 Submission October 2006 Tomoya Yamaura (Sony)Slide 1 Comments...

Documents

Transcript of Doc.: IEEE 802.11-06/1305r5 Submission October 2006 Tomoya Yamaura (Sony)Slide 1 Comments...