(no description)
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram.
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.
Name | Type | Description |
---|---|---|
Ieee80211BlockAckReq | packet |
8.3.1.8 BlockAckReq frame format |
Name | Type | Description |
---|---|---|
type | short |
type and subtype |
multiTid | bool | |
compressedBitmap | bool | |
barAckPolicy | bool |
0-Normal Acknowledgment, 1-No Acknowledgment. |
byteLength | ||
transmitterAddress | MACAddress |
aka address2 |
toDS | bool | |
fromDS | bool | |
retry | bool | |
moreFragments | bool | |
duration | simtime_t |
TODO: rename to durationField (levy) |
AID | short |
"id" (Association ID) in the Duration/ID field (-1=no ID) |
receiverAddress | MACAddress |
aka address1 |
MACArrive | simtime_t |
FIXME remove it, technical data, used inside of MAC module |
packet Ieee80211MultiTidBlockAckReq extends Ieee80211BlockAckReq { // byteLength TODO // The RA field of the BlockAck frame is the address of the recipient STA that requested the Block Ack. // The TA field is the address of the STA transmitting the BlockAck frame. type = ST_BLOCKACK_REQ; // The BAR Information field of the Compressed BlockAckReq frame contains the Block Ack Starting // Sequence Control subfield, as shown in Figure 8-21. The Starting Sequence Number subfield of the Block // Ack Starting Sequence Control subfield contains the sequence number of the first MSDU or A-MSDU for // which this BlockAckReq frame is sent. The Fragment Number subfield of the Block Ack Starting Sequence // Control subfield is set to 0. multiTid = 1; compressedBitmap = 1; // TODO: unimplemented }