Enhancing fragmentation and defragmentation procedures in broadband wireless networks

Abstract

A preemption system enables successful transmission of multiple service data units (SDUs) across a wireless interface. The preemption system addresses out-of-order transmissions of fragments of SDUs, such that the receiver is able to process each successfully. The preemption system enables a higher-priority SDU to simultaneously be transmitted with a lower-priority SDU, so that delays in processing the lower-priority SDU does not negatively affect processing of the higher-priority SDU. The preemption system also addresses non-automatic repeat request medium access controller (non-ARQ MAC) connections that only use hybrid automatic repeat request (HARQ), in which the HARQ transmission may cause out-of-order delivery of SDU fragments.

Description

TECHNICAL FIELD

This application relates to the 802.16m standard and the fragmentation and defragmentation of packets under the 802.16m standard.

BACKGROUND

WiMAX, short for worldwide interoperability for microwave access, is currently defined by the Institute of Electrical and Electronics Engineers, or IEEE, 802.16-series specification. The advanced air interface standard is defined under 802.16m.

Packets known as service data units (SDUs) travel wirelessly between a transmitter and a receiver, such as between a base station and a mobile station, using the advanced air interface standard. Sometimes, these SDUs are fragmented into two, three, or hundreds of fragments before transmission. A fragmentation state machine at the transmitter and a defragmentation state machine at the receiver process these fragmented SDUs.

Currently under 802.16m, if a first SDU, SDU1, is being fragmented, a second, higher-priority SDU, SDU2, would have to wait in queue until all the fragments of SDU1 have been transmitted before SDU2 may be fragmented and transmitted. Particularly where large, low-priority SDUs are transmitted, this leads to undesirable results. For example, a power control request, which involves only a few bytes, is unprocessed while waiting for a very large management message, such as is used with PKM (about two Kbytes) to be processed. The power control message may be delayed indefinitely while the large PKM message is being fragmented and transmitted.

Also, as currently defined under the 802.16m standard, SDUs are dropped under certain operating conditions, namely, for non-automatic repeat request (non-ARQ) media access controller (MAC) connections that only use hybrid automatic repeat request (HARQ). “Upon loss, the receiver shall discard all SDU fragments on the connection until a new first SDU fragment is detected . . . ”. HARQ operations may temporarily miss a burst that contains some fragment of a SDU because HARQ does not guarantee in-order delivery. If the 802.16m standard does not define a mechanism to restore the order of the protocol data units (PDUs)/bursts before such a defragmentation mechanism, it will drop SDUs even though all of its fragments are correctly received (just not in order). This is especially crucial for MAC management connections where ARQ is not used and only HARQ is used.

Thus, there is a continuing need for a method to overcome the shortcomings of the prior art.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this document will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein like reference numerals refer to like parts throughout the various views, unless otherwise specified.

FIG. 1 is a block diagram of a preemption system for processing out-of-order fragments of two different service data units, according to some embodiments;

FIG. 2 is a block diagram of a first service data unit having j fragments and a second service data unit having k fragments, both of which are processed by the preemption system of FIG. 1, according to some embodiments;

FIG. 3 is a block diagram of data connection headers with newly defined fields used by the preemption system of FIG. 1, according to some embodiments;

FIG. 4 is a block diagram of management connection headers with newly defined fields used by the preemption system of FIG. 1, according to some embodiments;

FIG. 5 is a schematic block diagram showing operations of the preemption system of FIG. 1 to simultaneously transmit fragments for two different service data units over two different channels using the fields of FIG. 3 or 4, according to some embodiments;

FIG. 6 is a flow diagram showing operations of the fragmentation state machine of the preemption system of FIG. 1, according to some embodiments;

FIG. 7 is a flow diagram showing operations of the defragmentation state machine of the preemption system of FIG. 1, according to some embodiments; and

FIG. 8 is a block diagram of a transceiver system including the preemption system of FIG. 1, according to some embodiments.

DETAILED DESCRIPTION

In accordance with the embodiments described herein, a preemption system is disclosed for successfully transmitting multiple SDUs across a wireless interface. The preemption system addresses out-of-order transmissions of fragments of SDUs, such that the receiver is able to process each SDU successfully. The preemption system enables a higher-priority SDU to simultaneously be transmitted with a lower-priority SDU, so that delays in processing the lower-priority SDU does not negatively affect processing of the higher-priority SDU. The preemption system also addresses non-ARQ MAC connections that only use HARQ, in which the HARQ transmission may cause out-of-order delivery of SDU fragments.

In the following detailed description, reference is made to the accompanying drawings, which show by way of illustration specific embodiments in which the subject matter described herein may be practiced. However, it is to be understood that other embodiments will become apparent to those of ordinary skill in the art upon reading this disclosure. The following detailed description is, therefore, not to be construed in a limiting sense, as the scope of the subject matter is defined by the claims.

FIG. 1 is a block diagram of a preemption system 500, according to some embodiments. The preemption system 500 consists of a transmitter 20 and a receiver 30, in which the transmitter and receiver are part of a WiMAX network. The preemption system 500 may found in a base station and in a subscriber station, such as a cellular phone, in which the base station and the subscriber station transmit wirelessly between one another. In FIG. 1, the transmitter 20 and receiver 30 are transmitting two service data units, SDU1 and SDU2, between one another. Although just two SDUs are shown in FIG. 1, the principles described herein may be applied to any number of concurrent SDUs being sent.

The transmitter 20 of the preemption system 500 includes a fragmentation state machine 100 for preparing the SDUs for wireless transmission. The fragmentation state machine 100 includes fragment characterization 22, which utilizes header fields 72, 82, 84, and 86 to communicate information about each SDU fragment to the receiver 30, such that the receiver does not discard fragments due to out-of-order transmission of SDU fragments. The header fields are described in more detail in FIGS. 3 and 4, below. The fragmentation state machine 100 further includes a channel select mechanism 24, which assigns different channels to different SDUs, where necessary, to ensure efficient transmission of both. The fragmentation state machine 100 is described in more detail in FIG. 6, below.

The receiver 30 of the preemption system 500 includes a defragmentation state machine 200, for processing the wirelessly received SDU fragments. The defragmentation state machine 200 includes a channel identifier 32, a discard timer 34, and up to N buffers 42A, 42B, . . . , 42C (collectively, buffers 42), where N is an integer. The channel identifier 32 uses the header fields, populated by the transmitter 20 with information about each SDU, as indexes into different buffers, as needed, enabling the receiver 30 to process the out-of-order SDU fragments. The defragmentation state machine 200 is described in more detail in FIG. 7, below.

Under the 802.16m standard, there are scenarios in which SDUs are either not processed at all (failure) or are processed in an undesirably slow manner (inefficient). The preemption system 500 enables these SDUs to be successfully and efficiently decoded at the receiver 30 following transmission over the WiMAX network. Under the current 802.16m standard, there exist multiple scenarios in which such processing failure or inefficiency may arise. For example, if a first SDU, SDU1, is fragmented before being transmitted, then a higher priority SDU, SDU2, waits in a queue until all the fragments of SDU1 have been transmitted before SDU2 can be fragmented and transmitted. Where SDU1 is very large, this can cause a significant delay in transmitting SDU2. Where SDU2 is a high-priority SDU, such as a power control request, the delay may be undesirable.

FIG. 2 is a block diagram of two service data units, SDU1 and SDU2, each having multiple fragments, according to some embodiments. In FIG. 2, the SDU1 has j fragments and the SDU2 has k fragments, where j and k are integers. The size of SDU1 is larger than SDU2, but it is not necessary that SDU1 be larger than SDU2. As used herein, however, SDU2 is presumed to have a higher priority than SDU1.

In some embodiments, the fragmentation state machine 100 of the transmitter 20 includes a mechanism to preempt the transmission of the fragments of SDU1 with the fragments of the higher priority SDU2 on the same MAC layer connection. The fragment characterization 22 utilizes an already defined field of one header and defines three new fields in a second header, where both headers are used under WiMAX for wirelessly transmitting the SDUs.

FIGS. 3 and 4 are block diagrams showing data connection headers and management connection headers, respectively, according to some embodiments. Each fragment of each data SDU is preceded by the headers in FIG. 3. The data connection headers include a general MAC header (GMH) 70 and a fragmentation and packing extension header (FPEH) 80. The GMH 70 includes a flow ID (FID) field 72. The FID 72 indicates the MAC channel upon which the SDU is to be transmitted. As used herein, reference to “the MAC channel” is defined as a channel with a MAC/flow connection. The FID 72 is not a newly defined field, but is used by the fragment characterization 22 of the fragmentation engine 200 to indicate the channel in which the SDU is to be transmitted. Likewise, the defragmentation state machine 200 receiving the SDU can identify its transmission channel by reading the FID field 72.

In some embodiments, the FPEH 80 includes three newly defined fields, a fixed-sized (two-bit) fragmentation control (FC) field 82, a variable-sized (n-bit) channel identifier (channel ID, or CID) field 84, and an m-bit sequence identifier (sequence ID, or SID) 86. The CID field 84 indicates which of 2ⁿ channels is used to transmit the SDU. For n=1, there are two available channels, for n=2, there are four available channels, and so on.

The other two fields, the FC field 82 and the SID field 86 are used by the fragment characterization engine 22 to explicitly characterize each fragment of each SDU. The FC field 82 identifies whether the SDU is fragmented or not. If the SDU is fragmented, the FC field 82 indicates whether this fragment is the first fragment (01), the last fragment (10), or a middle fragment (11) of the fragmented SDU. The SID field 86 then specifies the first, middle, and last fragments. In a preferred embodiment, the SID is added also for an unfragmented SDU, where the SID is incremented for any fragment and for any unfragmented SDU that is sent on the specific channel. An SDU may be fragmented into three fragments while a second SDU may include 512 fragments. In the latter case, the SID field 86 helps the receiver to identify each SDU fragment, even if they are received out of sequence.

The SID field 86 is also helpful when fragments are received out of order when two SDUs are sent on the same channel (one after the other) and each is fragmented into three parts. For example, SDU2_f1 (second SDU, first fragment) could be received before any fragment of SDU1. SDU1_f2 could be received next, followed by the remaining segments. To make sense of this, the defragmentation machine needs the SID to be incremented for each fragment that is sent, including the first and last fragments. Then, a distinction between SDU1_f1 and SDU2_f2 can be made, and it would be clear that SDU1_f2 does not come after SDU1_f1.

Similarly, FIG. 4 shows the management connection headers used by the preemption system 500 of FIG. 1. The newly defined fields in the fragmentation extension header (FEH) 90 are identical to the field found in the FPEH 80 (FIG. 3). Using these newly defined fields, the preemption system 500 thus provides a mechanism for the fragmentation state machine 100 at the transmitter 20 and the defragmentation machine 200 at the receiver 30 to fully identify the fragments of multiple SDUs so that fragments are neither lost nor unnecessarily retransmitted.

FIGS. 6 and 7 provide the details, from the perspective of the transmitter 20 and the receiver 30, respectively, for how the preemption system 500 operates. Before describing these details, FIG. 5 provides a simplified schematic diagram showing the preemption operations for two SDUs being wirelessly transmitted under WiMAX. The transmitter 20 is expected to transmit two SDUs, SDU1 and SDU2, each of which is split into an integer number of different fragments. SDU1 is divided into j fragments before transmission; SDU2 is divided into k fragments before transmission.

Each SDU fragment is coupled with the headers illustrated in FIGS. 3 and 4: the GMH 70 and FPEH 80 headers precede fragments for data SDUs and the GMH 70 and FEH 90 headers precede fragments for management SDUs. These headers 70, 80, 90 provide the information needed by the defragmentation state machine 200 to efficiently process all incoming fragments.

At the transmitter 20, the fragmentation state machine 100 begins to transmit the first SDU, SDU1, which is divided into fragments, denoted SDU_F1, SDU_F3, . . . , SDU_Fj. These fragments are transmitted wirelessly to the receiver 30 using a first channel, denoted channel 0. Before transmission of all SDU1 fragments is complete, the transmitter receives a request to send a second SDU, SDU2. It turns out that SDU2 has a higher priority than SDU1. As an example, SDU2 may be a power control request having only a few fragments while SDU1 may have hundreds of fragments. In prior art WiMAX implementations, the power control request is processed only after SDU1 is completely transmitted. Alternatively, the channel select mechanism 24 of the fragmentation state machine 100 establishes a second channel, channel 1, for transmitting SDU2. This enables SDU2 and SDU1 to be processed simultaneously.

On the receiver side, the defragmentation state machine 200 includes 2^N separate buffers 42 for storing SDU fragments from different channels. In the configuration of FIG. 5, N=1, thus, there are two buffers 42A and 42B, the first for channel 0 transmissions, the second for channel 1 transmissions. All fragments of each SDU are stored in a separate buffer. Further, because each fragment of each SDU is explicitly identified, the defragmentation state machine 200 can manage out-of-order transmissions of SDU fragments without having to discard them and request a resend.

Returning to FIG. 1, the defragmentation state machine 200 also includes the discard timer 34 for keeping track of the incoming SDU fragments. In some embodiments, there is a separate discard timer 34 for each buffer 42 of a non-ARQ MAC connection. Thus, in FIG. 5, there is a discard timer 34A for buffer 42A and a discard timer 34B for buffer 42B. There may also be a discard timer for each SDU in each buffer.

In some embodiments, the defragmentation state machine 200 is enhanced for non-ARQ MAC connections that only use HARQ. As described above, these types of connections can lead to out-of-order transmissions that, under the current 802.16m standard, are not resolved at the receiver, leading to SDUs being dropped. The preemption system 500 solves this problem by explicitly identifying each fragment of each SDU, allowing each SDU to be transmitted on a separate channel, and buffering each SDU fragment in a separate buffer at the receiver 30, with the different buffers being indexed by the channel ID field. So, in the example of FIG. 5, where the channel ID field indicates channel 0, the channel 0 buffer 42A used to store SDU1 fragments; where the channel ID field indicates channel 1, the channel 1 buffer 42B is used to store SDU2 fragments. The fragments of the two distinct SDUs will not be mixed together in a single data structure.

Further, the other newly defined header field, the sequence ID 86, will explicitly identify each segment of each SDU. In this manner, the receiver 30 will not be confused if the fragment, c, of SDU1 follows fragment, b, of SDU2, which follows fragment c+1 of SDU1, for integers b and c.

Further, the discard timer 34 will track the fragments of an SDU during transmission. Whenever a fragment, c, of the SDU is received on the non-ARQ connection, the discard timer for this SDU is started. In some embodiments, if all the fragments of the SDU don't arrive before the expiry of the discard timer 34, then all the fragments of that SDU that were already received are discarded. Since there is no ARQ, the MAC layer will no longer retransmit this SDU. Instead, the retransmission will be left to higher layers (if such capability exists in the higher layers).

In some embodiments, the value of the discard timer 34 is set by taking different parameters into account, such as the maximum delay time for a PDU (before the receiver gives up on receiving the missing sequence numbers, or SNs) and/or reordering buffer limitations in the receiver (which may be declared by the advanced mobile station, and influence the advanced base station's behavior on the downlink).

FIGS. 6 and 7 are diagrams showing operations of the fragmentation state machine 100 and the defragmentation state machine 200, respectively, in some embodiments. These diagrams depict a sequence of actions for a specific example when two SDUs are sent concurrently on the same FID on different channels. In FIG. 6, the fragmentation state machine transmits a first SDU, SDU1 with a flow ID 72 of one on a first MAC channel (e.g., channel 0) (block 102). A second SDU, SDU2, also arrives with a flow ID 72 of one. The headers of both SDU1 and SDU2 are populated with the FID value by the fragmentation characterization portion 22 of the fragmentation state machine 100. This second SDU, SDU2, has a higher priority than SDU1 (block 104). The channel select mechanism 24 of the fragmentation state machine 100 assigns SDU2 to a second MAC channel (e.g., channel 1) (block 106). This enables SDU1 fragments to transmit on the first channel while, simultaneously, SDU2 fragments are transmitted on the second channel (block 108). At some point, the transmission of SDU2 fragments is complete (block 110) and the transmission of SDU1 fragments is complete (block 112). It is irrelevant which SDU is received first, but both SDUs are received entirely by the receiver 30.

FIG. 7 shows the operations of the defragmentation state machine 200 to process SDU1 and SDU2. The defragmentation state machine operations show two independent paths that may occur simultaneously or serially, one for processing SDU1 (block 202-214) and the other for processing SDU2 (block 222-234). The channel identifier 32 of the defragmentation state machine 200 first determines the channel from which each fragment is received (as indicated in the headers), allowing SDU fragments of each channel to be processed separately. The scenario of FIG. 7 is for just two SDUs being transmitted wirelessly over two different channels. However, FIG. 7 could further be split into four parallel paths for N=2, eight paths for N=3, and so on.

The SDU1 fragments transmitted over the first MAC channel are received and stored in the first buffer 42A, at which point the defragmentation state machine 200 sets a first discard timer 34A (block 202). While the discard timer 34A is not expired (block 204) and before all SDU1 fragments have been received (block 208), the defragmentation state machine 200 receives additional SDU1 fragments into the first buffer 42A (block 212). Control returns to block 204 such that, before each succeeding fragment of SDU1 is received, the discard timer 34A is checked (block 204) and whether all SDU1 segments have been received is checked (block 208). Recall that the fragmentation control bits 82, found in the FPEH 80 of data SDUs and in the FEH 90 of management SDUs, indicates the last fragment of the SDU (FIGS. 3 and 4). When the FC 82 field indicates 10b, the final SDU fragment has been received.

If, on the other hand, the discard timer expires before the last fragment is received, the defragmentation state machine 200 empties the first buffer 34A, thus discarding all the fragments of the SDU1 (block 206). Where the discard timer has not expired, if all SDU1 segments have been received, the receiver 30 is able to identify each fragment, even where the fragments were obtained out-of-order, and decode SDU1 (block 210). For either the case where the buffer 42A is emptied of all fragments (block 206) or SDU1 is successfully decoded (block 210), the discard timer 34A is reset (block 214). For SDU1, the operations of the defragmentation state machine 200 is thus complete.

The operations for receiving the fragments of SDU2 mirror those of SDU1. The SDU fragments are stored in the second buffer 42B and the second discard timer 34B is set (block 222), and further SDU2 fragments are received (block 232) if the discard timer has not expired (block 224) and the receiver has not received all fragments (block 228). These operations are repeated until either the discard timer expires (block 224), in which case the second buffer 42B is emptied (block 226), causing all received SDU2 fragments to be discarded. Where all fragments have been successfully received, the receiver 30 decodes SDU2 (block 230) and the discard timer 34B is reset (block 234).

In some embodiments, there exists a single fragmentation state machine 100 and a single defragmentation state machine 200 for each connection. Also, in some embodiments, the defragmentation state machine 200 drops all fragments associated with the same SDU if any of them is treated as a loss at the HARQ layer.

The preemption system 500 of FIG. 1 may be found in a variety of different systems that are associated with WiMAX transmissions. For example, the preemption system 500 may be part of an advanced mobile station or an advanced base station supporting 802.16m. Both of these WiMAX entities are involved with both transmission and reception of packets; therefore, both entities need a transmitter and a receiver. FIG. 8 is a simplified block diagram of a transceiver 400 (transmitter and receiver), which includes the transmitter 20 with the fragmentation state machine 100 and the receiver 30 with the defragmentation state machine 200. Each state machine 100, 200 includes the features described above and illustrated in FIG. 1. With the fragmentation state machine 100, the transmitter 120 is able to explicitly characterize fragments before transmission and to separate fragments of different SDUs onto different transmission channels. With the defragmentation state machine 200, the receiver 130 is able to identify and buffer each fragment received based on its source channel and further process the fragments, despite their out-of-order transmission. Note that, in the transceiver 400, the transmitter 120 does not transmit to the receiver 130, but to a remote receiver (not shown) found on another device in the WiMAX network; likewise, the receiver 130 does not receive packets from the transmitter 120, but from a remote transmitter (not shown).

While the application has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of the invention.

Claims

1. A fragmentation state machine in a transmitter, the fragmentation state machine comprising: a fragmentation characterization engine to:generate a header for each fragment of a first service data unit (SDU), the first SDU comprising a plurality of fragments, the first SDU having a flow identifier (ID) indicating a first medium access channel (MAC)/flow connection, the header of each fragment comprising:a first channel ID to indicate a first fragmentation channel through which the fragment of the first SDU is transmitted;a sequence ID indicating a numerical location of the fragment in the first SDU; anda fragmentation extension ID indicating whether the fragment is a first fragment, a last fragment, or a middle fragment of the first SDU, or whether the first SDU is unfragmented; andgenerate a second header for each fragment of a second SDU, the second SDU comprising a plurality of fragments and the same flow ID as the first SDU, the second header of each fragment of the second SDU comprising:a second channel ID to indicate a second fragmentation channel through which the fragment of the second SDU is transmitted;a sequence ID indicating a relative numerical location of the fragment in the second SDU; anda fragmentation extension ID indicating whether the fragment is a first fragment, a last fragment, or a middle fragment of the second SDU, or whether the second SDU is unfragmented;wherein the fragments of the first and second SDUs are wirelessly transmitted on separate fragmentation channels of the same MAC/flow connection to a receiver.

2. The fragmentation state machine of claim 1, wherein transmission of the second SDU is initiated on the second fragmentation channel before transmission of the first SDU is completed on the first fragmentation channel.

3. The fragmentation state machine of claim 2, wherein the second SDU has a higher priority than the first SDU.

4. The fragmentation state machine of claim 1, wherein the flow ID is obtained from a field of a generic MAC header preceding each fragment.

5. The fragmentation state machine of claim 1, wherein the channel ID, the sequence ID, and the fragmentation extension ID are fields in a fragmentation and packing extension header preceding each fragment, the fragment comprising data.

6. The fragmentation state machine of claim 1, wherein the channel ID, the sequence ID, and the fragmentation extension ID are fields in a fragmentation extension header preceding each fragment, the fragment comprising management information.

7. A defragmentation state machine in a receiver, the defragmentation state machine comprising: means to decode a header of each fragment of either a first service data unit (SDU) or a second SDU, wherein the first SDU is received wirelessly from a transmitter on a first fragmentation channel and the second SDU is received wirelessly from the transmitter on a second fragmentation channel, the first SDU comprising a flow ID and second SDUs comprising the same flow ID, each header comprising:a channel ID, wherein the first SDU channel ID header indicates the first fragmentation channel and the second SDU channel ID header indicates the second fragmentation channel;a sequence ID indicating a numerical location of the fragment in its respective SDU; anda fragmentation extension ID indicating whether the fragment is a first fragment, a last fragment, or a middle fragment of the respective SDU, or whether the respective SDU is unfragmented;a first buffer to receive fragments received on the first fragmentation channel;a second buffer to receive fragments on the second fragmentation channel, wherein the channel ID operates as an index into the buffers of the receiver;

8. The defragmentation state machine of claim 7, wherein the flow identifier indicates the MAC/flow connection through which the fragment is wirelessly received from the transmitter.

9. The defragmentation state machine of claim 8, further comprising: a first discard timer to keep track of fragments stored in the first buffer, wherein all fragments of the first SDU are received before the first SDU is decoded; anda second discard timer to keep track of fragments stored in the second buffer, wherein all fragments of the second SDU are received before the second SDU is decoded.

10. The defragmentation state machine of claim 8, wherein the flow identifier is obtained from a field of a generic MAC header preceding each fragment.

11. The defragmentation state machine of claim 9, wherein the fragmentation extension ID, the channel ID, and the sequence ID are obtained from fields in a fragmentation and packing extension header preceding each fragment of a service data unit comprising data.

12. The defragmentation state machine of claim 9, wherein the fragmentation extension ID, the channel ID, and the sequence ID are obtained from fields in a fragmentation extension header preceding each fragment of a service data unit comprising management information.

13. The defragmentation state machine of claim 9, wherein the first buffer is emptied if the first discard timer expires before all fragments of the first service data unit are received from the transmitter.

14. The defragmentation state machine of claim 9, wherein the second buffer is emptied if the second discard timer expires before all fragments of the second service data unit are received from the transmitter.

15. The defragmentation state machine of claim 9, wherein the first discard timer has a value based on a maximum delay time for a protocol data unit.

16. A transceiver, comprising: a transmitter comprising a fragmentation state machine, the fragmentation state machine to: separately characterize each fragment of a service data unit (SDU) by adding a header to the fragment before transmission; andsend fragments of two distinct SDUs over different fragmentation channels to a remote receiver, wherein the two distinct SDUs share a flow identifier (ID); anda receiver comprising a defragmentation state machine, the defragmentation state machine to: store each fragment received from a remote transmitter into one of a plurality of buffers, with the selected storage buffer being based on a channel ID of the fragment, until either all fragments of a service data unit associated with that fragmentation channel are received or a discard timer expires; andfor each buffer, identify the characterized fragments of the service data unit associated with the fragmentation channel and reorder them if needed.

17. The transceiver of claim 16, wherein the one or more headers comprise the following fields: a flow identifier field to indicate the MAC/flow connection of the associated SDU;a fragment control field to indicate whether the fragment is one of several fragments and, if so, whether the fragment is a first fragment, a last fragment, or a middle fragment;a channel identifier field to specify the fragmentation channel through which the fragment is to be wirelessly transmitted to the remote receiver; anda sequence identifier field to characterize the fragment as either a first fragment, a last fragment, or a middle fragment of the respective SDU, or whether the respective SDU is unfragmented.

18. The transceiver of claim 16, wherein the defragmentation state machine discards the contents of the buffer storing the fragments without decoding the respective SDU if the discard timer expires.

19. The transceiver of claim 17, wherein the flow identifier field is part of a generic MAC header and the fragment control field, the channel identifier field, and the sequence identifier field are part of a fragmentation and packing extension header of a data packet.

20. The transceiver of claim 17, wherein the flow identifier field is part of a generic MAC header and the fragment control field, the channel identifier field, and the sequence identifier field are part of a fragmentation extension header of a management packet.