WO2015035558A1

WO2015035558A1 - Hybrid automatic repeat request method, apparatus, and system

Info

Publication number: WO2015035558A1
Application number: PCT/CN2013/083225
Authority: WO
Inventors: 倪锐; 罗毅; 刘亚林
Original assignee: 华为技术有限公司
Priority date: 2013-09-10
Filing date: 2013-09-10
Publication date: 2015-03-19
Also published as: CN105453472A; CN105453472B

Abstract

Disclosed are a hybrid automatic repeat request method, apparatus, and system, applied to the field of communications, so as to solve the problem of collision of data of multiple users in hybrid automatic repeat request (HARQ) caused by channel sharing in the prior art. The method comprises: a transmit end sending an HARQ capability negotiation request packet; receiving an HARQ capability negotiation response packet fed back by a receive end, determining, according to the HARQ capability negotiation response packet, whether the receive end supports HARQ, and if the receive end supports HARQ, allocating an HARQ session identifier to the receive end; obtaining a channel use right of sending an HARQ data packet, and sending an HARQ data packet to the receive end through a channel according to the HARQ session identifier; and the transmit end receiving a response packet fed back by the receive end, and according to the response packet, determining that the data packet is successfully sent or determining to perform a retransmission operation according to a preset rule. Embodiments of the present invention are applied to the HARQ technology.

Description

The present invention relates to the field of communications, and in particular, to a hybrid automatic repeat request method, apparatus and system. Background technique

Hybrid Automatic Repeat Request (HARQ) is a hybrid of Forward Error Correction Coding (FEC) and Automatic Repeat Request (ARQ). The codeword sent by the sender can not only check the error, but also has certain error correction capability. The Wireless Fidelity (WiFi) communication system uses the Automatic Repeat Request (ARQ) method. The transmitting terminal sends a codeword with certain error correction capability. If the receiving end of the codeword is successful, the receiving end sends an Acknowledgement (ACK) to the transmitting end; if the receiving of the codeword fails, the receiving end does not make any feedback. If the sender does not receive the success acknowledgment signal ACK from the receiver within the specified time, the codeword is retransmitted. In the WiFi communication system, the retransmission codeword of the transmitting end is the same as the original codeword, and the receiving end does not perform any combination and directly decodes. The reason why the receiving end fails to decode may be wireless channel fading, or it may be that the signals of multiple communication devices collide on the shared communication channel. Since there may be multiple senders on the shared channel at the same time, if the decoding of the receiver fails, ^ [艮 may not correctly know the sender information of the failed codeword.

Since the decoding failure of the WiFi communication system is complicated, and it is difficult to correctly acquire the sender information when the decoding fails, HARQ has not been applied to the WiFi communication system until now.

The prior art discloses a method of operating HARQ in a WLAN system. The WLAN system in the method refers to a wireless local area network communication system composed of a WiFi communication device. The method introduces a new HARQ sublayer between the MAC layer (media access layer) and the PHY layer (physical layer) of the WLAN protocol. The HARQ sublayer is responsible for performing HARQ capability negotiation, HARQ state machine maintenance, HARQ session identification (ID) allocation, HARQ codec policy selection, receiving duplicate data packet check, and receiving from the PHY. The data packets of the layer are decoded and submitted to the MAC layer, the data packets that fail to be decoded are buffered, the data packets that are successfully decoded are removed from the buffer, and the header of the HARQ layer is added and parsed. Through this HARQ sublayer, the patent can behave like a wireless cellular communication system. HARQ is implemented in the case where the decoding fails due to wireless channel fading. Although this patent introduces HARQ technology into the WiFi communication system, there is a problem of multi-user collision of the shared channel, and thus the HARQ gain effect is poor.

SUMMARY OF THE INVENTION Embodiments of the present invention provide a hybrid automatic repeat request method, apparatus, and system to solve the problem of multi-user data collision in a shared channel in the prior art. A first aspect of the present invention provides a hybrid automatic repeat request method, including: a sending end sends a hybrid automatic repeat request HARQ capability negotiation request message to a receiving end; and the sending end receives a HARQ capability negotiation fed back by the receiving end And responding to the HARQ capability negotiation response packet, determining whether the receiving end supports HARQ, and if yes, assigning a HARQ session identifier to the receiving end; acquiring a channel usage right for transmitting the HARQ data packet, and according to The HARQ session identifier sends a HARQ data packet to the receiving end by using the channel; the sending end receives the response packet fed back by the receiving end, and determines, according to the response packet, that the data packet is sent successfully or according to the The preset rule performs a retransmission operation. With reference to the first aspect, in a first possible implementation manner, before the acquiring a channel usage right for transmitting a HARQ data packet, the method further includes: generating a mapping relationship between the sending end and the HARQ session identifier, And sending, to the receiving end, a configuration request message that includes the mapping relationship; and the sending end receives the configuration request response message sent by the receiving end. With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the generating a mapping relationship between the sending end and the HARQ session identifier includes: sending, by the sending end, the HARQ The capability negotiation response message determines whether the receiving end supports orthogonal frequency division multiplexing multiple access OFDMA, and if so, establishes a mapping relationship between the subchannel of the OFDMA of the transmitting end and the HARQ session identifier. With reference to the first possible implementation manner of the first aspect, in a third possible implementation manner, the generating a mapping relationship between the sending end and the HARQ session identifier includes: The transmitting end allocates a corresponding special codeword for the HARQ session, and forms a mapping relationship between the HARQ session identifier and the special codeword, where the special codeword is used to mark the sending end. With reference to the first aspect, in a fourth possible implementation, the acquiring the channel usage right of the sending the HARQ data packet includes: sending, by the sending end, the request to access the RTS frame request in the channel that sends the HARQ data packet The right to use the channel, where the RTS frame includes the HARQ session identifier, a media access layer MAC address of the sending end, and a usage time of the channel; the sending end receives the receiving end according to the The RTS frame feedback clears the CTS frame, and the CTS frame is used to confirm that the sending end acquires the right to use the channel for sending the HARQ data packet, where the CTS frame includes the MAC address of the receiving end and the corresponding The time of use of the channel. With reference to the first aspect, in a fifth possible implementation manner, the sending end sends a hybrid automatic retransmission request (HARQ capability negotiation request) message to the receiving end, and the method further includes: sending, by the sending end, the hybrid automatic retransmission request HARQ capability After the request message is negotiated, the sending end starts a local timer; if the sending end does not receive the HARQ capability negotiation response message of the receiving end, the transmitting end resends the The HARQ capability negotiates the request message and increments the number of retransmissions by one; if the number of retransmissions exceeds the preset value, the HARQ is discarded. With reference to the first aspect, in a sixth possible implementation, the channel for sending the HARQ data packet includes: a carrier sense multiple access/collision avoidance CSMA/CA shared channel; or

OFDMA subchannel. With reference to the sixth possible implementation manner of the first aspect, in a seventh possible implementation manner, the channel is a carrier sense multi-point access/collision avoiding usage right of a CSMA/CA shared channel, where the basis is And the sending, by the HARQ session identifier, the HARQ data packet to the receiving end by using the channel, if: the length of the HARQ data packet is less than the packet length threshold, and then adopting the DATA/ACK mode according to the HARQ session identifier. The CSMA/CA shared channel channel Sending a HARQ data packet to the receiving end; or if the length of the HARQ data packet is greater than or equal to the packet length threshold, passing the CSMA/CA shared channel channel according to the HARQ session identifier in an RTS/CTS manner. Sending a HARQ data packet to the receiving end. With the fourth possible implementation of the first aspect, in an eighth possible implementation, the sending the HARQ data to the receiving end by using the channel according to the HARQ session identifier further includes: The HARQ data packet whose length is greater than or equal to the packet length threshold is sent by the HARQ, and the HARQ data packet whose length is less than the packet length threshold is sent by the ARQ. With the third possible implementation of the first aspect, in a ninth possible implementation manner, the sending, by using the channel, the HARQ data packet to the receiving end according to the HARQ session identifier includes: The sender encodes the source data;

Obtaining a special codeword corresponding to the HARQ session identifier; adding a HARQ header to the encoded data; and inserting the special codeword into the data after adding the HARQ header;

The data in which the special codeword is inserted is transmitted as a HARQ data message to the receiving end through the channel. With reference to the ninth possible implementation manner of the first aspect, in the tenth possible implementation manner, the inserting the special codeword into the data of adding the HARQ header includes: inserting the special codeword into the data that adds the HARQ header Mark between signal domain and data field; or,

Backing up the special codeword, inserting the special codeword into the physical layer convergence preamble domain PLCP

The first field of the Preamble, the special codeword backup is inserted into the second domain of the PLCP Preamble.

With reference to the first aspect, in an eleventh possible implementation, the sending the HARQ data packet to the receiving end by using the channel according to the HARQ session identifier includes: The transmitting end encodes source data;

Adding a HARQ header to the encoded data; transmitting the HARQ header-added data as a HARQ data packet to the receiving end through the channel. With reference to the first aspect, in a twelfth possible implementation manner, the sending end receives the response packet that is sent by the receiving end, and determines, according to the response packet, that the data packet is successfully sent or is executed according to a preset rule. The retransmission operation includes: if the ACK feedback of the receiving end is received, determining that the data packet is successfully sent; or if receiving the first NAK feedback of the receiving end, increasing the transmit power retransmission and the current HARQ datagram The same data; or if the second NAK feedback of the receiving end is received, the same data as the HARQ data message is sent; or the self-decodeable redundant data different from the HARQ data message; or The non-self-decodable redundant data different from the HARQ data message; or if the feedback is not received, the same data as the current HARQ data message is retransmitted with the constant transmit power. With reference to the twelfth possible implementation manner of the foregoing aspect, in a thirteenth possible implementation manner, if the ACK feedback of the receiving end is received, determining that the data packet is successfully sent, the method further includes: clearing Transmitting the HARQ data packet buffered by the sending end; if the service stream of the sending end does not need to send a new data packet, sending a HARQ session ending message to the receiving end; otherwise, continuing to use the HARQ session The receiving end sends a subsequent data packet. With the first to the thirteenth possible implementation manners of the first aspect, in the fourteenth possible implementation manner, before the sending end receives the response message fed back by the receiving end, the sending end further includes: Sending, by the sending end, a cooperation request to the auxiliary sending end, where the cooperation request includes the HARQ session identifier; The redundant data packet of the HARQ data packet; the sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to a preset rule, including The sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data message is successfully sent or performs a retransmission operation by using the auxiliary sending end according to a preset rule.

With reference to the fourteenth possible implementation manner of the first aspect, in a fifteenth possible implementation manner, the sending end receives the response message fed back by the receiving end, and determines the data packet according to the response message The text is sent successfully, including:

The sending end receives the response message fed back by the receiving end, and the response message is an ACK;

A redundant data message of the HARQ data packet;

If no new data message needs to be sent in the service flow of the sender, the HARQ session end message is sent to the receiving end. With reference to the fourteenth possible implementation manner of the first aspect, in a fifteenth possible implementation manner, the sending end receives the response message fed back by the receiving end, according to the response message, according to the preset And the sending, by the sending end, the retransmission operation, where the sending end receives the response message fed back by the receiving end, where the response message is a retransmitted HARQ data message; The preset rule notifies the auxiliary transmitting end to perform a retransmission operation. A second aspect of the present invention provides a hybrid automatic repeat request method, including: receiving, by a receiving end, a HARQ capability negotiation response message to a transmitting end; and receiving, by the receiving end, a HARQ session identifier allocated by the sending end;

The receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and feeds back the response packet to the sending end according to the HARQ data packet.

With reference to the second aspect, in a first possible implementation manner, the receiving end acquires the HARQ session identifier that is allocated by the sending end, and includes: Receiving, by the receiving end, the configuration request message sent by the sending end, where the configuration request includes a mapping relationship between the sending end and the HARQ session identifier;

The receiving end sends a HARQ configuration response message to the sending end.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation, the mapping relationship between the sending end and the HARQ session identifier is: between the HARQ session identifier and the special codeword Mapping relationship.

With reference to the first possible implementation manner of the second aspect, in a third possible implementation, the mapping relationship between the sending end and the HARQ session identifier is: the subchannel of the OFDMA of the sending end and the The HARQ session identifier establishes a mapping relationship.

With reference to the second aspect, in a fourth possible implementation manner, before the receiving end receives the HARQ data sent by the sending end according to the HARQ session identifier, the receiving end further includes: the receiving end is configured to send the HARQ Acquiring an RTS frame in the channel of the data packet; and feeding back a CTS frame to the sending end according to the RTS frame, where the CTS frame is used to confirm that the sending end acquires the right to use the channel for sending the HARQ data packet, where The CTS frame includes a MAC address of the receiving end and a usage time of the channel.

With the second possible implementation of the second aspect, in a fifth possible implementation manner, the receiving end, according to the HARQ session identifier, is configured to receive the HARQ data packet sent by the sending end, and further includes:

And acquiring a pilot sequence in the HARQ data packet, and obtaining a coded modulation mode and a HARQ data message length in the HARQ data packet; demodulating and decoding the HARQ data packet; and performing the decoded data Frame check sequence FCS check.

With the third possible implementation of the second aspect, in a sixth possible implementation, the receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and further includes: Frequency sequence

Obtaining a coded modulation mode and a HARQ data message length; And mapping the HARQ data identifier to the HARQ session identifier and the service flow according to the OFDMA subchannel information; demodulating and decoding the HARQ data packet; and performing the frame check sequence FCS check on the decoded data.

With reference to the fourth possible implementation manner of the second aspect, in a seventh possible implementation manner, the receiving end, according to the HARQ session identifier, receiving the HARQ data packet sent by the sending end, further includes:

Capture pilot sequence;

Obtaining a coded modulation mode and a HARQ data packet length;

And if the RTS frame is received and the CTS frame is replied, the received HARQ data packet is mapped to the HARQ session identifier and the service flow; the HARQ data packet is demodulated and decoded; The data is subjected to a frame check sequence FCS check.

With the fifth possible implementation of the second aspect, in an eighth possible implementation, the sending the response message to the sending end according to the HARQ data packet includes: acquiring a special from the HARQ data packet a codeword, and mapping the HARQ data to the HARQ session identifier and the service flow according to the special codeword;

If the FCS check passes, the ACK is fed back to the sending end; or, if the special codeword identification passes, the FCS check fails, the second NAK is fed back to the sending end; or, if the special code If the word recognition fails, the FCS check fails, and the second NAK is fed back to the transmitting end when the RTS/CTS mode or the OFDMA mode is received; or

If the special codeword identification does not pass, the FCS check fails, and in the DATA/ACK mode, no information is fed back to the transmitting end; or,

If the acquisition pilot sequence fails, in the DATA/ACK mode, no information is fed back to the sender; or,

If the acquisition pilot sequence fails, in RTS/CTS mode or OFDMA mode, then The sender feeds back the first NAK:.

With reference to the sixth possible implementation of the second aspect, in a ninth possible implementation manner, the sending, by the FAR, the response message to the sending end according to the HARQ data packet includes: if the FCS check passes And feeding back an ACK to the sending end; or, if the FCS check fails, feeding back a second NAK to the sending end;

With reference to the seventh possible implementation manner of the second aspect, in a tenth possible implementation manner, the feeding back the response message to the sending end according to the HARQ data packet includes: if the FCS check passes And feeding back an ACK to the sending end; or, if the FCS check fails, in the RTS/CTS mode, feeding back the second NAK to the transmitting end; or, if the FCS check fails, not RTS/ In the CTS mode, no information is fed back to the sender.

With reference to any one of the eighth to the tenth possible implementation manners of the second aspect, in the eleventh possible implementation manner, after the feeding back the second NAK to the sending end, the method further includes: buffering the current HARQ Data message.

With reference to any one of the eighth to the tenth possible implementation manners of the second aspect, in the twelfth possible implementation manner, after the feedback message is sent back to the sending end according to the result of the checking, The method includes: receiving, by the receiving end, HARQ retransmission data sent by the sending end; and decoding the HARQ retransmission data.

With the possible implementation of the twelfth aspect of the second aspect, in the thirteenth possible implementation manner, the decoding, by the HARQ retransmission data, includes: decoding the HARQ retransmission data; or The HARQ retransmission data and the buffered current HARQ data message are combined and decoded.

With reference to the second aspect, in a fourteenth possible implementation manner, after the sending the response message to the sending end according to the result of the checking, the method further includes: The receiving end receives the HARQ session end message sent by the sending end, and clears the HARQ data message and the HARQ session identifier corresponding to the HARQ session. The third aspect provides a sending end, including: a sending unit, configured to send a hybrid automatic repeat request HARQ capability negotiation request message to the receiving end;

a receiving unit, configured to receive a HARQ capability negotiation response message fed back by the receiving end, determine, according to the HARQ capability negotiation response message, whether the receiving end supports HARQ, and if supported, allocate a HARQ session to the receiving end Identification

The sending unit is further configured to: obtain a channel usage right for transmitting a HARQ data packet, and send a HARQ data packet to the receiving end by using the channel according to the HARQ session identifier;

The receiving unit is further configured to: receive, by the sending end, a response message that is fed back by the receiving end, and determine, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to a preset rule.

With reference to the third aspect, in a first possible implementation, the receiving end further includes a mapping unit,

And sending, by the sending unit, a configuration request message that includes the mapping relationship to the receiving end;

The receiving unit is configured to receive a configuration request response message sent by the receiving end.

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner, the mapping unit is specifically configured to determine, according to the HARQ capability negotiation response packet, whether the receiving end supports orthogonal frequency division The multiplexed multiple access OFDMA, if supported, establishes a mapping relationship between the subchannel of the OFDMA of the transmitting end and the HARQ session identifier.

With reference to the first possible implementation manner of the third aspect, in a third possible implementation, the mapping unit is specifically configured to allocate a corresponding special codeword for the HARQ session, and form the HARQ session identifier and the A mapping relationship between special code words for marking the transmitting end. With reference to the third aspect, in a fourth possible implementation, the sending unit is specifically configured to request a right to use the channel by marking a request to send an RTS frame in a channel for sending a HARQ data packet, where the RTS frame And including the HARQ session identifier, a media access layer MAC address of the sending end, and a usage time of the channel; the receiving unit is further configured to receive, by the receiving end, a CTS frame sent according to the clearing of the RTS frame feedback. The CTS frame is used to confirm that the sending end acquires the right to use the channel for sending the HARQ data packet, where the CTS frame includes the MAC address of the receiving end and the usage time of the channel. With the third aspect, in a fifth possible implementation manner, after the sending unit is further configured to send the hybrid automatic repeat request (HARQ capability negotiation request message), the sending end starts a local timer;

If the transmitting end does not receive the HARQ capability negotiation response message of the receiving end, the transmitting end resends the HARQ capability negotiation request message, and increases the number of retransmissions by one; If the number of retransmissions exceeds the preset value, the HARQ is abandoned.

With reference to the third aspect, in a sixth possible implementation, the channel for sending the HARQ data packet includes: a carrier sense multi-point access/collision avoidance CSMA/CA shared channel; or

OFDMA subchannel.

With reference to the sixth possible implementation manner of the third aspect, in a seventh possible implementation manner, if the channel is a carrier sense multi-point access/collision avoiding usage right of a CSMA/CA shared channel, the sending The unit is specifically configured to: if the length of the HARQ data packet is less than the packet length threshold, send the HARQ data packet to the receiving end by using the CSMA/CA shared channel channel according to the HARQ session identifier and using the DATA/ACK mode. Or the sending unit is specifically configured to: if the length of the HARQ data packet is greater than or equal to the packet length threshold, according to the HARQ session identifier, use the RTS/CTS manner to pass the CSMA/CA shared channel channel to the The receiving end sends a HARQ data packet.

With the fourth possible implementation of the third aspect, in an eighth possible implementation, the sending unit is further configured to:

Determining a packet length of the HARQ data packet; The HARQ data packet whose length is greater than or equal to the packet length threshold is sent by HARQ, and the HARQ data packet whose length is smaller than the packet length threshold is sent by ARQ.

In conjunction with the third possible implementation of the third aspect, in a ninth possible implementation, the sending unit includes:

a coding subunit, configured to: encode the source data; obtain a special codeword corresponding to the HARQ session identifier; add a HARQ header to the encoded data; insert the special codeword into the add HARQ header And a sending subunit, configured to send the data in which the special codeword is inserted as a HARQ data message to the receiving end through the channel. With reference to the ninth possible implementation manner of the third aspect, in a tenth possible implementation, the coding subunit is specifically configured to insert the special codeword into a tag signal field and a data domain of data added with a HARQ header Between; or,

The first domain of the PLCP Preamble of the preamble domain is merged into the physical layer, and the special codeword backup is inserted into the second domain of the PLCP Preamble. With reference to the third aspect, in an eleventh possible implementation manner, the sending unit includes: an encoding subunit, configured to encode source data; add a HARQ header to the encoded data; And transmitting, by using the HARQ data packet, the data that is added with the HARQ header to the receiving end by using the channel. With the third aspect, in a twelfth possible implementation manner, the receiving unit is specifically configured to: if the ACK feedback of the receiving end is received, determine that the data packet is successfully sent; or if the receiving end is received The first NAK feedback increases the transmit power to resend the same data as the current HARQ data message; or if the second NAK feedback of the receiving end is received, the same data as the HARQ data message is sent; or Redistributable redundant data different from the HARQ data message; or non-self-decodable redundant data different from the HARQ data message; or If no feedback is received, the same data as the current HARQ data message is retransmitted with constant transmit power.

In conjunction with the twelfth possible implementation of the third aspect, in a thirteenth possible implementation,

The receiving unit is further configured to: clear the HARQ data packet buffered by the sending end; if the service flow of the sending end does not need to send a new data packet, send the HARQ to the receiving end by using the sending unit. The session end message; otherwise, the sending unit continues to use the HARQ session to send subsequent data messages to the receiving end.

With reference to the third aspect or any possible implementation manner of the third aspect, in the fourteenth possible implementation manner,

Including the HARQ session identifier;

Corresponding to the redundant data packet of the HARQ data packet; the receiving unit is configured to receive the response packet fed back by the receiving end, and determine, according to the response packet, that the data packet is sent successfully or according to a preset rule A retransmission operation is performed by the auxiliary transmitting end.

In conjunction with the fourteenth possible implementation of the third aspect, in a fifteenth possible implementation,

The receiving unit includes: a receiving subunit, configured to receive a response message fed back by the receiving end, where the response message is an ACK, and a notification subunit, configured to notify the auxiliary sending end to delete the HARQ data packet And a redundant data packet corresponding to the HARQ data packet; if the service flow of the sender does not need to send a new data packet, sending a HARQ session end message to the receiving end.

With reference to the fourteenth possible implementation manner of the third aspect, in the sixteenth possible implementation manner, the receiving unit includes: a receiving subunit, configured to receive a response message fed back by the receiving end, where the response message is a retransmission HARQ data message, and a notification subunit, configured to receive, according to the response message received by the receiving subunit, Notifying the auxiliary transmitting end to perform a retransmission operation according to a preset rule.

A receiving end, comprising: a sending unit, configured to: feed back a HARQ capability negotiation response message to the sending end; an acquiring unit, configured to acquire a HARQ session identifier allocated by the sending end; and a receiving unit, configured to The HARQ session identifier receives the HARQ data packet sent by the sending end, and the sending unit is further configured to feed back the response packet to the sending end according to the HARQ data packet received by the receiving unit. With reference to the fourth aspect, in a first possible implementation manner, the acquiring unit is specifically configured to receive a configuration request packet that is sent by the sending end, where the configuration request packet includes the sending end and the HARQ The mapping relationship of the session identifiers; sending a HARQ configuration response message to the sending end. With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation, the mapping relationship between the sending end and the HARQ session identifier is: between the HARQ session identifier and the special codeword Mapping relationship. With reference to the first possible implementation manner of the fourth aspect, in a third possible implementation, the mapping relationship between the sending end and the HARQ session identifier is: the subchannel of the OFDMA of the sending end is The HARQ session identifier establishes a mapping relationship. In conjunction with the fourth aspect, in a fourth possible implementation,

frame; ' . . ,

The sending unit is further configured to feed back a CTS frame to the sending end according to the RTS frame, where the CTS frame is used to confirm that the sending end acquires a right to use the channel for sending the HARQ data packet, where the CTS The frame contains the MAC address of the receiving end and the time of use of the channel. With reference to the second possible implementation manner of the fourth aspect, in a fifth possible implementation manner,

Deriving the HARQ data packet to obtain a coded modulation mode and a HARQ data message length; demodulating and decoding the HARQ data message; and performing the frame check sequence FCS check on the decoded data. With reference to the third possible implementation manner of the fourth aspect, in a sixth possible implementation, the receiving unit is further configured to: acquire a pilot sequence; obtain a coded modulation mode and a HARQ data packet length; according to the OFDMA subchannel The information is used to map the HARQ data packet with the HARQ session identifier and the service flow; demodulate and decode the HARQ data packet; and perform the frame check sequence FCS check on the decoded data. With the fourth possible implementation of the fourth aspect, in a seventh possible implementation, the receiving unit is further configured to: acquire a pilot sequence; obtain a coded modulation mode and a length of a HARQ data packet; Deriving the RTS frame and replying to the CTS, and mapping the received HARQ data packet with the HARQ session identifier and the service flow; demodulating and decoding the HARQ data packet; and performing frame correction on the decoded data Check the sequence FCS check. With reference to the fifth possible implementation manner of the fourth aspect, in an eighth possible implementation, the sending unit is configured to obtain a special codeword from the HARQ data packet received by the receiving end, according to The special codeword establishes a mapping relationship between the HARQ data packet and the HARQ session identifier and the service flow; if the FCS check passes, feeds back an ACK to the sending end; or, if the special codeword is identified If the FCS check fails, the second NAK is fed back to the sending end; or, if the special codeword identification fails, the FCS check fails, and the RTS/CTS mode or the OFDMA mode is fed back to the sending end. a second NAK; or, if the special codeword identification does not pass, the FCS check fails, in the DATA/ACK mode, no information is fed back to the transmitting end; or, if the pilot sequence fails to be captured, the DATA/ACK mode Not feeding back any information to the sender; or, If the acquisition pilot sequence fails, in the RTS/CTS mode or the OFDMA mode, the first NAK is fed back to the transmitting end. With reference to the sixth possible implementation manner of the foregoing aspect, in a ninth possible implementation, the sending unit is specifically configured to: when the FCS check passes, feed back an ACK to the sending end; or In the tenth possible implementation manner, the sending unit is specifically used to: If the FCS check passes, the ACK is fed back to the sending end; or, if the FCS check fails, in the RTS/CTS mode, the second NAK is fed back to the sending end; or, if the FCS check fails, When it is not in the RTS/CTS mode, no information is fed back to the sender. With reference to any one of the possible implementations of the eighth to the tenth possible implementation manners of the fourth aspect, in the eleventh possible implementation manner, the receiving unit is further configured to cache the current HARQ data . With reference to any one of the possible implementations of the eighth to the tenth possible implementations of the fourth aspect, in a twelfth possible implementation, the receiving unit is further configured to receive the sending end HARQ retransmission data; decoding the HARQ retransmission data. With reference to the twelfth possible implementation manner of the fourth aspect, in the thirteenth possible implementation manner, the receiving unit is specifically configured to: decode the HARQ retransmission data; or

The HARQ retransmission data is buffered and the current HARQ data packet is buffered and then decoded.

With reference to the fourth aspect, in a fourteenth possible implementation manner, the receiving unit is further configured to receive a HARQ session end message sent by the sending end, and clear the HARQ data corresponding to the HARQ session. And HARQ session ID.

According to a fifth aspect, a communication system is provided, including a receiving end and a transmitting end that communicate with each other, wherein the transmitting end is any one of the sending ends described in the foregoing third aspect, and the receiving end is the foregoing Any of the receiving ends described in the fourth aspect. The hybrid automatic repeat request method, device, and system provided by the embodiment of the present invention establish a mapping relationship between the transmitting end and the HARQ session identifier by using the sending end, and send the HARQ data packet to the receiving end according to the HARQ session identifier, and the sending end receives the data according to the receiving end. The response message sent by the receiving end determines whether the data packet is sent successfully or performs a retransmission operation according to a preset rule, thereby avoiding the multi-user data collision problem of the HARQ in the shared channel, and improving the HARQ gain effect, and the applicable range widely. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. FIG. 1 is a schematic flowchart of a hybrid automatic repeat request method according to Embodiment 1 of the present invention; FIG. 2 is a schematic flowchart of another hybrid automatic repeat request method according to Embodiment 1 of the present invention; A schematic flowchart of a hybrid automatic repeat request method provided by Embodiment 2 of the present invention;

4 is a schematic diagram of inserting a special codeword according to Embodiment 2 of the present invention; FIG. 5 is a schematic diagram of still inserting a special codeword according to Embodiment 2 of the present invention; FIG. 6 is a third embodiment of the present invention; A schematic diagram of a flow of a hybrid automatic repeat request method provided;

7 is a schematic flow chart of a hybrid automatic repeat request method according to Embodiment 4 of the present invention;

8 is a schematic flow chart of a hybrid automatic repeat request method according to Embodiment 5 of the present invention;

9 is a schematic flow chart of a hybrid automatic repeat request method according to Embodiment 6 of the present invention;

10 is a schematic flowchart of a hybrid automatic repeat request method according to Embodiment 7 of the present invention; FIG. 11 is a schematic flowchart of a hybrid automatic repeat request method according to Embodiment 8 of the present invention;

FIG. 12 is a schematic structural diagram of a transmitting end according to an embodiment of the present invention; FIG. 13 is a schematic structural diagram of a transmitting end according to another embodiment of the present invention; FIG. 14 is a schematic diagram of another embodiment of the present invention. FIG. 15 is a schematic structural diagram of a transmitting end according to another embodiment of the present invention; FIG. 16 is a schematic structural diagram of a transmitting end according to another embodiment of the present invention; FIG. 18 is a schematic structural diagram of a transmitting end according to another embodiment of the present invention; FIG. 19 is a schematic structural diagram of a receiving end according to another embodiment of the present invention; A schematic structural diagram of a communication system provided by an embodiment of the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. In the embodiment of the present invention, the WiFi communication system can be either a Wireless Local Area Network (WLAN) or a Wireless Wide Area Network (WWAN) or a Wireless Personal Area Network (Wireless Personal Area Network). Referred to as WPAN). The embodiment of the present invention is applicable to the application of the HARQ in a WiFi communication system, and generally includes a transmitting end and a receiving end, wherein the transmitting end can generally be an access point in a WiFi communication system, such as an AP (Access Point, a wireless access node). Or an access point such as a wireless router, the receiving end is generally a mobile phone, a tablet computer or other computer. Embodiment 1 FIG. 1 is a schematic flowchart of a hybrid automatic repeat request method according to Embodiment 1 of the present invention. Referring to FIG. 1, the method may include the following steps: Step 10: The sending end sends a hybrid automatic repeat request HARQ capability to the receiving end. Negotiation Request a message. In the step 10, the MAC layer of the sending end knows that a new service flow needs to be sent to a receiving end, and a new traffic identifier (TID) is newly created. The MAC layer of the sender sends a HARQ capability negotiation request to the receiver, and the content of the message includes but is not limited to the following:

(1) Whether the receiving end supports HARQ;

(2) Whether the receiving end supports Orthogonal Frequency Division Multiplexing Access (OFDMDMA);

(3) the length of the message length;

(4) Whether the receiving end supports special code words. Specifically, (1) whether the receiving end supports HARQ refers to whether there is hardware and software processing capability supporting HARQ, that is, various HARQ capabilities referred to in the prior art; (2) whether the receiving end supports OFDMA, whether the receiving end has OFDMA or not (3) The packet length threshold is the value of the threshold used by the receiving end to determine the length of the long/short data packet. The length of the packet is greater than or equal to the length of the packet. For example, the short message data is smaller than the packet length threshold. (4) Whether the receiving end supports the special codeword refers to whether the PHY layer of the receiving end supports the mapping capability of the special codeword and the HARQ session ID. Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) is required to obtain the hybrid automatic retransmission request (HARQ capability negotiation request) packet, such as carrier Sense Multiple Access with Collision Avoidance (CSMA/CA). Shared channel usage rights or OFDMA subchannel usage rights, or other channel usage rights. Further, in step 10, the sending end sends the hybrid automatic repeat request HARQ capability negotiation request message to the receiving end, and may further include: after the sending end sends the hybrid automatic repeat request HARQ capability negotiation request message, The sending end starts the local timer, and if the sending end does not receive the HARQ capability negotiation response message of the receiving end, the transmitting end resends the HARQ capability negotiation request message, and The number of transmissions is increased by 1; if the number of retransmissions exceeds the preset value, the HARQ is discarded.

Step 20: The sending end receives the HARQ capability negotiation response message fed back by the receiving end, according to The HARQ capability negotiation response packet determines whether the receiving end supports HARQ. If supported, the receiving end allocates a HARQ session identifier. In the step 20, the transmitting end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the content of the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier to the receiving end. Identifies this HARQ session; if not, abandon this HARQ session and use ARQ to complete communication with the receiver. Step 30: The sending end acquires the channel usage right of sending the HARQ data packet, and sends the HARQ data to the receiving end according to the HARQ session identifier. Step 40: The sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to the preset rule. The embodiment is the flow of the receiving end in the hybrid automatic repeat request method provided by the present invention. Referring to FIG. ₂ , FIG. 2 is a schematic flowchart of another hybrid automatic repeat request method according to Embodiment 1 of the present invention. In this embodiment, the following steps may be included: Step 50: The receiving end feeds back a HARQ capability negotiation response message to the sending end. In the step 50, after receiving the HARQ capability negotiation request packet sent by the sending end, the receiving end feeds back the HARQ capability negotiation response message to the sending end according to its own situation. The HARQ capability negotiation response message may include the following contents: (1) the receiving end supports HARQ; (2) supports or is compatible with OFDMA; (3) the message length threshold; (4) supports special code words or does not support special code words. In this embodiment, the receiving end supports HARQ, and the supported channel types can be classified into three types: some receiving ends support OFDMA, some receiving ends do not support OFDMA only support CSMA/CA, and some receiving ends support both OFDMA and CSMA. /CA, which is compatible with OFDMA. There are two types according to whether special codewords are supported: Some receivers support special codewords, and some receivers do not support special codewords. The receiving end feeds back the HARQ capability negotiation response message to the sending end according to its specific situation.

Step 60: The receiving end receives the sending end to allocate the HARQ session identifier. In the step S60, the receiving end receives the HARQ session identifier, and the HARQ session identifier that is sent by the sending end to the receiving end can be sent to the receiving end through the HARQ configuration request message. Step 70: The receiving end receives the number of HARQs sent by the sending end according to the HARQ session identifier. According to the message, the response message is fed back to the sending end according to the HARQ data packet. In the step 70, the receiving end receives the HARQ data sent by the sending end according to the HARQ session identifier, and obtains the mapping relationship between the HARQ session identifier and the sending end, for example, identifies the mapping relationship between the OFDMA subchannel and the HARQ session identifier of the sending end, and sends the identifier. A mapping relationship between the special codeword of the terminal and the HARQ session identifier, and a mapping established between the received HARQ data packet and the HARQ session identifier. The hybrid automatic repeat request method provided by the embodiment of the present invention establishes a mapping relationship between the transmitting end and the HARQ session identifier by using the sending end, and sends a HARQ data packet to the receiving end according to the HARQ session identifier, and the sending end is configured according to the received receiving end. The feedback message is sent to determine whether the data packet is sent successfully or the retransmission operation is performed according to the preset rule, which avoids the multi-user collision problem of the shared channel in the WiFi communication system, and improves the HARQ gain effect, and has a wide application range.

Embodiment 2 This embodiment is an optimization scheme when the receiving end only supports CSMA/CA and the receiving end supports special code words based on the above implementation. Referring to FIG. 3, FIG. 3 is a schematic flowchart of a hybrid automatic repeat request method according to a second embodiment of the present invention (in FIG. 3, only keywords in the step are shown, and details are described in the embodiment). The method may include the following steps: Step 301: The sending end sends a hybrid automatic repeat request (HARQ capability negotiation request) message to the receiving end. In step 301, the MAC layer of the sending end knows that it needs to send a new service flow to a receiving end, and then creates a new traffic identifier (TID). The MAC layer of the sender sends a HARQ capability negotiation request packet to the receiver. The content of the packet includes but is not limited to the following:

(1) Whether the receiving end supports HARQ;

(2) Whether the receiving end supports OFDMA;

(3) the length of the message length;

(4) Whether the receiving end supports special code words. Before sending the HARQ capability negotiation request message, the sender first needs to follow the CSMA/CA mode to obtain the right to use the shared channel. Step 302: The receiving end feeds back a HARQ capability negotiation response message to the sending end. In step 302, the receiving end feeds back the HARQ capability negotiation response message to the sending end, including but not limited to the following: Supporting HARQ; not supporting OFDMA; the value of the packet length threshold is 256 (only the example value is given in this embodiment) ; Support special code words. Before issuing the HARQ capability negotiation response message, the receiving end first needs to follow the CSMA/CA mode to obtain the right to use the shared channel. Step 303: The sending end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier. In addition, in step 303, the transmitting end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier, and then performs the step. 304; If not, abandon this HARQ session and use ARQ to communicate with the receiver. Step 304: Generate a mapping relationship between the sender and the HARQ session identifier, and send a configuration request packet including the mapping relationship to the receiver. The transmitting end allocates a corresponding special codeword for the HARQ session, and forms a mapping relationship between the HARQ session identifier and the special codeword. The special codeword is used to mark the sending end. Specifically, the sending end negotiates the response report according to the HARQ capability. The message determines whether the special codeword is supported. If it supports, the special codeword of the sender is mapped to the HARQ session identifier. The sender sends a HARQ configuration request packet to the receiver. The HARQ configuration request packet includes the special code of the sender. Word and HARQ session ID. In step 304, the transmitting end first determines whether the receiving end supports OFDMA according to the HARQ capability negotiation response message. In this embodiment, it is not supported. Then, the packet length threshold is obtained from the HARQ capability negotiation response message and stored, and then the receiving end is determined. Whether the special codeword is supported, if it is supported in this embodiment, the HARQ is used for the data packet of all lengths, and the sender allocates a special codeword for identifying the sender, and maps the special codeword to the HARQ session identifier. relationship. Then, the sending end sends a HARQ configuration request message to the receiving end, where the HARQ configuration request message includes but is not limited to: a special code word identifying the transmitting end and a HARQ meeting Word logo. Before sending the HARQ configuration request message, the sender first needs to follow the CSMA/CA mode to obtain the right to use the shared channel. Step 305: The receiving end receives the configuration request message sent by the sending end, where the configuration request includes the mapping relationship between the sending end and the HARQ session identifier.

The mapping relationship between the sender and the HARQ session identifier is: a mapping relationship between the HARQ session identifier and the special codeword. In step 305, the receiving end receives the HARQ configuration request packet, and obtains a mapping relationship between the special codeword of the sending end and the HARQ session identifier, and stores the mapping relationship, and then the receiving end feeds back the configuration response message to the sending end. Step 306: The sending end acquires a CSMA/CA shared channel usage right. In step 306, the sender obtains the CSMA/CA shared channel usage right. If both the sender and the receiver work in the CSMA/CA mode, the length of the HARQ data packet needs to be differentiated according to the length of the HARQ data packet. If the length of the HARQ data packet is greater than or equal to The packet length threshold is sent by RTS/CTS; if the length of the HARQ data packet is less than the packet length threshold, it is sent by DATA/ACK. Step 307: Send a HARQ data packet to the receiving end by using the CSMA/CA shared channel usage right according to the HARQ session identifier. In step 307, before the sending of the HARQ data packet to the receiving end according to the HARQ session identifier, the method may further include the following steps: Step 3071: The sending end encodes the source data.

Step 3072: Obtain a special codeword corresponding to the HARQ session identifier; Step 3073, add a HARQ header to the encoded data; Step 3074, insert the special codeword into the data after adding the HARQ header; so that the special code is inserted. The data of the word is sent to the receiving end as a HARQ data message. The sending end encodes the source data in the step 3071, and the encoding may include, but is not limited to: a turbo code, an LDPC code, and the embodiment does not limit the encoding #. It is also possible to back up the encoded data for storage.

Inserting the special codeword into the data after adding the HARQ header in step 3074 may preferentially include the following: inserting the special codeword into the signal field and number of the data to which the HARQ header is added According to the domain. Referring to FIG. 4, FIG. 4 is a schematic diagram of inserting a special codeword according to Embodiment 2 of the present invention.

As shown in FIG. 4, an OFDM symbol includes a Physical Layer Convergence Procedure (PLCP) Preamble field, a SIGNAL field, and a Data field, and the PLCP Preamble field is an OFDM pilot sequence, SIGNAL. The main information included in the field is: code modulation mode and length, etc. The DATA field is a HARQ data message, and the special code word is inserted between the SIGNAL field and the DATA field in FIG. 4, and the scheme inserts a special code word into the HARQ. Forward compatibility is achieved between the SIGNAL field and the DATA field of the header data.

In step 307, the special codeword is inserted into the data after adding the HARQ header, and the following may be preferentially included: the special codeword is backed up, the special codeword is inserted into the first domain of the PLCP Preamble, and the special codeword backup is inserted into the PLCP Preamble. The second domain. A piece of codeword is placed in duplicate in the Preamble. The function is to perform a sliding correlation operation on the physical layer of the receiving end, thereby obtaining a correlation peak point and achieving frame synchronization. Channel estimation can also be performed by using two types of consecutively placed special code words that are known in advance by both the receiving end and the transmitting end. The scheme implements the special codeword backup and inserts the special codeword into the first domain of the PLCP Preamble, and inserts the special codeword backup into the second domain of the PLCP Preamble. In addition to the functions of frame synchronization and channel estimation, the solution is also implemented. Accurately identify the sender. The first domain may be a T1 domain, and the second domain may be a T2 domain. For details, refer to FIG. 5. FIG. 5 is a schematic diagram of another special codeword inserted according to Embodiment 1 of the present invention. The T1 and T2 domains are two fixed locations of the Preamble specified by the IEEE 802.1 1 protocol. The T1 and T2 fields are placed in a fixed sequence, which are placed in duplicate, and the functions are synchronization and channel estimation. In this solution, the sequences used by the T1 and T2 domains of all users are different, so that the transmission can be identified. end. In this solution, by inserting a special codeword into the T1 field of the PLCP Preamble, the special codeword backup is inserted into the T2 domain of the PLCP Preamble, and the codeword length is not increased, thereby reducing the overhead. The HARQ data message is then sent to the receiving end through the obtained CSMA/CA shared channel. Step 308: The receiving end receives the number of HARQs sent by the sending end according to the HARQ session identifier. According to the packet, the response message is fed back to the sender according to the HARQ data packet. In step 308, the physical layer of the receiving end detects a signal that is higher than the idle channel estimation threshold, and starts to acquire the pilot sequence. If the capture succeeds, the encoding mode and length of the HARQ data packet are obtained, and the HARQ data packet is obtained from the HARQ data packet. The special codeword forms a mapping relationship between the HARQ data packet and the HARQ session identifier according to the special codeword. Specifically, the special codeword obtained in the configuration request message received by the receiving end in step 305 is slidably correlated with the header of the special codeword obtained in the HARQ data packet received in step 308. If a peak occurs, it indicates that the special codeword in the HARQ data packet is consistent with the special codeword obtained in the configuration request message, and the HARQ data packet is from the sender, that is, the special codeword is recognized; if it does not appear The peak value indicates that the special codeword in the HARQ data packet is inconsistent with the special codeword obtained in the configuration request message. The HARQ data packet is not from the sender, that is, the special codeword identification fails. Then, the special codeword is established with the service flow identifier TID. Each service flow is composed of multiple HARQ data, and the mapping between the service flow and the HARQ session identifier is equivalent to mapping each data packet with the HARQ session identifier. The mapping is released when all HARQ data packets of a service flow are transmitted. Through the mapping relationship, the receiving end can be made aware of which transmitting end the HARQ data 4 is from. Then, the HARQ data packet is demodulated and decoded, and the FCS check is performed on the decoded binary bit number, and the response message is fed back to the transmitting end according to the result of the check. Further, the feedback message is sent back to the sending end according to the HARQ data packet, which may include the following: If the FCS check passes, the ACK is fed back to the sending end; if the special codeword identification is passed, and the FCS check fails, the sending end sends feedback to the sending end. Two NAK;

The FCS check is the decision basis for the success or failure of the WiFi communication system to decode and demodulate at the receiving end. The FCS can pass the feedback ACK, otherwise it will remain silent. After the FCS check is passed, the MAC layer of the receiving end can read the source address information from the MAC layer header, and then can know which sender the HARQ data message is from. The scheme forms a mapping relationship between the HARQ data packet and the HARQ session identifier by using a special codeword, so that the FSR can not know which sender the HARQ data packet comes from when the FCS does not pass. If the special codeword identification does not pass, the FCS check fails, the Request To Send (RTS)/Clear To Send (CTS) mode or the OFDMA mode, the second NAK is fed back to the sender; If the codeword recognition fails, the FCS check fails, and in the DATA/ACK mode, no information is fed back to the sender; if the pilot sequence fails to be captured, in the DATA/ACK mode, no information is fed back to the sender;

If the acquisition pilot sequence fails, in RTS/CTS mode or OFDMA mode, the first NAK: is fed back to the transmitting end. Further, when the receiving end feeds back the second NAK, the HARQ data packet that fails to be received may also be buffered. The buffer may be in the form of receiving an analog signal, or a digital signal, or a demodulated signal, or a decoded signal, or any combination of the foregoing signals. In the other three feedback modes, the receiving end does not buffer the HARQ data packets that failed to be received. When the data message ends and waits for the Short Interframe Space (SIFS) time interval, the receiving end can immediately feed back ACK:.

The PHY layer receives the signal energy level from high to low and waits for the SIFS time interval, and the receiving end immediately feeds back the first NAK:. After the data packet ends, it waits for the SIFS interval, and the receiver immediately feeds back the second NAK information. There is no feedback time for silence. Step 309: The sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to the preset rule. In step 309, after the transmitting end completes the transmission of the HARQ data packet, it starts to wait for the response message of the receiving end. If the sender does not receive any feedback until the timer expires, it will resend the same data message with the same power sent last time, and then continue to wait for the response message from the receiver. If the ACK feedback is received, the sender deletes the backup of the buffered data message and its associated redundant message, and continues to send other data packets of the service flow. If the first NAK feedback is received, the sender will resend the same as the last power sent. The data message then continues to wait for the response message from the receiver. If the second NAK feedback is received, the sender may have more retransmission policies. The specific retransmission policy is determined by the sender and the receiver in the HARQ capability negotiation phase. The power of the retransmitted data message can be either larger than the last transmission, or smaller than the last transmission, or the same as the last transmission. The retransmitted data packet may be the same data packet as the last time, or may be a self-decoding redundant packet different from the last time, or may be a non-self-decoding redundant packet different from the last time. . In this embodiment, it is preferable to transmit the self-decoded redundant message with the same power, and then continue to wait for the feedback information of the receiving end.

Step 310: The receiving end receives the HARQ retransmission data packet sent by the sending end, and decodes the HARQ retransmission data packet. If the receiving end receives the HARQ session ending packet sent by the sending end, the receiving end corresponding to the HARQ session is cleared. HARQ datagram and HARQ session identifier.

In step 310, the receiving end, if receiving the HARQ retransmission data packet sent by the sending end, decoding the HARQ retransmission data packet, may include: decoding the HARQ retransmission data; or retransmitting the HARQ The data is combined with the cached HARQ data message to be decoded.

When the sender receives the ACK, it determines that the data packet is sent successfully. If the service layer of the application layer does not need to send a new data packet, the HARQ session termination packet is sent to the receiver. Otherwise, continue to use the HARQ session to send subsequent data packets to the receiver. The content of the HARQ session end message includes but is not limited to: a HARQ session identifier. At the same time, the transmitting end is configured to establish a mapping relationship with the HARQ session identifier; the HARQ data packet is cleared; and the HARQ session ending packet is sent to the receiving end.

The receiving end receives the HARQ session end message, and clears the HARQ data file and the HARQ session identifier corresponding to the HARQ session. In this embodiment, the mapping between the special codeword and the HARQ session identifier is established by the receiving end, and the multi-user collision problem in the HARQ is solved, and the sending end determines whether the data packet is successfully sent according to the received response message fed back by the receiving end. The preset rule performs a retransmission operation. The gain effect of applying HARQ to a WiFi communication system is improved.

Embodiment 3

This embodiment is an optimization scheme when the receiving end supports only OFDMA and the receiving end supports the special codeword based on the foregoing implementation. FIG. 6 is a schematic flowchart diagram of a hybrid automatic repeat request method according to Embodiment 3 of the present invention. Only the keywords in the steps are shown in FIG. 6, and the specific description is referred to the embodiment. Referring to FIG. 6, the method may include the following steps: Step 401: The sending end sends a hybrid automatic retransmission request to the receiving end, the HARQ capability negotiation request. In step 401, the MAC layer of the sending end knows that a new service flow needs to be sent to a receiving end, and a new flow identifier TID is created. The MAC layer of the sender sends a HARQ capability negotiation request packet to the receiver. The content of the packet includes but is not limited to the following:

(1) Whether the receiving end supports HARQ;

(2) Whether the receiving end supports OFDMA;

(3) the length of the message length;

(4) Whether the receiving end supports special code words. Before sending the HARQ capability negotiation request message, the sender first needs to allocate and reserve the OFDMA subchannel. Under the OFDMA, the static channel allocation method is used, that is, the same subchannel is used in the subsequent HARQ process after one allocation. Step 402: The receiving end feeds back a HARQ capability negotiation response message to the sending end.

In the step 402, the receiving end feeds back the HARQ capability negotiation response message to the sending end according to the receiving end, including but not limited to the following: supporting HARQ; supporting OFDMA; the value of the packet length threshold is 256 (this embodiment only gives Example value); Support for special codewords. Before the HARQ capability negotiation response message is sent, the receiving end first needs to request the OFDMA subchannel from the transmitting end. After the transmitting end feeds back the OFDMA subchannel, the receiving end feeds back the HARQ capability negotiation response message to the transmitting end.

Step 403: The sender receives the HARQ capability negotiation response message fed back by the receiving end, and the root According to the HARQ capability negotiation response message, it is determined whether the receiving end supports HARQ, and if supported, the receiving end is assigned a HARQ session identifier.

In addition, in step 403, the sending end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier, and then performs the step. 404; If not, abandon this HARQ session and use ARQ to communicate with the receiver.

Step 404: Generate a mapping relationship between the sending end and the HARQ session identifier, and send a configuration request message including a mapping relationship to the receiving end.

The specific step 404 is: the sending end determines whether to support the orthogonal frequency division multiplexing multiple access OFDMA according to the HARQ capability negotiation response message, and if necessary, establishes a mapping relationship between the subchannel of the OFDMA of the transmitting end and the HARQ session identifier. The HARQ configuration request message includes: whether the HARQ is synchronized, and whether the HARQ is adaptive;

In the step 404, the transmitting end first determines that the receiving end supports the OFDMA according to the HARQ capability negotiation response message, and establishes a mapping relationship between the OFDMA subchannel and the HARQ session identifier, obtains the packet length threshold from the HARQ capability negotiation response message, and stores the packet to receive. The terminal sends a HARQ configuration request packet.

Step 405: The receiving end feeds back a HARQ configuration response message to the sending end. In step 405, the receiving end sends a HARQ configuration response message to the transmitting end according to its own situation, where the HARQ configuration response message includes: HARQ synchronization or non-synchronization selection result, HARQ adaptive or non-adaptive selection result.

Step 406: The sender acquires an OFDMA subchannel usage right. The OFDMA subchannel refers to the OFDMA subchannel that the sender needs to allocate and reserve first before sending the HARQ capability negotiation request message in step 401.

In step 406, the transmitting end allocates and reserves the OFDMA subchannel for the HARQ session, and notifies the receiving end that the OFDMA subchannel is exclusively used by the receiving end and the transmitting end before the end of the HARQ session. The receiving end establishes a mapping relationship between the OFDMA subchannel and the HARQ session identifier.

Step 407: Use the right to use the OFDMA subchannel according to the HARQ session identifier. The receiving end sends a HARQ data packet. In step 407, before sending the HARQ data packet to the receiving end according to the HARQ session identifier, the method may include the following steps: Step 4071: The sending end encodes source data; Step 4072: Add a HARQ header to the The encoded data is used to send the HARQ header-added data to the receiving end as a HARQ data message. Among them, the encoded data can also be backed up and stored. The HARQ data message is then sent to the receiving end through the obtained channel. Step 408: The receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and feeds back the response message to the sending end according to the HARQ data packet. In step 408, the physical layer of the receiving end detects a signal that is higher than the idle channel estimation threshold, and starts to acquire the pilot sequence. If the acquisition succeeds, the encoding mode and length of the HARQ data packet are obtained, and the HARQ is obtained according to the OFDMA subchannel. The data message and the HARQ session identifier form a mapping relationship with the service flow. Then, the HARQ data packet is demodulated and decoded, and the FCS check is performed on the decoded binary bit number, and the response message is fed back to the transmitting end according to the result of the check. Further, the acknowledgment message is sent to the sending end according to the HARQ data packet, and may include the following: if the capturing pilot sequence succeeds, the FCS check passes, and the ACK is fed back to the sending end; if the capturing pilot sequence succeeds, the FCS check fails. Then, the second NAK is fed back to the transmitting end; if the capturing pilot sequence fails, the first NAK is fed back to the transmitting end. The scheme forms a mapping relationship between the HARQ data packet and the HARQ session identifier by using the OFDMA subchannel, so that the FSR can not know which transceiver the HARQ data packet comes from when the FCS does not pass.

Further, when the receiving end feeds back the second NAK, the HARQ data packet that fails to be received may also be buffered. Step 409: The sending end receives the response message fed back by the receiving end, according to the response message, The data packet is sent successfully or the retransmission operation is performed according to the preset rule. In step 409, after the transmitting end completes the transmission of the HARQ data packet, it starts to wait for the response message of the receiving end. If the ACK feedback is received, the sender deletes the backup of the buffered data message and its associated redundant message, and continues to send other data packets of the service flow. If the second NAK feedback is received, the non-self-solvable redundant message can be sent with the same power. If the first NAK feedback is received, the power transmission may be increased to be the same as the current HARQ data message. Step 410: The receiving end receives the HARQ retransmission data packet sent by the sending end, and decodes the HARQ retransmission data packet. If the receiving end receives the HARQ session ending packet sent by the sending end, the receiving end corresponding to the HARQ session is cleared. In the HARQ data packet and the HARQ session identification step 410, if the receiving end receives the HARQ retransmission data packet sent by the transmitting end, and decoding the HARQ retransmission data packet, the method may include: retransmitting the HARQ data and The buffering of the current HARQ data message is combined and decoded. When the ACK is received by the sender, it is determined that the data packet is successfully sent. If the service stream of the application layer does not need to send a new data packet, the HARQ session termination packet is sent to the receiver. Otherwise, continue to use the HARQ session to send subsequent data packets to the receiver. The content of the HARQ session end message includes but is not limited to: a HARQ session identifier. At the same time, the transmitting end is configured to establish a mapping relationship with the HARQ session identifier; the HARQ data packet is cleared; and the HARQ session end message is sent to the receiving end. The receiving end receives the HARQ session end message, and clears the HARQ data file and the HARQ session identifier corresponding to the HARQ session. In this embodiment, the mapping relationship between the OFDMA subchannel and the HARQ session identifier is established by the transmitting end, and the multi-user collision problem in the HARQ is solved. And the sending end determines whether the data packet is successfully sent according to the received response message received by the receiving end, or performs a retransmission operation according to the preset rule, thereby improving the gain effect of applying the HARQ to the WiFi communication system.

Embodiment 4 This embodiment is based on the foregoing implementation, when the receiving end is compatible with supporting OFDMA, that is, an optimization scheme is supported when both C SMA/CA and OFDMA are supported, and the receiving end supports special code words. FIG. 7 is a schematic flowchart diagram of a hybrid automatic repeat request method according to Embodiment 4 of the present invention. Only the keywords in the steps are shown in FIG. 7, and the specific description is referred to the embodiment. Referring to FIG. 7, the method may include the following steps: Step 501: The sending end sends a hybrid automatic repeat request (HARQ capability negotiation request) message to the receiving end. In step 501, the MAC layer of the sending end knows that it needs to send a new service flow to a receiving end, and then creates a new flow identifier TID. The MAC layer of the sending end sends a HARQ capability negotiation request message to the receiving end, and the content of the message includes but is not limited to the following contents:

(1) Whether the receiving end supports HARQ;

(2) Whether the receiving end supports OFDMA;

(3) the length of the message length;

(4) Whether the receiving end supports special code words.

The HARQ capability negotiation request is sent, and the sender can either pass the CSMA/CA shared channel or allocate and reserve the OFDMA subchannel. Step 502: The receiving end feeds back a HARQ capability negotiation response message to the sending end.

In step 502, according to the situation of the receiving end, the receiving end feeds back the HARQ capability negotiation response message to the sending end, including but not limited to the following: Supporting HARQ; Compatible with OFDMA; The value of the packet length threshold is 256 (This embodiment only Give example values); support special codewords. The channel used by the sending end to send the HARQ capability negotiation request message may be a CSMA/CA shared channel or an OFDMA subchannel. Step 503: The sending end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier. In step 503, after receiving the HARQ capability negotiation response message fed back by the receiving end, the transmitting end determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message, and if yes, assigns the HARQ session identifier to the receiving end, and then performs the steps. 34; if not supported, put Discard this HARQ session and use ARQ to communicate with the receiver. Step 504: Generate a mapping relationship between the sender and the HARQ session identifier, and send a configuration request packet including the mapping relationship to the receiver. Since the scheme is compatible with the OFDMA orthogonal independent sub-channel and the CSMA/CA, the solution in this embodiment can be considered to take both the second and third solutions. In the specific step 504, the transmitting end negotiates the response according to the HARQ capability. The message first determines that the receiving end is compatible with OFDMA, and establishes a mapping relationship between the OFDMA subchannel and the HARQ session identifier. From the HARQ special codeword, HARQ is used for all lengths of data packets, and the sender allocates a special identifier for identifying the sender. a codeword, and forming a mapping relationship between the HARQ session identifier and the special codeword. Then, the sending end sends a HARQ configuration request message to the receiving end, where the HARQ configuration request message includes, but is not limited to: identifying a special codeword of the sending end, a HARQ session identifier, whether the HARQ is synchronized, and whether the HARQ is adaptive. The channel on which the sender sends the HARQ configuration request message may be a CSMA/CA shared channel or an OFDMA subchannel. Step 505: The receiving end receives the HARQ configuration request message of the sending end, and feeds back the HARQ configuration response message to the sending end. The HARQ configuration response message includes but is not limited to: HARQ synchronization or non-synchronization selection result, HARQ adaptive or non-adaptive selection result. Step 506: The sender acquires a CSMA/CA shared channel usage right or an OFDMA subchannel usage right.

In step 506, if the OFDMA subchannel can be obtained, the OFDMA subchannel is allocated and reserved for the HARQ session, and the receiving end is notified. If the OFDMA subchannel cannot be obtained, the CSMA/CA shared channel usage right is obtained. It should be noted that the channel used before step 506 can be different from the channel obtained in step 506, and the step after step 506 is the same as the channel obtained in step 506. For example, step 506 may be preceded by a CSMA/CA shared channel, and in step 506, the usage rights of the OFDMA subchannel may be obtained, and then the OFDMA subchannel is used after step 506.

Step 507: Send a HARQ data packet to the receiving end according to the HARQ session identifier. In step 507, the HARQ data packet is sent to the receiving end according to the HARQ session identifier, where For example, reference may be made to the schemes of the second embodiment and the third embodiment, that is, when the OFDMA subchannel usage right is obtained in step 506, reference may be made to the third embodiment, and the CSMA/CA shared channel usage right time obtained in step 506 is referred to. The solution provided in the second embodiment is not described here.

Step 508: The receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and feeds back the response packet to the sending end according to the HARQ data packet.

If the acquired OFDMA subchannel usage right is obtained, in step 508, the physical layer of the receiving end detects a signal higher than the idle channel estimation threshold, starts to acquire the pilot sequence, and if the acquisition is successful, acquires the encoding mode of the HARQ data. And length, and forming a mapping relationship between the HARQ data and the HARQ session identifier and the service flow according to the OFDMA subchannel, and then demodulating, decoding, and performing FCS check on the decoded binary bit number according to the The result of the check feeds back the response message to the sender.

Further, the feedback message is sent back to the sending end according to the HARQ data packet, and may include the following: if the capturing pilot sequence succeeds, and the FCS check passes, the ACK is fed back to the sending end; if the capturing pilot sequence succeeds, If the FCS check fails, the second NAK is fed back to the transmitting end; if the capturing pilot sequence fails, the first NAK is fed back to the transmitting end.

Further, when the receiving end feeds back the second NAK, the HARQ data packet that fails to be received may also be buffered.

If the CSMA/CA shared channel is obtained, in step 508, specifically, the physical layer of the receiving end detects a signal higher than the idle channel estimation threshold, and starts to acquire the pilot sequence. If the capture succeeds, the HARQ data is acquired. The coding mode and the length, the special codeword is obtained from the HARQ data packet, and the HARQ data packet is mapped to the HARQ session identifier according to the special codeword. Refer specifically to step 308 in the second embodiment. Then, the HARQ data packet is demodulated and decoded, and the FCS check is performed on the decoded binary bit number, and the response message is fed back to the transmitting end according to the result of the check.

Further, the response message is fed back to the sending end according to the HARQ data packet, which may include the following: If the FCS check passes, the ACK is fed back to the sender; if the special codeword identification is passed, the FCS check fails, the second NAK is fed back to the sender; if the special codeword identification fails, the FCS check fails, RTS/CTS mode Or in the OFDMA mode, the second NAK is fed back to the transmitting end; if the special codeword identification does not pass, the FCS check fails, and in the DATA/ACK mode, no information is fed back to the transmitting end; if the capturing pilot sequence fails, DATA/ACK In the mode, no information is fed back to the sender;

If the acquisition pilot sequence fails, in RTS/CTS mode or OFDMA mode, the first NAK: is fed back to the transmitting end. Further, when the receiving end feeds back the second NAK, the HARQ data packet that fails to be received may also be buffered. The buffer may be in the form of receiving an analog signal, or a digital signal, or a demodulated signal, or a decoded signal, or any combination of the foregoing signals. In the other three feedback modes, the receiving end does not buffer the HARQ data packets that failed to be received. The scheme forms a mapping relationship between the HARQ data and the HARQ session identifier by using a special codeword or an OFDMA subchannel, so that the FQ can not know which sender the HARQ data packet comes from when the FCS does not pass. Step 509: The sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to the preset rule. In step 509, after the transmitting end completes the sending of the HARQ data packet, the transmitting end waits for the response message of the receiving end. If the ACK feedback is received, the sender deletes the backup of the buffered data message and its associated redundant message, and continues to send other data packets of the service flow. If the second NAK feedback is received, the non-self-solvable redundant message can be sent with the same power, and then wait for the response message of the receiving end. If the first NAK feedback is received, the data packet with the same power transmission and the same HARQ data packet can be increased. Then continue to wait for the receiving end's response message.

In step 509, after the transmitting end completes the sending of the HARQ data packet, it starts to wait. The response message of the receiving end. If the sender does not receive any feedback until the timer expires, it will resend the same data message with the same power sent last time, and then continue to wait for the response message from the receiver. If the ACK feedback is received, the sender deletes the backup of the buffered data message and its associated redundant message, and continues to send other data packets of the service flow. If the first NAK feedback is received, the sender resends the same data message with more power than the last one sent, and then continues to wait for the response message from the receiver. If the second NAK feedback is received, the sender may have more retransmission policies. The specific retransmission policy is determined by the sender and the receiver in the HARQ capability negotiation phase. The power of the retransmitted data message can be either larger than the last transmission, or smaller than the last transmission, or the same as the last transmission. The retransmitted data packet may be the same data packet as the last time, or may be a self-decoding redundant packet different from the last time, or may be a non-self-decoding redundant packet different from the last time. . In this embodiment, it is preferable to transmit the self-decoded redundant message with the same power, and then continue to wait for the response message of the receiving end.

Step 510: The receiving end receives the HARQ retransmission data packet sent by the sending end, and decodes the HARQ retransmission data packet. If the receiving end receives the HARQ session ending packet sent by the sending end, the receiving end corresponding to the HARQ session is cleared. HARQ datagram and HARQ session identifier.

In step 510, if the receiving end receives the HARQ retransmission data packet sent by the transmitting end, and decoding the HARQ retransmission data packet, the receiving end may include: combining the HARQ retransmission data and the buffering the current HARQ data packet to perform decoding. . In step 510, if the receiving end receives the HARQ retransmission data packet sent by the transmitting end, and decoding the HARQ retransmission data packet, the receiving end may include: decoding the HARQ retransmission data; or retransmitting the HARQ data and the buffer version. The secondary HARQ data packets are combined and decoded. When the sender receives the ACK, it determines that the data packet is sent successfully. If the service layer of the application layer does not need to send a new data packet, the HARQ session termination packet is sent to the receiver. Otherwise, continue to use the HARQ session to send subsequent data packets to the receiver. The content of the HARQ session end message includes but is not limited to: a HARQ session identifier. At the same time, the transmitting end is configured to establish a mapping relationship with the HARQ session identifier; and the HARQ data packet is cleared;

Sending a HARQ session end message to the receiving end. The receiving end receives the HARQ session end message, and clears the HARQ data file and the HARQ session identifier corresponding to the HARQ session. In this embodiment, a multi-user collision problem in HARQ is solved by establishing a mapping relationship between an OFDMA subchannel and a HARQ session identifier, or establishing a mapping relationship between a special codeword and a HARQ session identifier. And the sending end determines whether the data packet is successfully sent according to the received response message received by the receiving end, or performs a retransmission operation according to the preset rule, thereby improving the gain effect of applying the HARQ to the WiFi communication system.

Embodiment 5 This embodiment is an optimization scheme when the receiving end only supports CSMA/CA and the receiving end does not support special code words based on the foregoing implementation 1. FIG. 8 is a flow chart showing a hybrid automatic repeat request method according to Embodiment 5 of the present invention. Only the keywords in the steps are shown in FIG. 8, and the specific description is referred to the embodiment. Referring to FIG. 8, the method may include the following steps: Step 601: The sending end sends a hybrid automatic repeat request to the receiving end, the HARQ capability negotiation request. Step 601 and step 301 are the same, and are not described in detail herein. Step 602: The receiving end feeds back a HARQ capability negotiation response message to the sending end. In step 602, the receiving end feeds back the HARQ capability negotiation response message to the sending end, including but not limited to the following: Supporting HARQ; not supporting OFDMA; the value of the packet length threshold is 256 (only the example value is given in this embodiment) ; Special code words are not supported. Before issuing the HARQ capability negotiation response message, the receiving end first needs to follow the CSMA/CA mode to obtain the right to use the shared channel.

Step 603: The receiving end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier. Step 604: The sender acquires a CSMA/CA shared channel usage right. The step 604 specifically includes: the sending end is marked by the channel that sends the HARQ data packet. Recording the right to use the RTS frame requesting channel, where the RTS frame includes the HARQ session identifier, the MAC address of the transmitting end, and the usage time of the channel; the receiving end is in the channel for transmitting the HARQ data packet Obtaining an RTS frame, and feeding back a CTS frame to the transmitting end according to the RTS frame, where the CTS frame is used to confirm that the sending end acquires a right to use the channel for sending the HARQ data packet, where the CTS frame includes The MAC address of the receiving end and the usage time of the channel, and the HARQ data to be received at this time is mapped to the HARQ session identifier. The transmitting end receives a CTS frame that is sent back by the receiving end according to the RTS frame, and the CTS frame is used to confirm that the sending end acquires a right to use the channel for sending the HARQ data packet, where the CTS frame includes The MAC address of the receiving end and the time of use of the channel.

Step 605: The sending end sends a HARQ data packet to the receiving end according to the HARQ session identifier.

In step 605, the data packet sent by the sending end is smaller than the packet length threshold, and the data packet sent by the ARQ is sent by the HARQ. It should be noted that when sending through ARQ, the existing standard can be used.

In step 605, the sending of the HARQ data packet to the receiving end according to the HARQ session identifier includes the following steps: Step 6051: The sending end encodes the source data.

Step 6052: Add a HARQ header to the encoded data. Step 6053: Send the data with the HARQ header as a HARQ data packet to the receiving end.

Step 606: The receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and feeds back the response message to the sending end according to the HARQ data packet.

In step 606, the physical layer of the receiving end detects a signal that is higher than the idle channel estimation threshold, and starts to acquire the pilot sequence. If the capture succeeds, the encoding mode and length of the HARQ data packet are obtained. If the receiving end receives the RTS frame and replies to the CTS frame, the mapping between the received HARQ data packet and the HARQ session identifier is established; if the RTS frame is not received, If the received data packet is sent through the ARQ, it can be processed according to the prior art. Then, the receiving end demodulates and decodes the HARQ data packet, performs FCS check on the decoded binary bit number, and feeds back the response message to the transmitting end according to the result of the check.

Further, the feedback message is fed back to the sending end according to the HARQ data packet, and may include the following: If the pilot acquisition succeeds, and the FCS check passes, the ACK: is fed back to the sending end. If the pilot acquisition is successful and the FCS check fails, if it is HARQ, the second NAK: is fed back to the sender. If the pilot acquisition is successful and the FCS check fails, if it is ARQ, no information is fed back to the sender.

If the pilot acquisition fails, in the RTS/CTS mode, the first NAK: is fed back to the sender. If the pilot acquisition fails, in the DATA/ACK mode, the receiver does not feed back any information and remains silent. The scheme establishes a mapping relationship between the received HARQ data packet and the HARQ session identifier, so that the FIQ data packet can be learned from which transmitting end when the FCS does not pass.

In addition, if the data message is sent through the ARQ, the receiving end does not feed back any information to the sending end.

When the receiving end feeds back the second NAK, the HARQ data packet that fails to be received may also be cached. The buffer may be in the form of receiving an analog signal, or a digital sample signal, or a demodulated signal, or a decoded signal, or any combination of the foregoing signals. In the other three feedback modes, the receiving end does not buffer the HARQ data packet that failed to be received. Step 607: The sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to the preset rule.

In step 607, after the transmitting end completes the transmission of the HARQ data packet, it starts to wait for the response message of the receiving end. If the sender does not receive any feedback until the timer expires, it will resend the same data message with the same power sent last time, and then continue to wait for the response message from the receiver. If the ACK feedback is received, the sender deletes the backup of the buffered data message and its associated redundant message, and continues to send other data packets of the service flow. in case After receiving the second NAK feedback, the sender has more optional retransmission policies. The specific retransmission policy is determined by the sender and the receiver in the HARQ capability negotiation phase. In this embodiment, it is preferable to transmit the self-decoded redundant message with the same power, and then continue to wait for the response message of the receiving end. If the first NAK feedback is received, the sender resends the same data message with more power than the last one sent, and then continues to wait for the response message from the receiver.

Step 608: The receiving end receives the HARQ retransmission data packet sent by the sending end, and decodes the HARQ retransmission data packet. If the receiving end receives the HARQ session ending packet sent by the sending end, the receiving end corresponds to the HARQ session. In the HARQ data packet and the HARQ session identification step 608, if the receiving end receives the HARQ retransmission data packet sent by the transmitting end, and decoding the HARQ retransmission data packet, the method may include: decoding the HARQ retransmission data; Or the HARQ retransmission data is buffered and the current HARQ data message is buffered and then decoded. When the sender receives the ACK, it determines that the data packet is sent successfully. If the service layer of the application layer does not need to send a new data packet, the HARQ session termination packet is sent to the receiver. Otherwise, continue to use the HARQ session to send subsequent data packets to the receiver. The content of the HARQ session end message includes but is not limited to: a HARQ session identifier. At the same time, the transmitting end is configured to establish a mapping relationship with the HARQ session identifier; the HARQ data packet is cleared; and the HARQ session ending packet is sent to the receiving end. The receiving end receives the HARQ session end message, and clears the HARQ data file and the HARQ session identifier corresponding to the HARQ session. In this embodiment, by establishing a mapping relationship between the HARQ data and the HARQ session identifier, the sending end determines that the data packet is successfully sent or performs a retransmission operation according to the preset rule according to the received response message fed back by the receiving end, thereby improving the Applying HARQ to the gain effect in a WiFi communication system.

Embodiment 6 This embodiment is based on the foregoing implementation, when the receiving end only supports OFDMA, and The optimization scheme when the receiving end does not support special code words. FIG. 9 is a schematic flowchart diagram of a hybrid automatic repeat request method according to Embodiment 6 of the present invention. Only the keywords in the steps are shown in FIG. 9, and the specific description is referred to the embodiment. Referring to FIG. 9, the method may include the following steps: Step 701: The sending end sends a hybrid automatic repeat request (HARQ capability negotiation request) message to the receiving end. In step 701, the MAC layer of the sending end knows that a new service flow needs to be sent to a receiving end, and a new flow identifier TID is created. The MAC layer of the sending end sends a HARQ capability negotiation request message to the receiving end, and the content of the message includes but is not limited to the following contents:

(1) Whether the receiving end supports HARQ;

(2) Whether the receiving end supports OFDMA;

(3) the length of the message length;

(4) Whether the receiving end supports special code words. Before sending the HARQ capability negotiation request message, the sender first needs to allocate and reserve the OFDMA subchannel. Under the OFDMA, the static channel allocation method is used, that is, the same subchannel is used in the subsequent HARQ process after one allocation. Step 702: The receiving end feeds back a HARQ capability negotiation response message to the sending end.

In step 702, the receiving end feeds back the HARQ capability negotiation response message to the sending end according to the receiving end, including but not limited to the following: supporting HARQ; supporting OFDMA; the value of the packet length threshold is 256 (this embodiment only gives Example value); Support for special codewords. Before the HARQ capability negotiation response message is sent, the receiving end first needs to request the OFDMA subchannel from the transmitting end. After the transmitting end feeds back the OFDMA subchannel, the receiving end feeds back the HARQ capability negotiation response message to the transmitting end.

Step 703: The receiving end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier. In addition, in step 703, the transmitting end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports HARQ according to the HARQ capability negotiation response message, such as If yes, the receiving end is assigned a HARQ session identifier, and then step 704 is performed; if not, the current HARQ session is abandoned, and the ARQ is used to communicate with the receiving end. Step 704: Generate a mapping relationship between the sender and the HARQ session identifier, and send a configuration request packet including the mapping relationship to the receiver.

The specific step 704 is: the transmitting end determines whether to support the orthogonal frequency division multiplexing multiple access OFDMA according to the HARQ capability negotiation response message, and if necessary, establishes a mapping relationship between the subchannel of the OFDMA of the transmitting end and the HARQ session identifier. The HARQ configuration request message includes: whether the HARQ is synchronized, and whether the HARQ is adaptive. In step 704, the transmitting end first determines, according to the HARQ capability negotiation response message, that the receiving end supports OFDMA, and maps the OFDMA subchannel and the HARQ session identifier. The relationship is obtained by obtaining a packet length threshold from the HARQ capability negotiation response packet, and sending a HARQ configuration request packet to the receiving end. Step 705: The receiving end feeds back a HARQ configuration response message to the sending end. In step 705, the receiving end sends a HARQ configuration response message to the sending end according to its own situation, where the HARQ configuration response message includes: HARQ synchronization or non-synchronization selection result, HARQ adaptive or non-adaptive selection result. Step 706: The sender acquires an OFDMA subchannel usage right. The OFDMA subchannel refers to the OFDMA subchannel that the sender needs to allocate and reserve first before sending the HARQ capability negotiation request message in step 701. In step 706, the transmitting end allocates and reserves the OFDMA subchannel for the HARQ session, and notifies the receiving end that the OFDMA subchannel is exclusively used by the receiving end and the transmitting end before the end of the HARQ session. The receiving end establishes a mapping relationship between the OFDMA subchannel and the HARQ session identifier.

Step 707: Send a HARQ data packet to the receiving end by using an OFDMA subchannel usage right according to the HARQ session identifier. In step 707, before sending the HARQ data packet to the receiving end according to the HARQ session identifier, the method may include the following steps: Step 7071: The sending end encodes source data. Step 7072: Add a HARQ header to the encoded data, so as to send the HARQ header-added data as a HARQ data packet to the receiving end. Among them, the encoded data can also be backed up and stored. The HARQ data message is then sent to the receiving end through the obtained channel. Step 708: The receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and feeds back the response packet to the sending end according to the HARQ data packet. In step 708, the physical layer of the receiving end detects a signal that is higher than the idle channel estimation threshold, and starts to acquire the pilot sequence. If the acquisition succeeds, the encoding mode and length of the HARQ data packet are obtained, and the HARQ is obtained according to the OFDMA subchannel. The data packet forms a mapping relationship with the HARQ session identifier. Then, the HARQ data packet is demodulated and decoded, and the FCS check is performed on the decoded binary bit number, and the response message is fed back to the transmitting end according to the result of the check.

Further, the acknowledgment message is fed back to the sending end according to the HARQ data packet, and may include the following: if the acquisition pilot sequence succeeds, the FCS check passes, and the ACK is fed back to the transmitting end; if the capturing pilot sequence succeeds, the FCS If the check fails, the second NAK is fed back to the transmitting end; if the acquisition of the pilot sequence fails, the first NAK is fed back to the transmitting end.

The scheme forms a mapping relationship between the HARQ data identifier and the HARQ session identifier by using the OFDMA subchannel, so that the FIQ data packet can be obtained from which sender when the FCS does not pass.

Step 709: The sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to the preset rule.

In step 709, after the transmitting end completes the transmission of the HARQ data packet, it starts to wait for the response message of the receiving end. If the ACK feedback is received, the sender deletes the buffered data packet. The backup and its associated redundant messages, and continue the transmission of other data messages of the traffic flow. If the second NAK feedback is received, the non-self-solvable redundant message can be sent with the same power. If the first NAK feedback is received, the power transmission may be increased to be the same as the current HARQ data message.

Step 710: The receiving end receives the HARQ retransmission data packet sent by the sending end, and decodes the HARQ retransmission data packet. If the receiving end receives the HARQ session ending packet sent by the sending end, the receiving end corresponding to the HARQ session is cleared. In the HARQ data packet and the HARQ session identification step 710, if the receiving end receives the HARQ retransmission data packet sent by the transmitting end, and decoding the HARQ retransmission data packet, the method may include: retransmitting the HARQ data and The buffering of the current HARQ data message is combined and decoded. When the sender receives the ACK, it determines that the data packet is sent successfully. If the service layer of the application layer does not need to send a new data packet, the HARQ session termination packet is sent to the receiver. Otherwise, continue to use the HARQ session to send subsequent data packets to the receiver. The content of the HARQ session end message includes but is not limited to: a HARQ session identifier. At the same time, the transmitting end is configured to establish a mapping relationship with the HARQ session identifier; the HARQ data packet is cleared; and the HARQ session ending packet is sent to the receiving end. The receiving end receives the HARQ session end message, and clears the HARQ data file and the HARQ session identifier corresponding to the HARQ session. In this embodiment, the mapping relationship between the OFDMA subchannel and the HARQ session identifier is established by the transmitting end, and the multi-user collision problem in the HARQ is solved. And the sending end determines whether the data packet is successfully sent according to the received response message received by the receiving end, or performs a retransmission operation according to the preset rule, thereby improving the gain effect of applying the HARQ to the WiFi communication system.

Example 7

This embodiment is based on the foregoing implementation, when the receiving end is compatible with supporting OFDMA, that is, an optimization scheme is supported when both CSMA/CA and OFDMA are supported, and the receiving end does not support special codewords. FIG. 10 is a flowchart of a hybrid automatic repeat request method according to Embodiment 7 of the present invention; Figure. Only the keywords in the steps are shown in FIG. 10, and the specific description is referred to the embodiment. Referring to FIG. 10, the following steps may be specifically included: Step 801: The sending end sends a hybrid automatic repeat request (HARQ capability negotiation request) message to the receiving end. In step 801, the MAC layer of the sending end knows that it needs to send a new service flow to a receiving end, and then creates a new flow identifier TID. The MAC layer of the sending end sends a HARQ capability negotiation request message to the receiving end, and the content of the message includes but is not limited to the following contents:

(1) Whether the receiving end supports HARQ;

(2) Whether the receiving end supports OFDMA;

(3) the length of the message length;

(4) Whether the receiving end supports special code words.

The HARQ capability negotiation request is sent, and the sender can either share the channel through the CSMA/CA or allocate and reserve the OFDMA subchannel. Step 802: The receiving end feeds back a HARQ capability negotiation response message to the sending end.

In step 802, the receiving end feeds back the HARQ capability negotiation response message to the sending end according to the receiving end, including but not limited to the following: supporting HARQ; compatible with OFDMA; the value of the packet length threshold is 256 (this embodiment only gives Example value); Special codewords are not supported. The channel used by the sending end to send the HARQ capability negotiation request message may be a CSMA/CA shared channel or an OFDMA subchannel. Step 803: The receiving end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message. If yes, the receiving end allocates the HARQ session identifier. In step 803, the transmitting end receives the HARQ capability negotiation response message fed back by the receiving end, and determines whether the receiving end supports the HARQ according to the HARQ capability negotiation response message, and if yes, assigns the HARQ session identifier to the receiving end, and then performs step 64; If it is not supported, the current HARQ session is abandoned, and the ARQ and the receiving end are used for communication. Step 804: Generate a mapping relationship between the sender and the HARQ session identifier, and send a configuration request packet including the mapping relationship to the receiver. The scheme is compatible with the OFDMA orthogonal independent subchannel and the CSMA/CA. In the specific step 804, the transmitting end first determines that the receiving end is compatible with the OFDMA according to the HARQ capability negotiation response message, and establishes a mapping relationship between the OFDMA subchannel and the HARQ session identifier. The packet length threshold is obtained from the HARQ capability negotiation response packet and stored. The HARQ configuration request message includes, but is not limited to, a HARQ session identifier, whether the HARQ is synchronized, and whether the HARQ is adaptive. The channel on which the sender sends the HARQ configuration request message may be a CSMA/CA shared channel or an OFDMA subchannel.

Step 805: The receiving end receives the HARQ configuration request message of the sending end, and feeds back the HARQ configuration response message to the sending end. The HARQ configuration response message includes but is not limited to: HARQ synchronization or non-synchronization selection result, HARQ adaptive or non-adaptive selection result. Step 806: The sender acquires a CSMA/CA shared channel usage right or an OFDMA subchannel usage right.

In step 806, if the OFDMA subchannel can be obtained, the OFDMA subchannel is allocated and reserved for the HARQ session, and the receiving end is notified, and the OFDMA subchannel is exclusively used by the receiving end and the transmitting end before the end of the HARQ session. The receiving end establishes a mapping relationship between the OFDMA subchannel and the HARQ session identifier. If the OFDMA subchannel cannot be obtained, the CSMA/CA shared channel usage right is acquired. It should be noted that the channel used before step 806 can be different from the channel obtained in step 806, and the step after step 806 is the same as the channel obtained in step 806. For example, step 806 may be preceded by a CSMA/CA shared channel, and in step 806, the usage right of the OFDMA subchannel may be obtained, and then the OFDMA subchannel is used after step 806.

Certainly, when the CSMA/CA shared channel usage right is acquired in step 806, the process of steps 804 and 805 may not be included in this embodiment. Since the receiving end does not support the special codeword, it is in the CSMA/CA shared channel. The data packet that is smaller than the packet length threshold uses ARQ, and HARQ is used for data packets that are greater than or equal to the packet length threshold.

Step 807: Send a HARQ data packet to the receiving end by using the channel according to the HARQ session identifier.

It can be understood that, in step 806, in order to obtain the OFDMA subchannel usage right, the specific steps of step 807 and the following steps may refer to Embodiment 6, and only the steps are not specific. For the purpose of obtaining the CSMA/CA shared channel usage right in step 806, the specific steps of step 807 and the following steps may refer to Embodiment 5, and only the steps given below are not specifically discussed. Step 808: The receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and feeds back the response packet to the sending end according to the HARQ data packet. Step 809: The sending end receives the response message fed back by the receiving end, and determines, according to the response message, that the data packet is successfully sent or performs a retransmission operation according to a preset rule.

Step 810: The receiving end receives the HARQ retransmission data packet sent by the sending end, and decodes the HARQ retransmission data packet. If the receiving end receives the HARQ session ending packet sent by the sending end, the receiving end clears the Further, the method provided by the embodiment further includes: receiving, by the receiving end, the HARQ session end message sent by the sending end; and clearing the HARQ corresponding to the HARQ session. Data message and HARQ session ID. In this embodiment, a mapping relationship between an OFDMA subchannel and a HARQ session identifier is established, or a HARQ data packet is mapped to a HARQ session identifier, thereby solving a multi-user collision problem in the HARQ. And the sending end determines whether the data packet is successfully sent according to the received response message received by the receiving end or performs a retransmission operation according to the preset rule, thereby improving the gain effect of applying the HARQ to the WiFi communication system.

Embodiment 8 On the basis of the solutions provided in the foregoing embodiments, multiple coordinated transmitting ends may perform HARQ communication to one receiving end. The multiple senders may be connected by a wired network or may be connected by a wireless link. For convenience of description, this embodiment uses two senders as an example, one of which is an auxiliary sender. The embodiment may include the following steps: Step 90: The sending end sends a hybrid automatic retransmission request to the receiving end, and the HARQ capability negotiation request message is sent;

Step 91: The receiving end feeds back a HARQ capability negotiation response message to the sending end. Step 92: The receiving end receives the HARQ capability negotiation response message fed back by the receiving end, and determines, according to the HARQ capability negotiation response message, whether the receiving end supports the HARQ, and if yes, assigns the HARQ session identifier to the receiving end. Step 93: The sending end sends a cooperation request to the auxiliary sending end, where the cooperation request includes the HARQ session identifier. Step 94: The sending end acquires a channel usage right for transmitting the HARQ data packet, and uses the channel according to the HARQ session identifier. The receiving end sends a HARQ data packet.

Redundant data packets of HARQ data packets. Step 96: The receiving end receives the HARQ data packet sent by the sending end according to the HARQ session identifier, and feeds back the response packet to the sending end according to the HARQ data packet. Step 97: The sending end receives the response message fed back by the receiving end, and determines according to the response message.

For the schemes related to the HARQ process of the transmitting end and the receiving end, reference may be made to the descriptions of the foregoing Embodiments 1 to 7, which are not described in detail herein. Optionally, on the basis of the foregoing solution, in step 97, determining, according to the response packet, that the data packet is sent successfully, the method includes: the sending end receiving the response message fed back by the receiving end, where the response message is an ACK And the sending end notifies the auxiliary sending end to delete the HARQ session identifier and the HARQ data packet and the redundant data packet corresponding to the HARQ data packet; if the service flow of the sending end application layer is not If a new data packet needs to be sent, the HARQ session end message is sent to the receiving end. Alternatively, in optional step 97, the retransmission operation is performed by the auxiliary sending end according to the preset rule according to the preset rule, where the sending end receives the response message fed back by the receiving end, where The response message is a retransmission HARQ data message; and the auxiliary sending end is notified to perform a retransmission operation according to a preset rule. The above retransmission operation is in the first embodiment to the seventh embodiment, and the retransmission operation on the transmitting end has been After detailed description,

The redundant data packet is copied to the auxiliary transmitting end, so the auxiliary transmitting end can complete the retransmission operation of the transmitting end of the foregoing embodiment without any difference. The preset rule may include that the sending end selects according to the channel quality, for example, the channel quality of the sending end to the receiving end is good, and then the sending end sends the HARQ retransmission message, and if the channel quality of the auxiliary transmitting end is good, the auxiliary sending is performed. The process of transmitting the HARQ retransmission packet is the same as that in the foregoing embodiment, and details are not described herein again. In this solution, the HARQ communication is coordinated by the auxiliary transmitting end and the transmitting end, thereby improving the stability and throughput of the WiFi network, and improving the gain of the HARQ.

An embodiment of the present invention provides a transmitting end, which is used to implement the foregoing hybrid automatic repeat request method. Referring to FIG. 12, the method includes: a sending unit 111, configured to send a hybrid automatic repeat request (HARQ capability negotiation request) to a receiving end. The receiving unit 112 is configured to receive a HARQ capability negotiation response message fed back by the receiving end, and determine, according to the HARQ capability negotiation response message, whether the receiving end supports the HARQ, and if yes, assign the HARQ session identifier to the receiving end; The method is further configured to: obtain a channel usage right for sending a HARQ data packet, and send a HARQ data packet to the receiving end according to the HARQ session identifier; the receiving unit 112 is further configured to: the sending end receives the response message fed back by the receiving end, According to the response packet, it is determined that the data packet is successfully sent or the retransmission operation is performed according to the preset rule.

Further, as shown in FIG. 12, the receiving end further includes a mapping unit 113, where the mapping unit 113 is configured to generate a mapping relationship between the sending end and the HARQ session identifier, and send, by the sending unit, a configuration request message including a mapping relationship to the receiving end; The receiving unit 112 is configured to receive a configuration request response message sent by the receiving end.

Optionally, the mapping unit 113 is specifically configured to determine, according to the HARQ capability negotiation response message, whether the receiving end supports orthogonal frequency division multiplexing multiple access OFDMA, and if supported, establish a mapping relationship between the subchannel of the OFDMA of the transmitting end and the HARQ session identifier. Optionally, the mapping unit 113 is specifically configured to allocate a corresponding special codeword for the HARQ session, and form a mapping relationship between the HARQ session identifier and the special codeword, where the special codeword is used to mark the sender.

Optionally, the sending unit 11 is specifically configured to mark, by using a channel that sends the HARQ data packet, a right to request to send an RTS frame requesting channel, where the RTS frame includes a HARQ session identifier, a media access layer MAC address of the sending end, and a pair. Channel usage time. The receiving unit 112 is further configured to receive, by the receiving end, the CTS frame sent according to the clearing of the RTS frame, and the CTS frame is used to confirm the channel acquiring right of the transmitting end to send the HARQ data packet, where the CTS frame includes the MAC address of the receiving end and the channel usage time. Optionally, after the sending unit 11 1 is further configured to send the hybrid automatic repeat request HARQ capability negotiation request message, the sending end starts the local timer; if the sending end does not receive the HARQ capability negotiation of the receiving end before the timer expires In response to the message, the sending unit 1 11 resends the HARQ capability negotiation request message and increments the number of retransmissions by one; if the number of retransmissions exceeds the preset value, the HARQ is discarded. Optionally, the channel for sending the HARQ data packet includes: a carrier sense multiple access/collision avoidance CSMA/CA shared channel; or

OFDMA subchannel. Optionally, if the channel is a carrier-sense multi-point access/collision avoiding usage right of the CSMA/CA shared channel, the sending unit 1 11 is specifically configured to: according to the HARQ session identifier, if the length of the HARQ data packet is less than the packet length threshold The DATA/ACK mode is used to send the HARQ data packet to the receiving end through the CSMA/CA shared channel channel. The sending unit 11 1 is specifically configured to identify the HARQ session according to the HARQ session identifier if the length of the HARQ data packet is greater than or equal to the packet length threshold. The HARQ data packet is sent to the receiving end through the CSMA/CA shared channel channel by using the RTS/CTS method.

Optionally, the sending unit 111 is further configured to: determine a packet length of the HARQ data packet; and send, by the HARQ, the HARQ data packet whose length is greater than or equal to the packet length threshold, and the HARQ datagram whose length is smaller than the packet length threshold. The text is sent via ARQ. Optionally, referring to FIG. 13, the sending unit 111 includes:

a coding subunit 1111a, configured to encode source data; obtain a special codeword corresponding to the HARQ session identifier; add a HARQ header to the encoded data; insert the special codeword into the data after adding the HARQ header; The unit 1 112a is configured to send the data with the special codeword inserted as a HARQ data message to the receiving end through the channel. Further, the coding subunit 1 111a is specifically configured to insert a special codeword between the tag signal domain and the data domain of the data to which the HARQ header is added; or

The coding sub-unit 1111a is specifically configured to back up the special codeword, insert the special codeword into the first domain of the physical layer convergence preamble PLCP Preamble, and insert the special codeword backup into the second domain of the PLCP Preamble. Optionally, referring to FIG. 14, the sending unit 111 includes: an encoding subunit 1 111b for encoding source data; adding a HARQ header to the encoded data; and a sending subunit 1112b for adding The HARQ header data is sent as a HARQ data message to the receiving end through the channel.

Optionally, the receiving unit 1 12 is specifically configured to: if the ACK feedback of the receiving end is received, determine that the data packet is successfully sent; or

If the first NAK feedback of the receiving end is received, increase the transmit power to resend the same data as the current HARQ data message; or if the second NAK feedback of the receiving end is received, send the same data as the HARQ data message; Or self-decodeable redundant data different from the HARQ data message; or non-self-decodable redundant data different from the HARQ data message; or if no feedback is received, retransmitted with constant transmit power and this time The same data of the HARQ data message. Optionally, the receiving unit 112 is further configured to: clear the HARQ data packet buffered by the sending end; if the service flow of the sending end does not need to send a new data packet, pass the sending unit. 1 11 Send a HARQ session end message to the receiving end; otherwise, the sending unit 111 continues to use the HARQ session to send subsequent data messages to the receiving end. Optionally, the sending unit 111 is further configured to send a collaboration request to the auxiliary sending end, where the cooperation request includes the HARQ session identifier, and the sending unit 111 is further configured to send the HARQ data packet and the redundant data of the corresponding HARQ data packet to the auxiliary sending end. The receiving unit 112 is specifically configured to receive a response message fed back by the receiving end, according to the response message. ... , ⁵ '' - ' . . Further, referring to FIG. 15, the receiving unit 112 includes: a receiving subunit 1 121a, configured to receive a response message fed back by the receiving end, and the response message is an ACK; and the notification subunit 1 122a is configured to notify the auxiliary sending end to delete The HARQ data packet and the redundant data packet corresponding to the HARQ data packet; if the service flow of the sender does not need to send a new data packet, the HARQ session termination packet is sent to the receiving end. Optionally, referring to FIG. 16, the receiving unit 112 includes: a receiving subunit 1121b, configured to receive a response message fed back by the receiving end, where the response message is a retransmitted HARQ data message; and a notification subunit 1122b, configured to The preset rule notifies the auxiliary sender to perform a retransmission operation.

Mapping the relationship, and transmitting the HARQ data packet to the receiving end according to the HARQ session identifier, and the sending end determines whether the data packet is successfully sent or performs the retransmission operation according to the preset rule according to the received response message fed back by the receiving end, thereby avoiding the HARQ. It is applied to the shared channel multi-user collision problem in the WiFi communication system, and the HARQ gain effect is improved at the same time, and the application range is wide. An embodiment of the present invention provides a receiving end, which is used to implement the foregoing hybrid automatic repeat request method. Referring to FIG. 17, the method includes: a sending unit 121, configured to feed back a HARQ capability negotiation response message to a sending end; The obtaining unit 122 is configured to obtain the HARQ session identifier that is sent by the sending end, and the receiving unit is configured to receive the HARQ data packet sent by the sending end according to the HARQ session identifier.

The sending unit 121 is further configured to feed back the response message to the sending end according to the HARQ data packet received by the receiving unit 121.

Optionally, the obtaining unit 122 is configured to receive a configuration request message sent by the sending end, where the configuration request message includes a mapping relationship between the sending end and the HARQ session identifier, and sends a HARQ configuration response message to the sending end. Optionally, the mapping relationship between the sender and the HARQ session identifier is: a mapping relationship between the HARQ session identifier and the special codeword.

Optionally, the mapping between the sender and the HARQ session identifier is as follows: the sub-channel of the OFDMA of the sender is mapped to the HARQ session identifier.

Optionally, the receiving unit 123 is further configured to: obtain an RTS frame in a channel that sends the HARQ data packet; the sending unit 121 is further configured to feed back the CTS frame to the sending end according to the RTS frame, where the CTS frame is used to confirm that the sending end sends the HARQ data. The channel of the message acquires the right to use, wherein the CTS frame includes the MAC address of the receiving end and the usage time of the channel. Optionally, the receiving unit 123 is further configured to: capture a pilot sequence in the HARQ data packet, and obtain a coded modulation mode and a HARQ data packet length in the HARQ data packet; demodulate and decode the HARQ data packet; The post data is subjected to a frame check sequence FCS check.

Optionally, the receiving unit 123 is further configured to: acquire a pilot sequence; obtain a coded modulation mode and a HARQ data packet length; and establish a mapping relationship between the HARQ data packet and the HARQ session identifier and the service flow according to the OFDMA subchannel information; and the HARQ data. The text is demodulated and decoded; the decoded data is subjected to a frame check sequence FCS check.

Optionally, the receiving unit 123 is further configured to: acquire a pilot sequence; obtain a coded modulation mode and a HARQ data message length; if the RTS frame is received and the CTS is returned, the received HARQ data is sent to the HARQ session identifier and the service flow. Establishing a mapping relationship; demodulating and decoding the HARQ data 4; performing the frame check sequence FCS check on the decoded data. Optionally, the sending unit 121 is specifically configured to receive the HARQ data packet from the receiving end. Obtaining a special codeword, and mapping the HARQ data packet with the HARQ session identifier and the service flow according to the special codeword;

If the FCS check passes, the ACK is fed back to the sender; or, if the special codeword identification is passed, and the FCS check fails, the second NAK is fed back to the sender; or

If the special codeword identification does not pass, the FCS check fails, and in the RTS/CTS mode or the OFDMA mode, the second NAK is fed back to the transmitting end; or,

If the special codeword identification does not pass, the FCS check does not pass, and in the DATA/ACK mode, no information is fed back to the sender; or,

If the acquisition of the pilot sequence fails, in the DATA/ACK mode, no information is fed back to the sender; or,

If the acquisition pilot sequence fails, in RTS/CTS mode or OFDMA mode, the first NAK: is fed back to the transmitting end. Optionally, the sending unit 121 is specifically configured to: if the FCS check passes, feed back an ACK to the sending end; or, if the FCS check fails, feed back the second NAK to the sending end; optionally, the sending unit 121 is specifically configured to: If the FCS check passes, the ACK is fed back to the transmitting end; or, if the FCS check fails, in the RTS/CTS mode, the second NAK is fed back to the transmitting end; or,

If the FCS check fails, not in RTS/CTS mode, no information is fed back to the sender.

Optionally, the receiving unit 123 is further configured to cache the current HARQ data packet. Optionally, the receiving unit 123 is further configured to receive the HARQ retransmission data sent by the sending end, and decode the HARQ retransmission data.

Optionally, the receiving unit 123 is specifically configured to: decode the HARQ retransmission data; or combine the HARQ retransmission data and the buffered current HARQ data packet to perform decoding. Optionally, the receiving unit 123 is further configured to: receive the HARQ session end message sent by the sending end; and clear the HARQ data message and the HARQ session identifier corresponding to the HARQ session. The receiving end provided by the embodiment of the present invention can establish a mapping relationship between the transmitting end and the HARQ session identifier, and send the HARQ data packet to the receiving end according to the HARQ session identifier, and the sending end responds to the received response message according to the received receiving end. The data packet is sent successfully or the retransmission operation is performed according to the preset rule, which avoids the multi-user collision problem of the shared channel in the HARQ application to the WiFi communication system, and improves the HARQ gain effect, and is applicable to a wide range. An embodiment of the present invention provides a transmitting end, as shown in FIG. 18, comprising: a transmitter 131, a receiver 132, a processor 133, a memory 134, and a bus 135, wherein the transmitter 131, the receiver 132, the processor 133, and The memory 132 is connected to each other through a bus 135 for storing program code executed by the processor 133; the bus 135 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component), and an external device interconnection. ) Bus or EISA (Extended Industry Standard Architecture) bus. The bus 135 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 18, but it does not mean that there is only one bus or one type of bus. among them:

Memory 134 is for storing executable program code, the program code including computer operating instructions. Memory 134 may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory. The transmitter 131 is configured to send a hybrid automatic repeat request HARQ capability negotiation request message to the receiving end;

The receiver 132 is configured to receive a HARQ capability negotiation response message fed back by the receiving end, and the processor 133 is configured to determine, according to the HARQ capability negotiation response message, whether the receiving end supports the HARQ, and if yes, assign the HARQ session identifier to the receiving end; The device 133 is further configured to: obtain a channel usage right for transmitting the HARQ data packet, and send the HARQ data to the receiving end according to the HARQ session identifier; the receiver 132 is configured to receive the response message fed back by the receiving end, and the processor 133 It is further configured to determine, according to the response packet, that the data packet is successfully sent or performs a retransmission operation according to a preset rule. Optionally, the processor 133 is further configured to: generate a mapping relationship between the sending end and the HARQ session identifier, and send, by using the transmitter 131, a configuration request message including a mapping relationship to the receiving end; the receiver 132 is configured to receive the configuration sent by the receiving end. Request response message. Optionally, the processor 133 is configured to determine, according to the HARQ capability negotiation response message, whether the receiving end supports orthogonal frequency division multiplexing multiple access OFDMA, and if supported, establish a mapping relationship between the subchannel of the OFDMA of the transmitting end and the HARQ session identifier. Optionally, the processor 133 is specifically configured to allocate a corresponding special codeword to the HARQ session, and form a mapping relationship between the HARQ session identifier and the special codeword, where the special codeword is used to mark the sender.

Optionally, the processor 133 is configured to: in the channel that sends the HARQ data packet, mark the use right of requesting to send the RTS frame request channel, where the RTS frame includes the HARQ session identifier, the media access layer MAC address of the sending end, and the pair of channels. The receiver 132 is configured to receive the CTS frame sent by the receiving end according to the RTS frame feedback, and the CTS frame is used to confirm the channel access right of the transmitting end to send the HARQ data message, where the CTS frame includes the MAC address of the receiving end and The time of use of the channel. Optionally, after the transmitter 132 is configured to send the hybrid automatic repeat request HARQ capability negotiation request, the sending end starts the local timer; if the sending end does not receive the HARQ capability negotiation response of the receiving end before the timer expires The message is retransmitted by the transmitter 132 to the HARQ capability negotiation request message, and the number of retransmissions is incremented by one; if the number of retransmissions exceeds the preset value, the HARQ is discarded. Optionally, the channel for sending the HARQ data packet includes: a carrier sense multiple access/collision avoidance CSMA/CA shared channel; or

OFDMA subchannel. Optionally, if the channel is a carrier sense multi-point access/collision avoiding usage right of the CSMA/CA shared channel, the transmitter 132 is specifically configured to: according to the HARQ session identifier, if the length of the HARQ data packet is less than the packet length threshold Transmitting a HARQ data packet to the receiving end on the CSMA/CA shared channel channel by using the DATA/ACK method; or the transmitter 132 is specifically configured to: if the length of the HARQ data packet is greater than or equal to the packet length For the threshold, the HARQ data packet is sent to the receiving end on the CSMA/CA shared channel channel according to the HARQ session identifier in the RTS/CTS manner.

Optionally, the processor 133 is further configured to: determine a packet length of the HARQ data packet; and send the HARQ data packet whose length is greater than or equal to the packet length threshold by using HARQ, and the HARQ datagram whose length is smaller than the packet length threshold. The text is sent via ARQ.

Optionally, the processor 133 is configured to: encode the source data; obtain a special codeword corresponding to the HARQ session identifier; add the HARQ header to the encoded data; and insert the special codeword into the data after adding the HARQ header; The transmitter 132 is further configured to send the data in which the special codeword is inserted as a HARQ data message to the receiving end through the channel.

Optionally, the processor 133 is specifically configured to insert a special codeword into the tag signal field and the data domain of the data added with the HARQ header; or

The processor 133 is specifically configured to specifically back up the special codeword, insert the special codeword into the first domain of the physical layer PLCP Preamble, and insert the special codeword backup into the second domain of the PLCP Preamble. Optionally, the processor 133 is configured to encode the source data, and the HARQ header is added to the encoded data. The transmitter 132 is configured to send the HARQ data packet as a HARQ data packet to the receiving end through the channel.

Optionally, the processor 133 is configured to determine that the data packet is successfully sent if the ACK feedback of the receiving end is received by the receiver 132; or

The receiver 132 receives the first NAK feedback from the receiving end, and the transmitter 132 is configured to increase the transmit power retransmission and the same data of the current HARQ data message; or the receiver 132 receives the second NAK feedback of the receiving end, and then transmits The machine 132 is configured to transmit the same data as the HARQ data message; or the self-decodeable redundant data different from the HARQ data message; or the non-self-decodeable redundant data different from the HARQ data message; or if the receiver 132 does not receive feedback, then the transmitter 131 is used to transmit with constant transmit power. Rate resend the same data as this HARQ data message. Optionally, the processor 133 is further configured to: clear the HARQ data packet buffered by the sending end; if the service stream of the sending end does not need to send a new data packet, the transmitter 131 is configured to send the HARQ session ending message to the receiving end; Otherwise, the transmitter 131 continues to use the HARQ session to send subsequent data messages to the receiving end. Optionally, the transmitter 131 is configured to send a collaboration request to the auxiliary sending end, where the cooperation request includes a HARQ session identifier, and the transmitter 131 is configured to send the HARQ data packet and the redundant datagram corresponding to the HARQ data packet to the auxiliary sending end. The receiver 132 is configured to receive a response message fed back by the receiving end, and the processor 133 is configured to perform an operation according to the retransmission. Optionally, the receiver 132 is configured to receive the response message fed back by the receiving end, and the response message is an ACK. The transmitter 132 is configured to notify the auxiliary sending end to delete the HARQ data message and the corresponding HARQ data message. The redundant data packet is sent by the transmitter 131 to the receiving end if the service stream of the transmitting end does not need to send a new data packet. Optionally, the receiver 131 is configured to receive the response message fed back by the receiving end, and the response message is a retransmission HARQ data message. The transmitter 132 is configured to notify the auxiliary sending end according to the preset rule according to the preset rule. Pass the operation.

Mapping the relationship, and transmitting the HARQ data packet to the receiving end according to the HARQ session identifier, and the sending end determines whether the data packet is successfully sent or performs the retransmission operation according to the preset rule according to the received response message fed back by the receiving end, thereby avoiding the HARQ. It is applied to the shared channel multi-user collision problem in the WiFi communication system, and the HARQ gain effect is improved at the same time, and the application range is wide. An embodiment of the present invention provides a receiving end, as shown in FIG. 19, comprising: a transmitter 141, a receiver 142, a processor 143, a memory 144, and a bus 145, wherein the transmitter 141, the receiver 142, the processor 143, and The memory 144 is connected to each other through the bus 145 to communicate with each other. The memory 144 is configured to store program code executed by the processor 143;

The bus 145 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component) bus, or an EISA (Extended Industry Standard Architecture) bus. The bus 145 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 19, but it does not mean that there is only one bus or one type of bus. among them:

Memory 144 is for storing executable program code, including computer operating instructions. Memory 134 may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory.

The processor 143 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more configured to implement the embodiments of the present invention. integrated circuit.

Specifically, the transmitter 141 is configured to feed back a HARQ capability negotiation response message to the sending end, and the processor 143 is further configured to obtain a HARQ session identifier that is allocated by the sending end.

The receiver 142 is configured to receive, according to the HARQ session identifier, a HARQ data packet sent by the sending end.

The transmitter 141 is configured to feed back a response message to the sender according to the received HARQ data message.

Optionally, the receiver 142 is configured to receive a configuration request message sent by the sending end, where the configuration request message includes a mapping relationship between the sending end and the HARQ session identifier, and the transmitter 141 is configured to send the HARQ configuration response to the sending end. .

Optionally, the mapping relationship between the sender and the HARQ session identifier is: a mapping relationship between the HARQ session identifier and the special codeword.

Optionally, the processor 143 is further configured to: obtain an RTS frame in a channel that sends the HARQ data packet; the transmitter 141 is configured to feed back the CTS frame to the sending end according to the RTS frame, where the CTS frame is used to confirm that the sending end sends the HARQ datagram. Channel access rights, where the CTS frame contains The MAC address of the receiving end and the time of use of the channel. Optionally, the processor 143 is further configured to: capture a pilot sequence in the HARQ data packet, and obtain a coded modulation mode and a HARQ data message length in the HARQ data packet; demodulate and decode the HARQ data packet; The post data is subjected to a frame check sequence FCS check. Optionally, the processor 143 is further configured to: acquire a pilot sequence; obtain a coded modulation mode and a length of the HARQ data packet; and establish a mapping relationship between the HARQ data packet and the HARQ session identifier and the service flow according to the OFDMA subchannel information; The text is demodulated and decoded; the decoded data is subjected to a frame check sequence FCS check. Optionally, the processor 143 is further configured to: acquire a pilot sequence; obtain a coded modulation mode and a HARQ data message length; if the RTS frame is received and the CTS is replied, the received HARQ data is sent to the HARQ session identifier and the service flow. Establishing a mapping relationship; demodulating and decoding the HARQ data 4; performing the frame check sequence FCS check on the decoded data.

Optionally, the processor 143 is configured to: obtain a special codeword from the HARQ data packet received by the receiving end, and establish a mapping relationship between the HARQ data packet and the HARQ session identifier and the service flow according to the special codeword; if the FCS check passes, Then, the transmitter 141 feeds back an ACK to the transmitting end; or, if the special codeword identification passes, and the FCS check fails, the transmitter 141 feeds back the second NAK to the transmitting end; or

If the special codeword identification does not pass, the FCS check fails, the RTS/CTS mode or the OFDMA mode, the transmitter 141 is used to feed back the second NAK to the transmitting end; or,

If the acquisition pilot sequence fails, in the RTS/CTS mode or the OFDMA mode, the transmitter 141 is configured to feed back the first NAK: to the transmitting end. Optionally, the processor 143 is specifically configured to: when the FCS check passes, the transmitter 141 is configured to feed back an ACK to the sending end; or, If the FCS check fails, the transmitter 141 is configured to feed back the second NAK to the transmitting end. Optionally, the transmitter 141 is specifically configured to: if the FCS check passes, feed back an ACK to the sending end; or, if the FCS check fails, in the RTS/CTS mode, the transmitter 141 is configured to feed back the second NAK to the transmitting end; Or, if the FCS check fails, not in the RTS/CTS mode, no information is fed back to the sender. Optionally, the memory 144 is configured to cache the current HARQ data packet. Optionally, the receiver 142 is further configured to receive the HARQ retransmission data sent by the sending end, and the processor 143 is configured to decode the HARQ retransmission data. Optionally, the processor 143 is specifically configured to: decode the HARQ retransmission data; or combine the HARQ retransmission data and the current HARQ data packet to perform decoding. Optionally, the receiver 142 is further configured to receive the HARQ session end message sent by the sending end, and the processor 143 is configured to clear the HARQ data message and the HARQ session identifier corresponding to the HARQ session. The receiving end of the present invention provides a mapping relationship between the transmitting end and the HARQ session identifier, and sends a HARQ data packet to the receiving end according to the HARQ session identifier, and the sending end responds to the received response message received by the receiving end. It is determined that the data packet is successfully sent or the retransmission operation is performed according to the preset rule, which avoids the multi-user collision problem of the shared channel in the HARQ application to the WiFi communication system, and improves the HARQ gain effect, and has a wide application range. An embodiment of the present invention provides a communication system, as shown in FIG. 20, including a receiving end 151 and a transmitting end 153 for communicating with each other, for implementing the hybrid automatic repeat request method provided by the foregoing method embodiment, where the sending end is the above Any of the transmitting ends provided by the device embodiment, and the receiving end is any receiving end provided by the foregoing device embodiment. The communication system provided by the embodiment of the present invention establishes a mapping relationship between the transmitting end and the HARQ session identifier, and sends a HARQ data packet to the receiving end according to the HARQ session identifier, and the sending end responds to the received response message received by the receiving end. Determining that the data packet is sent successfully or performing a retransmission operation according to a preset rule, thereby avoiding the multi-user collision problem of the shared channel in the HARQ application to the WiFi communication system, and improving the HARQ gain effect, and the application range is wide. Pan.

From the description of the above embodiments, it will be apparent to those skilled in the art that the present invention can be implemented in hardware, or firmware implementation, or a combination thereof. The functions described above may be stored on or transmitted as one or more instructions or code on a computer readable medium when using software implementation. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a computer. For example, but not limited to: the computer readable medium may include RAM (Random Access Memory), ROM (Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory). Read memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, disk storage media or other magnetic storage device, or can be used to carry or store desired programs in the form of instructions or data structures. Code and any other medium that can be accessed by a computer. Also. Any connection can be appropriate as a computer readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL (Digital Subscriber Line), or wireless technologies such as infrared, radio, and microwave, Then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the associated medium. As used in the present invention, the disc and the disc include a CD (Compact Disc), a laser disc, a disc, a DVD disc (Digital Versatile Disc), a floppy disc, and a Blu-ray disc, wherein the disc is usually magnetically copied, The disc uses a laser to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media. The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

claims

1. A hybrid automatic retransmission request method, characterized by including:

The sending end sends a hybrid automatic repeat request HARQ capability negotiation request message to the receiving end; the sending end receives the HARQ capability negotiation response message fed back by the receiving end, and determines the reception according to the HARQ capability negotiation response message Whether the end supports HARQ, and if so, allocate a HARQ session identifier to the receiving end; obtain the channel usage right to send HARQ data messages, and send HARQ datagrams to the receiving end through the channel according to the HARQ session identifier The sending end receives the response message fed back by the receiving end, and determines according to the response message that the data message is successfully sent or performs a retransmission operation according to preset rules.

2. The method according to claim 1, characterized in that, before obtaining the channel usage right for sending HARQ data messages, the method further includes:

Generate a mapping relationship between the sending end and the HARQ session identifier, and send a configuration request message containing the mapping relationship to the receiving end;

The sending end receives the configuration request response message sent by the receiving end.

3. The method according to claim 2, characterized in that: generating a mapping relationship between the sending end and the HARQ session identifier includes: the sending end determines the HARQ capability negotiation response message according to the Whether the receiving end supports Orthogonal Frequency Division Multiple Access OFDMA, and if so, establish a mapping relationship between the OFDMA sub-channel of the sending end and the HARQ session identifier.

4. The method according to claim 2, characterized in that generating the mapping relationship between the sending end and the HARQ session identifier includes:

The sending end allocates corresponding special codewords for the HARQ session, and forms a mapping relationship between the HARQ session identifier and the special codewords. The special codewords are used to mark the sending end.

5. The method according to claim 1, characterized in that, obtaining the channel usage right for sending HARQ data messages includes: the sending end requests to send RTS by marking in the channel for sending HARQ data messages The frame requests the right to use the channel, wherein the RTS frame includes the HARQ session identifier, the media access layer MAC address of the sending end, and the usage time of the channel; the sending end receives the receiving end according to The RTS frame feedback is cleared and a CTS frame is sent. The CTS frame is used to confirm that the sending end obtains the right to use the channel for sending HARQ data messages, where the CTS frame includes the MAC address of the receiving end and the The usage time of the channel.

6. The method according to claim 1, characterized in that: the sending end sends a hybrid automatic repeat request HARQ capability negotiation request message to the receiving end, further comprising: the sending end sends the hybrid automatic repeat request HARQ capability After negotiating the request message, the sending end starts the local timer;

If the sending end does not receive the HARQ capability negotiation response message from the receiving end before the timer expires, the sending end resends the HARQ capability negotiation request message and adds 1 to the number of retransmissions; If the number of retransmissions exceeds the preset value, this HARQ is given up.

7. The method according to claim 1, characterized in that the channel for sending HARQ data messages includes: carrier sensing multi-point access/collision avoidance CSMA/CA shared channel; or

OFDMA sub-channel.

8. The method according to claim 7, characterized in that, if the channel is a carrier sensing multi-point access/collision avoidance CSMA/CA shared channel use right, then the HARQ session identifier is passed through the The channel sends a HARQ data message to the receiving end, including: if the length of the HARQ data message is less than the message length threshold, using the DATA/ACK mode according to the HARQ session identifier through the CSMA/CA shared channel The channel sends a HARQ data message to the receiving end; or if the length of the HARQ data message is greater than or equal to the message length threshold, the RTS/CTS mode is used according to the HARQ session identifier to share the channel through the CSMA/CA The channel sends HARQ data packets to the receiving end.

9. The method according to claim 5, characterized in that: sending a HARQ data message to the receiving end through the channel according to the HARQ session identifier, further comprising: Determine the message length of the HARQ data message; HARQ data messages whose length is greater than or equal to the message length threshold are sent through HARQ, and HARQ data messages whose length is less than the message length threshold are sent through ARQ.

10. The method according to claim 4, characterized in that: sending a HARQ data message to the receiving end through the channel according to the HARQ session identifier includes: the sending end encoding the source data;

Obtaining a special codeword corresponding to the HARQ session identifier; adding a HARQ header to the encoded data; inserting a special codeword into the data after adding the HARQ header;

The data with special code words inserted is sent to the receiving end through the channel as a HARQ data message.

11. The method according to claim 10, wherein the inserting the special codeword into the data with the HARQ header added includes: inserting the special codeword into the mark signal field and the data field of the data with the HARQ header added. time; or,

The special codeword is backed up, the special codeword is inserted into the first field of the physical layer convergence preamble domain PLCP Preamble, and the special codeword backup is inserted into the second field of the PLCP Preamble.

12. The method according to claim 1, characterized in that: sending a HARQ data message to the receiving end through the channel according to the HARQ session identifier includes: the sending end encoding the source data;

Add a HARQ header to the encoded data; send the data with the HARQ header added as a HARQ data message to the receiving end through the channel.

13. The method according to claim 1, wherein the sending end receives the response message fed back by the receiving end, and determines according to the response message that the data message is successfully sent or performs a retransmission operation according to preset rules, including : If the ACK feedback from the receiving end is received, it is determined that the data message is sent successfully; or if the first NAK feedback from the receiving end is received, the transmit power is increased and the same data as the current HARQ data message is retransmitted; or If the second NAK feedback from the receiving end is received, the same data as the HARQ data message is sent; or self-decodable redundant data that is different from the HARQ data message; or the HARQ data message is sent redundant data with different messages and cannot be self-decoded; or if no feedback is received, the same data as the current HARQ data message is re-transmitted with constant transmit power.

14. The method according to claim 13, characterized in that, if an ACK feedback from the receiving end is received, it is determined that the data message is sent successfully, and further comprising: clearing the HARQ data message cached by the sending end. arts;

If there is no new data packet to be sent in the business flow of the sending end, a HARQ session end message is sent to the receiving end; otherwise, the HARQ session is continued to be used to send subsequent data packets to the receiving end.

15. The method according to any one of claims 1 to 14, characterized in that, before the sending end receives the response message fed back by the receiving end, it further includes: the sending end sends cooperation to the auxiliary sending end. request, the cooperation request includes the HARQ session identifier;

The redundant data message of the HARQ data message; the sending end receives the response message fed back by the receiving end, and determines that the data message is successfully sent according to the response message or performs a retransmission operation according to preset rules, including : The sending end receives the response message fed back by the receiving end, and determines according to the response message that the data message is successfully sent or performs a retransmission operation through the auxiliary sending end according to preset rules.

16. The method according to claim 15, characterized in that the sending end receives the response message fed back by the receiving end, and determines that the data message is sent successfully according to the response message, including: The sending end receives the response message fed back by the receiving end, and the response message is ACK;

redundant data packets of the HARQ data packet; if there is no new data packet to be sent in the business flow of the sending end, a HARQ session end message is sent to the receiving end.

17. The method according to claim 15, characterized in that, the sending end receives the response message fed back by the receiving end, and according to the response message, the auxiliary sending end performs retransmission according to preset rules. The operation includes: the sending end receiving a response message fed back by the receiving end, where the response message is a retransmission HARQ data message; and according to the response message, notifying the auxiliary sending end to execute according to preset rules. Retransmission operation.

18. A hybrid automatic repeat request method, characterized in that it includes: the receiving end feeds back a HARQ capability negotiation response message to the sending end; the receiving end obtains the HARQ session identifier assigned by the sending end; the receiving end obtains the HARQ session identifier assigned by the sending end; The HARQ session identifier receives the HARQ data message sent by the sending end, and feeds back a response message to the sending end according to the HARQ data message.

19. The method according to claim 18, characterized in that, the receiving end obtains the HARQ session identifier allocated by the sending end, including: the receiving end receives the configuration request message sent by the sending end, wherein the The configuration request message includes a mapping relationship between the sending end and the HARQ session identifier; the receiving end sends a HARQ configuration response message to the sending end.

20. The method according to claim 19, wherein the mapping relationship between the sending end and the HARQ session identifier is: the mapping relationship between the HARQ session identifier and the special codeword.

21. The method according to claim 19, wherein the mapping relationship between the sending end and the HARQ session identifier is: a mapping relationship is established between the OFDMA sub-channel of the sending end and the HARQ session identifier.

22. The method according to claim 18, characterized in that, before the receiving end receives the HARQ data message sent by the sending end according to the HARQ session identifier, the receiving end further includes: the receiving end transmits the HARQ data. Obtain an RTS frame from the channel of the message; Feed back a CTS frame to the sending end according to the RTS frame, and the CTS frame is used to confirm that the sending end obtains the right to use the channel for sending the HARQ data message, wherein the The CTS frame includes the MAC address of the receiving end and the usage time of the channel.

23. The method according to claim 20, characterized in that: the receiving end receives the HARQ data message sent by the sending end according to the HARQ session identifier, further comprising: capturing a pilot in the HARQ data message sequence, and obtain the coding modulation mode and HARQ data message length in the HARQ data message; demodulate and decode the HARQ data message; and perform frame check sequence FCS inspection on the decoded data.

24. The method according to claim 21, characterized in that, the receiving end receives the HARQ data message sent by the sending end according to the HARQ session identifier, further comprising: acquiring a pilot sequence; obtaining a coding modulation mode and The length of the HARQ data message; establishing a mapping relationship between the HARQ data message and the HARQ session identifier and service flow according to the OFDMA sub-channel information; demodulating and decoding the HARQ data message; framing the decoded data Check sequence FCS check.

25. The method according to claim 22, characterized in that: the receiving end receives the HARQ data message sent by the sending end according to the HARQ session identifier, further comprising: acquiring a pilot sequence; obtaining a coding modulation mode and The length of the HARQ data message; if the RTS frame is received and the CTS frame is replied to, establish a mapping relationship between the received HARQ data message and the HARQ session identifier and service flow; demodulate the HARQ data message and decoding; The decoded data is checked by the frame check sequence FCS.

26. The method according to claim 23, characterized in that, feeding back a response message to the sending end according to the HARQ data message includes: obtaining a special codeword from the HARQ data message, and according to the special code Establish a mapping relationship between the HARQ data text and the HARQ session identifier and service flow; if the FCS check passes, feed back ACK to the sending end; or, if the special codeword identification passes, FCS If the check fails, the second NAK is fed back to the sending end; or, if the special codeword identification fails, the FCS check fails, in RTS/CTS mode or OFDMA mode, the second NAK is fed back to the sending end. ; Or, if the special codeword identification fails, the FCS check fails, and no information is fed back to the sending end in DATA/ACK mode; or,

If the acquisition of the pilot sequence fails, no information is fed back to the sending end in DATA/ACK mode; or,

If the acquisition of the pilot sequence fails, in RTS/CTS mode or OFDMA mode, the first - NAK: is fed back to the sending end.

27. The method according to claim 24, wherein the feedback of a response message to the sending end according to the HARQ data message includes:

If the FCS check passes, an ACK is fed back to the sending end; or, if the FCS check fails, a second NAK is fed back to the sending end:

28. The method according to claim 25, wherein the feedback of a response message to the sending end according to the HARQ data message includes:

If the FCS check passes, an ACK is fed back to the sending end; or, if the FCS check fails, in RTS/CTS mode, a second NAK is fed back to the sending end; or, if the FCS check If it fails and is not in RTS/CTS mode, no information will be fed back to the sending end.

29. The method according to any one of claims 26 to 28, characterized in that, after feeding back the second NAK to the sending end, the method further includes: caching this HARQ data message.

30. The method according to any one of claims 26 to 28, characterized in that, after feeding back a response message to the sending end according to the result of the check, it further includes: the receiving end receives the sending HARQ retransmission data sent by the terminal;

Decode the HARQ retransmission data.

31. The method according to claim 30, characterized in that: decoding the HARQ retransmission data includes:

Decode the HARQ retransmission data; or decode the HARQ retransmission data and cache this HARQ data message after combining them.

32. The method according to claim 18, characterized in that, after feeding back a response message to the sending end according to the check result, further comprising: the receiving end receiving the HARQ sent by the sending end. Session end message;

Clear the HARQ data message and HARQ session identifier corresponding to the HARQ session.

33. A sending end, characterized in that it includes: a sending unit, configured to send a hybrid automatic repeat request HARQ capability negotiation request message to the receiving end;

A receiving unit, configured to receive the HARQ capability negotiation response message fed back by the receiving end, determine whether the receiving end supports HARQ according to the HARQ capability negotiation response message, and if so, allocate a HARQ session to the receiving end. logo;

The sending unit is also used to obtain the channel usage right for sending HARQ data messages, and send HARQ data messages to the receiving end through the channel according to the HARQ session identifier;

The receiving unit is also configured for the sending end to receive the response message fed back by the receiving end, According to the response message, it is determined that the data message is sent successfully or a retransmission operation is performed through the sending unit according to preset rules.

34. The sending end according to claim 33, characterized in that the receiving end further includes a mapping unit,

system, and sends a configuration request message containing the mapping relationship to the receiving end through the sending unit;

35. The sending end according to claim 34, characterized in that the mapping unit is specifically configured to determine whether the receiving end supports Orthogonal Frequency Division Multiple Access Multiple Access OFDMA according to the HARQ capability negotiation response message. If If supported, a mapping relationship is established between the OFDMA sub-channel of the sending end and the HARQ session identifier.

36. The transmitter according to claim 34, wherein the mapping unit is specifically configured to allocate corresponding special codewords to the HARQ session, and form a mapping relationship between the HARQ session identifier and the special codewords. , the special codeword is used to mark the sending end.

37. The sending end according to claim 33, characterized in that, the sending unit is specifically configured to request the right to use the channel by marking a request to send an RTS frame in the channel for sending the HARQ data message, wherein the RTS The frame includes the HARQ session identifier, the media access layer MAC address of the sending end, and the usage time of the channel; the receiving unit is also configured to receive the CTS frame sent by the receiving end according to the clearing of the RTS frame feedback , the CTS frame is used to confirm that the sending end obtains the right to use the channel for sending HARQ data messages, where the CTS frame includes the MAC address of the receiving end and the usage time of the channel.

38. The sending end according to claim 33, wherein the sending unit is further configured to start a local timer after sending the hybrid automatic repeat request HARQ capability negotiation request message; if Before the timer expires, if the sending end does not receive the HARQ capability negotiation response message from the receiving end, then the sending end resends the HARQ capability negotiation request message and adds 1 to the number of retransmissions; if it is retransmitted, When the number of transmissions exceeds the preset value, this HARQ is given up.

39. The sending end according to claim 33, characterized in that the channel for sending HARQ data messages includes: carrier sensing multi-point access/collision avoidance CSMA/CA shared channel; or

OFDMA sub-channel.

40. The sending end according to claim 39, characterized in that, if the channel is a carrier sensing multi-point access/collision avoidance CSMA/CA shared channel, the sending unit is specifically used if HARQ data If the message length is less than the message length threshold, the HARQ data message is sent to the receiving end through the CSMA/CA shared channel in the DATA/ACK mode according to the HARQ session identifier; or the sending unit specifically Used to, if the length of the HARQ data message is greater than or equal to the message length threshold, use the RTS/CTS mode according to the HARQ session identifier to send the HARQ data message to the receiving end through the CSMA/CA shared channel channel. .

41. The sending end according to claim 37, characterized in that, the sending unit is also used to: determine the message length of the HARQ data message; for HARQ data messages whose length is greater than or equal to the message length threshold The message is sent through HARQ, and the HARQ data message whose length is smaller than the message length threshold is sent through ARQ.

42. The sending end according to claim 36, characterized in that the sending unit includes:

Encoding subunit, used to encode source data; obtain special codewords corresponding to the HARQ session identifier; add a HARQ header to the encoded data; insert special codewords after the added HARQ header data; a sending subunit, configured to send the data with the special codeword inserted as a HARQ data message to the receiving end through the channel.

43. The sending end according to claim 42, characterized in that, the encoding subunit is specifically used to insert the special codeword between the mark signal field and the data field of the data added with the HARQ header; or, Enter the first field of the physical layer convergence preamble field PLCP Preamble, and insert the special codeword backup into the second field of the PLCP Preamble.

44. The sending end according to claim 33, characterized in that the sending unit includes:

Encoding subunit, used to encode source data; add a HARQ header to the encoded data;

A sending subunit, configured to send the data with the added HARQ header as a HARQ data message to the receiving end through the channel.

45. The sending end according to claim 33, the receiving unit, specifically configured to determine that the data message is successfully sent if an ACK feedback from the receiving end is received; or if a first NAK feedback from the receiving end is received. , then increase the transmit power and re-send the same data as the current HARQ data message; or if the second NAK feedback from the receiving end is received, then send the same data as the HARQ data message; or if the same data as the HARQ data message is received, Self-decodable redundant data that is different from the data message; or non-self-decodable redundant data that is different from the HARQ data message; or if no feedback is received, retransmit and this HARQ with constant transmit power The same data as the datagram.

46. The sending end according to claim 45, characterized in that, the receiving unit is also used to clear the HARQ data message cached by the sending end; if the service flow of the sending end does not have a new data message If sending is required, the sending unit sends a HARQ session end message to the receiving end; otherwise, the sending unit continues to use the HARQ session to send subsequent data messages to the receiving end.

47. The sending end according to any one of claims 33 to 46, characterized in that,

Contains the HARQ session identifier;

Redundant data packets corresponding to the HARQ data packets; The receiving unit is specifically configured to receive a response message fed back by the receiving end, and determine according to the response message that the data message is successfully sent or perform a retransmission operation through the auxiliary sending end according to preset rules.

48. The sending end according to claim 47, wherein the receiving unit includes: a receiving subunit, configured to receive a response message fed back by the receiving end, where the response message is ACK; and a notification subunit. , used to notify the auxiliary sending end to delete the HARQ data message and the redundant data message corresponding to the HARQ data message;

If there is no new data packet to be sent in the service flow of the sending end, a HARQ session end message is sent to the receiving end.

49. The method according to claim 47, characterized in that, the receiving unit includes: a receiving subunit, used for the sending end to receive the response message fed back by the receiving end, and the response message is a retransmission HARQ data message; a notification subunit, configured to notify the auxiliary sending end to perform a retransmission operation according to the preset rules according to the response message received by the receiving subunit.

50. A receiving end, characterized in that it includes: a sending unit, used to feed back a HARQ capability negotiation response message to the sending end; an obtaining unit, used to obtain the HARQ session identifier allocated by the sending end; a receiving unit, used to Receive the HARQ data message sent by the sending end according to the HARQ session identifier; the sending unit is also configured to feed back a response message to the sending end according to the HARQ data message received by the receiving unit.

51. The receiving end according to claim 50, characterized in that the obtaining unit is specifically configured to receive a configuration request message sent by the sending end, wherein the configuration request message includes the sending end and the Mapping relationship of HARQ session identifiers; sending a HARQ configuration response text to the sending end.

52. The receiving end according to claim 51, characterized in that: the sending end and the The mapping relationship between the HARQ session identifier is: the mapping relationship between the HARQ session identifier and the special codeword.

53. The receiving end according to claim 51, characterized in that the mapping relationship between the sending end and the HARQ session identifier is: the OFDMA sub-channel of the sending end establishes a mapping relationship with the HARQ session identifier.

54. The receiving end according to claim 50, characterized in that,

frame; ' . . ,

The sending unit is also configured to feed back a CTS frame to the sending end according to the RTS frame. The CTS frame is used to confirm that the sending end obtains the right to use the channel for sending the HARQ data message, wherein the CTS The frame contains the MAC address of the receiving end and the usage time of the channel.

55. The receiving end according to claim 52, characterized in that,

Obtain the coding modulation mode and HARQ data message length from the HARQ data message; demodulate and decode the HARQ data message; and perform frame check sequence FCS inspection on the decoded data.

56. The receiving end according to claim 53, characterized in that: the receiving unit is also used to capture a pilot sequence; obtain the coding modulation mode and the HARQ data message length; and convert the HARQ data 4 according to the OFDMA sub-channel information. Establish a mapping relationship between the Gen message and the HARQ session identifier and the service flow; demodulate and decode the HARQ data message; and perform frame check sequence FCS inspection on the decoded data.

57. The receiving end according to claim 54, characterized in that: the receiving unit is also used to capture a pilot sequence; obtain the coding modulation mode and the HARQ data message length; and reply to the RTS frame if the RTS frame is received. CTS: Establish a mapping relationship between the received HARQ data message and the HARQ session identifier and service flow; demodulate and decode the HARQ data message; and perform frame check sequence FCS inspection on the decoded data.

58. The receiving end according to claim 55, characterized in that, the sending unit is specifically configured to obtain special codewords from the HARQ data message received by the receiving end, according to Establish mapping relationship;

If the FCS check passes, an ACK is fed back to the sending end; or, if the special codeword identification passes and the FCS check fails, a second NAK is fed back to the sending end; or, if the special code word identification is passed, a second NAK is fed back to the sending end; If the word recognition fails, the FCS check fails, in RTS/CTS mode or OFDMA mode, the second NAK is fed back to the sending end; or, if the special codeword recognition fails, the FCS check fails, in DATA/ACK mode when, no information is fed back to the sending end; or,

59. The receiving end according to claim 56, wherein the sending unit is specifically configured to feed back an ACK to the sending end if the FCS check passes; or,

If the FCS check fails, a second NAK: is fed back to the sending end.

60. The receiving end according to claim 57, characterized in that, the sending unit is specifically configured to feed back ACK to the sending end if the FCS check passes; or, if the FCS check fails, RTS /CTS mode, the second NAK is fed back to the sending end; or, if the FCS check fails, and it is not the RTS/CTS mode, no information is fed back to the sending end.

61. The receiving end according to any one of claims 58 to 60, characterized in that the receiving unit is also used to cache this HARQ data message.

62. The receiving end according to any one of claims 58 to 60, characterized in that the receiving unit is also used to receive the HARQ retransmission data sent by the sending end; and decode the HARQ retransmission data.

63. The receiving end according to claim 62, characterized in that: the receiving unit The element is specifically used to decode the HARQ retransmission data; or to decode the HARQ retransmission data and the cached HARQ data message after merging them.

64. The receiving end according to claim 50, characterized in that: the receiving unit is further configured to receive the HARQ session end message sent by the sending end; and clear the HARQ data corresponding to the HARQ session. and HARQ session ID.

65. A communication system, characterized in that it includes a receiving end and a sending end that communicate with each other, wherein the sending end is the sending end as claimed in any one of claims 33-49, and the receiving end is as claimed in claim 50- 64 any one of the receiving ends.