KR101124762B1 - Method and apparatus for configuring enhanced transport format in communication system - Google Patents

Abstract

The present invention relates to a mobile communication system for transmitting packet data through an uplink, and provides a method for more effectively setting a transmission format corresponding to a plurality of packet data. That is, the present invention provides a method for the base station to recognize the size of a packet transmitted by the user terminal.

According to the present invention, a wireless network controller transmits parameters indicating a relationship between a plurality of packet data and a transmission format indicating the size of each packet data to a mobile terminal, and the mobile terminal is assigned to a first section of the parameters. Recognize the size of the packet data allocated to the first section by using the information indicating the size of the packet data to be allocated, and allocate the information to the second section by using the information indicating the size of the most frequently used upper layer packet data as the step size. The size of the packet data allocated to the third section is recognized by using the step size so that the information indicating the size of the most frequently used upper layer packet data is multipled.

MAC-e Medium Access Control-enhanced PROTocol Data Unit (PDU), Enhanced Transport Format (ETF),

Description

METHOD AND APPARATUS FOR CONFIGURING ENHANCED TRANSPORT FORMAT IN COMMUNICATION SYSTEM}

1A illustrates a change in a received signal of a base station when base station control scheduling is not used.

1B is a diagram illustrating a change in a received signal of a base station when base station control scheduling is used.

2 shows a user terminal and a base station performing uplink packet transmission.

3 is a diagram illustrating information transmitted and received between a user terminal and a base station to perform uplink packet transmission.

4 is a view schematically showing the structure of a user terminal according to the present invention;

5 schematically illustrates the structure of a MAC-e PDU used in an EDCH in accordance with the present invention.

6 is a diagram illustrating a relationship between the size of an interval MAC-e PDU and an E-TF according to an embodiment of the present invention.

7 illustrates control signal exchange between an RNC, a Node B, and a terminal according to an embodiment of the present invention;

8 is a diagram illustrating a control signal exchange between an RNC, a Node B, and a terminal according to another embodiment of the present invention;

The present invention relates to a mobile communication system for transmitting packet data through an uplink. In particular, the present invention provides a method for minimizing padding by defining information representing a size of packet data and a size of packet data.

The present invention assumes a situation in which an Enhanced Uplink Dedicated CHannel (hereinafter referred to as "EUDCH") is used in a wideband code division multiple access (WCDMA) communication system. The EUDCH is a channel proposed to improve the performance of packet transmission in reverse communication in an asynchronous code division multiple access communication system.

The mobile communication system supporting the EUDCH maximizes the efficiency of uplink transmission by using a fast scheduling technique and a hybrid automatic retransmission request (HARQ) technique. In this fast scheduling scheme, a base station (hereinafter referred to as 'Node B') receives a channel state and a buffer state of a user terminal (hereinafter referred to as 'UE'), and performs backward transmission of UEs based on the received information. To control. That is, a large amount of data transmission is allowed to UEs in good channel conditions, and data transmission for UEs in poor channel conditions is minimized, thereby enabling efficient use of limited uplink transmission resources.

In addition, the HARQ scheme is to increase the transmission success rate compared to the transmission output by executing HARQ between the UE and the Node B. That is, the HARQ technique does not discard the data block in which an error occurs, and soft-combines the retransmitted data block ( By performing soft combining, the probability of successful data block reception is increased.

In the uplink, orthogonality is not maintained between signals transmitted by a plurality of UEs, thus acting as interference signals. As a result, as the uplink signal received by the Node B increases, the amount of interference signal for the uplink signal transmitted by a specific UE also increases. Therefore, as the amount of the interference signal for the uplink signal transmitted by a specific UE increases, the reception performance of the Node B decreases. For this reason, the Node B proposes a method of limiting the amount of uplink signals that can be received while guaranteeing the reception performance, which is represented by Equation 1 below.

ROT = Io / No

Here, the ROT represents a radio resource that the Node B can allocate for the EUDCH packet data service on the uplink. Further, Io is the total received broadband power spectral density of the Node B, and No represents the thermal noise power spectral density of the Node B.                         

1A and 1B show an amount of uplink radio resources that can be allocated by a Node B. FIG.

As shown in FIGS. 1A and 1B, uplink radio resources allocated by the Node B may be represented as a sum of inter-cell interference (ICI), voice traffic, and EUDCH packet traffic. Can be. FIG. 1A illustrates a change in the total ROT when the Node B scheduling is not used. Since the scheduling is not performed on the EUDCH packet traffic, when a plurality of UEs simultaneously transmit the packet data using a high data rate, the UEDCH can transmit a higher ROT than a target ROT. In this case, the reception performance of the uplink signal is degraded.

Figure 1b shows the change in the total ROT when using the Node B scheduling. When using the Node B scheduling, it is possible to prevent the plurality of UEs from simultaneously transmitting the packet data using a high data rate. That is, the Node B scheduling may prevent the total ROT from increasing above the target ROT by allowing a low data rate to other UEs when allowing a high data rate to a specific UE.

Therefore, the Node B scheduling can always be guaranteed a constant reception performance. In this case, the Node B notifies whether EUDCH data transmission is possible for each UE by using request data rate or channel state information of UEs using the EUDCH or performs Node B scheduling to adjust the EUDCH data rate. do. The Node B scheduling may be regarded as an operation in which the Node B distributes the ROT to each UE based on channel conditions and buffer conditions of UEs performing EUDCH communication.

2 illustrates a basic concept of Node B scheduling.

Referring to FIG. 2, 200 in FIG. 2 represents a Node B supporting EUDCH, and UEs illustrated as 210 to 216 are UEs transmitting EUDCH. When the data rate of the UE increases, the reception power received by the Node B from the UE increases. Therefore, the ROT of the UE occupies a large part of the total ROT.

On the other hand, when the data rate of the UE decreases, the reception power received by the Node B from the UE decreases. Therefore, the ROT of the UE occupies a small part of the total ROT. The Node B performs Node B scheduling for the EUDCH packet data in consideration of the relationship between the data rate and radio resources and the data rate requested by the UE.

As illustrated in FIG. 2, the UEs transmit the packet data at transmit powers of different reverse channels according to a distance from the Node B. The UE 210 farthest from the Node B 200 transmits packet data at the transmit power 220 of the highest reverse channel, and the UE 214 nearest to the Node B 200 is the most. The packet data is transmitted at a transmit power 224 of a low reverse channel. At this time, the Node B can be scheduled in inverse proportion to the strength of the transmit power of the reverse channel and the data rate in order to improve the performance of the mobile communication system while reducing the ICI for other cells while maintaining the total ROT.

In other words, a small transmission resource is allocated to a UE having the highest transmission power of the reverse channel, and a large transmission resource is allocated to the UE having the lowest transmission power of the reverse channel to efficiently maintain the total ROT.

3 illustrates a process in which a UE is allocated a transmission resource for EUDCH packet data transmission from a Node B and transmits the packet data using the allocated transmission resource.

Referring to FIG. 3, in step 310, EUDCH is configured between the Node B 300 and the UE 302. Step 310 includes a process of transmitting and receiving messages through a dedicated transport channel. In step 312, the UE 302 transmits information about a required transmission resource and information for identifying an uplink channel condition to the Node B 300 in step 312. Information indicating the uplink channel status includes an uplink transmission power transmitted by the UE 302 and a transmission power margin of the UE 303.

The Node B 300 receiving the uplink transmission power may estimate a forward channel situation by comparing the uplink transmission power and the reception power. That is, if the difference between the uplink transmit power and the uplink receive power is small, the reverse channel situation is good. If the difference between the transmit power and the receive power is large, the reverse channel situation is poor. When the UE transmits a transmission power margin to estimate an uplink channel situation, the Node B 300 estimates the uplink transmission power by subtracting the transmission power margin from the maximum possible transmission power of a known UE. can do.

The Node B 300 determines possible transmission resources for the uplink packet channel of the UE by using the estimated channel status of the UE and information on the transmission resources required by the UE 302. The determined transmission resource is notified to the UE 302 in step 314. In this case, the transmission resource may be the size of data that can be transmitted or may be a transmission output that can be used. The UE 302 determines the size of packet data to be transmitted to the notified transmission resource, and transmits the data of the determined size to the Node B 300 in step 316.

At this time, the packet data transmitted through the EUDCH is called a MAC-e PDU (Medium Access Control-enhanced PROTocol Data Unit), and while the UE transmits the MAC-e PDU, information indicating the size of the MAC-e PDU is provided. Send together. The information indicating the size is called an enhanced transport format (ETF) and is expected to be a physical channel signal of about 5 to 6 bits. At this time, the number of information that can be represented by the 5-bit ETF is 32, and the number of information that can be represented by the 6-bit ETF is only 64. On the other hand, the maximum size of the MAC-e PDU is expected to reach 8600 bits in a 2 msec transmission period and 20000 bits in a 10 msec transmission period.

In other words, using the 5-bit or 6-bit ETF to represent a maximum of 20000 bits of MAC-e PDU size is a significant burden. For example, to represent 20000 bits with a 6-bit ETF, a step size of 312 bits is required. This means that the padding size can reach up to 311 bits. This is especially the case where the MAC-e PDU size is small, waste of the padding can lead to a serious degradation in transmission efficiency.

For example, when any E-TF x means 312 bits, and any E-TF y means 624 bits, if the size of the MAC-e PDU to be actually transmitted is 313 bits, the UE may send the E-TF y. Select and add 311 bits of padding to the MAC-e PDU to transmit 624 bits. In other words, 624 bits of transmission resources are used to transmit the 313 bits of user data (MAC-e PDU), and the remaining 311 bits are filled with padding which is meaningless data.

Therefore, when setting the E-TF and MAC-e PDU according to the prior art. Transmission efficiency is only 50% and has a problem of wasting limited radio resources.

Accordingly, an object of the present invention for solving the above-mentioned problems of the prior art is to provide a method for efficiently configuring a transmission format in a mobile communication system supporting uplink.

Another object of the present invention is to provide a method for setting an improved transmission format which minimizes the occurrence of padding in a mobile communication system supporting uplink.

In accordance with another aspect of the present invention, there is provided a method for setting a transmission format of packet data in a mobile communication system supporting uplink, wherein the wireless network controller transmits information indicating the size of a plurality of packet data. Dividing formats into a plurality of sections, and transmitting transmission format information indicating a relationship between the sizes of the plurality of packet data and the transmission formats to the mobile terminal for each of the divided sections, and wherein the mobile terminal transmits the transmission format. Among the pieces of information, the transmission formats included in the first section of the plurality of sections and the size of packet data corresponding to the transmission formats included in the first section are recognized and most frequently among the transmission format informations. The plurality of sections using the information indicating the size of the packet data to be used as the step size The size of the packet data corresponding to the transmission formats included in the second interval and the transmission formats included in the second interval are recognized, and a multiple of the size of the most frequently used packet data is used as the step size. Recognizing a size of packet data corresponding to transmission formats included in a third section and the transmission formats included in the third section among the plurality of sections, and when packet data to be transmitted in the uplink occurs, And checking, by the mobile terminal, the size of the generated packet data, and setting a transmission format corresponding to the size of the checked packet data as the transmission format of the generated packet data.

Another embodiment of the present invention for achieving the object of the present invention is a method for setting the transmission format of packet data in a mobile communication system supporting uplink, the wireless network controller of the packet data used in each logical channel Determines the number of packet data that can be transmitted in one transmission interval for each size, sets the combination of the determined number of packet data, and maps the combination of the number of packet data and the transmission format representing the size of a specific packet data. Transmitting the information to the mobile terminal, identifying a combination of the number of packet data that the mobile terminal can transmit in the one transmission interval, and using the mapping information, a transmission format corresponding to the combination of the number of specific packet data Packet data corresponding to the recognized transmission format The size of the packet data to be transmitted by checking the payload size and the header size of the packet data to be transmitted, and when the packet data to be transmitted is generated in the uplink, the mobile terminal according to the size of the packet data And a process of constructing packet data.
Another embodiment of the present invention for achieving the object of the present invention is an apparatus for setting the transmission format of the packet data in a mobile communication system supporting uplink, the transmission format that is information indicating the size of a plurality of packet data A wireless network controller for dividing a plurality of sections and transmitting transmission format information indicating a relationship between sizes of the plurality of packet data and the transmission formats for each of the divided sections, and transmitting the transmission format information from the wireless network controller. Receives and recognizes the size of the packet data corresponding to the transmission formats included in the first section of the plurality of sections and the transmission formats included in the first section of the received transmission format information, the transmission Among the format information, information indicating the size of packet data that is most frequently used is selected. The size of the packet data corresponding to the transmission formats included in the second section of the plurality of sections and the transmission formats included in the second section of the plurality of sections is used, and the most frequently used upper layer packet is used. Recognizing the size of the packet data corresponding to the transmission formats included in the third section and the transmission formats included in the third section of the plurality of sections using the step size as a multiple of the size of the data, the uplink When the packet data to be transmitted to the mobile station occurs, the mobile station checks the size of the generated packet data, and includes a mobile terminal for setting the transmission format corresponding to the size of the checked packet data as the transmission format of the generated packet data. It features.
Another embodiment of the present invention for achieving the object of the present invention is an apparatus for setting the transmission format of packet data in a mobile communication system supporting uplink, one transmission for each size of packet data used in a logical channel A radio for determining the number of packet data that can be transmitted in an interval, setting a combination of the determined number of packet data, and transmitting mapping information mapping a combination of the number of packet data and a transmission format indicating a size of a specific packet data. Identify a combination of a network controller and the number of packet data transmittable in the one transmission interval, receive the mapping information from the wireless network controller, and correspond to a combination of specific packet data using the received mapping information. Recognize the transmission format, and correspond to the recognized transmission format The payload size of the packet data and the header size of the packet data are checked to recognize the size of the packet data to be transmitted. When packet data to be transmitted is generated in the uplink, the mobile terminal determines the packet size according to the size of the packet data. And a mobile terminal constituting data.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.                     

The present invention provides a method of minimizing padding that may occur due to limited physical channel capacity by defining information indicating the size of packet data and the size of packet data. In particular, the present invention efficiently defines a relationship between the indication information indicating the size of packet data transmitted by a user terminal and the actual size of packet data, thereby reducing the padding size and setting a transmission format for supporting uplink. In providing. Therefore, the padding caused by the lack of indication information indicating the size of the packet data is minimized.

4 is a diagram illustrating a structure of an embodiment of a terminal performing EUDCH communication according to the present invention.

Referring to FIG. 4, the C / T multiplexing layer 410 and the MAC-e layer inserting multiplexing information into data transmitted from a plurality of Radio Link Control (RLC) layers 405 in the terminal. 415 and the like.

The RLC layer 405 is configured for each logical channel or radio bearer, and is a layer configured to store data generated in an upper layer and to have a size suitable for transmitting data generated in the upper layer in a radio layer. For reference, a radio bearer is a term referring to an RLC layer and an upper layer configured to process data of a specific application, and a logical channel is a logical channel between a specific RLC layer and a MAC layer.

The C / T multiplexing layer 410 inserts multiplexing information into the data delivered by the RLC layer 405. The multiplexing information may be an identifier of a logical channel, and a receiver sends data received with reference to the identifier to an appropriate RLC layer. The C / T multiplexing layer 410 is also called a MAC-d layer.

Although the structure of the MAC-e layer 415 is still under discussion, it is expected that the following functional blocks will be generally provided in the MAC-e layer.

Scheduling / Priority Processing Block 420: In consideration of the priority of the logical channels mapped to the EUDCH and the like, scheduling data to be transmitted in the next transmission interval.

Transmission buffer 430: A buffer for storing the data delivered by the RLC layer according to priority prior to transmission or for each MAC-d flow.

Priority is given to the logical channel, and the transmission buffer stores data of logical channels having the same transmission rank. Alternatively, the transmission buffer may store data of logical channels included in the same MAC-d flow.

The MAC-d flow classifies logical channels according to required quality of service (QoS). Logical channels requiring the same quality of service are classified into the same MAC-d flow, and the MAC-e layer 415 may provide a service quality specialized for each MAC-d flow. The quality of service may be adjusted by, for example, the number of HARQ retransmissions or the transmission power. In this case, the role of the transmission buffer is to store data until transmission.

As described above, a buffer exists in the RLC layer, and since the buffer of the RLC layer may serve as the transmission buffer 430, the buffer of the RLC layer may be used as the transmission buffer 430. Therefore, the transmission buffer in the MAC-e structure can be realized in the following three ways.

1. Configure transmit buffers by priority in the MAC-e layer                     

2. Configure transmission buffer in MAC-e layer by MAC-d flow

3. The RLC transmit buffer is used without a separate transmit buffer in the MAC-e layer.

Since any of the three methods is not particularly affected in the operation of the present invention, the transmission buffer in the present invention means one of the three.

The buffer distributor 425 transfers the data transferred from the C / T multiplexing layer 410 to the appropriate transmission buffer 430. The buffer distribution unit 425 is present only when the transmission buffer 430 is provided in the MAC-e layer 415.

The MAC-e PDU configuration unit 435 is a layer configured to receive data from the transmission buffers 430 and form a MAC-e PDU. The MAC-e PDU is a packet transmitted over a radio channel, and is composed of a header and a payload, and the payload stores data stored in the transmission buffer 430.

The HARQ layer 440 is a layer for controlling HARQ transmission and retransmission.

Data stored in the EUDCH is also referred to as a MAC-d PDU because it is delivered from a MAC-d entity. The size of MAC-d PDU is defined in units of logical channels. Therefore, the sizes of MAC-d PDUs stored in the transmission buffer may be different.

First Embodiment

The following first embodiment provides a method of classifying ETFs into a plurality of sections and increasing the transmission efficiency by distinguishing and setting the relationship between the ETF and the MAC-e PDU size for each section. That is, in the first section according to the first embodiment, the MAC-e PDU size for the special purpose is set to prevent the degradation of transmission efficiency that may occur in the small MAC-e PDU. Also, in the second section, padding is minimized by using the size of the MAC-d PDU (reference MAC-d PDU size) to be used most often as a step size. Also, in case the maximum MAC-e PDU size cannot be expressed because the size of the reference MAC-d PDU is small, the process of setting the size of the MAC-e PDU by setting the step size as a multiple of the reference MAC-d PDU in the last section is performed. Find out.

5 shows a structure of a MAC-e PDU according to the present invention.

Referring to FIG. 5, the MAC-e PDU includes a header portion 505 and a payload portion 510, and the MAC-d PDUs 515 and padding 520 are stored in the payload portion 510. The header portion 505 stores various kinds of control information.

The control information includes the size and number of MAC-d PDUs in the payload portion, information necessary for order reordering, and multiplexing information. The MAC-d PDU 515 is data transmitted from RLC entities connected to the EUDCH and may have a different size for each RLC entity. Therefore, there may be various sizes of MAC-d PDUs as many as the number of RLC entities connected to the EUDCH.

However, since only logical channels corresponding to packet services are mapped to EUDCH, and packet services generally do not limit the size of MAC-d PDUs, it can be expected that MAC-d PDUs of various sizes will not be stored in MAC-e PDUs. . Services with special requirements for the size of MAC-d PDUs are services that are very sensitive to delay, such as voice services, that do not buffer at the RLC layer.

For example, in the voice service, since the data generated by the codec is transmitted as it is without buffering, the size of the MAC-d PDU needs to be set according to the size of the data generated by the codec. However, the size of the MAC-d PDU is because data of services that are allowed to be buffered, such as packet services, are buffered in the buffer of the RLC layer and stored in MAC-d PDUs of a specific size through concatenation or partitioning with other data. Does not need to be correlated between In other words, the size of the MAC-d PDU need not vary.

In fact, 3GPP's test specification 34.108 defines 336-bit MAC-d PDUs and 656-bit MAC-d PDUs for packet services. It is not possible to rule out the need for more diverse MAC-d PDUs in the future, but in most cases only two or three MAC-d PDU sizes will exist in the EUDCH. Considering the above conditions, the predictability of the MAC-e PDU size is higher. For example, in EUDCH where only one type of MAC-d PDU size, MAC-d PDU_size_1, exists, the size of the MAC-e PDU will be as follows.

MAC-e PDU_size_1 = header_size + MAC-d PDU_size_1

MAC-e PDU_size_2 = header_size + 2 * MAC-d PDU_size_1

..

MAC-e PDU_size_n = header_size + n * MAC-d PDU_size_1

Here, n represents the number of MAC-d PDUs corresponding to the maximum transmission capacity of the EUDCH.

For example, if the maximum transmission capacity of the EUDCH is 8600 bits and MAC-d PDU_size_1 is 336 bits, n will be 25. That is, since the size of the possible MAC-e PDU is 25, it can be sufficiently encompassed by the ETF having a value between 0 and 63. If the ETF is set in association with the size of the MAC-d PDU, the likelihood of not requiring padding increases, thereby increasing transmission efficiency.

However, when the size of the MAC-d PDU is small, the maximum transmission capacity of the EDCH is large, or both cases are true, the size of the MAC-e PDU is not represented by an ETF having a value between 0 and 63. You may not be able to.

For example, when the maximum transmission capacity of the EDCH is 20000 bits, and MAC-d DPU_size_1 is 168 bits, n is 119. That is, since the possible MAC-e PDU size is 119, it cannot be expressed as an ETF.

In addition, if the size of the MAC-d PDU is not one type but is set in various types, the size of the possible MAC-e PDU is further increased, and thus may not be expressed by the 64 ETFs alone.

In the first embodiment of the present invention, the ETF is set in association with the size of the MAC-d PDU, but in order to solve the problem, some methods are added. That is, the ETF configuration proposed in the first embodiment of the present invention is as follows.

1. Determine one of the possible MAC-d PDU sizes as the reference MAC-d PDU size.

2. Split the ETF into multiple sections.

3. In the first section, the size of MAC-e PDUs to be used for a particular purpose is set according to the purpose.

4. In the second section, the size of the MAC-e PDU represented by the ETF is monotonically increased using the reference MAC-d PDU size as the step size.

5. In the third section, the size of the MAC-e PDU indicated by the ETF is monotonically increased by using a multiple of the reference MAC-d PDU size as the step size.

That is, the ETFs defined in the first section are for a small size MAC-e PDU used for, for example, a rate request or a buffer status report. When the rate request is performed using a MAC-e PDU, the buffer status report information of the corresponding UE may be stored in the MAC-e PDU, wherein the size of the MAC-e PDU is MAC- d It is independent of the size of the PDU. In addition, when several types of MAC-d PDU sizes are defined, the size of the MAC-e PDU in which one MAC-d PDU is stored may be defined in the first section. In other words, the sizes of the MAC-e PDUs defined in the first section may be the sizes of MAC-e PDUs that are frequently used and are irrelevant to the reference MAC-d PDU sizes.

For example, suppose that three logical channels are connected to a specific EUDCH, and each logical channel generates a 168-bit MAC-d PDU, a 336-bit MAC-d PDU, and a 656-bit MAC-d PDU. In this case, the size of the ETF defined in the first section may be as follows.                     

ETF 0 means the size of the MAC-e PDU to be used for the rate request,

ETF 1 means the size of a MAC-e PDU containing one 168-bit MAC-d PDU,

ETF 2 means the size of a MAC-e PDU containing one 336 bit MAC-d PDU,

ETF 3 may refer to a size of a MAC-e PDU containing one 656-bit MAC-d PDU.

In this case, since the size of the rate request may vary, ETF0 may be defined as the size of a rate request or the size of a rate request that is most frequently used.

For example, assuming that the MAC-e header size is 40 bits, the sizes indicated by the ETF1, ETF2, and ETF3 will be as follows. Below, MAC-e PDU_size_x means the size of MAC-e PDU corresponding to ETF x.

MAC-e PDU_size_0 = 50

MAC-e PDU_size_1 = 40 + 168 = 208

MAC-e PDU_size_2 = 40 + 336 = 376

MAC-e PDU_size_3 = 40 + 656 = 696

On the other hand, in the second section, the size of the MAC-e PDU is calculated using the reference MAC-d PDU size as the step size. That is, the size of the MAC-e PDU in the second interval may be calculated from Equation 2 below.                     

MAC-e PDU_size = header size + step size_1 * (ETF-n)

Here, value1 < ETF &lt;

In Equation 2, the header size is a value corresponding to the header size of the MAC-e PDU. The header size of the MAC-e PDU may have a variable value according to the characteristics of the MAC-d PDU stored in the payload of the MAC-e PDU, which may correspond to the maximum size of the MAC-e PDU header. . The step size _1 is a value corresponding to the reference MAC-d PDU size. In addition, the ETF means ETFs corresponding to the second section.

For example, if ETF 4 to ETF 52 correspond to the second interval, the ETF means values between 4 and 52. Here, value 1 is 3 because it means the maximum ETF of the first section and value 2 is 52 because it means the maximum ETF of the second section. N is a value for adjusting the MAC-e PDU size of the first ETF of the second interval. In other words, this value adjusts the starting point of the second section in terms of the MAC-e PDU size.

For example, if you want to set the MAC-e PDU size of ETF 4, the start point of the second interval, to header size + step size_1 * 2, n becomes 2. Here, assuming that the header size is 50 bits and the reference MAC-d PDU size is 168 bits, the sizes of the MAC-e PDUs indicated by the ETFs corresponding to the second interval will be as follows.

MAC-e PDU_size_4 = 50 + 168 * (4-2) = 386

MAC-e PDU_size_5 = 50 + 168 * (5-2) = 554                     

..

MAC-e PDU_size_52 = 50 + 168 * (52-2) = 8450

On the other hand, in the third section, the size of the MAC-e PDU is calculated using a multiple of the size of the reference MAC-d PDU as the step size. In this case, since the third section is the last section, the step size is set such that the last ETF is similar to the maximum size of the MAC-e PDU. That is, the size of the MAC-e PDU in the third section may be calculated from Equation 3 below.

MAC-e PDU_size = header size + step size_2 * (ETF-m)

Where value 2 < ETF &lt; ETF_max.

In Equation 3, step size_2 is a value corresponding to an arbitrary multiple of the reference MAC-d PDU size. The size of the step size_2 is determined by the size of the value 2 and the maximum size of the MAC-e PDU.

For example, if the maximum size of the MAC-e PDU is 20000 bits and value 2 is 52, interval 3 represents 11 values between 53 and 63 representing MAC-e between 8450 and 20000 bits. Therefore, step size_2 must be a multiple of 168 having a value close to (20000 8450) / 11 = 1050, and can be used as step size_2 since 1008 bits meet the condition.

That is, since ETFs mean ETFs corresponding to the third section, values of 53 to 63 are ETFs. ETF_max is the highest ETF, and if ETF is 6 bits, ETF_max is 63. Here, m is a value for adjusting the size of the MAC-e PDU of the second ETF of the third interval. In other words, this value adjusts the starting point of the third section in terms of MAC-e PDU size.

For example, assuming that the header size is 50 bits and the step size_2 is 1008 bits, the sizes of the MAC-e PDUs represented by the ETFs corresponding to the third section are as follows.

MAC-e PDU_size_53 = 50 + 1008 * (53-44) = 9122

MAC-e PDU_size_54 = 50 + 1008 * (54-44) = 10130

..

MAC-e PDU_size_63 = 50 + 1008 * (63-44) = 19202

In addition, for a small number of E-TFs, an E-TF indicating a MAC-e PDU size for a special purpose may be clearly transmitted through signaling, and the remaining E-TFs may use a stored value. For example, it can be set as follows.

E-TF 0 = 50 bit: signaled

E-TF 1 = 70 bit: signaled

E-TF 2 ~ E-TF 63 = predefined values

That is, the E-TF0 and the E-TF1 are transmitted through signaling similarly to the first interval information.

FIG. 6 is a diagram illustrating a relationship between an ETF and a MAC-e PDU size according to the present invention, illustrating a process of setting an ETF and a MAC-e PDU for each section. Here, the y-axis represents the MAC-e PDU size 605, the x-axis represents the ETF 610, and the bar 645 of the graph represents the MAC-e PDU size corresponding to a specific ETF.                     

Here, ETFs less than or equal to Value 1 630 correspond to the first interval, and specific Equations of MAC-e PDU sizes not derived from Equation 2 or Equation 3 correspond to the ETFs. .

In addition, ETFs greater than the value 1 630 and less than or equal to the value 2 635 correspond to the second interval, and the relationship between the ETF and the MAC-e PDU size may be calculated according to Equation 2 above. . At this time, the size is monotonically increased by the step size_1.

In addition, ETFs greater than value 2 (635) and less than or equal to ETF_max (640) correspond to the third interval, and the relationship between the ETF and the MAC-e PDU size may be calculated from Equation 3 above. It is characterized by the monotonous increase in size.

FIG. 7 is a diagram illustrating control signal exchange between an RNC, a terminal, and a Node B according to the present invention.

Referring to FIG. 7, the RNC 715 determines information required for ETF setting through the following process.

1. The reference MAC-d PDU size is determined in consideration of the logical channels connected to the EDCH, the MAC-d PDU sizes set in the logical channels, and the traffic characteristics of the logical channels. That is, the MAC-d PDU size of the logical channel expected to be used most frequently among the logical channels may be determined as the reference MAC-d PDU size.

2. Determine ETFs to be used for the first interval and MAC-e PDU sizes to correspond to the ETFs. This determines the ETF and MAC-e PDU size for the MAC-e control PDU to be used for the Buffer Status Report. In consideration of the logical channels connected to the EDCH and the MAC-d PDU sizes set in the logical channels, an ETF and a MAC-e PDU size to be used for the minimum set transmission are determined. The minimum set transmission refers to a transmission situation in which minimal data is transmitted on one logical channel and no data is transmitted on the remaining logical channels.

3. In the second section, parameters necessary for deriving the MAC-e PDU size are determined. Set value 1 and value 2 as appropriate. This means that ETFs to be included in the second section are determined. Step size 1 is set to the size of the reference MAC-d PDU. At this time, by setting n appropriately, the size of the MAC-e PDU corresponding to the first ETF of the second interval is adjusted.

4. Determine parameters to derive the MAC-e PDU size in the third interval. ETFs not included in the first and second sections are the ETFs to be included in the third section. step size 2 is set to a multiple of the reference MAC-d PDU size. At this time, by setting m appropriately, the size of the MAC-e PDU corresponding to the first ETF of the third section is adjusted.

That is, the RNC 715 sets the first section ETF setting information (the ETFs of the first section and the MAC-e PDU size information corresponding thereto) determined through the above process, value 1, value 2, step size_1, and step size_2. Information, such as n, m, header size, is transmitted to the Node B 710 (720).

The Node B 710 receives the information (ETFI) and sets an ETF (725).

At this time, the Node B 710 stores a table of the relationship between the ETFs and the MAC-e PDU size. Each time a TFI is received thereafter, the table identifies the relationship between the ETF and the MAC-e PDU. Alternatively, the relationship between the ETFs and the MAC-e PDU size for the first section is stored in a table for reference whenever necessary. For the second and third sections, <Equation 2> and <Equation 3> are constructed. It can be stored and saved as needed to derive a relationship between the ETF and the MAC-e PDU size as needed.

The RNC 715 transmits the same information transmitted to the Node B 710 to the terminal 705 (730).

When the terminal 705 receives the information, it sets an ETF (735). That is, the terminal stores a table of the relationship between the ETFs and the MAC-e PDU size. Then, when the UE configures the MAC-e PDU and transmits it to the Node B 710, the UE identifies the relationship between the ETF and the MAC-e PDU with reference to the table. Alternatively, the relationship between the ETFs and the MAC-e PDU size is stored in a table for the first section and referred whenever necessary.The second and third sections are composed of <Equation 2> and <Equation 3>. It can be stored and saved as needed to derive a relationship between the ETF and the MAC-e PDU size as needed.

Second embodiment

The second embodiment of the present invention proposes a method of considering the number of MAC-d PDUs having a predetermined size in the payload portion of the MAC-e PDU in determining the MAC-e PDU size. In this case, all possible combinations of the size and number of MAC-d PDUs to be accommodated in the payload of the MAC-e PDU may be calculated according to the type of logical channel connected to the EDCH and the MAC-d PDU sizes of the logical channel. It is possible to increase the transmission efficiency by corresponding to the ETF frequently used combinations of all the possible combinations.

For example, a logical channel having a MAC-d PDU size x and a logical channel having a MAC-d PDU size y are connected to an EDCH of an arbitrary terminal, and a MAC-d PDU having a size x during one transmission interval may have a maximum of 3 bits. , Up to 2 MAC-d PDUs of size y can be transmitted, and 12 combinations are possible as a combination of MAC-d PDUs that can be stored in one MAC-e PDU.

0 PDUs of size x 0 PDUs of size y

1 PDU of size x 0 PDUs of size y

2 PDUs of size x 0 PDUs of size y

3 PDUs of size x 0 PDUs of size y

0 PDUs of size x 1 PDU of size y

1 PDU of size x + 1 PDU of size y

2 PDUs of size x 1 PDU of size y

3 PDUs of size x 1 PDU of size y

0 PDUs of size x 2 PDUs of size y

1 PDU of size x 2 PDUs of size y

2 PDUs of size x + 2 PDUs of size y

3 PDUs of size x 2 PDUs of size y                     

The RNC may map some or all of the combinations to the ETF. For example, if the size of the ETF is 2 bits, only 4 of the 12 combinations may be used, and the RNC may determine which combination corresponds to which ETF and then notify the UE and the Node B. Accordingly, the UE and the Node B can know what MAC-e PDU size any ETF actually means based on the relationship between the combination of the ETF and the MAC-d PDUs.

That is, the second embodiment of the present invention performs the operation as follows.

When there are a plurality of logical channels connected to the EUDCH of any UE and there are a plurality of MAC-d PDU sizes, the RNC determines the number of MAC-d PDUs that can be transmitted at once for each MAC-d PDU size. The RNC calculates a combination of MAC-d PDU sizes and the number of MAC-d PDUs according to a predetermined scheme based on the information of the number of MAC-d PDUs that can be transmitted for each MAC-d PDU size. And the corresponding relationship between the ETFs.

The RNC transmits the information to the UE and the Node B, and the UE and the Node B are MAC-d PDU sizes and MACs that can be transmitted at one time based on the number of MAC-d PDUs that can be transmitted for each MAC-d PDU size. The combination of the number of PDUs is calculated according to the same method as the RNC, and the combination of the ETFs is recognized.

The UE and the Node B calculate the size of the MAC-e PDU that the ETF actually means by adding the size of the MAC-d PDUs and the MAC-e header size. The Node B and the UE determine the size of the MAC-e PDU for a given ETF based on the correspondence between the sizes of the ETF and the MAC-e PDU.

Next, the control signal exchange between the RNC and the Node B and the UE and the operation of each node will be described in more detail with reference to FIG. 8.

Referring to FIG. 8, at any point in time, the RNC 815 determines to set an EDCH in the terminal 805. Then, the correspondence relationship between the logical channel and the EDCH is determined. That is, it is determined which logical channel is mapped to the EDCH among the logical channels configured in the terminal or the logical channels to be set in the future. Through this process, the RNC can know the size of the MAC-d PDU to be used in the EDCH. For example, if any logical channel a having a MAC-d PDU size x and any logical channel b having a MAC-d PDU size y are mapped to an EDCH, the sizes of the MAC-d PDUs to be used in the EDCH are x and y. to be.

The RNC determines a set of the number of MAC-d PDUs that can be transmitted during one TTI (hereinafter, 'number of PDU set') for each MAC-d PDU size used for the EDCH (820). For example, if a MAC-d PDU of size x can transmit 0, 1, 2, or 4 at a time, the set of number of PDUs for size x is [0, 1, 2, 4]. do. The RNC may determine the number of PDU sets for any MAC-d PDU size as follows.

The RNC determines the maximum number of MAC-d PDUs that can be transmitted at one time by using the sum of maximum transmission rates of logical channels having a specific MAC-d PDU size and a transmission time interval of the EDCH. In this case, the transmission period refers to the time required for the transmission of one MAC-e PDU in the radio channel, the transmission period of 2 msec and 10 msec is defined. In addition, the maximum transmission rate of the logical channel is a value given by the core network, and is determined by the QoS characteristic of an application connected to the logical channel. That is, since several logical channels can use a single MAC-d PDU size, the RNC considers the sum of the maximum transmission rates.

If the sum of the maximum transmission rates of logical channels having a 200-bit MAC-d PDU size is 1 Mbps and the TTI of the EDCH is 2 msec, the maximum number of MAC-d PDUs that can be transmitted during one TTI is the maximum transmission rate. Sum * TTI / MAC-d PDU size rounded up to 10.

That is, 'the maximum number of MAC-d PDUs that can be transmitted during one TTI' of the size of the arbitrary MAC-d PDU is n means that 0 to n MAC-d PDUs can be transmitted during one TTI. The number of PDU set includes n + 1 elements up to [0,1,., N].

However, the RNC may include only some of these in the number of PDU sets. For example, when the maximum number of MAC-d PDUs that can be transmitted during one TTI is 10, the number of MAC-d PDU sets of the MAC-d PDU includes only five, such as [0,1,2,5,10]. You can. Of course, it is also possible to include all 11 elements. This is because MAC-d PDUs can be queued in the transmission buffer until the number defined in the number of PDU sets is collected, especially for MAC-d PDUs generated by an application that allows delay.

The RNC determines the 'maximum number of MAC-d PDUs that can be transmitted during one TTI' for all MAC-d PDU sizes used for EDCH and determines the number of PDU sets.

If the size of n + 1 MAC-d PDUs is set in the EDCH of any UE from S_0 to S_n, a number of elements may be defined in the number of PDU sets, and each element is indicated as follows.

number of PDU set for S_0 = [N_0_0, N_0_1,., N_0_ (x-1)],

number of PDU set for S_1 = [N_1_0, N_1_1,., N_1_ (y-1)]

...

number of PDU set for S_ (n-1) = [N_ (n-1) _0, N_ (n-1) _1,., N_ (n-1) _ (w-1)]

number of PDU set for S_n = [N_n_0, N_n_1,., N_n_ (z-1)]

In the above, N_j_k means (k + 1) th elements of the number of PDU set for S_j, which means that there are N_j_k MAC-d PDUs having an S_j size. x, y, w, z and the like are arbitrary integers meaning the number of elements of the number of PDU sets.

The RNC calculates the enhanced enhanced transport format (CETF: Computed Enhanced Transport Format) calculated as follows using the number of PDU sets (825). The CETF is all combinations of elements belonging to different number of PDU sets and identifiers of each combination.

[CETF calculation method]

CETF 0 = [N_0_0, N_1_0,., N_ (n-1) _0, N_n_0]

CETF 1 = [N_0_0, N_1_0,., N_ (n-1) _0, N_n_1]

.

CETF z = [N_0_0, N_1_0,., N_ (n-1) _0, N_n_z]

CETF (z + 1) = [N_0_0, N_1_0,., N_ (n-1) _1, N_n_0]                     

CETF (z + 2) = [N_0_0, N_1_0,., N_ (n-1) _1, N_n_1]

...

CETF (x * y *. * W * z-1) = [N_0_x, N_1_y,., N_ (n-1) _w, N_n_z]

For example, the CETF 1 means that MAC-d PDUs having N_0_0 S_0 sizes, MAC-d PDUs having N_1_0 S_1 sizes, and N_ (n-1) _0 S_ (n−) 1) MAC-d PDUs having a size, MAC-d PDUs having N_n_1 S_n sizes, and the like.

The total number of CETFs is x * y * ... * w * z, and the order of assigning identifiers to each CETF may be different from the above order. However, in assigning an identifier to each CETF, the RNC, the Node B, and the terminal all assign the identifiers in the same order so that the CETF meaning any identifier must be the same in the RNC, the Node B, and the UE.

[Example 1] below provides an embodiment of calculating CETFs and assigning identifiers as described above.

[Example 1]

There are a 100-bit MAC-d PDU, a 250-bit MAC-d PDU, and a 330-bit MAC-d PDU. When S_0 is represented by 100 bits, S_1 by 250 bits, and S_2 by 330 bits, it is assumed that the number of PDU sets are defined as follows.

number of PDU set for S_0 = [0,1,2],

number of PDU set for S_1 = [0,1]

number of PDU set for S_2 = [0,1]                     

Therefore, the CETF is calculated as follows.

CETF 0 = [0, 0, 0], CETF 1 = [0, 0, 1], CETF 2 = [0, 1, 0], CETF 3 = [0, 1, 1],

CETF 4 = [1, 0, 0], CETF 5 = [1, 0, 1], CETF 6 = [1, 1, 0], CETF 7 = [1, 1, 1],

CETF 8 = [2, 0, 0], CETF 9 = [2, 0, 1], CETF 10 = [2, 1, 0], CETF 11 = [2, 1, 1]

For example, CETF 10 means two 100-bit MAC-d PDUs, one 250-bit MAC-d PDU, and 330-bit MAC-d PDUs.

As shown in [Example 1], the CETF lists all combinations of MAC-d PDUs that can be obtained through given number of PDU sets. When the CETF is calculated as described above, the RNC determines mapping information between the CETF and the ETF (830). This is to determine which CETF corresponds to which ETF.

When the RNC determines the CETF-ETF mapping information, the following rules may be applied.

1. CETFs exceeding the maximum size of MAC-e PDUs are excluded from mapping to ETFs.

For example, when the maximum size of the MAC-e PDU is 500 bits, the size of the CETF 3 is 580 bits, the size of the CETF 7 is 680 bits, the size of the CETF 9 is 530 bits, The size of CETF 11 is 780 bits, so it is not mapped to ETF.

2. If there are enough ETFs available, map all remaining CETFs to ETFs.

If the number of available ETFs is not enough, only some of the CETFs map to ETFs. If there are multiple CETFs of similar size, you can match the number of CETFs with the number of ETFs by mapping only some of them to ETFs. Using the situation in Example 1 as an example, if the number of available ETFs is six, two of the eight remaining CETFs should be excluded. CETF 1 has a size of 330 bits and CETF 6 has a size of 350 bits, so CETF 1 can be excluded from the selection. In addition, the CETF 5 is 430 bits and the CETF 10 is 450, so CETF 5 can be excluded from the selection.

3. When mapping ETFs and CETFs, map the smallest CETFs in order from ETFs.

Taking [Example 1] as an example, the following CETFs remain.

CETF 0 = 0 bit, CETF 2 = 250 bit, CETF 4 = 100 bit, CETF 6 = 350 bit, CETF 8 = 200 bit, CETF 10 = 450 bit

If you map them to the ETF in order of magnitude,

ETF 0 = CETF 0 (= 0 bit), ETF1 = CETF 4 (= 100 bit), ETF 2 = CETF 8 (= 200 bit), ETF 3 = CETF 2 (= 250 bit), ETF 4 = CETF 6 (= 350 bit), ETF 5 = CETF 10 (= 450 bit)

After completing the process, the RNC 815 constructs an EDCH configuration message, stores the following information in the message, and transmits the following information to the Node B 810 (835).

Number of PDU set information: Includes all of the Number of PDU sets determined in step 820.

CETF-ETF mapping information: The CETF-ETF mapping information determined in step 830, and may additionally include the size of the MAC-e header to be used for each ETF. That is, the CETF-ETF mapping information includes information indicating which CETF the ETF is mapped to and information indicating which MAC-e header should be used for the ETF as many as the number of ETFs.

The size of the MAC-e header may have a variable value according to the type or size of the MAC-d PDU received in the MAC-e payload.

For example, in [Example 1], ETF 4 stores one 100-bit MAC-d PDU and one 250-bit MAC-d PDU in a payload.

In this case, if the MAC-d PDUs belong to different MAC-d flows, two MAC-d flow identifiers are inserted in a MAC-e header. On the other hand, since only one 100-bit MAC-d PDU is stored in the payload, only one MAC-d flow identifier is inserted in the MAC-e header. Therefore, in both cases, the size of the MAC-e header is different. As such, the size of the MAC-e header may vary depending on the characteristics of the MAC-d PDU stored in the payload, and the RNC calculates the size of the MAC-e header for each ETF, and calculates the value of the CETF-ETF. Include in mapping information.

When the Node B 810 receives the information, the Node B 810 calculates a CETF using the Number of PDU set information (840). This is done in the same way as the RNC computed the CETF in step 825, so the description is omitted.

The Node B 810 recognizes the CETF corresponding to the ETF by using the CETF-ETF mapping information, and then calculates the size of the MAC-e PDU that the ETF means by adding the MAC-e header size and the payload size. (845).

The CETF-ETF mapping information for any ETF x indicates that the CETF mapped to ETF x is CETF y and the MAC header size is n.

And when CETF y means

CETF y = [N_0_a, N_1_b,., N_n_c],

The payload size of CETF y is as follows.

Payload size of CETF y = S_0 * N_0_a + S_1 * N_1_b +. + S_n * N_n_c

And the size of the MAC-e PDU means ETF x is shown in Equation 4 below.

The CRC siz is a size of an error detection code added to a MAC-e PDU, and 24 bits may be used as an error detection code as a CRC.

The Node B 810 calculates the MAC-e PDU size for all the ETFs notified through the CETF-ETF mapping information and stores the MAC-e PDU size in an arbitrary table.

If the UE 805 transmits the ETF in the future, the Node B 810 recognizes the MAC-e PDU size corresponding to the ETF transmitted through the table. Of course, Node B may store the CETF and MAC-e header size corresponding to the ETF, and calculate the corresponding MAC-e PDU size whenever a predetermined ETF is received.                     

The RNC 815 also transmits an EDCH configuration message to the terminal, and the following information is also received in the message (850).

Number of PDU set information: Includes all the Number of PDU sets determined in step 820.

CETF-ETF Mapping Information: The CETF-ETF mapping information determined in step 830 may additionally include the size of MAC-e header to be used for each ETF.

In step 825, the terminal 805 calculates the CETF in the same manner as the RNC 815 (855). After recognizing the CETF corresponding to the ETF using the CETF-ETF mapping information, the MAC-e header size and the payload size are summed to calculate the size of the MAC-e PDU, which the ETF means (860). Since the above process is the same as that performed by Node B at 845, description thereof is omitted. When the UE configures the MAC-e PDU in the future, the UE is configured according to the size of the ETF, and transmits the size to the Node B according to the ETF information.

As described above, in the second embodiment of the present invention, the number of PDU sets may be defined for each size of the MAC-d PDU. In this case, except that the Number of PDU set information is defined for each MAC-d flow and transmitted from the RNC to the UE and the Node B, the CETF is calculated from the Number of PDU set information, and the CETF-ETF mapping information is used to generate the CETF-. Since the method of determining the mapping between ETFs is the same, detailed description thereof will be omitted.

In the present invention operating as described in detail above, the effects obtained by the representative of the disclosed invention are briefly described as follows.

The present invention can minimize the size of the padding information required for the MAC-e PDU by efficiently configuring information indicating the size of the packet data in the mobile communication system for transmitting the packet data over the uplink.

Claims (6)

In the method for setting the transmission format of the packet data in a mobile communication system supporting uplink, The wireless network controller divides transmission formats, which are information indicating the size of a plurality of packet data, into a plurality of sections, and transmits transmission format information indicating a relationship between the sizes of the plurality of packet data and the transmission formats for each divided section. Transmitting to a mobile terminal, The mobile station recognizes the size of packet data corresponding to the transmission formats included in the first section and the transmission formats included in the first section among the transmission format information, Among the format information, information indicating the size of packet data most frequently used is used as a step size to correspond to the transmission formats included in the second section of the plurality of sections and the transmission formats included in the second section. Recognizing the size of the packet data to be used, and using the multiple of the size of the most frequently used packet data as a step size, the transmission formats included in the third section and the third section of the plurality of sections Recognizing the size of packet data corresponding to the transmission formats; When the packet data to be transmitted on the uplink is generated, the mobile station checks the size of the generated packet data and sets a transmission format corresponding to the checked packet data to the transmission format of the generated packet data. Transmission format setting method characterized in that. In the method for setting the transmission format of the packet data in a mobile communication system supporting uplink, The wireless network controller determines the number of packet data that can be transmitted in one transmission interval according to the size of packet data used in each logical channel, sets the combination of the determined number of packet data, and the combination of the number of packet data and Transmitting mapping information mapped to a transmission format indicating a size of a specific packet data to a mobile terminal; The mobile station identifies a combination of the number of packet data that can be transmitted in the one transmission interval, recognizes a transmission format corresponding to the combination of the number of specific packet data by using the mapping information, and recognizes the transmission format according to the recognized transmission format. Identifying the size of the packet data to be transmitted by checking a payload size of a corresponding packet data and a header size of the packet data to be transmitted; And generating packet data according to the size of the recognized packet data when the packet data to be transmitted on the uplink is generated. 3. The method of claim 2, Recognizing the size of the packet data to be transmitted, And a mobile terminal recognizes the size of the packet data to be transmitted by checking the size of an error detection code added to the packet data to be transmitted together with the size of the header and the payload size. An apparatus for setting a transmission format of packet data in a mobile communication system supporting uplink, A wireless network that divides transmission formats, which are information indicating the size of a plurality of packet data, into a plurality of sections, and transmits transmission format information indicating a relationship between the sizes of the plurality of packet data and the transmission formats for each divided section. With the controller, Receiving the transmission format information from the wireless network controller, and among the received transmission format information corresponding to transmission formats included in a first section of the plurality of sections and transmission formats included in the first section Recognizing the size of the packet data and using the information indicating the size of the packet data most frequently used among the transport format information as a step size, the transmission formats included in the second section of the plurality of sections and the two Recognize the size of the packet data corresponding to the transmission formats included in the first section, and include the multiple of the size of the most frequently used higher layer packet data in the third section of the plurality of sections using the step size The size of the packet data corresponding to the transmitted transmission formats and the transmission formats included in the third section. And a mobile terminal that checks the size of the generated packet data and sets a transmission format corresponding to the checked packet data size as a transmission format of the generated packet data when packet data to be transmitted uplink is generated. Transmission format setting device, characterized in that. An apparatus for setting a transmission format of packet data in a mobile communication system supporting uplink, Determine the number of packet data that can be transmitted in one transmission interval according to the size of the packet data used in the logical channel, set the combination of the determined number of packet data, the combination of the number of the packet data and the size of specific packet data A wireless network controller for transmitting mapping information mapping a transmission format indicating a Check the combination of the number of packet data that can be transmitted in the one transmission interval, receive the mapping information from the radio network controller, and recognize the transmission format corresponding to the combination of specific packet data by using the received mapping information. And checking the payload size of the packet data corresponding to the recognized transmission format and the header size of the packet data to recognize the size of the packet data to be transmitted, and if the packet data to be transmitted on the uplink is generated, the recognized packet And a mobile terminal for constructing packet data according to the size of the data. The method of claim 5, And the mobile terminal recognizes the size of the packet data to be transmitted by checking the size of an error detection code added to the packet data to be transmitted together with the size of the header and the size of the payload.

Images