KR20060136382A - Data packet transmission - Google Patents

Abstract

Using characteristic priority to obtain more robust Forward Error Correction (FEC) for RLC-controlled PDUs transmitted over High Speed-Downlink Shared Channel (HS-DSCH) is also a priority. The handling will cause the RLC (Radio Link Control) control PDU (Protocol Data Unit) to scrutinize the RLC data PDU. As a result, the RLC protocol operation is severely interrupted because the above operation relies on the delivery of a prescribed order for control and data PDUs. According to an exemplary embodiment of the present invention, two types of containers are provided where data packets can be sent, where the first type of container is provided with stronger error coding than the second type container, and Data packets containing instructions are sent only in the first container type with stronger error correction. To this end, improved forward error correction for control PDUs of the Acknowledgment Mode (AM) -RLC protocol of the Universal Mobile Telecommunication System (UMTS) can be provided.

Description

Data packet transmission method, communication system, sending station, receiving station, software program product {DATA PACKET TRANSMISSION}

The present invention relates to the field of data transmission in which data packets are transmitted from a transmitting station to a receiving station or exchanged between both transmitting and receiving stations. In particular, the present invention relates to a method for transmitting a data packet from a transmitting station to a receiving station, a data communication system for transmitting a data packet from a transmitting station to a receiving station, a transmitting station for a communication system, a receiving station for a communication system, And a software program product for transmitting data packets from a transmitting station to a receiving station.

The data transmission system as well as the method of transmitting data packets between the transmitter and the receiver are described, for example, in the 3rd Generation Partnership Project (3GPP) Technical Specification (TS), 3GPP TS 25.308 V5.2.0 ( 2002-03); Technical specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA); Full documentation; Third Generation Partnership Project Technical Specification Stage 2 (5th Edition) and 3GPP TS 25.321 V5.2.0 (2002-09); Technical specification group radio access network; Described in the Medium Access Control (MAC) Protocol Specification (Fifth Edition), all of which are incorporated herein by reference.

According to the present invention, data is transmitted in a Universal Mobile Telecommunication System (UMTS) transmitter of a Node B through downlink, that is, a high speed downlink shared channel (HS-DSCH) at high speed. The receiver is transmitted to a UMTS mobile station or a receiver of a user equipment (UE). In a sublayer of the MAC layer, a so-called MAC-hs (high speed) layer, the Hybrid Automatic Repeat Request (HARQ) retransmission protocol controls the retransmission of MAC-hs PDUs. At the receiver of the mobile station, the soft bits of the retransmitted MAC-hs PDU are soft combined with the soft bits of the initial transmission of this MAC-hs PDU. The MAC-hs layer is located on Node B. Peer entities of the HARQ retransmission protocol are therefore located at the Node B and the mobile station or UE.

In addition to the HARQ retransmission protocol (hereinafter referred to as the second retransmission protocol), there is another protocol related to the present invention, which is called a Radio Link Control (RLC) protocol (hereinafter referred to as the first retransmission protocol). The peer entities are located on the serving mobile station's serving Radio Network Controller (RNC) and the mobile station. For details of the RLC protocol, for example, Acknowledged Mode (AM) and Unacknowledged Mode (UM) data transfer, see 3GPP TS 25.322 V5.2.0 (2002-09) Third Generation Partnership Project Technical Specification. , A technical specification group radio access network, which is incorporated herein by reference.

This RLC protocol is responsible for the following operations. In other words,

RLC SDUs (Service Data Units), i.e. data units received at the next higher layer above the RLC layer, are segmented into fragments, the fragments being RLC PDUs (Protocol Data Units). That is, as a data unit, the RLC layer is transmitted as part of the next lower layer, which is the MAC layer, and if applicable, concatenate different RLC SDUs or fragments of different RLC SDUs into RLC PDUs (if applicable). concatenation)

The receiver (if so configured) controls retransmission of the RLC PDUs indicating that they were not sent correctly to the transmitter.

If data is transmitted over the HS-DSCH, this data is also always processed by the RLC protocol entity above the HARQ protocol, which is then configured for later (i.e., if the data is transmitted over the HS-DSCH). Can be. In other words,

-Approval mode (AM) data transmission, or

-Non acknowledgment mode data transmission.

"Approval mode data" is also abbreviated AMD, and "unauthorized mode data" is abbreviated UMD.

In both UMD and AMD transmissions, RLC PDUs have a sequence number, where UM specifies 7 bits and AM specifies 12 bits to encode the sequence numbers. This ranges from 0 to 127 for UM and from 0 to 4095 for AM. When configured for AMD transmission, the RLC protocol improves the reliability of data transmission by performing splitting (and possibly concatenation) of RLC SDUs into RLC PDUs and performing retransmission. If configured for UMD transmission, the RLC protocol performs only segmentation and possibly concatenation.

In terms of transmission, the RLC PDU is further processed by the MAC layer, or more precisely by the MAC-d layer, and may add a MAC header if logical channels should be separated. This MAC header identifies the logical channel over which the RLC PDU is sent. The MAC-d PDU (ie, protocol data unit generated by the MAC-d layer) is then delivered to the MAC-hs layer located at Node B of UMTS. Here, one or more MAC-d PDUs that should be directed to the same mobile station are compiled into MAC-hs PDUs. These MAC-d PDUs may belong to different logical channels (ie, may have different MAC headers). Thus, the MAC-hs PDU multiplexes MAC-d PDUs of different logical channels (but for the same receiving mobile station). In contrast, one MAC-d PDU always contains exactly one RLC PDU.

MAC-hs PDUs compiled from one or more MAC-d PDUs are further processed by the physical layer. In general, the data units processed by the physical layer in the HS-DSCH are called transport blocks, that is, the MAC-hs PDU is also a transport block and forms a transport block (ie, MAC-hs PDU here). The total number of bits to be called is called the transport block size. Physical layer processing for the transport block of the type MAC-hs PDU is as follows.

3GPP TS 25.212 V5.2.0 (2002-09), third generation partnership project, incorporated herein by reference; Technical specification group radio access network; As described in Multiplexing and Channel Coding (FDD) (Fifth Edition), the physical layer adds a Cyclic Redundancy Check (CRC) sum (24 bits), followed by the transport block (type MAC-hs PDU) Turbo coding (rate-1 / 3-turbo-coding) of 1/3 coding rate is applied to bits and CRC bits, that is, parity parity bits due to turbo coding are added.

Moreover, rate matching is applied as described in TS 25.212 V5.2.0, which regulates the number of bits, which are output to the number of bits of the 1/3 rate rate turbo encoder, over the air interface. It can be sent within 2ms. The number of bits that can be transmitted within 2ms over the air interface is not only the selected number of channelization codes (1 to 15 are used and has a spreading factor of mode 16), but also quaternary phase shift keying (QPSK). It depends on the chosen modulation scheme, which can be either shifted modulation) or 16 Quadrature Amplitude Modulation (16QAM). For example, the number of bits that can be sent in 2ms with 16QAM is twice as large as the number of bits that can be sent in QPSK.

Code rate matching can mean, for example, puncturing (creating a new symbol with some data set to '0'), i.e. deleting certain bits within a sequence of bits, resulting in The number fits exactly into the number of bits that can be transmitted within 2 meters over the air interface. The receiving side knows the positions of the smoothed bits and considers them as being in the decoding process, for example, bits with a value of zero.

If puncturing is to be applied, forward error protection (FEC) is necessarily weaker than no puncturing. The puncturing can be avoided, for example, if one or more channelized codes are used for transmission over the air interface.

For the MAC-hs PDU to be considered, a specific type of code rate matching is applied, and one of modulation schemes QPSK and 16QAM may be selected. This combination of coding matching and modulation schemes may also be referred to as coding and modulation schemes.

TS 25.212 V5.2.0 describes some additional physical layer processing steps for transport blocks in MAC-hs format, which may not be important to the present invention.

The 2ms period is also called the Transmission Time Interval (TTI) of the HS-DSCH. Since this period is the same as the period in which the transport block (MAC-hs format) is transmitted by the physical layer on the air interface, the inter-arrival time of the transport block (MAC_hs format) at the physical layer, that is, the MAC layer. This also corresponds to the time between successive data transfers between the physical and physical layers. In other words, the physical layer processes bits of one container, that is, MAC-hs PDU bits, within 2 ms of TTI and is ready to process bits of the next container after 2 ms. In principle, because of CRC addition and channel coding by turbo coding, the number of bits to be transmitted over the air interface is then larger than the number of bits in the container. If the number of bits X that the physical layer can transmit over the air interface (after turbo encoding) within a 2 ms TTI remains fixed for two containers of different sizes (i.e. different bits), then the size of the container is X-24 ( Where smaller, the smaller container's FEC will be stronger than the larger container's FEC, for example, because less puncturing is intended to be applied for the smaller container. Similarly, if a container of predetermined size S once has X bits (X> S + 24) and once has Y> X bits and is transmitted over the air interface after physical layer processing, the FEC will generally indicate that Stronger when used for transmission over

Next, with respect to UMTS, the term "container" refers to the bits of a transport block in the form of a MAC-hs PDU, ie MAC-hs PDU.

As cited above, according to the release 5 of the HARQ protocol in the MAC-hs of UMTS, the transmission of the transmission is performed without success in the last transmission, i.e. without decoding the received MAC-hs PDU without error. It is expected to allow the loss of the MAC-hs PDUs (protocol data units, ie, data packets passed from one protocol layer to the underlying protocol layer) that the maximum number has been reached. In this case, transmission of this MAC-hs PDU is stopped, and RLC-PDUs in the PDU are discarded. As a result, these lost RLC-PDUs must be retransmitted at the RLC protocol level (which means that the transmission is performed by the RLC protocol, and the retransmitted PDUs are RLC PDUs), resulting in significant delay, because the node This is because the Iub and Iur interfaces must pass through B and DRNC and DRNC and SRNC respectively. DRNC is also referred to as drift DNC (Drift Radio Network Control). A mobile station that has left a serving area of its respective Serving Radio Network Control (SRNC) is located in one cell handled by another RNC. This other RNC may then be called the drift RNC of the mobile station considered above.

UMTS's RLC (Radio Link Control) protocol uses two logical channels to transmit RLC PDUs (RLC Protocol Data Units) according to its type, i.e. one logical channel and RLC control for transmission of RLC data PDUs. Allows you to configure an AM (Accept Mode) RLC entity to provide one channel for the transmission of PDUs. Logical channels can be mapped to transport channels with different FECs (forward error correction), thereby providing a logical channel with a stronger FEC for RLC control PDUs, which are not retransmitted and at the same time This is most important for the correction function.

If data is transmitted via the HS-DSCH (high speed downlink shared channel) to the highest operating AM RLC protocol, since there is only one transport channel of type HS-DSCH, the logical channels are different transport channels (e.g. , With different FECs), and will only map to different priority classes in the MAC-hs entity on Node B. The MAC-hs on Node B has only this priority and no information on the importance of the data packet, indicating the need to apply a more robust Modulation and Coding Scheme (MCS) to Node B afterwards. can do. Using the attribute "priority" to achieve stronger FEC will also accompany priority handling, allowing the RLC control PDU to examine the RLC data PDUs. As a result, the operation of the RLC protocol relies on sequential delivery of control and data PDUs, which can be severely disturbed (eg, one MRW-controlled PDU is sent or an RLC reset process is initiated).

It is an object of the present invention to provide improved transmission of data packets containing control information.

According to an exemplary embodiment of the invention as described in claim 1, a method is provided for transmitting a first data packet and a second data packet from a transmitting station to a receiving station. The first data packet contains first data, in particular control commands, and the second data packet comprises second data. In addition, the first data packet and the second data packet are transmitted from the transmitting station to the receiving station in the container. According to an exemplary embodiment of the invention, the first container comprises at least one first data packet and a first error encoding is provided. On the other hand, the second container contains at least one second data packet but no first data packet, and second error encoding is provided. The first error coding is more powerful than the second error coding.

In other words, two kinds of containers are provided, where the first and second data packets can be transmitted. Type 1 containers are provided with stronger error encoding than type 2 containers, and data packets containing control instructions are sent only in type 1 containers with stronger error correction rates. The control commands may be control commands related to the first retransmission protocol.

In particular, the transmission of a first data packet containing a control command only in a type 1 container that is provided with more robust error encoding or error correction than a type 2 container may result in an error in the control command, that is, the data packet containing the first data packet. Will not increase the baud rate.

There may be different types of control commands, for some it is important not to be lost, in others it can be tolerated from time to time, or more often than for important control commands, and May be sent more often.

According to another exemplary embodiment of the present invention, the second data packets will contain these control instructions as well as containing data, which can be sent more frequently.

In UMTS 99, 4, and 5, these most important control commands (loss of these commands should be prevented as much as possible) may be as follows.

RESET PDU and RESET ACK PDU,

A STATUS PDU containing MRW SUFI (Move Receive Window Superfield), and a STATUS PDU including MRW_ACK SUFI (Move Receive Window Acknowledgment Superfield),

A STATUS PDU comprising a window SUFI (i.e. a super field telling the sender to change the transmission window to reduce its size, in particular to the sender).

Less important control commands, whose loss can sometimes be tolerated more than the loss of important control commands, include the MRW SUFI or MRW SUFI ACK as the remaining RLC control PDUs, in particular STATUS PDUs, as defined in TS 25.322. It does not, but sends information on the RLC PDUs, forwards the RLC entity, the correctly received STATUS PDU and expects to be sent.

According to another exemplary embodiment of the invention, as described in claim 2, the number of first and second data packets in the first container is less than the number of second data packets in the second container, such that The first data payload sent at is lower than the second data payload sent at the second container.

In other words, the first data packet is transmitted together with the second data packet in the first container, and its error protection is stronger than the error protection of the second container which alone contains the second data packet. According to an exemplary embodiment of the present invention, such enhanced error protection reduces the number of first and second data packets contained in the first container, while providing a wireless interface for the first container after channel coding and rate matching. This is achieved by keeping the total number of bits transmitted through constant. In other words, the data payload included is reduced, for example the number of parity information bits (parity bits) is increased. For a fixed number of coded bits transmitted over the air interface, the number of parity bits per payload bit (included in the first or second data packet) and the resulting FEC increase as the number of payload bits increases.

The term data payload relates to data actually transmitted (related to control commands or, for example, user data), but physical layer bits that include the bits used for this transmission, i.e. parity bits transmitted over the air interface. Is not relevant.

According to another exemplary embodiment of the invention, as described in claim 3, the first retransmission protocol controls the transmission or retransmission of the first and second data packets for the third data packet, and the second retransmission protocol is Control transmission or retransmission of the first and second containers. Further, corresponding container sequence numbers are provided to the first container and the second container, and corresponding data packet sequence numbers are provided to each data packet of the second data packet. According to an exemplary embodiment of the present invention, the first order or sequence of the first and second data packets occurring when the first and second data packets are transmitted in the first and second containers is determined by the first and second data packets. It remains unchanged when compared with the second order or sequence of the first and second data packets received by the second retransmission protocol.

In other words, the first and second containers always have the first and second data packets in such a way that there is no change in sequence in the progress of the first and second data packets and they are transmitted by the second retransmission protocol over the air interface. It includes. However, the second data packet can thus disappear, because in some cases they have been lost due to undesirable channel conditions.

According to another exemplary embodiment of the invention, as described in claim 4, the second retransmission protocol is a fourth data packet, wherein the second retransmission protocol is received from a first retransmission protocol located above the second retransmission protocol. It is determined whether this is the first data packet or the second data packet.

According to another exemplary embodiment of the present invention, as described in claim 5, the second retransmission protocol determines whether the fourth data packet is the first data packet or the second data packet by the fourth retransmission protocol. A determination operation is performed by analyzing header information related to a data packet. This determination may be performed by a scheduler, which is based on the first bit of the header, whether the data packet is a first data packet containing a control command or a second data packet comprising data. To determine the acknowledgment, the header information of all received first and second data packets is read.

According to another exemplary embodiment of the invention, as described in claim 6, the fourth data packet is classified when carried from the first transport protocol to the second transport protocol, wherein the first transport protocol comprises: If it is the first data packet, it is located above the second transmission protocol.

In other words, according to the exemplary embodiment of the present invention, the first data packet may be transmitted in a different logical channel than the second data packet, and thus a network node implementing the first transport protocol and a second transport protocol are implemented. The frame protocol for the transmission of data packets or similar entities between network nodes may determine from each logical channel whether the data packet contains control information or non-control data. The frame protocol can then immediately recognize which data packet received without parsing the header is the first data packet and the second data packet, so that the first data per control information (definition) Data packet).

According to another exemplary embodiment of the invention, as described in claim 7, the method is applied to a fast downlink shared channel of UMTS.

According to another exemplary embodiment of the present invention as described in claim 8, the first data packet is RLC control PDUs and the second data packet is RLC data PDUs.

According to another exemplary embodiment of the invention, as described in claim 9, the first retransmission protocol controls the transmission or retransmission of the first and second data packets for the third data packet, and the second retransmission protocol. Controls the transmission or retransmission of the first and second containers. In addition, a corresponding container sequence number is provided to the first container and the second container, a corresponding data packet sequence number is provided to each data packet of the second data packet, and a receiving entity of the first retransmission protocol receives the second data packet. Discarding, the sequence number is outside the receiving window. According to an exemplary embodiment of the present invention, the first parallel entity of the second peer entities of the first retransmission protocol may initiate a reset of both parallel entities, wherein the reset may be performed by the first and second of the first data packet. Completed by a second reset message, the reset causes the first entity to send the first reset message to the second entity and the second entity sends the second reset message to the first entity in response to the first reset message. Wherein the first reset message sets the lower edge of the receiving window of the second object to be equal to the lower edge of the sending window of the first object, the lower edge being used before the reset, and the second reset message. Sets the lower edge of the receive window of the first entity to be equal to the lower edge of the transmit window of the second entity, which was used before the receipt of the first reset message. Note that the parallel entity according to the present exemplary embodiment may be a receiving entity or a transmitting entity of the retransmission protocol.

Due to the reset of the first retransmission protocol by the reset message, as defined in the method, even if the first data packet and in particular the first data packet (s) comprising the reset message precedes the second data packets. In this case, the receiving entity of the first retransmission protocol will not allow any data packets sent by the transmitting entity of the first retransmission after reset. This may allow the interruption of the reset to be kept to a minimum and in particular to allow service data units of the layer that realize the first retransmission protocol to be reassembled from invalid segments contained in the second data packet received after the reset, The second data packet was sent before the reset and was starting to be discarded because of the reset.

According to another exemplary embodiment of the present invention as described in claim 10, there is provided a communication system for transmitting a first data packet and a second data packet from a transmitting station to a receiving station, wherein the first data packet is provided. Contains the first data, in particular a control command, and the second data packet comprises the second data. Further, according to one aspect of another exemplary embodiment of the invention, the first data packet and the second data packet are transmitted from the transmitting station to the receiving station in the first container and the second container, wherein the first container is at least The first container includes one first data packet, and the second container includes at least one second data packet, but does not include the first data packet. Furthermore, a first error encoding is provided in the first container and a second error encoding is provided in the second container, which is more robust than the second error encoding.

According to another exemplary embodiment of the invention, as described in claim 11, a transmitting station for transmitting a first data packet and a second data packet from a transmitting station to a receiving station is provided, whereby the first and second data are provided. Permit transmission of first and second containers containing packets, the first container including at least one first data packet, and the second container including at least one second data packet, wherein the first data pocket Is not included, and the first container is provided with stronger error encoding than the second container.

According to another exemplary embodiment of the invention, as described in claim 12, a receiving station is provided for receiving a first data packet and a second data packet from a transmitting station, where the receiving station has an error of different strength. The encoding is applied to receive different kinds of containers provided.

According to another exemplary embodiment of the invention, as described in claim 13, for data processing, for example in a communication system, for example, a first data packet and a second data from a transmitting station to a receiving station, for example. In order to perform the transmission of the packet, a software program product is provided. The software program product according to the invention is preferably mounted on the working memory of the data processor. The data processor is arranged to carry out the method of the invention, as described, for example, in claim 1. The software program product may be stored on a computer readable medium such as a CD-ROM. The computer program can also be provided on a network, such as the World Wide Web, and can be downloaded from this network to the working memory of the data processor.

As a gist of the exemplary embodiment of the present invention, it is understood that two kinds of containers are provided in which data packets are transmitted, the first kind of container being provided with stronger error encoding than the second kind of container, and for transport or system The data packet containing the control command is sent only in the first container with stronger error correction. To this end, according to an exemplary embodiment of the present invention, enhanced forward error correction (FEC) for control PDUs of the AM RLC protocol of UMTS can be provided, wherein AM data is transmitted on the H-DSCH.

These and other forms of the invention will be apparent from and elucidated with reference to the embodiments described hereinafter.

Exemplary embodiments of the present invention will be described below with reference to the following drawings.

1 illustrates an exemplary embodiment of a layer of a transmitter or receiver of a data transmission system according to the present invention.

2 is a simplified representation of a Node B, DRNC and SRNC that may be used in a data transmission system, for example UMTS, in accordance with the present invention.

3 illustrates a communication system according to an exemplary embodiment of the present invention.

4 shows a schematic representation of a method according to an exemplary embodiment of the invention.

FIG. 5 shows an exemplary embodiment for modification of RLC RESET PDU and RELC RESET ACK PDU as included in current TS 25.322, in which part of the padding field may be used in accordance with one aspect of the present invention. .

1 shows a simplified representation of the hierarchy of a transmitter or receiver in accordance with an exemplary embodiment of the present invention, as they may be applied to the exemplary embodiment of another transmission system in the present invention. According to a preferred embodiment of the present invention, a data transmission system according to an exemplary embodiment of the present invention and a transmitter and a receiver together with the 3rd Generation Partnership Project (3GPP) Technical Specification (TS), 3GPP TS 25.308 V5.4.0 (2003-03); Technical specification Group Radio Access Network; High Speed Downlink Packet Access (HSDPA); Full documentation; Third Generation Partnership Project Technical Specification Stage 2 (5th edition) and 3GPP TS 25.321 V5.5.0 (2003-069); Technical specification group radio access network; Described in the Medium Access Control (MAC) Protocol Specification (Fifth Edition), all of which are incorporated herein by reference.

According to the above technical specification, different container sizes of HS-DSCH (High Speed Downlink Shared Channel) are defined. In other words, the size of the container is indicative of the number of bits received by the physical layer from the MAC layer, which are then defined in the Technical Specification and Error Correction Encoding, including CRC addition, and the addition of parity or error protection bits. After the application of the same rate matching, it is transmitted over the air interface. If there is good channel condition on the radio channel, a relatively large container can be transmitted without error with high probability from transmitter to receiver. However, if demanding or bad channel conditions exist, a small container size should be chosen to maximize the likelihood of successful transmission.

In the RLC protocol on the RNC (Radio Network Controller), data packets, such as RLC service data units (SDUs) that have been received from an upper layer of the RLC layer, are divided into portions having a predetermined segmentation size. In general, SDUs (Service Data Units) of the considered protocol layers are defined in the literature as data units, which are considered from the next higher protocol layer. This considered protocol layer handles SDUs, which in the case of the RLC protocol means, for example, that the SDUs are divided into fragments. As a result of the processing of the protocol, the SDUs are converted into one or more PDUs (Protocol Data Units), which in the case of the RLC protocol include, for example, one fragment of each of the divided SDUs. If concatenation is possible, one or more fragments are included. These fragments are provided with an RLC header containing at least one sequence number and forming the payload or content of the RLC PDU. In general, the PDUs of the considered protocol layer are defined in data units, which the considered protocol layer carries to the next lower protocol layer. These RLC PDUs are processed at the MAC-d layer, where they can be provided with a MAC header, for example. The RLC PDUs (with or without MAC header) are then delivered to the lower protocol layer as MAC-d PDUs. For data transmission on the HS-DSCH, this lower protocol layer is the MAC-hs layer, located at Node B, as can be obtained from FIG.

As can be obtained from FIG. 1, the MAC-hs layer processes received MAC-d PDUs, each containing exactly one RLC-PDU (FIG. 1 considers the case of AM and retains for UM). Thus, they are put in MAC-hs PDUs for transmission over the HS-DSCH and then over the wireless interface. For example, the MAC-hs layer should be selected for the next MAC-hs PDU to be transmitted on the HS-DSCH over the air interface, based on the channel quality estimate, which container size, i. Can be determined. Given the RLC-PDU size (which then determines the size of each MAC-d PDU as well), the MAC-hs PDU may be configured to determine a plurality of MAC-d PDUs (and RLC-PDUs together) according to the selected size of the container. It may include.

The size of the partition is given by subtracting the bits for the header of the RLC PDU from the size of the so-called RLC PDU. The size of the MAC-d PDU may be determined from the sum of the size of the RLC PDU and the size of the MAC header. In the remaining channels, except for the HS-DSCH, the size of the MAC-d PDU is usually the same as the container size, whereas for the HS-DSCH, there is no requirement of the same size. Rather, in the case of the HS-DSCH, the size of the MAC-hs PDU corresponds to the container size, the MAC-hs PDU may be composed of several MAC-d PDUs.

The size of the container or the size of the MAC-hs PDU to be used for transmitting MAC-hs PDUs over the HS-DSCH must be adjusted according to the current channel conditions, i.e., in good channel conditions the size of the container can be large, while in bad channel conditions It should be small, which is to achieve a reliable high possibility to achieve error-free transmission of MAC-hs PDUs. For the following reasons, it is not always possible to change the size of the RLC PDU in AM or UM to account for channel conditions.

When transmitting data in the AM, where the transmission and retransmission are performed in RLC PDUs with sequence numbers ranging from 0 to 4095, the size of the RLC-PDU is determined for the sending and receiving RLC machines or RLC entities. It can only be changed or converted by reconstruction that is time consuming. This reconfiguration may take between 100 and 200 ms. When transmitting data packets in UM, no retransmission is performed, and where containers are used with sequence numbers ranging from 0 to 127, the size of the RLC PDU can be modified without such time-consuming reconfiguration. However, in UTRAN, the RLC protocol is usually located on the RNC connected to Node B via DRNC. DRNC is a drift RNC. In this case, as can be taken from FIG. 2, two interfaces must be passed, i.e., Iur located between SRNC and DRNC, and Iur located between DRNC and Node B. This can cause delays.

Furthermore, in order to transfer data from the RNC to Node B, half the round trip time is usually required. The full round trip time relates to the time from data transmission from the RNC to the UE or mobile station until the RNC receives a response. In general, the full round trip time is in the range of 100 ms (worst case). In other words, data transmission between the RNC and Node B may be required up to 50 ms. Because of this long data transmission time, the size of the RLC PDU may not change very quickly in the case of UM data transmission. A control message is then sent from the Node B to the SRNC that attempts to indicate to each RLC machine on the SRNC that, for example, twice the size of the RLC PDU may be possible and only reaches the RLC machine after 50ms later. This will also require another time interval of up to 50 ms until the RLC PDUs (packed into MAC-d PDUs) with the changed size are received at the MAC-hs layer.

However, the radio channel can change the adjustment of container size more rapidly, ie the size for the actual channel condition of the MAC-hs PDU must be achieved as soon as possible by changing the RLC PDU size for UM or AM. Otherwise, the retransmission amount on the MAC-hs stage is greatly increased if the container size is selected too large because the RLC PDU size of one or more RLC PDUs to be carried in the container was selected too large.

For the above reasons, the size of RLC PDUs in UM as well as in AM, so that a single RLC PDU or a very small number of RLC PDUs are gathered in the smallest container, so that a reliable high probability of successful transmission is estimated under very bad channel conditions. It may be advantageous to choose.

RMAC-hs PDUs are transmitted over the air interface with priority class indicators (eight different priority values), ie these indicators in turn represent channel-like bundling, whereby the eight defined channels are only in priority order. Each is different. MAC-hs on Node B defines the mapping between MAC-d flows that receive MAC-hs PDUs, and on the one hand the logical channels in the MAC-hs flow and on the other hand their priority class. By this, the scheduler can assign MAC-d PDUs of individual logical channels to a separate priority class and send them to MAC-hs PDUs of the required priority. During data transmission in the RLC AM, in addition to the RLC data PDUs, the RLC control PDUs are switched between the transmitter and the receiver by which the RLC protocol can be controlled from both the transmitter and the receiver. For example, the transmitter may initiate an RLC reset by sending an RLC RESET PDU, ie the receiver assigns configurable parameters to its initial value and cancels all remaining RLC PDUs and RLC SDUs. In this way, the same processing can be performed at the transmitter side.

The RLC protocol was developed with the assumption that the sublayer transmits PDUs to the receiving side in the sequence that was delivered on the transmitter side. RLC control PDUs are very important for the correction function of AM RLC protocol. Because of this, it is most important that RLC protocol PDUs are not lost at the air interface. Thus, the UMTS 99 version allows RLC PDUs to be transmitted on two different logical channels, whereby one logical channel is dedicated for RLC control PDUs, which has a particularly good forward error correction (FEC). It provides what is carried on the transport channel. In order to avoid changing the original sequence of transmitted RLC control PDUs and RLC data PDUs, both logical channels must have the same priority. Although they are sent from the RLC layer to the MAC layer through two different service access points, they are nevertheless inserted into the MAC layer in the same queue as defined for this priority. Assuming that the RLC layer transmits RLC data PDUs and RLC control PDUs to each MAC layer through each service access point, the RLC data PDUs and RLC control PDUs are in the actual sequence in which the PDUs were delivered from the RLC layer to the MAC layer. It can be guaranteed to appear in the queue of.

Example to illustrate a problem resulting from a change in sequence:

Difficulties can arise from changes in the sequence, e.g., the RLC RESET PDUs may precede RLC data PDUs that were previously transmitted, as described below by the HS-DSCH (High Speed Downlink Shared Channel). If so, then:

For RLC resets (among other things),

All RLC reset parameters are initialized with their configured parameters (i.e. sequence number starts again from 0, and transmit, each receiver window is set so that the lower limit is 0, i.e. the receive window is sequence number 0, 1, ...). Is configured to include configured_Rx_window_size-1), where "configured_Rx_window_size" represents the configured receive window size, and the transmit window is sequence number 0, 1, .., VT ( WS) -1, where VT (WS) stores the currently configured transmission window size as a transmission window state variable.

All RLC PDUs in the AM RLC machine (and then in the received AM RLC machine) are deleted;

All remaining RLC SDUs transmit before the reset is cleared at the transmitter and receiver side.

These steps will be triggered if the RLC machine receives a RESET PDU. This step will also be triggered when the machine receives a RESET ACK PDU in response to a RESET PDU at the RLC machine initiating the reset. This initiating RLC machine does not send any more RLC PDUs after sending a RESET PDU.

One reason for the initiation of the RLC reset is that the maximum number of transmission repetitions for the RLC PDU has been reached. It is not important whether the RLC reset is initiated on the SRNC or the UE by the RLC machine, since both the released RLC machine and its peer entity must perform the above steps.

After successful completion of the RLC reset process, in this example embodiment where the UMTS system is considered, the transmitting and receiving RLC machines receive their data via the HS-DSCH and delete the stored RLC PDUs from the time before the RLC reset. In most cases, some of these RLC PDUs that have already been transmitted but no acknowledgment have been received are typically assigned RLC control PDUs (RESET PDU and RESET ACK PDU) such that a RESET PDU or a RESET ACK PDU outpaces the stored data PDUs. When transmitted over other fast priority logical channels as RLC data PDUs, they are still stored in the Node-B's MAC-hs layer, as long as they cannot yet be transmitted correctly to the MAC-hs layer without error. However, after the RLC reset, the RLC PDUs still stored in the MAC-hs no longer have any value for data transmission because the receiver no longer expects them. RLC PDUs are defined herein as "orphan RLC PDUs." After an RLC reset, "Discarded RLC PDUs" are typically sent on the HS-DSCH. If their sequence numbers are outside the receive window initialized by a reset, they will be rejected by the receiving RLC machine according to the prescribed error handling. On the other hand, if they are within the receive window, the receiving RLC machine will mistakenly accept them as valid RLC PDUs. However, since they are discarded RLC PDUs, they were never sent at the transmitting RLC machine after reset. However, after the RLC reset, the transmitting RLC machine on the SRNC will send the real RLC PDUs under the same sequence number, which has since reached the receiver side after the discarded RLC PDUs. Thus the true RLC PDUs are interpreted by the receiver side as replicas and therefore will be rejected. Among the remaining sequence numbers of the receive window, the receiver side receives the real RLC PDUs in turn. However, recombination for the RLC PDUs of the SDU segment received in the RLC PDUs now fails because the discarded RLC PDUs do not contain valid SDU segments. In many cases the result is the loss of some RLC SDUs, which have been sent after an RLC reset by substantially exceeding those RLC SDUs already lost via the RLC reset. The number of these RLC SDUs that are additionally lost after an RLC reset is size dependent on the size of the receive window, because at the risk that any of the discarded RLC PDUs on the one hand will have a sequence number in the receive window initialized after reset. Because you decide about. On the other hand, the size of the transmission window (of the transmitting RLC machine on the SRNC) determines the number of discarded RLC PDUs possible, and the receive and transmit windows of the same size are usually selected.

In addition, after reception of discarded RLC PDUs with sequence numbers in the receive window that were initiated with a reset, the status report acknowledges the correct reception of discarded RLC PDUs, while the sender identifies the true RLC PDU with the sequence number of this discarded RLC PDU. The status report, which has not been sent yet, ie, indicates a faultless reception of the RLC PDU that the sender has not yet sent. In accordance with the prescribed error handling, in some cases this causes additional reset processing initiated by the sender according to the criteria of the faulty sequence number, as described in section 10.1 of TS 25.322, to carry AM RLC PDUs. Causing additional interrupts to the data transfer for the logical channel.

STATUS PDUs containing MRW SUFI (super field) may not cause similar problems if they can outperform conventional RLC data PDUs.

STATUS PDUs containing MRW SUFI may be used in conjunction with "SDU discard with explicit signal" processing. This process is used at the AM to discard RLC SUDs on the sender (in other words the sender of the AM RLC protocol) and to send discard information to a peer on the receiver (in other words the receiver of the AM RLC protocol). In accordance with the above processing, the sender discards the RLC SUD, which failed to transmit successfully for a time interval or for multiple transmissions, and sends a Move Receiving Window (MRW) SUFI to the receiver. Depending on the received MRW SUFI (which contains only the fragments of the discarded SDU, it contains the sequence number of the RLC PDUs to be discarded at the receiving end), the receiver discards the AMD PDUs carrying the SDU and receives a receive window. Update the lower edge of the receive window so that the sequence number of the RLC PDUs containing fragments of the discarded SDU are no longer present in the receive window.

If a STATUS PDU containing MRW SUFI transmitted in downlink precedes RLC data PDUs transmitted before this STATUS PDU, then it is retained for the overtaken RLC data PDUs: some of these will be discarded by SDU discard processing. Same as the RLC PDUs, or none of them is the same. The same PDUs will be discarded when they are received after the SDU discard process ends, because the process will confirm that if these RLC PDUs are received after the end of the SDU discard process, the sequence number of these RLC PDUs is outside the receive window. to be.

Therefore, it is sufficient to handle only the case where the RLC reset PDU or the RLC reset ACK PDU exceeds the RLC data PDUs.

Special features of the HS-DSCH:

Since there is exactly one HS-DSCH transport channel, both logical channels can only operate on the same HS-DSCH, i.e. with respect to FEC, the RLC control PDUs and RLC data PDUs are then processed identically, i.e. FEC It is impossible to be certain that RLC control PDUs are sent with better FEC than RLC data PDUs.

According to an exemplary embodiment of the present invention, RLC control PDUs are sent with RLC data PDUs in a MAC-hs PDU, the error protection of which is better than the error protection of MAC-hs PDUs exclusively including RLC data PDUs. Do. This improved error protection reduces the number of RLC PDUs included in the MAC-hs PDU, while keeping the total number of bits in the MAC-hs PDU constant after channel coding and rate matching, ie the same number of physical layer bits It can be achieved by transmitting over the air interface at a TTI of 2ms.

MAC-hs PDUs may always consist of RLC PDUs in such a way that there is no change in sequence, in successive RLC PDUs transmitted entirely in all MAC-hs PDUs. However, RLC data PDUs can be lost thereby, because in some cases they can no longer be transmitted because of undesirable channel conditions.

The scheduler of Node-B's MAC-hs may read the first bit of one RLC PDU of all received RLC PDUs to determine if it is an RLC control PDU or an RLC data PDU.

Alternatively, the RLC control PDUs can be sent on different logical channels in the RLC data PDU, so whether the frame protocol for data transmission between the RNC and Node B includes an RLC control PDU or an RLC data PDU from each logical channel. And determine whether the received RLC PDUs are RLC control PDUs and RLC control PDUs in a way that Node B can immediately recognize, without analyzing the first bit of the RLC PDU.

According to another exemplary embodiment of the present invention, the entity of MAC-hs on Node B forming MAC-hs PDUs (eg, schedulers) is at least a subset of RLC control PDUs, such as RESET PDUs, RESET ACK PDUs. STATUS PDUs that include,, and MRW SUFI (super field) are sent in MAC-hs PDUs with better FEC. This is advantageous because these control PDUs are typically rarely transmitted. In contrast, STATUS PDUs, including, for example, status reports, are transmitted more often, and limiting their transmission to smaller MAC-hs PDUs with very strong FEC is not a possibility of downlink transmission over HS-DSCH. May reduce throughput.

Yes:

Indeed, the method for enhanced FEC for RLC control PDUs may be applied as follows: RLC data PDUs and RLC control PDUs for an RLC machine on an SRNC that delivers data to the mobile station via HS-DSCH. To this end, two logical channels are configured, whereby the first channel is intended independently for the transport of RLC control PDUs, and both logical channels have the same MAC logical priority (MLP). In the MAC-d layer, RLC data PDUs and RLC control PDUs are thus inserted into MAC-d PDUs with different MAC headers. As a result of the same MAC priority, these RLC PDUs gather in the same queue in the MAC-d layer, and then via a frame protocol between the S-RNC and Node B in the same sequence as the sequence that was in the queue of the MAC-d layer, It is carried to the MAC-hs layer on B, where it is stored in a different queue until transmission on the HS-DSCH without changing the sequence. When packing MAC-hs PDUs temporarily stored in the queue with MAC-d PDUs, the scheduler in the MAC-hs layer is responsible for, for each of these MAC-d PDUs, that they are in the RLC machine in question. It is analyzed whether it belongs to the first logical channel related to the transport of the RLC control PDUs. In order to achieve a particularly robust modulation and coding scheme (MCS) with particularly good FEC, the scheduler has a fixed number of coded codes that are ultimately transmitted over the air interface for MAC-hs PDUs after channel coding and rate matching. In the case of bits, since the number of parity bits per user bit (user bits are bits of the first or second data packet) and hence the FEC increases with decreasing number of user bits, it is associated with the same MAC-hs priority class. Allow certain MAC-d PDUs to be inserted into individual MAC-hs PDUs without changing the MAC-d PDU sequence, and MAC-d PDUs containing RLC control PDUs are MAC-d together with a small number of other MAC-d PDUs. Only share with hs PDUs (or even transmitted alone in MAC-hs PDUs).

If there are very many RLC control PDUs to be transmitted in the flow of the first class (for example, control PDUs for every tenth RLC PDU, not every hundredth), this means "MAC-d PDUs (this is therefore RLC). Due to the constraint that the sequence of the control and RLC data PDUs) must remain unchanged, only a small number of RLC data PDUs per MAC-hs PDU are transmitted, thus having a significantly improved FEC, here however the "HS -A reduction in downlink throughput on the DSCH can be expected. "However, in general, the number of RLC control PDUs is very small (eg 1 for the RLC PDUs of the RLC machine to be transmitted). % Only, the flow rate is not greatly reduced by this method.

On the other hand, if only main RLC control PDUs (e.g., RLC reset PDU, RLC reset ACK PDU, RLC STATUS PDU with MRW SUFI or MRW_ACK SUFI) are sent over this first logical channel, the packets If the scheduler contains MAC-hd PDUs with more robust FEC, while the remaining RLC control PDUs and RLC data PDUs are carried on the second logical channel, this restriction on the downlink transmission can be avoided. Important RLC control PDUs are transmitted very rarely, so the constraint rule for combining data units carried over the first logical channel only in powerful FEC and small size MAC-hs PDUs does not significantly reduce the throughput. .

A second possibility to cause the entity to be sent to the same MAC-hs PDU (eg, scheduler) for selection of the MAC-d PDU is to determine if the MAC-d PDU contains an RLC Control PDU or an RLC Data PDU. To analyze the first bit for every single RLC PDU (included in the MAC-d PDU in the queue of MAC-hs). The first bit of the RLC PDU indicates whether the RLC PDU includes an RLC Control PDU or an RLC Data PDU. Of course, this entity (e.g. scheduler) can determine whether the MAC-d layer's MAC header has been provided for the MAC-d PDU containing the RLC PDU in question, ie whether MAC multiplexing has been applied for this logical channel. Knowing that it is only possible to determine without error the first bit of the RLC PDU. MAC multiplexing here means that several logical channels are multiplexed on the same MAC-d flow. In this case, the MAC-d layer attaches the MAC header to the RLC PDU received by the RLC layer to form a MAC-d PDU. The MAC header consists of 4 bits. The MAC header may be omitted if exactly one logical channel is mapped on the MAC-d flow. In this second case example, in order to correctly identify the first bit of the RLC PDU, this entity (e.g., the scheduler) thus carries exactly one logical channel or how many logical channels the MAC-d flow carries. You must know In the second case, there is always a MAC header so that the scheduler must evaluate the fifth bit of the MAC-d PDU to determine if the MAC-d PDU contains an RLC data PDU or an RLC control PDU.

In the special case where the MAC-d flow carries exactly one logical channel, the MAC header may be missing, where the first bit of the MAC-d PDU is whether the MAC-d PDU contains an RLC data PDU or an RLC control PDU. It can indicate whether or not The less preferred configuration in this case may still include a MAC header, so that the scheduler may then set the fifth bit of the MAC-d PDU to determine whether the MAC-d PDU contains an RLC data PDU or an RLC control PDU. Since it must be evaluated, the scheduler must know that.

In addition, the entity for selecting a MAC-d PDU to be transmitted in the same MAC-hs PDU must know which logical channel carries UM RLC PDUs and which logical channel carries AM RLC PDUs. This can be achieved, for example, by providing a list of all logical channels carrying UM RLC PDUs to the entity. The same can be achieved by providing a list of all logical channels carrying AM RLC PDUs, such that only configurable transmission on the HS-DSCH for logical channels carrying AM RLC PDUs or UM RLC PDUs Because. Moreover, in order to distinguish between the important RLC control PDUs and the less important RLC control PDUs, this entity (e.g. scheduler) is assigned to the important RLC control PDUs (e.g. RLC RESET PDU, RLC RESET ACK PDU, MRW). STATUS PDU containing SUFI, and STATUS PDU containing MRW_ACK SUFI) which bits of the "PDU Type" field (3 bits after the first bit, which determines whether the RLC PDU is an RLC Control PDU) in the RLC Control PDU It can be seen that a combination needs to know if it identifies these important RLC control PDUs. For example, TS 25.322 specifies the following match.

The mapping does not yet allow to identify whether the STATUS PDU contains RMW SUFI or MRW SUFI_ACK. This information can be retrieved by further analyzing the structure of the STATUS PDU, which is described in TS 25.322. One alternative may be to use two five reserved bit combinations to indicate that a STATUS PDU is included, including the MRW SUFI or RMW SUFI_ACK field.

The information may be made possible to determine which MAC-d PDUs to send in the MAC-hs PDU on Node B for the entity as follows.

When setting up an AM logical channel, the data will be delivered over the HS-DSCH, and the SRNC informs the DRNC via RNSAP-processing of one or more information, which then goes to Node B by NBAP processing. Proceed. The most suitable RNSAP procedure and NBAP procedure are called with the same name and next. In other words,

-Radio link setup procedure (the corresponding message sent from SRNC to DRNC or DRNC to Node B is called "RADIO LINK SETUP").

Synchronous radio link reconfiguration preparation procedure (the corresponding message sent from SRNC to DRNC for NRSAP and from DRNC to Node B for NBAP is called "Radio Link Reconfiguration Ready").

 RNSAP (Radio Network System Application Part) includes 3GPP TS 25.423 V5.3.0 (2002-09), third generation partnership project; Technical specification group radio access network; UTRAN Iur interface RNSAP signaling (5th edition).

NBAP (Node B Application Part) includes 3GPP TS 25.433 V5.2.0 (2002-09), third generation partnership project; Technical specification group radio access network; UTRAN Iub interface NBAP signaling (5th edition). The overall UTRAN structure is 3GPP TS 25.401 V6.1.0 (2003-06), third generation partnership project; Technical specification group radio access network; UTRAN Full description (6th edition). These specifications are incorporated herein by reference.

3 illustrates a communication system according to an exemplary embodiment of the present invention. The communication system includes a transmitting station 30 having a network unit, a receiving station 31, and arithmetic means 34. The computing means 34 is used to execute a software program product for transmitting data packets from the transmitting station 30 to the receiving station 41. Transmission of the data packet from the transmitting station 30 to the receiving station 31 may be performed via the wireless communication link 32. The receiving station 31 may also be provided with computing means. The transmission system shown in FIG. 3 is applied to perform enhanced FEC according to an exemplary embodiment of the present invention.

4 schematically illustrates a method according to an exemplary embodiment of the invention. As described in detail with reference to FIGS. 1 and 2, the MAC-d layer 29 includes MAC-d PDUs including first data packet or RLC control PDUs 21, 22, and 27, and a second. MAC-D PDUs containing a data packet or RLC data PDUs 23, 24, 25, 26, 28, wherein the RLC control PDUs and RLC data PDUs are the same RLC entity in the layer above the MAC-d layer. Was sent by In the processing step, MAC-d PDUs containing RLC PDUs 21, 22, 23, 24, 25, 26, 27, 28 are delivered to MAC-hs layer 12, which layer 12 is a MAC. -d form MAC-hs PDUs (1, 2, 3, 4, 5, 6, 7, 8) from the PDUs.

The first container 9, 11 includes MAC-d PDUs 1, 2, 7 containing control information (RLC control PDUs), and the first container 11 also contains data (RLC data PDU). It includes a MAC-d PDU (8). On the other hand, the second container 10 includes only the MAC-d PDUs (3, 4, 5, 6) containing only data, not PDUs containing control information.

It should be noted that MAC-hs PDUs are always MAC-d PDUs (always exactly one RLC PDU in such a way that there is no change in sequence in the progress of RLC PDUs transmitted in all MAC-hs PDUs actually transmitted. It may comprise). However, in actual transmitted MAC-hs PDUs, RLC data PDUs may be missing, due to bad channel conditions, for the MAC-hs PDU to which the RLC data PDUs (included in MAC-d PDUs) were carried. This is because the error protection may not have been stronger than the error protection of the MAC-hs PDU to which the RLC control PDUs (contained in MAC-d PDUs) were carried.

In order to provide the correct sequence order for the first and second data packets, at least the second data packets may be provided with a sequence number of the corresponding data packet, in accordance with an exemplary embodiment of the present invention. Furthermore, in order to provide the correct sequence order of the first and second containers, the corresponding second container sequence number may be provided.

In another exemplary embodiment of the invention, which may be implemented in combination with the exemplary embodiment in claim 1, i.e. in combination with containers having different error encodings, but which may also be implemented separately from the solution of claim 1. According to the above-described problem, the RLC protocol is not initialized after the RLC reset processing procedure is completed, so that the lower edges of the windows are the same as sequence number 0, but the lower edges of these windows are not started. This can be solved by modifying it in such a way that it is set equal to the lower edge of the previous transmission window. By this, it can be achieved that the " Discarded RLC PDUs " are always outside the receiving RLC window after the reset process, and thus discarded in accordance with the error handling of the RLC protocol. In other words, RLC data PDUs whose sequence number is outside the receive window are discarded.

This modification of the RLC protocol includes the value of the lower edge of the transmit window immediately before the RLC reset PDU is sent and thus an additional 12 bits to trigger the RLC reset process (ie, without initializing the lower edge of the transmit window to zero). This may be accomplished by combining the fields in the RLC Reset PDU. When the receiving RLC entity receives this RLC reset PDU, it also reads this field and updates its receiving window so that the bottom edge of the window is equal to the value contained in the field. Similarly, the RLC entity receiving the RLC Reset PDU contains an additional 12 bit field in the RLC RESET ACK PDU to be sent in response to the RLC Reset PDU, which is immediately below the send window of the RLC RESET ACK PDU. Contains the value of the edge and maintains the transmission window, i.e. does not initialize the lower edge of the transmission window to zero. When an RLC RESET ACK PDU is received by an RLC entity that triggers an RLC reset process by sending an RLC Reset PDU, the entity reads a 12-bit field containing the lower edge of the transmission window of the RLC object that sent the RLC RESET ACK PDU. It updates its receive window so that the window lower edge is equal to the value contained in the field. Thus, in the Reset PDU and Reset ACK PDU as described in TS 25.322, for example, an additional 12-bit field can be added after the Hyper Frame Number Indicator (HFNI) field, which is As shown in FIG. 5, a padding field of 12 bits is taken. LEWI ("Lower Edge of the Window" -indicator) indicates a new field, while the rest are those described in TS 25.322.

According to an exemplary embodiment, the RLC control PDUs preceding the RLC data PDUs may no longer cause problems, so the possibility of sending RLC control PDUs on a logical channel with a higher priority than the logical channel used for the RLC data PDUs This can be. The FEC of RLC control PDUs better than RLC data PDUs can be obtained by the following fact: RLC control PDUs are collected in MAC-hs on Node B in a queue different from the queue of RLC data PDUs, the queue being higher Provided by a prioritized scheduler, where the scheduler is sufficiently reduced to achieve a robust FEC, i.e., a MAC-hs PDU used to transport the RLC control PDUs stored in the container or queue. It can be seen that it contains a specified number of RLC control PDUs.

It should be noted that despite the fact that the present invention has been consulted with reference to an exemplary embodiment of a UMTS system, the present invention can be applied to other systems with similar problems and similar configurations.

Claims (13)

A method for transmitting first data packets and second data packets from a transmitting station to a receiving station, the method comprising: Said first data packets comprise first data, in particular control commands, The second data packets include second data, The first data packets and the second data packets are sent from the transmitting station to the receiving station in containers; The first container includes at least one first data packet, The first container is provided with a first error encoding, The second container includes at least one second data packet, but does not include the first data packet, The second container is provided with a second error encoding, The first error encoding is stronger than the second error encoding Transmission method. The method of claim 1, The number of first and second data packets in the first container is smaller than the number of second data packets in the second container so that the first data payload sent in the first container is the second data sent in the second container. Lower than payload Transmission method. The method of claim 1, A first retransmission protocol controls the transmission or retransmission of the first and second data packets for a third data packet, A second retransmission protocol controls the transmission or retransmission of the first and second containers, The first container and the second container are provided with corresponding container sequence numbers, Each data packet of the second data packets is provided with a corresponding data packet sequence number, The first order of the first and second data packets that occurs when the first and second data packets are transmitted in the first and second containers is such that the first and second data packets are received by the second retransmission protocol. Remain unchanged when compared to the second order of the first and second data packets Transmission method. The method of claim 1, The second retransmission protocol is configured to determine whether the second retransmission protocol is a first data packet or a second data packet received from a first retransmission protocol located above the second retransmission protocol. Transmission method. The method of claim 4, wherein The second retransmission protocol performs an operation of determining whether the fourth data packet is a first data packet or a second data packet by analyzing header information associated with a fourth data packet by the first retransmission protocol. Transmission method. The method of claim 4, wherein If the fourth data packet is a first data packet, the fourth data packet is classified when carried from the first transport protocol to the second transport protocol, and the first transport protocol is located above the second transport protocol. doing Transmission method. The method of claim 1, The method is applied to transmit data through a high speed downlink shared channel of UMTS Transmission method. The method of claim 7, wherein The first data packets are RLC control PDUs, where the second data packets are RLC data PDUs Transmission method. The method of claim 1, The first retransmission protocol controls transmission or retransmission of a third data packet of the first and second data packets, The second retransmission protocol controls transmission or retransmission of the first and second containers, Corresponding container sequence numbers are provided to the first container and the second container; Each data packet of the second data packets is provided with a corresponding data packet sequence number, The receiving entity of the first retransmission protocol discards the second data packet whose sequence number is outside the receiving window; The first peer of the second peer entity of the first retransmission protocol is adapted to initiate a reset of both peer entities, the reset being in response to the first and second reset messages included in the first data packets. Finished by The reset causes the first entity to send the first reset message to the second entity and the second entity sends the second reset message to the first entity in response to the first reset message, The first reset message sets the lower edge of the receive window of the second entity equal to the lower edge of the transmit window of the first entity, wherein the lower edge is used prior to the reset, The second reset message sets the lower edge of the receive window of the first entity to be equal to the lower edge of the transmit window of the second entity, wherein the lower edge is used prior to receipt of the first reset message. Transmission method. A communication system for transmitting first data packets and second data packets from a transmitting station to a receiving station, the communication system comprising: Said first data packets comprise first data, in particular control commands, The second data packets include second data, The first data packets and the second data packets are sent from the transmitting station to the receiving station in containers; The first container includes at least one first data packet, The first container is provided with a first error encoding, The second container includes at least one second data packet, but does not include the first data packet, The second container is provided with a second error encoding, The first error encoding is stronger than the second error encoding Communication system. A transmitting station for transmitting first data packets and second data packets from a transmitting station to a receiving station, comprising: Said first data packets comprise first data, in particular control commands, The second data packets include second data, The first data packets and the second data packets are sent from the transmitting station to the receiving station in containers; The first container includes at least one first data packet, The first container is provided with a first error encoding, The second container includes at least one second data packet, but does not include the first data packet, The second container is provided with a second error encoding, The first error encoding is stronger than the second error encoding Sending station. A receiving station for receiving first data packets and second data packets from a transmitting station, Said first data packets comprise first data, in particular control commands, The second data packets include second data, The first data packets and the second data packets are sent from the transmitting station to the receiving station in containers; The first container includes at least one first data packet, The first container is provided with a first error encoding, The second container includes at least one second data packet, but does not include the first data packet, The second container is provided with a second error encoding, The first error encoding is stronger than the second error encoding Recipient.  A software program product for performing transmission of first data packets and second data packets from a transmitting station to a receiving station, the method comprising: Said first data packets comprise first data, in particular control commands, The second data packets include second data, The first data packets and the second data packets are sent from the transmitting station to the receiving station in containers; The first container includes at least one first data packet, The first container is provided with a first error encoding, The second container includes at least one second data packet, but does not include the first data packet, The second container is provided with a second error encoding, The first error encoding is stronger than the second error encoding Software Program Product.

Images