Burst Transmission and Acknowledgment

Slides:



Advertisements
Similar presentations
January 2002 Khaled Turki et. al, Texas InstrumentsSlide 1 doc.: IEEE /022r0 Submission TID Field Usage in QoS CF-Poll Khaled Turki and Matthew.
Advertisements

William Stallings Data and Computer Communications 7th Edition
William Stallings Data and Computer Communications 7 th Edition Chapter 7 Data Link Control Protocols.
EE 4272Spring, 2003 Chapter 7 Data Link Control Objectives: Effective & reliable data communication between two directly connected transmitting-receiving.
Data Link Control Protocols
Data Link Control Protocols Dr. Muazzam A. Khan. Flow Control Ensuring the sending entity does not overwhelm the receiving entity —Preventing buffer overflow.
Doc.: IEEE /494r0 Submission July 2001 Michael Fischer, Intersil (TGe Editor)Slide 1 Provisional Tge Ballot Comment Resolutions from the May,
Doc.: IEEE /0415r0 Submission April mc CIDs 1136,1118,1458 Date: Authors: Graham Smith, DSP GroupSlide 1.
November 2000 Jin-Meng Ho, Texas InstrumentsSlide 1 doc.: IEEE /367 Submission p-DCF for Prioritized MAC Service Jin-Meng Ho, Sid Schrum, and.
Doc.:IEEE /566r2 Submission November 2001 S. Choi, Philips & M.M. Wentink, Intersil Slide 1 Multiple Frame Exchanges during EDCF TXOP Sunghyun.
Doc.:IEEE /0318r0 March 2013 A. Asterjadhi, Qualcomm Inc. Short MAC Header Design Date: Authors:
Doc.: IEEE /248r0 Submission Bobby JoseSlide 1 February 2002 Contention Free TXOP Request and Allocation Issues Bobby Jose,
PROTOCOL BASICS. 2 Introduction In chapter 3: Circuits and techniques can be employed to transmit a frame of information between 2 DTEs Error detection.
Fast Retransmit For sliding windows flow control we waited for a timer to expire before beginning retransmission of a packet TCP uses an additional mechanism.
March 21, 2001 Recall we have talked about the Sliding Window Protocol for Flow Control Review this protocol A window of size I can contain at most I.
EA C451 (Internetworking Technologies)
Flow control for EDMG devices
Proposed Modifications to e-D4.0 Group ACK
Location Measurement Protocol for Unassociated STAs
Undetected Duplicate Frame Reception
Data link layer (LLC).
Lecture 27 WLAN Part II Dr. Ghalib A. Shah
Joint Proposal MAC Report
Data Communications and Networking Pipelined reliable data transfer
Flow control for EDMG devices
SB1000 CID 6304 PHY-CCARESET.request
How to collect STAs’ Tx demands for UL MU
Signaling for Parameterized QoS Support
Proposed Modifications to
Requirements and Implementations for Intra-flow/Intra-AC DiffServ
Requirements and Implementations for Intra-flow/Intra-AC DiffServ
Issue of Buffer Status reporting
Issue of Buffer Status reporting
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
MAC Capabilities Info. in HE Capabilities IE
Ack Bitmap length for Burst ACK
Multicast/Broadcast Communication With Acknowledge
Peer Power Save Mode for TDLS
EDCA and BlockAck Extensions for Reliable Multicast/Broadcast Services
MAC Clarifications Date: Authors: September 2016
Texas Instruments Incorporated
Issue of Buffer Status reporting
Fragmentation with A-MPDU
Ack Bitmap length for Burst ACK
Regarding HE fragmentation
Burst Transmission and Acknowledgment
Class-based Contention Periods (CCP) for the n MAC
EDCF Issues and Suggestions
Terminology Corrections and Improvements for the TGe Draft
BlockAck Enhancement for Multicast Transmissions
Group Polling for DCF Based Reservation Request
HCF Channel Access And Inter-BSS Channel Sharing
Suggested changes to Tge D3.3
Group Block Acknowledgements for Multicast Traffic
Acknowledgement for Multicast Streams
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Considerations on general MAC frame] Date Submitted:
Requirements and Implementations for Intra-flow/Intra-AC DiffServ
Suggested changes to Tge D3.3
Ack Bitmap length for Burst ACK
HCCA TXOP handling difficulties
Peer Power Save Mode for TDLS
Regarding HE fragmentation
QoS Metrics Date: Authors: January 2005 Month Year
July 2004 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Modified Delayed (Dly) Acknowledgement for.
HCF Channel Access And Inter-BSS Channel Sharing
Proposed Resolution for Draft 3.0
Requirements and Implementations for Intra-flow/Intra-AC DiffServ
GCR using SYNRA for GLK Date: Authors: July 2015 Month Year
Chapter 11 Comment Resolution for Letter Ballot 63
Name - WirelessHD August 2008
Presentation transcript:

Burst Transmission and Acknowledgment Jin-Meng Ho, Jie Liang, Sid Schrum Texas Instruments Incorporated 12500 TI Blvd. Dallas, Texas 75243 (214) 480-1994 jinmengho@ti.com

802.11e/D2.0 Burst Request/Ack Issues Buffer resource issue: How large should a burst be before the transmitting station requests a burst ack from the receiving station? A large burst may exceed the buffer capacity at the receiving station, resulting in the loss of some frames that were received correctly. Re-ordering and delay issue: How long should the receiving station hold correctly received higher sequence number frames to wait for missing lower sequence number frames? Some missing frames may have been discarded by the transmitting station and unnecessarily delay the delivery of frames correctly received by the receiving station to the upper layer.

Burst Ack Request and Control Frame (1) Burst Ack Starting Sequence Number: Indicating the sequence number for the starting MPDU from which the transmitter is requesting ACK status. This number can not be decreasing modulo 4096 for the subsequent Burst Ack Request frame for the same TID. This number shall not be offset by more than 256 from the latest sequence number for the same traffic stream. MSDUs of sequence number smaller than this number have been discarded by the transmitting MAC entity and are not to be awaited by the receiving MAC entity.

Burst Ack Request and Control Frame (2) TID (4 bits): TID of the traffic stream for which the burst Ack request is intended. Burst Ack Stop: When set to 1, indicates that the transmitter is terminating burst ack for this TID and the receiver can release relevant resources. When set to 0, indicates that the transmitter will continue burst ack for this TID

Burst Acknowledgment (BurstAck) Frame (1) The Duration field is set to the value obtained from the duration field of the immediately previous frame, subtracted by a SIFS period and the time required to transmit the Burst Ack frame. If the calculated duration includes a fractional microsecond, that value is rounded up to the next higher integer. The RA field is copied from the TA field of the immediately previous Burst Ack Request frame: This frame acknowledges the frames belonging to the same TID as contained in that previous frame.

Burst Acknowledgment (BurstAck) Frame (2) The Burst Control field is 2-octet field that contains a Buffer subfield in bits 0-7 , a Wait subfield in bit 8, and a Fragmentation subfield in Bit 9 The Buffer indicates the buffer space, in units of 1K octets (1K =1024), that the acknowledging station has, at the time of transmitting this BurstAck frame, for receiving MSDUs belonging to the same TID as contained in the previous frame. The Wait subfield, if set to 0, indicates that this frame contains a valid Burst Ack Bitmap, and if set to 1, indicates that a valid Burst Ack Bitmap cannot be sent with this Burst Ack frame. The value of the Wait subfield does not affect the meaning of the Buffer subfield. When Fragmentation bit is 1, each bit in the Burst Ack Bitmap indicates the status for each fragmentation of a MSDU. When Fragmentation bit is 0, each bit of the Burst Ack bitmap indicates the receiving status for a single MSDU.

Burst Acknowledgment (BurstAck) Frame (3) The Burst Ack Bitmap is a 16-octet field that indicates sequentially the reception status of MSDUs with consecutive sequence numbers and with the same TID as contained in the previous frame. When the Bitmap Fragmentation Indication bit is set to 1, every two octets relate to one MSDU, with the 16 bits corresponding to the 16 fragments of that MSDU in the same sequentially asending order; Otherwise, each bit corresponds to an MSDU. A bit in this bitmap is set to 1 if the corresponding fragment or MSDU is received correctly (after FEC decoding if appropriate), or otherwise the bit is set to 0. Some bits in the bitmap may correspond to fragments that did not exist or have not been transmitted; these bits are set to 0.

Burst Transmission and Acknowledgment (1) Within the access interval (such as a TXOP for a WSTA) in which a QSTA has the medium access right, the QSTA may transmit two or more directed MPDUs separated by a SIFS period that belong to a given TS (or a given TC if the QSTA limits that TC to a single destination and maintains a separate sequence control counter for that TC), and request a burst acknowledgment to those MPDUs to be returned by the addressed QSTA following receipt of the Burst Ack Request frame for with the same TID. Some of these MPDUs may be retries. The QSTA may proceed to transmit other MPDUs not belonging to the given TS or TC prior to requesting or receiving a burst acknowledgment, and then resume the transmission of the MPDUs belonging to the given TS or TC and request a burst acknowledgment to the MPDUs transmitted before and after the MPDUs not belonging to the given TS or TC. The QSTA may resume the transmission and request the burst acknowledgment in a subsequent access interval (such as in a subsequent TXOP for a WSTA) in which it has the medium access right. The QSTA should use a QoS Burst Ack Request frame to request a burst acknowledgment. The QSTA shall set the Burst Ack Starting Sequence Number subfield to specify the starting point of the MSDUs for which the transmitter is requesting Ack status. Other frames have been discarded by the transmitting MAC entity. The MSDUs referenced by this burst request may have been transmitted with the intervention of other frames not belonging to this TS or TC, or even not sent by this QSTA. The smallest sequence number of these MSDUs shall not be smaller, in modulo 4096, than the smallest sequence number of the MSDUs referenced by the Burst Ack Starting Sequence Number subfield in the burst acknowledgment request frame for the same TS or TC. The TC/TS queue size buffered at a WSTA may be indicated in frames other than the one requesting a burst acknowledgment. Following receipt of a BurstAck frame, the QSTA should not transmit an amount of MSDUs, belonging to the TS or TC to which the BurstAck frame applies, more than indicated in the Buffer subfield of that BurstAck frame, prior to requesting another burst acknowledgment for the same TS or TC and receiving the corresponding BurstAck frame which contains a new Buffer field value. Otherwise buffer overflow at the receiving QSTA may result and received MSDUs may be discarded.

Burst Transmission and Acknowledgment (2) The QSTA addressed by a frame containing a burst acknowledgment request (i.e., a frame containing a QoS Control field wherein both Burst and Ack bits are set to 1) shall immediately respond with a BurstAck frame, wherein the Burst Ack Bitmap is set to acknowledge the MSDUs referenced by the Burst Offset subfield in the burst acknowledgment request frame (with unused higher order bits set to 0). These MSDUs may have been transmitted with the intervention of other frames not belonging to the same TS or TC, or not even sent by the QSTA requesting the burst acknowledgment. If the addressed station is not ready to respond with an updated Burst Ack Bitmap, it shall return with a Burst Ack frame wherein the Wait bit is set to 1. The addressed QSTA shall set the Buffer field to indicate the amount of available buffer for further receiving the MSDUs from the same QSTA and the same TS or TC as indicated by the burst acknowledgment request frame. When the Burst Ack Starting Sequence Number corresponds to a MSDU that is larger than 8 MSDU away from the current MSDU, then the QSTA shall set the Bitmap Fragmentation Indication subfield in the BurstAck frame to 1 so that each bit of BurstAck Bitmap correspond to a single MSDU instead of a fragment of a MSDU. The addressed QSTA shall pass up to the higher layer all MSDUs that have been correctly received but held at the MAC sublayer in waiting for missing MSDUs with sequence numbers lower than those specified by the Burst Ack Starting Sequence Number subfield of the burst acknowledgment request frame. The addressed QSTA should not hold any correctly received MSDUs at the MAC sublayer for longer than their applicable lifetimes. If the burst acknowledgment request frame is sent by a WSTA, the expected BurstAck frame shall be transmitted within the TXOP allocated to that WSTA. The WSTA may continue to use the remaining TXOP upon receiving a BurstAck frame.

Motion To replace the frame formats, figures, and text pertaining to the Burst Acknowledgment mechanism in Draft 2.0 with those provided in this document.