A method and a device for improved status reports

TECHNICAL FIELD [0001] The present invention discloses a method for use in a cellular communication system in which system traffic can be exchanged between the first and second transceiver devices. This traffic is sent in data modules, each of which is given an identifier and which can be divided into segments. The receiving transceiver can send to the sender transceiver, i.e. to the transceiver from which this data was transmitted, status information in data frames or data modules about the sent data modules.

BACKGROUND ART [0002] In the 3GPP LTE (3rd Generation Partnership Project, Long Term Evolution) project for cellular communication systems for communication between users in the cell and the cell control node, i.e. the eNodeB node, "evolved NodeB", uses the RLC protocol (Radio Link Contro!).

[0003] In the RLC protocol, traffic is sent as so-called PDU modules, i.e. Protocol Data Units, which are identified by assigning sequence numbers. In response to PDU modules from the sending party, the receiving party sends to this transmitting party the so-called RLC status PDU modules ACK and / or NACK, i.e. acknowledgment (ACK) that the data was received correctly, or information (NACK) that the data was not received correctly, i.e. were received only partially or not at all. ACK and NACK messages in RLC status PDUs are sent as PDU sequence numbers to identify the PDU in question.

[0004] In LTE systems, RLC PDUs can be segmented, with the consequence that there are then two or more PDUs with the same sequence number, since sequence number is a property of the PDU. The process of segmenting PDUs is also referred to as resegmentation.

[0005] Due to the resegmentation in the LTE system, the sequence numbers are not sufficient to identify the data for which the ACK or NACK message is sent.

[0006] Document R2-073174, RLC status PDU type and format, discusses the type and format of the RLC status PDU for the UTRAN system. Said document discloses a method of indicating feedback for segmented PDUs in a state PDU.

SUMMARY OF THE INVENTION [0007] As a result of the above discussion, there is a need for a solution by which ACK and NACK messages can be identified in 3G LTE systems that are sent by the receiving side to the transmitting party in relation to data segments in response to which they have been sent.

[0008] In addition, another need that the solution under consideration should address should be that it should be

-2 it is possible to send a variable number of NACK messages.

[0009] To this need, the present invention relates to disclosing a method for use in a cellular communication system in which system traffic can be exchanged between the first and second transceiver devices. Traffic in this system is sent in data modules, each of which is given an identifier. These data modules can be segmented, and the receiving transceiver can send to the sender transceiver, i.e. to the transceiver device from which this data was sent, status information in data frames or data modules on correctly received, partially received or missed data modules. [0010] According to the method of the present invention, in the case of one or more partially received or missed data modules, the status information that is sent to the transmitting transceiver contains information on whether the data module has not been received or were partially received, and in the case of a partially received data module, which parts of the data modules were not received.

[0011] Thus, with the present invention, it becomes possible to unambiguously indicate by the receiving transceiver the unclaimed portions of data modules to the transmitting transceiver, which in turn allows the transmitting transceiver to retransmit these parts.

[0012] The present invention also makes it possible to identify roughly any amount of unclaimed data, which was another need to be solved by the present invention.

[0013] In one embodiment of the present invention, information whether a data module has not been received or has been partially received is contained as a flag in said data frames or data modules.

[0014] In another example, information about which parts of the data module are not received is contained in the data frames or data modules as information that indicates the first and last part of the unclaimed data.

[0015] In yet another aspect of the present invention, in the case in which the frame or data module of the transmitting transceiver was segmented and one or more recent segments did not reach the receiving transceiver, this may be indicated by the receiving transceiver transceiver.

[0016] In a further embodiment of the present invention, information about which parts of the data module have not been received is contained in data frames or data modules as information that indicates the identifier of the data module as well as information about the beginning of the unclaimed data in said data module and amount of data not received.

[0017] These and other aspects and advantages of the present invention will be described in more detail in the detailed description below.

[0018] The present invention also discloses a transceiver for use in the system of the present invention.

BRIEF DESCRIPTION OF THE FIGURES

[0019] The present invention will be described below in more detail with reference to the figures of the attached drawing, in which

Fig. 1 is a schematic view of the system in which the present invention may be used,

Figs. 2-6 show various embodiments of the present invention,

Fig. 7 shows a flow chart of the method according to the present invention,

Fig. 8 shows a block diagram of a transceiver in accordance with the present invention.

DETAILED DESCRIPTION [0020] Fig. 1 is a schematic view of the system 100 in which the present invention may be used. As already mentioned, the present invention is mainly intended for systems such as 3GPP LTE, i.e. Third Generation Partnership Project, Long Term systems

Evolution, sometimes simply called LTE systems, and in the 3GPP project known as evolved UTRAN or E-UTRAN. In this description, these names will be used interchangeably.

[0021] As shown in Fig. 1, the LTE system 100 may include a number of so-called cells, one of which is shown as 130 in Fig. 1. Each cell in the LTE system can accommodate a number of users, sometimes generally referred to as UEs. In Fig. 1 one UE is shown symbolically with reference number 120.

[0022] LTE systems, e.g. 100 of Fig. 1, also contain so-called The "eNodeB" node, evolved NodeB, for each of the cells. One of the functions of the cell's eNodeB node is to control traffic to and from users in the cell. In Fig. 1, the eNodeB node 110 is shown as the eNodeB node for cell 130.

[0023] Traffic from the eNodeB node to the UE is called downlink traffic, or simply DL (downlink) traffic, and traffic from the UE to the eNodeB node is known as uplink traffic, or simply UL traffic ( uplink).

[0024] In LTE systems, the RLC protocol Radio Link Control is used to communicate between the eNodeB node and UEs in the cell.

According to the RLC protocol, in LTE systems, traffic between two transceiver devices, i.e. the UE and its eNodeB, is sent in a so-called PDU modules, called Protocoi Data Units. According to the RLC protocol, each PDU module is assigned an identifier, the so-called a sequence number that allows both the sending and receiving sides to identify the PDU.

[0026] The following description assumes that data PDUs are sent via eNodeB, i.e. via DL, and that status PDUs are sent by UE, ie via UL. However, it should be noted that this only an example intended to facilitate the reader's understanding of the present invention, and the present invention may very well be used in a different direction, i.e. for data PDUs on the UL link and state PDUs on the DL link. It can be mentioned here that the EUTRAN RLC protocol can operate in various modes, configured by the eNodeB node, namely in Acknowledged Mode (AM), Unacknowledged Mode (UM) and Transparent Mode (UM). TM, transparent mode), Status PDUs are only in AM mode. [0027] If the eNodeB 110 sends a PDU that contains data for UE 120, i.e. module

-4PDU data, the UE may respond with a so-called a state PDU module, i.e. a PDU module that indicates to the eNodeB node the status of receiving data from a data PDU module that has been issued from this eNodeB node.

[0028] In the state PDU module for the eNodeB node, data modules that have been correctly received by the UE are confirmed by this UE using the so-called ACK messages or indicators, while data modules that were received incorrectly, i.e. only partially received or not received at all, are indicated by this UE by means of so-called negative ACK, NACK. If the eNodeB node from which the data originated receives a NACK message in response to the sent data, this eNodeB node thus knows that this information should be retransmitted, usually until the ACK message is received. In the case of DL data traffic, the UE therefore sends to the eNodeB, in response to data PDUs from this eNodeB, status PDUs with ACK and / fub NACK messages.

[0029] ACK messages provide information to which sequence number of PDUs have been correctly received. This can be done by providing the highest number of a successfully received PDU or the first number of a missed PDU, [0030] In the E-UTRAN RLC protocol, data PDUs can be re-segmented, i.e., the block of data from the previously created RLC PDU can be split during retransmission Segments sent separately.

[0031] It is accepted in the LTE system that RLC PDUs should be identified by the sequence number of the original RLC PDU, as well as the so-called segmentation offset (SO), which indicates the beginning of the segment in the original RLC PDU. The ACK or NACK message is sent in the form of the sequence number of the original RLC PDU, ate because the segmentation may occur, the segments to which the ACK or NACK messages relate from the UE cannot be uniquely identified on the eNodeB by means of the sequence number, and not even SO shift, due to the fact that segmentation can occur in a number of "generations", i.e. multiple re-segmentation may occur, and the eNodeB node does not know which generation the ACK / NACK messages relate to.

[0032] The present invention is intended to solve this problem, i.e. to identify the RLC PDU data module to which the ACK / NACK message relates.

[0033] Regarding state PDUs, different cases can be distinguished:

a. Status PDU module with only one ACK message and no NACK messages.

b. Status PDU module with one ACK message and one or more NACK messages, for which there are two sub-cases:

i. One or more NACK messages are "segmented NACK", ii. All NACK messages are unsegmented NACK.

[0034] For the above case "a", the present invention proposes a state PDU module which is indicated in Fig. 2 with reference number 200. As shown in Fig. 2, the state PDU module 200 includes a D / C 210 field which indicates whether PDU 200 module is a data or control PDU module. It is understood that

-5The status PDU module is a control PDU module.

[0035] In addition, the status PDU 200 includes the ACK field 220, with the ACK message provided in the form of a sequence number, SN, of the RLC PDU to which the ACK message relates. Module

The status PDU 200 also includes an indicator, e.g., a flag or bit, shown in Fig. 2 as "E-bit" 230, which is used to indicate the presence or absence of NACK messages in the status PDU 200.

[0036] In the absence of NACK messages in the status PDU, i.e. in the case shown in Fig. 2, so-called so-called status PDU 200 can be used to achieve the appropriate alignment. "fill" or "empty" bits. One example of such alignment is the so-called "Octet alignment", ie, alignment that is used if the state PDU is split into data octets. This alignment is shown in Fig. 2 as 240.

[0037] Turning now to the case indicated above as "bi", i.e. in which one or more NACK messages relates to segmented data modules, in other words in the case in which the NACK messages indicate that the data module has been partially received, a concept will be presented used in the present invention. This concept is referred to herein as "segment offset pairs" or "Segment Offset pairs," i.e. a data pair, one of which is used to indicate the first unclaimed data octet of the PDU to which the NACK message applies, and the other is used to indicate the last unclaimed data octet to which the NACK message relates. It may be added here that although octets were used to illustrate examples of the invention because octets are used in the LTE RLC protocol, naturally the present invention can also be used if other size data is being transmitted.

[0038] An example of the state PDU module format 300 that can handle the above "bi" case is shown in Fig. 3. Like the state PDU module format 200 of Fig. 2, the format of the state PDU module 300 includes a bit field that indicates whether the PDU 300 module is a data or control PDU module, as well as an ACK field with an ACK message provided in the form of a sequence number, SN, sequence number of the RLC PDU module to which the ACK message relates. The status PDU module 300 also includes an indicator, e.g. the flag or bit, shown in Fig. 3 as the "E-bit", which is used to indicate the presence or absence of NACK messages in the status PDU 300.

[0039] If, as in Fig. 3, one or more NACK messages are contained, each of these NACK messages is followed by a bit fub flag "E" and a bit or flag "F", wherein bit / flag E indicates whether another NACK message is present or not, and the F bit / flag indicates whether the SO pair is included for this particular NACK message, or not. In other words, it can be said that the F bit / flag indicates whether the data module to which the NACK message relates was segmented because this is the only case where SO pairs are used.

[0040] It may also be mentioned that the case (e.g.) of two missing but non-consecutive parts of one and the same PDU module can be handled by the present invention such that one and the same SN number of the NACK message occurs twice, but with different SO pairs .

[0041] As in the example of Fig. 2, the ACK and NACK messages of the state PDU module 300 in Fig. 3 are provided in the form of the sequence number, SN, ang sequence number of the RLC PDU module to which the ACK or NACK message relates, for which reason ACK / NACK messages are represented as ACK_SN

-6 or NACK_SN.

[0042] After the last NACK message of the status PDU module 300 of Fig. 3, SO pairs are included for NACK messages for which the "F" flags / bits have been set. Thus, the SO pair shown as SO11 and SO12 "belongs" to NACK1_SN, and SO pair shown as SO21 and SO22 "belongs" to NACK2_SN. Also, as shown in Fig. 3, "padding", PAD, may be used in the state PDU module 300 of Fig. 3 to achieve octet alignment or for a similar purpose.

[0043] Returning now to the information contained in the SO pairs, the first SO offset in the SO pair indicates the first missing data octet from the PDU module, and the last SO shift in the pair indicates the last missing octet data from this PDU module.

[0044] It should be noted that if the data from the received PDUs, i.e., from the PDUs to which the ACK / NACK messages relate, are organized in groups other than octets, the present invention can of course also be used for such systems. Then SO pairs would indicate, in a similar way to the one described above, the beginning and end of data from the PDU module to which the NACK message relates.

[0046] It can also be added that the state PDU modules of the present invention can also be expanded by means of a field, e.g., after a D / C field, which indicates the nature of the state PDU module, e.g. if RLC control PDU modules other than modules are used PDU STATUS. This field is included in the example shown in Fig. 3, indicated as "PDU type". The same principle, i.e. PDU type, can be used in the version shown in Fig. 2.

[0046] Still referring to the status PDUs of the present invention, it should also be pointed out that the order of the data fields in the status PDUs shown in Figs. 2 and 3 are only examples of possible embodiments of the invention, the data fields in the status PDUs of the present invention they can be moved to other positions in the PDU state without affecting the functionality of the invention, e.g. to obtain octet alignment. Eg. in the case of only the ACK message, without the NACK messages, i.e. the example shown in Fig. 2, the PDU status module 200 could start with the D / C field followed by the E bit followed by the fill and the ACK message with its number sequential at the end.

[0047] Turning now to the case shown as b-ii above, i.e. in which one or more NACK messages relates to unclaimed data PDUs, unlike partially received data modules, it is handled as follows: flag F, corresponding to this NACK messages, indicates that for these NACK messages, no SO pairs are included in the status PDU.

[0048] A special case to which the present invention also applies is when the last PDU of the RLC PDU is not received by the UE (still assuming the case of data PDUs on the DL link). Consider the example in which the RLC PDU module with sequence number 10 was segmented into 3 RLC PDU modules, which PDU segments contain octets 1-10,1125 and 26-40, respectively.

[0049] Let us now consider the case in which the UE received the first two segments of the RLC PDU module 10, i.e. octets 1-10 and 11-25, and also received another RLC PDU module, i.e. RLC PDU module 11, in full, but this UE did not receive the last segment of the RLC PDU 10, i.e. octets 26-40.

[0050] In this case, the UE knows that the RLC segment has been lost, but does not know its length, by

- what UE may not set the second segmentation offset value in the corresponding SO pair in the state PDU. The solution to this, which is proposed by the present invention, is to allow the particular value of the SO shift to indicate that the end of the segment covered by the NACK message is not known. Thus, when the eNodeB node receives the NACK message for the RLC PDU 10 module, the first SO offset is set to 26 and the corresponding second SO offset is set to a special value that tells the eNodeB node that all data octets from 26 and subsequent from the RLC PDU module 10 must be retransmitted.

[0051] In some cases, SO pair is not always necessary to achieve the desired effect. As will be shown below, complete identification of unclaimed data can be achieved using two bits in the "Fⁿ.

[0052] This is shown in the example of Fig. 4, which shows all four combinations of two bits in field F, i.e. 00, 01, 10 and 11. In Fig. 4 the meanings of each of these combinations are also indicated. below:

Importance

Field F

The NACK message applies to the entire RLC PDU module, so SO offsets are not necessary.

The NACK message applies to the first part of the RLC PDU module, 1 SO offset is needed to indicate the last unclaimed data group, e.g. octet.

The NACK message applies to the last part of the RLC PDU module, 1 SO shift is needed to indicate the first unclaimed data group, e.g. octet,

The NACK message applies to the central part of the RLC PDU, 2 SO offsets are needed to indicate the first and last missed data group, e.g. octet.

[0053] It should be pointed out that in the case shown in Fig. 4, as in the previous examples, a "type field" may be required to separate the state RLC PDUs from other RLC PDU control modules. [0054] In another embodiment of the present invention , partially received RLC data PDU modules from the DL link are indicated to the eNodeB by the UE in the RLC state PDU module in the UL link in a slightly different way than the one shown above, i.e. SO pairs. In the example under consideration, the state RLC PDU module 500 shown in Fig. 5, the RLC PDU module on the UL link from the UE includes the NACK field, shown as 510, as well as the sequence number field, SN, shown as 520, which indicates the sequence number of the PDU module RLC data to which the NACK message applies. Naturain, in the embodiment 500, the SN number may also be included in the NACK message as shown in the previous examples.

[0055] As in previous examples, example 500 also includes the use of the "E" field, shown in Fig. 5 as 530. However, the meaning of this field E, i.e. bit or flag, differs slightly from that of the previous examples: in the example 500 of Fig. 5, field E is used to indicate whether a NACK message

-8510 applies to the entire RLC data PDU, or data within the RLC data PDU. For example, if poie E is zero, E = 0, it may mean that the NACK 510 message applies to the entire PDU module of the RLC data, which is identified by the SN 520 number.

Otherwise, if E-0 means the entire PDU, then E = 1 means that the NACK 510 message relates to data in the PDU identified by SN 520. In this case, for the eNodeB to identify the data in question, status PDU module 500 contains information. This information, regarding the data in Example 500, includes a segment offset value, SO, segment offset, shown in Fig. 5 as 540. This SO 540 value indicates the byte offset or the beginning of the unclaimed data from the DL link. However, unlike the previous examples, Example 500 does not use SO pairs to indicate all unclaimed data. Instead, Example 500 uses the Length Field, LF, whose value indicates the beginning of unclaimed data, starting with the value SO 540, up to the last byte of unclaimed data.

[0057] As can be seen, in this embodiment of the present invention, i.e. that shown in Fig. 5, to achieve effective retransmission from the original data sender, the exact number of bytes that should be retransmitted must be indicated to the sender. Because the LTE RLC PDU modules can be quite large (e.g. 32767 bytes), the fields (e.g. SO ί LF) needed to indicate RLC PDUs would also have to be quite large. However, as can also be seen, in many cases the maximum theoretical size of SO and LF fields need not be used, which would lead to inefficient use of data space if the size of the fields were static.

In one embodiment of the present invention, the inventors propose to avoid this problem, i.e. inefficient use of space for data for SO and LF fields. This example will be described below.

[0059] In this aspect of the present invention, the basic principle is that the sizes of SO and LF fields in the RLC state PDU can be adapted to the needs of the current RLC state PDU. Of course, it is possible to use two different sizes for SO and LF values, e.g. 6 bits for RSO and 4 bits for RSL. However, it is assumed in the following description that the size is the same.

[0060] If, as proposed in this aspect of the present invention, dynamic length length poia is used for SO and LF, the eNodeB (for DL ​​data and UL status messages) must know the size of this length length to could read the status message.

[0061] The first way to achieve this is to include an additional field in the header of the RLC PDU status message indicating the size of the SO and LF fields. For example, there could be a field indicating that all length fields in the current message have 6 bits. This size could be variable for messages about the status of the RLC PDU.

[0062] If SO and LF values ​​were to receive values ​​of different sizes, two such lengths would be needed or a predetermined relationship between them could be used, e.g. the SO value is always x bits longer / shorter than the LF value. However, because SO and LF values ​​are usually of the same order, this optimization might not be required.

[0063] According to another possible aspect of the present invention, an explicit indication of the size of the SO ί LF fields is superfluous due to the reorganization in the status message of the RLC PDU. In this aspect

It is proposed to transfer SO and LF "length fields" to the end of the RLC PDU module status message, which will be described with reference to Fig. 6.

[0064] In the example shown in Fig. 6, status information for all included PDUs is provided first, i.e., SN segment number, RF resection flag, and extension bit "E" (extension). In this way, it also becomes possible to include complete PDU modules for which there is no need to send any specific segment information. For PDUs that have been resegmented, the RF flag is used to indicate that segment location and length information continue to appear, and SO and LF values ​​are added to the message frame.

Thus, in the example of Fig. 6, the "dynamic" part of the status message, i.e. the SO and LF values, follows the last bit of the extension E, i.e. the first bit E of the value indicating that it is the last, e.g. "0" because in this example the total message size must be known, e.g. from the MAC header or RLC, the receiver knows how many bits are left for the SO and LF fields, and also knows that the SO and LF pairs will follow the last bit of the extension. Thus, the receiver can calculate the sizes of SO and LF fields.

[0066] If it is required for the RLC state PDU to be aligned with the byte, an additional step must be performed in that the number of remaining bits is also divided by the number of segments indicated. The resulting integer is used as the length, and the other bits are not used. For example, if the remaining length is 51 bits and byte alignment (8 bits) is used, we arrive at 51/8 = 6 mod 3. Thus, in this example, no 3 bits will be used at the end of the state PDU.

[0067] In the above example, the LF value is used to determine the end of the RLC PDU. However, it is possible to use an absolute shift within the scope of the present invention, similar to the SO shift. In this case, this shift would indicate the original location of the last byte in the RLC PDU.

[0068] The contents of the status message could describe the data to which the ACK or NACK message relates. A combination of ACK and NACK messages could also be posted with one or more additional bits to provide the appropriate ACK / NACK indicator.

[0069] The described status message of Fig. 6 can only be seen as an example, in some applications additional fields could be required, e.g. flags of type dfa indicating whether the PDU module contains data or status information, additional length fields, etc. they would fall within the scope of the present invention. Explicit status information can also be added to status reports, especially if the standard or implementation allows reporting a number of state types, e.g. NACK and ACK.

[0070] Explicit status indication may also be necessary if the LTE system is adapted to exchange status reports of one type, e.g. only NACK messages. Alternatively, the status report sending module may receive from the PDU sending module a request for a status report of a certain type (e.g., only the NACK message) and then generates this status report only for a subset of received segments that have not been received.

[0071] In another aspect of the present invention, it can be envisaged to send an RLC PDU module status message as a separate PDU module or connected to another PDU module.

[0072] Fig. 7 is a simplified flow chart of method 700 according to the present invention. Stages that are options or alternatives are shown by dashed lines.

[0073] As indicated in the above description, the method of the present invention is intended for use in a cellular communication system, e.g. the system 100 of Fig. 1, i.e. a system in which traffic can be exchanged between the first and second transceiver , e.g. UE 120 device and eNodeB 120 node.

[0074] Traffic in the system 100 is sent in data modules, and each of these data modules is assigned an identifier. Data modules can be divided into segments, and the receiving transceiver can send to the transmitting transceiver, i.e. to the transceiver from which the data was sent, status information in data frames or data modules with correctly received, partially received or missed data modules.

[0075] According to the invented method 700, as indicated in step 705, for one or more partially received or missed data modules, the status information that is sent to the transmitting transceiver contains, as shown in step 710, information about whether the data module or modules were not received or were partially received, and if so, as shown in step 715, in the case of one or more partially received data modules which parts of these data modules have not been received.

[0076] In one embodiment of the present invention as shown in step 720, information whether a data module has been partially received or not received is included as a flag in said data frames or data modules.

[0077] As indicated in step 725, in a further embodiment of the present invention, information about which parts of the data module has not been received is contained in said data frames or data modules as information indicating the first and last parts of the unclaimed data module.

[0078] Step 730 indicates that in one aspect of the present invention, if the frame or data module of the transmitting transceiver has been segmented or resegmented and the last segment has not reached the receiving transceiver, this may be indicated by that receiving device the transceivers of this transmitting transceiver, respectively by means of a specific predetermined value for information on the last part of the missed received segments.

[0079] Step 735 indicates that in one embodiment of the present invention, if the frame or data module of the transmitting transceiver has been segmented and the last segment has not reached the receiving transceiver, this may be indicated by the receiving transceiver - receiving to this transmitting transceiver.

[0080] As already indicated in the present description and as shown in step 740, the method 700 of the present invention can be suitably used in the LTE Long Term Evolution system, e.g. the system 100, which is schematically shown in Fig. 1.

[0081] If the invented method 700 is used in an LTE system, data PDUs may be sent over a DL link, and corresponding state PDUs will then be sent over a UL link as indicated in step 750, in which case the "transmitting" the transceiver device 'is the LTE cell's eNodeB node, and the' transceiver transceiver 'is the user device (UE) in the LTE cell.

[0082] The present invention may equally well be used in the opposite case such that data PDUs can be sent over a UL link and the corresponding status PDUs will then be sent over a DL link as indicated in step 745, in which case the above-mentioned "transmitting transceiver" is the UE in the LTE cell, and the receiving transceiver is the LTE cell's eNodeB.

[0083] With reference to the state PDU module 300 shown in Fig. 3, it can be pointed out that information from the receiving transceiver to the transmitting transceiver may be sent as a message which may include one or more of:

• Information (D / C) about the nature of the message, e.g. data or control message, • Information (PDU type) about the type of message about the nature, e.g. status message in the case of a control message, • Data (ACK) confirming correctly received module or data frame, in the form of a certain sequence number, • Indicator of the first extension (E), • Data (NACK) regarding a missed or partially received module or data frame, in the form of a certain sequence number (SN) of said module or data frame.

• Second extension indicator (F), • Information about the beginning (SO11, SO21) and the end (SO12, SO22) of unclaimed data.

[0084] In the exemplary state PDU shown in Fig. 3, the first extension indicator, E, indicates the absence or presence of a set containing the remaining of the first and second extension indicators, i.e. E and F, as well as the NACK data regarding partially received or a missed module or data frame in the form of an identifier, SN, that module or data frame. The second extension indicator, F, indicates the absence or presence of information about the beginning, SO11, SO21, and the end, SO21, SO22, of unclaimed data.

[0085] The present invention also discloses a transceiver for use in a system in which the present invention applies. As can be seen from the description above, the present invention can be used both when data PDU modules are sent via DL link and the corresponding state PDU modules are sent via UL link, in which case the transceiver sending data (in the case of applications in E-UTRAN system) is the eNodeB node, while the receiving transceiver, i.e. the transceiver that transmits the status PDUs is the UE, and otherwise the data PDUs are transmitted over the UL link and the corresponding status PDUs are transmitted over the DL link, in which case the transceiver device the sender is the UE and the sender is the transceiver. i.e. the transceiver that transmits status PDUs is the eNodeB node. Thus, the transceiver device of the present invention can be both an eNodeB node of the E-UTRAN system and an UE of the E-UTRAN system.

[0086] A block diagram of a generic invented transceiver 800 for use as an eNodeB node of the E-UTRAN system or an E-UTRAN system UE is shown in Fig. 8. As indicated in Fig. 8, the transceiver 800 includes the antenna, shown as block 810, and also includes a receiving portion 820 and a transmitting portion 830. In addition, the transceiver 800 also includes control means 840, e.g., a microprocessor, as well as memory 850. In addition, if the transceiver 800 is to be used as an eNodeB, then the transceiver 800 also includes an interface 860 to other system components, bypassing UEs. Because this interface may not be present if the transceiver 800 is a UE, the interface 860 is shown by dashed lines.

[0087] The transceiver 800 may use the antenna 810, the receiving portion 820 and the transceiver 830 to send traffic and to receive traffic from the second transceiver in the system, and the transceiver 800 may use control means 840 together with memory 850 for sending said traffic in data modules.

[0088] Control means 840 and memory 850 can also be used to give each of the data modules an identifier, e.g. a sequence number, and also the same means, i.e. blocks 840 and 850, can be used to divide these data modules into segments .

[0089] The invented transceiver 800 also uses control means 840, memory 850, transmitter 830 and antenna 810 to send to a second transceiver, i.e. the transceiver from which data was sent, in data frames or modules data information about correctly received, partially received or missed data modules.

[0090] In addition, the transceiver 800 may use control means 840 and memory 850, in the case of one or more missed or partially received data modules, to include in the status information information as to whether the module or data modules have been received. or partially received, and in the case of one or more partially received data modules, which parts of those data modules were not received.

[0091] In one example, means 840 and 850 are used by the transceiver 800 to include information as to whether the data module has been partially received or not received as flags in said data frames or data modules.

[0092] Additionally, in a further embodiment of the invention, blocks 840 and 850 are used by the transceiver to contain information about which parts of the data module were not received in said data frames or data modules as information that indicates the first and last part of the unclaimed data module, [0093] In another aspect of the present invention, control means 840, memory 850, transmitter 830, together with antenna 810, can be used by the transceiver 800 to indicate to the transmitting transceiver whether the frame or data module from this transceiver was segmented, and the last segment did not reach the transceiver 800.

[0094] The indication of the missing segment is the application carried out by using a specific predetermined value for information about the last part of the missing segment.

[0095] In one example, control means 840 and memory 850 may be used by transceiver 800 to include in said data frames or data modules information about which parts of the partially received data module have not been received as information, which indicates the identifier of the data module as well as information about the beginning of the unclaimed data from said data module and the amount of unclaimed data.

[0096] In addition, antenna 810, transmitter 830, control means 840 and memory 850 can be used by the invented transceiver to send status information to the transceiver as a message, e.g., 300 from Fig. 3, which can contain one or more of the following:

• Information (D / C) about the nature of the message, e.g. data or control message, • Information about the type of message about the nature, e.g. status message in the case of a control message, • Data (ACK) confirming correctly received modules or data frames, in the form of a certain sequence number, • Indicator of the first extension (E), • Data (NACK) regarding a missed or partially received module or data frame, in the form of a certain sequence number, • Indicator of the second extension (F), • Information about the beginning (SO11, SO21) and end (SO12, SO22) of unclaimed data.

[0097] Accordingly, the first extension indicator (E) indicates the absence or presence of a set containing another of said first (E) and second (F) extension indicators and data (NACK) for the partially received or missed data module or frame in the form of identifier (SN) of said module or data frame, and said second extension indicator (F) indicates the absence or presence of information about the beginning (SO11, SO21) and the end (SO12, SO22) unclaimed data.

[0098] The present invention is not limited to the embodiments described above and shown in the drawing, but may be arbitrarily changed within the scope of the appended claims.