JP2006352844A - Wireless communication apparatus - Google Patents

Wireless communication apparatus Download PDF

Info

Publication number
JP2006352844A
JP2006352844A JP2006127110A JP2006127110A JP2006352844A JP 2006352844 A JP2006352844 A JP 2006352844A JP 2006127110 A JP2006127110 A JP 2006127110A JP 2006127110 A JP2006127110 A JP 2006127110A JP 2006352844 A JP2006352844 A JP 2006352844A
Authority
JP
Japan
Prior art keywords
frame
transmission
terminal
time
nav
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP2006127110A
Other languages
Japanese (ja)
Other versions
JP4364210B2 (en
JP2006352844A5 (en
Inventor
Tomoko Adachi
Toshihisa Nabeya
Toru Nakajima
Masahiro Takagi
Tomoya Tandai
Yoriko Utsunomiya
徹 中島
依子 宇都宮
智哉 旦代
朋子 足立
寿久 鍋谷
雅裕 高木
Original Assignee
Toshiba Corp
株式会社東芝
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toshiba Corp, 株式会社東芝 filed Critical Toshiba Corp
Priority to JP2006127110A priority Critical patent/JP4364210B2/en
Publication of JP2006352844A5 publication Critical patent/JP2006352844A5/ja
Publication of JP2006352844A publication Critical patent/JP2006352844A/en
Application granted granted Critical
Publication of JP4364210B2 publication Critical patent/JP4364210B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Abstract

A transmission success probability of a frame used for delivery confirmation such as a BlockAck frame or a BlockAckRequest frame is improved.
When acquiring a transmission period for data transmission and performing data transmission, a part of the acquired transmission period is allocated for data transmission to a wireless communication device serving as a receiving side related to the data transmission. In a wireless communication apparatus according to a communication method capable of generating a first physical frame including a delivery confirmation frame for received data and a second physical frame in which a plurality of transmission data frames are aggregated, and the first physical frame Transmitting means for transmitting a physical frame at a first transmission rate, and transmitting the second physical frame at a second transmission rate after a certain period of time has elapsed from the transmission time of the first physical frame. .
[Selection] Figure 1

Description

  The present invention relates to a method for realizing a robust wireless communication system even in a poor wireless propagation environment in a wireless communication system including wireless communication devices such as a mobile phone and a wireless LAN, which transmits and receives data via wireless.

  In the IEEE802.11e extended wireless LAN standard relating to QoS (Quality of Service) in the medium access control (MAC) layer with respect to the IEEE802.11 standard, the transmission side communication device (Initiator) transmits data. There are EDCA (enhanced distributed channel access) method and HCCA (HCF controlled channel access) method as a method for acquiring a transmission opportunity (TXOP) period (see Non-Patent Document 1).

  In IEEE802.11n aiming at further high-speed transmission, in order to reduce overhead existing between frames during transmission / reception operations in IEEE802.11e, A-MPDU (Aggregated-MAC protocol data unit), HTP (high-throughput) Several methods such as PHY) Burst have been proposed.

  In the A-MPDU, an aggregation frame combined with one PHY (Physical Layer) frame is transmitted by adding a field for identifying each frame to the head of each of a plurality of MAC (Medium Access Control) frames (see Non-Patent Document 2). ).

  In HTP Burst, PHY frames are transmitted with a RIFS (Reduced Interface Space) time shorter than a SIFS (Short Interframe Space) period used in conventional burst transmission. In HTP Burst, when performing transmission operation at different transmission rates and transmission powers to each of a plurality of communication devices (Responders), the transmission rate and transmission power can be changed by providing a RIFS between each PHY frame. Each PHY frame can be transmitted (see Non-Patent Document 2 and Non-Patent Document 3).

  In IEEE802.11n, the initiator that acquired the TXOP time gives part of the TXOP time (TXOP allocation time) to the responder and performs bidirectional communication by the piggyback method during the TXOP time acquired by the initiator, that is, Improvement of transmission efficiency by the Reverse Direction (RD) method has been proposed.

  In IEEE802.11n, if A-MPDU is used for the RD method (the method in which the initiator performs bi-directional communication with the responder using the piggyback method during the TXOP time acquired by the EDCA method or the HCCA method), the initiator is IAC ( Initiator Aggregation Control) frames are transmitted, and after SIFS has elapsed since the transmission, an IAC-RAC frame exchange is performed in which the Responder returns a RAC (Responder Aggregation Control) frame. If the RD method is adopted on the assumption that such an IAC-RAC frame exchange is performed, the initiator transmits an IAC frame written to adopt the RD method for communication within the acquired TXOP time to the responder. To do. The responder that received the IAC frame and was notified of adopting the RD method for communication during the TXOP time, and the number of Data frames that it can transmit when given a part of the TXOP time, The transmission data rate is written in the RAC frame, and the destination is sent as an initiator. The initiator determines an RDG (Reverse Direction Grant) Duration as a part of the TXOP time allocated to the responder from the number of data frames written in the RAC frame and the transmission data rate. The initiator writes the determined RDG Duration in the IAC frame, attaches it to the head of the Aggregation frame to be transmitted, and transmits it when only SIFS after the completion of the RAC frame reception has passed.

  At this time, the delivery confirmation method (AckPolicy) of the Data frame is the BlockAck system, and when this BlockAck system receives the Immediate BlockAck system (delivery confirmation request frame (BlockAckRequest frame) defined in IEEE802.11e, the delivery confirmation is performed after SIFS. When using the frame (BlockAck frame)), the BlockAckRequest frame is also combined at the end of the Aggregation frame transmitted from the Initiator (however, in the Implicit Block Ack method proposed in IEEE802.11n) BlockAckRequest is omitted).

In the above case, the Responder must transmit the reception status of the Block Ack frame when SIFS has elapsed after receiving the Aggregation frame from the initiator. In the case of RD, when a Block Ack frame is returned after SIFS, an aggregation frame obtained by aggregating the Data frame from the responder to the Block Ack frame is transmitted using a piggyback method. The time taken to transmit this aggregation frame must not exceed the RDG Duration written in the IAC frame. When the responder transmits an RDG Duration when transmitting an aggregation frame, the number of data frames ready for transmission (that is, scheduled to be transmitted this time) and the transmission data rate are put in the RAC frame, and the aggregation to be transmitted this time is sent. A reply is made at the top of the frame (see Non-Patent Document 2).
IEEE 802.11e Draft 13.0, IEEE P802.11e / D13.0, January 2005. TGn Sync Proposal Technical Specification, IEEE 802.11-04 / 889r6, May 2005. WWiSE Proposal: High throughput extension to the 802.11 Standard, IEEE 802.11-05 / 0149r2, March 2005.

  However, in the RD scheme, the BlockAck frame and the BlockAckRequest frame are combined with the Data frame group and transmitted as one PHY frame, and therefore, the Data frame group, the BlockAck frame and the BlockAckRequest frame are transmitted at the same transmission rate. . Therefore, the probability of transmission error due to the deterioration of the radio propagation environment, the occurrence of a collision, or the like is almost the same between the Data frame group, the BlockAck frame, and the BlockAckRequest frame.

  In general, when a high transmission rate is used, the probability of transmission error increases. Therefore, in order to increase the delivery probability of a BlockAck frame and a BlockAckRequest frame, it is necessary to reduce the transmission rate of the Aggregation frame. However, when the transmission rate is lowered, the aggregation frame becomes longer and the throughput is lowered.

  Conversely, if the transmission rate is increased to transmit and receive the Data frame quickly, the probability of delivery of the BlockAck frame and BlockAckRequest frame decreases, and the initiator or responder that failed to receive the BlockAck frame or BlockAckRequest frame will retransmit the aggregation frame. This becomes an extremely deteriorated communication efficiency, that is, a significant deterioration factor of the throughput. The present invention has been made to solve the above-described problem, and an object of the present invention is to improve the transmission success probability of a frame used for delivery confirmation such as a BlockAck frame or a BlockAckRequest frame.

  When a wireless communication apparatus according to an aspect of the present invention acquires a transmission period for data transmission and performs data transmission, the wireless communication apparatus uses a part of the acquired transmission period as a receiving side related to the data transmission. In a wireless communication device according to a communication method that can be shared for data transmission, a first physical frame including an acknowledgment frame for received data and a second physical frame in which a plurality of transmission data frames are aggregated are generated And generating means for transmitting the first physical frame at a first transmission rate, and transmitting the second physical frame at a second transmission rate after a certain period of time has elapsed since the transmission of the first physical frame. A wireless communication device comprising:

  According to the present invention, it is possible to satisfy both the suppression of the Responder retransmission request due to the failure of receiving the control frame and the high-speed transmission of the Data frame.

(First embodiment)
FIG. 1 is a block diagram according to an example of a wireless communication apparatus 101 that supports the contents proposed in IEEE802.11n of the wireless LAN communication standard. That is, a description will be given below on the assumption that a high-speed transmission rate of a MIMO (Multiple Input Multiple Output) method proposed in IEEE 802.11n and a transmission method in which a frequency band is extended from a 20 MHz band to a 40 MHz band are supported.

  Note that the contents proposed in IEEE802.11n described here include the IEEE802.11 standard and IEEE802.11a / b / g / e (including those positioned as amendments and recommended practices). Are all included.

  However, IEEE 802.11n is merely an example of the present invention, and it goes without saying that the present invention can be applied to all wireless communication systems.

  The wireless communication apparatus 101 includes a transmission data management unit 102, an access control unit 103, a frame generation / transmission unit 104, and a reception processing unit 105.

  The transmission data management unit 102 includes a transmission queue 106 that buffers transmission data. The transmission data management unit 102 manages transmission data in the transmission queue 106.

  The access control unit 103 performs access control such as frame transmission / reception processing and retransmission processing. The frame handled by the access control unit 103 includes a data (Data) frame including transmission data buffered in the transmission queue 106. Also included are delivery confirmation frames (such as BlockAck frames), control frames such as IAC frames, RAC frames, RTS frames, CTS frames, and management frames. The access control unit 103 includes a transmission / reception method determination unit 107, a transmission / reception state management unit 108, and a carrier sense unit 109.

  The transmission / reception method determination unit 107 determines a transmission / reception method including an aggregation method, a reverse direction (RD) method, and the presence / absence of RTS-CTS frame exchange.

  The transmission / reception state management unit 108 performs access control such as transmission / reception timing management and retransmission processing related to the transmission / reception method determined by the data transmission / reception method determination unit 107.

  The carrier sense unit 109 monitors the reception processing unit 105, and during the time indicated by the value of the NAV (network allocation vector) written in the Duration field in the received frame, the virtual carrier sense processing that becomes Busy, and the received power A carrier sense process that is Busy when larger than a predetermined value is performed.

  The frame generation / transmission processing unit 104 generates a control frame and a Data frame. The frame generation / transmission processing unit 104 performs frame aggregation and performs transmission processing.

  The reception processing unit 105 performs reception processing such as reception frame identification processing and delivery confirmation bitmap generation.

  FIG. 2 is a timing chart illustrating a method for transmitting a BlockAck frame and a plurality of Data frames at different transmission rates using the HTP Burst method when transmitting and receiving in the RD method. 3 is a flowchart relating to the operation of the terminal A201, and FIG. 4 is a flowchart relating to the operation of the terminal B202.

  In the bidirectional communication described below, it is assumed that all transmission data from the terminal A201 that is the initiator is data addressed to the terminal B202 that is the responder, and all transmission data from the terminal B202 is data that is addressed to the terminal A201. These terminals A201 and B202 are assumed to have the configuration of the wireless communication apparatus 101, and the corresponding codes in FIG. 1 are used.

  As shown in FIG. 5, in this bidirectional communication, terminals C201, D204, E205, and F206 other than terminals A201 and B202 other than terminals A201 and B202 belong to a wireless communication system to which terminals A201 and B202 belong. Shall also exist.

  The terminal C203 is within the range 207 that can receive the transmission wave of the terminal A201 and the range 208 that can receive the transmission wave of the terminal B202 when the two-way communication between the terminal A201 and the terminal B202 starts.

  When the two-way communication between the terminal A 201 and the terminal B 202 starts, the terminal D 204 is within the range 207 that can receive the transmission wave of the terminal A 201 and outside the range 208 that can receive the transmission wave of the terminal B 202.

  The terminal E205 is outside the range 207 where the transmission wave of the terminal A201 can be received and within the range 208 where the transmission wave of the terminal B202 can be received when the two-way communication between the terminal A201 and the terminal B202 starts.

  When the two-way communication between the terminal A201 and the terminal B202 starts, the terminal F206 cannot receive the transmission waves of the terminal A201 and the terminal B202, and after the two-way communication between the terminal A201 and the terminal B202 is started (that is, RTS-CTS). It is assumed that the transmission waves of the terminal A201 and the terminal B202 can be received after the exchange is completed.

  The Data frame delivery confirmation method (AckPolicy) is the ImplicitBlockAck method of the BlockAck methods proposed in IEEE802.11n. In the BlockAck method, a BlockAck frame is transmitted from the receiver as delivery confirmation of the frame transmitted by the transmitter. In the ImplicitBlockAck method, the sender does not transmit a delivery confirmation request frame (BlockAckRequest frame) as a transmission request for a BlockAck frame.

  Assume that terminal A201 performs management frame exchange such as association with terminal B202 in advance and knows that terminal B202 supports the RD method and the amount of data that terminal B202 wants to transmit to terminal A201.

  In addition, if the RD scheme is negotiated by this management frame exchange, the management frame indicates that two PHY frames with the RIFS time are transmitted from the next after the aggregation frame 304 transmitted first by the terminal A201. Both terminal A 201 and terminal B 202 know by writing to. Thereafter, both the terminal A 201 and the terminal B 202 wait for two PHY frames with the RIFS time between them when waiting in RD communication.

  However, it may be arranged to wait for two PHY frames with a RIFS time between them when it is found that bidirectional communication is performed by the RD method (that is, without management frame exchange).

  However, it may be decided to wait for three or more PHY frames sandwiching the RIFS time during standby in RD communication.

  Alternatively, when the terminal A201 performs an operation as a base station, if the RD method is used for the Beacon frame transmitted from the terminal A201, the terminal A201 will have two PHYs with the RIFS time between the first aggregation frame 304 and the next PHY. The sending of a frame may be written.

(1-1-1. RTS frame transmission of terminal A)
When data is accumulated in the transmission queue 106 prior to the start of bidirectional communication in the terminal A 201, the transmission data management unit 102 stores the priority and amount of the accumulated transmission data in the transmission / reception state management unit 108 and the transmission destination. (Step 1 in FIG. 3).

  The transmission state management unit 108 inquires of the carrier sense unit 109 whether the transmission data received can be transmitted. The carrier sense unit 109 monitors whether the received power is above a certain value (Idle) or not (Busy) (carrier sense processing). The carrier sense unit 109 monitors whether or not a transmission band is reserved (virtual carrier sense process). The transmission state management unit 108 does not perform the AIFS + Backoff time (Backoff is not necessary depending on the case. The period when the carrier sense of the carrier sense unit 109 and the result of the virtual carrier sense are both idle and the transmission band is not reserved. .)), It is determined that transmission is possible. The transmission state management unit 108 that has determined that transmission is possible passes the priority, amount, and transmission destination of the transmission data to the transmission / reception method determination unit 107 (step 2 in FIG. 3).

  In the transmission / reception method determination unit 107, the exchange of the RTS frame 301 and the CTS frame 303, the bidirectional communication by the RD method, and the length of time (NAV time) in which the bandwidth is reserved in the TXOP time (this time) In the embodiment, it is equal to the TXOP time) and a part of the TXOP time (TXOP allocation time) to be allocated to the terminal B 202 is determined (step 3 in FIG. 3).

  Here, the NAV time and the TXOP dispensing time may be fixed values, for example, or may be calculated by any calculation method. Since the calculation method is not the gist of the present invention, a description thereof will be omitted.

  The transmission / reception state management unit 108 passes the NAV value to be written in the Duration field of the RTS frame 301 to the frame generation / transmission processing unit 104 according to the determination by the transmission / reception method determination unit 107 (step 4 in FIG. 3). The value of the NAV written to the RTS frame 301 is treated as the time until TXOPLimit used in the RD method.

  The frame generation / transmission processing unit 104 generates an RTS frame 301 in which the length of the received TXOP time is written as a NAV value in the Duration field, and transmits it at the first transmission rate (step 5 in FIG. 3).

  The first transmission rate is, for example, a transmission rate or basic rate such as the 802.11a standard. Alternatively, the lower transmission rate or basic rate in 802.11n. For example, if a terminal that does not support 802.11n but supports 802.11a is in a position where it can receive the transmission wave of terminal A201 or terminal B202, the transmission rate is set to 802.11a. Conversely, if there is only a terminal that supports 802.11n at a position where the transmission wave of terminal A201 or terminal B202 can be received, the lower transmission rate or basic rate of 802.11n is set. Alternatively, when there is a terminal that does not support 802.11n but a band reservation has already been made for a terminal that does not support 802.11n, the lower transmission rate or basic rate of 802.11n is set. The RTS frame 301 addressed to the terminal B202 transmitted from the terminal A201 is also received by the terminal C203 and the terminal D204. When the terminal C203 and the terminal D204 know that the destination of the received RTS frame 301 is the terminal B202, the terminal C203 and the terminal D204 do not perform communication using the transmission band for the NAV time. As a result, the terminal A 201 can reserve the transmission band.

When the transmission of the RTS frame 301 is completed, the reception processing unit 105 waits for the CTS frame 303 from the terminal B 202 for a time corresponding to 1 slot in addition to the SIFS time. If the reception of the CTS frame 303 cannot be started within the time obtained by adding 1 slot to the SIFS time, the Backoff process for retransmitting the RTS frame 301 is started (step 6 in FIG. 3).
(1-1-2. Reception of RTS frame and transmission of CTS frame by terminal B)
The reception processing unit 105 of the terminal B 202 receives the RTS frame 301, and transmits the CTS frame 303 at the first transmission rate after SIFS time after the completion of the reception (step 101 in FIG. 4). In the CTS frame 303, a value obtained by subtracting the SIFS time and the time required to transmit the CTS frame 303 from the NAV value written in the RTS frame 301 is written as the NAV value (the length of each frame alone is set in advance). I know and have decided the transmission rate, so I know the time it takes to send). Since the RTS frame 301 and the CTS frame 303 are the same as the normal RTS-CTS exchange of IEEE 802.11, which is an existing standard, the terminal B 202 does not know that the terminal A 201 uses the RD method at this time.

  When the transmission of the CTS frame 303 is completed, the reception processing unit 105 waits until a Data frame is received (step 102 in FIG. 4).

  The CTS frame 303 addressed to the terminal A201 transmitted from the terminal B202 is also received by the terminal E205. When the terminal E205 knows that the destination of the received CTS frame 303 is the terminal A201, the terminal E205 does not perform communication using the transmission band by the value of the NAV written in the CTS frame 303. As a result, the terminal A 201 can reserve the transmission band.

(1-1-3. Reception of CTS frame and transmission of aggregation frame of terminal A)
In the terminal A 201, when the reception processing unit 105 receives the CTS frame 303 from the terminal B 202, the transmission / reception state management unit 108 displays the value indicating that the CTS frame 303 has been received and the NAV value written in the CTS frame 303. (Step 7 in FIG. 3).

  The transmission / reception state management unit 108 extracts the transmission data buffered in the transmission queue 106 and passes it to the frame generation / transmission processing unit 104 together with the TXOP allocation time determined by the transmission / reception method determination unit 107 (step 8 in FIG. 3).

  The frame generation / transmission processing unit 104 creates Data1-A305 as a QoS Cf-Poll + Data frame and Data2-A306, Data3-A307, and Data4-A308 as Data frames from the transmission data. Further, an aggregation frame 304 is formed by combining these frames with Data1-A305 as the head, Data1-A305, Data2-A306, Data3-A307, and Data4-A308 in the order of each field with a field for identifying each frame. Create (step 9 in FIG. 3).

  The TXOP allocation time is written in the QoS Control field of Data1-A305 which is a QoS Cf-Poll + Data frame. In this embodiment, the TXOP allocation time is a value obtained by adding the RIFS time, the time required for transmission of the Aggregation in frame 311 described later, the SIFS time, and the time required for transmission of the BlockAck frame 317 to the Aggregation in frame 311. . In each of Data1-A305, Data2-A306, Data3-A307, and Data4-A308, the SIFS time and the time taken to transmit the aggregation frame 304 are calculated from the NAV value written in the CTS frame 303 transmitted by the terminal B202. The value obtained by subtracting is written as the NAV value. That is, the NAV value is a value indicating the length from the completion of transmission of the aggregation frame 304 to the end time of the NAV time.

  The frame generation / transmission processing unit 104 starts transmission of the aggregation frame 304 after SIFS time after the reception processing unit 105 completes reception of the CTS frame 303 of the terminal B 202 (step 10 in FIG. 3). This transmission is performed at a second transmission rate that is higher than the first transmission rate. This second transmission rate is, for example, a higher transmission rate of the 802.11n standard, for example, a higher rate by MIMO.

  When transmission of the aggregation frame 304 is completed, the reception processing unit 105 waits for the BlockAck frame 310 from the terminal B 202 for a time corresponding to 1 slot in addition to the SIFS time. If the BlockAck frame 310 cannot be received within the time obtained by adding 1 slot time to the SIFS time, the aggregation frame 304 is retransmitted (step 11 in FIG. 3).

  Here, since the terminal A 201 knows that it will use the RD method, the terminal A 201 causes the reception processing unit 105 to wait for two PHY frames with the RIFS time interposed therebetween.

(1-1-4. Terminal B Aggregation Frame Reception and HTP Burst Frame Transmission)
The reception processing unit 105 of the terminal B 202 that has received the aggregation frame 304 receives the value indicating that the QoS Cf-Poll + Data frame has been received, the TXOP distribution time written in the Data 1 -A 305, the Data 1 -A 305, and the Data 2 -A 306. , Data3-A307, Data4-A308, and the NAV value written to each of them, is sent to the transmission / reception state management unit 108. Also, the reception processing unit 105 creates a Bitmap for notifying the other party of the delivery confirmation from the reception success / failure status of Data1-B312, Data2-B313, Data3-B314, Data4-B315 transmitted from the terminal A201, and performs transmission / reception state management It passes to the part 108. (Step 103 in FIG. 4).

  Terminal B 202 knows that terminal A 201 uses the RD method only when receiving a QoS Cf-Poll + Data frame that also has a function as a Poll frame for notifying that a TXOP allocation time has been given. The terminal B 202 that knows to use the RD method transmits the transmission data to be transmitted to the terminal A 201 in the TXOP allocation time as a Data frame.

  The terminal B 202 that knows that the terminal A 201 uses the RD method causes the reception processing unit 105 to wait for two PHY frames sandwiching the RIFS time in the subsequent standby.

  The transmission / reception state management unit 108 determines that the terminal A 201 is communicating by the RD method from the value indicating that the QoS Cf-Poll + Data frame has been received. The transmission / reception state management unit 108 takes out transmission data buffered in the transmission queue 106, generates a frame together with a bit map for notifying the partner of the TXOP allocation time, the NAV value received from the reception processing unit 105, and the delivery confirmation. The data is transferred to the transmission processing unit 104 (step 104 in FIG. 4). The amount of transmission data extracted from the transmission queue 106 will be described later.

  The frame generation / transmission processing unit 104 uses the Bitmap for notifying the other party of the delivery confirmation, and sends a delivery confirmation (BlockAck) frame 310 for the Data1-A305, Data2-A306, Data3-A307, and Data4-A308 transmitted from the terminal A201. create. Further, the frame generation / transmission processing unit 104 creates Data1-B312, Data2-B313, Data3-B314, Data4-B315 from the transmission data as Data frames. Data 1 -B 312, Data 2 -B 313, Data 3 -B 314, and Data 4 -B 315 are combined to create an aggregation frame 311.

  Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the SIFS time and the time required for transmission of the BlockAck frame 310 from the received NAV value as the NAV value in the BlockAck frame 310. That is, the NAV value is a value indicating the length from the completion of transmission of the BlockAck frame 310 to the end time of the NAV time.

  The frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the RIFS time and the time taken to transmit the aggregation frame 311 from the value of the NAV written in the BlockAck frame 310, Data1-B312, Data2-B313, Data3-B314, Data4 -Write to B315 as the value of NAV. That is, the NAV value is a value indicating the length from the completion of transmission of the aggregation frame 311 to the end time of the NAV time. (Step 105 in FIG. 4).

  Hereinafter, a frame in which the RIFS time is sandwiched between the BlockAck frame and the Aggregation frame is referred to as an HTP Burst frame (details will be described in the tenth embodiment). The amount of transmission data that the transmission / reception state management unit 108 takes out from the transmission queue 106 and passes to the frame generation / transmission processing unit 104 is such that the frame length of the HTP Burst frame 351 exceeds the TXOP allocation time written in the Data 1 -A 305. No amount. The frame generation / transmission processing unit 104 starts transmission of the created HTP Burst frame 351 after SIFS time after the reception processing unit 105 completes reception of the aggregation frame 304 transmitted from the terminal A201.

  The transmission of the HTP Burst frame 351 will be described in detail. First, transmission of the BlockAck frame 310 is started (step 106 in FIG. 4). The transmission rate of transmission of the BlockAck frame 310 is set as the first transmission rate.

  The frame generation / transmission processing unit 104 waits for the RIFS time to start transmission of the aggregation frame 311 after completing transmission of the BlockAck frame 310 (step 107 in FIG. 4). During this time, the frame generation / transmission processing unit 104 changes the transmission rate from the first transmission rate to the second transmission rate.

The frame generation / transmission processing unit 104 transmits the aggregation frame 311 at the second transmission rate when the RIFS time has elapsed after completing the transmission of the BlockAck frame 310 (step 108 in FIG. 4).
When the aggregation frame 311 is transmitted, the reception processing unit 105 waits for a frame from the terminal A 201 (step 109 in FIG. 4).

(1-1-5. Reception of HTP Burst Frame and Transmission of HTP Burst Frame by Terminal A)
The operation of the terminal A 201 when data to be transmitted to the terminal B 202 is accumulated in the transmission queue 106 when the HTP Burst frame is received will be described.

  The reception processing unit 105 of the terminal A 201 that has received the HTP Burst frame 351 receives a Bitmap for notifying the other party of the delivery confirmation indicating the delivery confirmation from the reception success / failure status of the Data 1 -B 312, Data 2 -B 313, Data 3 -B 314, and Data 4 -B 315. It is generated and transferred to the transmission / reception state management unit 108 together with the NAV value written in each of Data1-B312, Data2-B313, Data3-B314, and Data4-B315. The reception processing unit 105 also passes the received Bitmap written in the BlockAck frame 310 to the transmission / reception state management unit 108 (step 12 in FIG. 3).

  The transmission / reception state management unit 108 will be described later in order to retransmit the Data frame when values indicating non-delivery of Data1-A305, Data2-A306, Data3-A307, and Data4-A308 are written in the received Bitmap. Put it in the Aggregation frame 318. Further, the transmission / reception state management unit 108 extracts transmission data buffered in the transmission queue 106, generates a frame together with the TXOP allocation time received from the transmission / reception method determination unit 107, the NAV value received from the reception processing unit 105, and the transmission bitmap. -It passes to the transmission process part 104 (step 13 of FIG. 3).

  The frame generation / transmission processing unit 104 creates a BlockAck frame 317 for Data1-B312, Data2-B313, Data3-B314, Data4-B315 transmitted from the terminal B202 using the received transmission Bitmap. In addition, the frame generation / transmission processing unit 104 creates an aggregation frame 318 of Data5-A319 as a QoS Cf-Poll + Data frame and Data5-A319, Data6-A320, Data7-A321, and Data8-A322 as Data frames from transmission data. To do. However, if there is a Data frame to be retransmitted, the Data frame to be retransmitted is added before the new Data frame created here. However, when the number of retransmitted data frames is large, the number of new data frames is reduced or no new data frame is attached. Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the SIFS time and the time required to transmit the BlockAck frame 317 from the NAV value received from the reception processing unit 105 in the BlockAck frame 317 as the NAV value. That is, the NAV value is a value indicating the length from the completion of transmission of the BlockAck frame 317 to the end time of the NAV time.

  The frame generation / transmission processing unit 104 writes the TXOP allocation time in Data1-A305 that is a QoS Cf-Poll + Data frame.

  The frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the RIFS time and the time required to transmit the aggregation frame 318 from the value of the NAV written in the BlockAck frame 317, Data5-A319, Data6-A320, Data7-A321, Data8. -Write to A322 as NAV value. That is, the NAV value is a value indicating the length from the completion of transmission of the aggregation frame 318 to the end time of the NAV time (step 14 in FIG. 3). The frame generation / transmission processing unit 104 starts transmission of the created HTP Burst frame 352 after SIFS time after the reception processing unit 105 completes reception of the HTP Burst frame 351 transmitted from the terminal B202.

  The transmission of the HTP Burst frame 352 will be described in detail. First, transmission of a BlockAck frame 317 is started (step 15 in FIG. 3). The transmission rate of transmission of the BlockAck frame 317 is set as the first transmission rate.

  The frame generation / transmission processing unit 104 waits to start transmission of the aggregation frame 318 for the RIFS time after completing transmission of the BlockAck frame 317 (step 16 in FIG. 3). During this time, the frame generation / transmission processing unit 104 changes the transmission rate from the first transmission rate to the second transmission rate.

  The frame generation / transmission processing unit 104 transmits the aggregation frame 318 at the second transmission rate when the RIFS time has elapsed after completing the transmission of the BlockAck frame 317 (step 17 in FIG. 3).

  The terminal F206 could not receive the RTS frame 301 transmitted by the terminal A201 and the CTS frame 303 transmitted by the terminal B202 because they were not in a state where they could be received when they were transmitted. By receiving any BlockAck frame or Aggregation frame later, the NAV value written in the Frame is received, and communication using the transmission band is not performed only for the time of the NAV value. . As a result, the terminal A 201 can also reserve the transmission band for the terminal F 206.

  In addition, even if the terminal F206 does not support 802.11n and cannot receive an aggregation frame or a frame transmitted at a high transmission rate by MIMO, the first transmission that can also be received by the terminal F206 prior to the Data frame. Since the BlockAck frame 317 is transmitted at the rate, the terminal F206 can know the destination and the value of the NAV by the BlockAck frame 317 before receiving the Data frame transmitted as the aggregation frame 318. By knowing the destination and the value of NAV, the terminal F206 can know that the bandwidth is reserved and its length even when the data frame sent thereafter cannot be received.

  When the transmission of the HTP Burst frame 352 is completed, the reception processing unit 105 waits for the BlockAck frame 324 from the terminal A 201 for a time corresponding to 1 slot in addition to the SIFS time. If the BlockAck frame 324 cannot be received within the time obtained by adding 1 slot to the SIFS time, the HTP Burst frame 352 is retransmitted (step 18 in FIG. 3).

(1-1-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
The reception processing unit 105 of the terminal B202 that has received two PHY frames sandwiching the RIFS time, that is, the HTP Burst frame 352, confirms delivery based on the reception success / failure status of Data5-A319, Data6-A320, Data7-A321, and Data8-A322. A Bitmap that indicates delivery confirmation to the other party is generated. The reception processing unit 105 receives the value indicating that the QoS Cf-Poll + Data frame has been received, the TXOP allocation time written in the Data5-A319, the Data5-A319, the Data6-A320, the Data7-A321, and the Data8-A322. 4 is passed to the transmission / reception state management unit 108 (step 110 in FIG. 4). The Nap value written in (2), the Bitmap for notifying the other party of the delivery confirmation, and the Bitmap written in the BlockAck frame 317 are received.

  The transmission / reception state management unit 108 will be described later in order to retransmit the Data frame when values indicating non-delivery of Data1-B312, Data2-B313, Data3-B314, Data4-B315 are written in the received Bitmap. Put it in the Aggregation frame 325. The transmission / reception state management unit 108 extracts the transmission data buffered in the transmission queue 106, and sends it to the frame generation / transmission processing unit 104 together with the NAV value received from the reception processing unit 105 and the Bitmap for notifying the other party of the delivery confirmation. (Step 111 in FIG. 4). The amount of transmission data extracted from the transmission queue 106 will be described later.

  The frame generation / transmission processing unit 104 creates a BlockAck frame 324 for Data5-A319, Data6-A320, Data7-A321, and Data8-A322 transmitted from the terminal A201, using the Bitmap that notifies the other party of the delivery confirmation.

  The frame generation / transmission processing unit 104 creates Data5-B326, Data6-B327, Data7-B328, and Data8-B329 from the transmission data as Data frames. Data 5 -B 326, Data 6 -B 327, Data 7 -B 328, and Data 8 -B 329 are combined to create an aggregation frame 325 (step 112 in FIG. 4).

  Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the SIFS time and the time required to transmit the BlockAck frame 324 from the received NAV value as the NAV value in the BlockAck frame 324. That is, the NAV value is a value indicating the length from the completion of transmission of the BlockAck frame 324 to the end time of the NAV time.

  Further, the frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the RIFS time and the time taken to transmit the aggregation frame 325 from the value of the NAV written in the BlockAck frame 324, Data5-B326, Data6-B327, Data7-B328, Write to Data8-B329 as the value of NAV. That is, this NAV value is a value indicating the length from the completion of transmission of the Aggregation frame 325 to the end time of the NAV time. The amount of transmission data that the transmission / reception state management unit 108 extracts from the transmission queue 106 and passes to the frame generation / transmission processing unit 104 is the frame length of the HTP Burst frame with the RIFS time between the BlockAck frame 324 and the Aggregation frame 325. , QoS Cf-Poll + Data frame is set to an amount that does not exceed the TXOP dispensing time written in Data5-A319. However, if there are Data frames to be retransmitted, the number of Data frames created here is reduced by that amount. That is, the amount of transmission data that the transmission / reception state management unit 108 takes out from the transmission queue 106 and passes to the frame generation / transmission processing unit 104 is the frame length of the HTP Burst frame 353 formed by the BlockAck frame 324, the RIFS time, and the aggregation frame 325. Is an amount that does not exceed the TXOP dispensing time.

  The frame generation / transmission processing unit 104 starts transmission of the created HTP Burst frame 353 after SIFS time after the reception processing unit 105 completes reception of the HTP Burst frame transmitted from the terminal A201.

  The transmission of the HTP Burst frame 353 will be described in detail. First, transmission of a BlockAck frame 324 is started (step 113 in FIG. 4). The transmission rate of transmission of the BlockAck frame 324 is set as the first transmission rate.

  After completing the transmission of the BlockAck frame 324, the frame generation / transmission processing unit 104 waits for the RIFS time to start transmission of the Aggregation frame 325 (step 114 in FIG. 4). During this time, the frame generation / transmission processing unit 104 changes the transmission rate from the first transmission rate to the second transmission rate.

  The frame generation / transmission processing unit 104 transmits the aggregation frame 325 at the second transmission rate when the RIFS time has elapsed after completing the transmission of the BlockAck frame 324 (step 115 in FIG. 4).

  When the transmission of the HTP Burst frame 353 is completed, the reception processing unit 105 waits for a frame from the terminal A 201 (step 116 in FIG. 4).

(1-1-7. Terminal A HTP Burst Frame Reception and BlockAck Frame Transmission)
When the HTP Burst frame 353 is received, if there is no data to be transmitted to the terminal B 202 in the transmission queue 106 and there is no Data frame to be retransmitted, or the NAV time when transmission cannot be continued any more immediately before the end of the TXOP time. The operation of terminal A201 at the end will be described.

  The reception processing unit 105 of the terminal A 201 that has received two PHY frames sandwiching the RIFS time, that is, the HTP Burst frame 353 confirms the delivery based on the reception success / failure status of Data 5 -B 326, Data 6 -B 327, Data 7 -B 328, and Data 8 -B 329. Is transmitted to the transmission / reception state management unit 108 together with the NAV values written in Data5-B326, Data6-B327, Data7-B328, and Data8-B329. The reception processing unit 105 also passes the received Bitmap written in the BlockAck frame 324 to the transmission / reception state management unit 108 (step 19 in FIG. 3).

  The transmission / reception state management unit 108 confirms whether or not the transmission of each of Data5-A319, Data6-A320, Data7-A321, and Data8-A322 is achieved from the received Bitmap. Further, the transmission / reception state management unit 108 passes the NAV value received from the reception processing unit 105 to the frame generation / transmission processing unit 104 (step 20 in FIG. 3).

  Using the received Bitmap, the frame generation / transmission processing unit 104 creates a BlockAck frame 331 for Data5-B326, Data6-B327, Data7-B328, and Data8-B329 transmitted from the terminal B202.

  Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the SIFS time and the time required to transmit the BlockAck frame 331 from the NAV value received from the reception processing unit 105 as the NAV value in the BlockAck frame 331. That is, the NAV value is a value indicating the length from the completion of transmission of the BlockAck frame 331 to the end time of the NAV time. (Step 21 in FIG. 3).

  The frame generation / transmission processing unit 104 starts transmission of the generated BlockAck frame 331 after SIFS time after the reception processing unit 105 completes reception of the HTP Burst frame 353 transmitted from the terminal A201 (step 22 in FIG. 3). ). The transmission rate of transmission of the BlockAck frame 331 is the first transmission rate.

(1-1-8. End of TXOP time)
When the time corresponding to the value of NAV written in the BlockAck frame 331 transmitted by the terminal A201 elapses from the transmission end time of the BlockAck frame 331, the bandwidth reservation is released and the two-way communication between the terminal A201 and the terminal B202 ends. When this two-way communication ends, the reception processing units 105 of the terminals A201 and B202 stop waiting for two PHY frames with the RIFS time in between and enter a normal standby state. Furthermore, when it is desired to perform this bidirectional communication, the procedure of 1-1-1 is performed again after the AIFS + Backoff time has elapsed after the band reservation is released. Alternatively, when it is desired to perform bidirectional communication or normal communication as in the present embodiment with another terminal, after the bandwidth reservation is released and after the AIFS + Backoff time has elapsed, the other terminal is designated as terminal B202 1-1-1. Repeat from step 1.

  As described above, in the present embodiment, the control frame is transmitted at a low transmission rate, and the Data frame is transmitted at a high transmission rate.

  If transmission is performed at a low transmission rate, transmission errors due to noise or the like can be suppressed. Conversely, if transmission is performed at a high transmission rate, high-speed transmission is possible.

  According to the present invention, it is possible to satisfy both the suppression of the Responder retransmission request due to the failure of receiving the control frame and the high-speed transmission of the Data frame.

  It should be noted that terminal A 201 and terminal B 202 of the present embodiment are proposed by IEEE 802.11n as a frequency band for transmitting data, instead of the 20 MHz frequency band used in the conventional IEEE 802.11a / b / g and the like. When using a 40 MHz band frequency band in which two 20 MHz band frequencies are bundled, normal transmission data is transmitted in the 40 MHz band frequency band, and the RTS frame 301, the CTS frame 303, and the BlockAck frame 305 are transmitted. , 310, 317, 324, 331, etc., with the frequency band of the analog part set to 40 MHz band, the transmission frequency band is switched to the 20 MHz band in the PHY layer of the digital processing unit. Transmit as a 20 MHz band frame By that, it is possible to notify the value of NAV to the terminal using only 20MHz bandwidth, such as IEEE802.11a / b / g.

  When there is no terminal that uses only the 20 MHz band, or when a NAV has already been established for a terminal that uses only the 20 MHz band, it is necessary to notify the NAV to the wireless communication device that uses the 20 MHz band in the control frame. If not, the BlockAck frame can be lowered to a low transmission rate in the 40 MHz band to increase the possibility of the BlockAck frame reaching all terminals in the wireless communication system. Further, in the present embodiment, it has been described that the NAV value is notified by RTS-CTS frame exchange in which the RTS frame 301 is transmitted from the terminal A 201 and the CTS frame 303 is transmitted from the terminal B 202. However, the NAV value notification method is not limited to this. It is possible to transmit the HTP Burst frame as in the present embodiment even in the so-called IAC-RAC frame exchange or the method of transmitting the Aggregation frame only after the SIFS time when the CTS-self frame is transmitted. Not too long.

  Alternatively, when the base station makes a bandwidth reservation by the NAV for the HCCA time as in the communication by the HCCA method, the RD method may be started from the transmission of the aggregation frame without performing the RTS-CTS frame exchange or the like.

  Further, in the present embodiment, the description has been made assuming that the TXOP allocation time is written in the QoS Cf-Poll + Data frame. However, the QoS Cf-Poll frame and the Data frame are separated, and the TXOP allocation time is set in the QoS Control field of the QoS Cf-Poll frame. May be written.

  In the present embodiment, the two-way communication between the terminal A 201 and the terminal B 202 has been described. However, there is no problem whether the terminal A 201 or the terminal B 202 is a base station or a terminal station. However, if the terminal A201 is a base station, when an RTS frame is to be transmitted after the reserved transmission band is released, the access is performed by the EDCA method in which the access is started in the AIFS + Backoff time from the release. May be. Or you may perform the access by the HCCA system which transmits an RTS frame, a QoS Cf-Poll frame, and a Data frame after only PIFS time passes.

(Modification 1 of the first embodiment)
In the first embodiment, the terminal A201 writes the TXOP allocation time in the QoS Cf-Poll + Data frame. That is, the terminal A201 notifies the terminal B202 of the TXOP allocation time. Terminal B 202 has transmitted a transmission data amount not exceeding the given TXOP allocation time.

  However, the terminal B 202 may be configured to transmit transmission data as much as desired regardless of the TXOP allocation time.

  In this case, the terminal A 201 does not need to write the TXOP allocation time in the QoS Cf-Poll + Data frame. In step 105 and step 112 in FIG. 4, the amount of transmission data that the transmission / reception state management unit 108 extracts from the transmission queue 106 and passes to the frame generation / transmission processing unit 104 may be arbitrarily set.

  Even in this case, since the length of the Aggregation frame sent after the BlockAck frame transmitted by the terminal B202 is changed after the RIFS time is changed, the terminal A201 can receive without any problem. As a result of the above, terminal A 201 does not need to calculate the TXOP allocation time.

(Modification 2 of the first embodiment)
FIG. 6 is a block diagram according to an example of the wireless communication apparatus 2101 according to the present modification. FIG. 7 is a flowchart relating to the operation of the terminal A 1201, and FIG. 8 is a flowchart relating to the operation of the terminal B 1202.

  In the first embodiment, the terminal A 1201 and the terminal B 1202 both transmit their own frame, SIFS time, and BlockAck that the other party transmits next from the value of the NAV written in the control frame or Data frame received from the other party. In the above description, the value obtained by subtracting the time required for the transmission of the frame is set as the value of the NAV written in the frame transmitted by itself.

  In this modification, a value obtained by subtracting the time taken for the transmission of the own frame, the SIFS time, and the time required for the transmission of the BlockAck frame to be transmitted next by the partner from the remaining time until the end of the NAV time counted by the timer 110 is obtained. A configuration in which the value of the NAV written in the frame transmitted by itself is used will be described.

  It is assumed that the terminal A 1201 and the terminal B 1202 have the configuration of the wireless communication device 1101 described below.

  The wireless communication apparatus 1101 includes a timer 110 in addition to the configuration of the wireless communication apparatus 101 illustrated in FIG. The timer 110 provides the transmission / reception state management unit 108 with remaining time information up to a certain time.

  Other configurations are the same as those of the wireless communication apparatus 101 in FIG.

(1-3-1. RTS frame transmission of terminal A)
Steps 1001 to 1004 in FIG. 7 are the same as steps 1 to 4 in FIG.

  The frame generation / transmission processing unit 104 generates the RTS frame 301 in which the received TXOP time length is written in the Duration field as the NAV value, and transmits the RTS frame 301 at the first transmission rate. When the transmission of the RTS frame 301 is started, the timer 110 starts counting down with the value of the NAV as an initial value. (Step 1005 in FIG. 7).

  The subsequent step 1006 is the same as step 6 in FIG.

(1-3-2. RTS frame reception and CTS frame transmission of terminal B)
The timer 110 of the terminal B 1202 starts counting down using the NAV value of the RTS frame 301 received by the reception processing unit 105 as an initial value.

  Further, the reception processing unit 105 transmits the CTS frame 303 at the first transmission rate after SIFS time from the completion of reception of the RTS frame 301 (step 1101 in FIG. 8). In the CTS frame 303, a value obtained by subtracting the SIFS time and the time required to transmit the CTS frame 303 from the remaining time until the end of the NAV time counted by the timer 110 is written as the NAV value.

  The subsequent step 1102 is the same as step 102 in FIG.

(1-3-3. CTS frame reception and aggregation frame transmission of terminal A)
In the terminal A 1201, when the reception processing unit 105 receives the CTS frame 303 from the terminal B 1202, the value indicating that the CTS frame 303 has been received is passed to the transmission / reception state management unit 108 (step 1007 in FIG. 7).

  The subsequent step 2008 is the same as step 8 in FIG.

  The frame generation / transmission processing unit 104 creates Data1-A305 as a QoS Cf-Poll + Data frame and Data2-A306, Data3-A307, and Data4-A308 as Data frames from the transmission data. Further, an aggregation frame 304 is formed by combining these frames with Data1-A305 as the head, Data1-A305, Data2-A306, Data3-A307, and Data4-A308 in the order of each field with a field for identifying each frame. It is created (step 1009 in FIG. 7).

  The TXOP allocation time is written in Data1-A305 which is a QoS Cf-Poll + Data frame. For each of Data1-A305, Data2-A306, Data3-A307, and Data4-A308, the SIFS time and the time taken to transmit the aggregation frame 304 are subtracted from the remaining time until the end of the NAV time counted by the timer 110. The value is written as the value of NAV.

  Subsequent steps 1010 to 1011 are the same as steps 10 to 11 in FIG.

(1-3-4. Terminal B Aggregation Frame Reception and HTP Burst Frame Transmission)
The reception processing unit 105 of the terminal B 1202 that has received the aggregation frame 304 sends a value indicating that the QoS Cf-Poll + Data frame has been received and the TXOP allocation time written in the Data 1 -A 305 to the transmission / reception state management unit 108. hand over. In addition, the reception processing unit 105 creates a Bitmap for notifying the other party of the delivery confirmation from the reception success / failure status of Data1-B312, Data2-B313, Data3-B314, Data4-B315 transmitted from the terminal A 1201 and transmitting / receiving Passed to the state management unit 108. (Step 1103 in FIG. 8).

  The transmission / reception state management unit 108 determines that the terminal A 2201 is communicating by the RD method from the value indicating that the QoS Cf-Poll + Data frame has been received. Then, the transmission / reception state management unit 2108 takes out the transmission data buffered in the transmission queue 106 and passes it along with the TXOP allocation time and Bitmap to the frame generation / transmission processing unit 104 (step 1104 in FIG. 8).

  The frame generation / transmission processing unit 104 creates a BlockAck frame 310 for Data 1 -A 305, Data 2 -A 306, Data 3 -A 307, and Data 4 -A 308 transmitted from the terminal A 1201 using Bitmap. Further, the frame generation / transmission processing unit 104 creates Data1-B312, Data2-B313, Data3-B314, Data4-B315 from the transmission data as Data frames. Data 1 -B 312, Data 2 -B 313, Data 3 -B 314, and Data 4 -B 315 are combined to create an aggregation frame 311.

  Here, the frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the SIFS time and the time required for transmission of the BlockAck frame 310 from the remaining time until the end of the NAV time counted by the timer 110, to the BlockAck frame 310. Write as a value. That is, the NAV value is a value indicating the length from the completion of transmission of the BlockAck frame 310 to the end time of the NAV time.

  Further, the frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the RIFS time and the time taken to transmit the aggregation frame 311 from the value of the NAV written in the BlockAck frame 310, Data1-B312, Data2-B313, Data3-B314. , Data4-B315 is written as the value of NAV (step 1105 in FIG. 8).

  Subsequent steps 1106 to 1109 are the same as steps 106 to 109 in FIG.

(1-3-5. Terminal A HTP Burst Frame Reception and HTP Burst Frame Transmission)
The reception processing unit 105 of the terminal A 1201 that has received the HTP Burst frame 351 generates a Bitmap indicating delivery confirmation from the reception success / failure status of Data1-B312, Data2-B313, Data3-B314, Data4-B315, and a transmission / reception state management unit Pass to 108. (Step 1012 in FIG. 7).

  The transmission / reception state management unit 108 extracts the transmission data buffered in the transmission queue 106, and sends it to the frame generation / transmission processing unit 104 together with the TXOP allocation time received from the transmission / reception method determination unit 107 and the Bitmap received from the reception processing unit 105. (Step 1013 in FIG. 7).

  The frame generation / transmission processing unit 104 uses the received Bitmap to create a BlockAck frame 317 for Data1-B312, Data2-B313, Data3-B314, Data4-B315 transmitted from the terminal B1202. In addition, the frame generation / transmission processing unit 104 creates an aggregation frame 318 of Data5-A319 as a QoS Cf-Poll + Data frame and Data5-A319, Data6-A320, Data7-A321, and Data8-A322 as Data frames from transmission data. To do.

  Here, the frame generation / transmission processing unit 104 deducts the value obtained by subtracting the SIFS time and the time required for transmission of the BlockAck frame 317 from the remaining time until the end of the NAV time counted by the timer 110, in the BlockAck frame 317. Write as a value. The frame generation / transmission processing unit 104 writes the TXOP allocation time in Data1-A305 that is a QoS Cf-Poll + Data frame. The frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the RIFS time and the time required to transmit the aggregation frame 318 from the value of the NAV written in the BlockAck frame 317, Data5-A319, Data6-A320, Data7-A321, Data8. -Write to A322 as NAV value. (Step 1014 in FIG. 7).

  Subsequent steps 1015 to 1018 are the same as steps 15 to 18 in FIG.

(1-3-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
The reception processing unit 105 of the terminal B 2202 that has received two PHY frames sandwiching the RIFS time, that is, the HTP Burst frame 352 confirms the delivery from the reception success / failure status of Data5-A319, Data6-A320, Data7-A321, and Data8-A322. A Bitmap indicating The reception processing unit 105 passes the value indicating that the QoS Cf-Poll + Data frame has been received and the created Bitmap to the transmission / reception state management unit 108 (step 1110 in FIG. 8).

  The transmission / reception state management unit 108 takes out the transmission data buffered in the transmission queue 106 and passes it to the frame generation / transmission processing unit 104 together with the Bitmap received from the reception processing unit 105 (step 1111 in FIG. 8).

  The frame generation / transmission processing unit 104 creates a BlockAck frame 324 for Data5-A319, Data6-A320, Data7-A321, and Data8-A322 transmitted from the terminal A 1201 using Bitmap. The frame generation / transmission processing unit 104 creates Data5-B326, Data6-B327, Data7-B328, and Data8-B329 from the transmission data as Data frames. Data 5 -B 326, Data 6 -B 327, Data 7 -B 328, and Data 8 -B 329 are combined to create an aggregation frame 325.

  Here, the frame generation / transmission processing unit 104 deducts the value obtained by subtracting the SIFS time and the time required for transmission of the BlockAck frame 324 from the remaining time until the end of the NAV time counted by the timer 110, in the BlockAck frame 324. Write as a value.

  Further, the frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the RIFS time and the time taken to transmit the aggregation frame 325 from the value of the NAV written in the BlockAck frame 324, Data5-B326, Data6-B327, Data7-B328, Data N-value is written in Data8-B329 (step 1112 in FIG. 8).

  Subsequent steps 1113 to 1116 are the same as steps 113 to 116 in FIG.

(1-3-7. Terminal A HTP Burst Frame Reception and BlockAck Frame Transmission)
The reception processing unit 105 of the terminal A 2201 that has received two PHY frames sandwiching the RIFS time, that is, the HTP Burst frame 353 confirms the delivery from the reception success / failure status of Data 1 -B 312, Data 2 -B 313, Data 3 -B 314, and Data 4 -B 315. Is transmitted to the transmission / reception state management unit 108. (Step 1019 in FIG. 7).

  The transmission / reception state management unit 108 passes the Bitmap received from the reception processing unit 105 to the frame generation / transmission processing unit 104 (step 1019 in FIG. 7).

  Using the received Bitmap, the frame generation / transmission processing unit 104 creates a BlockAck frame 331 for Data5-B326, Data6-B327, Data7-B328, and Data8-B329 transmitted from the terminal B1202.

  Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the SIFS time and the time required to transmit the BlockAck frame 331 from the NAV value received from the reception processing unit 105 as the NAV value in the BlockAck frame 331.

  A value obtained by subtracting the SIFS time and the time required for transmission of the BlockAck frame 331 from the remaining time until the end of the NAV time counted by the timer 110 is written in the BlockAck frame 331 as the value of NAV. (Step 1020 in FIG. 7).

  Subsequent steps 1021 to 22 are the same as steps 21 to 22 in FIG.

(1-3-8. End of TXOP time)
When the countdown of the timer 110 of the terminal B 1202 ends, the bandwidth reservation is released and the two-way communication between the terminal A 1201 and the terminal B 1202 ends. Further, when it is desired to carry out this bidirectional communication, the procedure of 1-1 is performed again after the AIFS + Backoff time has elapsed after the band reservation is released.

  As described above, the value obtained by subtracting the time required for transmission of its own frame from the remaining time until the end of the NAV time counted by the timer 110 is set as the value of the NAV written in the frame transmitted by itself. As a result, the end of the NAV time can be reliably recognized even if there is an error in the control frame or Data frame received from the other party.

(Modification 3 of the first embodiment)
FIG. 9 is a block diagram according to an example of the wireless communication apparatus 3101 according to the present modification. FIG. 10 is a flowchart relating to the operation of the terminal A2201, and FIG. 11 is a flowchart relating to the operation of the terminal B2202.

  In the first embodiment, both the terminal A 2201 and the terminal B 2202 both determine the time required for transmission of their own frames, SIFS time, and the other party from the NAV value written in the control frame or the Data frame received from the other party. In the above description, the value obtained by subtracting the time required to transmit the BlockAck frame to be transmitted is used as the value of the NAV to be written in the frame transmitted by itself.

  In this modification, a configuration for calculating the NAV value from the time supplied by the RTC (real time clock) 111 will be described. Specifically, the time information obtained from the RTC 111 is used to record the end time of the NAV time, and then the transmission start time of the own frame, the time taken to transmit the frame, the SIFS time, and the other party transmit next. A configuration in which the value obtained by subtracting the time required for transmitting the BlockAck frame to be used is the NAV value to be written in the frame transmitted by itself will be described.

  In the bidirectional communication described below, it is assumed that all transmission data from the terminal A 2201 as the initiator is data addressed to the terminal B 2202 as the responder, and all transmission data from the terminal B 2202 is data addressed to the terminal A 2201.

  These terminal A 2201 and terminal B 2202 are assumed to have the configuration of the wireless communication apparatus 3101 described below.

  The wireless communication apparatus 3101 includes an RTC 111 in addition to the configuration of the wireless communication apparatus 101 illustrated in FIG. The RTC 111 provides time information to the transmission / reception state management unit 108.

  Other configurations are the same as those of the wireless communication apparatus 101 in FIG.

(1-4-1. Terminal A RTS frame transmission)
Steps 2001 to 2006 in FIG. 10 are the same as steps 1 to 3 in FIG.

(1-4-2. Terminal B RTS frame reception and CTS frame transmission)
The transmission / reception state management unit 108 of the terminal B 2202 stores the NAV value of the RTS frame 301 received by the reception processing unit 105 as the end time of the NAV time. Further, the reception processing unit 105 transmits the CTS frame 303 at the first transmission rate after SIFS time from the completion of reception of the RTS frame 301 (step 2101 in FIG. 11). In the CTS frame 303, a value obtained by subtracting the scheduled transmission completion time of the CTS frame 303 from the end time of the NAV time is written as the NAV value. The scheduled transmission completion time of the CTS frame 303 is calculated from the time obtained from the RTC 111 and the time taken to transmit the CTS frame 303.

  The subsequent step 2102 is the same as step 102 in FIG.

(1-4-3. CTS frame reception and aggregation frame transmission of terminal A)
In the terminal A2201, when the reception processing unit 105 receives the CTS frame 303 from the terminal B2202, the value indicating that the CTS frame 303 has been received is passed to the transmission / reception state management unit 108 (step 2007 in FIG. 10).

  The subsequent step 2008 is the same as step 8 in FIG.

  The frame generation / transmission processing unit 104 creates Data1-A305 as a QoS Cf-Poll + Data frame and Data2-A306, Data3-A307, and Data4-A308 as Data frames from the transmission data. Further, an aggregation frame 304 is formed by combining these frames with Data1-A305 as the head, Data1-A305, Data2-A306, Data3-A307, and Data4-A308 in the order of each field with a field for identifying each frame. create. (Step 2009 in FIG. 10). The TXOP allocation time is written in Data1-A305 which is a QoS Cf-Poll + Data frame. In each of Data 1 -A 305, Data 2 -A 306, Data 3 -A 307, and Data 4 -A 308, the value obtained by subtracting the transmission start time of the aggregation frame 304 and the time required for transmission of the aggregation frame 304 from the end time of the NAV time is the NAV value. Written as The transmission start time of the aggregation frame 304 is determined to be after SIFS time from the reception completion time of the CTS frame 303. Therefore, the transmission start time of the aggregation frame 304 can be calculated from the time obtained from the RTC 111.

  Subsequent steps 2010 to 2011 are the same as steps 10 to 11 in FIG.

(1-4-4. Aggregation frame reception and HTP Burst frame transmission of terminal B)
The reception processing unit 105 of the terminal B 2202 that has received the aggregation frame 304 sends a value indicating that the QoS Cf-Poll + Data frame has been received and the TXOP allocation time written in the Data 1 -A 305 to the transmission / reception state management unit 108. hand over. Also, the reception processing unit 105 creates a Bitmap indicating delivery confirmation from the reception success / failure status of Data1-B312, Data2-B313, Data3-B314, Data4-B315 transmitted from the terminal A2201, and sends it to the transmission / reception state management unit 108. hand over. (Step 2103 in FIG. 11).

  The transmission / reception state management unit 108 determines that the terminal A 2201 is communicating by the RD method from the value indicating that the QoS Cf-Poll + Data frame has been received. Then, the transmission / reception state management unit 2108 takes out the transmission data buffered in the transmission queue 106 and passes it along with the TXOP allocation time and Bitmap to the frame generation / transmission processing unit 104 (step 2104 in FIG. 11).

  The frame generation / transmission processing unit 104 creates a BlockAck frame 310 for Data 1 -A 305, Data 2 -A 306, Data 3 -A 307, and Data 4 -A 308 transmitted from the terminal A 2201 using Bitmap. Further, the frame generation / transmission processing unit 104 creates Data1-B312, Data2-B313, Data3-B314, Data4-B315 from the transmission data as Data frames. Data 1 -B 312, Data 2 -B 313, Data 3 -B 314, and Data 4 -B 315 are combined to create an aggregation frame 311.

  Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the transmission start time of the BlockAck frame 310 and the time required for transmission of the BlockAck frame 310 from the end time of the NAV time as the value of the NAV in the BlockAck frame 310.

  The transmission start time of the BlockAck frame 310 is determined to be after SIFS time from the reception completion time of the aggregation frame 304. Therefore, the transmission start time of the BlockAck frame 310 can be calculated from the time obtained from the RTC 111.

  Further, the frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the transmission start time of the aggregation frame 311 and the time required for transmission of the aggregation frame 311 from the end time of the NAV time, Data 1 -B 312, Data 2 -B 313, Data 3 -B 314, Write to Data4-B315 as the value of NAV.

  The transmission start time of the aggregation frame 311 is determined to be after SIFS time from the reception completion time of the aggregation frame 304. Therefore, the transmission start time of the aggregation frame 311 can be calculated from the time obtained from the RTC 111 (step 2105 in FIG. 11).

  Subsequent steps 2106 to 2109 are the same as steps 106 to 109 in FIG.

(1-4-5. Terminal A HTP Burst Frame Reception and HTP Burst Frame Transmission)
The reception processing unit 105 of the terminal A 2201 that has received the HTP Burst frame generates a Bitmap indicating delivery confirmation from the reception success / failure status of Data1-B312, Data2-B313, Data3-B314, Data4-B315, and the transmission / reception state management unit 108 To pass. (Step 2012 in FIG. 10).

  The transmission / reception state management unit 108 extracts the transmission data buffered in the transmission queue 106, and sends it to the frame generation / transmission processing unit 104 together with the TXOP allocation time received from the transmission / reception method determination unit 107 and the Bitmap received from the reception processing unit 105. (Step 2013 in FIG. 10).

  Using the received Bitmap, the frame generation / transmission processing unit 104 creates a BlockAck frame 317 for Data1-B312, Data2-B313, Data3-B314, Data4-B315 transmitted from the terminal B2202. In addition, the frame generation / transmission processing unit 104 creates an aggregation frame 318 of Data5-A319 as a QoS Cf-Poll + Data frame and Data5-A319, Data6-A320, Data7-A321, and Data8-A322 as Data frames from transmission data. To do.

  Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the transmission start time of the BlockAck frame 317 and the time required for transmission of the BlockAck frame 317 from the end time of the NAV time as the value of the NAV in the BlockAck frame 317. The frame generation / transmission processing unit 104 writes the TXOP allocation time in Data1-A305 that is a QoS Cf-Poll + Data frame. The transmission start time of the BlockAck frame 317 is determined to be after SIFS time from the reception completion time of the aggregation frame 311. Therefore, the transmission start time of the BlockAck frame 317 can be calculated from the time obtained from the RTC 111.

  The frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the transmission start time of the aggregation frame 318 and the time required for transmission of the aggregation frame 318 from the end time of the NAV time, Data5-A319, Data6-A320, Data7-A321, Data8. -Write to A322 as NAV value. The transmission start time of the aggregation frame 318 is determined to be after SIFS time from the reception completion time of the aggregation frame 311. Therefore, the transmission start time of the aggregation frame 318 can be calculated from the time obtained from the RTC 111 (step 2014 in FIG. 10).

  Subsequent steps 2015 to 2018 are the same as steps 15 to 18 in FIG.

(1-4-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
The reception processing unit 105 of the terminal B 2202 that has received the HTP Burst frame generates a Bitmap indicating delivery confirmation from the reception success / failure status of Data5-A319, Data6-A320, Data7-A321, and Data8-A322. The reception processing unit 105 passes the value indicating that the QoS Cf-Poll + Data frame has been received, the TXOP allocation time written in the Data5-A319, and the created Bitmap to the transmission / reception state management unit 108 (FIG. 11). Step 2110).

  The transmission / reception state management unit 108 extracts the transmission data buffered in the transmission queue 106 and passes it to the frame generation / transmission processing unit 104 together with the Bitmap received from the reception processing unit 105 (step 2111 in FIG. 11).

  The frame generation / transmission processing unit 104 creates a BlockAck frame 324 for Data5-A319, Data6-A320, Data7-A321, and Data8-A322 transmitted from the terminal A2201 using Bitmap. The frame generation / transmission processing unit 104 creates Data5-B326, Data6-B327, Data7-B328, and Data8-B329 from the transmission data as Data frames. Data 5 -B 326, Data 6 -B 327, Data 7 -B 328, and Data 8 -B 329 are combined to create an aggregation frame 325.

  Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the transmission start time of the BlockAck frame 324 and the time required for transmission of the BlockAck frame 324 from the end time of the NAV time as the value of the NAV in the BlockAck frame 324.

The transmission start time of the BlockAck frame 324 is determined to be after SIFS time from the reception completion time of the aggregation frame 318. Therefore, the transmission start time of the BlockAck frame 324 can be calculated from the time obtained from the RTC 111. Also, the frame generation / transmission processing unit 104 transmits the transmission start time of the aggregation frame 325 and the transmission of the aggregation frame 325 from the end time of the NAV time. The value obtained by subtracting the time taken for is written in Data5-B326, Data6-B327, Data7-B328, Data8-B329 as the value of NAV. The transmission start time of the aggregation frame 325 is determined to be after SIFS time from the reception completion time of the aggregation frame 318. Therefore, the transmission start time of the aggregation frame 325 can be calculated from the time obtained from the RTC 111 (step 2112 in FIG. 11).

  Subsequent steps 2113 to 2116 are the same as steps 113 to 116 in FIG.

(1-4-7. Terminal A HTP Burst Frame Reception and BlockAck Frame Transmission)
The reception processing unit 105 of the terminal A 2201 that has received the HTP Burst frame generates a Bitmap indicating delivery confirmation from the reception success / failure status of Data1-B312, Data2-B313, Data3-B314, Data4-B315, and the transmission / reception state management unit 108 To pass. (Step 2019 in FIG. 10).

  The transmission / reception state management unit 108 passes the Bitmap received from the reception processing unit 105 to the frame generation / transmission processing unit 104 (step 2020 in FIG. 10).

  Using the received Bitmap, the frame generation / transmission processing unit 104 creates a BlockAck frame 331 for Data5-B326, Data6-B327, Data7-B328, and Data8-B329 transmitted from the terminal B2202. Here, the frame generation / transmission processing unit 104 writes a value obtained by subtracting the transmission start time of the BlockAck frame 331 and the time required for transmission of the BlockAck frame 331 from the end time of the NAV time as the value of the NAV in the BlockAck frame 331. The transmission start time of the BlockAck frame 331 is determined to be after SIFS time from the reception completion time of the aggregation frame 325. Therefore, the transmission start time of the BlockAck frame 331 can be calculated from the time obtained from the RTC 111 (step 2021 in FIG. 10).

  The subsequent step 2021 is the same as step 22 in FIG.

(1-4-8. End of TXOP time)
When the end time of the NAV time is reached, the bandwidth reservation is released and the two-way communication between the terminal A 2201 and the terminal B 2202 ends. Further, when it is desired to carry out this bidirectional communication, the procedure of 1-1 is performed again after the AIFS + Backoff time has elapsed after the band reservation is released.

  As described above, the time information obtained from the RTC 111 is used to record the end time of the NAV time, and the value obtained by subtracting the transmission start time of the frame and the time required for transmission of the frame is transmitted by itself. The NAV value written in the frame is used. As a result, the end of the NAV time can be reliably recognized even if there is an error in the control frame or Data frame received from the other party.

(Modification 4 of the first embodiment)
FIG. 12 is a timing chart when the AckPolicy is a BlockAckRequest in which a BAR (BlockAckRequest) frame is connected after the Aggregation frame of the Data frame, as compared to the first embodiment.

  In this modification, the BAR frame 3309 is transmitted with the RIFS time between the transmission of the aggregation frame 3304 in the first embodiment. During this time, the frame generation / transmission processing unit 104 changes the transmission rate from the second transmission rate when the aggregation frame 3304 is transmitted to the first transmission rate. The frame generation / transmission processing unit 104 transmits the BAR frame 3309 at the first transmission rate.

  Even after the aggregation frames 3315158 and 3325 are transmitted at the second transmission rate, the BAR frames 3316, 3323 and 3330 are transmitted at the first transmission rate after waiting for the RIFS time.

  Note that the HTP Burst frame in the present modification is three PHY frames in which the RIFS time is sandwiched between the PHY frames. That is, the HTP Burst frame 3352 transmitted by the terminal A 3201 in this modification has the BAR frame 3323 behind the HTP Burst frame 352 shown in FIG. Further, the HTP Burst frame 3351 transmitted from the terminal B 3201 has a BAR frame 3316 behind the HTP Burst frame 351 shown in FIG.

  Terminal B 3202 knows that terminal A201 transmits three PHY frames with the RIFS time between the first Aggregation frame 3304 and the first Aggregation frame 3304 if the RD method is used by association or management frame exchange. Shall.

  Alternatively, when the terminal A 3201 performs an operation as a base station, if the RD method is used for the Beacon frame transmitted from the terminal A 201, the terminal A 201 has three PHYs with the RIFS time between the first aggregation frame 3304 and the next. The sending of a frame may be written.

  In this case, the reception processing unit 105 of the terminal A 3201 waits for three PHY frames with the RIFS time between the PHY frames after step 11 in FIG. Also, the reception processing unit 105 of the terminal B 3201 waits for three PHY frames with the RIFS time between the PHY frames after step 103 in FIG. As described above, the control frame including the BAR frame is transmitted at a low transmission rate, and the Data frame is transmitted at a high transmission rate. If transmission is performed at a low transmission rate, transmission errors due to noise or the like can be suppressed. Conversely, if transmission is performed at a high transmission rate, high-speed transmission is possible. Accordingly, it is possible to suppress both the Responder's resending request due to the failure of receiving the control frame including the BAR frame and the high-speed transmission of the Data frame.

(Second Embodiment)
FIG. 13 is a timing chart of the present embodiment. Terminal A 4201 is described as operating according to the flowchart of operation of terminal A 202 of the first embodiment shown in FIG. 3, and terminal B 4202 is operated according to the flowchart of operation of terminal B 202 of the first embodiment as shown in FIG. .

  In the first embodiment, the RTS frame 301 transmitted by the terminal A201 and the CTS frame 303 transmitted by the terminal B202 are each transmitted from the completion of transmission until the end of the TXOP period of the RD scheme started by the terminal A201. Has been described as writing as a value of NAV.

  In this embodiment, the value of the NAV written in the sender's RTS frame is a value until the transmission of the first aggregation frame sent by the sender and the BlockAck frame sent back by the receiver is completed. Also, each time a BlockAck frame is transmitted, an Aggregation frame of the Data frame is transmitted only after the RIFS time of the BlockAck frame, and the value of the NAV written in the BlockAck frame each time a BlockAck frame is received for this Aggregation frame Only the configuration extending from the NAV time 4361 will be described.

(2-1-1. RTS frame transmission of terminal A)
Steps 1 to 2 in FIG. 3 are the same.

  The length of the NAV time 4361 determined in step 3 is the time from the start of transmission of the RTS frame 4301 to the completion of reception of the BlockAck frame 4310 received from the terminal B 4202 unlike the first embodiment.

  Steps 4 to 6 are the same.

(2-1-2. Reception of RTS frame and transmission of CTS frame by terminal B)
Steps 4101 to 4102 in FIG. 4 are the same.

(2-1-3. Reception of CTS frame and transmission of aggregation frame of terminal A)
Steps 7 to 11 in FIG. 3 are the same.

(2-1-4. Terminal B Aggregation Frame Reception and HTP Burst Frame Transmission)
Steps 103 to 104 in FIG. 4 are the same.

  In step 105, the frame generation / transmission processing unit 104 calculates the RIFS time, the time required for transmission of the aggregation frame 4311, the SIFS time, and the time required for transmission of the BlockAck frame 4317 transmitted next by the terminal A4201. The added value is written in the BlockAck frame 4310 as the NAV value. That is, the value of this NAV is a value indicating the length from the completion of transmission of the BlockAck frame 4310 to the completion of transmission of the BlockAck frame 4317 next transmitted by the terminal A4201.

  Steps 106 to 109 are the same.

When terminal C 203 completes receiving BlockAck frame 4310, terminal C 203 prevents terminal A 4201 and terminal B 4202 from performing communication using the band in which bidirectional communication is performed for the time indicated by the value of NAV written in Block Ack frame 4310. .

  Hereinafter, the length from the bandwidth reservation end time specified by the NAV value of the RTS frame 4301 to the bandwidth reservation end time specified by the NAV value written in the BlockAck frame 4310 is referred to as a NAV extension time 4362. .

(2-1-5. Terminal A HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 12 to 13 in FIG. 3 are the same.

  In step 14, the frame generation / transmission processing unit 104 adds the RIFS time, the time required for transmission of the aggregation frame 318, the SIFS time, and the time required for transmission of the BlockAck frame 4324 next transmitted by the terminal B 4202. The combined value is written in the BlockAck frame 4317 as the NAV value. That is, the value of this NAV is a value indicating the length from the completion of transmission of the BlockAck frame 4317 to the completion of transmission of the BlockAck frame 4324 transmitted by the terminal B 4202 next.

  The same applies from step 15 to step 18.

  Here, when reception of the BlockAck frame 4317 is completed, the terminal C203 does not perform communication using the band in which the terminal A4201 and the terminal B4202 are bi-directionally communicated for the time represented by the value of the NAV written in the BlockAck frame 4317. Like that.

  Hereinafter, the length from the bandwidth reservation end time specified by the NAV value of the BlockAck frame 4310 to the bandwidth reservation end time specified by the NAV value written to the BlockAck frame 4317 is referred to as a NAV extension time 4363. .

(2-1-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 110 to 111 are the same.

  In step 112, the frame generation / transmission processing unit 104 determines the RIFS time, the time required for transmission of the aggregation frame 325, the SIFS time, and the time required for transmission of the BlockAck frame 4317 transmitted next by the terminal A4331. The added value is written in the BlockAck frame 4324 as the NAV value. That is, the value of this NAV is a value indicating the length from the completion of transmission of the BlockAck frame 4324 to the completion of transmission of the BlockAck frame 4331 transmitted by the terminal A 4201 next.

  Steps 113 to 116 are the same.

  When terminal C 203 completes receiving BlockAck frame 4324, terminal C 203 prevents terminal A 4201 and terminal B 4202 from communicating using the band in which bidirectional communication is performed for the time indicated by the value of NAV written in Block Ack frame 4324. .

  Hereinafter, the length from the bandwidth reservation end time defined by the NAV value of the BlockAck frame 4317 to the bandwidth reservation end time defined by the NAV value written to the BlockAck frame 4324 is referred to as a NAV extension time 4364. .

(2-1-7. Terminal A HTP Burst Frame Reception and BlockAck Frame Transmission)
Steps 19 to 20 in FIG. 3 are the same.

  In step 21, the frame generation / transmission processing unit 104 writes 0 as the NAV value. That is, the value of NAV is a value indicating that the band reservation is canceled, that is, the end of the NAV time 4361. Step 22 is similar.

  As described above, in the present embodiment, the NAV extension time can be further extended from the initially set NAV time.

  In this embodiment, it is necessary that the value of NAV does not exceed a predetermined maximum limit (TXOP Limit) of NAV time.

  When monitoring the value of NAV so that only terminal A 4021 does not exceed TXOPLimit, for example, the following is performed. That is, the TXOP allocation limit time is written in the QoS Control field of Data1-A4319, which is a QoS Cf-Poll + Data frame transmitted by the terminal A 4021, instead of a value indicating that communication is performed in the RD scheme. The terminal B 4202 sets the TXOP allocation limit time as the upper limit of a value obtained by adding the time required for transmission of the aggregation frame of the Data frame, the SIFS time, and the time required for transmission of the BlockAck frame. Decide. If the value obtained by adding the NAV value written in the BlockAck frame 4317 and the TXOP allocation limit time is longer than the length from the transmission completion of the BlockAck frame 4317 to the TXOP Limit, the TXOP allocation limit time is shortened. Then, the sum of the time required for transmission of the HTP Burst frame 4353 transmitted by the terminal B 4202, the SIFS time, and the time required for transmission of the BlockAck frame 4331 is adjusted to be shorter than the remaining time until the TXOP Limit. . Alternatively, the terminal A 4021 makes the HTP Burst frame 4352 only when the value obtained by adding the value of the NAV written in the BlockAck frame 4317 and the TXOP allocation limit time is longer than the length from the completion of transmission of the BlockAck frame 4317 to the TXOP Limit. May be transmitted.

  Further, when the value of NAV is monitored so that the terminal B 4022 does not exceed TXOPLimit, for example, the following is performed. Each of the terminal A 4201 and the terminal B 4202 has a value obtained by adding the HTP Burst frame and SIFS time transmitted by the terminal A 4201 and the time required to transmit the BlockAck frame for the Data frame included in the HTP Burst frame, from the remaining time until the TXOP Limit. Also, the data amount of the aggregation frame of the HTP Burst frame is reduced so as to be shorter.

(Third embodiment)
FIG. 14 is a timing chart of the present embodiment. Terminal A5201 is described as operating according to the flowchart of operation of terminal A202 of the first embodiment shown in FIG. 3, and terminal B5202 is described as operating according to the flowchart of operation of terminal B202 of the first embodiment shown in FIG. .

  In this embodiment, a description will be given of a configuration in which the NAV value written in the RTS frame 5301 of the terminal A 5201 is a value until the transmission completion of the BlockAck frame 5324 returned after the terminal B 5202 receives the HTP Burst frame 5352.

(3-1-1. RTS frame transmission of terminal A)
Steps 1 to 2 are the same.

  Unlike the first embodiment, the length of the NAV time 5361 determined in step 3 is five SIFS times, the time required for transmitting the CTS frame 5303, and the transmission of the aggregation frame 5304 transmitted by the terminal A5201. , Time required for transmission of the HTP Burst frame 5351 transmitted by the terminal B 5202, time required for transmission of the HTP Burst frame 5352 transmitted by the terminal A 5201, and time required for transmission of the BlockAck frame 5324 transmitted by the terminal B 5202 Is added to the RTS frame 5301 as the NAV value. That is, the value of this NAV is a value indicating the length from the completion of transmission of this RTS frame 5301 to the completion of transmission of the second BlockAck frame 5324 transmitted by the terminal B 5202.

  Steps 4 to 6 in FIG. 3 are the same.

(3-1-2. Reception of RTS frame and transmission of CTS frame of terminal B)
Steps 101 to 102 are the same.

(3-1-3. Terminal A CTS Frame Reception and Aggregation Frame Transmission)
Steps 7 to 11 are the same.

(3-1-4. Terminal B Aggregation Frame Reception and HTP Burst Frame Transmission)
Steps 103 to 109 are the same.

(3-1-5. Reception of HTP Burst Frame and Transmission of HTP Burst Frame by Terminal A)
Steps 12 to 13 are the same.

  In step 14, the frame generation / transmission processing unit 104 performs one RIFS time, two SIFS times, a time required to transmit the aggregation frame 318, a time required to transmit the HTP Burst frame 5353, and a BlockAck frame. A value obtained by adding the time required for the transmission of 5331 is written in the BlockAck frame 5317 as the NAV value. That is, the value of this NAV is a value indicating the length from the completion of transmission of the BlockAck frame 5317 to the completion of transmission of the BlockAck frame 5331 transmitted by the terminal A5201 itself.

  The same applies from step 15 to step 18.

  When the terminal C203 and the terminal D204 have received the BlockAck frame 5317, they do not perform communication using the band in which the terminal A5201 and the terminal B5202 are bi-directionally communicating for the time indicated by the value of the NAV written in the BlockAck frame 5317. Like that.

  Hereinafter, the length from the bandwidth reservation end time specified by the NAV value of the RTS frame 4301 to the bandwidth reservation end time specified by the NAV value written in the BlockAck frame 5317 is referred to as a NAV extension time 4362. .

(3-1-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 110 to 111 are the same.

  In step 112, the frame generation / transmission processing unit 104 adds the RIFS time, the time required for transmission of the aggregation frame 325, the SIFS time, and the time required for transmission of the BlockAck frame 5324 transmitted next by the terminal A5331. The combined value is written in the BlockAck frame 5324 as the NAV value. That is, this NAV value is a value indicating the length from the completion of transmission of the BlockAck frame 5324 to the completion of transmission of the BlockAck frame 5331 transmitted by the terminal A5201 next, and is the value of the NAV written in the BlockAck frame 5317. It is a value indicating the remaining time until the end time of the specified bandwidth reservation.

  Steps 113 to 116 are the same.

(3-1-7. Terminal A HTP Burst Frame Reception and BlockAck Frame Transmission)
Steps 19 to 20 are the same.

  In step 21, the frame generation / transmission processing unit 104 writes 0 as the NAV value. Step 22 is similar.

  As described above, both the terminal A 5201 and the terminal B 5202 notify that the NAV has been extended until the NAV started by the RTS-CTS exchange is completed. Therefore, it is possible to reliably notify the terminal that can receive only the transmission wave of the terminal A5201 or the terminal that can receive only the transmission wave of the terminal B5202 that the NAV has been extended.

(Fourth embodiment)
FIG. 15 is a timing chart of the present embodiment.

  Note that the base station A 6201 operates according to the flowchart of the operation of the terminal A 201 of the first embodiment shown in FIG. 3, and the terminal B 5202 operates according to the flowchart of the operation of the terminal B 202 of the first embodiment shown in FIG. To do.

  In this embodiment, as shown in FIG. 16, this bidirectional communication is performed in the wireless communication system to which the terminal A 6201 and the terminal B 6202 belong, in addition to the terminal A 6201 and the terminal B 6202, the terminal C 203 and the terminal D 204 that are not transmission data destinations. Terminal E205 is also present.

  It is assumed that the terminal C203, the terminal D204, and the terminal E205 can receive the transmission wave of the terminal A6201 when the two-way communication between the terminal A201 and the terminal B202 starts. That is, it is assumed that there is no hidden terminal for terminal A6201 that cannot receive the transmission wave of terminal A6201.

(4-1-1. RTS frame transmission of terminal A)
Steps 1 to 2 are the same.

  The length of the NAV time 6361 determined in step 3 is the same as that in the second embodiment.

Steps 4 to 6 are the same.

(4-1-2. Terminal B RTS frame reception and CTS frame transmission)
Steps 101 to 102 in FIG. 4 are the same.

(4-1-3. Reception of CTS frame and transmission of aggregation frame of terminal A)
Steps 7 to 11 in FIG. 3 are the same.

(4-1-4. Aggregation frame reception and HTP Burst frame transmission of terminal B)
Steps 103 to 109 in FIG. 4 are the same.

(4-1-5. Terminal A HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 12 to 13 in FIG. 3 are the same.

  In step 14, the frame generation / transmission processing unit 104 transmits the RIFS time, the two SIFS times, the time taken to transmit the aggregation frame 6318, the TXOP allocation time to be written to the Data5-A6319, and the BlockAck frame 6331. The sum of these times is written in the BlockAck frame 6317 as the NAV value. That is, the value of this NAV is a value indicating the length from the completion of transmission of the BlockAck frame 6317 to the completion of transmission of the BlockAck frame 6331 transmitted next by the terminal A 6201 itself.

  Steps 15 to 18 in FIG. 3 are the same.

  When terminal C203 and terminal D204 have received the BlockAck frame 6317, they do not communicate using the band in which terminal A6201 and terminal B6202 are bi-directionally communicating for the time indicated by the value of the NAV written in the BlockAck frame 6317. Like that.

  Hereinafter, the length from the bandwidth reservation end time specified by the NAV value of the RTS frame 4301 to the bandwidth reservation end time specified by the NAV value written in the BlockAck frame 6317 is referred to as a NAV extension time 6362. .

(4-1-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 110 to 116 in FIG. 4 are the same.

(4-1-7. Terminal A HTP Burst Frame Reception and BlockAck Frame Transmission)
Steps 19 to 22 in FIG. 3 are the same.

  As described above, until the NAV started by the RTS-CTS exchange is completed, the base station A 6201 transmits the BlockAck frame 6317 that extends the NAV.

  Until all of the terminal C203, the terminal D204, and the terminal E205 can receive the transmission wave of the base station A6201, the base station A6201 completes the transmission of the BlockAck frame 6317 and notifies the NAV extension time to all the terminals. Since the time continues, the NAV time can be extended without interruption even in the system including the base station A6201.

  Note that when extending the NAV, the base station A 6201 adjusts so that the end time of the NAV extension time does not exceed the TXOP Limit.

  In the present embodiment, the base station A6201 is referred to as a base station. However, assuming that there are no hidden terminals, the base station A 6201 may be a terminal.

(Fifth embodiment)
FIG. 17 is a timing chart of the present embodiment, FIG. 18 is a flowchart relating to the operation of the terminal A 7201, and FIG. 19 is a flowchart relating to the operation of the terminal B 7202.

Terminal A 7201 is assumed to be at the position of terminal A 201 in FIG. 5, and terminal B 7202 is assumed to be at the position of terminal B 202 in FIG.

  In this embodiment, a configuration is added to the first embodiment in which the TXOP allocation time given by terminal A7201 is changed so that bidirectional communication is performed by raising the extra time when terminal B7202 cannot use it. Will be described.

(5-1-1. RTS frame transmission of terminal A)
Steps 7001 to 7006 in FIG. 18 are the same as steps 1 to 6 in FIG.

(5-1-2. Terminal B RTS Frame Reception and CTS Frame Transmission)
Steps 7101 to 7102 in FIG. 19 are the same as steps 101 to 102 in FIG.

(5-1-3. CTS frame reception and aggregation frame transmission of terminal A)
Steps 7007 to 7011 in FIG. 18 are the same as steps 7 to 11 in FIG.

(5-1-4. Terminal B Aggregation Frame Reception and HTP Burst Frame Transmission)
Steps 7103 to 7104 in FIG. 19 are the same as steps 103 to 104 in FIG.

  In step 7105, the frame generation / transmission processing unit 104 creates Data 1 -B 7312, Data 2 -B 7313, and Data 3 -B 7314 as Data frames from the transmission data.

It should be noted that the TXOP allocation time is a value capable of transmitting four Data frames in addition to the RIFS time, the SIFS time, and the time required to transmit the BlockAck frame, whereas the terminal B7202 Only three Data frames such as Data1-B7312, Data2-B7313, and Data3-B7314 are created. This is the case, for example, when the transmission queue 106 does not have a transmission data addressed to the terminal A 7201 so that the terminal B 7202 generates four Data frames.

  Subsequently, the frame generation / transmission processing unit 104 creates an aggregation frame 7311 by combining Data1-B7312, Data2-B7313, and Data3-B7314.

Here, the frame generation / transmission processing unit 104 includes the RIFS time, the time taken to transmit the aggregation frame 311 including three Data frames (that is, the time taken to send three Data frames), the SIFS time, A value obtained by adding the time required for transmission of the BlockAck frame 7317 transmitted by the terminal A 7201 and the NAV value is written in the BlockAck frame 7310. That is, the value of this NAV is a value indicating the length from the completion of transmission of the BlockAck frame 7310 to the completion of transmission of the BlockAck frame 7317 transmitted next by the terminal A7201.

  Steps 7106 to 7109 in FIG. 19 are the same as steps 106 to 109 in FIG.

  Here, even if the terminal C204 receives the BlockAck frame 7310, regardless of the value of the NAV written in the BlockAck frame 7310, the end of the NAV time 7361 defined by the RTS-CTS frame exchange or a Cf-end frame 7332 described later is provided. Communication using the transmission band is not performed until is received.

(5-1-5. Reception of HTP Burst Frame and Transmission of HTP Burst Frame by Terminal A)
Steps 7012 to 7018 in FIG. 18 are the same as steps 12 to 18 in FIG.

  Here, when the value of the NAV written in the BlockAck frame 7310 transmitted by the terminal B 7202 is shorter than the remaining time up to the end time of the NAV time 7361 here, which is equivalent to the TXOP time, the terminal A 7201 has the Data 1 -A 4305. Know that the TXOP allocation time written in is left by that short amount.

(5-1-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 7110 to 7110 in FIG. 19 are the same as steps 110 to 110 in FIG.

  In step 7111, the transmission / reception state management unit 108 determines whether there is a data frame to be retransmitted from the bitmap of the BlockAck frame 7317, prepares a data frame to be retransmitted, and then sends new transmission data from the transmission queue 106. Perform the removal process. Here, since the transmission data addressed to the terminal A7201 is not in the transmission queue 106, the transmission / reception state management unit 108 passes the Bitmap for notifying the delivery confirmation to the frame generation / transmission processing unit 104 and there is no transmission data addressed to the terminal A7201. To be notified.

  In step 7112, the frame generation / transmission processing unit 104 creates a BlockAck frame 7324 for Data5-A7319, Data7-A7320, Data7-A7321, and Data8-A7322 transmitted from the terminal A7201 using Bitmap. Further, since the frame generation / transmission processing unit 104 is notified that there is no transmission data addressed to the terminal A 7201, the frame generation / transmission processing unit 104 creates a QoS Null frame 7326 for notifying the terminal A 7201 that there is no transmission data addressed to the terminal A 7201. The frame generation / transmission processing unit 104 adds the RIFS time, the time taken for transmission of the QoS Null frame 7326, the SIFS time, and the time taken for transmission of the BlockAck frame 7317 next transmitted by the terminal A7331. Are written in the BlockAck frame 7324 as the value of NAV. That is, the NAV value is a value indicating the length from the completion of transmission of the BlockAck frame 7324 to the completion of transmission of the BlockAck frame 7331 transmitted next by the terminal A7201.

  The frame generation / transmission processing unit 104 writes the value obtained by subtracting the RIFS time and the time taken to transmit the QoS Null frame 7326 from the NAV value written in the BlockAck frame 7324 as the NAV value in the QoS Null frame 7326. That is, the NAV value is a value indicating the length from the completion of transmission of the QoS Null frame 7326 to the completion of transmission of the BlockAck frame 7331 transmitted next by the terminal A7201.

  From Step 7113 to Step 7116 in FIG. 19, the transmission aggregation frame in Step 113 to Step 116 in FIG. 4 is simply replaced with a QoS Null frame.

(5-1-7. Terminal A HTP Burst Frame Reception and BlockAck Frame Transmission)
The reception processing unit 105 of the terminal A 7201 that has received two PHY frames sandwiching the RIFS time, that is, the HTP Burst frame 7353, normally receives the QoS Null frame 7326, and passes a transmission request for the Ack frame 7331 to the transmission / reception state management unit 108. (Step 7019 in FIG. 18).

  The transmission / reception state management unit 108 passes the transmission request for the Ack frame 7331 to the frame generation / transmission processing unit 104 (step 7020 in FIG. 18).

  The frame generation / transmission processing unit 104 creates an Ack frame 7331 for the QoS Null frame 7326 transmitted from the terminal B 7202 according to the received transmission request. Further, the frame generation / transmission processing unit 104 creates a Cf-end frame 7332 for forcibly terminating the NAV time (step 7021 in FIG. 18).

  The frame generation / transmission processing unit 104 starts transmission of the created HTP Burst frame 7354 after SIFS time after the reception processing unit 105 completes reception of the HTP Burst frame 7353 transmitted from the terminal B 7202.

  The transmission of the HTP Burst frame 7354 will be described in detail. First, transmission of an Ack frame 7331 is started (step 22 in FIG. 18). The transmission rate of transmission of the Ack frame 7331 is set as the first transmission rate.

  When the RIFS time has elapsed after completing the transmission of the Ack frame 7331, the frame generation / transmission processing unit 104 transmits the Cf-end frame 7332 at the same transmission rate as the transmission rate of the Ack frame 7331 (see FIG. 18 step 23).

  By receiving the Cf-end frame 7332, the terminal C203 knows that the band reservation of the terminal A7201 is canceled and the band may be used.

  Furthermore, when it is desired to perform this bidirectional communication or communication with another terminal, it is performed again from the procedure 1-1-1 after the AIFS + Backoff time has elapsed.

  As described above, in this embodiment, when the terminal B 7202 cannot use the TXOP allocation time given by the terminal A 7201, it is possible to perform bidirectional communication by raising the extra time. Further, the terminal B 7202 can be notified that there is no transmission data addressed to the terminal A 7201.

As a result, the bidirectional communication can be terminated quickly without making the time left by the terminal B 7202 not be a wasted time during which no transmission / reception is performed. In this embodiment, the QoS Null frame 7326 is transmitted in step 116. Explained as what to do. However, in any frame, when the terminal A 7201 can be notified that there is no transmission data addressed to the terminal A 7201 in the transmission queue 106 of the terminal B 7202, the QoS Null frame 7326 can be replaced with another frame. This can be realized, for example, by determining that the terminal A 7201 considers that the terminal B 7202 has no transmission data addressed to the terminal A 7201 when the value of the NAV written in the BlockAck frame 7324 is 0.

  Further, in order to guarantee reception of the Cf-end frame 620 even for a terminal that only supports the IEEE802.11a / b / g / e standard, the Ack frame 7331 and the Cf-end frame 7332 are changed to a RIFS time. Instead of transmitting as an HTP Burst frame, only a SIFS time may be transmitted.

  In addition, the Cf-end frame 7332 may be transmitted after SIFS time after the reception processing unit 105 completes reception of the HTP Burst frame 7353 transmitted from the terminal B 7202 without transmitting the Ack frame 7331. In this case, it is assumed that the terminal B 7202 receives the Cf-end frame 7332, the HTP Burst frame is delivered, and the bidirectional communication is terminated. In this case, the Ack frame 7331 for the QoS Null frame 7326 is not necessary, and the Cf-end frame 7332 is transmitted alone instead of the HTP Burst frame 7354.

  In the present embodiment, the terminal A 7201 has been described as changing the transmission rate from the first transmission rate to the second transmission rate during the RIFS time after completing the transmission of the Ack frame 7331. However, Cf-end The frame 7332 may be transmitted at the first transmission rate.

(Sixth embodiment)
FIG. 20 is a timing chart of the present embodiment, and FIG. 21 is a flowchart relating to the operation of terminal A8201.

  Terminal B 8202 will be described as operating according to the flowchart of the operation of terminal B 8202 of the fifth embodiment shown in FIG.

  Further, description will be made assuming that terminal A8201 is at the position of terminal A201 in FIG. 5 and terminal B8202 is at the position of terminal B202 in FIG.

  In the present embodiment, a configuration is added to the second embodiment in which the TXOP allocation time given by the terminal A8201 is changed so that the terminal B8202 can fully use the extra time to perform bidirectional communication. Will be described.

(6-1-1. RTS frame transmission of terminal A)
Steps 8001 to 8002 in FIG. 21 are the same as steps 7001 to 7002 in FIG.

  The length of the NAV time 8361 determined in step 8003 is the same as that in the second embodiment.

  Steps 8004 to 8006 in FIG. 21 are the same as steps 7004 to 7006 in FIG.

(6-1-2. Terminal B RTS Frame Reception and CTS Frame Transmission)
Steps 7101 to 102 in FIG. 19 are the same.

(6-1-3. CTS frame reception and aggregation frame transmission of terminal A)
Steps 8007 to 8011 in FIG. 21 are the same as steps 7008 to 7011 in FIG.

(6-1-4. Terminal B Aggregation Frame Reception and HTP Burst Frame Transmission)
Steps 7103 to 7104 in FIG. 19 are the same.

  In step 7105, the frame generation / transmission processing unit 104 creates Data1-B8312, Data2-B8313, and Data3-B8314 as Data frames from the transmission data.

It should be noted that the TXOP allocation time is a value capable of transmitting four Data frames in addition to the RIFS time, the SIFS time, and the time required to transmit the BlockAck frame, whereas the terminal B8202 Only three Data frames are created, Data1-B8312, Data2-B8313, and Data3-B8314. This is the case, for example, when the terminal B 8202 does not have enough transmission data addressed to the terminal A 8201 in the transmission queue 106 to create four Data frames.

  Subsequently, the frame generation / transmission processing unit 104 combines the Data1-B8312, Data2-B8313, and Data3-B8314 to create an aggregation frame 8311.

  Here, the frame generation / transmission processing unit 104 determines the RIFS time, the time required to transmit the aggregation frame 8311 (that is, the time required to send three Data frames), the SIFS time, and the BlockAck transmitted from the terminal A8201 next. A value obtained by adding the time required for transmission of the frame 8317 and the value added to the BlockAck frame 8310 is written as the NAV value. That is, the value of this NAV is a value indicating the length from the completion of transmission of the BlockAck frame 8310 to the completion of transmission of the BlockAck frame 8317 transmitted next by the terminal A8201.

  The frame generation / transmission processing unit 104 subtracts the value obtained by subtracting the RIFS time and the time required to transmit the aggregation frame 7311 from the value of the NAV written in the BlockAck frame 8310, Data1-B8312, Data2-B8313, Data3-B8314, Data4. -Write to B8315 as the value of NAV. That is, this NAV value is a value indicating the length from the completion of transmission of the aggregation frame 7311 to the completion of transmission of the BlockAck frame 8317 transmitted by the terminal A8201 next.

  Steps 7106 to 7109 in FIG. 19 are the same.

  Here, when the terminal C204 receives the BlockAck frame 8310, the terminal A8201 and the terminal B8202 have the two-way communication bandwidth indicated by the value of the NAV written in the BlockAck frame 8310 after the completion of the reception of the BlockAck frame 8310. Do not use communication. That is, the bandwidth reservation for the terminal C204 of the terminal A8201 is extended.

(6-1-5. Terminal A HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 8012 to 8018 in FIG. 21 are the same as steps 7012 to 7018 in FIG.

  Here, if the value of the NAV written in the BlockAck frame 8310 transmitted by the terminal B8202 is shorter than the remaining time until the end of the TXOP allocation time written in the Data1-A8305, the terminal A8201 wrote in the BlockAck frame 4305 Know that the TXOP allocation time has gone by that short amount.

(6-1-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 7110 to 7111 in FIG. 19 are the same.

  In step 7112, the frame generation / transmission processing unit 104 creates an Ack frame 8324 for Data5-A8319, Data8-A8320, Data8-A8321, and Data8-A8322 transmitted from the terminal A8201 using Bitmap. Further, the frame generation / transmission processing unit 104 creates a QoS Null frame 8326.

  The frame generation / transmission processing unit 104 adds the RIFS time, the time taken for the transmission of the QoS Null frame 8326, the SIFS time, and the time taken for the transmission of the Ack frame 8317 next transmitted by the terminal A 8331. Is written in the Ack frame 8324 as the value of NAV. That is, the value of this NAV is a value indicating the length from the completion of transmission of this Ack frame 8324 to the completion of transmission of the Ack frame 8331 transmitted next by the terminal A8201.

  The frame generation / transmission processing unit 104 writes a value obtained by subtracting the RIFS time and the time taken to transmit the QoS Null frame 8326 from the NAV value written in the Ack frame 8324 as the NAV value in the QoS Null frame 8326. That is, the NAV value is a value indicating the length from the completion of transmission of the QoS Null frame 8326 to the completion of transmission of the Ack frame 8331 transmitted by the terminal A8201 next.

  Steps 7113 to 7115 in FIG. 19 are the same.

  In addition, since the frame to be transmitted is simply replaced with the QoS Null frame 8326 in Step 7116, the description thereof is omitted.

(6-1-7. Terminal A's HTP Burst Frame Reception and Ack Frame Transmission)
Steps 8019 to 8020 in FIG. 21 are the same as steps 7019 to 7020 in FIG.

  The frame generation / transmission processing unit 104 creates an Ack frame 8331 for the QoS Null frame 8326 transmitted from the terminal B 8202, using the received Bitmap. (Step 8021 in FIG. 20).

  The frame generation / transmission processing unit 104 transmits the created Ack frame 8331 after SIFS time after the reception processing unit 105 completes reception of the HTP Burst frame 8353 transmitted from the terminal B 8202 (step 22 in FIG. 20).

  In this embodiment, since the NAV extension time 8364 ends when transmission of the Ack frame 8331 is completed, it is not necessary to transmit the Cf-end frame 8332.

  Furthermore, when it is desired to perform this bidirectional communication, it is performed again from the procedure 1-1-1 after the AIFS + Backoff time has elapsed.

  As described above, in this embodiment, even in the second embodiment, when terminal B 8202 cannot use the TXOP allocation time given by terminal A 8201, the remaining time is increased and bidirectional communication is performed. Showed that it can be done.

As a result, the two-way communication can be terminated earlier by the time that the terminal B 8202 leaves (seventh embodiment).
FIG. 22 is a timing chart of the present embodiment.

  The base station A 9201 is assumed to operate according to the flowchart of the operation of the terminal A 7201 of the fifth embodiment shown in FIG. 18, and the terminal B 9202 is assumed to operate according to the flowchart of the operation of the terminal B 7202 of the fifth embodiment shown in FIG. To do. Further, description will be made assuming that base station A 9201 is at the position of terminal A 201 in FIG. 5 and terminal B 9202 is at the position of terminal B 202 in FIG.

  In this embodiment, with respect to the fourth embodiment, when the terminal B 9202 does not use up the TXOP allocation time given by the base station A 9201, it is changed so that bidirectional communication is performed by increasing the extra time. The configuration will be described.

(7-1-1. RTS frame transmission of terminal A)
Steps 7001 to 7002 in FIG. 18 are the same.

  The length of the NAV time 9361 determined in step 3 is the same as that in the fourth embodiment.

  Steps 7004 to 7006 are the same.

(7-1-2. RTS frame reception and CTS frame transmission of terminal B)
Steps 7101 to 102 in FIG. 19 are the same.

(7-1-3. Reception of CTS frame and transmission of aggregation frame of terminal A)
Steps 7007 to 7011 in FIG. 18 are the same.

(7-1-4. Terminal B Aggregation Frame Reception and HTP Burst Frame Transmission)
Steps 7103 to 7109 in FIG. 19 are the same.

(7-1-5. Terminal A HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 7012 to 7013 in FIG. 18 are the same.

  In step 14, the frame generation / transmission processing unit 104 transmits the RIFS time, the two SIFS times, the time required for transmission of the aggregation frame 9318, the TXOP allocation time to be written in the Data 5 -A 9319, and the transmission of the BlockAck frame 9331. The sum of these times is written as a NAV value in the BlockAck frame 9317, and the bandwidth reservation is extended.

  Steps 7015 to 7018 in FIG. 18 are the same.

(7-1-6. Terminal B HTP Burst Frame Reception and HTP Burst Frame Transmission)
Steps 7110 to 7115 in FIG. 19 are the same.

  Also, in the step 7116, as in the fifth and sixth embodiments, the frame to be transmitted is simply replaced with the QoS Null frame 9326, so that the description thereof is omitted.

(7-1-7. Terminal A HTP Burst Frame Reception and Ack Frame Transmission)
This is the same as steps 7019 to 7024 in FIG.

  In this embodiment, since the NAV extension time 9364 defined by the BlockAck frame 9317 continues at the time when transmission of the Ack frame 9331 is completed, it is necessary to transmit the Cf-end frame 8332.

  As described above, in this embodiment, even in the fourth embodiment, when the terminal B 9202 cannot use the TXOP allocation time given by the base station A 9201, the remaining time is incremented to perform bidirectional communication. Showed that can be done.

  As a result, the two-way communication can be terminated earlier by the time that the terminal B 9202 leaves.

(Eighth embodiment)
This will be described below with reference to the timing chart of the fifth embodiment shown in FIG. However, the BlockAck frame 7317 is replaced with the CTS-Self frame 7317.

When the terminal A 7201 cannot normally receive the HTP Burst frame transmitted from the terminal B 7202, one of the following four states occurs. In the present embodiment, the recovery will be described for each of the fifth embodiments whenever it falls into those states.

(1) When SIFS + 1 Slot time has elapsed after completion of transmission of an Aggregation frame combined with a QoS Cf-Poll + Data frame, and when the carrier sense unit 109 does not detect busyness of received power in carrier sense processing, SIFS + 1 Slot time from completion of transmission of the Aggregation frame After monitoring whether or not the received power busy is detected, the aggregation frame combined with the QoS Cf-Poll + Data frame is retransmitted. Alternatively, a BlockAck frame may be transmitted. These are the same as those defined in IEEE 802.11e.

  In this case, the CTS-Self frame 7317 is transmitted when the TXOP allocation time has elapsed. However, the terminal B 7202 waiting for two PHY frames sandwiching the RIFS time cannot receive it if the CTS-Self frame 7317 is transmitted alone.

Therefore, after the time indicated by the value of the NAV written by the terminal B 7202 in the BlockAck frame 7310 has elapsed after the terminal A 7201 has received the BlockAck frame 7324, only the RIFS time has elapsed after completing the transmission of the CTS-Self frame 7317. To transmit a Data frame. That is, the CTS-Self frame 7317 is transmitted as the HTP Burst frame 7352 with the Data frame.

(2) In the case where the carrier sense unit 109 does not detect the received power busy in the carrier sense process after the RIFS time since the block Ack frame was normally received. After the terminal A 7201 has completed the transmission of the first aggregation frame 7304, the RIFS time It is known beforehand by exchanging management frames or the like that two PHY frames sandwiching each other are transmitted with each other.

  Therefore, even if the carrier sense unit 109 of the terminal A7201 is idle in the carrier sense process after the completion of reception of the BlockAck frame 7314, that is, the first PHY frame, the terminal B7202 does not receive any frame (here, The Aggregation frame 7311) should be transmitted as the second PHY frame.

Here, according to the coverage method as in the past, the terminal A 7201 transmits a frame to be retransmitted after the PIFS time (SIFS + 1Slot) has elapsed after receiving the BlockAck frame 7310 which is the first PHY frame.

  However, the terminal B 7202 waiting for two PHY frames with the RIFS time interposed therebetween cannot receive the frame retransmitted by the terminal A 7201. Further, the frame retransmitted by the terminal A7201 collides with some frame transmitted by the terminal B7202.

  In order to avoid this, it is also conceivable to refrain from transmission for the TXOP allocation time given by the terminal A7201 to the terminal B7202. However, in this embodiment, in this case, after the terminal A 7201 receives the BlockAck frame 7324, the length of the aggregation frame transmitted by the terminal B 7202, the SIFS time, and the NAV value written in the Block Ack frame 7310 by the terminal B 7202 , The time taken to transmit the BlockAck frame is known. Thanks to this, the CTS-Self frame 7317 is transmitted after the time represented by the value of the NAV written in the BlockAck frame 7310 has elapsed. Thereafter, after a lapse of the RIFS time, the Data frame is transmitted. That is, the CTS-Self frame 7317 is transmitted as the HTP Burst frame 7352 with the Data frame.

(3) In the case where the carrier sense unit 109 detects the received power busy in the carrier sense process after the RIFS time has elapsed since the successful reception of the BlockAck frame, the RIFS after completing the reception of the BlockAck frame 7314, that is, the first PHY frame If the carrier sense unit 109 of the terminal A 7201 is Busy in the carrier sense process after a time, when the Busy changes to Idle after that, the terminal B 7202 transmits some frame (here, the Aggregation frame 7311) as the second PHY frame. ) Is considered complete.

  Therefore, in this case, after completion of reception of the BlockAck frame 7314, that is, the first PHY frame, after the RIFS time, the carrier sense unit 109 of the terminal A7201 is busy, and when the PIFS time elapses after becoming idle, -Transmission of the Self frame 7317 is started, and after completion of the RIFS time, the Data frame or the Aggregation frame is transmitted. That is, the CTS-Self frame 7317 is transmitted as the HTP Burst frame 7352 with the Data frame.

(4) The case where the carrier sense unit 109 detects the received power busy in the carrier sense process after SIFS from the completion of transmission of the aggregation frame combined with the QoS Cf-Poll + Data frame, but the received frame cannot be read normally. This corresponds to the HTP Burst frame 7351, and after the SIFS time has elapsed after the completion of the transmission of the Aggregation frame 7304, it becomes Busy only for the time corresponding to the transmission of the BlockAck frame 7314, becomes Idle only for the RIFS time, and also Busy and Become. The next Idle time is considered to correspond to the transmission completion time of the HTP Burst frame 7351. Therefore, the transmission of the CTS-Self frame 7317 is started after the PIFS time has elapsed from that point, and only the RIFS time has elapsed after the completion. Then, a Data frame is transmitted. That is, the CTS-Self frame 7317 is transmitted as the HTP Burst frame 7352 with the Data frame.

  By performing such recovery, it is possible to avoid a collision between the recovery operation frame transmitted by the terminal A 7201 and the HTP Burst frame transmitted by the terminal B 7202 in the RD scheme.

  In addition, when the terminal B 7202 cannot use the TXOP allocation time given by the terminal A 7201, if the terminal A 7201 can receive the BlockAck frame 7310, the extra time can be increased to perform bidirectional communication. it can.

  Further, by combining the recovery as in the present embodiment with the fifth embodiment, the sixth embodiment, and the seventh embodiment, the NAV stretched by the RTS-CTS frame exchange or the BlockAck frame Even if it ends at the same time as the NAV set in the BlockAck frame 7314 of the terminal B 7202, the CTS-Self frame 7317 is transmitted before or immediately after the end time of the NAV, so that the NAV has not ended, and the terminal A 7201 A collision of transmission frames with terminals other than the terminal B 7202 can be avoided.

(Ninth embodiment)
This will be described below with reference to the timing chart of the third embodiment shown in FIG. However, it is assumed that the BlockAck frame 5317 is replaced with the CTS-Self frame 5317.

  In the present embodiment, recovery will be described for the case of (2) described in the eighth embodiment with respect to the third embodiment.

  The cases (1), (3), and (4) are the same as those in the eighth embodiment.

(2) In the case where the carrier sense unit 109 does not detect the received power Busy in the carrier sense process after the RIFS time since the BlockAck frame was normally received After the terminal A5201 has completed the transmission of the first Aggregation frame 304, the RIFS time It is known beforehand by exchanging management frames or the like that two PHY frames sandwiching each other are transmitted with each other.

  Therefore, even if the reception power is idle in the carrier sense processing by the carrier sense unit 109 of the terminal A 5201 after the completion of reception of the BlockAck frame 5314, that is, the first PHY frame, the terminal B 5202 does not receive any frame. (Here, the Aggregation frame 5311) should be transmitted as the second PHY frame.

  According to the conventional recovery method, the terminal A 5201 transmits a frame to be retransmitted after the PIFS time (SIFS + 1Slot) has elapsed after receiving the BlockAck frame 5310 which is the first PHY frame.

  However, the terminal B 5202 waiting for two PHY frames with the RIFS time interposed therebetween cannot receive the frame retransmitted by the terminal A 5201. Further, the frame retransmitted by the terminal A5201 collides with some frame transmitted by the terminal B5202.

In order to avoid this, in this case, after the terminal A 5201 receives the BlockAck frame 5324, after the TXOP allocation time given to the terminal B 5202 by the terminal A 5201 ends, the RIFS is completed after the transmission of the CTS-Self frame 5317 is completed. After a lapse of time, a Data frame and an Aggregation frame are transmitted. That is, the CTS-Self frame 5317 is transmitted as the HTP Burst frame 5352 with the Data frame.

  By performing such recovery, it is possible to avoid a collision between the recovery operation frame transmitted from the terminal A5201 and the HTP Burst frame transmitted from the terminal B5202 in the RD scheme.

  Further, when the terminal B 5202 cannot use the TXOP allocation time given by the terminal A 5201, if the terminal A 5201 can detect the busyness of the reception power, the remaining time is increased and bidirectional communication is performed. Can do.

  Further, by combining the recovery as in the present embodiment with the fifth embodiment, the NAV stretched by the RTS-CTS frame exchange or the BlockAck frame is completed simultaneously with the NAV stretched by the BlockAck frame 5314 of the terminal B5202 Even in this case, the NAV has not ended before transmitting the CTS-Self frame 5317, and collision of transmission frames between the terminals A5201 and B5202 can be avoided.

(Tenth embodiment)
The configuration of the HTP Burst frame and the reception operation when receiving the HTP Burst frame in each embodiment of the present application will be described in detail.

  FIGS. 23A and 23B show the configuration of the PHY frame, and FIGS. 23C and 23D show the configuration of the HTP Burst frame.

  As shown in FIG. 23 (a), a frame transmitted / received between the terminals of each embodiment of the present application is, before the MAC frame 5 transmitted from the MAC layer such as the Data frame or the BlockAck frame to the PHY layer, A PHY header 3 that describes information such as a transmission rate and transmission frame length necessary for PHY layer control at the time of data transmission / reception is attached, and a preamble 1 necessary for time synchronization at the time of reception at the PHY layer is added before that. Are transmitted and received in a frame configuration.

In each embodiment of the present application, a plurality of PHY headers 3 and MAC frames 5 are alternately combined after the frame having the configuration of FIG. 23A and the frame of FIG. 23A. The configuration frame (Aggregation frame 20) is called a PHY frame 10. In addition, when aggregation is performed in the MAC layer, the MAC frame 5 is an aggregation frame that is aggregated without the PHY header 3.

  The HTP Burst frame has a frame configuration as shown in FIG. 23 (c). The PHY frame 10 described in FIG. 23 (a) or FIG. 23 (b) is attached with the preamble 1 and the PHY header 3 attached thereto. It is transmitted as a burst as the HTP Burst method which is one of the aggregation methods with a RIFS interval in between. This burst transmission is called an HTP Burst frame in each embodiment of the present application. Alternatively, as shown in FIG. 23D, a method may be used in which the preamble is omitted after the RIFS.

  In the HTP Burst frame 50, the RIFS time 7 is vacant during the PHY frame 10, but the RIFS time 7 is shorter than the SIFS time (16 μs in IEEE802.11a) which is the minimum time interval in the conventional IEEE802.11 standard. Since it is a significantly short period (2 μs), in order to reduce the reception processing in the PHY layer, whether the data is transmitted in the RIFS time 7 or the data is transmitted in the conventional SIFS interval or more in advance. Need to be notified. In particular, when preamble 1 is omitted as shown in FIG. 23 (d), if the PHY layer does not recognize that the PHY header comes after 2 μs, it cannot be time synchronized and may be received. I can't.

  In each embodiment of the present application, in the RD scheme, all Aggregation frames after the Aggregation frame transmitted first by the Initiator terminal are attached with one BlockAck frame at the beginning of the Aggregation frame, and one PHY with a RIFS time of 7 is provided. The fact that communication is performed using the aggregation frame of the HTP Burst method using the two PHY frames 10 that have been aggregated from the frame 10 means that before the bidirectional data transmission / reception using the RD method is started, the initiator terminal and the responder terminal Since it is decided by exchanging management frames such as associations, it is necessary to receive at RIFS time 7 in the MAC layer when transmission / reception in the RD scheme starts Because there can be seen, with respect to PHY layer, it is possible to instruct whether or not to receive treatment with RIFS time 7.

  In addition, if the above arrangement is decided to use three or more PHY frames 10 instead of two PHY frames 10, and the number of decided PHY frames 10 is also decided only by the maximum value, After receiving the PHY frame 10 in the PHY header part, preparation for continuous reception processing at RIFS time 7 is performed without giving an instruction from the MAC layer by indicating whether or not the PHY frame 10 is transmitted. I can do it.

  In addition, like the BlockAck frame, Ack frame, and Cf-end frame of each embodiment of the present application, the RD scheme communication ends at the MAC layer, and the process of transmitting two PHY frames at the RIFS interval is not performed. When the frame is received, it is notified that the PHY layer does not need to be received at the RIFS time 7 after receiving the frame, and the reception mode of the PHY layer can be returned to the normal state.

  Therefore, in the HTP Burst method in which burst transmission is performed at the RIFS interval, a special situation in which data reception is performed at the RIFS interval and a normal reception method can be appropriately controlled from the MAC layer. Further, by using the PHY header, it becomes possible to control only by the PHY layer, and the notification operation from the MAC layer can be omitted.

(Eleventh embodiment)
In the first embodiment, an RD initiator terminal performs bidirectional data transmission / reception processing with a single responder terminal. On the other hand, in this embodiment, bandwidth reservation by NAV in the RTS frame and the CTS frame described in the first embodiment is performed for the TXOP time that is all transmission periods, and the RD method and the HTP Burst method are performed. A description will be given of a method of performing transmission / reception processing combining the RD method and the HTP Burst method even when a plurality of responder terminals exist when performing combined transmission / reception processing.

  In the present embodiment, there are a plurality of responder terminals, and only the portion where the transmission destination of each data is different is different from the first embodiment. Therefore, the description will focus on the portions different from the first embodiment.

  FIG. 24 is a diagram for explaining a transmission / reception method when there are a plurality of responder terminals at the time of transmission / reception combining the RD method and the HTP Burst method.

  In this embodiment, an RTS frame 1504 in which the TXOP time used in the RD scheme is written as a NAV value is transmitted from the terminal A 1501 that is an RD initiator terminal to the terminal B 1502 that is the first responder terminal. The terminal B 1502 that has received the RTS frame 1504 describes the value obtained by subtracting the SIFS time and the time required for transmission of the CTS frame 1505 from the value of the NAV described in the RTS frame 1504 in the CTS frame 1505, and sends it to the terminal A 1501. Reply. Next, terminal A 1501 transmits an aggregation frame obtained by aggregating transmission data Data 1 -A, Data 2 -A, Data 3 -A, and Data 4 -A addressed to terminal B 1502 with a QoS Cf-Poll + Data frame at the head. Terminal B 1502 returns an HTP Burst frame 1509 prefixed with a BlockAck frame 1508 to terminal A 1501. The transmission / reception operations so far are the same as those in the first embodiment.

  Unlike the first embodiment, the terminal A 1501 that has received the HTP Burst frame 1509 switches to the RD scheme with the terminal C 1503 when transmitting the BlockAck frame for the HTP Burst frame 1509. Here, the terminal A1501 creates a BlockAck frame 1510 as a BlockAck frame for the data Data1-B, Data2-B, Data3-B, and Data4-B transmitted from the terminal B 1502 to the terminal A 1501 in the HTP Burst frame 1509. Next, after RIFS of the BlockAck frame 1510, an HTP Burst frame 1511 obtained by aggregating transmission data Data5-A, Data6-A, Data7-A, and Data8-A from the terminal A1501 to the terminal C1503 is created, and is transmitted to the terminals B1502 and C1503. Send to. In the present embodiment, the HTP Burst frame 1511 includes a BlockAck frame 1510 addressed to the terminal B 1502 and transmission data Data5-A, Data6-A, Data7-A, and Data8-A addressed to the terminal C1503. Are combined. The transmission data Data5-A addressed to the terminal C1503 is a QoS Cf-Poll + Data type frame, and performs an operation of assigning a part of the TXOP time to the terminal C1503.

  The terminal B 1502 that has received the HTP Burst frame 1511 confirms the delivery confirmation status of the data transmitted from the own station from the BlockAck frame 1510. Further, the terminal C 1503 that has received the HTP Burst frame 1511 can be seen from the QoS Cf-Poll + Data frame 1512 after the RIFS of the BlockAck frame 1510 that the TXOP time has been allocated to the own station. Next, the terminal C1503 creates a BlockAck frame 1513 for the data Data5-A, Data6-A, Data7-A, Data8-A in the HTP Burst frame 1511, and transmits transmission data Data1-C, Data2-C, An HTP Burst frame 1514 obtained by aggregating Data3-C and Data4-C after the RIFS of the BlockAck frame 1513 is created and returned to the terminal A1501. The terminal A 1501 that has received the HTP Burst frame 1514 creates a Block Ack frame 1515 for transmission data Data 1 -C, Data 2 -C, Data 3 -C, and Data 4 -C for the terminal A 1501 in the HTP Burst frame 1514, and the HTP Burst frame 1514. Is transmitted after SIFS is received, and the transmission / reception processing between the terminal B 1502 and the terminal C 1503 by the RD method is ended.

  At this time, the NAV setting method and transmission rate of the BlockAck frame in the HTP Burst frame are the same as those in the first embodiment.

  In the method described in the above embodiment, an aggregation frame obtained by aggregating a QoS Cf-Poll + Data frame is received, and after the SIFS, an HTP burst with a RIFS interval between a blockAck frame and a frame obtained by aggregating a plurality of pieces of transmission data. Since the method of transmitting a frame itself is the same as that of the other embodiments, all the transmission / reception methods of the other embodiments can be applied to the transmission / reception processing with a plurality of terminals according to the RD scheme of the present embodiment, Further, the recovery operation can be performed in the same manner.

  By the transmission / reception method of this embodiment, bidirectional communication with a plurality of terminals by the RD method is possible, and the arrival probability of a BlockAck frame can be improved over transmission data during bidirectional communication with the plurality of terminals. In addition, by transmitting the BlockAck frame using a PHY frame different from the transmission data, it is possible to extend the bandwidth reservation period using the BlockAck frame. Thus, bidirectional communication can be efficiently performed with a plurality of terminals while having the same effects as those described in other embodiments.

(Twelfth embodiment)
This embodiment is the same as the eleventh embodiment, except that when performing bidirectional communication with a plurality of terminals, a multi-pole frame that assigns a transmission period to the plurality of terminals at once is used. Only the parts different from the eleventh embodiment will be described.

  FIG. 25 is a diagram for explaining a method of bi-directionally communicating transmission data from the own station and transmission data from the plurality of terminals by assigning a transmission period to the plurality of terminals in an MMP (Multiple Receive Aggregate Multi-Poll) frame.

  Terminal A 1601, which is a terminal that starts bidirectional communication with a plurality of terminals according to the present embodiment, attaches an MMP frame 1604 to the head, and after RIFS, transmits transmission data Data1-A, Data2-A, Data3-A, Data4 to terminal B1602. The frame obtained by combining -A with one PHY frame is combined, and further, after RIFS, the transmission data Data5-A, Data6-A, Data7-A, and Data8-A to the terminal C1603 are connected to transmit the HTP Burst frame 1611.

  In the MMP frame 1604, an offset period 1607 for the terminal B 1602 and a TXOP time 1608 for the terminal B 1602 are described as a transmission period to be allocated to the terminal B 1602, and a terminal C 1603 is provided as a transmission period to be allocated to the terminal C 1603. The offset period 1609 and the TXOP time 1610 given to the terminal C 1603 are described. In the MMP frame 1604, the value of the NAV for performing bandwidth reservation for the bidirectional communication period 1605 starting from the MMP frame 1604 is described.

  The terminal B 1602 that has received the HTP Burst frame 1611 combined with the MMP frame 1604 at the head extracts the offset period 1607 for the terminal B 1602 written in the MMP frame 1604, and the transmission / reception state management unit 108 of the terminal B 1602 uses the timer for the offset period 1607. multiply. Next, the transmission data Data1-A, Data2-A, Data3-A, and Data4-A addressed to the terminal B 1602 in the HTP Burst frame 1611 are received, and a BlockAck frame 1611 is created.

  After the terminal B 1602 receives the HTP Burst frame 1611, when the timer of the offset period 1607 for the terminal B 1602 set by the transmission / reception state management unit 108 expires, the TXOP time 1608 to be given to the terminal B 1602 is obtained. At this time, the terminal B 1602 creates a BlockAck frame 1611, and after the RIFS of the BlockAck frame 1611, creates an HTP Burst frame 1612 obtained by aggregating transmission data Data1-B, Data2-B, Data3-B, and Data4-B for the terminal A1601. Then, the block Ack frame 1613 is received from the terminal A 1601 after the SIFS is transmitted to the terminal A 1601 and the HTP burst frame 1612 is transmitted. However, the HTP Burst frame 1612 adjusts the number of data to be aggregated so as not to exceed the TXOP time 1608 given to the terminal B 1602. As shown in FIG. 25, since the HTP Burst frame 1612 has a RIFS period between the BlockAck frame 1611 and the transmission data Data1-B, Data2-B, Data3-B, and Data4-B for the terminal A1601, another implementation is performed. As in the case of, the transmission rate can be changed and NAV can be notified.

  Next, when receiving the HTP Burst frame 1611, the terminal C1603 extracts the offset period 1609 with respect to the terminal C1603 described in the MMP frame 1604 as with the terminal B1602, and the transmission / reception state management unit 108 of the terminal C1603 uses the offset period. Set 1607 timer. Thereafter, the transmission data Data5-A, Data6-A, Data7-A, and Data8-A addressed to the terminal C1603 in the HTP Burst frame 1611 are received, and a BlockAck frame is created. When the timer of the offset period 1609 for the terminal C1603 expired by the transmission / reception state management unit 108 of the terminal C1603 expires, the TXOP time 1610 to be given to the terminal C1603 is reached, and the terminal C1603 creates the BlockAck frame 1614 and the RIFS of the BlockAck frame 1614 The HTP Burst frame 1615 obtained by aggregating the transmission data Data1-C, Data2-C, Data3-C, and Data4-C for the terminal A1601 is created, transmitted to the terminal A1601, and the HTP Burst frame 1615 is transmitted. After the SIFS, the BlockAck frame 1616 from the terminal A 1601 is received, and the bidirectional communication period 1605 starting from the MMP frame 1614 ends.

  However, the TXOP time 1610 given to the terminal C 1603 starts after the TXOP time 1608 given to the terminal B 1602 ends.

  As shown in FIG. 25, when the number of data accumulated in the transmission queue of the terminal B 1602 is small and the terminal B 1602 cannot use all the TXOP time 1608 given to the terminal B 1602, the terminal A 1601 that gives the TXOP time separately is As in the other embodiments, if one PHY frame is received after the RIFS that received the BlockAck frame to indicate that the communication for the given TXOP time is completed, the remaining TXOP time is set to the terminal A1601. May be used for data transmission to other terminals. However, when the extra TXOP time is used, it is a period up to the start time of the TXOP time 1610 given to the terminal C1603.

  As described above, by using the communication method according to the present embodiment, it is possible to improve the arrival probability of a BlockAck frame over transmission data in a communication method using a multi-pole frame that assigns a transmission period to a plurality of terminals at once. it can. Further, by transmitting the BlockAck frame using a PHY frame different from the transmission data, it becomes possible to notify the band reservation period again using the BlockAck frame. In addition, by describing the period of time that the terminal to which the TXOP is assigned in the BlockAck frame is used, it is possible to notify the period in which the terminal to which the TXOP is assigned is not used. Can be used.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. In addition, various inventions can be formed by appropriately combining a plurality of components disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

1 is a block diagram of a wireless communication apparatus according to a first embodiment. 3 is a timing chart according to the first embodiment. The flowchart which concerns on operation | movement of the terminal A of 1st Embodiment. The flowchart which concerns on operation | movement of the terminal B of 1st Embodiment. The figure which shows the positional relationship of the terminal of 1st Embodiment. The block diagram of the radio | wireless communication apparatus which concerns on the modification 2 of 1st Embodiment. The flowchart which concerns on operation | movement of the terminal A to the modification 2 of 1st Embodiment. The flowchart which concerns on operation | movement of the terminal B to the modification 2 of 1st Embodiment. The block diagram of the radio | wireless communication apparatus which concerns on the modification 3 of 1st Embodiment. The flowchart which concerns on operation | movement of the terminal A to the modification 3 of 1st Embodiment. The flowchart which concerns on operation | movement of the terminal B to the modification 3 of 1st Embodiment. The timing chart which concerns on the modification 4 of 1st Embodiment. The timing chart which concerns on 2nd Embodiment. The timing chart which concerns on 3rd Embodiment. The flowchart which concerns on operation | movement of the terminal B of 4th Embodiment. The figure which shows the positional relationship of the terminal of 4th Embodiment. 10 is a timing chart according to the fifth embodiment. The flowchart which concerns on operation | movement of the terminal A of 5th Embodiment. The flowchart which concerns on operation | movement of the terminal B of 5th Embodiment. The timing chart which concerns on 6th Embodiment. The flowchart which concerns on operation | movement of the terminal A of 6th Embodiment. The timing chart which concerns on 7th Embodiment. The figure which shows the flame | frame structure of 10th Embodiment. The timing chart which concerns on 11th Embodiment. The timing chart which concerns on 12th Embodiment.

Explanation of symbols

101 ... Wireless communication device, 102 ... Transmission data management unit, 103 ...
Access control unit 104 ... Frame generation / transmission unit 105 ... Reception processing unit 106 ... Transmission queue 107 ... Transmission / reception method determination unit 108 ... Transmission / reception state management unit 109 ... -Career sense part.

Claims (22)

  1. In a wireless communication device that is given a distribution period from an initiator and performs bidirectional communication with the initiator,
    Generating means for generating a first physical frame including a delivery confirmation frame for a plurality of data frames received from the initiator and a second physical frame in which a plurality of transmission data frames destined for the initiator are aggregated;
    During the distribution period, the first physical frame is transmitted at a first transmission rate, and the second physical rate is transmitted at a second transmission rate after a certain period of time has elapsed since the transmission of the first physical frame. A transmission means for transmitting a frame;
    Means for receiving a delivery confirmation request frame following data from the initiator, wherein the delivery confirmation request frame is transmitted at a transmission rate lower than the transmission rate of the data.
  2. The radio communication apparatus according to claim 1, wherein the first physical frame and the second physical frame are separated by a RIFS (Reduced Interframe Space).
  3. The wireless communication apparatus according to claim 1, further comprising means for executing an RTS-CTS frame exchange, wherein the bidirectional communication is started after the RTS-CTS exchange.
  4. Means for detecting that the two-way communication has started;
    2. The wireless communication apparatus according to claim 1, further comprising: a unit that waits for two physical frames to be transmitted with a RIFS (Reduced Interframe Space) time between when the start of the bidirectional communication is detected.
  5. Means for extending a first NAV (network allocation vector) to a second NAV during a TXOP (Transmission Opportunity) period, wherein the first physical frame includes the value of the second NAV; A terminal that transmits at a transmission rate lower than that of the second physical frame and supports the lower transmission rate can receive the first physical frame, and sets a third NAV based on the value of the second NAV. The wireless communication apparatus according to claim 1, wherein the wireless communication apparatus can be set.
  6. 6. The wireless communication according to claim 5, wherein the value represents a period length necessary for transmission of transmission data addressed to the initiator and reception of a delivery confirmation frame sent from the initiator with respect to the transmission data. apparatus.
  7. The initiator includes means for extending the first NAV to the fourth NAV during the TXOP period by transmitting a third physical frame including a value of the fourth NAV, and the legacy terminal 6. The wireless communication apparatus according to claim 5, wherein the third NAV can be set based on both the value of the fourth NAV and the value of the second NAV.
  8. In the first physical frame, a period length necessary for transmission of transmission data addressed to the initiator and reception of a delivery confirmation frame sent from the initiator with respect to the transmission data is set as a value of NAV (network allocation vector). The wireless communication apparatus according to claim 1, further comprising: a duration field that indicates a duration that is shorter than the dispensing time.
  9. The wireless communication apparatus according to claim 1, further comprising means for transmitting a null frame for notifying that there is no transmission data addressed to the initiator after transmission of the first physical frame during the distribution period.
  10. In a wireless communication method in which a distribution period is given from an initiator and bidirectional communication is performed with the initiator,
    Generating a first physical frame including a delivery confirmation frame for a plurality of data frames received from the initiator and a second physical frame in which a plurality of transmission data frames destined for the initiator are aggregated;
    During the distribution period, the first physical frame is transmitted at a first transmission rate, and the second physical rate is transmitted at a second transmission rate after a certain period of time has elapsed since the transmission of the first physical frame. A transmission step of transmitting a frame;
    Receiving a delivery confirmation request frame following data from the initiator, wherein the delivery confirmation request frame is transmitted at a transmission rate lower than the transmission rate of the data.
  11. The wireless communication method according to claim 10, wherein the first physical frame and the second physical frame are separated by a RIFS (Reduced Interface Space).
  12. The wireless communication method according to claim 10, further comprising a step of performing an RTS-CTS frame exchange, wherein the bidirectional communication is started after the RTS-CTS exchange.
  13. Detecting that the bidirectional communication has started;
    The wireless communication method according to claim 10, further comprising a step of waiting for two physical frames to be transmitted with a RIFS (Reduced Interframe Space) time between when the start of the bidirectional communication is detected.
  14. The method further comprises extending a first NAV (network allocation vector) to a second NAV during a TXOP (Transmission Opportunity) period, wherein the first physical frame includes the value of the second NAV. A terminal that transmits at a transmission rate lower than that of the second physical frame and supports the lower transmission rate can receive the first physical frame, and sets a third NAV based on the value of the second NAV. The wireless communication method according to claim 10, wherein the wireless communication method can be set.
  15. The wireless communication according to claim 14, wherein the value represents a period length necessary for transmission of transmission data addressed to the initiator and reception of a delivery confirmation frame sent from the initiator for the transmission data. Method.
  16. The initiator includes a step of extending the first NAV to the fourth NAV during the TXOP period by transmitting a third physical frame including a value of the fourth NAV; 15. The wireless communication method according to claim 14, wherein the third NAV can be set based on both the value of the fourth NAV and the value of the second NAV.
  17. In the first physical frame, a period length necessary for transmission of transmission data addressed to the initiator and reception of a delivery confirmation frame sent from the initiator with respect to the transmission data is set as a value of NAV (network allocation vector). The wireless communication method according to claim 10, further comprising: a duration field that indicates a duration length shorter than the dispensing time.
  18. The wireless communication method according to claim 10, further comprising a step of transmitting a null frame for notifying that there is no transmission data addressed to the initiator after transmission of the first physical frame during the distribution period.
  19. In a wireless communication device that gives a distribution period to a responder and performs bidirectional communication with the responder,
    Generating means for generating a first physical frame including an acknowledgment frame for a plurality of data frames received from the responder and a second physical frame in which a plurality of transmission data frames destined for the responder are aggregated;
    Transmitting means for transmitting the first physical frame at a first transmission rate, and transmitting the second physical frame at a second transmission rate after a predetermined period of time has elapsed since the transmission of the first physical frame. ,
    Means for receiving a delivery confirmation request frame following data from the responder, wherein the delivery confirmation request frame is transmitted at a transmission rate lower than the transmission rate of the data.
  20. In a wireless communication method for giving a distribution period to a responder and performing bidirectional communication with the responder,
    Generating a first physical frame including an acknowledgment frame for a plurality of data frames received from the responder and a second physical frame in which a plurality of transmission data frames destined for the responder are aggregated;
    A transmission step of transmitting the first physical frame at a first transmission rate, and transmitting the second physical frame at a second transmission rate after a predetermined period has elapsed from the transmission time of the first physical frame; ,
    Receiving a delivery confirmation request frame following the data from the responder, wherein the delivery confirmation request frame is transmitted at a transmission rate lower than the transmission rate of the data.
  21. In a wireless communication device that gives a distribution period to a responder and performs bidirectional communication with the responder,
    Means for transmitting a first physical frame aggregated with a plurality of data to the responder;
    Means for receiving a second physical frame including an acknowledgment frame for the data, wherein the second NAV (network allocation vector) is extended by the second NAV during a transmission permission period;
    And a means for controlling the value of the distribution period so that the value of the second NAV falls within the transmission permission period limit.
  22. In a wireless communication device that gives a distribution period to a responder and performs bidirectional communication with the responder,
    Means for transmitting a first physical frame aggregated with a plurality of data to the responder;
    Means for receiving a second physical frame including an acknowledgment frame for the data, wherein the second NAV (network allocation vector) is extended by the second NAV during a transmission permission period;
    Means for extending the first NAV by a third NAV by transmitting a third physical frame including a second acknowledgment frame for data from the responder to the first NAV. Wireless communication device.
JP2006127110A 2006-04-28 2006-04-28 Wireless communication device Active JP4364210B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2006127110A JP4364210B2 (en) 2006-04-28 2006-04-28 Wireless communication device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2006127110A JP4364210B2 (en) 2006-04-28 2006-04-28 Wireless communication device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
JP2005178584 Division

Publications (3)

Publication Number Publication Date
JP2006352844A5 JP2006352844A5 (en) 2006-12-28
JP2006352844A true JP2006352844A (en) 2006-12-28
JP4364210B2 JP4364210B2 (en) 2009-11-11

Family

ID=37648133

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2006127110A Active JP4364210B2 (en) 2006-04-28 2006-04-28 Wireless communication device

Country Status (1)

Country Link
JP (1) JP4364210B2 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008306419A (en) * 2007-06-07 2008-12-18 Sony Corp Transmission device and method, and program
JP2009060213A (en) * 2007-08-30 2009-03-19 Sony Corp Wireless communication device, wireless communication system, wireless communication method and program
JP2011525085A (en) * 2008-06-18 2011-09-08 エルジー エレクトロニクス インコーポレイティド Channel connection method in VHT wireless LAN system and station supporting the same
US8089868B2 (en) 2007-10-05 2012-01-03 Kabushiki Kaisha Toshiba Wireless communication apparatus and wireless communication method using variable transmission rate
JP2012501102A (en) * 2008-08-20 2012-01-12 クゥアルコム・インコーポレイテッドQualcomm Incorporated Power and resource efficient aggregated physical layer PDU based approach with scheduled block acknowledgment for WLAN
JP2016540434A (en) * 2013-11-27 2016-12-22 クゥアルコム・インコーポレイテッドQualcomm Incorporated System and method for multicast communication in a wireless network

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8861490B2 (en) 2007-06-07 2014-10-14 Sony Corporation Transmission device, transmission method, and computer-readable medium
JP2008306419A (en) * 2007-06-07 2008-12-18 Sony Corp Transmission device and method, and program
JP2009060213A (en) * 2007-08-30 2009-03-19 Sony Corp Wireless communication device, wireless communication system, wireless communication method and program
US8089868B2 (en) 2007-10-05 2012-01-03 Kabushiki Kaisha Toshiba Wireless communication apparatus and wireless communication method using variable transmission rate
JP2011525085A (en) * 2008-06-18 2011-09-08 エルジー エレクトロニクス インコーポレイティド Channel connection method in VHT wireless LAN system and station supporting the same
US9788346B2 (en) 2008-06-18 2017-10-10 Lg Electronics Inc. Channel access method for very high throughput (VHT) wireless local access network system and station supporting the channel access method
US8989158B2 (en) 2008-06-18 2015-03-24 Lg Electronics Inc. Channel access method for very high throughput (VHT) wireless local access network system and station supporting the channel access method
US9107222B2 (en) 2008-06-18 2015-08-11 Lg Electronics Inc. Channel access method for very high throughput (VHT) wireless local access network system and station supporting the channel access method
US9526114B2 (en) 2008-06-18 2016-12-20 Lg Electronics Inc. Channel access method for very high throughput (VHT) wireless local access network system and station supporting the channel access method
US10499431B2 (en) 2008-06-18 2019-12-03 Lg Electronics Inc. Channel access method for very high throughput (VHT) wireless local access network system and station supporting the channel access method
JP2012501102A (en) * 2008-08-20 2012-01-12 クゥアルコム・インコーポレイテッドQualcomm Incorporated Power and resource efficient aggregated physical layer PDU based approach with scheduled block acknowledgment for WLAN
US8730878B2 (en) 2008-08-20 2014-05-20 Qualcomm Incorporated Power and resource efficient APPDU based approach with scheduled block ACKS for WLAN
JP2016540434A (en) * 2013-11-27 2016-12-22 クゥアルコム・インコーポレイテッドQualcomm Incorporated System and method for multicast communication in a wireless network

Also Published As

Publication number Publication date
JP4364210B2 (en) 2009-11-11

Similar Documents

Publication Publication Date Title
Ji et al. Exploiting medium access diversity in rate adaptive wireless LANs
Balasubramanian et al. Interactive wifi connectivity for moving vehicles
KR100728039B1 (en) Method and apparatus for forwarding control frame to hidden node in wlan
JP5637988B2 (en) Apparatus for requesting and transmitting multicast data acknowledgment in a wireless local area network
USRE43705E1 (en) Method and system for optimally serving stations on wireless LANs using a controlled contention/resource reservation protocol of the IEEE 802.11E standard
EP1690352B1 (en) Wireless communication system, wireless communication device and wireless communication method, and computer program
CN2852545Y (en) Control system for accessing wireless communication medium
US8274992B2 (en) Communication method for wireless lans
EP1735932B1 (en) Multiple receiver aggregation
ES2419662T3 (en) High speed media access control
CN101222299B (en) Relay apparatus and method for relaying a data packet
Shi et al. Starvation mitigation through multi-channel coordination in CSMA multi-hop wireless networks
US8284753B2 (en) Wireless communication apparatus and wireless communication method
JP4981840B2 (en) Fast media access control and direct link protocol
JP4152322B2 (en) Apparatus and method for establishing recovery and backoff rules for an IEEE 802.11e hybrid coordinator
US8155013B2 (en) Synchronized multi-link transmission in an ARQ-enabled multi-hop wireless network
JP2007509532A (en) High-speed medium access control with existing system interoperability
JP2007531410A (en) Method and apparatus for ad hoc wireless communication system
JP2005510130A6 (en) Apparatus and method for establishing recovery and backoff rules for an IEEE 802.11e hybrid coordinator
US8175003B2 (en) Cooperative wireless communications
US7756089B2 (en) Fair rate allocation on an IEEE 802.11e communication medium
JP4047836B2 (en) Communication device, communication system, communication method, and communication control program
JP4561630B2 (en) Communication method, communication device, and computer program
US20040105412A1 (en) Point coordinator control passing scheme using a scheduling information parameter set for an IEEE 802.11 wireless local area network
JP4005974B2 (en) Communication device, communication method, and communication system

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20080613

A521 Written amendment

Effective date: 20090327

Free format text: JAPANESE INTERMEDIATE CODE: A523

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20090421

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20090617

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20090728

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20090818

FPAY Renewal fee payment (prs date is renewal date of database)

Free format text: PAYMENT UNTIL: 20120828

Year of fee payment: 3

FPAY Renewal fee payment (prs date is renewal date of database)

Year of fee payment: 3

Free format text: PAYMENT UNTIL: 20120828

FPAY Renewal fee payment (prs date is renewal date of database)

Year of fee payment: 4

Free format text: PAYMENT UNTIL: 20130828