WO2007112698A1

WO2007112698A1 - A method and apparatus for sending ack/nack

Info

Publication number: WO2007112698A1
Application number: PCT/CN2007/001111
Authority: WO
Inventors: Ming Fang; Guang Liu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-04-05
Filing date: 2007-04-05
Publication date: 2007-10-11
Also published as: CN101043299A; CN101043299B

Abstract

An ACK/NACK method, for the receiver providing feedback of the receiving situation of the radio link control RLC/media access control MAC data block. The method includes: the receiver determines whether TBF exists or not between the receiver and the sender, if TBF exists, the receiver provides feedback of the receiving situation of the RLC data block in the RLC/MAC data block sent by the sender, via carrying short ACK/NACK message in the RLC/MAC data block sent from the receiver to the sender. The ACK/NACK method, has instantaneity of event driven ACK/NACK method, and the method can improve the using bandwidth of TBF without the necessary to allocate additional wireless block to ACK/NACK message when TBF exists.

Description

ACK/NACK transmission method and device

The present invention relates to the field of wireless communications, and in particular, to an acknowledgement (Acknowledge, ACK for short)/negative acknowledgement of a Radio Link Control (RLC)/Media Access Control (MAC) data block reception status. (Not Acknowledge, abbreviated as NACK) transmission method and device. Background technique

In the way of allocation of radio resources, two different mechanisms are used for uplink and downlink. Temporary Block Flow (TBF) is a temporary connection between a mobile station (MS) and the network, and only exists during data forwarding. It supports one-way forwarding of logical link control (Logic Link Control, LLC) packet data units on a packet physical channel. A TBF can use radio resources on one or more Packet Data Channels (PDCHs). The network allocates a Temporary Flow Identity (TFI) for each TBF. In the TBF that appears at the same time, the TFI of each TBF is different. The MS identifies the TBF by detecting the TFI.

Each LLC frame of the upper layer consists of a series of RLC data blocks, each block having a corresponding Block Sequence Number (BSN) and transmitted in the order of the BSN. A radio block is a basic unit of radio resource allocation and radio transmission. Each radio block is composed of 4 time slots and is respectively located in 4 consecutive Time Division Multiple Access (TDMA) frames. The RLC MAC data block includes an RLC AC block header and an RLC data block (data portion). The transmission of the RLC MAC data block is carried by the radio block, and one radio block carries one RLC MAC data block. The block header of the RLC/MAC data block has a block number corresponding to the RLC data block. Due to different coding modes, one RLC MAC data block can carry up to two RLC data blocks. In order to optimize the data transmission in the packet switching mode, the transmission of the RLC data block in the RLC/MAC data block is controlled by the ARQ mechanism in the RLC acknowledgement mode, and the MS reports the relevant downlink status and successfully succeeds by polling. Information about the received RLC data block. The polling mechanism is only applicable to downlink data transmission, and the polling request is controlled by the Packet Control Unit (PCU). FIG. 1 is a polling process of a RLC/MAC data block (Block) with a round-robin polling interval of an ARQ mechanism in the prior art, which specifically includes:

The network side RLC/MAC layer sends the first downlink RLC/MAC data block to the MS;

The ^second downlink RLC/MAC data block receives an error;

Carrying ACK/NACK polling when transmitting to the 12th downlink RLC/MAC data block;

The MS returns a polling response: that is, reporting an ACK/NACK report to the RLC data block in the downlink packet RLC/MAC data block;

The network side retransmits the erroneous/lost RLC data block based on the returned ACK/NACK report. 20ms in Figure 1 represents the transmission time of an RLC/MAC block.

Because the RLC layer of the MS needs to collect all the RLC data blocks contained in the LLC frame in the RLC/MAC data block, the packet can be uploaded to the upper layer. The network can know whether the MS correctly receives all downlink RLC data blocks by polling the ACK/NACK report of the MS response. Since polling is generated by interval, when a block loss or error occurs, the network cannot immediately know and retransmit the wrong block or the lost block. It will only retransmit if it waits for polling and the MS reports an ACK/NACK report. In the actual situation, the PCU knows that the downlink error block or the lost block takes about 150 ~ 250ms, which results in a large transmission delay.

Prior art one:

In order to reduce the transmission delay caused by the polling interval, the prior art proposes an event-driven ACK/NACK method. Because the RLC data block in the RLC/MAC data block is received in the BSN order, when the BSN sequence error indicates that the RLC data block is lost, the MS can actively report the ACK/NACK report, and the PCU can immediately know the error block retransmission. Or the block header of a certain RLC/MAC data block can be correctly solved, but the data part of the RLC/MAC block is in error, that is, the RLC data block corresponding to the block number in the RLC/MAC block header is in error, and the MS can also actively report the ACK. /NACK reports that the PCU can also retransmit immediately. The event-driven ACK/NACK can reduce the transmission delay caused by waiting for retransmission by relying on the uplink resource indicated by the uplink state flag (USF) on the network side. The network side controls event-driven by balancing the amount of upstream data and the amount of ACK/NACK messages. The frequency of ACK/NACK reports. FIG. 2 is a process of driving ACK/NACK based on an event, specifically including:

The RLC/MAC layer on the network side sends the downlink RLC MAC data block to the MS;

A downlink RLC/MAC data block receives an error;

The MS actively reports the event-driven ACK/NAKC report to the packet downlink data block; the network side RLC/MAC layer immediately retransmits the RLC data block in the received RLC/MAC data block;

Carry ACK/NACK polling when sent to the 12th RLC/MAC data block;

The MS returns a polling response: that is, an ACK/NACK report for polling the downlink packet data block. In Figure 2, regular polling with 12 RLC MAC blocks is used as a supplement to the event-driven ACK/NACK report.

In the above prior art 1, when there is uplink TBF data transmission on the downlink corresponding uplink channel, the spare bits in the RLC/MAC block header can be used to feed back the ACK/NACK information.

A disadvantage of the prior art is as follows:

(1) Since the spare bits in the block header of the uplink RLC/MAC data block are limited in length, when the number of RLC data blocks that need to be received by the feedback is large, the spare bits in the block header of the RLC/MAC data block are not enough to represent the ACK/NACK information.

(2) If the event driver reports a complete ACK/NACK message, an upstream radio block is required, which will occupy more uplink resources.

Prior art 2:

Use the fast ACK/NACK mechanism as a supplement to the polling mechanism. The fast ACK/NACK occupies part of the uplink data space in the uplink RLC/MAC data block to transmit an ACK/NACK report. Since one radio block carries one RLC/MAC data block, one RLC/MAC data block can carry up to two RLC data blocks. Therefore, one radio block can carry at most two RLC data blocks (MCS7-9), so In the short bitmap, 2 bits are required for one radio block. The meaning of the fast ACK/NACK short bitmap is shown in Table 1 below: 0 0 - block header error

- The block is correct, but TFI does not belong to the current user

- The block header is correct, the TFI is correct, but the data part is decoded incorrectly (including the case of MCS 7/8/9)

0 1 The block header is correct and the TFI is correct, but the first RLC block data part is decoded incorrectly, and the second RLC block data part is decoded correctly.

1 0 block header is correct, TFI is also correct, but the first RLC block data part is decoded correctly, and the second RLC block data part is decoded incorrectly.

1 1 The block header is correct, the TFI is also correct, and all RLC block data portions are decoded correctly. When there are multiple TBFs, the short bitmap indicates the RLC/MAC data block of all TBFs, when the correctly received downlink RLC/MAC data block carries The specified TFI value, the corresponding bit in the short bitmap will be set to 1.

Assuming that the downlink radio block received by the MS at time Tx carries a polling request, the first pair of bits in the short bitmap indicates the reception of the radio block on the first downlink channel allocated at the time Tx, and the second pair of bits indicates the Tx time. The reception of the radio block on the allocated second downlink channel is so analogous. If there is any remaining bit space in the short bitmap, the next pair of bits can indicate the reception of the radio block on the first downlink channel allocated at time Tx-1 (that is, the time before 20ms), and so on. Figure 3 illustrates the operation of a fast ACK/NACK report, specifically:

It is assumed that the downlink time slot allocated by TBF1 is TS0, 1, 2, 3. At the time Tx, the MS receives the polling request in time slot TS2, and the MS transmits data in the corresponding uplink time slot TS2. At this time, the data carries ACK/NACK report information. , that is, short bitmap. In Fig. 3, the 2 bit (11) of the ellipse circle labeled 1 indicates that the radio block on the downlink time slot TS0 is correctly received at the Tx time, and the second pair of bits (00) indicates that the radio block on the downlink time slot TS1 does not have its own. TFI, the third pair of bits (11) indicates that the radio block on the downlink time slot TS2 is correctly received, and the fourth pair of bits (00) indicates the radio block reception error on the down time slot TS3. The 2 bit (10) enclosed by the ellipse labeled 2 indicates the data portion of the first RLC MAC data block carried by the radio block on the downlink time slot TS2 at the time Tx-1 (the first 20 ms) (ie, the first RLC data block) The decoding is correct, and the data portion of the second RLC/MAC data block (ie, the second RLC data block) is decoded incorrectly.

The structure of the EGPRS uplink RLC/MAC data block with the short bitmap information is as shown in FIG. 4, which keeps the structure of the original RLCMAC data block unchanged, and the designed short bitmap has a length of 4 bytes. Occupies the last 4 bytes of the RLC/MAC data block. In order to distinguish whether the RLC/MAC data part carries the short bitmap information, it needs to use the lbit in the spare bits in the uplink RLC/MAC data block header to indicate.

The disadvantages of the prior art 2 are as follows:

(1) The utilization of the short bitmap in the fast ACK/NACK method is not high. When other MSs are multiplexed on the downlink channel of an MS, some bits in the short bitmap report that they are not their own RLC/MAC blocks. That is, the information fed back by these bits has nothing to do with the downlink reception of the MS, resulting in short bitmap and uplink. Waste of wireless resources. When certain channel coding modes are CS1-4 or MCS1-6 at certain moments, each R1 block carries 1 RLC block, and 2bit is not required to indicate the reception condition of 1 RLC block. At this time, short bitmap and uplink radio are also caused. Waste of resources.

(2) Fast ACK/NACK—The range of RLC/MAC blocks to be represented is determined by the corresponding polling request; and the 32-bit short bitmap can feed back up to 16 radio blocks. When the downlink allocates more channels, the network side frequently needs to initiate a polling request, so that the uplink frequently carries the short bitmap information. For example, the allocation of 8 downlink channels, the short bitmap indicates the reception of 2 block periods, that is, the polling needs to be performed every 2 block periods, and the short bitmap information needs to be carried every 1 block in the uplink, causing the uplink TBF. The available bandwidth is reduced. Summary of the invention

The embodiment of the invention provides an ACK/NACK transmission method, which occupies less uplink resources and implements ACK/NACK transmission.

An ACK/NACK transmission method is applied to the receiving end feedback radio link control RLC/media access control MAC data block receiving status, including:

The receiving end determines whether there is a temporary block flow TBF between the transmitting end and the transmitting end. If there is a TBF, the RLC/MAC data block sent by the receiving end to the transmitting end carries a short acknowledgement ACK7 non-acknowledgement NACK information, and feeds back the RLC/ sent by the sending end. The reception status of the MAC data block.

An ACK/NACK transmitting apparatus includes:

a data block receiving module, configured to receive an RLC/MAC data block sent by the sending end; a first determining module, configured to determine whether there is a temporary block flow TBF between the sending end, and if there is a TBF, send a first notification to the first feedback module;

a feedback module, configured to receive the first notification, by sending a short acknowledgement ACK/non-acknowledgement NACK information to the RLC/MAC data block sent by the sender, and sending the feedback sender to the local RLC/MAC data block Receiving status.

The ACK/NACK transmission method provided by the embodiment of the present invention has the immediacy of the event-driven ACK/NACK transmission method, and does not need to allocate a separate radio block for the ACK/NACK message when the TBF exists, thereby increasing the available bandwidth of the TBF. DRAWINGS

1 is a conventional polling process in which a polling interval is 12 RLC/MAC blocks in the prior art; FIG. 2 is a prior art event-driven ACK/NACK process;

FIG. 3 is a fast ACK/NACK reporting process in the prior art;

4 is a structural diagram of an EGPRS uplink RLC/MAC data block carrying short bit bitmap information in the prior art;

FIG. 5 is an ACK/NACK process according to an embodiment of the present invention;

6 is a structural diagram of an uplink RLC/MAC data block carrying short ACK/NACK information in an embodiment of the present invention when applied to GPRS;

7 is a second structural diagram of an uplink RLC/MAC data block carrying short ACK/NACK information in an embodiment of the present invention when applied to EGPRS;

8 is a third schematic diagram of an uplink RLC/MAC data block structure carrying short ACK/NACK information according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an ACK/NACK transmitting apparatus according to an embodiment of the present invention. detailed description

The following takes the downlink RLC/MAC data block sent by the network side as an example to describe in detail how the MS uploads the RLC block in each downlink RLC/MAC data block. The ACK/NACK triggering mechanism in the embodiment of the present invention is the same as the event-driven ACK/NACK in the prior art, that is, when the MS finds that the downlink receiving has a wrong block or a lost block, the active uplink resource is immediately reported according to the available uplink resource indicated by the USF on the network side. ACK/NACK information. The present invention differs from the prior art event-driven ACK/NACK in that: when there is a TBF in the uplink, instead of using a separate complete ACK/NACK report, the uplink RLC/MAC data block (RLC/MAC Block) is utilized. Carrying short ACK/NACK information, and feeding back the reception status of the RLC block in the received downlink RLC MAC data block. The ACK/NACK process of the present invention is as shown in FIG. 5, and includes:

The RLC/MAC layer on the network side sends the downlink RLC/MAC data block to the MS;

A downlink RLC/MAC data block receives an error;

The MS carries the event-triggered short ACK/NACK information through the uplink RLC/MAC data block to return an ACK/NAKC report to the network side;

The RLC/MAC layer on the network side immediately retransmits the RLC data block in the RLC/MAC data block that received the error;

Carry ACK/NACK polling when sent to the 12th RLC/MAC data block;

The MS returns a polling response: that is, an ACK/NACK report for polling on the downlink packet data block. As can be seen from the flow of Figure 5, once the MS finds that the downlink RLC data block receives an error, the MS occupies a small amount of space in the uplink RLC/MAC data block to carry short ACK/NACK information. A conventional poll with an interval of 12 RLC/MAC blocks is also used in FIG. 5 as a supplement to the ACK/NACK of the present invention.

The length of the short ACK/NACK information portion is L octets ( Octet ). The value of L can be adjusted according to the reception.

Example 1:

The short ACK/NACK information is carried through a number of bytes at the very end of the RLC/MAC data block. General Packet Radio with short ACK/NACK information (General Packet Radio

Service, GPRS), enhanced GPRS (ie EGPRS) uplink data block structure are shown in Figure 6, Figure 7, respectively.

The short ACK/NACK information includes at least: a starting block sequence number and a receiving block bitmap of the RLC data block. For a single TBF, it is not necessary to include TFI in short ACK/NACK information; for multiple TBFs, Since the reported downlink TBF needs to be indicated by the TFI, the corresponding TFI needs to be included in the short ACK/NACK information to correspond to the downlink TBF.

Since the TFI in both GPRS and EGPRS is 5 bits, the TFI in the short ACK/NACK information is also set to 5 bits.

Set the selection principle of the starting block: Try to make the reported information feedback the RLC data block that currently receives the error, and push the sending window forward.

For GPRS, because there is a sufficiently long bitmap indicating the reception of all the windows, the starting block number can be set to the BSN corresponding to the RLC data block with the highest block number in the RLC/MAC data block received by the MS. Since the BSN in GPRS is 7 bits, the starting block number in the short ACK/NACK information corresponding to GPRS is also 7 bits.

For EGPRS, the starting block sequence number can be set to the corresponding BSN of the RLC data block with the smallest sequence number in the RLC/MAC block that the MS does not correctly receive, and the receiving status of the RLC data block starting with the BSN+1 is carried in the bitmap. Since the BSN in EGPRS is libit, the starting block number in the short ACK/NACK information corresponding to EGPRS is also llbit.

The receive block bitmap can consist of a series of binary variables. The receiving status of the RLC data block in the plurality of downlink RLC/MAC data blocks whose block number is greater than or smaller than the starting block number is sequentially indicated according to the set starting block number.

For GPRS, if the starting block number is set to the BSN corresponding to the RLC data block with the highest block number in the RLC/MAC data block received by the MS, then each variable in the received block bitmap starts from the starting block number. (ie, BSN 4 is in the direction of the starting block number) Maps the reception status of (LX 8 - 12) RLC data blocks.

For EGPRS, if the starting block number is set to the BSN corresponding to the RLC data block with the smallest sequence number in the RLC/MAC data block that the MS does not correctly receive, each variable in the received block bitmap starts from the starting block number and backward. (ie, the direction in which the BSN is higher than the starting block number) Maps ((L - 2 ) χ 8) the reception status of the RLC/MAC blocks.

For example, when the variable value is "0", the downlink RLC/MAC data block receiving error indicating the block number is received; when the variable value is "Γ, the downlink RLC/MAC data block receiving the block number is received. Correct.

The correspondence between the value of each position variable in the received block bitmap and the reception status of the RLC/MAC data block is shown in Table 2 below (assuming that the BSN is reported in the direction larger than the starting block number):

Table 2

The relationship between the value of each position variable in the receiving block bitmap and the RLC/MAC data block receiving status is as shown in Table 3 below (assuming that the BSN is reported in the direction smaller than the starting block number):

table 3

The short ACK/NACK information of the present invention can flexibly set the position of each field, as shown in Table 4 and Table 5 below:

Table 4

Bi t

8 7 6 5 4 3 2 1

Octets 1

Octets 2

Octets L

Bi t

8 7 6 5 4 3 2 1

Starting block number TFI Octet s 1

Start block number Octets 2 Receive block bitmap

Octet s L In the above embodiment 1, the short ACK/NACK information (containing at least the start block number and the received block bitmap) is carried by the last few bytes in the data payload field in the RLC/MAC data block. The short ACK/NACK information is encoded together with the RLC MAC data and sent to the network side.

Example 2:

The short ACK/NACK information (including at least the starting block number and the received block bitmap) can also be carried in other ways. For example: Carry it in a separate field set in the RLC/MAC data block. Referring to Figure 8, before the data payload field in the RLC/MAC data block, a field dedicated to carrying short ACK/NACK information is set. In the carrying mode shown in Figure 8, the block header, short ACK/NACK information, and RLC data block of the RLC/MAC data block are independently encoded and sent to the network side.

In the methods of the foregoing Embodiment 1 and Embodiment 2, if the uplink RLC/MAC data block carries the short ACK/NACK information, the flag information may be carried in the uplink RLC/MAC data block header spare bits (reserved bits), indicating The data block has short ACK/NACK information, so that the network side RLC/MAC layer obtains the short ACK/NACK information carried by the RLC/MAC layer according to the flag information in the uplink RLC/MAC data block, and learns according to the short ACK/NACK information. The MS receives the RLC data block in the corresponding downlink RLC/MAC.

In the foregoing embodiment, the network side sends the downlink RLC/MAC data block to the MS, and the MS carries the short ACK7 NACK information through the uplink RLC/MAC data block, and feeds back the receiving status of the RLC data block in the downlink RLC/MAC data block sent by the network side. For example. In the opposite direction, the method provided by the embodiment of the present invention is also applicable to the MS sending an uplink RLC/MAC data block to the network side, and the network side feeds back the RLC in the uplink RLC/MAC data block sent by the MS through the downlink RLC/MAC data block. The receiving status of the data block. Since the methods are identical, only the body that sent the feedback is exchanged, the example description is not repeated.

According to the ACK/NACK sending method provided by the foregoing embodiment of the present invention, a schematic structural diagram of an ACK/NACK transmitting apparatus is shown in FIG. 9, which includes:

a data block receiving module, configured to receive an RLC/MAC data block sent by the sending end;

a first determining module, configured to determine whether there is a temporary block flow TBF between the sending end, and if there is a TBF, send a first notification to the first feedback module;

a first feedback module, configured to receive the first notification, by sending the RLC/MAC data block of the sending end locally, carrying a short acknowledgement ACK7 non-acknowledgement NACK information, and sending the feedback to the sender The reception status of the RLC data block in the local RLC/MAC data block.

Also includes:

a second feedback module, configured to receive a second notification sent by the first determining module when there is no TBF between the sending end, and report an event-driven ACK/NACK report, where the feedback sending end sends the information to the local RLC/MAC data block. The reception status of the RLC data block.

Also includes:

a second judging module, configured to determine whether the received RLC/MAC data block receives an error/loss, or whether an ACK/NACK report reporting period arrives; when it is determined that the RLC/MAC data block receives an error/loss, or an ACK/NACK report When the reporting period arrives, the first determining module is instructed to start determining whether there is a temporary block flow TBF between the transmitting end and the transmitting end.

In summary, the ACK/NACK sending method provided by the embodiment of the present invention has the immediacy of the event-driven ACK/NACK method, and does not need to allocate a separate radio block for the ACK/NACK message when the TBF exists, thereby improving the available TBF. bandwidth.

In the process of the MS feeding back the RLC/MAC data block receiving status, the short ACK/NACK information in the embodiment of the present invention only feeds back the downlink RLC/MAC data block related to the MS itself; that is, the MS passes the downlink data block header. The TFI field determines which RLC/MAC data blocks are related to itself, and only reports the reception of the downlink data blocks sent to itself; the utilization of the received block bitmap reaches 100%, which is much higher than the utilization of the short bitmap in the fast ACK/NACK. rate.

In the present invention, the short ACK/NACK information adopts the TFI+starting block number+receiving block bitmap mode, and the range of the RLC/MAC block to be fed back can be clearly indicated without corresponding polling request; therefore, the uplink data block does not have to carry Short ACK frequently. NACK Message information to increase the available bandwidth of the upstream TBF. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

An ACK/NACK method, which is applied to a receiving end feedback radio link control RLC/media access control MAC data block receiving status, and includes:

The receiving end determines whether there is a temporary block flow TBF between the transmitting end and the transmitting end. If there is a TBF, the RLC MAC data block sent by the receiving end to the transmitting end carries the short acknowledgement ACK/non-acknowledgement NACK information, and feeds back the RLC/ sent by the sending end. The reception status of the RLC data block in the MAC data block.

2. The method according to claim 1, wherein before the receiving end determines whether there is a TBF between the transmitting end and the transmitting end, the method further includes:

The receiving end determines whether the RLC/MAC data block sent by the sending end receives an error/loss, or whether the reporting period of the ACK/NACK report arrives;

When the receiving end determines that the RLC/MAC data block received by the transmitting end receives an error/loss, or determines that the reporting period of the ACK/NACK report arrives, a step of determining whether there is a TBF between the transmitting end and the transmitting end is performed.

The method according to claim 1, wherein when the RLC/MAC data block sent by the receiving end carries the short ACK/NACK information, the data block header carries the flag information; The flag information in the RLC/MAC data block sent by the receiving end acquires the short ACK/NACK information carried by the receiving end.

4. The method according to claim 3, wherein when the receiving end determines that there is no TBF between the transmitting end, the receiving end reports an event-driven ACK/NACK report, and feeds back the RLC/MAC data sent by the sending end. The reception status of the RLC data block in the block.

The method according to any one of claims 1-4, wherein the RLC/MAC data block sent by the receiving end to the transmitting end carries short ACK/NACK information, which is specifically:

Carrying the short ACK/NACK information by occupying the last few bytes of the RLCMAC data block sent by the receiving end; or

The short ACK/NACK information is carried by a separately set field in the RLC/MAC data block transmitted by the receiving end.

The method according to claim 1, wherein the short ACK/NACK information includes at least:

The starting block number and the receiving block bitmap of the RLC data block in the RLC/MAC data block of the feedback receiving condition;

The receiving block bitmap sequentially indicates the receiving status of the RLC data block in the plurality of RLC/MAC data blocks whose block number is greater than or smaller than the starting block number.

The method according to claim 6, wherein the short ACK/NACK information further includes a temporary block indication TFL.

8. The method according to claim 6 or 7, wherein the receiving block bitmap is composed of a string of binary variables;

When the value of the variable is "0", it indicates that the RLC data block corresponding to the block number is incorrectly received. When the value of the variable is "1", it indicates that the RLC data block corresponding to the block number is received correctly.

The method according to claim 8, wherein the starting block sequence number is a block number of any RLC data block in the received RLC/MAC data block in which the receiving status is not reported; the receiving block bitmap Contains bitmap length information.

The method according to claim 9, wherein for the general packet radio service GPRS, the starting block sequence number is a maximum block number of the RLC data block in the received RLC/MAC data block; the receiving block The bitmap length is (L x 8 - 12) binary variables, and is used to sequentially indicate the reception status of (L x 8 - 12) RLC data blocks whose block number is smaller than the start block number; wherein L is The number of octets occupied by the short ACK/NACK information.

The method according to claim 9, wherein, for the enhanced general packet radio service EGPRS, the starting block sequence number is a minimum block number of the RLC data block in the RLC/MAC data block that is not correctly received; The receiving block bitmap has a length of ((L - 2 ) x 8 ) binary variables, and is used to sequentially indicate ((L - 2 ) x 8 ) RLC data blocks whose block numbers are greater than the starting block number Receive status; where L is the number of octets occupied by the short ACK/NACK information.

12. An ACK/NACK transmitting apparatus, comprising:

a first feedback module, configured to receive the first notification, by sending an RLC/MAC data block locally sent to the sending end, carrying a short acknowledgement ACK/non-acknowledgement NACK information, and sending the feedback sender to the local RLC/MAC data block The reception status of the RLC data block in the medium.

The ACK/NACK transmitting apparatus according to claim 12, further comprising: a second feedback module, configured to receive, by the first determining module, that there is no

The second notification sent during the TBF reports the event-driven ACK/NACK report, and the feedback sender sends the reception status of the RLC data block in the local RLC MAC data block.

The ACK/NACK transmission apparatus according to claim 13, further comprising: a second determining module, configured to determine whether the received RLC/MAC data block receives an error/loss, or reports the ACK/NACK report Whether the period arrives; when it is determined that the RLC/MAC data block receives the error/loss, or the reporting period of the ACK/NACK report arrives, the first determining module is instructed to start determining whether there is a temporary block flow TBF between the transmitting end and the transmitting end.