RIM071-03PC

Fragmenting Large Packets in the Presence of High Priority Packets

BACKGROUND

[0001] IEEE 802.11 Enhanced Distributed Channel Access (EDCA) is a method of medium access defined in IEEE 802.1 Ie and is an enhancement to the original IEEE 802.11 Media Access Control (MAC) sublayer. EDCA provides four prioritized queues for data transmission. The queues use a contention-based mechanism to determine the next packet for transmission. The queue parameters are set such that the high priority queues have a preference for access to the wireless medium.

[0002] When the size of the MAC protocol data units (MPDUs) being transmitted for each class of traffic are approximately the same, the contention mechanism works well. However, when the MPDUs are of different sizes, the larger MPDU transmissions end up taking more medium time. For a device that is transmitting small voice MPDUs and large best effort MPDUs, the best effort traffic will introduce delays in the transmission of the voice traffic.

RIM071-03PC

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like reference numerals indicate corresponding, analogous or similar elements, and in which:

[0004] FIG. 1 illustrates an exemplary mobile station;

[0005] FIGS. 2 and 3 are flowcharts of an exemplary method for controlling transmission of traffic from a mobile station over a wireless medium;

[0006] FIG. 4 is a flowchart of another exemplary method for controlling transmission of traffic from a mobile station over a wireless medium; and

[0007] FIGs. 5-1 and 5-2 are exemplary timing diagrams that illustrate high priority traffic and low priority traffic sharing a wireless medium.

[0008] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity.

RIM071-03PC

DETAILED DESCRIPTION

[0009] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of embodiments. However it will be understood by those of ordinary skill in the art that the embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the embodiments.

[0010] A mobile station controls transmission of traffic over a wireless medium by dynamically adjusting a fragmentation threshold in a wireless local area network (WLAN) medium access control (MAC) layer of the mobile station according to the presence or absence of high priority traffic. In the absence of high priority traffic received at the mobile station over the wireless medium or to be transmitted by the mobile station over the wireless medium, the fragmentation threshold is set to a first value. In the presence of high priority traffic, the fragmentation threshold is set to a value that is smaller than the first value.

[0011] The first value may be a large fragmentation threshold to promote efficient transmission of low priority traffic. The second value may be larger than any expected size of MAC service data unit (MSDLJ) for high priority traffic, so as not to fragment high priority traffic. The second value may be slightly larger than the largest expected size of MSDU for high priority traffic.

[0012] A stream control application in the mobile station may be monitored to determine whether the high priority traffic is present. The stream control application may also be monitored to determine an expected size of MSDUs for the high priority traffic.

[0013] Although this description states "first value" and "second value", these are only labels and it is contemplated that there will be more than one "second value". The "second value" may depend on what is considered to be high priority traffic and what is considered to be low priority traffic. For example, if the high priority traffic is voice traffic, the low priority traffic may be considered to comprise video traffic, best effort traffic and background traffic. Since voice MSDUs are typically around 108 bytes in size, the "second value" may be set to 256 bytes, for example. If the high priority traffic is real-time video traffic, the low priority traffic may be considered to comprise best effort traffic and background traffic. Since video

RIM071-03PC

MSDUs are typically around 500 bytes in size, the "second value" may be set to somewhere in the range of 600 to 800 bytes, for example.

[0014] FIG. 1 illustrates an exemplary mobile station 100. Mobile station 100 is compatible with one or more WLAN standards, for example, IEEE 802.11 standards, ETSI HiperLAN standards, or future related standards.

[0015] A non-exhaustive list of examples for mobile station 100 includes a wireless- enabled laptop computer, a wireless-enabled tablet computer, a wireless-enabled cellphone, a wireless-enabled personal digital assistant (PDA), a wireless-enabled smart phone, a wireless- enabled video camera/monitor, a wireless-enabled gaming/multimedia console, a wireless- enabled sensor/reporting/storage device, a wireless Internet Protocol (IP) phone and any other suitable WLAN client device.

[0016] Mobile station 100 comprises a processor 102 and a memory 104 coupled to processor 102. A non-exhaustive list of examples for processor 102 includes a central processing unit (CPU), a digital signal processor (DSP), a reduced instruction set computer (RISC), a complex instruction set computer (CISC) and the like. Furthermore, processor 102 may be part of an application specific integrated circuit (ASIC) or may be a part of an application specific standard product (ASSP).

[0017] A non-exhaustive list of examples for memory 104 includes any combination of the following: a) semiconductor devices such as registers, latches, read only memory (ROM), mask ROM, electrically erasable programmable read only memory devices (EEPROM), flash memory devices, non-volatile random access memory devices (NVRAM), synchronous dynamic random access memory (SDRAM) devices, RAMBUS dynamic random access memory (RDRAM) devices, double data rate (DDR) memory devices, static random access memory (SRAM), universal serial bus (USB) removable memory, and the like; b) optical devices, such as compact disk read only memory (CD ROM), and the like; and c) magnetic devices, such as a hard disk, a floppy disk, a magnetic tape, and the like.

[0018] Mobile station 100 may comprise an audio input element 106, for example a microphone, and an audio output element 108, for example, a speaker, coupled to processor

RIM071-03PC

102. Mobile station 100 may comprise a video input element 110, for example, a video camera, and a video output element 112, for example an analog or a digital screen, coupled to processor 102. Alternatively, mobile station 100 may be connectable to external audio input elements, external audio output elements, external video input elements and external video output elements.

[0019] Mobile station 110 comprises a WLAN MAC layer module 114 and a WLAN physical layer (PHY) module 116. For example, MAC module 114 may be compatible with IEEE 802.11 and PHY module 116 may be compatible with IEEE 802.2.

[0020] The functional architecture of mobile station 100 as shown in FIG. 1 is merely an example, and embodiments of the invention are applicable to communication devices having any other functional architecture. Mobile station 100 includes other components that, for clarity, are not shown in FIG. 1.

[0021] One or more applications 122 generate best effort data and/or background data. A non-exhaustive list of examples of applications 122 includes web browsers, email clients and file transfer protocol (FTP) clients. Best effort traffic includes email synchronization, file downloads and web browsing.

[0022] One or more streaming applications 124 generate or receive streaming data, including voice and video. A non-exhaustive list of examples of applications 124 includes Internet Protocol television (IPTV), telephone calls using Real-Time Transport Protocol (RTP), video conferencing, and the like. For example, streaming applications 124 may control an audio coder-decoder (codec) 126 to generate a compressed audio stream from audio received from audio input element 106, or may control a video codec 126 to generate a compressed video stream from video received from video input element 110. Memory 104 may store one or more compressed video and/or audio files 130 accessible by streaming applications 124 as input.

[0023] A non-exhaustive list of examples for audio codec 126 includes G711, G722, G723, G.726, G.728, G.729, MP3, Windows® Media Audio (WMA), Vector Sum Excited Linear Prediction (VSELP), Digital Speech Standard (DSS), and any other suitable audio codec.

RIM071-03PC

[0024] A non-exhaustive list of examples for video codec 128 includes H.261, H.263, H.264, flavors of Moving Picture Experts Group (MPEG), RealVideo®, Windows® Media Video, DivX®, Pixlet®, and any other suitable video codec.

[0025] A stream control application 132 is coupled to streaming applications 124 to handle stream set up, call control, codec negotiation and the like. For example, stream control application 132 may implement Session Initiation Protocol (SIP) and/or Session Announcement Protocol (SAP) and/or Real Time Streaming Protocol (RTSP).

[0026] Packets 134 and 136 generated by applications 122 and 124, respectively, are provided to WLAN MAC module 114. The applications set the priorities of the packets. For example, the packets may include user priority (UP) bits of IEEE 802. Id, which allow for eight different user priority levels.

[0027] A component 138 in WLAN MAC module 208 may classify the packets, fragment any packets that are larger than a fragmentation threshold into fragments, and encapsulate the fragments with a header and/or footer. An encapsulated fragment is also known a packet. If a packet is fragmented, then the header of the encapsulated fragment includes information as to the order of the fragments to allow for reassembly at the receiver. For example, component 138 may classify the packets using four IEEE 802.1 Ie access categories (AC) that are derived from the IEEE 802. Id user priorities, as follows:

[0028] Based on their classification, the packets are directed to one of several memory queues partitioned based on priority. For example, memory four queues are shown in FIG. 1 : a voice queue 140 for packets classified with AC VO, a video queue 142 for packets classified with AC VI, a best effort queue 144 for packets classified with AC BE, and a background queue 146 for packets classified with AC_BK.

RIM071-03PC

[0029] A packet scheduler 148 schedules packets from the memory queues to be passed to WLAN PHY module 116. For example, IEEE 802.1 Ie has separate minimum and maximum values for each access category. Within each access category, a random number is generated that represents a wait time as multiplied by a "slot time". In IEEE 802.1 la/g, a slot time is 9 microseconds. Once the wireless medium is quiet or unoccupied, a countdown begins before transmission. Each count is 9 microseconds in real time. For voice queue 140, the countdown begins at a value between 31 and 127. For video queue 142, the countdown begins at a value between 127 and 255. For best effort queue 144, the countdown begins at a value between 255 and 511. For background queue 146, the countdown begins at a value between 511 and 1023. If the countdown is interrupted, it is paused until the wireless medium is once again quiet, and is then resumed from the value at which it was paused. If the countdowns for different queues begin at the same time, traffic in a higher priority queue will gain access to the wireless medium ahead of traffic in a lower priority queue.

[0030] WLAN PHY module 116 comprises a radio 150 and a transmitter 152. Radio 150 encrypts, interleaves and modulates the packets received from packet scheduler 148. Transmitter 152 is a radio frequency (RF) chain that represents everything after the digital-to- analog converter to the antenna. This chain comprises, for example, an analog-to-digital converter, a filter, a mixer/frequency converter, a bandpass filter, a transmit/receive switch, a power amplifier, additional filters, antenna matching circuits, an antenna switch and an antenna.

[0031] A stream control monitor 154 is coupled to stream control application 132 and to WLAN MAC module 114.

[0032] Reference is made additionally to FIGS. 2 and 3, which are flowcharts of an exemplary method for controlling transmission of traffic from a mobile station over a wireless medium. The methods of FIGS. 2 and 3 may be implemented in stream control monitor 154, which monitors stream control application 132.

[0033] The method of FIG. 2 is invoked when stream control monitor 154 detects the setup of a new media stream session, for example, a new audio stream session or a new video stream session, at 202. For example, there is an admission control protocol defined for IEEE 802.1 Ie, which allows the mobile station's control monitor to detect high priority traffic flows.

RIM071-03PC

8

At the start of a flow, the mobile station will send an admission control request to the access point to request a high priority traffic flow. In another example, stream control monitor 154 could snoop the stream or call signaling messages. In yet another example, stream control monitor 154 could act as a proxy for call control.

[0034] Stream control monitor 154 detects the priority of the new media stream session. The classification may be done, for example, based on IEEE 802. Id user priorities in layer 2, IP Type of Service (ToS) information at layer 3, or IP Differentiated Services Code Point (DSCP) information at layer 3. The IP address and IP port number in the packet headers may also be used to detect the priority of the new media stream session.

[0035] At 204, stream control monitor 154 may detect the type of the new media stream. The type may be inferred from the priority. For example, the highest priority may correspond to audio streams. However, different streams of the same priority may be of different types. For example, video streams of MPEG type A, MPEG type B, MPEG4 broadcast, and MPEG7 conferencing may all have the same priority.

[0036] At 206, stream control monitor 156 may detect the packet size (or maximum packet size) of the new media stream. This detection may occur along with the detection of the setup of the media stream session. For example, according to IEEE 802.1 Ie, the packet size of a high priority traffic flow is transmitted as part of the admission control request from the mobile station to the access point in what is known as a traffic specification (TSPEC). In another example, snooping the stream or call control messages may yield the packet size (or maximum packet size).

[0037] At 208, stream control monitor 156 checks whether the new media stream session is of higher priority than any other media stream sessions currently set up in the mobile station. If not, then the method ends. If the new media stream session is of higher priority than any other media stream sessions currently set up in the mobile station, then at 210, stream control monitor 156 provides a fragmentation threshold corresponding to the priority of the new media stream session to component 138 of WLAN MAC module 114. Component 138 then fragments packets received by WLAN MAC module 114 into packets no larger than the fragmentation size it has been provided by stream control monitor 156.

RIM071-03PC

[0038] A lower bound on the fragmentation threshold provided by stream control monitor 156 to component 138 is that the fragmentation threshold equals or is larger than the expected size of any packet of the new media stream. If the fragmentation threshold is smaller than the expected size of packets of the new media stream, then the packets of the new media stream will be fragmented by component 138, which is undesirable. Therefore, the fragmentation threshold may be set to slightly larger than the largest expected packet size for the new media stream, for example, 10 bytes or 20 bytes larger.

[0039] An upper bound on the fragmentation threshold provided by stream control monitor 156 to component 138 is that the fragmentation threshold is sufficiently small to reduce latency caused to traffic of the priority of the new media stream session by lower priority traffic. If the fragmentation threshold is too large, large packets of lower priority traffic may occupy the wireless medium for a duration that adversely affects the transmission of traffic of the priority of the new media stream session.

[0040] In one implementation, fragmentation thresholds corresponding to different types of media streams may be defined. At 210, stream control monitor 156 may provide the fragmentation threshold corresponding to the type of the new media stream to component 138 of WLAN MAC module 114. For example, since voice packets are typically around 108 bytes in size, the fragmentation threshold corresponding to voice media streams may be defined as 256 bytes. In another example, since MPEG type A and MPEG4 broadcast packets are typically around 647 bytes in size, the fragmentation threshold corresponding to video media streams of those types may be defined as 754 bytes. In yet another example, since MPEG type B and MPEG7 conferencing packets are typically around 245 bytes or 446 bytes in size, the fragmentation threshold corresponding to video media streams of those types may be defined as 512 bytes.

[0041] In another example, fragmentation thresholds corresponding to different priorities may be defined, ignoring the possibility that streams of the same priority may be of different types. At 210, stream control monitor 156 may provide the fragmentation threshold corresponding to the priority of the new media stream to component 138 of WLAN MAC module 114. For example, the fragmentation threshold for packets having IEEE 802. Id user priorities 111 and 110 may be defined as 256 bytes, and the fragmentation threshold for packets having IEEE 802. Id user priorities 101 and 100 may be defined as 754 bytes.

RIM071-03PC

10

[0042] The method of FIG. 3 is invoked when stream control monitor 154 detects the end of a particular media stream session, at 302. For example, if the TSPEC expires without a renewal or is explicitly terminated by the access point, this is an indication that the media stream session has ended. In another example, if the ToS bit in the header of the IP packet for that priority is absent for a certain time out period, for example, 3 seconds, this is also an indication that the media stream session has ended. At 304, stream control monitor 154 checks whether other media stream sessions are currently set up. If not, then at 306, stream control monitor 154 provides a fragmentation threshold corresponding to the absence of high priority traffic to component 138. Since fragmentation introduces overhead, about 48 bytes of overhead in IEEE 802.1 Ie systems, it decreases the perceivable throughput. Therefore, the fragmentation threshold corresponding to the absence of high priority traffic may be a value that promotes efficient transmission, such as a value that is very large in comparison to the packet size of high priority traffic. For example, the value may be larger than 1500 bytes, or larger than 2048 bytes, or even as large as 7000 bytes, as proposed for IEEE 802.1 In HD RIFS traffic.

[0043] If other media stream sessions are currently set up, then stream control monitor 154 checks at 308 whether the particular media stream session which has just ended was of higher priority than any other media stream sessions currently set up. If not, then the method ends. Otherwise, at 310, stream control monitor 154 provides to component 138 a fragmentation threshold corresponding to the priority of the other media stream session that has the highest priority.

[0044] Consider the following scenario:

1. A video stream session of MPEG7 conferencing packets is set up, so the fragmentation threshold is set to 512 bytes, for example. Packets of lower priority traffic which are larger than 512 bytes are fragmented into packets that are no larger than 512 bytes.

2. While the MPEG7 video stream session is still set up, a voice stream session is set up for a telephone call. The fragmentation threshold is therefore set to 256 bytes, for example. Packets of lower priority traffic which are larger than 256 bytes - including

RIM071-03PC

11 the packets of the MPEG7 video stream - are fragmented into packets that are no larger than 256 bytes.

3. While the telephone call is in progress, the MPEG7 video stream session ends. No change is made to the fragmentation threshold, because the telephone call is still the media stream session of highest priority.

4. While the telephone call is still in progress, a video stream session of MPEG4 broadcast packets is set up. No change is made to the fragmentation threshold, because the telephone call is still the media stream session of highest priority.

5. The telephone call ends. Since the MPEG4 video stream session is still set up, the fragmentation threshold is set to 754 bytes, for example.

6. The MPEG4 video stream session ends, and the fragmentation threshold is set to 2048 bytes, for example.

[00451 FlG. 4 is a flowchart of another exemplary method for controlling transmission of traffic from a mobile station over a wireless medium, corresponding to the fragmentation thresholds described in the previous scenario. It is obvious to a person of ordinary skill in the art how to modify the method of FIG. 4 to correspond to other scenarios.

[0046] Stream control monitor 154 continually monitors stream control application 132. If an audio stream session is set up, as checked at 402, then the fragmentation threshold is set (or maintained) at 256 bytes, as indicated at 404. If no audio stream session is set up, but a video stream session is set up, as checked at 406, then the fragmentation threshold is set (or maintained) at 512 bytes or 754 bytes, as indicated at 408, depending on the type of the video stream. If neither an audio stream session nor a video stream session is set up, then at 410, the fragmentation threshold is set (or maintained) at a value corresponding to the absence of any high priority traffic.

[00471 Reference is now made to FIGs. 5-1 and 5-2, which are exemplary timing diagrams that illustrate high priority traffic and low priority traffic sharing a wireless medium. In FIG. 5-1, the mobile stations do not implement dynamic fragmentation sizes, whereas in FIG. 5-2, the mobile stations do implement dynamic fragmentation sizes. The examples shown in FIGs. 5-1 and 5-2 are for IEEE 802.1 lb/g communications.

RIM071-03PC

12

[0048] High priority voice traffic produces packets 504 of 108 bytes. Each such packet, when transmitted at a data rate of 1 Mbps, occupies the wireless medium for approximately 870 microseconds. A typical voice application may generate packets to be transmitted at an interval of 20 milliseconds. Low priority traffic may produce, for example, a packet 506 of 1546 bytes which, when transmitted at a data rate of 1 Mbps, occupies the wireless medium for approximately 18.9 milliseconds. Since a mobile station may wait 0.2 milliseconds once the wireless medium is quiet or unoccupied before transmitting, the low priority traffic causes a delay of up to 19.1 milliseconds in the transmission of the voice traffic. The voice traffic must wait until packet 506 has been transmitted before gaining access to the medium. This may significantly affect the quality of service for the voice traffic.

[0049] If, however, the packet of low priority traffic is fragmented into packets 510 of no more than 256 bytes, then each such packet 510, when transmitted at a. data rate of 1 Mbps, will occupy the wireless medium for approximately 2.2 milliseconds. Since a mobile station may wait 0.2 milliseconds once the wireless medium is quiet or unoccupied before transmitting, the low priority traffic causes a delay of up to 2.4 milliseconds in the transmission of the voice traffic. High priority voice traffic is transmitted in between fragments of the low priority traffic.

[0050] Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.