Methods and apparatus for formatting headers in a communication frame

BACKGROUND

Field

0001The present disclosure generally relates to methods and apparatus for formatting a header in a communication frame, and more specifically to formatting headers within a communication frame to optimize the frame for either processing or header size.

Background

0002In particular wireless communication systems, signals are transmitted in a frame format. Within the frame format, information is packetized and formatted according to actual payload data to be communicated over the communication system and other overhead information that is used for communicating various other information particular to the communication system, such as information used for timing acquisition and decoding the frame, as examples. This overhead information is typically arranged into a header packet within the frames, and associated with a corresponding payload data packet to which the header information pertains.

0003In some types of communication having low data rate (and small packet sizes), such as Voice-over-IP (VoIP) for example, it is desirable to minimize the header overhead information in order to increase system capacity, such as supporting more VoIP calls in system). Additionally, it is noted that at the media access control (MAC) layers and higher, frames are organized such that the headers are formatted in order of processing immediately before their associated data packets or payloads. With communications having higher data rates and larger packet sizes, however, the header size naturally increases for processing of the larger packets at the receiver. Utilizing a typical format with headers organized for processing before each corresponding data packet that is favorable for low data rate communications, tends to slow processing of the larger packets and their larger headers at a receiver during high data rate communications. Accordingly, a need exists to accommodate both low data rate communications and high data rate communications in a communication system, while allowing a mechanism to improve the efficiency of header processing for high data rate communications.

0004The <patcit id="pcit0001" dnum="US2004184450A"><text>US patent application publication US 2004/184450</text></patcit> relates to transport and routing of packets over frame-based networks.

0005The International patent application publication <patcit id="pcit0002" dnum="WO2006052085A"><text>WO 2006/052085</text></patcit> relates to method and apparatus for transmitting control information relating to an uplink packet data service from an UE to a Node B in a mobile communication system.

0006The US patent application publication <patcit id="pcit0003" dnum="US2006146868A"><text>US 2006/146868</text></patcit> relates to selective aggregation of transmission streams.

0007The European patent application <patcit id="pcit0004" dnum="EP1494425A"><text>EP 1 494 425</text></patcit> discloses that packets of Advanced Systems Format (ASF) audio-visual (AV) data are repacketized into Real-Time Transport Protocol (RTP) packets and sent over a network from a server to client or by peer-to-peer network communications in response to a request to stream the AV data. The AV data is encrypted to form encryption units. The repacketizing process includes packetizing the encryption units into the RTP packets each of which includes an RTP packet header, one or more payloads of a common data stream, and a RTP payload format (PF) header for each payload. The RTP PF header includes, for the corresponding encryption units, a boundary for the payload. The payload in the RTP packet can be one or more encryption units or a fragment of an encryption unit. After the RTP packets are sent over a network, the encryption units contained in the received RTP packets are reassembled. The reassembly process uses the payloads in the RTP packets and the respective boundary in the respective RTP PF header. The reassembled encryption units can be decrypted for rendering. Each RTP PF header can have attributes for its corresponding payload that can be used to render the payload.

0008The US patent <patcit id="pcit0005" dnum="US5828858A"><text>US 5,828,858</text></patcit> discloses a worm-hole run-time reconfigurable processor field programmable gate array.

0009The US patent application publication <patcit id="pcit0006" dnum="US2006256818A"><text>US 2006/256818</text></patcit> relates to transmitting and receiving data.

SUMMARY

0010The invention is defined by the independent claims. Further embodiments are disclosed in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

0011<ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> illustrates a wireless communication system 100 in which the presently disclosed methods and apparatus may be employed.</li><li><figref idref="f0002">FIG. 2</figref> illustrates an exemplary media access control (MAC) layer frame formatting for header optimization that may be transmitted in a UMB system of <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0003">FIG. 3</figref> illustrates an alternate exemplary media access control (MAC) layer frame formatting for processing optimization that may be transmitted in a UMB system.</li><li><figref idref="f0004">FIG. 4</figref> illustrates a method for formatting communication frames that may be used by a base station, AP, or other transmitter of a communication system, such as UMB or LTE communication systems.</li><li><figref idref="f0005">FIG. 5</figref> illustrates an exemplary sequential series of frame assembly through multiple layers in an LTE system.</li><li><figref idref="f0006">FIG. 6</figref> illustrates exemplary headers that may be used for the headers of the various layers illustrated in <figref idref="f0005">FIG. 5</figref>.</li><li><figref idref="f0007">FIG. 7</figref> illustrates a flow chart of such an exemplary method for use in formatting the header configuration in a communication frame dependent on the payload or data packet size.</li><li><figref idref="f0008">FIG. 8</figref> illustrates an exemplary transceiver that formats and transmits the communication frames based on packet data size in accordance with the disclosed formats and methods.</li><li><figref idref="f0009">FIG. 9</figref> illustrates a further example of an apparatus for use in a transceiver in a communication system that may be utilized for formatting headers in communication frames.</li><li><figref idref="f0010">FIG. 10</figref> illustrates a still further example of an apparatus for use in a transceiver in a communication system that may be utilized for formatting headers in communication frames.</li></ul>

DETAILED DESCRIPTION

0012In an aspect, the presently disclosed methods and apparatus provide frame formatting that engenders optimized processing for frames received at a mobile device, such as an access terminal (AT), for instance. This is accomplished through a frame format that arranges headers at the beginning of a wireless communication frame prior to the payload packets, particularly for frames having large payload packets, and thus larger frame size. When processed at a receiver, such formatting affords more efficient processing than frames arranged where each header is placed with its associated payload. In another aspect, the presently disclosed methods and apparatus provide frame formatting that is dependent on either the overall size of the communication frame (e.g., a MAC Frame) or the size of payload packets within a particular communication frame. If the frame or the payload packets in a frame are smaller, such as for VoIP communications, the headers are arranged in conjunction with their associated payload packet in order to optimize the header size. On the other hand, if the communication frame or the payload packets within the frame are large, such as for high throughput data communications, such as UMB or LTE, the frames are alternately arranged to include all headers up front in the frame prior to the payload packets in order to optimize the ability of a receiver processing the frame. In this manner, the frame formatting is tailored to be most optimal for the type of communication effected with the frame.

0013In the following described examples, for reasons of conciseness and clarity the disclosure uses some terminology associated with Ultra Mobile Broadband (UMB) technology. It should be emphasized, however, that the presently described examples are also applicable to other technologies, such as technologies related to Long Term Evolution (LTE), Code Division Multiple Access (CDMA), cdma2000 EV-DO, Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA) and so forth. It will be appreciated by those skilled in the art, that when applying the disclosed methods and apparatus to other technologies, the associated terminology would clearly be different. As examples, an access point (AP) may be a fixed station used for communicating with the terminals and may also be referred to as an access point, a Node B, base station, or some other terminology. An access terminal (AT) may also be called an access terminal (AT), user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

0014According to an aspect, <figref idref="f0001">FIG. 1</figref> illustrates a wireless communication system 100 in which the presently disclosed methods and apparatus may be employed. An access point (AP) or base station 102 transmits information to access terminals 104 over forward links 106, 108. The transmitted information may be arranged in communication frames to packetize the data.

0015An access point (AP) may be a fixed station used for communicating with the terminals and may also be referred to as an access point, a Node B, or some other terminology. An access terminal (AT) may also be called an access terminal, user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

0016<figref idref="f0002">FIG. 2</figref> illustrates an exemplary media access control (MAC) layer (and above) frame formatting that may be transmitted with AP 102 in the system of <figref idref="f0001">FIG. 1</figref>, for example. Frame 200, in particular, is exemplary of a UMB format for header optimization, such as for smaller payload packets. As discussed above, VoIP communication utilizes smaller payload packets, but frame 200 is not limited solely to such, and is optimal with various other types of communications which are timing sensitive in manner similar to voice communications. As illustrated, the MAC frame 200 includes a one or more frame headers 202 (shown singular for brevity) for each packet within the frame 200. Headers 202 are referred to as a Packet Consolidation Protocol (PCP) headers, are arranged first in the frame 200, and serve to indicate where to find the various n number of data packets within the communication frame 200. After header 202, a first header 204 is shown placed immediately prior to an associated or corresponding data payload 206. The headers, as will be explained later, may be configured according to Radio Link Protocol, Stream Protocol, fragmentation and reassembly protocol, or logical channel identification protocol, as examples. The pair of the header and payload, such as header 204 and payload 206, may be termed as a "packet", and more specifically a MAC packet in the present example.

0017After payload 206, a next header 208 and an associated payload 210 come in sequential order through an n^th header 212 and associated data payload or packet 214. After the header and data payload pairs, a trailer 216 for MAC frame 200 may be included to delineate or signal an end of the frame 200, or at least the end of the n number of data payloads within the frame 200. The overall size of the frame 200 is illustrated in <figref idref="f0002">FIG. 2</figref> by the dimension 217.

0018<figref idref="f0002">FIG. 2</figref> also illustrates an expanded or blown up view 218 of an exemplary upper layer header that is applicable to all headers of frame 200, such as header 204. As may be seen, header 218 includes a number of fields, some of which are variable in bit length and dependent of the size of the payload or data packet to which it corresponds. Accordingly, this allows the header to be varied according to the particular size of the data payload or the packet.

0019As illustrated, header 218 may include a Route Header 220, which has Route bits of variable bit length to indicate destination route of the packet. Header 218 may also include Stream Header 222 to indicate a stream corresponding to this packet. Additionally, the header 218 includes a radio link protocol (RLP) header that includes a Ciphering Key Index 224, a SAR (Segmentation and Reassembly) Sequence field 226, First + Last filed 228, and a Quick Nak (QN) header 230. The RLP header is derived or obtained from another layer than the MAC layer and added to the header 218. Various fields in the RLP header may also be variable based on the packet size, such as the SARSeq field 226 or the QN Header 230. It is noted that the RLP header is derived from other layers (e.g., RLP layer or when assembling the headers for the MAC layer frame 200.

0020It is also noted that the PCP header 202 may also be formatted to include information fields (not shown) to indicate if more than one PCP header is present in the frame 200. The PCT header 202 may also include short or long length field that used to indicate expanded payload lengths in the case of a long field to support larger Segmentation and Reassembly Protocol Data Unit (SAR PDU) payload sizes. As an example, the length field in the PCP header may be 6 bits in length to indicate shorter payload lengths up to 64 bytes and a length field of 14 bits to indicate large payload lengths of up to 16,384 bytes.

0021<figref idref="f0003">FIG. 3</figref> illustrates an alternative exemplary media access control (MAC) layer (and above) frame formatting that may be transmitted with AP 102 in the system of <figref idref="f0001">FIG. 1</figref>, for example. In particular, the frame 300, which is a MAC layer frame for a UMB system in this example, is arranged or formatted to afford optimized processing by a receiver receiving and processing the frame. As may be seen in <figref idref="f0003">FIG. 3</figref>, the frame 300 includes an n number of headers (302, 304, through 306) arranged at the beginning of frame 300 prior to their corresponding payloads (308, 310, 312). As has been discovered by the present inventors, this arrangement of the headers and payloads within a communication frame, such as frame 300, has proven to optimize processing at a receiver demodulating and decoding the frame.

0022Frame 300 may also include a Number of Headers packet 314 at the beginning of the frame (e.g., a one byte field indicating the number of data packets in the frame 300). The packet 314 communicates the number of header packets (i.e., n number) within the frame 300. Frame 300 also includes a MAC trailer 315 that ends the frame 300.

0023Also illustrated in <figref idref="f0003">FIG. 3</figref> is an expanded view 316 of a typical header, such as header 302. As illustrated by view 316, the header includes a PCP header 318 that may be used to communicate PCP information from another layer, as well as route header information. The header also may included an RLP header having a reserved field 320, Encryption Key Index field 322, First + Last field 324, and a Cryptosync field 326. Furthermore, within the Cryptosync filed, various bits (not shown) may be used to indicate a Function code, direction, a router counter, a stream ID, a SAR Reset Counter, and a virtual SAR Sequence number. It is noted that in an example that the Cryptosync may be set to 96 bits in length.

0024Additionally, according to an aspect, the length of the headers in frame 300 may be set to a fixed size to enhance optimization of processing by a receiver. By fixing the size of the header, processing at the receiver is further optimized as a fixed size affords predictability for the processing receiver and serves to prevent bottlenecks in the processing by a receiver. The particular length of the headers may be set according to the particular system or type of communication being effected with the communication frame.

0025<figref idref="f0004">FIG. 4</figref> illustrates a method for formatting communication frames that may be used by a base station, AP, or other transmitter of a communication system, such as UMB or LTE communication systems. As illustrated, a size of a wireless communication frame, such as a MAC frame, to be assembled is determined, as illustrated by block 402. It is noted that this size determination may be based on the total size of the wireless frame (e.g., 217), or alternatively the size determination may be based on one or more of the size(s) of data payloads in the communication frame. As another alternative, the size determination in block 402 may be based on whether the type of communication is known (e.g., broadband communication with attendant large frame size). Thus, if the communication is broadband communication, such as in UMB or LTE systems, it is known that the frame size will be large as compared to other communication such as VoIP.

0026According to the method of <figref idref="f0004">FIG. 4</figref>, the MAC frame is then assembled where a plurality of headers each corresponding to a respective MAC payload are arranged in the communication frame prior to the plurality MAC payloads when the determined size of the frame is greater than a predetermined threshold as illustrated by the process in block 404. As discussed above, by arranging all of the MAC headers before any of the MAC payloads, such as illustrated by the example of <figref idref="f0003">FIG. 3</figref>, processing of the communication frame may be optimized at the receiver.

0027According to an alternative aspect, the size determination in block 402 may be based on determination of the size of at least one of the payloads and corresponding headers, rather than on the overall communication frame size. Accordingly, the decision to format the frame by placing headers before any payloads in block 404 would then be based on whether it is determined that at least one payload and header size is greater than a predetermined threshold

0028As an example of a process by which the MAC payloads may be formed or assembled in the process of blocks 402 and 404, <figref idref="f0005">FIG. 5</figref> illustrates a sequential series of frame assembly through multiple layers. It is noted that the terminology used in this example pertains to LTE communication systems, but the concepts are not limited to such and may be applied to UMB or any number of other suitable communication systems. As illustrated, a data packet 502, such as a data IP packet, is associated with or added with a Packet Data Convergence Protocol (PDCP) header 504 at the PDCP layer. This header 504, as an example, may include a PDCP Sequence Number (SN). In a further aspect, the SN may be 7 or 12 bits in length, dependent on the logical channel. The pairing of the data packer 502 and PDCP Header 504 may optionally include an added trailer with a security checksum (e.g., a 4 byte field).

0029The pairing 502, 504 is then next associated with or added to a radio link control (RLC) header 506 at a next RLC layer. Finally, the combined RLC payload consisting of the RLC header 506, PDCP header 504, and data packet 502, or multiple RLC payloads (not shown) may be then assembled for use as a MAC payload 508 at the MAC layer. As may be seen in this example, the MAC payload 508, designated as MAC Payload 1, is associated with a MAC header 510. As further illustrated, a MAC Payload 2 (512) is also placed in a communication frame with an associated MAC Header 2 (514), which is located prior to the MAC payloads (508, 512).

0030<figref idref="f0006">FIG. 6</figref> illustrates exemplary headers that may be used for the headers of the various layers illustrated in <figref idref="f0005">FIG. 5</figref>. Again, as in <figref idref="f0005">FIG. 5</figref>, the terminology used in this example pertains to LTE communication systems, but the concepts are not limited to such and may be applied to UMB or any number of other suitable communication systems. As illustrated, a PDCP Header 602 includes a control field 604 of 4 bits and a sequence number field 606 having either 7 or 12 bits. An RLC Header 608 particular to a mode such as Unacknowledged Mode or VoIP, may include a control field 610 having 3 or 6 bits, and sequence number field 612 of 5 or 10 bits. Another alternative for an RLC header for an Acknowledged Mode such as FTP/TCP, is shown by header 614 having a control field of 6 bits and a sequence number of 10 bits.

0031A MAC header 616 may consist of a control field 618 having 3 bits, a logical channel ID field 620 that is 5 bits in length, and a Length field 622 of 7 or 15 bits. Additionally, the size of the headers may be fixed for larger data packet sizes. Thus, in the example of <figref idref="f0006">FIG. 6</figref>, the RLC sequence number 606 would be set at 10 bits, the PDCP sequence number 604 set at 12 bits, and the MAC header length filed 622 at 15 bits.

0032According to another aspect, the formatting of communication frames may be made dependent on the size of the payload data packets in order to optimize the formatting for communication types. When the payload frames are small, such as in VoIP communications, the communication frame may be formatted to first format, such as a format to optimize header sizing. Conversely, when payloads are large, such as in high throughput communications, the communication frame may be alternatively formatted to another format, such as a format to optimize processing of the frame at a receiver.

0033<figref idref="f0007">FIG. 7</figref> illustrates a flow chart of such an exemplary method for use in formatting the header configuration in a communication frame dependent on the size of the communication frame. As shown, the size of the communication frame to be formatted is determined in block 702. After determination of the size of the communication, flow proceeds to block 704. At block 704 at least one header corresponding to the at least one data packet is formatted according to a first format when the size of the packet is below a predetermined size and according to a second format when the size of the packet is equal to or greater than the predetermined size. The predetermined size is dependent on the communication system and attendant standards. As merely an example, clearly large packets on the order to 4000-6000 bytes in UMB or LTE communications would be above the predetermined threshold, whereas much smaller VoIP packets of 40-50 bytes would be well below the predetermined threshold.

0034According to an aspect, the first format may include variably configuring the size of the at least one header based on a length of the corresponding at least one data packet. As an example from <figref idref="f0002">FIG. 2</figref>, the header 218 in a header optimized format utilizes various variable length fields, such that the header may be sized or tailored based on the size of the data packet. This variability affords the ability to ensure that the header size is optimized to be as small as possible for a given data packet. Additionally, the first format of block 704 may also include grouping the at least one header with the corresponding at least one data packet within the communication frame, as illustrated by the example of frame 200 in <figref idref="f0002">FIG. 2</figref>, which is suited for particular types of communication such as voice over IP communications.

0035According to another aspect, the second format in block 704 may include placing the at least one header in the communication frame prior to and independent from the corresponding at least one data packet. That is, each header corresponding to a data packet is separated or made independent from the data packet and placed prior to the data packets or payloads in the communication frame. An example of this formatting is illustrated by MAC frame 300 in <figref idref="f0003">FIG. 3</figref>. By separating the headers from their associated payloads or data packets, especially in the case of large data packets used in data communications (e.g., TCP/IP), a resultant benefit is more efficient processing of the communication frame at a receiver, as header processing may be begin while waiting to receive the actual payloads that will be demodulated and decoded.

0036In an example of the second format in block 704, the size of the at least one header may be set to at a prescribed fixed length, such as was discussed above in connection with the example of the MAC header in <figref idref="f0005">FIG. 5</figref>. By setting the headers to a fixed length, a benefit of predictability afforded to the receiver. When the size of each header is known to the receiver, less processing is required to determine how many bits will be present in header, thereby contributing to further optimization of processing.

0037According to still another aspect of the second format in block 704, the header format of the second information used by a receiver of the communication frame for ciphering or processing the at least one data packet is contained within the at least one header. As an example of this feature, <figref idref="f0003">FIG. 3</figref> illustrates that the header 316 includes the PCP header 318 within each header such that the PCT and Route information is contained within each respective header. Accordingly, processing of the headers may be optimized and the headers themselves may be independent from other headers, and more importantly, their corresponding data packets. This is in contrast to the header optimized format of <figref idref="f0002">FIG. 2</figref>, where the PCP headers 220 are separate from the headers (e.g., 202) and are processed prior to processing of the grouping of headers and data packets.

0038<figref idref="f0008">FIG. 8</figref> illustrates an exemplary transceiver 800 that formats and transmits the communication frames based on packet data size in accordance with the formats and methods disclosed herein. Transceiver 800 may constitute an AP (e.g., AP 102 in <figref idref="f0001">FIG. 1</figref>), a base station, or other suitable hardware (e.g., processor, or a collection of circuits/modules), software, firmware, or any combination thereof for use in an AP device. As illustrated, transceiver 800 includes a central data bus 802, or similar device for communicatively linking or coupling several circuits together. The circuits include a CPU (Central Processing Unit) or a controller 704, transceiver circuits 806, and a memory unit 808.

0039The transceiver circuits 806 include receiver circuits to process received signals before sending out to the central data bus 802, as well as transmit circuits to process and buffer data from the data bus 802 before sending out of the device 800, such as to one or more ATs as illustrated by wireless communication link(s) 810. Accordingly, the transceiver circuits 806 may include RF circuits to transmit over the wireless link 810 to the one or more ATs.

0040The CPU/controller 806 performs the function of data management of the data bus 802 and further the function of general data processing, including executing the instructional contents of the memory unit 808. It is noted here that instead of separately implemented as shown in <figref idref="f0008">FIG. 8</figref>, as an alternative, the transceiver circuits 706 can be incorporated as parts of the CPU/controller 704. As a further alternative, the entire apparatus 700 may be implemented as an application specific integrated circuit (ASIC) or similar apparatus.

0041The memory unit 808 may include one or more sets of instructions/modules. In the exemplary apparatus 800, the instructions/modules include, among other things, a frame formatting function 812, which is configured to effect the methodologies described herein; namely the frame formatting discussed above in connection with <figref idref="f0002 f0003 f0004 f0005 f0006 f0007">FIGs. 2-7</figref>. In the example of <figref idref="f0008">FIG. 8</figref>, the memory unit 808 may be a RAM (Random Access Memory) circuit. The exemplary portions, such as the functions in block 812, are software routines, modules and/or data sets. The memory unit 808 can be tied to another memory circuit (not shown) which either can be of the volatile or nonvolatile type. As an alternative, the memory unit 808 can be made of other circuit types, such as an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM (Electrical Programmable Read Only Memory), a ROM (Read Only Memory), an ASIC (Application Specific Integrated Circuit), a magnetic disk, an optical disk, and other computer-readable media well known in the art.

0042<figref idref="f0009">FIG. 9</figref> illustrates a further example of an apparatus for use in a transceiver in a communication system that may be utilized for formatting headers in communication frames. It is noted that the apparatus 900, may be implemented in an AP or base station, as examples. It should be further noted, that disclosed apparatus 900 is not limited to implementation only in an AP or base station, but also any suitable apparatus that formats communication frames for transmission.

0043Apparatus 900 includes a module or means 902 for determining a size of a wireless communication frame (or alternatively the size of one or more data payloads within the communication frame). As an example, means 902 may be implemented with one or more components within a transceiver. As an example from <figref idref="f0008">FIG. 8</figref>, the memory 810 in conjunction with CPU/Controller 804 may effect means 902. The information determined by means 902 may then be communicated to various other modules or means in apparatus 900 via a bus 904, or similar suitable communication coupling.

0044Apparatus 900 also includes a means 906 for formatting the communication frame to include one or more headers at the beginning of the frame prior to any data packets in the frame when the determined size of the wireless communication frame is above a predetermined threshold. Alternatively, means 906 may determine that a size of one or more data payloads is above a predetermined threshold in order to decide whether to format the headers at the beginning of a frame. It is noted that means 906 may implement the processes of block 404 and the formatting shown in <figref idref="f0003">FIGs. 3</figref> or <figref idref="f0005">5</figref>, as examples. Similar to means 902 above, means 906 may be implemented with one or more components within a transceiver, and more specifically by those that effect assembly or organization of communication frames, particularly MAC frames. As an example from <figref idref="f0008">FIG. 8</figref>, the memory 810 in conjunction with CPU/Controller 804 may effect means 906. Means 906 may communicate with transceiver circuits 908 to effect transmission of communication frames having the desired formatting performed by means 906.

0045In addition, apparatus 900 may include an optional computer readable medium or memory device 910 configured to store computer readable instructions and data for effecting the processes and behavior of one or more of the modules in apparatus 900. Additionally, apparatus 900 may include a processor 912 configured to execute the computer readable instructions in memory 910, and thus may be configured to execute one or more functions of the various modules in apparatus 900.

0046<figref idref="f0010">FIG. 10</figref> illustrates a still further example of an apparatus 1000 for use in a transceiver in a communication system that may be utilized for formatting headers in communication frames. It is noted that the apparatus 1000, may be implemented in an AP or base station, as examples. It should be further noted, that disclosed apparatus 1000 is not limited to implementation only in an AP or base station, but also any suitable apparatus that formats communication frames for transmission.

0047Apparatus 1000 includes a module or means 1002 for determining a size of MAC wireless communication frame. In an alternative aspect, the size of one or more data payloads to be placed in the communication frame may be determined by means 1002. As an example, means 1002 may be implemented with one or more components within a transceiver. As an example from <figref idref="f0008">FIG. 8</figref>, the memory 810 in conjunction with CPU/Controller 804 may effect means 1002. The information determined by means 1002 may then be communicated to various other modules or means in apparatus 1000 via a bus 1004, or similar suitable communication coupling.

0048Apparatus 1000 also includes a means 1006 for formatting header corresponding to the at least one packet according to a first format when the size of the MAC wireless communication frame is below a predetermined size, and format the at least one header according to a second format when the size of the packet is equal to or greater than the predetermined size. It is noted that means 1006 may implement the processes of block 704 in <figref idref="f0007">FIG. 7</figref> and the formatting shown in both <figref idref="f0002">FIG. 2</figref> and <figref idref="f0003">FIGs. 3</figref> or <figref idref="f0005">5</figref>, as examples, dependent on the size of the communication frame. Also, means 1006 may alternatively be configured to decide formatting based on whether a size of one or more data payloads in a frame is either above or below a predetermined threshold. Similar to means 1002 above, means 1006 may be implemented with one or more components within a transceiver, and more specifically by those that effect assembly or organization of communication frames, particularly MAC frames. As an example from <figref idref="f0008">FIG. 8</figref>, the memory 810 in conjunction with CPU/Controller 804 may effect means 1006. Means 1006 may communicate with transceiver circuits 1008 to effect transmission of communication frames having the desired formatting performed by means 1006.

0049In addition, apparatus 1000 may include an optional computer readable medium or memory device 1010 configured to store computer readable instructions and data for effecting the processes and behavior of one or more of the modules in apparatus 1000. Additionally, apparatus 1000 may include a processor 1012 configured to execute the computer readable instructions in memory 1010, and thus may be configured to execute one or more functions of the various modules in apparatus 1000.

0050In light of the above discussion, it can be appreciated that the presently disclosed methods and apparatus afford formatting of headers in a communication frame that improves processing time for frames having large payloads. Additionally, the present disclosed methods and apparatus afford a selective optimizing of communication frames for header minimization or processing efficiency based on the payload sizes.

0051It is understood that the specific order or hierarchy of steps in the processes disclosed is an example of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

0052Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

0053Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, means, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

0054The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

0055The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium (not shown) may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

0056The examples described above are merely exemplary and those skilled in the art may now make numerous uses of, and departures from, the above-described examples without departing from the inventive concepts disclosed herein. Various modifications to these examples may be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples, e.g., in an instant messaging service or any general wireless data communication applications, without departing from the scope of the novel aspects described herein. Thus, the scope of the disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. It is noted that the word "exemplary" is used exclusively herein to mean "serving as an example, instance, or illustration." Any example described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other examples. Accordingly, the novel aspects described herein are to be defined solely by the scope of the following claims.