<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xml:lang="en" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Sensors</journal-id>
<journal-title>Sensors</journal-title>
<issn pub-type="epub">1424-8220</issn>
<publisher>
<publisher-name>Molecular Diversity Preservation International (MDPI)</publisher-name></publisher></journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3390/s111009700</article-id>
<article-id pub-id-type="publisher-id">sensors-11-09700</article-id>
<article-categories>
<subj-group>
<subject>Article</subject></subj-group></article-categories>
<title-group>
<article-title>Coexistence of WiFi and WiMAX Systems Based on PS-Request Protocols<xref ref-type="fn" rid="fn1-sensors-11-09700"><sup>†</sup></xref></article-title></title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>Kim</surname><given-names>Jongwoo</given-names></name><xref ref-type="aff" rid="af1-sensors-11-09700"><sup>1</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Park</surname><given-names>Suwon</given-names></name><xref ref-type="aff" rid="af1-sensors-11-09700"><sup>1</sup></xref><xref ref-type="corresp" rid="c1-sensors-11-09700">*</xref></contrib>
<contrib contrib-type="author">
<name><surname>Rhee</surname><given-names>Seung Hyong</given-names></name><xref ref-type="aff" rid="af2-sensors-11-09700"><sup>2</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Choi</surname><given-names>Yong-Hoon</given-names></name><xref ref-type="aff" rid="af3-sensors-11-09700"><sup>3</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Chung</surname><given-names>Young-uk</given-names></name><xref ref-type="aff" rid="af4-sensors-11-09700"><sup>4</sup></xref></contrib>
<contrib contrib-type="author">
<name><surname>Hwang</surname><given-names>Ho Young</given-names></name><xref ref-type="aff" rid="af5-sensors-11-09700"><sup>5</sup></xref></contrib></contrib-group>
<aff id="af1-sensors-11-09700">
<label>1</label> Department of Electronics and Communications Engineering, Kwangwoon University, Seoul 139-701, Korea; E-Mail: <email>jongwoo_kim@kw.ac.kr</email></aff>
<aff id="af2-sensors-11-09700">
<label>2</label> Department of Electronics Convergence Engineering, Kwangwoon University, Seoul 139-701, Korea; E-Mail: <email>rhee@kw.ac.kr</email></aff>
<aff id="af3-sensors-11-09700">
<label>3</label> Department of Information Control Engineering, Kwangwoon University, Seoul 139-701, Korea; E-Mail: <email>yhchoi@kw.ac.kr</email></aff>
<aff id="af4-sensors-11-09700">
<label>4</label> Department of Electronic Engineering, Kwangwoon University, Seoul 139-701, Korea; E-Mail: <email>yuchung@kw.ac.kr</email></aff>
<aff id="af5-sensors-11-09700">
<label>5</label> Department of Computer Engineering, Kwangwoon University, Seoul 139-701, Korea; E-Mail: <email>hyhwang@kw.ac.kr</email></aff>
<author-notes>
<corresp id="c1-sensors-11-09700">
<label>*</label>Author to whom correspondence should be addressed; E-Mails: <email>spark@kw.ac.kr</email> or <email>spark@ieee.org</email>; Tel.: +82-2-940-5139; Fax: +82-2-909-5441.</corresp><fn id="fn1-sensors-11-09700">
<label>†</label>
<p>This work was presented in part at <italic>Future Generation Information Technology (FGIT) 2010</italic>, Jeju Island, Korea, 13–15 December 2010.</p></fn></author-notes>
<pub-date pub-type="collection">
<year>2011</year></pub-date>
<pub-date pub-type="epub">
<day>13</day>
<month>10</month>
<year>2011</year></pub-date>
<volume>11</volume>
<issue>10</issue>
<fpage>9700</fpage>
<lpage>9716</lpage>
<history>
<date date-type="received">
<day>28</day>
<month>8</month>
<year>2011</year></date>
<date date-type="rev-recd">
<day>28</day>
<month>9</month>
<year>2011</year></date>
<date date-type="accepted">
<day>9</day>
<month>10</month>
<year>2011</year></date></history>
<permissions>
<copyright-statement>© 2011 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement>
<copyright-year>2011</copyright-year>
<license>
<p>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (http://creativecommons.org/licenses/by/3.0/).</p></license></permissions>
<abstract>
<p>We introduce both the coexistence zone within the WiMAX frame structure and a PS-Request protocol for the coexistence of WiFi and WiMAX systems sharing a frequency band. Because we know that the PS-Request protocol has drawbacks, we propose a revised PS-Request protocol to improve the performance. Two PS-Request protocols are based on the time division operation (TDO) of WiFi system and WiMAX system to avoid the mutual interference, and use the vestigial power management (PwrMgt) bit within the Frame Control field of the frames transmitted by a WiFi AP. The performance of the revised PS-Request protocol is evaluated by computer simulation, and compared to those of the cases without a coexistence protocol and to the original PS-Request protocol.</p></abstract>
<kwd-group>
<kwd>coexistence</kwd>
<kwd>mutual interference</kwd>
<kwd>power saving mode</kwd>
<kwd>PS-Request</kwd>
<kwd>duration field</kwd></kwd-group></article-meta></front>
<body>
<sec sec-type="intro">
<label>1.</label>
<title>Introduction</title>
<p>Many wireless communication systems have been developed and deployed to support various kinds of wireless data services. Many of the developed frequency bands are becoming more congested, especially in the densely populated urban areas due to the scarcity of commercially usable frequency resources and the explosive increasing desire for wireless data service. Consequently, it is essential that several heterogeneous wireless communication systems share a frequency band if possible, such as the 2.4 GHz ISM (Industrial, Scientific, and Medical) band. The spectrum sharing of several heterogeneous systems is termed coexistence. Coexistence can improve the utilization of the frequency band, because all the participating systems are not fully using their frequency band. However, the coexistence of heterogeneous wireless communication systems sharing a spectrum simultaneously and in the same geographic region causes their mutual interference, the coexistence problem. This degrades the performance of each wireless communication system. Sharing in the unlicensed bands, including 2.4 GHz ISM band, has been studied for a long time. Well known wireless communication systems in the ISM band are WiFi for wireless local area network (WLAN) systems, Bluetooth or ZigBee for wireless personal area networks (WPANs), and the like.</p>
<p>There has been growing demand for broadband connections, along with the proliferation of wireless data services. WiMAX (Worldwide Interoperability for Microwave Access) for wireless metropolitan area network (WMAN) systems is an attractive technology to address this need. WiMAX is being considered as a candidate system operated in the ISM band, because it can provide low price or free high speed wireless internet service. If the WiMAX system is newly deployed in the ISM band, like a kind of home base station, it inevitably generates interference with the other wireless communication systems that exist in the ISM band. WiFi is a popular wireless communication system operated in that band, and deployed in many indoor or outdoor places. Therefore, the coexistence of WiFi and WiMAX systems sharing a frequency band should be studied, when they operate in an adjacent or the same area, as shown in <xref ref-type="fig" rid="f1-sensors-11-09700">Figure 1</xref>.</p>
<p><xref ref-type="table" rid="t1-sensors-11-09700">Table 1</xref> defines the four types of coexistence of heterogeneous wireless communication systems. In this paper, we focus on the case in which WiFi system based on IEEE 802.11g and WiMAX system based on IEEE 802.16e are collaborative. We want to make them coexist, based on their minimum collaboration and the minimum change of their specifications.</p>
<p>In Section 2, we explain related work on coexistence. In Section 3, we introduce the time division operation of WiFi and WiMAX systems to avoid their mutual interference. In Sections 4 and 5, we introduce the previously proposed PS-Request protocol of the WiFi system and coexistence zone within the WiMAX frame structure. In Section 6, we propose a revised PS-Request protocol to resolve drawbacks of the original PS-Request protocol. In Section 7, we evaluate by simulation the performance of the revised PS-Request protocol. Finally, we will conclude in Section 8.</p></sec>
<sec>
<label>2.</label>
<title>Related Work</title>
<p>Many studies have been conducted on the coexistence of heterogeneous wireless communication systems. The coexistence of WiFi and Bluetooth systems was dealt in [<xref ref-type="bibr" rid="b1-sensors-11-09700">1</xref>–<xref ref-type="bibr" rid="b3-sensors-11-09700">3</xref>], that of WiFi and ZigBee systems was discussed in [<xref ref-type="bibr" rid="b4-sensors-11-09700">4</xref>,<xref ref-type="bibr" rid="b5-sensors-11-09700">5</xref>]. Chiasserini [<xref ref-type="bibr" rid="b1-sensors-11-09700">1</xref>] proposed two solutions for the coexistence of WiFi and Bluetooth systems. One involves WiFi STAs estimating the interference pattern, and transmitting a frame of the minimum payload size, 500 bytes, comparable to the duration of a single slot Bluetooth packet. This may reduce the probability of collisions between the two systems. However, it is hard to estimate the interference pattern. The second deals with frequency hopping, a suggested packet length and restricts the length of packets. Thus, the allowable data rate decreased. Golmie [<xref ref-type="bibr" rid="b2-sensors-11-09700">2</xref>] introduced a backoff strategy and adaptive frequency hopping (AFH). This also reduced the collision probability of the two systems. The backoff strategy does not require changes to the Bluetooth specification. However, changing the frequency hopping pattern requires some changes to the Bluetooth specification. The benefits of AFH may not be as obvious for delay jitter and packet loss constrained applications, such as voice or video services. Hsu [<xref ref-type="bibr" rid="b3-sensors-11-09700">3</xref>] studied a dynamic WiFi system fragmentation technique. A WiFi station (STA) divides one frame into several fragments, and sends them. The WiFi STA should be acknowledged fragment by fragment. If the transmission of a specific fragment fails, the WiFi STA only retransmits the failed fragment. This decreases the allowable data rate, because it reduces the length of the collided fragment. Sikora [<xref ref-type="bibr" rid="b4-sensors-11-09700">4</xref>] evaluated the effects of the mutual interference, and quantity coexistence issues. Wei [<xref ref-type="bibr" rid="b5-sensors-11-09700">5</xref>] introduced several coexistence models between ZigBee and WiFi systems, and evaluated their interference effects.</p>
<p>References [<xref ref-type="bibr" rid="b6-sensors-11-09700">6</xref>–<xref ref-type="bibr" rid="b11-sensors-11-09700">11</xref>] deal with the coexistence of WiFi and WiMAX systems. Dongeun Kim [<xref ref-type="bibr" rid="b6-sensors-11-09700">6</xref>] proposed a solution based on a circulator to reduce the mutual interference between them. It showed a width of the overlapped frequency band to tolerate the mutual interference. Even though both systems can endure a certain amount of mutual interference, it does not avoid but rather mitigates the mutual interference. Berlemann [<xref ref-type="bibr" rid="b7-sensors-11-09700">7</xref>,<xref ref-type="bibr" rid="b8-sensors-11-09700">8</xref>] and Siddique [<xref ref-type="bibr" rid="b9-sensors-11-09700">9</xref>] proposed solutions based on time division multiplexing (TDM) of WiMAX systems based on IEEE802.16 and WiFi systems based on IEEE802.11a/e. They improved spectral efficiency. However, no protocol controls the transmission of WiFi STAs. Even if a certain period is allocated to the WiFi system, a WiFi STA may send frames beyond the period. This can cause the mutual interference. Jing [<xref ref-type="bibr" rid="b10-sensors-11-09700">10</xref>] studied the coexistence between WiMAX systems based on IEEE802.16a and WiFi systems based on IEEE802.11b. A WiFi access pointer (AP) senses WiFi channels and selects a channel with the minimum received signal strength indicator (RSSI). The WiFi AP broadcasts the selected WiFi channel, and all of WiFi STAs move to it. However, if an interferer is not located within the range of a WiFi AP, the WiFi AP cannot recognize it. Jing [<xref ref-type="bibr" rid="b11-sensors-11-09700">11</xref>] also introduced a cognitive radio (CR) method. Each node announces information, such as frequency, power, modulation, duration, interference margin, and service type, through the common spectrum coordination channel. The method can reduce the influence of the mutual interference, but it needs much overhead. Two mechanisms termed Listen-Before-Talk (LBT) and Extended Quiet Period (EQP) are adopted to perform white space detection efficiently based on IEEE 802.16h [<xref ref-type="bibr" rid="b12-sensors-11-09700">12</xref>]. A WiMAX BS should listen to a channel all the time to know whether the channel is occupied, and adopt LBT to determine if an EQP is needed after the end of a quiet period. If the channel is unoccupied, the WiMAX BS and WiMAX MSs transmit frames during an active period. The WiMAX BS and WiMAX MSs do not transmit during a quiet period. This information about the quiet period is included in the DL-MAP. It is extended if the channel is still occupied after the quiet period. Thus, it is termed Extended Quiet Period (EQP) in which there is no transmission. John [<xref ref-type="bibr" rid="b13-sensors-11-09700">13</xref>] evaluated the performance of LBT and EQP protocols.</p></sec>
<sec>
<label>3.</label>
<title>Time Division Operation of WiFi and WiMAX Systems</title>
<p>We exploit the time division operation (TDO) to avoid or reduce the mutual interference between WiFi and WiMAX systems, as shown in <xref ref-type="fig" rid="f2-sensors-11-09700">Figure 2</xref>. The mutual interference can be avoided, since the TDO means that only one of two systems transmits, and the other system pauses its transmission [<xref ref-type="bibr" rid="b14-sensors-11-09700">14</xref>,<xref ref-type="bibr" rid="b15-sensors-11-09700">15</xref>]. Master devices of the systems, such as a WiFi AP and a WiMAX base station (BS), should control the signal transmission of its terminals, such as WiFi STAs and WiMAX mobile stations (MSs), respectively, to achieve the TDO, as shown in <xref ref-type="fig" rid="f2-sensors-11-09700">Figure 2</xref>. A little information exchange between WiFi and WiMAX systems is needed for timing synchronization of the transmission periods of two systems.</p>
<p>In this paper, we only focus on the coexistence of collaborative WiFi and WiMAX systems. Thus, we assume the minimum collaboration between a WiMAX BS and a WiFi AP for timing synchronization of the transmission period of each system is acquired. Information exchange among the WiMAX BS and WiFi STAs, among WiMAX MSs and the WiFi AP, and among WiMAX MSs and WiFi STAs, is unnecessary. However, the WiMAX BS and the WiFi AP should independently provide information about the transmission period to their terminals. If the WiMAX BS and the WiFi AP are in one device, as shown in <xref ref-type="fig" rid="f1-sensors-11-09700">Figure 1(b)</xref>, the collaboration can be easily implemented.</p>
<p>A WiMAX BS based on IEEE802.16e specification can control the signal transmission of all of its WiMAX MSs through the DL-MAP (Downlink map) and UL-MAP (Uplink map). However, a WiFi AP based on IEEE802.11g cannot control the signal transmission of all its WiFi STAs. Thus, the desired structure of the TDO, as shown in <xref ref-type="fig" rid="f2-sensors-11-09700">Figure 2</xref>, cannot be achieved at the WiFi STAs, even though the WiFi AP can be operated based on the TDO structure due to the minimum information exchanged with the WiMAX BS. We propose a PS-Request protocol, the so called original PS-Request protocol, which makes the WiFi AP control the signal transmission of all of its WiFi STAs, to solve the problem.</p></sec>
<sec>
<label>4.</label>
<title>Original PS-Request Protocol</title>
<p><xref ref-type="fig" rid="f3-sensors-11-09700">Figure 3</xref> shows the format of a general medium access control (MAC) frame of the WiFi system based on the IEEE802.11g specification. It comprises a set of fields that occur in a fixed order in all frames, as shown in <xref ref-type="fig" rid="f3-sensors-11-09700">Figure 3</xref>. The conventional WiFi system has three frame types: control, data, and management. Each of the frame types has several defined subtypes. The control frame consists of sixteen subtypes. Eight subtypes are being used, and eight subtypes are reserved. Detailed explanations of the types and subtypes are given in the IEEE802.11g specification [<xref ref-type="bibr" rid="b16-sensors-11-09700">16</xref>].</p>
<p>The original PS-Request protocol is based on the use of the vestigial power management (PwrMgt) bit within the frames transmitted by a WiFi AP. In the case of an infrastructure configuration, the conventional WiFi system based on IEEE 802.11g specification can only support the power management mode for WiFi STAs. A WiFi STA can be in one of the two power management modes: an active mode (AM) or a power-saving mode (PSM). A WiFi STA in the AM is fully activated. It can send or receive frames at any time. A WiFi STA in the PSM can be in one of two states: a sleep state or an awake state. The WiFi STA in the PSM is usually in the sleep state, and periodically moves to the awake state to receive frames from a WiFi AP, such as beacon frames. The WiFi STA consumes much smaller energy than it does in the AM, because the WiFi STA in the PSM does not send any frames.</p>
<p>In the legacy WiFi system of an infrastructure configuration, a WiFi STA that wishes to move into the PSM shall inform its WiFi AP of an indication by setting the PwrMgt bit within the Frame Control field of the frame including the indication to ‘1’. The WiFi STA should be acknowledged by its WiFi AP, and move into the PSM. However, a WiFi AP cannot be in the PSM, because none of its WiFi STA can communicate for the PSM duration of the WiFi AP. Therefore, the PwrMgt bit within the Frame Control field of all frames transmitted by the WiFi AP is always set to ‘0’. This indicates that the WiFi AP is always in the AM.</p>
<p>If all WiFi STAs within the coverage of a WiFi AP are in the PSM, they do not transmit any signals. Thus, they do not generate interference to other systems during the PSM period. That is, if a WiFi system, including a WiFi AP and all of its WiFi STAs, do not transmit a signal during a specified period, the other wireless communication systems, such as a WiMAX system, can communicate without interference during the period. However, this can be achieved, only if the WiFi AP and all of its WiFi STAs move into the PSM. As mentioned before, the PSM of the conventional WiFi system can be controlled only by the WiFi STAs. That is, the WiFi AP cannot control the signal transmission of its WiFi STAs.</p>
<p>We previously proposed to use the vestigial PwrMgt bit within the Frame Control field of frames transmitted by a WiFi AP for the WiFi AP to control the signal transmission of all of its WiFi STAs. We named it the PS-Request protocol. The PS-Request frame transmitted by the WiFi AP commands all its WiFi STAs to move into the PSM to stop them transmitting a signal. <xref ref-type="fig" rid="f4-sensors-11-09700">Figure 4</xref> shows a format of the proposed PS-Request frame. One of the eight reserved subtypes, such as 0000, can be allocated, and the PwrMgt bit is set to ‘1’ in the Frame Control field. The Duration/ID field represents the value of a network allocation vector (NAV). This means that the WiFi AP will not transmit a signal during the PSM period of the NAV, and the WiFi AP stops its WiFi STAs from transmitting a signal during the period. <xref ref-type="fig" rid="f5-sensors-11-09700">Figure 5</xref> shows an example of the original PS-Request protocol. There are three cases after the start time of WiFi Tx ON period equal to the end time of WiMAX Tx ON period, as shown in <xref ref-type="fig" rid="f5-sensors-11-09700">Figure 5</xref>.</p>
<sec>
<title/>
<sec>
<title>Case (a):</title>
<p>A WiFi AP collaborating with a WiMAX BS senses a wireless medium during a distributed inter-frame space (DIFS) time. If the medium is idle, the WiFi AP begins the backoff procedure. When its backoff timer expires, the WiFi AP sends the proposed PS-Request frame. From then on, the PSM of all of WiFi STAs starts.</p></sec>
<sec>
<title>Case (b):</title>
<p>Before the transmission of the original PS-Request frame, a WiFi STA receiving a packet sends its data frame after the CSMA (Carrier Sense Multiple Access)/CA (Collision Avoidance) procedure of the WiFi system, and receives an ACK frame from its WiFi AP. Then, the WiFi AP sends the proposed PS-Request frame, as in Case (a). Then, the PSM of all WiFi STAs starts.</p></sec>
<sec>
<title>Case (c):</title>
<p>Before the transmission of the original PS-Request frame, a WiFi AP receiving a packet sends its data frame after the CSMA/CA procedure of the WiFi system, and receives an ACK frame from a corresponding WiFi STA. Then, a WiFi STA receiving a packet sends its data frame after the CSMA/CA procedure of the WiFi system, and receives an ACK frame from its WiFi AP, as in Case (b). Then, the WiFi AP sends the proposed PS-Request frame, as in Case (a). Then, the PSM of all WiFi STAs starts. All WiFi STAs are in the PSM without sending an ACK frame to its WiFi AP, because the PS-Request frame is broadcast. The value of the Destination Address field within the frames transmitted by the WiFi AP determines if it is unicast or broadcast.</p></sec></sec></sec>
<sec>
<label>5.</label>
<title>Proposed Coexistence Zone within WiMAX Frame Structure</title>
<p>There are already several zones in the WiMAX system, as shown in <xref ref-type="fig" rid="f6-sensors-11-09700">Figure 6(a)</xref>. The IEEE802.16e specification provides detailed explanations of these zones [<xref ref-type="bibr" rid="b17-sensors-11-09700">17</xref>]. They may exist in the WiMAX frame structure to support some particular functions for a WiMAX system. The DL PUSC (Partial Usage of Sub-Channel) zone for FCH and DL-MAP is mandatory, and the UL PUSC is the default. We proposed a new zone, termed the coexistence zone, as shown in <xref ref-type="fig" rid="f6-sensors-11-09700">Figure 6(b)</xref>.</p>
<p><xref ref-type="fig" rid="f7-sensors-11-09700">Figure 7</xref> shows the coexistence zone within the WiMAX frame structure. During the coexistence zone, the WiMAX system does not transmit any signal, because no OFDM symbols and subcarriers should be used for communication. We temporarily call the coexistence zone the WiFi zone, for the coexistence of WiFi and WiMAX systems, because the coexistence zone is used for WiFi systems in this paper. The PSM and the AM of WiFi STAs are alternated, based on the original PS-Request frame transmitted by a WiFi AP, as shown in <xref ref-type="fig" rid="f7-sensors-11-09700">Figure 7</xref>. The WiMAX system pauses its signal transmission during the WiFi zone. Thus, either the WiFi AP or its WiFi STAs can send frames without interference from the WiMAX system according to the CSMA/CA procedure of the WiFi system. The WiFi AP sends the original PS-Request frame to all its WiFi STAs to protect the WiMAX UL and DL transmission ON time from signals from WiFi STAs.</p></sec>
<sec>
<label>6.</label>
<title>Revised PS-Request Protocol</title>
<p>We proposed the PS-Request protocol, the so called original PS-Request protocol, to avoid the mutual interference between WiFi and WiMAX systems. However, we found that the original PS-Request protocol cannot completely solve the coexistence problem of WiFi and WiMAX systems. In the original PS-Request protocol, a WiFi AP only informs its WiFi STAs of the time to the start of the next WiFi zone, which is given in the Duration/ID field of the PS-Request frame, as shown in <xref ref-type="fig" rid="f4-sensors-11-09700">Figure 4</xref>. From this time, the WiFi AP and its WiFi STAs may compete to acquire the WiFi channel based on the CSMA/CA procedure of the WiFi system.</p>
<p>As shown in <xref ref-type="fig" rid="f5-sensors-11-09700">Figure 5</xref>, the WiFi STAs receiving the original PS-Request frame from its WiFi AP cannot know the time remaining in the current WiFi zone. They only know the time to the start of the next WiFi zone. Thus, the remaining time of the current WiFi zone can be wasted. A WiFi STA that acquires a wireless medium after competition within the next WiFi zone, may send a frame beyond the next WiFi zone, as shown in <xref ref-type="fig" rid="f8-sensors-11-09700">Figure 8</xref>, because it does not know the time to the end of the next WiFi zone. In that case, the mutual interference may be inevitable. This degrades the performance of both WiMAX and WiFi systems.</p>
<p>If WiFi STAs can know the remaining time of the current WiFi zone after receiving a PS-Request frame, they can decide to send frames either at a time or at several times by segmentation. By doing so, the mutual interference, as shown in <xref ref-type="fig" rid="f8-sensors-11-09700">Figure 8</xref>, can be avoided. Thus, we propose a revised PS-Request protocol that delivers both the time to the end of the current WiFi zone and the PSM duration to the WiFi STAs, as shown in <xref ref-type="fig" rid="f9-sensors-11-09700">Figure 9</xref>. The Duration/ID field in the revised PS-Request frame represents two values of NAV. One is the time to the end of the current WiFi zone, and the other is the PSM duration. The sum is equal to the time to the start of the next WiFi zone of the original PS-Request frame. In this paper, we assume that seven bits of fifteen bits represent the time to the end of the current WiFi zone and the other eight bits represent the PSM duration. The number of bits for each part is determined according to the desired resolution and maximum value of the time.</p>
<p><xref ref-type="fig" rid="f10-sensors-11-09700">Figure 10</xref> shows an example of the revised PS-Request protocol. A WiFi AP broadcasts a revised PS-Request frame through the transmission procedure of the WiFi system. WiFi STAs receiving the frame can send their frames until the time to the end of the current WiFi zone after a competition. After that time, all WiFi STAs are in the PSM, until the start of the next WiFi zone.</p></sec>
<sec sec-type="results">
<label>7.</label>
<title>Simulation Results</title>
<sec>
<label>7.1.</label>
<title>System Assumption</title>
<p>As mentioned before, the proposed two PS-Request protocols operate based on an information exchange only between a WiFi AP and a WiMAX BS. They need the minimum collaboration between the WiFi AP and the WiMAX BS, such as the timing synchronization, to know the start and end times of the coexistence zone within the WiMAX frame structure. However, they do not need an information exchange among WiFi AP and WiMAX MSs, among WiFi STAs and WiMAX BS, and among WiFi STAs and WiMAX MSs.</p></sec>
<sec>
<label>7.2.</label>
<title>Performance Measures</title>
<p>Throughput of each system is considered as one of the performance measures to be evaluated by the simulation [<xref ref-type="bibr" rid="b18-sensors-11-09700">18</xref>].</p>
<p>
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> are the total number of successfully transmitted data bits of WiFi and WiMAX systems, respectively. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="italic">DL</mml:mi></mml:mrow>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="italic">UL</mml:mi></mml:mrow>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> are the total number of successfully transmitted WiMAX data bits through DL (Downlink) and UL (Uplink), respectively:
<disp-formula id="FD1">
<label>(1)</label>
<mml:math display="block">
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">STA</mml:mi></mml:msub></mml:mrow></mml:msubsup>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:mn>48</mml:mn>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>M</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi>i</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>C</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi>i</mml:mi></mml:msubsup></mml:mrow></mml:mrow></mml:math></disp-formula>where <italic>i</italic> is the index of a WiFi STA and <italic>N<sub>STA</sub></italic> is the number of WiFi STAs. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> is the number of transmitted OFDM symbols. Forty eight is the number of data subcarriers of 64 subcarriers for the WiFi system based on IEEE802.11g. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>M</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi>i</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>C</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi>i</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> denote the modulation order and the code rate of WiFi STA of index <italic>i</italic>, respectively:
<disp-formula id="FD2">
<label>(2)</label>
<mml:math display="block">
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="italic">DL</mml:mi></mml:mrow>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">MS</mml:mi></mml:msub></mml:mrow></mml:msubsup>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">slot</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>j</mml:mi></mml:mrow></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:mn>48</mml:mn>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>M</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi>j</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>C</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi>j</mml:mi></mml:msubsup></mml:mrow></mml:mrow></mml:math></disp-formula>
<disp-formula id="FD3">
<label>(3)</label>
<mml:math display="block">
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="italic">UL</mml:mi></mml:mrow>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:msubsup>
<mml:mo>∑</mml:mo>
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mo>=</mml:mo>
<mml:mn>1</mml:mn></mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">MS</mml:mi></mml:msub></mml:mrow></mml:msubsup>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">tile</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>j</mml:mi></mml:mrow></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:mn>12</mml:mn>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>M</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi>j</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>C</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi>j</mml:mi></mml:msubsup></mml:mrow></mml:mrow></mml:math></disp-formula>where <italic>j</italic> is the index of WiMAX MS, and <italic>N<sub>MS</sub></italic> is the number of WiMAX MS’s. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>M</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi>j</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>C</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi>j</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> denote the modulation order and the code rate for each data burst of WiMAX MS of index <italic>j</italic>, respectively. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">slot</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>j</mml:mi></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">tile</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>j</mml:mi></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula> denote the number of allocable resource units to the MS of index <italic>j</italic> for DL and UL, respectively. Forth eight and 12 denote the number of subcarriers in one slot and in one tile, respectively.</p>
<p>
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">frame</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> is the number of WiMAX frames transmitted in a simulation. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">frame</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> is the frame time of the WiMAX system, and is typically <italic>5</italic> ms:
<disp-formula id="FD4">
<label>(4)</label>
<mml:math display="block">
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">frame</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mrow>
<mml:mo>(</mml:mo>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">DL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">CZ</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">UL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow>
<mml:mo>)</mml:mo></mml:mrow>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">symbol</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">TTG</mml:mi></mml:msub>
<mml:mo>+</mml:mo>
<mml:msub>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">RTG</mml:mi></mml:msub></mml:mrow></mml:math></disp-formula>
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">DL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula>, 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">CZ</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">UL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> denote the number of WiMAX OFDM symbols allocated to the DL subframe, the coexistence zone and the UL subframe within a WiMAX frame structure, respectively. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">DL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> includes one DL OFDM symbol for preamble, two DL OFDM symbols for FCH, DL-MAP and UL-MAP, and the other DL OFDM symbols for DL-Bursts of the WiMAX system. DL-Bursts of the WiMAX system are composed of DL OFDM symbols in multiples of two, and UL-Bursts of the WiMAX system are composed of UL OFDM symbols in multiples of three. 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">symbol</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula> is one OFDM symbol duration of the WiMAX system. <italic>T<sub>TTG</sub></italic> and <italic>T<sub>RTG</sub></italic> denote the transmit/receive transition gap (TTG) and the receive/transmit transition gap (RTG) within a WiMAX frame structure, respectively.</p>
<p>For the performance evaluation of each system, the average throughputs of WiFi and WiMAX systems are defined, as follows:
<disp-formula id="FD5">
<label>(5)</label>
<mml:math display="block">
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi></mml:msub>
<mml:mo>≜</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow>
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">TxON</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">frame</mml:mi></mml:msubsup></mml:mrow></mml:mfrac>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">CZ</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">symbol</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">frame</mml:mi></mml:msubsup></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula>
<disp-formula id="FD6">
<label>(6)</label>
<mml:math display="block">
<mml:mrow>
<mml:msub>
<mml:mi>R</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi></mml:msub>
<mml:mo>≜</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow>
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">TxON</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">frame</mml:mi></mml:msubsup></mml:mrow></mml:mfrac>
<mml:mo>=</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="italic">DL</mml:mi></mml:mrow>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="italic">UL</mml:mi></mml:mrow>
<mml:mi mathvariant="italic">bit</mml:mi></mml:msubsup></mml:mrow>
<mml:mrow>
<mml:mo stretchy="false">(</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">DL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">UL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo stretchy="false">)</mml:mo>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">symbol</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>×</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">frame</mml:mi></mml:msubsup></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula></p></sec>
<sec>
<label>7.3.</label>
<title>Simulation Environment</title>
<p>In this paper, WiMAX and WiFi systems are based on IEEE802.16e and IEEE802.11g specifications, respectively. For the simplicity of simulation and the performance evaluation of an extreme case, we assume that the WiMAX system consists of one WiMAX BS and only one WiMAX MS, and all of the radio resources are allocated to the WiMAX MS. The WiFi system also comprises one WiFi AP and one WiFi STA. <xref ref-type="table" rid="t2-sensors-11-09700">Table 2</xref> specifies the simulation parameters of the WiMAX system. <xref ref-type="table" rid="t3-sensors-11-09700">Table 3</xref> gives simulation conditions. The transmission period of each system is allocated based on the number of OFDM symbols of the WiMAX system.</p>
<p>For the case of 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">DL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">CZ</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>+</mml:mo>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">UL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mn>42</mml:mn></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">symbol</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mn>115.2</mml:mn>
<mml:mo>μ</mml:mo>
<mml:mi mathvariant="normal">s</mml:mi></mml:mrow></mml:math></inline-formula>, 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">WiFi</mml:mi>
<mml:mi mathvariant="italic">TxON</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mn>1.8432</mml:mn>
<mml:mo> </mml:mo>
<mml:mtext>ms</mml:mtext>
<mml:mo>=</mml:mo>
<mml:mn>16</mml:mn>
<mml:mo>×</mml:mo>
<mml:mn>115.2</mml:mn>
<mml:mo>μ</mml:mo>
<mml:mi mathvariant="normal">s</mml:mi></mml:mrow></mml:math></inline-formula> and 
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>T</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mi mathvariant="italic">TxON</mml:mi></mml:msubsup>
<mml:mo>=</mml:mo>
<mml:mn>2.9952</mml:mn>
<mml:mo> </mml:mo>
<mml:mtext>ms</mml:mtext>
<mml:mo>=</mml:mo>
<mml:mn>26</mml:mn>
<mml:mo>×</mml:mo>
<mml:mn>115.2</mml:mn>
<mml:mo>μ</mml:mo>
<mml:mi mathvariant="normal">s</mml:mi></mml:mrow></mml:math></inline-formula>.</p></sec>
<sec sec-type="results">
<label>7.4.</label>
<title>Simulation Results</title>
<p><xref ref-type="fig" rid="f11-sensors-11-09700">Figures 11</xref> and <xref ref-type="fig" rid="f12-sensors-11-09700">12</xref> show the simulation results for the following three cases: without the proposed protocols, with the original PS-Request protocol, and with the revised PS-Request protocol. The Signal-to-Interference Ratio (SIR), denoted as <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic>. <italic>P<sub>interfree</sub></italic> is the average received signal power of the interferee system, and <italic>P<sub>interferer</sub></italic> is the average received interference power from the interferer system. The case without the proposed protocols is evaluated for the following six conditions: without interference (<italic>P<sub>interferer</sub></italic> = 0 [W], which is equivalent to <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic> = ∞ [dB]), <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic> = 12 [dB], <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic> = 9 [dB], <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic> = 6 [dB], <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic> = 3 [dB], <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic> = 0 [dB]. If a WiFi AP can transmit a revised PS-Request frame within a WiFi zone, there will be no mutual interference in the following WiMAX Tx ON period equal to the PSM duration of the WiFi system. That is, <italic>P<sub>interferee</sub></italic>/<italic>P<sub>interferer</sub></italic> = ∞ [dB].</p>
<p><xref ref-type="fig" rid="f11-sensors-11-09700">Figure 11</xref> shows the throughput of a WiMAX system <italic>vs</italic>. the received <italic>E<sub>b</sub>/N<sub>0</sub></italic> under interference from a WiFi system sharing the same frequency band. Cases with the proposed PS-Request protocols perform better than the case without the proposed protocols. The performance of the revised PS-Request protocol does not depend on the interference power received from the WiFi system but the received <italic>E<sub>b</sub>/N<sub>0</sub></italic> of the WiMAX system, differing from the original PS-Request protocol. The revised PS-Request protocol has about 50% more throughput than the original PS-Request protocol for <italic>P<sub>WiMAX</sub>/P<sub>WiFi</sub></italic> = 0 or 3 [dB] and <italic>E<sub>b</sub>/N<sub>0</sub></italic> = 12 [dB] at which the throughput for the case without the proposed protocols is zero. Protecting the transmission of WiFi STAs beyond the end of the WiFi zone, as shown in <xref ref-type="fig" rid="f10-sensors-11-09700">Figure 10</xref>, improves performance. For smaller or zero interference environments corresponding to large <italic>P<sub>WiMAX</sub>/P<sub>WiFi</sub></italic>, the proposed PS-Request protocols may have worse performance, such as smaller throughput, because the allowed transmission interval for the WiFi system cannot be used to transmit data by the WiMAX system. However, for larger interference environments, corresponding to small <italic>P<sub>WiMAX</sub>/P<sub>WiFi</sub></italic>, the proposed PS-Request protocols can have better performance, such as relatively higher throughput. For the worst case of <italic>P<sub>WiMAX</sub></italic> = <italic>P<sub>WiFi</sub></italic> corresponding to <italic>P<sub>WiMAX</sub>/P<sub>WiFi</sub></italic> = 0 [dB] at which the WiMAX throughput, the WiFi throughput and the sum of two throughputs for the case without the proposed protocols are zero, the revised PS-Request protocol has about 50% more WiMAX throughput than the original PS-Request protocol does.</p>
<p><xref ref-type="fig" rid="f12-sensors-11-09700">Figure 12</xref> shows the throughput of a WiFi system <italic>vs</italic>. the received <italic>E<sub>b</sub>/N<sub>0</sub></italic> under the interference from a WiMAX system sharing the same frequency band. The two proposed PS-Request protocols also perform better than the case without the proposed protocols. The performance of the revised PS-Request protocol outperforms the original PS-Request protocol. This also results from avoiding the overlap of the transmission time of the WiFi system and WiMAX system. The performance of the revised PS-Request protocol depends on the received <italic>E<sub>b</sub>/N<sub>0</sub></italic> of the WiFi system, rather than on the interference power received from the WiMAX system. For smaller or zero interference environments, corresponding to large <italic>P<sub>WiFi</sub>/P<sub>WiMAX</sub></italic>, the proposed PS-Request protocols have worse performance, such as smaller throughput, because the allowed transmission interval for the WiMAX system cannot be used to transmit data by the WiFi system. However, for larger interference environments, corresponding to small <italic>P<sub>WiFi</sub>/P<sub>WiMAX</sub></italic>, the proposed PS-Request protocols can have better performance, such as relatively higher throughput. For the worst case of <italic>P<sub>WiFi</sub></italic> = <italic>P<sub>WiMAX</sub></italic> corresponding to <italic>P<sub>WiFiX</sub>/P<sub>WiMAX</sub></italic> = 0 [dB] at which the WiMAX throughput, the WiFi throughput and the sum of two throughputs for the case without the proposed protocols are zero, the WiFi throughput of the revised PS-Request protocol is similar to the WiFi throughput at the interference-free condition for the case without the proposed protocols, even if that of the original PS-Request protocol is still zero.</p></sec></sec>
<sec sec-type="conclusions">
<label>8.</label>
<title>Conclusions</title>
<p>In this paper, we introduced the TDO for the coexistence of WiFi and WiMAX systems sharing a frequency band. We proposed a coexistence zone within WiMAX frame structure, and two PS-Request protocols to achieve the TDO. The two proposed PS-Request protocols are based on the vestigial power management bit within the Frame Control field transmitted by a WiFi AP. We showed using computer simulation that they outperform the case without the proposed protocols. The revised PS-Request protocol can resolve a drawback of the original PS-Request protocol. We evaluated and compared the performance for three cases: without the proposed protocols, with the original PS-Request protocol, and with the revised PS-Request protocol.</p>
<p>For smaller or zero interference environments, the proposed PS-Request protocols have worse performance, such as smaller throughput, because the transmission interval allowed to the other system cannot be used to transmit data by one system. However, for larger interference environments, the revised PS-Request protocols have the best performance of the three cases.</p>
<p>As a topic for further study, we plan to upgrade the simulator used to obtain more realistic and accurate performance measures for more combinations of simulation conditions. We also have a plan to solve the coexistence issue of WiFi and 3GPP LTE (Long Term Evolution) systems.</p></sec></body>
<back>
<ack>
<p>This work was partly supported by Mid-career Researcher Program through the National Research Foundation of Korea (NRF) grant funded by the Ministry of Education, Science and Technology (MEST) (No. 2011-0027572). And the present research was partly conducted by a Research Grant of Kwangwoon University in 2011.</p></ack>
<ref-list>
<title>References</title>
<ref id="b1-sensors-11-09700"><label>1.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Chiasserini</surname><given-names>CF</given-names></name><name><surname>Rao</surname><given-names>RR</given-names></name></person-group><article-title>Coexistence mechanisms for interference mitigation between IEEE 802.11 WLANs and bluetooth</article-title><conf-name>Proceedings of INFOCOM 2002</conf-name><conf-loc>New York, NY, USA</conf-loc><conf-date>June 2002</conf-date><fpage>590</fpage><lpage>598</lpage></citation></ref>
<ref id="b2-sensors-11-09700"><label>2.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Golmie</surname><given-names>N</given-names></name><name><surname>Chevrollier</surname><given-names>N</given-names></name><name><surname>Rebala</surname><given-names>O</given-names></name></person-group><article-title>Bluetooth and WLAN coexistence: Challenges and solutions</article-title><source>IEEE Wirel. Commun</source><year>2003</year><volume>10</volume><fpage>22</fpage><lpage>29</lpage></citation></ref>
<ref id="b3-sensors-11-09700"><label>3.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Hsu</surname><given-names>AC-C</given-names></name><name><surname>Wei</surname><given-names>DSL</given-names></name><name><surname>Kuo</surname><given-names>C-CJ</given-names></name></person-group><article-title>Coexistence mechanism using dynamic fragmentation for interference mitigation between WiFi and Bluetooth</article-title><conf-name>Proceedings of MILCOM 2006</conf-name><conf-loc>Washington, DC, USA</conf-loc><conf-date>October 2006</conf-date><fpage>1</fpage><lpage>7</lpage></citation></ref>
<ref id="b4-sensors-11-09700"><label>4.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Sikora</surname><given-names>A</given-names></name><name><surname>Groza</surname><given-names>VF</given-names></name></person-group><article-title>Coexistence of IEEE 802.15.4 with other systems in the 2.4 GHz-ISM-Band</article-title><conf-name>Proceedings of IMTC 2005</conf-name><conf-loc>Ottawa, ON, Canada</conf-loc><conf-date>May 2005</conf-date><fpage>1786</fpage><lpage>1791</lpage></citation></ref>
<ref id="b5-sensors-11-09700"><label>5.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Wei</surname><given-names>Y</given-names></name><name><surname>Xiangyu</surname><given-names>W</given-names></name><name><surname>Linnartz</surname><given-names>J-PMG</given-names></name></person-group><article-title>A coexistence model of IEEE 802.15.4 and IEEE 802.11b/g</article-title><conf-name>Proceedings of the 14th IEEE Symposium</conf-name><conf-loc>Delft, The Netherland</conf-loc><conf-date>November 2007</conf-date><fpage>1</fpage><lpage>5</lpage></citation></ref>
<ref id="b6-sensors-11-09700"><label>6.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Kim</surname><given-names>D</given-names></name><name><surname>Kim</surname><given-names>J</given-names></name><name><surname>Park</surname><given-names>S</given-names></name><name><surname>Rhee</surname><given-names>SH</given-names></name><name><surname>Kang</surname><given-names>C</given-names></name><name><surname>Han</surname><given-names>K</given-names></name><name><surname>Kang</surname><given-names>H</given-names></name></person-group><article-title>Circulator-based collocated system for coexistence of WiFi and WiMAX systems in shared bands</article-title><conf-name>Proceedings of the 1st International Conference on Ubiquitous and Future Networks</conf-name><conf-loc>Hong Kong</conf-loc><conf-date>June 2009</conf-date><fpage>214</fpage><lpage>219</lpage></citation></ref>
<ref id="b7-sensors-11-09700"><label>7.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Berlemann</surname><given-names>L</given-names></name><name><surname>Hoymann</surname><given-names>C</given-names></name><name><surname>Hiertz</surname><given-names>GR</given-names></name><name><surname>Mangold</surname><given-names>S</given-names></name></person-group><article-title>Coexistence and interworking of IEEE 802.16 and IEEE 802.11(e)</article-title><conf-name>Proceedings of Vehicular Technology Conference</conf-name><conf-loc>Melbourne, Australia</conf-loc><conf-date>May 2006</conf-date><fpage>27</fpage><lpage>31</lpage></citation></ref>
<ref id="b8-sensors-11-09700"><label>8.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Berlemann</surname><given-names>L</given-names></name><name><surname>Hoymann</surname><given-names>C</given-names></name><name><surname>Hiertz</surname><given-names>GR</given-names></name><name><surname>Walke</surname><given-names>B</given-names></name></person-group><article-title>Unlicensed operation of IEEE 802.16: Coexistence with 802.11(a) in shared frequency bands</article-title><conf-name>Proceedings of PIMRC 2006</conf-name><conf-loc>Helsinki, Finland</conf-loc><conf-date>September 2006</conf-date><fpage>1</fpage><lpage>5</lpage></citation></ref>
<ref id="b9-sensors-11-09700"><label>9.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Siddique</surname><given-names>MM</given-names></name><name><surname>Wenning</surname><given-names>BL</given-names></name><name><surname>Muehleisen</surname><given-names>M</given-names></name></person-group><article-title>Spectrum sharing between IEEE 802.16 and IEEE 802.11 based wireless networks</article-title><conf-name>Proceedings of WoWMoM 2010</conf-name><conf-loc>Montreal, QC, Canada</conf-loc><conf-date>June 2010</conf-date><fpage>1</fpage><lpage>6</lpage></citation></ref>
<ref id="b10-sensors-11-09700"><label>10.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Jing</surname><given-names>X</given-names></name><name><surname>Raychaudhuri</surname><given-names>D</given-names></name></person-group><article-title>Spectrum co-existence of IEEE 802.11b and IEEE 802.16a networks using the CSCC etiquette protocol</article-title><conf-name>Proceedings of DySPAN 2005</conf-name><conf-loc>Baltimore, MD, USA</conf-loc><conf-date>November 2005</conf-date><fpage>243</fpage><lpage>250</lpage></citation></ref>
<ref id="b11-sensors-11-09700"><label>11.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Jing</surname><given-names>X</given-names></name><name><surname>Mau</surname><given-names>S-H</given-names></name><name><surname>Raychaudhuri</surname><given-names>D</given-names></name><name><surname>Matyas</surname><given-names>R</given-names></name></person-group><article-title>Reactive cognitive radio algorithms for co-existence between IEEE 802.11b and 802.16a networks</article-title><conf-name>Proceedings of GLOBECOM’05</conf-name><conf-loc>St Louis, MO, USA</conf-loc><conf-date>November 2005</conf-date><fpage>2465</fpage><lpage>2469</lpage></citation></ref>
<ref id="b12-sensors-11-09700"><label>12.</label><citation citation-type="book"><person-group person-group-type="author"><collab>IEEE Std 80216h™-2010</collab></person-group><source>IEEE Standard for Local and Metropolitan Area Networks—Part 16: Air interface for Broadband Wireless Access Systems</source><publisher-name>IEEE Computer Society</publisher-name><publisher-loc>New York, NY, USA</publisher-loc><year>2010</year></citation></ref>
<ref id="b13-sensors-11-09700"><label>13.</label><citation citation-type="web"><person-group person-group-type="author"><name><surname>John</surname><given-names>S</given-names></name><name><surname>Amir</surname><given-names>G</given-names></name></person-group><source>C80216h-07/017, Simulation of IEEE 802.16h and IEEE 802.11y Coexistence (Preliminary Report)</source><comment>Available online: <ext-link xlink:href="http://ieee802.org/16/le/contrib/C80216h-07_017.pdf" ext-link-type="uri">http://ieee802.org/16/le/contrib/C80216h-07_017.pdf</ext-link> (accessed on 28 August 2011)</comment></citation></ref>
<ref id="b14-sensors-11-09700"><label>14.</label><citation citation-type="book"><person-group person-group-type="author"><name><surname>Kim</surname><given-names>J</given-names></name><name><surname>Park</surname><given-names>S</given-names></name><name><surname>Rhee</surname><given-names>SH</given-names></name><name><surname>Choi</surname><given-names>Y-H</given-names></name><name><surname>Hwang</surname><given-names>H</given-names></name></person-group><source>Energy Efficient Coexistence of WiFi and WiMAX Systems Sharing Frequency Band</source><publisher-name>Springer</publisher-name><publisher-loc>Berlin, Germany</publisher-loc><month>December</month><year>2010</year><volume>6485</volume><fpage>164</fpage><lpage>170</lpage></citation></ref>
<ref id="b15-sensors-11-09700"><label>15.</label><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Kim</surname><given-names>J</given-names></name><name><surname>Park</surname><given-names>S</given-names></name><name><surname>Choi</surname><given-names>H-Y</given-names></name><name><surname>Rhee</surname><given-names>SH</given-names></name></person-group><article-title>Performance of WiFi system due to interference from WiMAX system in a shared frequency band</article-title><conf-name>Proceedings of China-Korea Joint Conference on Information and Communications</conf-name><conf-loc>Xi’an, China</conf-loc><conf-date>August 2008</conf-date><fpage>103</fpage><lpage>104</lpage></citation></ref>
<ref id="b16-sensors-11-09700"><label>16.</label><citation citation-type="book"><person-group person-group-type="author"><collab>IEEE Std 80211™-2007</collab></person-group><source>IEEE Standard for Local and Metropolitan Area Networks-Specific Requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications</source><publisher-name>IEEE Computer Society</publisher-name><publisher-loc>New York, NY, USA</publisher-loc><year>2007</year></citation></ref>
<ref id="b17-sensors-11-09700"><label>17.</label><citation citation-type="book"><person-group person-group-type="author"><collab>IEEE Std 80216™-2004</collab></person-group><source>IEEE Standard for Local and Metropolitan Area Networks-Part 16: Air Interface for Fixed Broadband Wireless Access Systems</source><publisher-name>IEEE Computer Society</publisher-name><publisher-loc>New York, NY, USA</publisher-loc><year>2004</year></citation></ref>
<ref id="b18-sensors-11-09700"><label>18.</label><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Kim</surname><given-names>J</given-names></name><name><surname>Park</surname><given-names>S</given-names></name><name><surname>Rhee</surname><given-names>SH</given-names></name><name><surname>Choi</surname><given-names>Y-H</given-names></name><name><surname>Hwang</surname><given-names>H</given-names></name><name><surname>Chung</surname><given-names>Y</given-names></name></person-group><article-title>Coexistence of WiFi and WiMAX systems based on coexistence zone within WiMAX frame structure and modified power saving mode of WiFi system</article-title><source>IEICE Trans Commun</source><year>2011</year><volume>E94-B</volume><fpage>1781</fpage><lpage>1784</lpage><pub-id pub-id-type="doi">10.1587/transcom.E94.B.1781</pub-id></citation></ref></ref-list>
<sec sec-type="display-objects">
<title>Figures and Tables</title>
<fig id="f1-sensors-11-09700" position="float">
<label>Figure 1.</label>
<caption>
<p>Coexistence of WiFi and WiMAX systems. (<bold>a</bold>) WiFi AP and WiMAX BS are not collocated; (<bold>b</bold>) WiFi AP and WiMAX BS are collocated.</p></caption>
<graphic xlink:href="sensors-11-09700f1a.gif"/>
<graphic xlink:href="sensors-11-09700f1b.gif"/></fig>
<fig id="f2-sensors-11-09700" position="float">
<label>Figure 2.</label>
<caption>
<p>Desired TDO of WiFi and WiMAX systems.</p></caption>
<graphic xlink:href="sensors-11-09700f2.gif"/></fig>
<fig id="f3-sensors-11-09700" position="float">
<label>Figure 3.</label>
<caption>
<p>Format of general MAC frame of WiFi system.</p></caption>
<graphic xlink:href="sensors-11-09700f3.gif"/></fig>
<fig id="f4-sensors-11-09700" position="float">
<label>Figure 4.</label>
<caption>
<p>Format of original PS-Request frame.</p></caption>
<graphic xlink:href="sensors-11-09700f4.gif"/></fig>
<fig id="f5-sensors-11-09700" position="float">
<label>Figure 5.</label>
<caption>
<p>Example of the original PS-Request protocol.</p></caption>
<graphic xlink:href="sensors-11-09700f5.gif"/></fig>
<fig id="f6-sensors-11-09700" position="float">
<label>Figure 6.</label>
<caption>
<p>WiMAX zones. (<bold>a</bold>) Conventional WiMAX zones; (<bold>b</bold>) WiMAX zones, including the proposed coexistence zone.</p></caption>
<graphic xlink:href="sensors-11-09700f6.gif"/></fig>
<fig id="f7-sensors-11-09700" position="float">
<label>Figure 7.</label>
<caption>
<p>Proposed coexistence zone within WiMAX frame structure.</p></caption>
<graphic xlink:href="sensors-11-09700f7.gif"/></fig>
<fig id="f8-sensors-11-09700" position="float">
<label>Figure 8.</label>
<caption>
<p>Drawback of the original PS-Request protocol.</p></caption>
<graphic xlink:href="sensors-11-09700f8.gif"/></fig>
<fig id="f9-sensors-11-09700" position="float">
<label>Figure 9.</label>
<caption>
<p>Format of revised PS-Request frame.</p></caption>
<graphic xlink:href="sensors-11-09700f9.gif"/></fig>
<fig id="f10-sensors-11-09700" position="float">
<label>Figure 10.</label>
<caption>
<p>Example of the revised PS-Request protocol.</p></caption>
<graphic xlink:href="sensors-11-09700f10.gif"/></fig>
<fig id="f11-sensors-11-09700" position="float">
<label>Figure 11.</label>
<caption>
<p>WiMAX throughput <italic>vs</italic>. received <italic>E<sub>b</sub>/N<sub>0</sub></italic>.</p></caption>
<graphic xlink:href="sensors-11-09700f11.gif"/></fig>
<fig id="f12-sensors-11-09700" position="float">
<label>Figure 12.</label>
<caption>
<p>WiFi throughput <italic>vs</italic>. received <italic>E<sub>b</sub>/N<sub>0</sub></italic>.</p></caption>
<graphic xlink:href="sensors-11-09700f12.gif"/></fig>
<table-wrap id="t1-sensors-11-09700" position="float">
<label>Table 1.</label>
<caption>
<p>Types of system for coexistence.</p></caption>
<table frame="box" rules="all">
<thead>
<tr>
<th colspan="2" align="center" valign="middle" rowspan="2"/>
<th colspan="2" align="center" valign="middle"><bold>Collaboration</bold></th></tr>
<tr>
<th align="center" valign="middle"><bold>Not collaborative</bold></th>
<th align="center" valign="middle"><bold>Collaborative</bold></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="middle" rowspan="2"><bold>Collocation</bold></td>
<td align="center" valign="middle"><bold>Not collocated</bold></td>
<td align="center" valign="middle" rowspan="2">Out of scope</td>
<td align="center" valign="middle"><xref ref-type="fig" rid="f1-sensors-11-09700">Figure 1(a)</xref></td></tr>
<tr>
<td align="center" valign="middle"><bold>Collocated</bold></td>
<td align="center" valign="middle"><xref ref-type="fig" rid="f1-sensors-11-09700">Figure 1(b)</xref></td></tr></tbody></table></table-wrap>
<table-wrap id="t2-sensors-11-09700" position="float">
<label>Table 2.</label>
<caption>
<p>WiMAX system parameters.</p></caption>
<table frame="box" rules="cols">
<thead>
<tr>
<th align="center" valign="bottom"/>
<th align="center" valign="bottom"><bold>Conventional protocol</bold></th>
<th align="center" valign="bottom"><bold>PS-Request protocols</bold></th></tr>
<tr>
<th colspan="3" align="left" valign="middle">
<hr/></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="top">
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">CZ</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula></td>
<td align="center" valign="top">0</td>
<td align="center" valign="top">16</td></tr>
<tr>
<td align="center" valign="top">
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">DL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula></td>
<td align="center" valign="top">27(=1 + 2 + 2 × 12)</td>
<td align="center" valign="top">17(=1 + 2 + 2 × 7)</td></tr>
<tr>
<td align="center" valign="top">
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">UL</mml:mi>
<mml:mi mathvariant="italic">ofdm</mml:mi></mml:msubsup></mml:mrow></mml:math></inline-formula></td>
<td align="center" valign="top">15(=3 × 5)</td>
<td align="center" valign="top">9(=3 × 3)</td></tr>
<tr>
<td align="center" valign="top"><italic>T<sub>TTG</sub></italic></td>
<td align="center" valign="top">87.2 μs</td>
<td align="center" valign="top">87.2 μs</td></tr>
<tr>
<td align="center" valign="top"><italic>T<sub>RTG</sub></italic></td>
<td align="center" valign="top">74.4 μs</td>
<td align="center" valign="top">74.4 μs</td></tr>
<tr>
<td align="center" valign="top">
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">slot</mml:mi>
<mml:mo>,</mml:mo>
<mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula></td>
<td align="center" valign="top">360</td>
<td align="center" valign="top">180</td></tr>
<tr>
<td align="center" valign="top">
<inline-formula>
<mml:math>
<mml:mrow>
<mml:msubsup>
<mml:mi>N</mml:mi>
<mml:mi mathvariant="italic">WiMAX</mml:mi>
<mml:mrow>
<mml:mi mathvariant="italic">tile</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi> </mml:mi>
<mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula></td>
<td align="center" valign="top">1050</td>
<td align="center" valign="top">840</td></tr></tbody></table></table-wrap>
<table-wrap id="t3-sensors-11-09700" position="float">
<label>Table 3.</label>
<caption>
<p>Simulation conditions.</p></caption>
<table frame="box" rules="cols">
<thead>
<tr>
<th align="center" valign="middle"/>
<th align="center" valign="middle"><bold>WiFi System (IEEE802.11g)</bold></th>
<th align="center" valign="middle"><bold>WiMAX System (IEEE802.16e)</bold></th></tr>
<tr>
<th colspan="3" align="left" valign="middle">
<hr/></th></tr></thead>
<tbody>
<tr>
<td align="center" valign="top">Bandwidth (MHz)</td>
<td align="center" valign="top">20</td>
<td align="center" valign="top">8.75</td></tr>
<tr>
<td align="center" valign="top">Sampling frequency (MHz)</td>
<td align="center" valign="top">20</td>
<td align="center" valign="top">10</td></tr>
<tr>
<td align="center" valign="top">Oversampling</td>
<td align="center" valign="top">1</td>
<td align="center" valign="top">2</td></tr>
<tr>
<td align="center" valign="top">Sample rate (Msps)</td>
<td align="center" valign="top">20</td>
<td align="center" valign="top">20</td></tr>
<tr>
<td align="center" valign="top">FFT size</td>
<td align="center" valign="top">64</td>
<td align="center" valign="top">1,024</td></tr>
<tr>
<td align="center" valign="top">Subcarrier allocation</td>
<td align="center" valign="top">-</td>
<td align="center" valign="top">PUSC</td></tr>
<tr>
<td align="center" valign="top">Modulation</td>
<td align="center" valign="top">QPSK</td>
<td align="center" valign="top">QPSK</td></tr>
<tr>
<td align="center" valign="top">Pulse shaping filter</td>
<td align="center" valign="top">Square root raised cosine filter (Roll-off factor = 1.0)</td>
<td align="center" valign="top">Square root raised cosine filter (Roll-off factor = 1.0)</td></tr>
<tr>
<td align="center" valign="top">Channel coding</td>
<td align="center" valign="top">Convolutional code (R = 1/2, K = 7)</td>
<td align="center" valign="top">Convolutional code (R = 1/2, K = 7)</td></tr>
<tr>
<td align="center" valign="top">Matched filter</td>
<td align="center" valign="top">Square root raised cosine filter (Roll-off factor = 1.0)</td>
<td align="center" valign="top">Square root raised cosine filter (Roll-off factor = 1.0)</td></tr>
<tr>
<td align="center" valign="top">Channel</td>
<td align="center" valign="top">AWGN</td>
<td align="center" valign="top">AWGN</td></tr>
<tr>
<td align="center" valign="top">Allocated time interval, not including TTG and RTG</td>
<td align="center" valign="top">1.8432 ms</td>
<td align="center" valign="top">2.9952 ms</td></tr>
<tr>
<td align="center" valign="top">Allocated time interval, including TTG and RTG</td>
<td align="center" valign="top">1.8432 ms</td>
<td align="center" valign="top">3.1568 ms</td></tr>
<tr>
<td align="center" valign="top">SIFS</td>
<td align="center" valign="top">16 μs</td>
<td align="center" valign="top">-</td></tr>
<tr>
<td align="center" valign="top">DIFS</td>
<td align="center" valign="top">34 μs</td>
<td align="center" valign="top">-</td></tr>
<tr>
<td align="center" valign="top">Frame time</td>
<td align="center" valign="top">Variable</td>
<td align="center" valign="top">5 ms</td></tr></tbody></table></table-wrap></sec></back></article>
