KR100810274B1 - Apparatus for transmitting/receiving transprot format resource set in communication system using high speed downlink packet access scheme and method therof - Google Patents

Abstract

The present invention relates to a communication system using a fast forward packet access scheme, comprising code information used by a user terminal for a fast forward packet access call and transport format resource information for the user terminal, each of which includes different fields of a specific channel. In a communication system using a fast forward packet access scheme, each base station transmits a transmission block set size corresponding to a modulation and coding scheme level supported by the user terminal and a modulation and coding scheme level supported by the user terminal. Determine a transport format resource set for the user terminal, compare the size with a size of a field for transmitting the transport format resource information, and determine a block coding scheme for the transport format resource set according to the comparison result. .

TFRS, TFRI, TFRS_FT, TFRS_RT, code info, N / C

Description

Apparatus and method for transmitting and receiving a transmission format resource set in a communication system using a high-speed forward packet access method {APPARATUS FOR TRANSMITTING / RECEIVING TRANSPROT FORMAT RESOURCE SET IN COMMUNICATION SYSTEM USING HIGH SPEED DOWNLINK PACKET ACCESS SCHEME AND METHOD THEROF}             

1 is a diagram illustrating an example of allocating an OVSF code in a typical high speed forward packet access communication system;

2 illustrates a common control channel structure of a communication system using a conventional high speed forward access method.

3 illustrates a transmitter physical layer channel structure of a typical high speed forward packet access communication system.

4 is a diagram illustrating the amount of data of each process in the physical layer channel structure of FIG.

5 illustrates a conventional rate matching scheme.

6 is a diagram illustrating a signal flow for transmitting a transport format and resource related information in a communication system using a fast forward packet access scheme according to an embodiment of the present invention.                 

7 illustrates an initial transport format resource set structure according to an embodiment of the present invention.

8 is a diagram illustrating an initial transport format resource information tree structure according to a subcomponent ratio according to another embodiment of the present invention.

9 illustrates a TBS component structure according to another embodiment of the present invention.

10 illustrates a structure of a common control channel transmitter according to another embodiment of the present invention.

11 illustrates a common control channel receiver structure of a communication system using a conventional high speed forward packet access scheme.

12 is a flowchart illustrating a process of configuring a transport format resource set in a base station according to another embodiment of the present invention.

13 is a flowchart illustrating a process of configuring a transport format resource set in a user terminal according to another embodiment of the present invention.

14 illustrates a fast forward common channel transmitter physical layer channel structure according to another embodiment of the present invention.

FIG. 15 is a diagram illustrating the amount of data of respective processes in a transmitter physical layer channel structure of a fast forward packet access communication system according to another embodiment of the present invention.

16 illustrates a common control channel structure according to another embodiment of the present invention.

17 illustrates a common control channel transmitter structure corresponding to the common control channel structure of FIG. 16.

FIG. 18 illustrates a common control channel receiver structure corresponding to the common control channel transmitter structure of FIG. 17.

19 illustrates a common control channel structure according to another embodiment of the present invention.

20 illustrates a common control channel transmitter structure corresponding to the common control channel structure of FIG.

21 illustrates a common control channel receiver structure corresponding to the common control channel transmitter structure of FIG. 20.

22 illustrates a common control channel structure according to another embodiment of the present invention.

FIG. 23 illustrates a common control channel transmitter structure corresponding to the common control channel structure of FIG. 22.

24 is a diagram illustrating a common control channel receiver structure corresponding to the common control channel transmitter structure of FIG. 23.

The present invention relates to a communication system using a fast forward packet access method, and more particularly, to an apparatus and method for transmitting a transport format resource set for user data.

The present invention relates to a high speed forward packet access communication system, and more particularly to a method of reducing the amount of reverse control information.

In general, a high speed downlink packet access (High Speed Downlink Packet Access) method is a high speed forward common channel (HS-DSCH: High Speed), which is a forward data channel for supporting forward high speed packet data transmission in a universal mobile terrestrial system (UMTS) communication system. -Data transmission scheme including Downlink Shared Channel (hereinafter referred to as "HS-DSCH") and control channels related thereto. Adaptive Modulation and Coding (hereinafter referred to as "AMC"), Hybrid Automatic Retransmission Request (hereinafter referred to as "HARQ"), and fast cell selection to support the fast forward packet access. Fast Cell Select (hereinafter, referred to as "FCS") has been proposed.

Next, the AMC scheme, the FCS scheme, and the HARQ scheme, which are schemes for supporting the fast forward packet access, will be described.

First, the AMC method will be described.

The AMC scheme is a modulation scheme and coding of different data channels according to channel conditions between a specific base station (Node B, hereinafter referred to as Node B ") and a user terminal (UE: User Element, hereinafter referred to as UE). The AMC scheme has a plurality of modulation schemes and a plurality of coding schemes, and the data is obtained by combining the modulation schemes and coding schemes. Modulate and code a channel signal, typically each of the combinations of modulation schemes and coding schemes is called a modulation and coding scheme (hereinafter referred to as " MCS ") and level according to the number of MCSs. A plurality of MCSs may be defined from 1 to level n. That is, the AMC scheme sets a level of the MCS to a channel between the UE and a Node B that is currently wirelessly connected. A manner in accordance with the state determined adaptively for improving the Node B overall system efficiency.

Second, the FCS scheme will be described.

The FCS scheme is a method for quickly selecting a cell having a good channel state among a plurality of cells when the UE using the fast forward packet access scheme is located in a cell overlap region, that is, a soft handover region. Specifically, the FCS scheme includes: (1) when a UE using the fast forward packet access scheme enters a cell overlap region of any first Node B and any second Node B, the UE includes a plurality of cells. That is, a radio link (hereinafter referred to as "Radio Link") with a plurality of Node Bs is set. In this case, a set of cells configured with the UE and a radio link is called an active set. (2) Receive the packet data for the fast forward packet access method only from the cells maintaining the best channel state among the cells included in the active set to reduce the overall interference. In this case, the cell in which the channel state is the best in the active set is transmitted, and a cell transmitting high-speed forward packet access packet data is called a best cell, and the UE 130 periodically checks channel states of cells belonging to the active set. When a cell having a better channel state is generated than a current best cell, a best cell indicator is transmitted to cells belonging to the active set to replace the current best cell with a cell having a better channel state. do. The best cell indicator includes an identifier of a cell selected as a best cell and is transmitted. Accordingly, cells in the active set receive the best cell indicator and examine a cell identifier included in the best cell indicator. Thus, each of the cells in the active set checks whether the best cell indicator corresponds to its best cell indicator, and the corresponding cell selected as the best cell is a packet to the UE using a fast forward common channel (HS-DSCH). Send the data.

Third, an HARQ scheme, in particular, a multi-channel Stop And Wait Hybrid Automatic Retransmission Request (hereinafter referred to as "n-channel SAW HARQ") will be described.

The HARQ scheme newly applies the following two methods to increase the transmission efficiency of the ARQ (Automatic Retransmission Request) scheme. The first scheme is to perform the retransmission request and response between the UE and the Node B. The second scheme is to temporarily store the data in error and combine it with the retransmission data of the corresponding data. will be. In addition, the fast forward packet access scheme has introduced the n-channel SAW HARQ scheme to compensate for the shortcomings of the conventional Stop and Wait ARQ (SAW ARQ) scheme. In the SAW ARQ scheme, the next packet data is transmitted only after receiving an ACK for the previous packet data. However, since the next packet data is transmitted only after receiving the ACK for the previous packet data, there may occur a case where the ACK should be waited even though the packet data may be transmitted at present. In the n-channel SAW HARQ scheme, a plurality of packet data may be continuously transmitted without receiving an ACK for the previous packet data, thereby improving channel usage efficiency. That is, if n logical channels are established between the UE and the Node B, and each of the n channels can be identified by a specific time or channel number, the UE, which receives the packet data, at any point in time It is possible to know which channel the received packet data is transmitted through, and to take necessary measures such as reconstructing the packet data in the order to be received or soft combining the packet data.

The fast forward packet access communication system, which supports the AMC scheme, the FCS scheme, and the HARQ scheme to increase communication efficiency, is a system in which a plurality of UEs share transmission resources of some forward transmission resources. The forward transmission resources include a transmission output and an orthogonal variable orthogonal variable spreading factor (OVSF) code. In the case of the OVSF code, as discussed in the current standard, a spreading factor (SF) is spread. It is contemplated to use 10 OVSF codes in the high speed forward packet access communication system when the factor) is 16 (SF = 16).

Multiple OVSF codes available in the fast forward packet access communication system may be simultaneously used by multiple UEs at a particular time. That is, OVSF code multiplexing is possible between a plurality of UEs at a specific same time in the fast forward packet access communication system. Such OVSF code multiplexing will be described with reference to FIG. 1.

1 is a diagram illustrating an example of assigning an OVSF code in a typical high speed forward packet access communication system. In FIG. 1, in particular, the diffusion coefficient of 16 (SF = 16) will be described as an example.

Referring to FIG. 1, each OVSF codes are shown as C (i, j) according to the location of the code tree. In C (i, j), the variable i represents the spreading coefficient value, and the variable j represents the order from the leftmost in the OVSF code tree. For example, C (16,0) indicates that the spreading factor is 16, and the spreading factor is 16 when the spreading factor is 16 in the OVSF code tree. FIG. 1 assigns 10 OVSF codes to the fast forward packet access communication system from 7th to 16th, that is, C (16.6) to C (16,15) in the OVSF code tree when the spreading factor is 16. The case is shown. The ten OVSF codes may be multiplexed to multiple UEs.

For example, assuming that A, B, and C are any users using the fast forward packet access communication system, i.e., any UEs, four codes for A and five codes for B at any time t0. For C, code multiplexing is possible, such as one code. The number of OVSF codes to allocate to each UE and the location on the OVSF code tree are determined by the Node B, which is determined in consideration of the amount of user data of each of the UEs stored in the Node B.

Meanwhile, the types of channels used in the HSDPA communication system are as follows.

First, the HS-DSCH through which user data is actually transmitted, and the shared control channel (SHCCH) used by Node B to transmit information about AMC, FCS, HARQ, etc., described above to the UE. SHCCH ") and Associated Forward Channels (DPCHs) for the Node B to inform the UE that there is data that the UE should receive in the near future. In order to support HARQ and AMC, there is one type of reverse channel through which the UE transmits feedback information to the Node B.

The SHCCH will now be described with reference to FIG. 2.

2 is a diagram illustrating a common control channel structure of a communication system using a conventional high speed forward access method.

Referring to FIG. 2, first, a transport format and resource related information (TFRI) field is referred to as an MCS level, code allocation information, and a transport block set (TFRI). TBS: Transport Block Set, which will be referred to as " TBS ") and the like. The HARQ information field includes HARQ related information such as a HARQ processor number. In addition, the cyclic redundancy check (CRC) field performs an error check on the TFRI field or an error check on the TFRI field and the HARQ field.                         

Here, the information included in the TFRI field will be described.

(1) MCS level: MCS level to be used for HS-DSCH transmitted to the UE

(2) code allocation information: number of codes of HS-DSCH transmitted to a corresponding UE

(3) TBS size: The number of transport blocks (TB: Transport Block, hereinafter referred to as "TB") carried on the HS-DSCH transmitted to the corresponding UE, the rate matching (rate matching) of the corresponding UE This is a required parameter.

However, a method of separately setting an individual field in a TFRI field and separately delivering the MCS level, the code allocation information, and the TBS size information as described above is inefficient for the following reasons. The reason is that the number of MCS levels and code allocation information may be different for each UE. That is, any UE A supports all defined MCS levels, while another UE B may only support a few of them. Similarly, any UE A can process a large number of codes simultaneously, but any UE B can only process fewer codes than the UE A. Therefore, UE A may need 3 bits and 6 bits in the MCS level and code allocation information fields, respectively, and UE B may need 2 bits and 4 bits in the MCS level and code allocation information fields, respectively. In this case, the MCS level field And fixing the size of the Code info field will be inefficient. The same problem of inefficiency also applies to the TBS size information.

Therefore, in the current standard discussion, a scheme is provided to configure the information, that is, the MCS level, code allocation information, and TBS size information into one set so as to give logical setters to the set. As such, an example in which logical identifiers are assigned to TFRI is shown in Table 1 below.

The transport channel (TCH: hereinafter referred to as "TCH") ID (ID) and the TBS size information will be described in more detail here. The TCH refers to a set of schemes for processing data in a physical channel, and in general, the TCH refers to a channel coding scheme at a certain coding rate for data transmitted through the corresponding TCH. Is defined in terms of the size of the data, the size of the data to be divided (TB size), and the number of TBs that can be transmitted during one transmission time interval (TTI). do. Thus, any two different TCHs will be different from each other as described above. Since multiple TCHs can be multiplexed in time through the same high-speed forward physical common channel (HS-PDSCH: High Speed-Physical Downlink Shared CHannel, hereinafter referred to as "HS-PDSCH"), the HS received at any time The UE should be able to recognize which transport channel the PDSCH belongs to, and this is the TCH ID.

The TBS size is information that Node B informs the UE so that the physical layer of the UE can calculate the rate matched number of bits. The TBS size represents the number of TBs transmitted by any UE during one TTI, and the rate matching scheme indicates that when the Node B physical layer repeats or punctures user data, the repetition or puncturing may occur. Information indicating whether or not in the form. The TBS size is transmitted through the TFRI field as described above, and the rate matching scheme is not transmitted separately because the TBS size and the rate matching scheme have a corresponding relationship with each other. This is because the matching method is also known.

Next, a transmitter physical layer structure of the HSDPA communication system will be described with reference to FIG. 3.

3 is a diagram illustrating a transmitter physical layer channel structure of a typical high speed forward packet access communication system.

Referring to FIG. 3, transport blocks to be transmitted from a higher layer to a physical layer, that is, a transport channel, are transferred (301). Here, the period in which the transport blocks are transmitted from the upper layer to the physical layer is performed every transmission time interval (TTI), and the transport blocks transmitted in units of the transmission time period constitute a transport block set. The number of transport blocks transmitted through the transport block set is the size of the transport block set (TBS size). Header information, as shown in FIG. 3, is inserted into transport blocks, that is, transport block sets, transmitted from the upper layer (302). The header information may be information such as a serial number available for ordering of transport blocks of the transport block set at a receiver side corresponding to the transmitter. Then, a CRC (Cyclic Redundancy Check) is added to the transport block set into which the header information is inserted (303). Here, for example, a 24-bit CRC operation may be considered as the CRC.

The transport block set to which the CRC is added is segmented into a code block of a size suitable for channel coding for an error correction code (304), and then channel coded for channel transmission. 305). Here, the data completed up to the channel coding is called a coded block, and after performing the code block segmentation, that is, an information bit constituting the transport block at D4 is determined through the channel coding. In other words, it is converted to a symbol at D5. The coding block is rate matched in consideration of the length of the physical layer frame, the spreading factor, and the like, for transmission to the actual physical layer (306). That is, the rate matching is a process of making the coding block equal to the amount of information that can be transmitted through an actual physical channel. For example, if the number of symbols output through the channel coding is D5 and the number of symbols to be transmitted through the physical channel is D9, the number of symbols to be transmitted is matched through the rate matching. That is, if D5 is greater than D9, puncturing is performed. If D9 is greater than D5, iteration is performed to match the number of symbols of D5 and D9.                         

The rate matched data is divided into units that can be transmitted through a physical channel (physical channel segmentation) 307. In the physical channel segmentation, since the fast forward common channel may be composed of a plurality of codes, the entire data is divided into a size corresponding to each code. The physical channel segmented data is interleaved to prevent burst error (308), and the interleaved data is mapped to a physical channel to be finally transmitted (physical channel mapping) and transmitted on the corresponding physical channel. (309).

As described above with reference to FIG. 3, the amount of data to be transmitted is changed as follows through the above processes.

D1 = size of transport block (TB_size) * size of transport block set (TBS_size)

D2 = D1 + Header Size (Header_size)

D3 = D2 + CRC size (e.g. 24 bit)

D4 = D3

D5 = D4 * 1 / Coding Rate (CR)

D6 = D5 + Size of Rate Matching (RM)

D7 = D6

D8 = D7

D9 = D8 = {(Transport block size * Transport block set size * Header size + CRC size) / coding rate + rate matching} [(TB_Size * TBS + Header_Size + CRC) / CR + RM]

In addition, in FIG. 3, the data unit of the user data changes as follows. D1 to D4 are information bit (IB) units, D5 to D8 are symbol units, and D9 is a modulated symbol (MS) unit. That is, when the information bit is subjected to channel coding, the symbol becomes a symbol, and the symbol becomes a modulated symbol through the modulation process.

In addition, since D9 means the total sum of data transmitted through an actual physical channel, it can be expressed as Equation 1 below.

D9 = NC (number of codes) * Code_capa (amount of data that one code can pass) = NC * [(chiprate / diffusion coefficient per time slot) * number of timeslots per transmission time period (TTI) * MO (Modulated order)] = NC * MO * 480

In Equation 1, a unit becomes a symbol unit, and when Equation 1 is rearranged to be equivalent to D9, Equation 2 may be expressed as Equation 2 below.

[TB_Size * TBS + Header_Size + CRC] / CR + RM = NC * 480 * MO

Equation 2 may be expressed as Equation 3 below.

RM = NC * 480 * MO * CR TB_Size * TBS Header_Size CRC

In Equation 3, if the rate matching is repetition, the variable RM is a positive value. If the rate matching is puncturing, the variable RM is a negative value.

A data amount of each process described in FIG. 3 will be described with reference to FIG. 4.

4 is a diagram illustrating the amount of data of each process in the physical layer channel structure of FIG.

Referring to FIG. 4, D9 denotes a total of data transmitted through a physical channel, and is a constant determined by Node B at an arbitrary time point. That is, the D9 is determined by the number of codes assigned to any user terminal at any time and the MCS level. The transport block size (TB_Size), CRC size, and header size (Header_Size) are also constants that do not change during the call, and the transport block set (TBS) depends on the amount of data of the corresponding user terminal stored in Node B. It is a variable that changes. In other words, in the above equations, the parameters that change every transmission time period (TTI) are a transport block set (TBS), a code number (NC), a modulation order (MO), and a coding rate (CR). The transport format resource information (TFRI) of the common control channel is notified from the base station to the user terminal every transmission period. A data amount of each process described in FIG. 3 will be described with reference to FIG. 4.

In addition, the rate matching operation of the physical layer structure described with reference to FIG. 3 will be described with reference to FIG. 5.

5 is a diagram illustrating a conventional rate matching scheme.                         

Referring to FIG. 5, when the base station, that is, the transmitter determines rate matching, the next channel after repeating or puncturing the coding blocks shown as D5 in the physical layer channel structure described with reference to FIG. After performing the processing, the data is transmitted to the user terminal, that is, the receiver. Then, when the rate matching value is negative, that is, when the coding blocks are punctured, the receiver inserts 0 into the punctured portion to generate the same size as that of D5 and then uses a channel decoder. Output

On the contrary, when the rate matching value is positive, that is, when the coding blocks are repeated, the repeated bits are summed to generate the same size as that of D5 and then output to the channel decoder. As a result, when the receiver recognizes the rate matching value transmitted by the transmitter, the receiver can operate correctly. In addition, the HSDPA notifies the base station and the user terminal of the transport block set (TBS), the number of codes (NC), and the coding rate from the base station to the user terminal at every transmission time interval so that the base station and the user terminal can calculate the same rate matching value. Doing.

However, in the current communication system using the HSDPA method, the message exchange and TFRI ID allocation method previously required for HSDPA call setup are not implemented, and the plurality of information, that is, MCS level information and code information (code info) are not implemented. ), With TBS size information. By transmitting information such as TCH ID information and the like as reverse control information, there is a problem that many bits are used to transmit the reverse control information, thereby reducing the efficiency of resources.

Accordingly, an object of the present invention is to provide an apparatus and method for transmitting and receiving transmission format and resource related information for user data in a communication system using a fast forward packet access scheme.

Another object of the present invention is to provide an apparatus and method for reducing the amount of control information transmitted over a common control channel in a communication system using a high speed forward packet access scheme.

It is still another object of the present invention to provide an apparatus and method for performing differential channel coding according to an amount of information transmitted through a transport format resource information field in a communication system using a fast forward packet access scheme.

The present invention for achieving the above object; In a communication system using a fast forward packet access method, code information used by a user terminal for a fast forward packet access call and transmission format resource information for the user terminal are transmitted through different fields of a specific channel, respectively. In the method for transmitting and receiving a format resource set, the base station has a modulation and coding scheme level supported by the user terminal and a transport block set size corresponding to the modulation and coding scheme level supported by the user terminal for the user terminal. Determining a transport format resource set, comparing the size of the determined transport format resource set with a size of a field for transmitting the transport format resource information, the size of the transport format resource set and the transport format resource information The transmission format corresponding to the result of the field size comparison And a block coding scheme to the original set, characterized in that it comprises the step of determining.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that in the following description, only parts necessary for understanding the operation according to the present invention will be described, and descriptions of other parts will be omitted so as not to distract from the gist of the present invention.

6 is a diagram illustrating a signal flow for transmitting a transport format and resource related information in a communication system using a fast forward packet access scheme according to an embodiment of the present invention.

6, a user terminal (UE: User Element, hereinafter referred to as "UE"), a base station (Node B), a radio network controller (RNC: referred to as "RNC") and The signal flow for establishing a High Speed Downlink Packet Access (HSDPA) call between Core Networks (CNs, hereinafter referred to as " CNs ") is shown. In addition, the part shown in oval in FIG. 6 means a protocol entity for transmitting and receiving a message. Types of information to be included in the illustrated messages are shown in Table 2 below, and only information to be newly added or modified for the HSDPA is indicated. In addition, the Refernce area of Table 2 below shows references for obtaining information on the entire list of IE.

Next, the process of setting up the HSDPA call by the UE will be described with reference to FIG. 6 and Table 2. FIG.

First, when the UE enters a cell, the UE acquires necessary system information (SI) through a cell selection process and transmits a Radio Resource Control (RRC) CONNECTION REQUEST message (step 601). The cell selection process may be performed by synchronizing with a corresponding cell using a common pilot channel (CPICH: Common PI CHannel) and a first control channel (PCCPCH) of a random cell, and using a random access channel (RACH). Random Access CHannel, hereinafter referred to as "RACH") means a process of acquiring information. A UE identity IE is inserted into the RRC CONNECTION REQUEST message so that the RNC can determine whether the RRC connection is established to the corresponding UE. The RRC connection refers to a signaling connection through which the UE first accesses a system and transmits necessary information to a network. However, in some cases, a dedicated channel (DCH: Dedicated CHannel) for transmitting user data. ) May be included in the RRC connection.

After receiving the RRC CONNECTION REQUEST message, the RNC determines whether the RRC connection is to the corresponding UE by using the UE identity IE, and when the RRC connection is granted, the RNC sends an RRC CONNECTION SETUP message including various IEs related to the RRC connection. In step 602. The RRC CONNECTION SETUP message includes a UE identifier to be used in a common channel such as a RACH and a forward access channel (FACH). Upon receiving the message, the UE includes the UE radio access capability IE in the RRC CONNECTION SETUP COMPLETE message and transmits it to the RNC (step 603). Typically, the UE radio access capability IE includes a physical channel capability item and an item indicating whether turbo codung is supported. However, in the embodiment of the present invention, modulation schemes supported by the corresponding UE are added to the IE, and this information will be defined as modulation capability. For example, if any UE supports QPSK and 16QAM, QPSK and 16 QAM are specified in the Modulation Capability item of the UE radio access capability IE. In addition, if the corresponding UE supports the HSDPA, the physical channel capability item includes information on the number of OVSF codes that the UE can process at one time, and this information will be defined as multi code capability. Upon receiving the RRC CONNECTION SETUP COMPLETE message, the RNC stores the multi code capability and modulation capability items in a variable called UE HSDPA capability. As described above, if the UE which has established the RRC connection transmits a message requesting new call establishment to the CN (step 604). Here, the message for requesting a new call establishment by the UE to the DN is transmitted in a Non Access Stratum (NAS) message IE of an RRC message called INITIAL DIRECT TRANSFER. The NAS message may include information necessary for the CN to process the call, for example, information related to the quality of the call. Accordingly, as the UE sends an INITIAL DIRECT TRANSFER message to the RNC, the RNC transforms the message into a RANAP message called INITIAL UE MESSAGE and transmits the message to the CN (step 605). Upon receiving the INITIAL UE MESSAGE, the CN determines a Radio Access Bearer (RAB) parameter based on the quality related information of the NAS message IE included in the INITIAL UE MESSAGE message. The RAB parameter may include a maximum bit rate of the corresponding call, a Guranteed bit rate, and a traffic class indicating the type of call. The traffic class includes a conversational class, a streaming class, an interactive class, a background class, and the like, and the conversational class and the streaming class have real-time characteristics, and a multimedia service including voice communication is mainly used. Data service is mainly applied. Therefore, if the call requested by the UE in step 604 and 605 is a data service, the CN will apply an interactive or background class to the RAB parameter, and if it is a voice service, it will apply a conversational class. The CN having determined the RAB parameters as described above transmits a RAB ASSIGNMENT REQUEST message to the RNC (step 606). The RNC determines which channel to configure for the UE based on the RAB parameter included in the RAB ASSIGNMENT REQUEST message. If the RAB parameter indicates that the call to be set up is a high-speed data service, i.e., if the traffic class of the RAB parameter is extremely high as the interactive or background class, the RNC may set the call as an HSDPA call. In this case, the following actions are taken.

First, the RNC determines a UE supported MCS level set and a UE supported code space with reference to a UE HSDPA capability of a corresponding UE. Here, the UE supported MCS level set is a set of values obtained by taking only MCS levels supported by the UE itself from among MCS levels supported by a cell in which the UE is located. For example, a cell supported MCS level set, which is a set of MCS levels supported by a cell to which the UE belongs, is represented by [{MCS 1 = QPSK & 1/3 turbo coding}, {MCS 2 = QPSK & 2/3 turbo coding}, {MCS 3 = 16QAM & 1/3 turbo coding}, {MCS 4 = 16QAM & 2/3 turbo coding}, {MCS 5 = 64QAM & 2/3 turbo coding}]. If the modulation capability is QPSK and 16QAM, the UE supported MCS level set is [{MCS 1 = QPSK & 1/3 turbo coding}, {MCS 2 = QPSK & 2/3 turbo coding}, {MCS 3 = 16QAM & 1/3) turbo coding}, {MCS 4 = 16QAM & 2/3 turbo coding}]. As a result, generalizing a rule for determining the UE supported MCS level set is as follows. After extracting the MCS levels that match the modulation scheme supported by the UE from the cell supported MCS level set, list the MCS levels in the order of modulation order and coding rate in small order, and assign a level index to each of them. The configuration is complete.

In addition, the cell supported MCS level set is managed by the RNC for each cell managed by the RNC. The cell supported MCS level set is created in the cell configuration step and stored in the cell HSDPA context. The cell code space is stored in the cell HSDPA context in addition to the cell supported MCS level set. The cell code space is represented by starting and ending points of OVSF codes used for the HS-PDSCH in the corresponding cell. If any cell uses 10 codes from (16,6) to (16,15) for the HS-PDSCH, the cell code space is [(16,6), (16,15)]. In addition to the cell HSDPA context, OVSF code information allocated to SHCCH is also stored. For example, if four SHCCHs are configured in a cell, [SHCCH 0 = (256,32), SHCCH 1 = (256,64), and SHCCH 2 = (256), which correspond to the identifier of each SHCCH and the OVSF code. 96), and SHCCH 3 = (256, 128)].

After receiving the RAB ASSIGNMENT REQUEST message and determining the UE supported MCS level set, the RNC transmits a RADIO LINK SETUP REQUEST message to the Node B managing the corresponding cell (step 607). In the embodiment of the present invention, the HS-DSCH info IE is newly defined in the RADIO LINK SETUP REQUEST message, and the HS-DSCH info IE includes a UE supported MCS level set and a multi code capability of the UE. Node B configures a Transport Format Resource Set (TFRS) using the UE supported MCS level set and the multi-code capability of the UE, and then sends a RADIO LINK SETUP RESPONSE message to complete the TFRS configuration for the UE. Notify that the operation is completed (step 608). Meanwhile, as another embodiment, in step 603 instead of step 607, a transport format resource set may be configured using the UE supported MCS level set from which the RNC is received and the multi code capability of the UE.

Since the method for configuring the TFRS will be described below, a detailed description thereof will be omitted. Upon receiving the RADIO LINK SETUP RESPONSE, the RNC transmits a RADIO BEARER SETUP message to the UE (step 609). At this time, the HS-PDSCH info IE is newly added to the RADIO LINK SETUP RESPONSE message. The HS-PDSCH info includes UE supported MCS level set, cell code space, SHCCH identifier and OVSF code information. After receiving the RADIO BEARER SETUP message, the UE configures the TFRS and sends a RADIO BEARER SETUP COMPLETE message to notify the RNC that it is ready to receive the HS-DSCH (step 610). The RNC sends a RAB ASSIGNMENT RESPONSE message to the CN, notifying that call setup is completed (step 611).

A summary of the HSDPA call setup process described with reference to FIG. 6 is as follows.

The UE informs the RNC of the multi code capability and modulation capability using the RRC CONNECTION SETUP COMPLETE message, and the RNC stores this information in the UE HSDPA context. The RNC also stores the cell supported MCS level set and cell code space in the cell HSDPA context during the initial cell configuration. When the RNC receives a request for establishing a random call from the CN, the RNC determines whether to set the call as an HSDPA call based on the RAB parameters for the call, and if the call is an HSDPA call, the UE supports MCS level using the UE HSDPA context and the cell HSDPA context. produces a set Then, the RNC delivers the UE supported MCS level set and multi code capability to Node B, and Node B receiving the UE supported MCS level set and multi code capability configures TFRS using these informations. In addition, the RNC delivers UE supported MCS level set, cell code space, and SHCCH related information to the UE, and when the UE configures TFRS using the received UE supported MCS level set and cell code space, the HSDPA communication is ready. Is done.

Next, a scheme in which each of the UE and the Node B configures the TFRS will be described. In order to configure the TFRS, the present invention describes a number of embodiments, which are the same in the following basic operations. Through the HSDPA call setup process described with reference to FIG. 6, the UE and the Node B recognize the same UE supported MCS level set, cell code space, and multi code capability. The TFRI field consists of a combination of MCS level information, code information, and TBS size information. In the following description, each of the information included in the TFRI field, that is, MCS level information, code information, and TBS size information, will be referred to as a "component". Each of the components will be referred to as a tree as shown in FIG. It is configured in the form of a tree to generate an initial transport format resource set (ITFRS: Initial TFRS, hereinafter referred to as "ITFRS"). The ITFRS means a collection of all initial transport format resource related information (ITFRI).

Next, the ITFRS structure will be described with reference to FIG. 7.

7 is a diagram illustrating an initial transport format resource set structure according to an embodiment of the present invention.

In FIG. 7, three components exist, component X is level 1, component Y is level 2, and component Z is level 3. As shown in FIG. 7, the level is increased from the left to the right in the ITFRS tree structure, and level 1 means the highest element in the code, and level 2 means the next higher element. The method of configuring the ITFRS can be generalized as follows.

First, when components to be used for ITFRS configuration are determined, a level is assigned to each component. Subcomponents belonging to a certain level n are placed on the left side of the ITFRS tree rather than level n-1, and all subcomponents of level n-1 are placed per subcomponent of level n. The above process is completed for all levels, and if an identifier is assigned from top to bottom in the ITFRS tree structure, the ITFRS configuration is completed. When the ITFRS is configured, Node B configures the TFRS by removing ITFRIs not to be used, and then informs the UEs of ITFRIs not to be used.

Next, a first ITFRS configuration method for configuring the ITFRS using MCS level (component_MCS) information, code information (component_code), and transport block set size (component_TBS) information as components to be used for configuring the ITFRS will be described. Let's do it.

1. How to configure the first ITFRS

The subcomponents of Component_MCS are composed of elements of a UE supported MCS level set. For example, any UE supported MCS level set may be {{MCS 1 = QPSK & 1/3 turbo coding}, {MCS 2 = QPSK & 2/3 turbo coding}, {MCS 3 = 16QAM & 1/3 turbo coding} , {MCS 4 = 16QAM & 2/3 turbo coding}], the subcomponents of component_MCS become MCS 1, MCS 2, MCS 3, and MCS 4. In addition, the subcomponents of Component_code are calculated using the method of patent application P2001-55572, which includes 10 OVSF codes having a spreading factor of 16 (SF = 16), that is, on the OVSF code tree (16,6) to When (16,15) codes are used for the HS-DSCH, code assignment information corresponds to logical identifiers as shown in Table 3 below.                     

In Table 3, SP indicates a start point (SP) of an assigned code, and NC indicates a number of codes (NC). As shown in Table 3, the code identifier table constructed using the cell code space will be defined as a "code identifier base table." If the multi code capability of the UE is equal to the number of codes of the cell code space, the items of the code identifier base table correspond to the subcomponents of component_code. If the multi code capability of the UE is smaller than the number of codes in the cell code space, the code identifier base table shown in Table 3 is transformed into a code identifier modification table based on the following rules. If the multi code capability value is n, the code identifier modification table is constructed by removing columns from the table whose NC items in the code identifier base table are larger than n and assigning them again from top to bottom. Table 4 shows a code identifier modification table when the multi code capability is 5.

In Table 3, that is, when the multi code capability is greater than or equal to the cell code space, the number of subcomponents of the component_code is 55, and as shown in Table 3, the identifiers between 0 and 54 are distinguished. However, in Table 4, namely, when the multi code capability is smaller than the cell code space, the number of subcomponents of component_code is 40, and is divided by an identifier between 0 and 39. Therefore, the UE and the Node B can configure the same code identifier base table or code identifier modification table using cell code space and multi code capability information.

Next, the subcomponents of Component_TBS reduce the amount of information required to inform the TBS size in such a manner that only the difference from the predetermined reference value is not the absolute value of the TBS size. The reference value is defined as the capacities of the physical channels corresponding to the MCS level and the number of codes, and the density of the reference value is set to the number of codes in the third embodiment in P2001-61543, but in the present invention, it is flexible in some cases. Set it. As shown in FIG. 5, when the MCS level and the number of codes are determined at any time, the maximum value of the TBS size that can be transmitted can be calculated.

If the maximum transmittable TBS size corresponding to an arbitrary MCS level and the number of codes is TBS (number of codes, MCS level), the reference values at the code number x and the MCS level y may be set to TBS (x-1, y). . The purpose of the reference value is that, when Node B informs the UE of the difference between the TBS size actually used and the reference value, the UE calculates the reference value using the MCS level and the number of codes at an arbitrary time, and the reference value and the offset Summing up to get the TBS size. The reference value corresponds one-to-one with the capacity of a physical channel corresponding to an arbitrary MCS level and the number of codes. Table 5 shows the capacity of the physical channel according to the MCS level and the number of codes. Ten OVSF codes with a spreading factor of 16 were allocated for the HS-DSCH, and the UE supported MCS level set was [{MCS 1 = QPSK & 1/3 turbo coding}, {MCS 2 = QPSK & 2/3 turbo coding}, { Assume a situation consisting of five MCS levels of MCS 3 = 16QAM & 1/2 turbo coding}, {MCS 4 = 16QAM & 3/4 turbo coding}, and {MCS 5 = 64QAM & 2/3 turbo coding}]. Numbers are in bits.

When the physical channel capacity for an arbitrary code number x and MCS level y is PCC (x, y), the numerical values of Table 5 are calculated according to Equation 4 below.

PCC (x, y) = (chip rate / SF) * Time slots in a TTI * MO_y * CR_y * x

In Equation 4, the chip rate is 2560, the diffusion coefficient SF is 16, and the number of timeslots in one TTI is 3, and MO_y and CR_y denote modulation orders and coding rates of MCS level y. The modulation order is 2 for QPSK, 4 for 16QAM, and 6 for 64QAM. Using Equation 5 below, TBS (x, y) can be calculated using PCC (x, y).

TBS (x, y) = RD {[PCC (x, y)-OH] / TB_size}

In Equation 5, OH means the size of overhead, and is calculated as the sum of the MAC-hs header size added at 302 and the CRC size added at 303. TB_size refers to the size of TB, and one value per transport channel is determined by the RNC during call setup, and the Node B and UE are transmitted through a RADIO LINK SETUP REQUEST message (607) and a RADIO BEARER SETUP message (609). You will be notified. RD {} is a function that rounds an arbitrary real number to an integer.

Table 6 below shows a reference table in which the values of TBS (x, y) were calculated using the values in Table 5. In this case, OH is assumed to be 30 bits and TB_size is assumed to be 100 bits.

When the UE receives a TB size (TB_size), a MAC-hs header size and a CRC size, and a UE supported MCS level set through a RADIO BEARER SETUP message 609, the UE refers to its multi-code capability as shown in Table 6 above. Configure the same TBS table. First, the code count item of the table is set from 1 to the code capability value, the MCS level item is set to the values of the UE supported MCS level set, and TBS (x, y) is calculated to prepare a TBS table as shown in Table 6 above. When the Node B receives the TB size (TB_size), MAC-hs header size and CRC size, UE supported MCS level set, and UE multi code capability through a RADIO LINK SETUP REQUEST message 607, the TBS table is received like the UE. Can be configured.                     

In addition, when a state corresponding to an arbitrary code number x and an arbitrary MCS level y is S (x, y), Node B has an TBS table at S (x, y) as shown in Equation 6 below. ) Value.

Offset = ATBS (x, y) -TBS (x-1, y)

In Equation 6, the ATBS is the number of actual TBs to be transmitted at that time. The Node B notifies the UE of the offset value through TFRI, and the UE calculates ATBS using the TBS table and the offset.

Subcomponents of Component_TBS are basically determined by the difference between the largest PCC and the maximum TBS corresponding to the next largest PCC. Referring to Table 6 as an example, since 19 subcomponents, which are the difference between TBS (5,5) and TBS (5,4), are required, a relationship as shown in Equation 7 below is established.

Component_TBS = [1,2,3,, TBS_MAX_VARIATION],

In Equation 7, TBS_MAX_VARIATION = TBS (code_MAX, MCS_MAX) -TBS (code_MAX-1, MCS_MAX), and Code_MAX is a multi code capability that is a number of codes that can be simultaneously processed by any UE, and the MCS_MAX is The highest MCS level among the UE supported MCS level sets.

In the above, components for configuring the ITFRS, that is, component_MCS, component_code, and component_TBS, have been described. Next, a method of configuring a first TFRS for configuring a TFRS using each of the above described components will be described.

1. How to configure the first TFRS

In the first TFRS configuration method, component_MCS and component_code are classified as hard components and component_TBS is classified as soft components. Here, the hard component means a component in which all subcomponents should be included in the TFRS, and the soft component means a component in which some subcomponents may be excluded from the TFRS.

First, Node B determines the maximum transport format resource set size (TFRS_MAX_SIZE) based on the size of the TFRI field of the SHCCH. The TFRS_MAX_SIZE is obtained as shown in Equation 8 below.

In Equation 8, TFRI_FIELD_SIZE means the size of a TFRI field. For example, if the TFRI field size, that is, TFRI_FIELD_SIZE is 10 bits, TFRS_MAX_SIZE is 1024.

Next, the Node B obtains the number of subcomponents belonging to component_MCS (component_MCS_SIZE) and the number of subcomponents belonging to component_code (component_code_SIZE). Here, Component_MCS_SIZE is equal to the number of elements belonging to the UE supported MCS level set, and component_code_SIZE is equal to the number of columns in the code identifier modification table. The Node B then multiplies the component_MCS_SIZE and component_code_SIZE to find hard component_SIZE and obtains soft component_SIZE. This is represented by Equation 9 below.

Hard component_SIZE = component_MCS_SIZE * component_code_SIZE

Available soft component_SIZE = TFRS_MAX_SIZE / hard component_SIZE

In addition, when there are a plurality of soft components, the Node B determines the number of soft components as follows. For example, if there are soft component_x, soft component_y, and soft_component_z, the sizes of the soft components are determined to be soft component_x_SIZE * soft component_y_SIZE * soft component_z_SIZE <= Available soft component_SIZE. When the size of each soft component is determined, a sub component ratio of each soft component is determined as follows.

When the subcomponent of any soft component_x is [x_1, x_2, x_3,, x_n], assuming that the sub component ratio of each subcomponent is [x_r_1, x_r_2, x_r_3,, x_r_n], x_r_1 + x_r_2 + x_r_3 ++ x_r_n = soft component_x_SIZE, and 0 <x_r_1, x_r_2, x_r_3, x_r_n <= 1, where the sub component ratio means the probability that the sub component exists in the TFRS tree configured up to the level of the component. This will be described in detail with reference to FIG. 8.

8 is a diagram illustrating an initial transport format resource information tree structure according to a subcomponent ratio according to another embodiment of the present invention.

Referring to FIG. 8, the ITFRI is classified by level, such as "ITFRI_level_sequential integer". In other words, ITFRI_3_2 means the second ITFRI of the ITFRS configured by considering only the level 3 component. As shown in FIG. 8, three components, x, y, and z, are x are hard components, and y and z are soft components. In addition, the subcomponents of the soft components are defined as component_x = [1,2], component_y = [1,2,3], component_z = [1,2], and the TFRS_MAX_SIZE is defined for convenience of description. In this case, Available soft component_SIZE considering the hard component is 4.5. When the Soft_component_y_SIZE is 2.5 and the Soft_component_z_SIZE is 1.8, the product of the Soft_component_y_SIZE and Soft_component_z_SIZE is equal to 4.5, which is the Available soft component_SIZE. Therefore, when the sub component ratio of the soft component is calculated based on the corresponding soft component_SIZE, it is expressed as Equation 10 below.

Sub component ratio_y = [1,1,0.5], sub component ratio_z = [1,0.8]

In Equation 10, y_1 and y_2 exist for all cases of level 1, which is a higher level, and y_3 exists with a probability of 0.5. In FIG. 8, ITFRI_2_3 corresponding to y_3 exists, but ITFRI_2_6 does not exist. Similarly z_1 always exists, but ITFRI_3_4 corresponding to z_2 does not exist. Next, a method of configuring the TFRS in the above manner will be described.

First, Node B determines TFRS_MAX_SIZE, configures components, and divides each component into hard components (hard component_1, ..., hard component_n) and soft components (soft component_1, ..., soft component_m). After determining the level of components, only the hard components are used to configure ITFRS_n. ITFRS_n means ITFRS configured using components up to level n. For convenience of explanation, it is assumed that the level is determined as follows.

Level 1 = hard component_1, ..., Level n = hard component_n, Level n + 1 = soft component_1, ..., Level n + m = soft component_m

Then, Node B calculates hard component_SIZE (Hard component_SIZE = hard component_size_1 * hard component_size_2 * hard component_size_3 * ·· * hard component_size_n), and again calculates Available soft component_SIZE (Available soft component_SIZE = TFRS_MAX_SIZE / Hard component_SIZE), Soft component_SIZEs are determined based on the calculated Available soft component_SIZE (Soft component_1_SIZE * ·· * soft component_m_SIZE <= Available soft component_SIZE). Here, the soft component_SIZEs are determined by referring to the importance and original size of each soft component. For example, if the number of subcomponents of soft component_x is 3, the number of subcomponents of soft component_y is 5, and the available soft component_SIZE is 12, if soft component_x is more important, soft component_x_SIZE is 3 and soft component_y_SIZE is 4 Will be set to

The base station then determines the subcomponents of each of the soft components. At this time, the important subcomponents are selected from all the subcomponents. Again, the base station determines the sub component ratio of the selected subcomponents, and also determines the sub component ratio according to the importance of the subcomponent. As an example, Soft component_x including K subcomponents will be described below.

X_r_1 + x_r_2 + + x_r_k = soft component_x_SIZE

The base station then configures ITFRS_n + 1 using the highest level soft component. And storing ITFRI_n + 1s excluded from the configured ITFRS_n + 1 according to the detected sub component ratio. At this time, the ITFRIs to be excluded can be excluded based on a certain rule. When determining the ITFRI to be excluded by the above rule, the rule is stored and applied to the same. Thereafter, the base station configures ITFRS_n + 2 using a next level soft component and stores ITFRI_n + 2 excluded from ITFRS_n + 2 according to the sub component ratio. At this time, the same rule is applied to determine the ITFRI to be excluded from the ITFRS_n + 2. In this way, the ITFRI is configured up to the soft component. As a result, when the ITFRS_n + m + 1 is completed, the base station stores the ITFRS_n + m + 1 as a TFRS.

The Node B that completed the TFRS as described above includes the following information, that is, the type of the hard component, the type of the soft component, the soft component_SIZE and the type of each subcomponent, the subcomponent ratio, and the removed ITFRI_n + 1s. .., ITFRI_n + m + 1s or removal rules are included in the RADIO LINK SETUP RESPONSE message and forwarded to the RNC. Then, the RNC includes the information received from the base station in a RADIO BEARER SETUP message and delivers it to the UE, whereby the UE repeats the process using the information received from the RNC to configure the same TFRS.

Next, an example according to an embodiment of the present invention will be described.

There is component_MCS, component_code, component_TBS between any cell and the UE. The component_MCS, component_code, component_TBS consists of the following subcomponents, and component_MCS and component_code are hard components. Here, Component_MCS = [{MCS 1 = QPSK & 1/3 turbo coding}, {MCS 2 = QPSK & 2/3 turbo coding}, {MCS 3 = 16QAM & 1/3 turbo coding}, {MCS 4 = 16QAM & 2/3 turbo coding}], and the meaning of each component_code = [0,1,, 39] is the same as in Table 4 described above. When the TFRS_MAX_SIZE is 1024, the available soft component_SIZE is 6.4 (= 1024). / (40 * 4)). In addition, since only one soft component exists, component_TBS_SIZE becomes 6.4, and the subcomponents of Component_TBS are set to [1,2,3,4,5,6,7] and the sub component ratio is [1,1,1,0.4]. , 1,1,1]. At this time, the subcomponents of the component_TBS have relative values and have the same meaning as in Equation 11 below in S (x, y).

Variation (x, y) = TBS (x, y) -TBS (x-1, y)

Sub component n = INT [(n / component_TBS_SIZE) * variation (x, y)]

In Equation 11, INT [X] means an integer closest to any real number X. Subcomponent n in S (x, y) means the same as the offset value obtained by dividing variation (x, y) by component_TBS_SIZE equal to n times its value. This will be described with reference to FIG. 9.

9 is a diagram illustrating a TBS component structure according to another embodiment of the present invention.

Referring to FIG. 9, if component_TBS is set to [1,2,3] in S (x, y), TBS (x, y) is 43 and TBS (x-1, y) is 30, variation ( x, y) becomes 13. Therefore, subcomponent 1 actually means INT [(1/3) * 13] = 4, and subcomponent 2 actually means INT [(2/3) * 13] = 9. The actual meaning is the offset value INT [(3/3) * 13] = 13. If any Node B needs to transmit 36 TBs to any UE in S (x, y), the Node B transmits a TFRI including sub component 2, and the difference between the actual number of TBs and the offset value , TB repeated 3 times. When the UE receives the sub component 2, the UE recognizes and processes the number of TBs of the received HS-DSCH data as 39, and the repeated TBs are discarded in a radio link control (RLC) layer. Is described in the first embodiment of P2001-61543 filed by the present applicant.

TFRS in Node B using the RNC when the RNC determines the TFRS using the UE supported MCS level set and the multi code capability received in step 603, or the UE supported MCS level set and the multi code capability received in step 607. When the Node B determines that subcomponents of all components are determined, B sets Component_MCS to level 1, component_code to level 2, component_TBS to level 3, and configures ITFRS_3 as shown in Table 7 below.

Table 7 above is ITFRS_3 including all levels, and since all include 1120 elements, 96 ITFRS_3, which is a difference from TFRS_MAX_SIZE, should be removed. In this case, since the sub component ratio of sub component 4 is 0.4 and the remaining sub component ratios are all 1, after removing the ITFRI_3 corresponding to the sub component 4, if the identifiers of the remaining ITFRIs are specified in order again, the TFRS as shown in Table 8 is shown. It is composed.

That is, when Node B determines the TFRS using the UE supported MCS level set and the multi code capability received in step 607, Node B stores the identifiers of ITFRI_3 removed from ITFRS_3 in a variable called DELETED_ITFRI_3, and RADIO LINK SETUP RESPONSE Include it in the message and pass it to RNC. At this time, the ITFRI_3 may be made according to a predetermined elimination rule. For example, subcomponent 4 of ITFRI_3 belonging to ITFRI_2 in which (ITFRI_2) MOD5 becomes 2 and 0 may be removed. In this case, the Node B stores the rule in the DELETED_ITFRI_3 variable and delivers the rule to the RNC.                     

In another embodiment, when the RNC determines the TFRS in the RNC using the UE supported MCS level set and the multi code capability received in step 603, the RNC is configured to include TFRI as well as Component_MCS, component_code, and component_TBS information. Deliver DELETED_ITFRI_3 directly to Node B and UE. In this case, the identifiers of the ITFRI_3 selected from the ITFRS_3 may be stored in a predetermined variable instead of the DELETED_ITFRI_3 and transmitted.

Next, operation of Node B constituting the TFRS will be described with reference to FIG. 12.

12 is a flowchart illustrating a process of configuring a transport format resource set in a base station according to another embodiment of the present invention.

12, first, in step 1201, the Node B receiving the RADIO LINK SETUP REQUEST message from the RNC recognizes information required for TFRS configuration and proceeds to step 1202. In step 1202, the Node B configures component_MCS using a UE supported MCS level set of information required for configuring the TFRS, and then proceeds to step 1203. In step 1203, the Node B configures a code identifier base table using a cell code space. If the multi code capability of the UE is smaller than the size of the cell code space, the Node B configures a code identifier modification table and proceeds to step 1204. Here, when the multi code capability and the cell code space are the same, the code identifier base table and the code identifier modification table are the same. In addition, the Node B configures component_code by mapping the items of the cell identifier modification table to subcomponents of component_code and proceeds to step 1204. In step 1204, the Node B sets the level of the component_MCS and component_code, configures ITFRS_2, and then proceeds to step 1205. In step 1205, the Node B calculates the available soft component_SIZE using the hard component_SIZE value, and then proceeds to step 1206. Since only one soft component is component_TBS, the available soft component_SIZE is equal to component_TBS_SIZE.

In step 1206, the Node B determines the subcomponents of the component_TBS and proceeds to step 1207. In step 1207, the Node B sets the respective sub component ratios, and then proceeds to step 1208. In step 1208, the Node B configures ITFRS_3, removes ITFRI_3 according to the sub component ratio set in step 1207, reallocates identifiers to the remaining ITFRI_3, and completes TFRS configuration. Here, identifiers or removal rules of the removed ITFRI_3 are stored in the DELETED_ITFRI_3. In step 1209, the UE inserts information necessary for configuring the TFRS in the RADIO LINK SETUP RESPONSE message and transmits the information to the RNC.

Next, an operation of the UE configuring the TFRS will be described with reference to FIG. 13.

13 is a flowchart illustrating a process of configuring a transport format resource set in a user terminal according to another embodiment of the present invention.

Referring to FIG. 13, in step 1301, when a UE receives a RADIO BEARER SETUP message from an RNC, the UE recognizes information related to TFRS configuration and proceeds to step 1302. In step 1302, the UE configures Component_MCS and proceeds to step 1303. In step 1303, the UE configures Component_code, proceeds to step 1304, configures ITFRS_2, and then proceeds to step 1305. In step 1305, the UE configures component_TBS and proceeds to step 1306 to configure ITFRS_3 and proceeds to step 1307. In step 1307, the UE configures the TFRS using the information of DELETED_ITFRS_3. In step 1308, the UE sends a RADIO BEARER SETUP COMPLETE message to notify the RNC that the TFRS configuration has been completed successfully.

Next, a common control channel transmitter structure will be described with reference to FIG. 10.

10 is a diagram illustrating a common control channel transmitter structure according to another embodiment of the present invention.

Before transmitting user data through the HS-DSCH, the Node B uses MCS level information (MCS) to apply code information of the number of codes to be applied through the code allocator 1006 through the MCS control unit 1005. info), and transmits the number information (TBS size) of the transport block to be transmitted through the rate matching controller 1004 to the TFRI generation unit 1007. In this case, the code allocator allocates the codes in consideration of the situation of the user buffer 1001, the rate matching controller determines the number of transport blocks to be transmitted according to the instruction of the user buffer, and the MCS controller controls the backward control transmitted by the corresponding UE. The MCS level is determined in consideration of the channel quality information of the reverse control information processing unit 1002 that processes the information. The TFRI generator 1007 determines the TFRI using the received code info, MCS info, and TBS size information. The TFRI generation unit stores the TFRS configured by the above-described method, code info is information about an OVSF code that a UE to receive the HS-DSCH should receive, and MCS info is an MCS level allocated to the UE to receive the HS-DSCH. The TBS size information indicates the actual number of transport blocks transmitted through the HS-DSCH. The TFRI generator should allocate the TFRI corresponding to the subcomponent of component_TBS corresponding to the offset value closest to the TBS size information, and transfers the difference between the TBS size information and the offset to 1401 and 1401 repeats the transport block. Do it. It also passes the offset value to 1407, which causes 1407 to perform the appropriate rate matching operation. The CRC field of FIG. 2 is added to the TFRI stream after the CRC operation is performed in the CRC calculator. The bit stream to which the CRC field is added is delivered to the multiplexer 1009. The multiplexer 1009 transforms the HARQ info delivered from the HARQ controller 1003 and the bit stream delivered in 1008 into a single bit stream conforming to the slot format of FIG. 2. The single bit stream is spread with a predetermined spreading code at spreader 1010 and mixed with a scrambling code at scrambler 1011. Thereafter, the summer 1012 is summed with data of other channels, modulated by the modulator 1013, converted into an RF band signal by the RF unit 1014, and then transmitted through the antenna 1015.

11 is a diagram illustrating a common control channel receiver structure of a communication system using a conventional high speed forward packet access scheme.

The RF band signal is converted by the antenna 1101 into a baseband signal in the RF unit 1102, demodulated by the demodulator 1103, and then demixed in the descrambler 1104, and then despreader 1105. Despread. The despread signal is separated into a TFRI field, a CRC field and a HARQ field in the demultiplexer 1106. The TFRI field and the CRC field are separated into a code info, an MCS level, and a TBS size info in the TFRI interpreter 1108 through a CRC operation in the CRC calculator 1107. HARQ info separated from the demultiplexer 1106 is transmitted to the HARQ controller.

14 illustrates a fast forward common channel transmitter physical layer channel structure according to another embodiment of the present invention.

Referring to FIG. 14, except for the transport block repetition step 1401 and the rate matching step 1407, the same as FIG. 3 described above. In step 1401, Node B repeats as much as the value delivered by the TFRI generator 1007. In operation 1407, the rate matching unit executes rate matching using the offset value transmitted from the TFRI generator as follows. In this case, it is assumed that the situation is S (x, y).

RM = PCC (x, y)-{[TBS (x-1, y) + offset] * TB_size + MAC_hs header_size + CRC_size}

Hereinafter, since the remaining operations are the same as those described with reference to FIG. 3, detailed descriptions thereof will be omitted.

In the above, the case where the TFRI includes the MCS level, code information, and TBS information as a component has been described as an example. Hereinafter, a method of effectively configuring a TFRS when the component of the TFRI includes a modulation scheme, code information, and TBS information will be described.

As described above, the MCS level is a combination of a modulation scheme and a coding scheme. Therefore, when Node B delivers Modulation Scheme, Code Info, and TBS information to the UE through TFRI, the UE determines the coding rate based on the modulation scheme, code information, and TBS information received from Node B. It becomes possible to detect. This will be described in detail as follows.

First, for convenience of description, a method of including MCS, code info, and TBS in a TFRI is defined as "Rule 1," and a method of including MS, codeinfo, and TBS in the TFRI is defined as "Rule 2." That is, the rule 1 has been described above, and the rule 2 will now be described.

In Rule 2, the channel coding unit 305 performs primary channel coding according to a predetermined value, and the rate matching unit 306 performs additional coding. For example, under certain circumstances, Node B uses a rate matching in the rate matching unit 305 when the given PCC is 1000 symbols and the size of the primary channel coded TB in the channel coding unit 305 is 300 symbols. The 300 symbols are repeated to generate 1000 symbols. Before transmitting the rate-matched data, Node B informs the UE of the MS, Code info, and TBS through TFRI of SHCCH, and the UE calculates symbol PCC through the MS and Code info received from Node B. The coding rate is calculated by dividing the PCC by TBS.

This will be described with reference to FIG. 15.                     

15 is a diagram illustrating the amount of data of respective processes in a transmitter physical layer channel structure of a fast forward packet access communication system according to another embodiment of the present invention.

Before describing FIG. 15, the D values illustrated in FIG. 15 have the same values as the D values described with reference to FIG. 3. In FIG. 15, D3 denotes the number of bits after concatenating TBs and attaching a header and a CRC. The D3 is converted into a positive symbol multiplied by the inverse of the MCR (Mother Coding Rate) while passing through a channel coding unit. To D5. The MCR is used when a UE or a Node B cannot support all coding rates, so that one channel rate is used to perform primary channel coding, and as necessary, iterate or puncture to match the final coding rate. Means the coding rate of the primary coding. In general, the use of 1/3 coding rate is considered for MCR. The D5 is repeated or punctured by the rate matching unit so as to exactly match the PCC D7 to be D6. At this time, the ratio of D6 and D5 will be defined as "a second coding rate (hereinafter, referred to as" 2CR ") for convenience. As a result, the final coding rate of the user data D3 in bits becomes TCR (Total Coding Rate), which is a product of MCR and 2CR, and the value obtained by dividing D3 by TCR matches the size of the PCC.

As described above, if the UE knows the number of TBs (TBS size), TB size (TB size), header and CRC size, and PCC size at any point in time, the TCR can be calculated and the MCR is fixed. As a result, the value of 2CR can be calculated. The 2CR value serves as a basis for calculating the number of symbols to be repeated or punctured when performing reverse rate matching in the receiver. For example, if 2CR is 3.5, reverse rate matching may be performed by 3.5 times to obtain a size D3 of a symbol to be input by the channel decoder.

As a result, in Rule 2, the Node B and the UE transmit and receive MS, Code info, and TBS size information through the TFRI field so as to take necessary actions in the actual physical layer. The TBS size corresponds to the ratio between D5 and D6 in FIG. 3 in a one-to-one manner so that the physical layer of the receiver performs the rate matching operation appropriately. Of course, as currently considered in the standardization process for the communication system using the high-speed forward packet access method may be considered a method of mapping the absolute value of the number of TB to the TBS size information, as described above Since the TBS size is highly variable depending on the TB size, the number of codes, and the MS, there is a problem in that the size of the TBS_component becomes very large when the absolute value of the TBS size is used as a subcomponent of the TBS_component.

Therefore, Rule 2 of the present invention also proposes a method of reducing the TBS_component size by using a relative value of the TBS size as a subcomponent of the TBS_component.

Rule 2 limits the range of the TCR so that the Node B and the UE calculate a reference value of the TBS size according to a given number of MSs and codes, and reduce the size of the component_TBS by transmitting and receiving only the difference value from the reference value. This will be described in detail as follows.                     

First, if the TBS transmitted during a certain TTI is converted into symbol units, it is represented by Equation 12 below.

D6 = (TB size * TBS size + Header Size + CRC size) * 1 / MCR * 1 / 2CR

D7 = NC * MO * (Chip Rate / SF) * 3 = PCC (MO, NC)

In Equation 12, D7 denotes a capacity of a physical channel under a given situation, and the capacity of the physical channel is a variable of MO and NC. Since D6 and D7 in Equation 12 are the same, 2CR is expressed as Equation 13 below.

2CR = (TB size * TBS size + Header Size + CRC size) / [MCR * PCC (MO, NC)]

In Equation 13, the TBS size is represented by Equation 14 below.

TBS size = [2CR * MCR * PCC (MO, NC)-(Header Size + CRC size)] / TB size

Since all variables except 2CR in the right side of Equation 14 are given in advance, if the range of 2CR is determined in advance, the range of TBS size, TBS (x, y) can be determined in any S (x, y). have. S (x, y) means any situation given an MO of x and an NC of y.

When defining TBS (x, y) in any S (x, y) as follows: TBS_MIN (x, y) <= TBS (x, y) <= TBS_MAX (x, y) TBS_MIN (x, y) and TBS_MAX (x, y) are represented by Equation 15 below.                     

TBS_MIN (x, y) = RD {[2CR_MIN * MCR * PCC (MO, NC)-(Header Size + CRC size)] / TB size}

TBS_MAX (x, y) = RD {[2CR_MAX * MCR * PCC (MO, NC)-(Header Size + CRC size)] / TB size}

In Equation 15, 2CR_MIN and 2CR_MAX mean a minimum value and a maximum value of 2CR predefined in an arbitrary HSDPA call setup process.

Eventually, the UE and the Node B exchange the minimum value and the maximum value of 2CR when setting up the HSDPA call, and set TBS_MIN (x, y) as a reference value in an arbitrary situation S (x, y), and through TFRI of SHCCH. Only the offset needs to be transmitted and received.

Signal flows for supporting the rule 2 are the same as the signal flows described with reference to FIG. 6, except that the IE included in some messages is changed as follows.

In FIG. 6, the signal flows from steps 601 to 606 are equally applied to rule 2, but differently from step 607. Referring to this, the HS-DSCH information IE of the RADIO LINK SETUP REQUEST message includes the UE supported MS set, the multi code capability of the UE and the coding rate range of the corresponding call. Here, the UE supported MS set has the same value as the modulation capability included in the UE radio access capability IE of the RRC CONNECTION SETUP COMPLETE message, and the multi code capability has the same value as the information included in the IE of the message. As described above, the coding rate range may include a maximum value (2CR_MAX) and a minimum value (2CR_MIN) of the 2CR, or a maximum value (TCR_MAX) and a minimum value (TCR_MIN) of the TCR. The coding rate range may be determined as a suitable value as a simulation value for the channel environment, and a process of setting the value itself will not be described in detail herein. The coding rate range may be given different values according to the type of MS. For example, 1/6 <= TCR <= 1/3 in QPSK, 1/3 <= TCR <= 2/3, 64 QAM in 16QAM. May predefine using only 2/3 <= TCR <= 5/6. In this case, if TCR or 2CR corresponding to each MS in each S (x, y) is represented as TCR_x or 2CR_x, TBS_MIN (x, y) and TBS_MAX (x, y) in S (x, y) are as follows. Induced.

TBS_MIN (x, y) = RD {[2CR_x_MIN * MCR * PCC (x, y)-(Header Size + CRC size)] / TB size}

TBS_MAX (x, y) = RD {[2CR_x_MAX * MCR * PCC (x, y)-(Header Size + CRC size)] / TB size}

When the Node B receives the RADIO LINK SETUP REQUEST message, the Node B sets the elements of the UE supported MS set as subcomponents of component_MS and sets the subcomponent of component_code using multi code capability information. At this time, the component_code configuration is the same as that described in Rule 1. In addition, a subcomponent of component_TBS is configured using a coding rate range. Since the subcomponent setting process of the component_TBS will be described below, a detailed description thereof will be omitted. When the configuration of the subcomponents for each of the components is completed, ITFRS and TFRS are configured according to the method proposed in Rule 1. Whether a component is a hard component or a soft component can be adaptively determined according to channel conditions. In addition, the subcomponent ratio of the subcomponents of the soft components can also be adaptively determined according to the situation. For example, component_MS and component_code may be set as hard components and component_TBS may be set as soft components. When the TFRS configuration is completed, Node B sends a RADIO LINK SETUP RESPONSE message to the RNC. Here, the RADIO LINK SETUP RESPONSE message is used in the same form in both rule 1 and rule 2.

Upon receiving the RADIO LINK SETUP RESPONSE message, the RNC transmits a RADIO BEARER SETUP message to the UE. Here, the HS-DSCH information IE of the RADIO BEARER SETUP message includes cell code space information, UE supported MS set, coding rate range information, hard component type, soft component type, soft component size and sub component ratio. do. The UE configures component_code using its multi code capability and cell code space information, configures component_MS using UE supported MS set, and configures component_TBS using coding rate range information. After completing the configuration of the components, after configuring the TFRS using the type of hard component, the type of soft component, the size of the soft component and the sub component ratio, and transmits a RADIO BEARER SETUP COMPLETE message to the RNC.

Next, subcomponents of component_TBS will be described.

As described above, in any situation S (x, y), TBS_MIN (x, y) and TBS_MAX (x, y) are represented by Equation 16 below.

TBS_MIN (x, y) = RD {[2CR_x_MIN * MCR * PCC (x, y)-(Header Size + CRC size)] / TB size}

TBS_MAX (x, y) = RD {[2CR_x_MAX * MCR * PCC (x, y)-(Header Size + CRC size)] / TB size}

The UE and the Node B calculate TBS_MIN (x, y) and TBS_MAX (x, y) values for all S (x, y) according to Equation (16). For example, UE supported MS set is QPSK, 16QAM, multi code capability is 10, header and CRC sum is 30 bits, TB size is 100 bits, MCR is 1/3, coding rate range is 1/6 <= TCR_QPSK Given <= 1/3, 1/3 <= TCR_16QAM <= 2/3, TBS_MIN (x, y) and TBS_MAX (x, y) are as shown in Table 9 below.                     

In the above example, the subcomponent of component_TBS is a set of integers ranging from 0 to the difference between TBS_MIN (x, y) and TBS_MAX (x, y) in S (x, y), as shown in Table 10 below. Unlike the component_TBS described above, in rule 2, subcomponents change according to S (x, y). Then, subcomponents of Component_MS are defined as [QPSK = 1, 16 QAM = 2].                     

In Table 10, left sets of subcomponent items are actual TBS sizes, and right sets are subcomponents corresponding to offset values.

And in the above example ITFRS is shown in Table 11.

When the component_code is 1, the number of codes is 10. The component_code is the same as the situation of S (1, 10). Therefore, 17 subcomponents are present in the corresponding component_TBS, that is, from 0 to 16. When Component_code is 2, it means that the code number is 9, and thus, there are 15 subcomponents from 0 to 14 in the corresponding component_TBS. Thus, after first configuring ITFRS_2 using hard components up to level 2, referring to S (x, y) corresponding to each ITFRI_2, subcomponents of component_TBS for each ITFRI_2 correspond to ITFRS_3 as shown in Table 11 above. . In the above example, since the size of ITFRS_3 is 1967, it may be necessary to change the size of the soft component component_TBS. In this case, as in Rule 1 of the present invention, subcomponents of less importance may be excluded from the ITFRS as necessary, and the excluded ITFRIs may be delivered to the RNC.

As a result, Rule 2 of the present invention described above relates to a method of configuring a TBS_component when an MS other than an MCS ultimately corresponds to a TFRI, and also changes the size of the TBS_component when assuming a TBS_component as a soft component. It is about a method. The other parts are the same in Rule 1 and Rule 2, except that the types of information included in information (HS-DSCH info IE) previously transmitted / received by the RNC, Node B, and UE to configure the TFRS are as described above. There are different points as described in.

The third embodiment of the present invention relates to a case in which TFRS is transmitted when code info is not included in a TFRI field.

The TFRS is transmitted without including the code info in the TFRI field to enable rapid despreading. A channel structure for transmitting the TFRI field without including the code info in the TFRI field will be described with reference to FIG. 16.

16 is a diagram illustrating a common control channel structure according to another embodiment of the present invention.                     

Referring to FIG. 16, a code info is arranged in a separate field on the SHCCH for rapid despreading. According to the structure of transmitting the code info in a separate field, a third embodiment of the present invention is provided. Example is applied. Each of the fields of the SHCCH shown in FIG. 16, that is, the size of the code info field, the TFRI field, the CRC field, and the HARQ information fields, that is, the number of transmission bits, is 6 bits in the code info field. Consider the case of allocating 4 bits (4 bits) to the TFRI field. Even if the code info is allocated to an independent field, when the TBS is included in a component of the TFRS, the code info and the TBS information have a close relationship with each other. Therefore, in the third embodiment of the present invention, the code info is defined as "separate hard component (hereinafter, referred to as" separate hard component "). The separate hard component is always assigned a higher level than a hard component and is transmitted through an independent field. Temporary Transport Format Resource Set (TTFRS) (hereinafter referred to as " TTFRS ") is described above in the same manner as in the embodiments described above using the separate hard component, hard component, and soft component. It is configured as shown in Table 12 in the same manner as the examples.                     

In Table 12, the TTFRS has a form similar to the ITFRS described above, but sets the TTFRI instead of the ITFRI. The ITFRI is assigned an identifier above and below the ITFRS, but the TTFRS is assigned an identifier for each separate hard component. The situation assumed in Table 12 is the same as the situation assumed in Table 11 of the second embodiment. In the third embodiment of the present invention, component_MS, component_code, and component_TBS are configured in the same manner as in the second embodiment of the present invention described above. If it is necessary to configure other components, such as a Transport Channel ID, the components that need to be configured together are also components. In the third embodiment of the present invention, since the component_code is set as a separated hard component, a level 1 is assigned to the component_code, the component_MS which is a hard component is set to level 2, and the component_TBS which is a soft component is set to level 3.

Here, once again the level assignment rules commonly applied to all embodiments of the present invention will be described. In the presence of any number of components, each component is classified into separate hard components, hard components, and soft components, and the respective components, that is, separate hard components, hard components, and soft components, respectively Defined as separate hard component set, hard component set, and soft component set. Level 1 is assigned to the most important component in a separate hard component set, then assigns levels to hard separate components sequentially, then assigns levels to all separate hard components, and the same process applies to hard component sets and soft component sets. Iteratively assigns levels to each of the components. In the third embodiment of the present invention, since the separate hard component is set to component_code, the hard component to component_MS, and the soft component to component_TBS, level 1 is assigned to component_code, level 2 to component_MS, and level 3 to component_TBS. When the TTFRS configuration is completed as shown in Table 12, the soft component_SIZE is determined in consideration of TFRS_SIZE.

As shown in Table 12, the TTFRI has a meaning associated with subcomponents of a separate hard component. For example, when subcomponent of component_code, which is a separate hard component, is 1, TTFRI_3 1 means that MS is QPSK and TBS is 1, and subcomponent 1 of TBS_component is TBS_MIN (1,10). ), So the TBS size is 15. As another example, when the subcomponent of component_code is 55, TTFRI_3 0 means that MS is QPSK and TBS size is 1, which is the same value as TBS_MIN (1,1). Therefore, as shown in Table 12, the number of TTFRIs can be generated variably according to the value of component_code. For example, when component_code is 1, the number of TTFRIs is 82, when component_code is 2, the number of TTFRIs is 73, and when component_code is 55, the number of TTFRIs is 9.

Therefore, when TFRS is configured in TTFRS to transmit TTFRIs having a variable size according to the situation through a TFRI field having a fixed size, that is, a fixed number of transmission bits, the TFRS is configured according to the following rules.

이 된 다. 그리고, 상기 separate hard component의 subcomponent 당 TTFRI의 개수를 N_TTFRI_subcomponent로 정의하기로 한다. 예를 들어 subcomponent 23의 TTFRI의 개수는 N_TTFRI_23이다. separate hard component의 subcomponent 당 TTFRS를 TTFRS_subcomponent로 명명한다. 예를 들어 TTFRS_54는 상기 표 12에서 음영 처리된 Level 1에 해당하는 부분이 된다. 상기 separate hard component의 subcomponent가 [1, ,x]까지 x개 존재할 경우, 상기 1에서 x까지 N_TTFRI들을 산출한다. 그리고 상기 산출한 N_TTFRI들을 상기 TFRI_SIZE와 비교한다. 상기 비교 결과 상기 TFRI_SIZE를 초과하는 N_TTFRI가 존재할 경우, 상기 TFRI_SIZE와 상기 N_TTFRI간의 차를 구하고, 상기 구한 차이만큼의 TTFRI들을 해당 TTFRS에서 제거한다. 예를 들어 N_TTFRI_1이 83이고, TFRI_SIZE가 64일 경우, 상기 TTFRS_1에서 채널 상황에 적정하게 TTFRI들을 19개 제거하여 TFRI_SIZE를 상기 64에 일치시킨다. When the number of transmission bits of the TFRI field is n bits, the TFRS_SIZE is

This becomes The number of TTFRIs per subcomponent of the separate hard component is defined as N_TTFRI_subcomponent. For example, the number of TTFRIs of subcomponent 23 is N_TTFRI_23. TTFRS per subcomponent of a separate hard component is named TTFRS_subcomponent. For example, TTFRS_54 becomes a portion corresponding to Level 1 shaded in Table 12. When x subcomponents of the separate hard component exist up to [1,, x], N_TTFRIs are calculated from 1 to x. The calculated N_TTFRIs are compared with the TFRI_SIZE. If there is an N_TTFRI exceeding the TFRI_SIZE as a result of the comparison, a difference between the TFRI_SIZE and the N_TTFRI is obtained and TTFRIs corresponding to the obtained difference are removed from the TTFRS. For example, when N_TTFRI_1 is 83 and TFRI_SIZE is 64, 19 TTFRIs are removed from the TTFRS_1 according to the channel condition so that TFRI_SIZE matches 64.

The removed TTFRIs are stored in a variable called TTFRI_DELETED in Node B as described above in other embodiments of the present invention, and are later notified to the RNC through a RADIO CONNECTION SETUP RESPONSE message. The variable TTFRI_DELETED is stored with the TTFRS_subcomponent to which the removed TTFRI belongs and is then notified to the UE. For example, if TTFRI 2, 10, 18 has been removed from TTFRS_2, the information that the TTFRI 2, 10, 18 has been removed is stored in one set in the TTFRI_DELETED variable as TTFRS_2 = [2,10,18]. In addition, in the third embodiment of the present invention, the removal rule may be stored in TTFRI_DELETED like the other embodiments of the present invention. In this case, the TTFRS_subcomponent is also stored together. When all N_TTFRIs are equal to or smaller than TFRI_SIZE through the above removal process, if the identifiers of remaining TTFRIs are reassigned from the upper side to the lower side on the TTFRS, the configuration of the TFRS is completed.

Next, a third embodiment of the present invention described above will be described as an example.

이 된다. 그리고 상기 Component_MS_SIZE가 2이므로, available soft component_SIZE는 8이다. 상기 예에서 component_TBS가 유일한 soft component이므로, component_TBS를 조정해서 N_TTFRI가 TFRI_SIZE보다 동일하거나 작게 구성해야 한다. 하기 표 13에 component_code의 subcomponent당 N_TTFRI를 나타내었다. First, the process of determining Component_code as a separate hard component, component_MS as a hard component, component_TBS as a soft component, and determining the subcomponent of each of the components in the manner according to the third embodiment of the present invention is performed. TTFRS equal to 12 is configured. Assuming that 4 bits are allocated to the TFRI field, the TFRI_SIZE is

Becomes And since the Component_MS_SIZE is 2, available soft component_SIZE is 8. Since component_TBS is the only soft component in the above example, N_TTFRI must be configured to be equal to or smaller than TFRI_SIZE by adjusting component_TBS. Table 13 shows N_TTFRI per subcomponent of component_code.

In Table 13, if the N_TTFRI is larger than 16, there are 45 TTFRS_1 to TTFRS_45, and the corresponding TTFRSs should be adjusted to 16. Node B decides which TTFRIs to remove, removes the maritime TTFRI according to the decision, and stores the removed TTFRIs in the variable TTFRI_DELETED. However, if there are more TTFRIs to be removed from the generated TTFRI than the remaining TTFRIs, the remaining TTFRIs are stored in a new variable TTFRI_STAY, and the RNC is notified later.

Meanwhile, as described above, component_TBS corresponds to S (x, y). That is, arbitrary subcomponents of Component_TBS belonging to the same S (x, y) have the same meaning. When the component_code corresponds to S (x, y), it is shown in Table 14 below.

As shown in Table 14, since subcomponent 2 and subcomponent 3 of component_code correspond to the same S (x, y), the same TFRI can be used. That is, the subcomponent 2 means 9 code sets between C (16,6) and C (16,14) in the code space, and the subcomponent 3 means C (16,7) ~ in the code space. Since 9 means a code set between C (16,15), the two subcomponents have only the same number of positions in the code space. In Table 14, parameter S (9,1) refers to a case in which MS is used as a QPSK scheme and 9 codes are used, and parameter S (9,2) uses MS as a 16QAM scheme. Since 9 codes are used, the same corresponds to both the subcomponent 2 and the subcomponent 3.                     

As shown in Table 14, after configuring subcomponents of the separate hard component into sets corresponding to the same S (x, y), that is, sets of the same number of codes, the same TTFRI is applied to the TTFRS of the subcomponents belonging to the same set. If you remove it, you can reduce the size of TTFRI_DELETED or TTFRI_STAY. That is, the TTFRIs removed for each sub component must be stored separately. However, when the above-described method is used, only the removed or left TTFRIs can be stored for each code number. After adjusting the length of the N_TTFRI_SIZE to TFRI_SIZE in the same manner as described above, if a new identifier is sequentially assigned to each TTFRI, the configuration of the TTFRS is completed.

As described above, the component_TBS has a variable size depending on the number of codes. Therefore, N_TTFRI_SIZE is different depending on the number of codes used, that is, code info. Therefore, when the N_TTFRI_SIZE is larger than the number of transmission bits that can be transmitted through the TFRI field, a method of generating TFRS by grouping the subcomponents by subcomponents having the same code number and removing the subcomponents according to TFRI_SIZE. On the contrary, in the case of subcomponents whose N_TFRI_SIZE is smaller than TFRI_SIZE, that is, in case of subcomponents having bits smaller than the number of transmission bits that can be transmitted through the TFRI field, there is a problem in that the capacity of a given TFRI field cannot be efficiently used. For example, when the TFRI is 4 bits, as described above, the subcomponents up to 46 to 55 have N_TTFRI_SIZE of 7, so that the TFRS can be transmitted using only 3 bits. Therefore, the remaining 1 bit other than the 3 bits used for the actual TFRS transmission does not use the given capacity without meaning even though the actual data can be transmitted.

On the other hand, block coding (hereinafter, referred to as "block coding") may be applied to the TFRI field. In this case, if all bits allocated to the TFRI field are m bits and the size of the TFRI field is n bit, the TFRI field Can be (m, n) block coding. For example, if the SF of the SHCCH is 256, one TTI is composed of 60 bits. If 20 bits are the size allocated to the TFRI field and the size of the TFRI field is 4 bits, the TFRI is (20,4) block coded and transmitted. Therefore, subcomponents whose N_TFRI_SIZE is smaller than TFRI_SIZE can be prevented from wasting the physical channel capacity by using block coding corresponding to N_TFRI_SIZE. Then, the transmission on the actual physical channel as described above will be described in more detail.

First, N_TTFRI_SIZE_n, which is the size of the nth subcomponent of the hard separate component, is converted into the number of bits as shown in Equation 17 below.

NB_TTFRS_n = RU [log2 (N_TTFRI_SIZE_n)]

After calculating NB_TTFRS for all subcomponents of the hard separate component using Equation 17, subcomponents whose NB_TTFRS is smaller than NB_TFRI (where "NB_TTFRS" is the number of bits used for TFRI) are grouped by NB_TTFRS as follows. Store it in the NB_TTFRS set.

NB_TTFRS set = [(NB_TTFRS 1: subcomponents), (NB_TTFRS 2: subcomponents)]

In the above example, subcomponents 46 to 55 are configured as one set, and the corresponding NB_TTFRS has a value of 3. The Node B and the UE support a plurality of block coding schemes corresponding to the physical channel capacities allocated to the TFRI field, and store the input unit of each block coding scheme in the block coding input set as follows.

Block coding input set = [block coding input 1, block coding input 2,]

For example, if any Node B and the UE support the (20, 4) and (20, 3) block coding scheme, the block coding input set becomes [3, 4].

Node B configures the TFRS, determines the TFRI at any point in time, and transmits the determined TFRI through SHCCH, and applies block coding to the TFRI that matches the block coding input that is greater than or equal to NB_TTFRS of the subcomponent to which the TFRI belongs. do. For example, if TFRI 12 of subcomponent 6 is selected at any point in time, Node B recognizes that the block coding input corresponding to NB_TTFRS of subcomponent 6 is 4, and transmits TFRI using (20, 4) block coding. As illustrated in FIG. 16, the UE may recognize a subcomponent to which a TFRI belongs by using a value of a code info field. When the block coding input is determined using the NB_TTFRS of the subcomponent, the TFRI is decoded using a block coding scheme corresponding to the block coding input.

Next, a structure of a common control channel transmitter for performing a function in the third embodiment of the present invention will be described with reference to FIG. 17. FIG.                     

FIG. 17 illustrates a common control channel transmitter structure corresponding to the common control channel structure of FIG. 16.

Referring to FIG. 17, first, before transmitting user data through the HS-DSCH, the Node B transmits code information about the number of codes to be used for transmitting the user data through the code allocator 1706. The MS information (MS info) to be applied to the user data transmission through the MS control unit 1705, and the number information (TBS size) of the transport block (TB) to be used for the user data transmission through the rate matching control unit 1704 ) Are output to the TFRI generator 1707, respectively. In this case, the code allocator 1706 allocates a code to be used to transmit the user data in consideration of the situation of the user data buffered in the user buffer 1701, and the rate matching controller 1704 is configured to the user buffer 1701. The number of transport blocks to be transmitted, that is, TBS_SIZE, is determined according to an instruction of the, and the MS control unit 1705 outputs from the reverse control information processing unit 1702 to process the reverse control information received from the UE to which the user data is to be transmitted. The MS level is determined by considering the channel quality information.

The TFRI generation unit 1707 determines TFRI using the code info, MS info, and TBS size information output from the code assignment unit 1706, the MS control unit 1705, and the rate matching control unit 1704, respectively. . That is, the TFRI generation unit 1707 stores the TFRS configured in the same manner as described in the third embodiment of the present invention, and the code info relates to the OVSF code that the UE to receive the HS-DSCH should receive. The information, MS info, refers to the MS level allocated to the UE to receive the HS-DSCH, and the TBS size information refers to the actual number of transport blocks transmitted through the HS-DSCH. The TFRI generation unit 1707 needs to allocate a TFRI corresponding to a sub component of component_TBS that is most similar to the TBS size information, and shows the difference between the TBS size information and the offset actually indicated by the subcomponent of cmponent_TBS corresponding to the selected TFRI. In step 1401 of the fast forward common channel transmitter physical layer channel structure shown in FIG. 14, the transport block is repeated in step 1401. In addition, the subcomponent value of component_TBS is transferred to step 1407 of FIG. 14 to perform a proper rate matching operation in step 1407.

Thus, the TFRI generator 1707 generates a TFRI and outputs it to the CRC calculator 1708. The CRC calculator 1708 adds a CRC bit to the TFRI output from the TFRI generator 1707. The CRC bit is output to a multiplexer (MUX) 1709. The CRC calculator 1708 outputs the TFRI output from the TFRI generator 1707 to the switching unit 1716. The switching unit 1716 applies a block coding scheme to the TFRI bit stream transmitted from the CRC calculator 1708 by using code info output from the code allocator 1706. A block coder (1717-1, .1717-n) for performing a corresponding block coding scheme on the TFRI bit stream output from the CRC operation unit 1708 according to the determined block coding scheme. Switch to output. In addition, when the TFRI bit stream received from the CRC calculator 1708 is smaller than an input value of the determined block coder, the switching unit 1716 pads 0 or 1 to be equal to the input value of the determined block coder. )do. For example, if the determined block coder is a (20,3) block coder and the TFRI bitstream is 2 bits, the switching unit 1716 should make the TFRI bit stream 3 bits. That is, since the TFRI bit stream is two bits, the switching unit 1716 must make an input of the (20,3) block coder by padding two bits of the TFRI bit stream with one or zero bits. In FIG. 17, for convenience of description, it is assumed that the switching unit 1716 outputs the TFRI bit stream to block coder 1 (1717-1).

Then, the block coder 1 1701-1 performs the block coding using the corresponding block coding method using the TFRI bit stream transmitted from the switching unit 1716 and outputs the block coder to the multiplexer 1709. The multiplexer 1709 may include HARQ info output from the HARQ controller 1703 and CRC bits output from the CRC calculator 1708, code info output from the code allocator 1706, and the block coder 11717. The TFRI bit stream outputted by -1) is multiplexed into a single bit stream matching the slot format shown in FIG. 16 and output to the spreader 1710. The spreader 1710 spreads a single bit stream output from the multiplexer 1709, that is, one SHCCH TTI with a predetermined spreading code and then outputs it to a scrambler 1711. The scrambler 1711 scrambles the signal output from the spreader 1710 with a predetermined scrambling code, and then outputs the scrambler 1711 to the summer 1712. The summer 1712 sums the SHCCH signal output from the scrambler 1711 and other channel data and outputs the sum data to the modulator 1713. The modulator 1713 modulates the signal output from the summer 1712 in a preset manner and outputs the modulated signal to the RF unit 1714. The RF unit 1714 wirelessly processes the signal output from the modulator 1713 and transmits the signal over the air through the antenna 1715.

17 illustrates a structure of a transmitter for transmitting a SHCCH signal in a manner according to a third embodiment of the present invention. Next, a receiver structure corresponding to the structure of the transmitter of FIG. 17 will be described with reference to FIG. .

FIG. 18 is a diagram illustrating a common control channel receiver structure corresponding to the common control channel transmitter structure of FIG. 17.

Referring to FIG. 18, the RF band signal received through the antenna 1801 is converted into a baseband signal by the RF unit 1802 and output to the demodulator 1803. The demodulator 1803 demodulates the signal output from the RF unit 1802 in a demodulation method corresponding to the modulation scheme transmitted from the SHCCH transmitter, and then outputs the demodulated signal to the inverse scrambler 1804. The descrambler 1804 descrambles the signal output from the demodulator 1803 with the scrambling code applied by the SHCCH transmitter, and then outputs the descrambler 1805 to the despreader 1805. The despreader 1805 despreads the signal output from the descrambler 1804 with a spreading code applied by the SHCCH transmitter and outputs the despreader to a demultiplexer (DEMUX) 1806. The demultiplexer 1806 splits the signal output from the despreader 1805 into a code info field, a TFRI field, a CRC field, and a HARQ field. Herein, the Code info field is transmitted to the code information receiver 1809 and the switching unit 1813, the TFRI field is transferred to the switching unit 1813, the CRC field is transferred to the CRC calculator 1807, and the HARQ field. Is transmitted to the HARQ control unit 1812. The switching unit 1813 determines which block decoder 1814-1,... 1181-n to transfer the received TFRI to, based on the received code info. Deliver the received TFRI. In FIG. 18, for convenience of description, it will be assumed that the switching unit 1813 transfers the information to the block decoder 1 1814-1. Then, the block decoder 1 1814-1 decodes the signal output from the switching unit 1813 using the corresponding block decoding method, and then transfers the signal to the CRC calculator 1807. Meanwhile, the CRC calculator 1807 performs a CRC operation by serially connecting the CRC field transmitted by the demultiplexer 1806 and the TFRI bit stream transmitted by the block decoder 1 1814-1, and performs the CRC operation. If no error occurs, the TFRI bitstream is transferred to the TFRI analysis unit 1808. The TFRI interpreter 1808 interprets the information of the received TFRI by using the TFRS in advance and transmits the information to the MS controller 1810 and the rate matching controller 1811, respectively.

A third embodiment of the present invention has been described with reference to FIGS. 16 to 18, and a fourth embodiment of the present invention will be described next.

First, prior to describing the fourth embodiment of the present invention, information included in the SHCCH includes code info, MS, TBS size, coding information, HARQ info, and the like as described above. The HARQ info includes HARQ channel number, Redundancy Version, New / Continue indicator, and the like. Herein, the roles of the respective information of the HARQ info, that is, the HARQ channel number, the redundancy version, and the New / Continue indicator will be described. The HARQ channel number means the HARQ channel number of the coded block transmitted during any TTI. Here, the HARQ channel represents a correlation between arbitrary coded blocks, and whether or not the coded blocks are soft combined with each other according to their HARQ channel number. For example, if an error occurs while transmitting a coded block with a HARQ channel number of "1", when the Node B retransmits the coded block with the error, the HARQ assigned to the coded block with the error occurs. By assigning the same channel number as the channel number, the UE can soft combine the retransmitted coded block and the initial transmit coded block. The redundancy version indicates how many times the coded block is a retransmitted coded block, and indicates a specific method of soft combining for the coded blocks in an IR (Incremental Redundancy) scheme. In addition, the New / Continue indicator (retransmission indicator, hereinafter referred to as “N / C”) indicates whether the corresponding coded block is initial transmission or retransmission.

Meanwhile, the information included in the SHCCH may include a transport channel ID (TCH_ID) although description thereof is omitted in the first embodiment, the second embodiment, and the third embodiment of the present invention. In a conventional voice data-oriented mobile communication system, a transport channel refers to a technique for processing user data in a physical layer. For example, if a transport channel with TCH ID 1 is specified to use QPSK for MS, 1/3 convolutional coding for channel coding, and 320 bits for transport block size, then the sender may The user data having the TCH ID is subjected to physical layer processing according to the above rule, and the receiver performs the physical layer processing according to the above rule for the user data having the same TCH ID. However, the size of the transport block is unique in that the MS and the channel coding scheme are not defined as a single scheme and differentiated by the TCH ID in the HSDPA system that varies according to channel conditions. That is, if the TCH ID is defined as a component of the TFRI, the component_TCH ID may be newly defined. In this case, the TFRS is composed of component_MS, component_TCH ID, and component_TBS. Since the Component_TCH ID has a different transport block size for each subcomponent, the component_TCH ID should be defined as a higher component than the component_TBS, and different component_TBS is configured for each subcomponent of the component_TCH ID. When the component_TCH ID is included, since the TFRS configuration is configured in the same manner as in the third embodiment of the present invention, a detailed description thereof will be omitted.

After all, in the fourth embodiment of the present invention, when any coded block is retransmitted, a TBS size equal to the TBS size of the initially transmitted coded block is used and retransmitted in consideration of the same TCH ID. The coded block relates to a method of transmitting TFRS in a manner of reducing the size of the TFRI field by not including TBS size information and TCH ID information.

In general, the N / C is represented by 1 bit information. The SHCCH structure applied to the third embodiment of the present invention has a form in which code info is allocated to a separate field and transmitted before the TFRI field as described in FIG. 16. In the SHCCH structure applied to the fourth embodiment of the present invention, as shown in FIG. 19, the TFRI field is transferred by allocating not only the code info but also N / C in the HARQ info as a separate field such as the code info. Will be sent to. This will be described in detail with reference to FIG. 19.

19 is a diagram illustrating a common control channel structure according to another embodiment of the present invention.

Referring to FIG. 19, first, (a) illustrated in FIG. 19 has a structure in which code info and the N / C are allocated as separate fields before the TFRI field and transmitted. Here, component_code is inserted into the code info field as a separate hard component, and 1-bit information indicating whether the corresponding coded block is N, that is, initial transmission or C, that is, retransmission, is inserted into N / C. When the N / C field is N, a TFRI including a combination of component_MS, component_TBS, component_TCH ID, and other necessary information is inserted in the TFRI field according to the TFRS configuration method described in the third embodiment of the present invention. When the N / C field is C, TFRI is inserted into the TFRI field as a TFRS composed of components excluding component_TBS and component_TCH ID. Since the TFRS configuration for the TFRI excluding the component_TBS and the component_TCH ID will be described below, detailed description thereof will be omitted. The HARQ info is the same as the conventional HSDPA scheme, but differs only in that the N / C information included in the HARQ info is transmitted in a separate field as described above.                     

In (a) of FIG. 19, the SHCCH structure for transmitting the code info and the N / C as separate fields has been described. Next, FIG. 19 (b) shows the MS as well as the code info and N / C. A structure of allocating the data into two separate fields is shown. That is, as shown in FIG. 19B, the component_MS of the TFRI may be divided into independent fields, and a structure of transmitting the TFRI field before the TFRI field may be considered. In the fourth embodiment of the present invention, a structure in which TFRS is transmitted assuming a case of SHCCH structure as shown in FIG. 19 (a) will be described. The present invention is also described in the structure of FIG. 19 (b). Of course, the fourth embodiment of the same is applicable.

Next, a fourth embodiment of the present invention will be described. First, in order to apply the fourth embodiment of the present invention, a TFRS that does not include component_TBS, that is, a retransmission TFRS (TFRS_RT: TFRS_Retransmission, hereinafter referred to as "TFRS_RT") must be configured. The configuration of the TFRS_RT is as follows. First, the components to be included in the retransmission TFRI (TFRI_RT: TFRI_Retransmission, hereinafter referred to as "TFRI_RT") should be determined, and the components to be included in the TFRI_RT are included in the initial transmission TFRI (TFRI_FT: TFRI_First Transmission, hereinafter referred to as "TFRI_FT"). The other components except the component_TCH ID and component_TBS among the components, for example, if the TFRI_FT includes component_MS, component_TCH ID, and component_TBS, TFRI_RT consists of only component_MS. In this case, the TFRI_FT consists of a combination of component_MS and component_TBS, the TFRI_RT consists of only component_MS, and if necessary, the TFRI_FT consists of a combination of component_MS, component_TCH ID and component_TBS, and TFRI_RT consists of component_MS only.

As described above, after determining the components to be included in the TFRI_RT, the TTFRS is configured in the same manner as described in the third embodiment of the present invention. When there are a large number of components to be included in the TFRI_RT, the TTFRS is configured by allocating the levels of each component in the same order as when configuring the TFRS_FT, and determining the subcomponents of each component in the assigned levels. Referring again to the third embodiment of the present invention described above as an example, since there is only one component, the TTFRS consists only of component_MS, and the subcomponent becomes [1 = QPSK, 2 = 16QAM], in which case it is necessary for TFRI. The number of bits is one bit. Of course, there is only one type of component to be included in TFRI_RT as in the third embodiment of the present invention. However, even if a plurality of components are included in TFRI_RT, TFRS_RT_SIZE is always smaller than TFRS_FT_SIZE. Here, TFRS_RT_SIZE means the total size of TFRS_RT, and TFRS_FT_SIZE means the total size of TFRS_FT. In the third embodiment of the present invention, the TTFRS_FT_SIZE has a maximum size of 83 to 7 (see Table 13), and TFRS_FT_SIZE is eventually smaller than or equal to TFRI_SIZE to be 16 or 7, but TFRS_RT_SIZE is 2.

When TFRI_RT_SIZE is the number of bits allocated to TFRI_RT in the pre-channel coding step, and TFRI_FT_SIZE is the number of bits allocated to TFRI_FT in the pre-channel coding step, the channel coding of SHCCH is performed by the channel coding corresponding to TFRI_RT_SIZE and the channel coding corresponding to TFRI_FT_SIZE. When the scheme is dualized, retransmission has the advantage of more stable transmission of TFRI. That is, since TFRI_RT_SIZE is always smaller than TFRI_FT_SIZE, more powerful channel coding can be used for TFRI_RT. As described in the third embodiment of the present invention, the channel coding may be block coding or convolutional coding.

Next, the fourth embodiment of the present invention will be described as an example. For example, an OVSF code having 6 bits in the code info field, 1 bit in N / C, 6 bits in TFRI, 16 bits in CRC, and 5 bits in HARQ info, and a diffusion coefficient of 256 (SF = 256) in SHCCH It is assumed that the case is assigned. If the spreading factor is 256, the acceptable number of channel coded bits is 60 bits. There are a plurality of ways of channel coding the 34 bits which are not channel coded into 60 bits. For example, (16,7) block coding is applied to the code info and N / C fields, (20,11) block coding is applied to 11 bits of the TFRI and HARQ info, and (24,16) block coding is applied to the CRC. can do. As another example, (16,7) block coding may be applied to the code info and N / C fields, and (44,27) convolutional coding may be applied to 27 bits including TFRI / CRC / HARQ info. have. That is, when grouping bits transmitted through a plurality of fields and processing as one channel coding, if sets of channel coding units are defined as "channel coding sets", channel coding sets as shown in Table 15 may be formed. have.                     

In Table 15, the size of the channel coding set including the TFRI varies as described above depending on whether the coded block is the first transmission or retransmission. Therefore, if the coding scheme is changed according to the size of the channel coding set including the TFRI, the coding efficiency can be increased as a result. Herein, a method of changing a corresponding coding scheme according to the size of the changed coding set when the size of the channel coding set changes is as follows.

First, the Node B and the UE each include a channel encoder and a channel decoder that support coding schemes to be applied to the channel coding set. That is, when a node B and a UE are previously set to apply a block coding of a or b to an arbitrary channel coding set according to a situation, each of the Node B and the UE performs block coding on the a and b. It must have a supported channel encoder and channel decoder. For example, when "case 2" is used in Table 15, the Node B and the UE are supposed to use (34,22) block coding and (34,17) block coding for channel coding set 2. Must have both a channel encoder and a channel decoder supporting the (34, 22) block coding and a channel encoder and a channel decoder supporting the (34, 17) block coding. Similarly, when " case 1 " is used in Table 15, when using (44,27) convolutional coding and (44,22) convolutional coding for channel coding set 2, the Node B and the UE are determined as described above. A channel encoder and channel decoder supporting (44,27) convolutional coding and a channel encoder and channel decoder supporting (44,22) convolutional coding must be provided.

Here, the channel coding set in which the channel coding scheme changes according to the situation as in the channel coding set 2 of case 1 will be defined as an "adaptive channel coding set". In order to use the adaptive channel coding set, a coding scheme indicator indicating a change in the adaptive channel coding scheme of the adaptive channel coding set must be determined, and an agreement must be made between the Node B and the UE. Thus, like the channel coding set 2 of the case 1, the coding scheme indicator may be in charge of N / C. That is, if the N / C is N, (44,27) convolutional coding is applied. If the N / C is C, convolutional coding is applied to the channel coding set to perform channel coding.

Prior to transmitting the SHCCH, the Node B determines an appropriate coding scheme suitable for the adaptive channel coding set according to whether the corresponding coded block is initial transmission or retransmission, and performs channel coding according to the determined coding scheme. Done. The UE first decodes a field serving as a channel coding indicator and then decodes an adaptive channel coding set according to the result. The channel coding scheme to be used for the adaptive channel coding set is predetermined by the Node B and the UE, and both the Node B and the UE must have a channel encoder and a channel decoder supporting the channel coding scheme. If the channel coding scheme applied to the actual adaptive channel coding set is due to the size change depending on whether the TFRI field is initially transmitted or retransmitted, the channel coding schemes are determined as follows.

First, the input of the channel coding scheme used for the initial transmission is the sum of the number of bits before the fields of the adaptive channel coding set are channel coded. For example, in Table 15, if channel coding set 2 of Case 1 is an adaptive channel coding set, channel coding set 2 includes a TFRI_FT field, a CRC field, and an HARQ info field, and thus, 27 is a sum of bits applied to the fields. The bit is the input size of the channel coding scheme used for the initial transmission. On the other hand, the input of the channel coding scheme used for retransmission is equal to the sum of the number of bits before the fields are coded in the fields belonging to the adaptive channel coding set, except that the reduced bits are applied to the field in which the bits used for retransmission are reduced. . In the case of Table 15, if channel coding set 2 is an adaptive channel coding set in 1, since channel coding set 2 is composed of TFRI_RT, CRC, and HARQ info, 21 bits, which is the sum of bits applied to the fields, are used for retransmission. The input size of the channel coding scheme. That is, since the number of bits to be transmitted is reduced than when the TFRI_RT is the first transmission, the TFRI_RT is reduced from 27 bits used for the first transmission to 21 bits. And an output size of channel coding schemes used for the adaptive channel coding set is a value obtained by subtracting an output size of a channel coding scheme used for other coding sets from the total capacity of the SHCCH. In the case 1, since the total capacity of the SHCCH is 60 bits and the output size of the channel coding set 1 is 16 bits, the output size of the channel coding set 2 is 44.

Next, a structure of a common control channel transmitter performing a function in the fourth embodiment of the present invention will be described with reference to FIG. 20. FIG.

20 is a diagram illustrating a common control channel transmitter structure corresponding to the common control channel structure of FIG. 19.

Referring to FIG. 20, first, before transmitting user data through the HS-DSCH, Node B transmits code information about the number of codes to be used for transmitting the user data through the code allocator 2006. The MS information (MS info) to be applied to the user data transmission through the MS control unit 2005, and the number information (TBS size) of the transport block (TB) to be used for the user data transmission through the rate matching control unit 2004 ), And outputs the transport channel ID of the coded block to be transmitted through the transport channel controller 2018 to the TFRI generation unit 2007, respectively. In this case, the code allocator 2006 allocates a code to be used for transmitting the user data in consideration of the situation of the user data buffered in the user buffer 2001, and the rate matching controller 2004 performs the user buffer 2001. The number of transport blocks to be transmitted, that is, TBS_SIZE, is determined according to the instruction of the MS, and the MS control unit 2005 outputs from the reverse control information processor 2002 which processes the reverse control information received from the corresponding UE to which the user data is to be transmitted. The MS level is determined by considering the channel quality information. The HARQ control unit 2003 outputs HARQ information excluding N / C to the CRC calculation unit 2008 and the N / C information to the TFRI generation unit 2007.

The TFRI generation unit 2007 outputs the code assignment unit 2006, the MS control unit 2005, the rate matching control unit 2004, the HARQ control unit 2003, and the transport channel control unit 2018, respectively. TFRI is determined using code info, MS info, and TBS size information, N / C, and transport channel ID. That is, the TFRI generation unit 2007 stores TFRS_FT and TFRS_RT configured in the same manner as described in the fourth embodiment of the present invention. If N / C is N, the TFRI generation unit 2008 determines the TFRI using the TFRS_FT using the TFRS_FT and using the TFRS_RT if N / C is C. The code info is information on an OVSF code that a UE to receive the HS-DSCH should receive, the MS info is an MS level allocated to the UE to receive the HS-DSCH, and the TBS size information is transmitted through an HS-DSCH. The actual number of port blocks, and the transport channel ID means the ID of the transport block transmitted through the HS-DSCH. When using the TFRS_FT, the TFRI generation unit 2007 should allocate a TFRI corresponding to the subcomponent of component_TBS closest to the TBS size information, and the offset indicated by the subcomponent of cmponent_TBS corresponding to the TBS size information and the selected TFRI. In step 1401, the transport block is repeated in step 1401 of the fast forward common channel transmitter physical layer channel structure shown in FIG. In addition, the subcomponent value of component_TBS is transferred to step 1407 of FIG. 14 to perform a proper rate matching operation in step 1407.

Thus, the TFRI generation unit 2007 outputs the generated TFRI and N / C to the CRC operation unit 2008. Accordingly, the CRC operation unit 2008 performs CRC operation on the HARQ info, N / C, and code info. After performing the operation, the CRC bit generated according to the operation result is output to the multiplexer (MUX) 2009, and the TFRI bit stream is output to the switching unit 2016. In this case, not only the TFRI but also other information may be channel coded like the TFRI. In this case, the position of the channel encoder with respect to the other information may be located between the CRC operation unit 2008 and the multiplexer 2009. It is good if it is provided. Channel coding for the remaining fields except for the TFRI is not directly related to the fourth embodiment of the present invention, and thus, detailed description thereof will be omitted. The switching unit 2016 determines which channel coding scheme to use by referring to the size of the TFRI bit stream transferred from the CRC calculator 2008, and selects a channel coder according to the determined channel coding scheme to select the TFRI bit stream. To pass. That is, as described above, since the size of the TFRI bit stream may be generated differently, a plurality of channel coders having the size of the TFRI bit stream as an input may be provided. In FIG. 20, for example, channel coder 1 2017-1 and channel coder 2 2017-2 are provided, and channel coder 1 2017-1 includes channel coding when the coded block to be transmitted is the first transmission. The channel coder 2 (2017-2) supports a channel coding scheme when the coded block to be transmitted is retransmission. That is, when the Node B and the UE have two channel encoders and a channel decoder having the same output bits and different input bits, the switching unit 2016 is a bit stream of the TFRI delivered by the CRC operation unit 2008. The TFRI bit stream is delivered to a channel encoder having an input value equal to the number of bits of. In FIG. 20, for convenience of description, it will be assumed that the switching unit 2016 connects the TFRI bit stream to the channel coder 1 2017-1.

The channel coder 1 2017-1 performs channel coding on the TFRI bit stream received from the switching unit 2016 using a set channel coding scheme and then outputs the channel coder to the multiplexer 2009. The multiplexer 2009 multiplexes the HARQ info, the CRC bit, the code info, and the TFRI bit stream output from the channel coder 1 (2017-1) into a single bit stream of the SHCCH having the slot format shown in FIG. To the diffuser 2010. The spreader 2010 spreads a single bit stream output from the multiplexer 2009, that is, one SHCCH TTI with a predetermined spreading code and then outputs it to a scrambler 2011. The scrambler 2011 scrambles the signal output from the spreader 2010 with a predetermined scrambling code and outputs the scrambler code to the summer 2012. The summer 2012 sums up the SHCCH signal and other channel data output from the scrambler 2011 and outputs the same to the modulator 2013. The modulator 2013 modulates the signal output from the summer 2012 in a preset manner and outputs the modulated signal to the RF unit 2014. The RF unit 2014 performs radio frequency processing on the signal output from the modulator 2013 and transmits the signal over the air through the antenna 2015.

20 illustrates a transmitter structure for transmitting a SHCCH signal in a manner according to the fourth embodiment of the present invention. Next, a receiver structure corresponding to the transmitter structure of FIG. 20 will be described with reference to FIG. 21. .

21 is a diagram illustrating a common control channel receiver structure corresponding to the common control channel transmitter structure of FIG. 20.

Referring to FIG. 21, the RF band signal received through the antenna 2101 is converted into a baseband signal by the RF unit 2102 and output to the demodulator 2103. The demodulator 2103 demodulates the signal output from the RF unit 2102 by a demodulation method corresponding to the modulation method transmitted from the SHCCH transmitter side and outputs the demodulation method to the inverse scrambler 2104. The descrambler 2104 descrambles the signal output from the demodulator 2103 with the scrambling code applied by the SHCCH transmitter and outputs the descrambler 2105 to the despreader 2105. The despreader 2105 despreads the signal output from the descrambler 2104 with a spreading code applied by the SHCCH transmitter and outputs the despreader to a demultiplexer (DEMUX) 2106. The demultiplexer 2106 demultiplexes the signal output from the despreader 2105 into a code info field, an N / C field, a TFRI field, a CRC field, and a HARQ info field. The demultiplexer 2106 outputs the code info field to the code information receiver 2109, outputs the TFRI field and the N / C field to the switching unit 2113, and outputs the CRC field and code info and N / C. HARQ info including the field is output to the CRC calculator 2107. The switching unit 2113 determines which channel decoding scheme to apply to the received TFRI based on the N / C field value, and corresponds to the channel decoding schemes 2114-1 and 2114-2 according to the determined channel decoding scheme. Decide to output one of In FIG. 21, for convenience of description, it will be assumed that the switching unit 2113 transfers the TFRI to the channel decoder 1 2114-1.

The channel decoder 1 2114-1 decodes the TFRI received from the switching unit 2113 by the corresponding channel decoding method and outputs the result to the CRC calculator 2107. The CRC calculator 2107 performs a CRC operation by serially connecting the information of the fields transmitted by the demultiplexer 2106 and the TFRI bit stream transmitted by the channel decoder 1 2114-1, and performs the CRC operation error. If is not generated, the serial bit stream is output to the TFRI analysis unit 2108, the HARQ control unit 2112, and the code information receiving unit 2109. The TFRI analyzer 2108 outputs the information of the received TFRI to the MS controller 2110, the rate matching controller 2111, and the transport channel controller 2115 by using the TFRS that is previously present. In this case, the TFRI interpreter 2108 receives HARQ info and N / C from the HARQ controller 2112, and refers to TFRS_FT when N / C is N, and TFRS_RT when N / C is C. In addition, when N / C is C, the TBS and the transport channel ID are determined using the HARQ processor number among the HARQ info. Here, the TBS and the transport channel ID determination method using the HARQ processor number are as follows.

First, when the N / C of the SHCCH received at any time is N, the TFRI interpreter 2108 stores the TBS value indicated by the TFRI and the transport channel ID corresponding to the HARQ processor number of the corresponding TFRI. This process is repeated whenever a TFRI with N / C of SHCCH set to N is received. For example, if the TBS value of HARQ processor number a is n and the transport channel ID is b at any point in time, then the TBS value of HARQ processor number a is m and the transport channel ID is c at any point in time. If changed, the TFRI analysis unit 2108 stores m and c in correspondence with the HARQ processor number a. When the TFRI interpreter 2108 receives the TFRI whose N / C is C, the TBS value and the transport channel ID use the stored value as they are.

A fourth embodiment of the present invention has been described with reference to FIGS. 19 to 21, and a fifth embodiment of the present invention will be described next.

Unlike the fourth embodiment of the present invention described above, the fifth embodiment of the present invention uses a so-called blind detection method without using an N / C field as an identifier for the coding scheme of the adaptive channel coding set. It introduces and transmits TFRS. In the fifth embodiment of the present invention, the method of configuring the TFRS_FT and the TFRS_RT is the same as the fourth embodiment of the present invention, and the SHCCH structure applied to the fifth embodiment of the present invention is illustrated in FIG. As shown in the drawing, only the code info is allocated as a separate field and transmitted before the TFRI field. Of course, this has the same SHCCH structure as that described in FIG. 16, but it should be noted that a separate drawing is made to describe TFRS differentiated according to whether the coded block is initially transmitted or retransmitted.

22 illustrates a common control channel structure according to another embodiment of the present invention.

Referring to FIG. 22, a TFRI of TFRS_FT reflecting component_MS, component_TBS and other components may be used in the TFRI field, or TFRI of TFRS_RT reflecting only component_MS and other components may be used. Node B selects TFRI using TFRS_FT when any coded block is the first transmission, transmits SHCCH by block coding the TFRI field using a block coding scheme suitable for the first transmission, and then transmits the SHCCH. Send the coded block. Then, the UE receives the SHCCH, performs block decoding of the TFRI field using all block decoding schemes applicable to decoding of an adaptive block coding set, and performs CRC operation on each of the all block decoding schemes, thereby making an error. The TFRI determined to have not occurred is determined as the TFRI of the SHCCH. That is, the Node B may identify an identifier for a channel coding scheme indicating whether the coded block to be transmitted is the first transmission or the retransmission despite differentiating and transmitting the block coding scheme applied thereto depending on whether the coded block to be transmitted is the first transmission or retransmission. Since the UE does not transmit, the UE detects the TFRI by performing block decoding on all block coding schemes.

Next, a structure of a common control channel transmitter for performing a function in the fifth embodiment of the present invention will be described with reference to FIG.

FIG. 23 is a diagram illustrating a common control channel transmitter structure corresponding to the common control channel structure of FIG. 22.

Referring to FIG. 23, first, before transmitting user data through the HS-DSCH, Node B transmits code information about the number of codes to be used for transmitting the user data through the code allocator 2306. The MS information (MS info) to be applied to the user data transmission through the MS control unit 2305, the number information of the transport block (TB) to be used for the user data transmission through the rate matching control unit 2304 (TBS) size) is output to the TFRI generator 2307, respectively. In this case, the code allocator 2306 allocates a code to be used for transmitting the user data in consideration of the situation of the user data buffered in the user buffer 2301, and the rate matching controller 2304 is configured to the user buffer 2301. According to the instruction of the number of transport blocks to be transmitted, that is, TBS_SIZE is determined, the MS control unit 2305 outputs from the reverse control information processing unit 2302 for processing the reverse control information received from the UE to transmit the user data. The MS level is determined by considering the channel quality information. The HARQ controller 2303 outputs HARQ information excluding N / C to the CRC calculator 2308, and the N / C information to the TFRI generation unit 2007.

The TFRI generation unit 2307 may include code info, MS info, and TBS size information output from the code allocation unit 2306, the MS control unit 2305, the rate matching control unit 2304, and the HARQ control unit 2303, respectively. TFRI is determined using N / C. That is, the TFRI generator 2307 stores TFRS_FT and TFRS_RT configured in the same manner as described in the fourth and fifth embodiments of the present invention. If N / C is N, the TFRI generation unit 2008 determines the TFRI using the TFRS_FT using the TFRS_FT and using the TFRS_RT if N / C is C. The code info is information on an OVSF code that a UE to receive the HS-DSCH should receive, the MS info is an MS level allocated to the UE to receive the HS-DSCH, and the TBS size information is transmitted through an HS-DSCH. The actual number of port blocks. When using the TFRS_FT, the TFRI generator 2307 should allocate a TFRI corresponding to the subcomponent of component_TBS closest to the TBS size information, and the offset indicated by the subcomponent of cmponent_TBS corresponding to the TBS size information and the selected TFRI. In step 1401, the transport block is repeated in step 1401 of the fast forward common channel transmitter physical layer channel structure shown in FIG. In addition, the subcomponent value of component_TBS is transferred to step 1407 of FIG. 14 to perform a proper rate matching operation in step 1407.

Thus, the TFRI generation unit 2307 outputs the generated TFRI and N / C to the CRC operation unit 2308. Accordingly, the CRC operation unit 2308 calculates a CRC operation on the HARQ info, N / C, and code info. After performing the operation, the CRC bit generated according to the operation result is output to the multiplexer (MUX) 2309, and the TFRI bit stream is output to the switching unit 2316. In this case, not only the TFRI but also other information, channel coding may be performed like the TFRI. In this case, the position of the channel encoder with respect to the other information may be located between the CRC calculator 2308 and the multiplexer 2309. It is enough to provide. Channel coding for the other fields except for the TFRI is not directly related in the fifth embodiment of the present invention, and thus a detailed description thereof will be omitted. The switching unit 2316 determines which channel coding scheme to use by referring to the size of the TFRI bit stream transmitted from the CRC calculator 2308, and selects a channel coder according to the determined channel coding scheme to select the TFRI bit stream. To pass. That is, as described above, since the size of the TFRI bit stream may be generated differently, a plurality of channel coders having the TFRI bit stream size as an input may be provided. In FIG. 23, for example, channel coder 1 2317-1,..., And channel coder n (2017-n) are provided. That is, when the Node B and the UE have n channel encoders and channel decoders having the same output bits and different input bits, the switching unit 2316 is configured to determine the bit stream of the TFRI delivered by the CRC operation unit 2308. The TFRI bit stream is delivered to a channel encoder having an input value equal to the number of bits. In FIG. 23, for convenience of description, it is assumed that the switching unit 2316 connects the TFRI bit stream to the channel coder 1 2317-1.

The channel coder 1 2317-1 performs channel coding on the TFRI bit stream received from the switching unit 2316 using a set channel coding method, and then outputs the channel coder to the multiplexer 2309. The multiplexer 2309 multiplexes the HARQ info, the CRC bit, the code info, and the TFRI bit stream output from the channel coder 1 2317-1 into a single bit stream of the SHCCH having the slot format shown in FIG. 22. To the diffuser 2310. The spreader 2310 spreads a single bit stream output from the multiplexer 2309, that is, one SHCCH TTI with a predetermined spreading code, and outputs it to a scrambler 2311. The scrambler 2311 scrambles the signal output from the spreader 2310 with a preset scrambling code, and then outputs it to the summer 2312. The summer 2312 sums up the SHCCH signal output from the scrambler 2311 and other channel data and outputs the sum data to the modulator 2313. The modulator 2313 modulates the signal output from the adder 2312 in a preset manner and outputs the modulated signal to the RF unit 2314. The RF unit 2314 performs radio frequency processing on the signal output from the modulator 2313, and transmits the signal over the air through the antenna 2315.

In FIG. 23, a transmitter structure for transmitting a SHCCH signal in a manner according to the fifth embodiment of the present invention has been described. Next, a receiver structure corresponding to the transmitter structure of FIG. 23 will be described with reference to FIG. .

24 is a diagram illustrating a common control channel receiver structure corresponding to the common control channel transmitter structure of FIG. 23.

Referring to FIG. 24, the RF band signal received through the antenna 2401 is converted into a baseband signal by the RF unit 2402 and output to the demodulator 2403. The demodulator 2403 demodulates the signal output from the RF unit 2402 using a demodulation method corresponding to the modulation method transmitted from the SHCCH transmitter, and then outputs the demodulated signal to the inverse scrambler 2404. The descrambler 2404 descrambles the signal output from the demodulator 2403 with the scrambling code applied by the SHCCH transmitter and outputs the descrambler 2405 to the despreader 2405. The despreader 2405 despreads the signal output from the descrambler 2404 with a spreading code applied by the SHCCH transmitter and outputs the despreader to a demultiplexer (DEMUX) 2406. The demultiplexer 2406 demultiplexes the signal output from the despreader 2405 into a code info field, a TFRI field, a CRC field, and a HARQ info field.

The demultiplexer 2406 outputs the code info field to the code information receiver 2409, the TFRI field to the switching unit 2413, and the CRC field and code info and HARQ info to the CRC calculator 2407. Will output The switching unit 2413 transfers the received TFRI to all block decoders provided in the receiver, that is, block decoder 1 2414-1,..., Block decoder n 241-n. All the decoders block-decode the TFRI field received from the switching unit 2413 in each block decoding method and then output the block-decoded CRC calculator 2407.

The CRC operation unit 2407 performs a CRC operation by serially connecting the fields transmitted by the demultiplexer 2406 and the TFRI bit streams transmitted by all the block decoders, and performs an CRC operation if no error occurs as a result of the CRC operation. The bitstream is transmitted to the TFRI analyzer 2408, the HARQ controller 2412, and the code information receiver 2409. Here, since there are a plurality of block decoders and all of the TFRI streams decoded by each of the plurality of block decoders are transferred to the CRC calculator 2407, a plurality of TFRI bit streams may exist. Thus, the CRC operator 2407 combines all the TFRI bit streams with the fields delivered by the demultiplexer 2406 to perform a CRC operation to discard the TFRI field in which an error occurs. The TFRI interpreter 2408 transfers the information that the received TFRI means to the MS controller 2410 and the rate matching controller 2411 by using the TFRS which is already present. Here, the TFRI analyzer 2408 receives HARQ information from the HARQ controller 2412 and refers to TFRS_FT when the coded block corresponding to the corresponding SHCCH is the first transmission and TFRS_RT when retransmission. In case of retransmission, the TBS is determined using the HARQ processor number among the HARQ info. Here, the TBS determination method using the HARQ processor number is as follows.

First, if the N / C of the HARQ info received at any time indicates that the coded block is the first transmission, that is, N, the TFRI interpreter 2408 corresponds to the TBS value indicated by the TFRI and the HARQ processor number of the corresponding TFRI. Save it. This process is repeated whenever the TBS value changes. For example, if the TBS value of HARQ processor number a is n at any point in time, and then the TBS value of HARQ processor number a is changed to m at any point in time, the TFRI interpreter 2408 is the HARQ processor number a. Store m by mapping The TFRI interpreter 2408 uses the stored value when the N / C of the HARQ info is C, that is, when the coded block indicates retransmission. In the process, the process of determining the initial transmission / retransmission by the TFRI analysis unit 2408 is determined through the number of bits of the TFRI field which is found to be an error as a result of performing the CRC operation. That is, if the number of bits of the TFRI of TFRS_FT and the number of bits of the TFRI field are the same, it means the first transmission. If the number of bits of the TFRI of TFRS_RT is the same, it means retransmission.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

 As described above, the present invention has the advantage of reducing the number of bits for transmitting reverse control information for user data in a communication system using a high speed forward packet connection, thereby increasing resource efficiency and increasing system efficiency.

Claims (13)

In a communication system using a fast forward packet access method, code information used by a user terminal for a fast forward packet access call and transmission format resource information for the user terminal are transmitted through different fields of a specific channel, respectively. In the method for transmitting and receiving a format resource set, Determining, by the base station, a transport format resource set for the user terminal having a modulation and coding scheme level supported by the user terminal, and a transport block set size corresponding to the modulation and coding scheme level supported by the user terminal; Comparing the size of the determined transport format resource set with a size of a field for transmitting the transport format resource information; And determining a block coding scheme for the transport format resource set according to a result of comparing the size of the transport format resource set and the size of the transport format resource information field. Method of transmitting and receiving a transport format resource set in a system. The method of claim 1, A block coding rate applied when the size of the transport format resource set is equal to the size of the transport format resource information field and a block coding rate applied when the size of the transport format resource set is smaller than the size of the transport format resource information field A method for transmitting and receiving a transport format resource set in a communication system using a high speed forward packet access method, characterized in that the larger decision. The method of claim 2, And the input of the block coding is a size of the transport format resource set. The method of claim 1, And transmitting and receiving a transmission format resource set in a communication system using a fast forward packet access scheme, wherein the specific channel is a common control channel. The code information used by the user terminal for the fast forward packet access call, the retransmission indicator indicating whether the coded block to be transmitted is the first transmission or the retransmission, and the transmission format resource information for the user terminal are different fields of a specific channel. A method for transmitting and receiving a transmission format resource set in a communication system using a high speed forward packet access scheme, each transmitting through a packet, A base station checking whether the coded block to be transmitted is the first transmission or retransmission; The user terminal has a modulation and coding scheme level that can be supported by the user terminal when the coded block to be transmitted is the first transmission and a transport block set size corresponding to the modulation and coding scheme level that the user terminal can support. Determining an initial transmission transport format resource set for Determining a retransmission transmission format resource set for the user terminal with a modulation and coding scheme level supported by the user terminal when the coded block to be transmitted is retransmission as a result of the checking; Transmitting and receiving a transport format resource set in a communication system using a fast forward packet access method, characterized by differently determining a block coding scheme for each of the initial transport transmission format resource set and the retransmission transport format resource set. How to. The method of claim 5, A block coding rate applied to the initial transmission transmission format resource set is less than the block coding rate applied to the retransmission transmission format resource set. A method of transmitting and receiving a transmission format resource set in a communication system using a fast forward packet access scheme. . The method of claim 6, And the input of the block coding is a size of the transport format resource set. The method of claim 5, And transmitting and receiving a transmission format resource set in a communication system using a fast forward packet access scheme, wherein the specific channel is a common control channel. delete delete delete delete An apparatus for transmitting and receiving a transport format resource set in a communication system using a fast forward packet access method, A code allocation unit for generating code information used by a user terminal for a high speed forward packet access call; According to the modulation and coding scheme level that the user terminal can support and the transmission block set size corresponding to the modulation and coding scheme level that the user terminal can support according to whether the coded block to be transmitted is the first transmission or retransmission, A transport format resource information generator for generating a transport format resource set for the user terminal; A plurality of block coders for performing block coding with the size of the generated transport format resource set as an input; And a multiplexer for multiplexing the code information and the set of the block-coded transport format resources into a single bit stream. 10. An apparatus for transmitting and receiving a transport format resource set in a communication system using a fast forward packet access scheme.

Images