<author>, <company>

Slides:



Advertisements
Similar presentations
Submission Title: [Resolution on comment #20,22 and 30]
Advertisements

Submission Title: [Add name of submission]
<month year> <doc.: IEEE doc> May 2015
doc.: IEEE <doc#>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
doc.: IEEE <doc#>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Usage model for short-range line-of-sight.
doc.: IEEE <02/139r0> <January 2002> May, 2009
doc.: IEEE <doc#>
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
Name - WirelessHD August 2008
doc.: IEEE <doc#>
Name - WirelessHD August 2008
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE /XXXr0 Sep 19, 2007 July 2008
November 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Geometry for the usage models ] Date Submitted:
doc.: IEEE <doc#>
Submission Title: [Resolution on comment #20,22 and 30]
<month year> <doc.: IEEE doc> March 2015
July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Project Plan] Date Submitted: [ July.
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> December 2015
Submission Title: [Comment Resolutions for #309, #310, and #314]
Submission Title: [One-to-many and many-to-many peering procedures]
<month year> <doc.: IEEE doc> March 2015
<month year> <doc.: IEEE doc> September 2015
<month year> doc.: IEEE <xyz> November 2000
<month year> <doc.: IEEE doc> November 2015
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> May 2015
<month year> <doc.: IEEE doc> May 2015
doc.: IEEE <doc#>
Doc.: IEEE /XXXr0 Sep 19, 2007 Sep Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)‏ Submission Title: [Resolutions.
doc.: IEEE <doc#>
Submission Title: [One-to-many and many-to-many peering procedures]
平成31年4月 doc.: IEEE /424r1 July 2008 doc.: IEEE c
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> December 2015
<month year> <doc.: IEEE doc> January 2016
Submission Title: [Comment Resolutions for #345, #347, #348, and #349]
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> March 2015
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<author>, <company>
doc.: IEEE <doc#>
Doc.: IEEE /XXXr0 Sep 19, 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)‏ Submission Title: [Resolutions.
<month year> <doc.: IEEE doc> July 2015
January 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Project Plan] Date Submitted: [17.
November 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Project Plan] Date Submitted: [15.
doc.: IEEE <doc#>
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
doc.: IEEE <doc#>
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
May 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Project Plan] Date Submitted: [15 May.
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
<month year> <doc.: IEEE doc> September 2015
<month year> <doc.: IEEE doc> March 2015
Name - WirelessHD August 2008
September 2015 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Timeline of TG4s] Date Submitted: [17.
July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Project Plan] Date Submitted: [ July.
Presentation transcript:

<author>, <company> doc.: IEEE 802.15-<doc#> <month year> Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Adding BA base sequence number] Date Submitted: [March 18, 2007] Source: [Zhou Lan, Chang-woo Pyo, Fumihide Kojima, Hiroyuki Nakase, Shuzo Kato, Gal Basson(2) , Tal Azogui(2)] Company [National Institutep of Information and Communications Technology (NICT), Wilocity(2)] Address1[3-4 Hikari-no-oka, Yokosuka-shi, Kanagawa 239-0847, Japan] Voice1:[] , FAX1: [] E-Mail:[lan@nict.go.jp, other contributors are listed in “Contributors” slides] Re: [In response to TG3c comments (IEEE P802.15-08-0255-02-003c)] Abstract: [Comment resolutions] Purpose: [To be considered in TG3C baseline document.] Notice: This document has been prepared to assist the IEEE P802.15. 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 contributors acknowledge and accept that this contribution becomes the property of IEEE and may be made publicly available by P802.15. <author>, <company> Page 1

Comment # 63 63 GB DF3 12.2.4.3.2 65-66   T PHY add a "Block-ACK base sequence field" (to optional MAC header adjuscent to BA field) - in order resolve ACK/NAK correlation ambiguity of corrupted MSDU number and BA-bit-offset

Block ACK / aggregated MSDU correlation problem description current Draft text suggests that correlation of MSDU sequence to Block ACK bit offset, is based on its order-offset in the frame. MSDU sequence numbers in the MAC frame body are not necessarily consecutive (e.g. in case of selective retransmit) there is no way to tell how many MSDU’s are corrupted (assuming MSDU headers are also corrupted) No way to set/clear the correlated bit in the block-ACK

Problem description diagram DEV1 DEV2 PHY HDR MAC HDR BA MSDU #11 #12 #13 #14 PHY HDR MAC HDR BA {0,1,0,1,…} MSDU # … PHY HDR MAC HDR BA MSDU #11 #13 #15 #16 #17 PHY HDR MAC HDR BA {???,1,1,1,…} MSDU # … Unknown number of MSDU corrupted from the beginning of the frame

Block ACK / aggregated MSDU correlation suggested solution Add “Block ACK– base sequence number” to the transmitted “MAC optional header”. Each bit offset in the block ACK, is taken as the offset from the BA-base sequence (in the MAC optional header) to the MSDU sequence number

Solution description diagram DEV1 DEV2 PHY HDR MAC HDR BA MSDU #11 #12 #13 #14 PHY HDR MAC HDR BA-BASE # 12 BA {1,0,1,…} MSDU # … PHY HDR MAC HDR BA MSDU #11 #13 #15 #16 #17 PHY HDR MAC HDR BA-BASE # 15 BA {1,1,1,…} MSDU # … Corrupted leading MSDU # are NOT acknowledged – receiver of the BA required to retransmit non-ACKed MSDU (lower than BA-BASE )

Frame Structure Add BA Base Sequence number – 12 bits field First 3 nibbles- are the base sequence number for the current aggregated MSDU Last nibble - reserved