A method and a device for improved status reports

The present invention discloses methods for use in cellular communication systems. In this cellular communication system, traffic can be exchanged between the first transceiver and the second transceiver. Traffic is transmitted in the form of data units, each data unit is given an identifier and can be divided into several segments. The receiving transceiver can transmit state information about the transmitted data to the transmitting transceiver, that is, the transceiver that transmitted the data, in the form of a data frame or data unit.

The 3GPP LTE project for cellular communication systems (3rd Generation Partnership Project Long Term Evolution) uses the RLC (Wireless Link Control) protocol to communicate between users in a cell and control nodes in the cell. This control node is called the so-called eNodeB "evolved NodeB".

In RLC, traffic is transmitted as a so-called PDU (Protocol Data Unit), and PDUs are identified by being given a given sequence number. In response to the PDU from the transmitting party, the receiving party transmits a so-called RLC state PDU to the transmitting party with at least one of so-called ACK and NACK. That is, an acknowledgment (ACK) indicating that the data was received correctly, or information (NACK) indicating that the data was not received correctly, that is, partially received or not received at all. Will be sent. The ACK and NACK in the RLC state PDU are sent as PDU sequence numbers to identify the PDU in question.

In LTE systems, RLC PDUs can be segmented, resulting in two or more PDU segments with the same sequence number because the sequence number is unique to the PDU. The process of dividing the PDU into segments is called re-segmentation.

<p> For re-segmentation in LTE, sequence numbers may not be sufficient to identify the data for which an ACK or NACK was transmitted.</p><p> As is clear from the above description, in a 3G LTE system, the ACKs and NACKs sent from the receiving party to the sending party need to be resolved by being able to identify the data segments they are sent in response.</p><p> In addition, another need to be addressed by the solution in question is that it should be possible to send a variable number of NACKs.</p>

<p> This need is addressed by the present invention, which discloses the following methods. That is, it is a method used in a cellular communication system, in which traffic is exchanged between a first transceiver and a second transceiver. The traffic of the system is transmitted in the form of data units, and each data unit is given an identifier. The data unit is divided into multiple segments, and the receiving transceiver is the transmitting transceiver, that is, whether the data unit was correctly received, partially received, or not received by the transceiver that transmitted the data. Status information can be transmitted in the form of data frames or data units.</p><p> According to the method of the invention, if one or more data units are partially received or not received correctly, the state information transmitted to the transmitting transceiver will be received by the data units. Contains information about whether it was not or was partially received. It also includes information about which part of the data unit was not received when the data unit was partially received.</p><p> Therefore, the present invention allows the receiving transceiver to clearly identify the unreceived portion of the data unit to the transmitting transceiver. As a result, the transmitting transceiver is able to retransmit those parts.</p><p> In addition, the present invention makes it possible to identify the amount of data that has not been received to some extent. This is another need to be addressed by the present invention.</p><p> In one embodiment of the invention, information about whether the data unit was not received or was partially received is included as a flag in the data frame or data unit.</p><p> In another embodiment, information about which part of the data unit was not received is included in the data frame or data unit as information indicating the first and last part of the unreceived data.</p><p> Looking at the present invention from yet another aspect, if the data frame or data unit from the transmitting transceiver is divided into segments and one or more last segments do not reach the receiving transceiver, then this This is indicated by the transceiver on the receiving side.</p><p> In a further embodiment of the invention, information about which part of the data unit was not received is received as information indicating the identifier of the data unit, as well as the beginning of unreceived data in the data unit. Included within a data frame or data unit as information about the amount of data that was not available.</p><p> Various aspects and advantages of the present invention will be described in more detail in the detailed description below.</p><p> The present invention also discloses transceivers used in the systems of the present invention.</p><p> Hereinafter, the present invention will be described in more detail with reference to the accompanying drawings.</p>

<figref num="1">It is a figure which shows the system to which this invention is applied.</figref><figref num="2">、</figref><figref num="3">、</figref><figref num="4">、</figref><figref num="5">、</figref><figref num="6">It is a figure which shows various examples of this invention.</figref><figref num="7">It is a flowchart which shows the method of this invention.</figref><figref num="8">It is a block diagram of the transceiver of this invention.</figref>

FIG. 1 shows a system 100 to which the present invention is applied. As mentioned above, the present invention is primarily intended for 3GPP LTE type systems. The 3GPP LTE system is a third-generation partnership project long-term evolution system, often referred to as the LTE system, but in 3GPP it is officially known as the Evolved UTRAN or E-UTRAN. These names are used interchangeably in the following description.

As shown in FIG. 1, the LTE system 100 includes what are called multiple cells, one of which is shown at 130 in FIG. Each cell in an LTE system can accommodate a large number of users, sometimes commonly referred to as UEs (user devices). In Figure 1, one UE is symbolically represented by reference number 120.

LTE systems, such as the system shown at 100 in FIG. 1, also have a node called "eNodeB" (evolved NodeB) for each cell. One of the functions of the cell's eNodeB is to control traffic to and from the user within the cell. In FIG. 1, eNodeB 110 is shown as eNodeB for cell 130.

Traffic from eNodeB to UE is referred to as downlink traffic, or simply DL traffic, and traffic from UE to eNodeB is known as uplink traffic, or simply UL traffic.

In LTE systems, the RLC protocol (wireless link protocol) is used for communication between the eNodeB and UE in the cell.

According to RLC in LTE systems, traffic between two transceivers (ie, UE and UE eNodeB) is transmitted in PDUs (Protocol Data Units). According to RLC, each PDU is assigned an identifier called a sequence number. This allows both the sending party and the receiving party to identify the PDU.

The description below assumes that the data PDU is transmitted by eNodeB, ie in DL, and the state PDU is transmitted by UE, ie in UL. However, this is merely an example intended to facilitate the reader's understanding of the invention, and the invention applies equally and well to other directions: data PDUs in UL and state PDUs in DL. It should be pointed out that it is possible. Here, it can be said that the E-UTRAN RLC can operate in different modes configured by eNodeB: acknowledgment mode (AM), non-acknowledgement mode (UM), and transparent mode (TM). .. State PDUs are currently only used in AM.

When the eNodeB 110 transmits a PDU containing data, that is, a so-called data PDU to the UE 120, the UE is a so-called state PDU, that is, a PDU that indicates the data reception state of the data PDU transmitted from the eNodeB to the eNodeB. I can reply.

In the state PDU to eNodeB, the data unit correctly received by the UE is acknowledged by the UE with a so-called ACK message or indicator. Also, data units that are erroneously received, i.e. only partially received, or not received at all, are indicated by the UE by a so-called negative ACK or NACK. If the eNodeB that originated the data receives an NACK in response to the transmitted data, the eNodeB will know that this information must normally be retransmitted until the ACK is received. In the case of DL data traffic, the UE will thus send a state PDU to the eNodeB with at least one of the ACK and NACK states in response to the data PDU from the eNodeB.

The ACK provides information about how many sequence numbers the PDU has received correctly. This is done by providing the maximum number of PDUs that have been successfully received, or the first number of PDUs that have not been received.

With E-UTRAN RLC, the data PDU can be segmented again. That is, the previously generated RLC PDU payload can be segmented and transmitted separately at the time of retransmission.

In LTE, it is intended that the RLC PDU segment should be identified by the so-called segmentation offset (SO), which indicates the beginning of the segment in the original RLC PDU, along with the sequence number of the original RLC PDU. .. An ACK or NACK is sent in the form of the original RLC PDU sequence number. However, since re-segmentation may have been performed, the segment referenced by the ACK or NACK from the UE cannot be uniquely identified by the sequence number in eNodeB. In addition, segmentation may have "occurred" many times, i.e. multiple re-segmentations, and eNodeB knows which occurrence ACK / NACK is referring to. Due to the fact that it is not, it cannot be uniquely identified even by SO.

What the present invention is trying to address is this issue, namely the identification of RLC PDUs referred to by ACK / NACK. Several different cases are recognized for state PDUs. That is, a. For PDUs with only one ACK and no NACK, b. For a state PDU with one ACK and one or more NACKs In addition, there are two cases: i. When one or more of the NACKs are segment NACKs and ii. When not all NACKs are NACKs in the segment Is.

In order to handle the case of a above, the present invention proposes a state PDU indicated by reference numeral 200 in FIG. As shown in FIG. 2, the state PDU 200 includes a D / C field 210. The D / C field 210 indicates whether the PDU 200 is a data PDU or a control PDU. As will be understood, the state PDU is a control PDU.

In addition, the state PDU 200 includes an ACK field 220. The ACK is provided in the form of the sequence number SN of the RLC PDU referenced by the ACK. The status PDU 200 also includes an indicator. This indicator is, for example, the flag or bit shown as E-bit 230 in FIG. 2 and is used to indicate the presence or absence of NACK in the state PDU 200.

In the absence of NACK in the state PDU, that is, as shown in FIG. 2, the so-called "padding" or "dummy bit" is used to achieve the proper alignment of the contents of the state PDU 200. can do. One example of such an array is the so-called "octet sequence", which is the alignment used when the state PDU is divided into data octets. The padding is shown as 240 in Figure 2.

Now, when identified by the "bi" above, i.e. when one or more NACKs refer to a segmented data unit, in other words, the NACK indicates that the data unit has been partially received. Moving on to the case, we will introduce the concepts used by the present invention. This concept is referred to herein as a "segment offset pair" or "SO pair". This is a data pair, one of which is used to indicate the first unreceived data octet of the PDU referenced by NACK, and one of which indicates the last unreceived data octet of the PDU referenced by NACK. Used for. It should be added here that LTE RLC uses octets, so octets are used to illustrate the invention, but of course the invention also when data is transmitted in other sizes. Is that it can be used.

Figure 3 shows one example of a state PDU format 300 that can handle the bi case above. Similar to the state PDU format 200 of FIG. 2, the state PDU format 300 includes a field indicating whether the PDU 300 is a data PDU or a control PDU, and an ACK field. The ACK is provided in the form of the sequence number SN of the RLC PDU referenced by the ACK.

The state PDU 300 comprises an indicator. This indicator is, for example, the flag or bit indicated by the E-bit in FIG. 3 and is used to indicate the presence or absence of NACK in the state PDU 300.

As shown in FIG. 3, when one or more NACKs are included, each NACK is followed by an E bit or flag and an F bit or flag. Here, the E bit / flag indicates whether or not another NACK exists, and the F bit / flag indicates whether or not an SO pair is included for a specific NACK. In other words, the F bit / flag can be said to indicate whether the data unit referenced by NACK is divided into segments. This is the only case where SO pairs are used.

Also, the present invention is because two parts (for example) are missing in one and the same PDU, but they are different SO pairs even if one and the same NACK SN can occur twice. It can also be pointed out that it is possible to handle cases where they are not continuous.

Similar to the embodiment of FIG. 2, the ACKs and NACKs of the state PDU 300 of FIG. 3 are provided in the form of ACK or the sequence number SN of the RLC PDU referenced by the NACK. For this reason, ACK / NACK is shown as ACK_SN or NACK_SN.

The last NACK of the state PDU in Figure 3 is followed by the SO pair for the NACK with the F flag / bit set. Therefore, the SO pair represented by SO11 and SO12 "belongs" to NACK1_SN, and the SO pair represented by SO21 and SO22 "belongs" to NACK2_SN. Also, as shown in FIG. 3, a "padding" PAD may be used in the state PDU 300 of FIG. 3 to obtain an octet sequence or for other similar purposes.

Returning to the discussion of the information contained within the SO pair, the first SO in the SO pair indicates the first missing data octet in the PDU, and the last SO in the pair is in the PDU. Shows the last missing data octet of.

Even when the received PDU, that is, the data of the PDU referenced by ACK / NACK is configured in a group other than the octet, the present invention can be applied to such a system as a matter of course. is there. Therefore, the SO pair will indicate the beginning and end of the data in the PDU referenced by NACK in a manner similar to that described above.

It should be noted that the state PDU of the present invention can be extended by a field indicating the characteristics of the state PDU, for example, when an RLC control PDU other than the STATUS PDU is used after the D / C field. be able to. This field is included in the example shown in Figure 3 and is shown as "PDU type". The same principle, ie, PDU type, can also be applied to the form shown in FIG.

Continuing with reference to the state PDUs of the present invention, the following points must also be pointed out. That is, the order of the state PDU data fields shown in FIGS. 2 and 3 is merely an example in the appropriate embodiment, and the state PDU data fields of the present invention are, for example, to achieve an octet sequence. It is also possible to move to other locations in the state PDU without affecting the functionality of the invention. As an example, if there is only an ACK and no NACK, that is, in the embodiment shown in FIG. 2, the state PDU200 starts with a D / C field, followed by an E bit, then padding, and so on. Finally, it could be an ACK with that sequence number.

Now, move on to the case indicated by b-ii above, that is, the case of referring to the data PDU in which one or more NACKs have not been received, as opposed to the case of the partially received data unit. In this case, it is processed as shown below. That is, the F flags corresponding to these NACKs indicate that the state PDUs for these NACKs do not contain SO pairs.

The special case treated by the present invention is when the last PDU segment of the RLC PDU was not received by the UE (again, assuming the data PDU in DL). Suppose an RLC PDU with sequence number 10 is divided into three RLC PDU segments, each containing octets 1-10, 11-25, 26-40.

Now, the UE has received the first two segments of RLC PDU10, octets 1-10 and octets 11-25, and also the subsequent RLC PDU, RLC PDU11, completely received, but the UE Consider the case where the last segment of RLC PDU10, octet 26-40, was not received.

In this case, the UE knows that the RLC segment has been lost, but not its length. Therefore, the UE cannot set the second segmentation offset value of the corresponding SO pair in the state PDU. The solution to this proposed by the present invention is to have a special value of SO indicate that the end of the segment recognized as NACK is unknown. Therefore, when eNodeB receives a NACK for RLC PDU10, the first SO is set to "26" and the corresponding second SO is set to its special value, 26 or later for RLC PDU10. Tell eNodeB that all data octets in are needed to be retransmitted.

In some cases, SO pairs are not always needed to achieve the desired effect. Complete identification of unreceived data can be achieved by using the 2 bits in the "F" field, as shown below.

This is shown in the example of FIG. FIG. 4 shows all four combinations of two bits in the F field, namely 00, 01, 10, and 11. The meaning of each of these combinations is also shown in FIG. 4 and is as follows.

<u style="single">F field</u><u style="single">meaning</u> 00 NACK refers to all RLC PDUs. So you don't need SO 01 See the first part of the RLC PDU for NACK. Not received To indicate the last data group, eg octets, etc. Need one SO 10 See the last part of the RLC PDU for NACK. Not received To indicate the first data group, eg octets, etc. Need one SO 11 For NACK, refer to the middle part of the RLC PDU. Not received To indicate the first and last data groups, such as octets, etc. Requires 2 SOs.

In the case shown in FIG. 4, a type field may be required to separate the state RLC PDU from other RLC control PDUs, as in the previously shown embodiment.

In another embodiment of the invention, the partially received DL RLC data PDU is shown to the eNodeB by the UE in the UL state RLC PDU in the manner shown above, i.e., in a manner slightly different from the SO pair. .. In the embodiment in question, ie, the state RLC PDU 500 shown in FIG. 5, the UL state RLC PDU from the UE comprises a NACK field shown as 510 and a sequence number field SN shown as 520. The sequence number field SN indicates the sequence number of the DL RLC data PDU referenced by NACK. Of course, in Example 500, the SN may be included in the NACK together, as shown in the previous examples.

As in previous examples, Example 500 also includes the use of the "E" field shown as 530 in FIG. However, the meaning of the E-field, ie the bit or flag, is slightly different from the previous embodiment. That is, in Example 500 of FIG. 5, the E field is used to mean whether the NACK 510 refers to the entire RLC data PDU or the data in the RLC data PDU. For example, if the E field is zero, i.e. E = 0, this can mean that NACK510 refers to the entire RLC data PDU identified by SN520.

Conversely, if E = 0 means the entire PDU, then E = 1 means that NACK510 refers to the data in the PDU identified by the SN520. In this case, information is included in the state PDU 500 so that the eNodeB can identify the data. This information about the data in Example 500 comprises the segment offset value SO shown as 540 in FIG. SO540 indicates the byte offset or first of the DL data that was not received. However, contrary to previous examples, Example 500 does not use SO pairs to show the entire unreceived data. Instead, Example 500 utilizes a length field (LF) 550. This value indicates from the beginning of the unreceived data to the last byte of the unreceived data, starting with the SO value 540.

As will be appreciated in this embodiment of the invention, ie, that shown in FIG. 5, the bytes to be retransmitted in order to achieve efficient retransmission from the original sender of the data. The exact number needs to be shown to the sender. Since LTE RLC PDUs can be very large (eg 32767 bytes), the fields required to indicate the RLC PDU segment (ie SO and LF) will need to be quite large as well. However, as will be similarly understood, in many cases it will not be necessary to utilize the theoretical maximum size of the SO and LF fields. Therefore, if the size of these fields were static, it would result in wasting data space.

In one embodiment of the invention, the inventor proposes to alleviate this problem, i.e., the problem of inefficient use of data space for SO and LF fields. Next, this embodiment will be described.

The basic principle of this aspect of the invention is that the SO and LF field sizes of the RLC state PDU are adaptively set according to the needs of the current RLC state PDU. Obviously, it is possible to use two different sizes for SO and LF, for example 6 bits for RSO and 4 bits for RSL. However, in the following description, it is assumed that these sizes are the same.

As proposed in this aspect of the invention, if dynamically variable length fields are used for SO and LF, eNodeB (if DL has data and UL has status messages). Must know the size of this length field in order to be able to read the status message.

The first way to achieve this is to provide an additional field in the RLC state PDU message header to indicate the size of the SO and LF fields. For example, it could have a field indicating that all length fields in the current message are 6 bits. This size can vary depending on the RLC PDU status message.

If SO and LF are given different size values, these two length fields are needed or used with a given relationship between them. This predetermined relationship is, for example, SO is always x bits longer / shorter than LF. However, SO and LF are usually on the same order, so this optimization may not be necessary.

From another aspect of the invention, a clear indication of the size of the SO and LF fields is no longer needed by reconstructing the RLC PDU status message. In this aspect of the invention, it is proposed to move the "length fields" SO and LF to the end of the RLC PDU status message. Next, this will be described with reference to FIG.

In the embodiment shown in FIG. 6, state information is provided first for all included PDUs. That is, these are the SN (segment number), RF (re-segmentation flag), and extension bit E. In this way it is also possible to include a complete PDU. In this case, the individual segment information does not need to be transmitted. For re-segmented PDUs, RF is used to indicate that segment position and length information follows, with SO and LF attached to the message frame.

Thus, in the embodiment of FIG. 6, the "dynamic" variable portion of the state message, ie SO and LF, indicates that it is after the last extension bit E, i.e. this is the last E bit, eg, "0". Occurs after the first E bit with a value such as ". In this embodiment, the overall message size needs to be known, for example, from the MAC or RLC headers, so the receiver knows how many bits are left for the SO and LF fields. The receiver also knows how many SO and LF pairs follow the last extension bit. Therefore, the receiver can calculate the size of the SO field and the LF field.

If the RLC state PDU is required to be byte-arrayed, the number of remaining bits is also divided by the number of segment fields indicated, and further steps must be taken. The resulting integer is used as the length, but the remaining bits are not used. As an example, if the remaining length is 51 bits and a byte array (8 bits) is used, the calculation result of 51/8 = 6mod3 (quote 6 remainder 3) is obtained. Therefore, in this example, the last 3 bits of the state PDU would not be used.

In the above example, LF is used to determine the end of the RLC PDU segment. However, as with SO, it is possible to use absolute offsets, which would fall within the scope of the present invention. In such cases, the offset would point to the original position of the last byte of the RLC PDU segment.

The content of the status message could describe whether the data was recognized as ACK or NACK. It can also contain a mixture of ACK and NACK with one or more additional bits, which could provide an appropriate ACK / NACK indicator.

The status message described in FIG. 6 should be seen as merely an example, and some applications also include additional fields such as type flags, additional length fields, etc. that indicate whether the PDU contains data or status. May be needed. These will also fall within the scope of the present invention.

Clear state information can also be added to the state report, in particular if the standard or embodiment allows reporting of multiple types of state, such as ANCK and ACK.

If the LTE system is configured to exchange status reports for only one type, eg NACK, then explicit status indications may also be needed. Alternatively, the status report sending entity may receive a request for a status report of some type (eg, NACK only) from the PDU transmitting entity and generate a status report for only the unreceived subset of the received segments. Sometimes.

From a further aspect of the invention, it can be considered that the RLC PDU status message is transmitted as a separate PDU or in addition to another PDU.

FIG. 7 shows a schematic flowchart of the method 700 of the present invention. Options and alternative steps are indicated by dashed lines.

As suggested in the above description, the method of the invention is a cellular communication system such as System 100 of FIG. 1, i.e. traffic is exchanged between a first transceiver such as UE120 and eNodeB 110 and a second transceiver. Intended to be used in a system.

Traffic in System 100 is sent in the form of data units, and each of these data units is given an identifier. The data unit can be segmented and the receiving transceiver can provide state information about whether the data unit was correctly received, partially received, or not received in the data frame or data unit. It can be transmitted to the transceiver on the transmitting side in the form. In this case, the transceiver on the transmitting side is the transceiver that transmitted the data.

According to method 700 of the present invention, as shown in step 705, state information transmitted to the transmitting transceiver if one or more data units are partially received or not received. Includes information about whether one or more data units were not received or were partially received, as shown in step 710. And if so, as shown in step 715, if one or more data units are partially received, it includes information about which part of these data units was not received.

In one embodiment of the invention, as shown in step 720, information about whether the data unit was partially received or not received is included as a flag in the data frame or data unit.

As shown in step 725, in a further embodiment of the invention, the information about which part of the data unit was not received is said to be information indicating the first and last parts of the unreceived data unit. Included in a frame or data unit.

Step 730 shows that: That is, from one aspect of the invention, if the data frame or data unit from the transmitting transceiver is segmented or re-segmented, the receiving transceiver is the last. If the segment has not been reached, this is due to the receiving transceiver telling the transmitting transceiver a special predetermined value of information about the last unreceived portion of the received segment. , Can be shown appropriately.

Step 735 indicates that: In one embodiment of the invention, if the data frame or data unit from the transmitting transceiver was divided into segments and the last segment did not reach the receiving transceiver, this would be received. It can be indicated to the transmitting transceiver by the side transceiver.

As suggested in the previous part of this description, and as shown in step 740, the method 700 of the present invention is suitable for LTE (Long Term Evolution) systems such as System 100 shown in FIG. can do.

When applying the method 700 of the present invention to an LTE system, the data PDU will be transmitted in DL and the corresponding state PDU will be transmitted in UL. This is shown in step 750, where the "transceiver on the transmitting side" is the eNodeB of the LTE cell and the "transceiver on the receiving side" is the user equipment (UE) of the LTE cell.

The present invention is equally well applicable in the opposite case, in which case the data PDU will be transmitted by UL and the corresponding state PDU will be transmitted by DL. This is shown in step 745. In this case, the "transceiver on the transmitting side" is the UE of the LTE cell, and the "transceiver on the receiving side" is the eNodeB of the LTE cell.

With respect to the state PDU 300 shown in Figure 3, it has been pointed out that the information from the receiving transceiver to the transmitting transceiver can be sent as a message that may contain one or more of the following: To. That is, · For example, information (D / C) about the characteristics of a message, such as a data or control message, For example, in the case of a control message, information about the type of message (PDU type) in the above characteristics, such as a status message, -Data (ACK) that confirms that a data unit or data frame in the form of a fixed sequence number has been received correctly, and The first expansion indicator (E) and Data (NACK) relating to the data unit or data frame that was not received or was partially received in the form of a fixed sequence number (SN) of the data unit or data frame. The second expansion indicator (F) and -Information about the beginning (SO11, SO21) and the end (SO12, SO22) of the data that was not received Is.

In a typical state PDU shown in FIG. 3, the first extended indicator E is the first extended indicator and the second extended indicator, namely E and F, which are partially received or received. Indicates the presence or absence of a set of data units or data frames that are different from the data NACK represented in the form of the data unit or data frame identifier SN. The second extended indicator F indicates the presence or absence of information about the beginning SO11, SO21 and the ending SO12, SO22 of the data that was not received.

The present invention also discloses transceivers used in systems to which the present invention applies. As is clear from the above description, the present invention presents the present invention when a data PDU is transmitted in DL and a corresponding state PDU is transmitted in UL, or conversely, a data PDU is transmitted in UL and a corresponding state. It can be applied to any case where the PDU is transmitted by DL. In the former case, the data transmit transceiver (when applied to E-UTRAN) is the eNodeB and the receive transceiver, i.e. the transceiver that transmits the state PDU, is the UE. In the latter case, the data transmitting transceiver is the UE and the receiving transceiver, i.e. the transceiver transmitting the state PDU, is the eNodeB. Therefore, the transceiver of the present invention may be either an ENodeB of E-UTRAN or a UE of E-UTRAN.

FIG. 8 shows a block diagram of a general transceiver 800 of the present invention. This transceiver is used as the eNodeB of E-UTRAN or the UE of E-UTRAN shown in Figure 8. As shown in FIG. 8, the transceiver 800 will include the antenna shown in block 810 and will also include a receiver 820 and a transmitter 830. Further, the transceiver 800 also includes a memory 850 along with a control means 840 such as a microprocessor. In addition, if the transceiver 800 is used as an eNodeB, the transceiver 800 also has an interface 860 for other components of the system, separate from the UE. Interface 860 is shown by the dashed line because this interface does not have to exist if transceiver 800 is UE.

Transceiver 800 can use antenna 810, receiver 820, and transmitter 830 to send traffic to and receive traffic from the second transceiver in its system. The transceiver 800 can then use the control means 840 together with the memory 850 to transmit the traffic in the form of a data unit.

Further, the control means 840 and the memory 850 can be used to assign an identifier such as a sequence number to each of the data units. Also, the same means, namely blocks 840 and 850, can be used to divide the data unit into segments.

The transceiver 800 according to the invention also uses control means 840, memory 850, transmitter 830, and antenna 810 to receive correctly received data units, partially received data units, or not received. Information about the data unit is transmitted in a data frame or data unit to a second transceiver, the transceiver that transmitted the data.

In addition, the transceiver 800 uses control means 840 and memory 850 to either not receive one or more data units, or if partially received, no data units received, or Includes information about whether it was partially received in the state information, and if one or more data units were partially received, about which part of those data units was not received. Information can be included.

In one embodiment, the transceiver 800 uses means 840 and 850 to include information about whether the data unit was partially received or not received as a flag in the data frame or data unit. be able to.

Further, in a further embodiment, blocks 840 and 850 are used by the transceiver to provide information about which part of the data unit was not received within the data frame or data unit of the data unit that was not received. It can be included as information indicating the first and last parts.

From another aspect of the invention, the control means 840, memory 850, transmitter 830, and antenna 810 are used by the transceiver 800, and if the data frame or data unit from the transmitting transceiver is segmented. If the last segment did not reach the transceiver 800, this can be indicated to the transmitting transceiver.

Instructions for missing segments are properly performed by using special predetermined values for information about the last part of the missing segment.

In one embodiment, the control means 840 and the memory 850 are used by the transceiver 800 to provide information about which part of the data unit that was partially received by the data frame or data unit was not received. It can also be included as information indicating the identifier of, and also as information about the beginning of unreceived data and the amount of unreceived data in the data unit.

In addition, the antenna 810, transmitter 830, control means 840, and memory 850 can be used by the transceiver according to the invention to transmit state information to the transmitting transceiver as a message as shown in 300 in FIG. it can. The information can include one or more of the following: That is, · For example, information (D / C) about the characteristics of a message, such as a data or control message, For example, in the case of a control message, information about the type of message in the property, such as a status message, -Data (ACK) that confirms that a data unit or data frame in the format of a certain sequence number has been received correctly, and The first expansion indicator (E) and Data (NACK) about unreceived or partially received data units or data frames in the form of a fixed sequence number, The second expansion indicator (F) and -Information about the beginning (SO11, SO21) and the end (SO12, SO22) of the data that was not received Is.

Appropriately, the first expansion indicator (E) is a unit or unit that is partially received or not received with the first expansion indicator (E) and the second expansion indicator (F). Indicates the presence or absence of a set of frames that is different from the data unit or data (NACK) represented in the form of a data frame identifier (SN). Further, the second extended indicator (F) indicates the presence / absence of information about the beginning (SO11, SO21) and the end (SO12, SO22) of the unreceived data.

The present invention is not limited to the examples described above and the examples shown in the drawings, and can be freely modified within the scope of the appended claims.