User equipment and base station for wideband code division multiple access frequency division duplex

Wide frequency division code multiple access frequency division duplex user equipment and base station

This creation is about a wireless communication technology, especially an enhanced uplink (hereinafter referred to as EU, enhanced uplink) transmission technology.

In the third-generation (3G) cellular system, such as the system 100 shown in Figure 1, EU improves the output and transmission delay of uplink data. The system 100 includes a Node B 102, an RNC 104, and a wireless transmission/reception unit (hereinafter referred to as a WTRU) 106.

As shown in Figure 2, the WTRU 106 includes a protocol architecture 200, which includes a higher layer 202 and an EU media access control (hereinafter referred to as MAC) (hereinafter referred to as MAC-e) 206 to support a dedicated channel MAC ( Hereinafter referred to as MAC-d) 204 and the physical layer (hereinafter referred to as PHY) 208 between EU operations. The data received by the MAC-e 206 from the channel for EU transmission is the MAC-d stream. The MAC-e 206 is responsible for demultiplexing the data from the MAC-d stream into a MAC-e protocol data unit (hereinafter referred to as PDUs) for transmission, and is responsible for selecting the appropriate EU transmission format combination for EU transmission (hereinafter referred to as E-TFCs).

In order to allow EU transmission, the physical resource permission is allocated to the WTRU 106 by the Node B 102 and RNC 104, and the WTRU UL data channel that requires fast dynamic channel configuration has the fast "schedule" permission provided by the Node B 10 , And the channels that need to be continuously configured have the "unscheduled" permission provided by RNC 106. The MAC-d flow provides resources for UL transmission to configure the MAC-e 206, and the MAC-d flow is configured as a scheduled or unscheduled MAC-d flow.

"Service permission" is a permission for scheduled data, and "non-scheduled permission" is a permission for non-scheduled data. The service license is converted into the power ratio corresponding to the amount of scheduled data that can be multiplexed, and therefore, the schedule data license is generated.

The RNC 104 uses radio resource control (RRC) procedures to configure the non-scheduled permission for each MAC-d flow. Multiple non-scheduled MAC-d flows can be configured in the WTRU 106 at the same time. This configuration is typically in wireless access (RAB, radio access bearer) is executed immediately after establishment, but it can also be reconfigured when needed. The unscheduled permission of each MAC-d flow will specify the number of bits that can be multiplexed into MAC-e PDUs. If multiplexing is performed in the same transmission time interval (hereinafter referred to as TTI), the WTRU 106 will then allow transmission Unscheduled transmission until the total amount of unscheduled licenses.

According to the scheduling information sent from the WTRU 106 in the rate request, the Node B 102 dynamically generates the scheduling permission for scheduling the MAC-d flow. The signal transmission between the WTRU 106 and the Node B 102 is performed by fast The MAC layer signal transmission is executed, and the scheduling permission generated by the Node B 102 specifies the maximum allowable EU dedicated entity data channel (hereinafter referred to as E-DPDCH)/dedicated entity control channel (hereinafter referred to as DPCCH) power ratio, the WTRU 106 uses this power ratio and other configuration parameters to determine the maximum number of bits for all scheduled MAC-d flows to be multiplexed into one MAC-e PDU.

The scheduled permission is "above the non-scheduled permission" and is mutually exclusive with the non-scheduled permission, that is, the scheduled MAC-d flow cannot use the non-scheduled license transmission, and the non-scheduled MAC-d flow is also Unable to use scheduled license transfer.

The EU transport format combination set (E-TFCS) contains all possible E-TFCs known to the WTRU 106. For each EU transmission, an E-TFC is selected from a group of supporting E-TFCs in the E-TFCS.

Since other UL channels are better than EU transmission, the effective power of EU data transmission on E-DPDCH is the power remaining after the power required by DPCCH, dedicated physical data channel (DPDCH), high-speed dedicated physical control channel (HS- DPCCH) and EU dedicated entity control channel (E-DPCCH) will also be considered. According to the remaining power for EU transmission, the status of blocking or supporting E-TFCs in the E-TFCS is continuously determined by the WTRU 106.

Each E-TFC corresponds to some MAC layer data bits that can be transmitted in one EU transmission time interval (TTI). Since each E-TFC transmitted in each EU TTI has only one MAC-e PDU, The maximum E-TFC supported by the remaining power defines the maximum amount of data (that is, the number of bits) that can be transmitted in a MAC-e PDU.

Multi-scheduled and/or non-scheduled MAC-d flows can be multiplexed in each MAC-e PDU according to absolute priority. The amount of data multiplexed by each MAC-d flow is the current scheduled or The minimum value of the non-scheduled permission, the effective MAC-e PDU load from the maximum supported TFC, and the effective data transmitted on the MAC-d stream.

Within the supported E-TFCs, the WTRU 106 selects the smallest E-TFC that maximizes data transmission based on the scheduling and non-scheduled permissions. When the scheduled and non-scheduled permissions are fully used, valid MAC-e PDUs are fully used, Or when the WTRU 106 no longer has data and is allowed to transmit, MAC-e PDUs will be assembled (padded) to meet the next largest E-TFC size, and this multiplexed MAC-e PDU and corresponding TFC will pass through the Physical layer for transmission.

The service and non-service licenses will specify the maximum amount of data that can be multiplexed from MAC-d streams into MAC-e PDUs in each EU TTI. Since the scheduling license is based on the E-DPDCH/DPCCH ratio, each The number of data bits allowed by the MAC-e PDU that can be multiplexed cannot only be explicitly controlled to allow a specific size. The specific size is consistent with the support of the E-TFCs in the E-TFCS. Restricted data size.

The remaining transmission power used for EU data transmission will determine the list of supported E-TFCs in the E-TFCS. Since the supported E-TFCs are determined by a limited number of E-TFCs in the TFCS, MAC should be allowed -The interval size of e PDU size will not allow all MAC-d flows to be combined with MAC-e headers. Therefore, since the permission is multiplexed into a MAC-e PDU allowed MAC-d flow, it is often not compatible with this Supporting one of the sizes of E-TFCs requires the use of assembly methods to form MAC-e PDUs in order to meet the smallest possible E-TFC size in the list of supported E-TFRCs.

It is generally expected that when EU cells are operating at maximum capacity, MAC-e PDU multiplexing will often be restricted by the service and non-service licenses, and will not be subject to the maximum support of E-TFC or WTRU EU for transmission. Limited by valid data. In this case, it needs to be assembled to comply with the selected E-TFC, which may exceed the size of the multiplexed processing block of the MAC-d stream data containing the relevant MAC-e header information, depending on what is in the E-TFCS. The size of the interval between the specified E-TFCs. In this case, the effective data rate will unnecessarily drop from the data rate allowed by the selected E-TFC and the physical resource used for the transmission.

Figure 3 shows a MAC-e PDU 300. The MAC-e PDU header 302 and the MAC-d flow data 304, which are permitted by the scheduled and non-scheduled permissions, are multiplexed. Among a set of supported E-TFCs, the WTRU 106 selects a smallest E-TFC from the list of supported E-TFCs, which is larger than the MAC-e PDU header 302 and the MAC-d flow data 304. The assembly 306 is then used for the MAC-e PDU to meet the selected E-TFC size, however, the assembly 306 may exceed the multiplexing block size of the MAC-d stream data. In this case, the physical resources used for EU transmission cannot be fully utilized, and the effective WTRY data rate will drop unnecessarily. Therefore, it is necessary to change the way of multiplexing EU data.

This creation is about quantizing the amount of multiplexed data allowed by the license to closely match the size of a selected E-TFC transmission block. The amount of the scheduled and/or unscheduled data allowed to be transmitted is either increased or decreased relative to the permission, so that the amount of data multiplexed into a MAC-e PDU will be closer to meeting the selected E-TFC transmission block size.

When the scheduling data is adjusted to more closely match a selected E-TFC, the scheduling data to be multiplexed, the maximum amount of scheduling load to be transmitted, and the scheduled and non-scheduled data that can be transmitted are determined by The quantization is the sum allowed by the permission of the next larger or smaller E-TFC size, minus the amount of non-scheduled data that can be transferred allowed by the non-scheduled permission.

The quantization process is performed when the multiplexing permission is limited, and is not limited by the maximum E-TFC size caused by the E-TFC limitation, or is limited by the E-DCH data that can be used for transmission.

When referring to "WTRU" hereinafter, it includes but is not limited to, a user equipment (hereinafter referred to as UE), a mobile station, a fixed or mobile subscriber unit, a pager, or any other that can be used in a wireless environment s installation. When referring to "a node B" hereinafter, it includes, but is not limited to, a base station, a site controller, an access point (AP), or any other interface device in a wireless communication environment. One possible system using the WTRU and Node B is a wide frequency division code multiple access (hereinafter referred to as W-CDMA) frequency division duplex (hereinafter referred to as FDD) communication system, but these embodiments can also be applied to other communication systems.

The features of this creation can be integrated into an integrated circuit (hereinafter referred to as IC) or configured in a circuit containing many interconnected elements.

The modification of the MAC-e PDU multiplexing processing logic proposed below is to more effectively multiplex the data and improve the radio resource utilization in the following situations, which is because the MAC-e PDU multiplexing processing is limited by the row Scheduled and/or non-scheduled licenses, and are not limited to the maximum supported E-TFC or valid EU data for transmission. According to scheduling and non-scheduled permits, the amount of data that multiplexes the MAC-d flow into MAC-e PDUs will increase or decrease to more closely match the next smallest or next largest E-TFC size, which is relative to the Scheduled and non-scheduled permission allows the amount of data to be multiplexed.

Figure 4 shows a flow chart of a procedure 400 for generating MAC-e PDUs based on this creation. In step 405, a WTRU receives a scheduled data permission from a Node B, and/or a non-scheduled data permission from an RNC. In step 410, the size of an E-TFC transmission block is selected based on the scheduled and non-scheduled permissions, and the amount of data allowed to be multiplexed. In step 415, quantization processing is performed on the maximum scheduled and/or unscheduled data volume allowed to be transmitted according to the scheduling and non-scheduled permits, so that the multiplexing process is the data volume of each MAC-e PDU. It is closer to meet the selected E-TFC transmission block size.

Figure 5 shows a flowchart of a procedure 500 for generating MAC-e PDUs according to another embodiment of the present creation. In step 505, a WTRU receives a scheduled data permission from a Node B, and/or a non-scheduled data permission from an RNC. In step 510, the size of an E-TFC transmission block is selected based on the scheduled and non-scheduled permissions, and the amount of data allowed to be multiplexed. In step 515, the amount of buffered WTRU data allowed to be multiplexed by the at least one license is quantized to make the scheduled and non-scheduled data of each EU MAC-e PDU (including the MAC table). The sum of the header and control information) will be closer to the selected E-TFC transmission block size.

Or, in a separate embodiment, the interval size of the E-TFC size is defined within the E-TFCS, so that the change between the E-TFC size will not be greater than a MAC-d PDU and the related MAC -e header burden, E-TFCs are defined for each possible MAC-d stream multiplexing combination and related MAC-e header burden. By optimizing the E-TFCS in this way, after the MAC-d stream data is multiplexed according to the scheduling and non-scheduled permissions, the assembly requirement will not exceed the possible MAC-d stream multiplexing block size.

Figure 6 shows a flowchart of a procedure 600 for generating MAC-e PDUs according to another embodiment of the present creation. The largest E-TFC is selected from a group of supporting E-TFCs, which is smaller than the size of the MAC-d stream data, and the current license 602 allows MAC-e control signal transmission. As a result, the selected E-TFC allows a reduced amount of data to be multiplexed into MAC-e PDUs relative to the amount allowed by the license, so as to be closer to complying with the maximum E-TFC size, which is smaller than the row. The amount required for scheduled and unscheduled permits. The MAC-d flow data (scheduled and/or unscheduled) is multiplexed into a MAC-e PDU according to an absolute priority until there is no MAC-d flow data block within the limit of the selected E-TFC 604 So far, the MAC-e PDU is assembled to conform to the selected E-TFC size 606.

Figure 7 shows the reduced size of MAC-e PDU 700B, which is closer to the E-TFC size selected according to the embodiment of Figure 6. A MAC-e PDU header 702 and MAC-d flow data blocks 704a-704c are supported by current scheduled and unscheduled permissions. Please refer to Figures 6 and 7, the largest E-TFC smaller than the MAC-d stream data size allowed by the current license is selected from the group of supported E-TFCs (step 602). The MAC-d flow data block, (in this embodiment, it is two MAC-d flow data blocks 704a, 704b), is multiplexed into MAC-e PDU 700B according to absolute priority, until the selected Until there is no MAC-d stream data block within the E-TFC size limit (step 604). The MAC-d stream data block 704c is not multiplexed because it will exceed the limit of the selected E-TFC. Preferably, the amount of multiplexed scheduling data is adjusted to more closely match the selected E-TFC. -TFC size. Next, the assembly 706 is used on the MAC-e PDU 700B to conform to the selected E-TFC size (step 606). The assembly technique can be completed by inserting a data tail indicator into the MAC-e PDU header data.

Figure 8A shows a flow chart of the process 800 for generating a MAC-e PDU, where the minimum E-TFC size is selected from the group of E-TFCs, and the supporting E-TFC system supports allowing according to the current schedule and non- Schedule the amount of data allowed for multiplexing. The MAC-d stream data block is multiplexed into a MAC-e PDU according to an absolute priority until it reaches the maximum data volume 802 allowed by the current scheduled and unscheduled permissions. The smallest possible E-TFC is selected from a group of supporting E-TFCs, which is larger than the size of the multiplexed MAC-e PDU 804. If the selected E-TFC size exceeds the multiplexed MAC-e stream data block and the MAC-e header, and exceeds the minimum MAC-d stream data multiplexed block size, add one according to the absolute priority Or multiple additional MAC-d flow data blocks, until no more MAC-d flow data blocks and related MAC-e header information can be matched in the selected E-TFC size.

In another procedure 850 shown in Figure 8B, the minimum E-TFC that supports the data volume that allows multiplexing according to the current scheduling and non-scheduled permissions is selected from the group of supporting E-TFCs 852. The MAC-d stream data block is then multiplexed into a MAC-e PDU according to the order of absolute priority until it reaches the maximum amount of data allowed by the selected E-TFC size. Preferably, only the The amount of scheduled data allowed by the license is adjusted to more closely match the selected E-TFC, and the non-scheduled MAC-d stream data of multiplexed processing can be restricted by the non-scheduled license. The assembly is then used to conform to the selected E-TFC size 856. According to this mechanism, data can be transmitted beyond the scheduled and/or non-scheduled license.

Figure 9 shows an increased size MAC-e PDU 900, which fully utilizes a selected E-TFC size that can support the currently licensed E-TFC. A MAC-e PDU header 902 and MAC-d flow data blocks 904a-904c are supported by the current scheduled and unscheduled permissions. Please refer to Figure 8A, Figure 8B, and Figure 9. The MAC-d stream data blocks 904a-904c are multiplexed into a MAC-e PDU according to an absolute priority until the current scheduled and non-scheduled permissions are reached Up to the amount of data allowed. As shown in Figure 9, it uses three (3) MAC-d stream data blocks 904a-904c as an example for multiplexing. This creation can also multiplex any number of MAC-d stream data blocks. handle. The smallest possible E-TFC is selected from a group of supporting E-TFCs, which is larger than the multiplexed MAC-e The size of the PDU. If the selected E-TFC size exceeds the size of the multiplexed MAC-d flow data blocks 904a-904c and the MAC-e header 902, and exceeds the minimum MAC-d flow multiplexed block size, then One or more additional MAC-d flow data blocks 904d will be added according to absolute priority until there are no more MAC-d flow data blocks and related MAC-e headers within the selected E-TFC size As far as the information is met, preferably, only scheduled MAC-d flow data is added to exceed the current permission, but non-scheduled MAC-d flow data can also be added. The assembly 906 is then used to conform to the selected E-TFC size. According to this mechanism, MAC-d stream multiplexing is optimized in order to utilize unused data bits that do not fill the assembled bits.

Please refer to Fig. 10A and Fig. 10B together, which are the flowcharts of the program 1000 for multiplexing, so that before the MAC-e PDU is multiplexed, the multiple tasks are performed according to the schedule and/or non-scheduled permission. The data volume will be adjusted to be closer to the next-highest or next-smallest E-TFC size, which is relative to the data volume allowed by the scheduling and/or non-scheduled permission to multitask. Figure 10A is a method in which only the amount of scheduled data to be multiplexed is adjusted to more closely match the selected E-TFC.

Please refer to Figure 10A, an E-TFC restriction procedure (step 1005) is executed to determine the set of supporting E-TFCs that includes the largest possible E-TFC size (step 1010) by considering the highest priority available for transmission The MAC-d flow power deviation of Quanzhi data is determined.

Still referring to Figure 10A, if the maximum E-TFC size generated by the E-TFC restriction (considering the remaining power and the highest priority MAC-d stream power deviation), it is determined in step 1015 to be smaller than the schedule And the amount of data allowed by the non-scheduled permission (in the example of the remaining power limit), the maximum possible load used for MAC-e PDU multiplexing will be set to the maximum possible E-TFC size. The maximum amount of the scheduled data to be processed will be set to the amount of data specified by the scheduling permission (step 1025), and the maximum amount of the non-scheduled data to be multiplexed will be set to the non-scheduled permission The specified amount of data (step 1030).

Still referring to Figure 10A, if the maximum E-TFC size generated by the E-TFC limit is determined in step 1015, it is determined to be greater than the data amount allowed by the schedule and the non-scheduled permission (under the remaining power limit) In the example of ), the maximum amount of the scheduled data to be multiplexed will be adjusted to match the next largest or next smallest E-TFC size, which is relative to the effective data amount of the scheduled and non-scheduled permits (Steps 1040, 1045).

For example, the maximum amount of scheduled data is set to the selected E-TFC size minus the effective amount of data allowed to be transmitted by the non-scheduled permission, instead of setting the maximum amount of scheduled data to be multiplexed Is the amount of data allowed by the scheduling permission (step 1040), and the maximum amount of the non-scheduled data to be multiplexed is set to the non-scheduled permission of each non-scheduled data flow (step 1045), these methods or Other similar methods will cause the scheduling and unscheduled data of multiple jobs to be set to match the selected E-TFC size, instead of setting the amount of multiple scheduling and unscheduled data according to the relevant permission.

Preferably, the amount of data allowed to be multiplexed by the scheduled MAC-d stream is increased or decreased to more closely match the selected E-TFC size. Optionally, the maximum possible load for MAC-e PDU multiplexing is set to the selected E-TFC size. It is also possible to pre-determine the optimal multi-tasking schedule and/or other operations for the amount of non-scheduled data before the multi-tasking.

Please refer to Figure 10B. The MAC-d stream is then multiplexed into MAC-e PDUs in the order of priority until the maximum supported E-TFC size, the amount of data allowed by the scheduling and non-scheduled permits is reached, or until the All data that can be transmitted on the MAC-d stream has been multiplexed. In step 1050, the remaining total load is set to the maximum possible MAC-e PDU load, the remaining scheduled load is set to the maximum scheduled data to be multiplexed, and the remaining non-scheduled load is set to the maximum to be multiplexed Unscheduled data.

"Remaining total load" is the maximum possible load generated by the E-TFC limit (that is, the maximum supported E-TFC), but it is very important that in step 1060, this parameter is due to the multiple processing loop It is reduced every time the multiple data block. When in the maximum E-TFC restriction type, in step 1065, this parameter will make it out of the multiplexing loop. The "remaining scheduled load" and the "remaining non-scheduled load" are the remaining scheduled and remaining non-scheduled data, which are initially set to the maximum allowable multiplexing value of the data in this form. Then, this parameter will be As the multiplexing of the data form decreases each time, in the permission restriction type, it will also cause the multiplexing loop to leave in step 1065, and the effective highest priority data will be selected for transmission.

In step 1055, for each scheduled channel of this priority, the minimum remaining total load, the remaining scheduled load, and the effective data of this channel are multiplexed, and the remaining total load and the remaining scheduled load are borrowed Reduced by the amount of data processed by multiplexing. In step 1060, for each non-scheduled data of this priority, the minimum remaining total load, the remaining non-scheduled load, and the valid data on this channel are multiplexed, the remaining total load and the remaining scheduled The load will be reduced by the amount of data that is multiplexed.

If it is determined in step 1065 that the remaining total load is equal to zero, or the remaining scheduled load and remaining unscheduled load are equal to zero, or there is no data available for transmission, select the smallest possible E-TFC size, which supports multiple data supply If necessary, increase the size of the MAC-e PDU to fit the size (step 1070). Otherwise, in step 1075, the data with the next lowest priority is selected for transmission. It is worth noting that if the next lowest priority is not selected in step 1075, it is also possible to select only the highest priority logical channel that has not been served, and continue the multiplexing process loop until all the logical channels are served.

Please refer to FIG. 11A and FIG. 11B together, which are used to illustrate another embodiment of the present creation. In step 1301, a power deviation of the MAC-d stream is determined. In step 1302, using this power deviation, a maximum support load that can be sent by the WTRU, such as the maximum support E-TFC, is determined based on the deviation, and the remaining power allowed by the E-DCH data is determined, which can be regarded as E -TFC restricted program. In step 1303, a variable "remaining power" is initially set as the maximum support load. In step 1304, based on the scheduling permission, a variable "remaining scheduling load" is set as the maximum load that can be transmitted according to the scheduling permission and the power deviation. In step 1305, for each MAC-d flow with an unscheduled permission, a variable "remaining unscheduled load" is set as the permitted value. In step 1306, a variable "unscheduled load" is the amount of unscheduled data that can be transmitted, and is based on the sum of the non-service permission and the effective data amount of each unscheduled MAC-d stream.

In step 1307, if the "remaining load" is greater than the sum of the amount of data permitted to be transmitted by the "remaining scheduled load" and "remaining unscheduled load", it includes any MAC header information and control signal transmission burden , Then select the second smallest supported E-TFC based on the total. If the "remaining load" is not greater than the sum, the maximum supported E-TFC will be used to limit the amount of multiplexed data. There is no "scheduled load" in this type, and the selected E-TFC will be the maximum supported E-TFC. At the same time, the "remaining load" will not be greater than the sum. This allows all "unscheduled" load transfers unless the E-TFC restriction does not allow this transfer.

The second-smallest supporting E-TFC is the largest supporting E-TFC, which does not carry more than the total amount. In other words, the selected E-TFC is the small E-TFC, which is based on the service license , Non-service permission, power deviation, valid data, including any MAC information and control signal burden, such as scheduling information. In step 1308, the "remaining schedule load" is set to the selected E-TFC, which can also be regarded as a "quantized sum" minus the "unscheduled load" and any MAC header information and control signals Send burden. By setting the "Remaining Scheduled Load" in this way, only the scheduled data will be quantized, and the "Unscheduled Load" will be stored in the selected E-TFC according to the non-scheduled permission. In step 1309, according to the priority, each logical channel and its related MAC-d flow are multiplexed to the MAC-e/es PDU.

In step 1310, if the MAC-d flow of the logical channel is used for non-scheduled permission, the MAC-e/es PDU is filled with the MAC-d flow data by this logical channel until the "remaining non-scheduled load" , "Remaining Load", or until all valid MAC-d flow data of the logical channel is filled, the bits used to fill the MAC-e/es PDU are determined by the "Remaining Load" and "Remaining Unscheduled "Load" is subtracted, which takes into account any MAC header and control signal transmission burden. In step 1311, if the MAC-d flow is used for the scheduling permission, the MAC-e/es PDU is filled with the MAC-d flow data by this logical channel until the "remaining scheduling load" and "remaining Load" or all valid MAC-d stream data of the logical channel is filled. In step 1312, the bits used to fill the MAC-e/es PDU are subtracted from the "remaining load" and "remaining scheduled load", which takes into account any MAC header and control signal transmission burden. In step 1313, this procedure is repeated for all logical channels, or until the "remaining non-scheduled load" and "remaining scheduled load" are used up, or there is no valid data for transmission. In step 1314, the MAC header information and control signal transmission burden is added to the PDU, and the PDU is assembled to the selected E-TFC size.

This procedure allows the operation of the UE to be "decidable", and the Node B scheduler can therefore accurately predict how the UE will use the resource license, and therefore, the Node B can allocate resources more efficiently. The ability to adjust (quantize) the amount of multiplexed data is what we need, so that: first, physical resources can be used more effectively, and second, the data rate can be increased. In order to achieve this goal, in the case of license restrictions, the E-TFC must be selected according to the current license, and this load size is used to allow quantization before the MAC-e/es PDU multiplexing process. The amount of scheduled data. With effective E-TFC selection and multiple processing algorithms, better utilization of physical resources and increased data rates can be achieved.

Figure 12 shows a simple block diagram of EU multiplexing. In the WTRU 1414, the MAC-d streams 1403 of different logical channels 1402 are input to the MAC-e/es 1404 through the MAC-d 1401. An E-TFC selection device 1405 selects an E-TFC for EU transmission, such as based on an enhanced dedicated channel (E-DC) TTI basis. The E-TFC selection device 1405 receives input, such as scheduling permission (SG) 1406, non-scheduling permission (NSG) 1407, power deviation (PO) 1408, MAC header information and control signal transmission burden (MAC control), The MAC-d mapped to the E-DCH buffer occupies 1422 and supports E-TFCs (or the remaining E-DCH power to perform the E-TFC restriction procedure). Similarly, the "permitted quantization" that adjusts the maximum amount of multiplexed data allowed by the resource license can occur between the E-TFC selection 1405 and the multiplexer (MUX) 1401. A multiplexer (MUX) 1410 multiplexes the MAC-d stream 1403 for transmission according to the license, which is quantized to more closely match the selected E-TFC. The MUX 1410 multiplexes the MAC-d stream 1403 plus header information 1409, and adds the assembly if necessary to meet the selected E-TFC size. The MAC-e/es PDUs generated by the MUX 1410 1411. The selected E-TFC and power deviation are input to a physical layer device (PHY) 1412 to use the selected E-TFC for transmission on the E-DPCH(s) 1413.

On the base station/node B and radio network controller (RNC) 1415, the E-DPCH(s) 1413 is received and processed by a PHY 1416 of the base station/node B 1415. The MAC-e/es PDUs 1417 generated by the PHY 1416 are demultiplexed by a demultiplexer (DEMUX) 1418 of the MAC-e/es 1420 into a MAC-d stream 1419 and a logical channel 1420. The MAC-d stream 1419 is transmitted to the MAC-d 1421.

Please refer to Figure 13A and Figure 13B together, which is a flowchart of the multiplex processing program 1100, in which the amount of multiplex scheduled and/or unscheduled data is adjusted to be closer to the second highest or second lowest E-TFC Size, and perform data multiplexing at the same time. The multiplexing shown in Figure 10B returns to the full priority order. If the amount of data to be multiplexed is limited by the permission, the amount of data to be multiplexed will be adjusted according to the next highest or second lowest E-TFC size , Which is based on the amount of data allowed for multiplexing by the sum of the licenses.

Please refer to Figure 13A. In step 1105, the remaining total load is set to the maximum possible MAC-e PDU load, the remaining scheduled load is set to the maximum scheduled data to be multiplexed, and the remaining non-scheduled load is set to the desired The largest non-scheduled data for multiplexing.

In step 1110, it is determined whether the remaining scheduled load is less than or equal to the remaining total load. Optionally, determine whether the remaining unscheduled load and unscheduled data are greater than zero (step 1115), and select the next smallest or second largest E-TFC size, which is relative to the amount of data that has been multiplexed (including MAC table Head load) plus the remaining scheduled load (step 1120). The remaining scheduling load is equal to the selected E-TFC size minus the amount of data that has been multiplexed (including the MAC header burden).

In step 1125, for each scheduled channel with this priority, the minimum remaining total load, the remaining scheduled load, and the valid data on this channel are multiplexed, and the remaining total load and the remaining schedule are reduced by multiplexing the amount of data.Cheng load.

Please refer to Figure 13B. In step 1130, for each non-scheduled channel of this priority, the minimum remaining total load, the remaining unscheduled load, and the valid data on this channel are multiplexed by multiplexing the data volume Reduce the remaining total load and the remaining scheduled load.

If it is determined in step 1135 that the remaining total load is equal to zero, or the remaining scheduled load and remaining unscheduled load are equal to zero, or there is no data available for transmission, select the smallest possible E-TFC size, which supports multiple data supply If necessary, increase the size of the MAC-e PDU to fit the size (step 1140). Otherwise, in step 1145, the data available for transmission with the second lowest priority is selected. It must be noted that if the second lowest priority is not selected in step 1145, only the highest priority logical channel that has not been served can be selected.

Figure 14 shows a flowchart of a multiplexing processing program 1200 according to another embodiment of the present creation. In the case of permission restriction, the MAC-d flow data is multiplexed into a MAC-e PDU until the amount of data allowed by the scheduled or unscheduled permission and the multiplexed data per MAC-d flow is reached.

Before assembling the MAC-e PDU to meet the selected E-TFC size, if the multiplexing block size (the MAC-d PDU size) is smaller than the assembly required to meet the next largest E-TFC size, it is Compared with the amount of data allowed by the scheduled and non-scheduled permissions, more MAC-d stream data will be multiplexed. Preferably, for additional multiplexing, only the scheduled data with the highest priority available for transmission is used, and the non-scheduled multiplexed data is restricted by the non-scheduled permission.

Or, if the multiplexed block size (the MAC-d PDU size) is smaller than the size that needs to be assembled to the next-highest E-TFC, reduce the multiplexed data to support the next-lowest E-TFC size. The amount of data allowed by the scheduling permission. Optionally, in addition to reducing the size of the multi-tasking block of the E-TFC size, the assembly threshold value can also be considered, or "assembly is required to meet the next-lowest E-TFC size smaller than the larger E-TFC". As a criterion to reduce the size of the E-TFC.

Please refer to the amount of data that can be multiplexed according to the permission and the amount of data that can be multiplexed according to a selection of E-TFC, which takes into account the MAC header information and other control signal transmission burdens required in the MAC-e PDU format.

Please refer to Figure 14 to select the smallest possible E-TFC size, which supports the data size that has been multiplexed (including the burden of the MAC header) (step 1205). If the remaining scheduled load and the remaining non-scheduled load are equal to zero (optional step 1210), then the total remaining load is equal to the selected E-TFC size minus the amount of data that has been multiplexed (including the MAC header burden) (Step 1215).

In step 1220, if it is determined that the remaining total load is greater than or equal to the multiplexing block size of each MAC-d stream, the minimum remaining total load of the multiplexing and the valid data of this channel for each scheduled channel of this priority.

Reduce the remaining total load and the remaining scheduled load by multiplexing the amount of data (step 1225). In step 1230, the next lowest priority data available for transmission is selected. In step 1235, if necessary, add to the MAC-e PDU to meet the selected E-TFC size.

Any combination of the above-mentioned embodiments can also be used to achieve improved multi-tasking efficiency and wireless resource utilization.

Although the features and elements of this creation are all described in specific combinations in the embodiments, each feature or element in the embodiments can be used alone, and does not need to be combined with other features or elements of the preferred embodiment, or with /Do not combine differently with other features and components of this creation. Although this creation has been described through the preferred embodiments, other variations that do not depart from the scope of the patent application for this creation are obvious to those who are familiar with this technique.

<p>MUXMultiplexer</p><p>PHYPhysical layer</p><p>MACMedia Access Control</p><p>E-DPCHDedicated physical channel</p><p>1406Scheduling permission</p><p>1407Unscheduled License</p><p>1408Power deviation</p><p>1409Header Information</p><p>E-TFCEnhanced dedicated channel transmission form combination</p><p>WTRUWireless Transmission/Receiving Unit</p><p>MAC-dMedia Access Control-Dedicated Channel</p><p>DEMUXDemultiplexer</p><p>RNCWireless Network Controller</p><p>MAC-e PDUMedia Access Control Enhanced Dedicated Channel Packet Data Unit</p><p>1420Logic Channel</p><p>400, 500, 600, 800, 850, 1000, 1100, 1200 program</p>

By following the description of a preferred embodiment, the examples given, and referring to the corresponding drawings, this creation can be understood in more detail. Among them: Figure 1 shows a 3G cellular system; Figure 2 Shown is an EU communication protocol architecture in a WTRU; Figure 3 shows a MAC-e PDU generation process; Figure 4 shows a flow chart of a procedure for generating MAC-e PDUs, which is based on quantum The maximum amount of scheduled and/or non-scheduled data allowed to be transmitted is generated according to the first embodiment of this creation; Figure 5 shows a block diagram of a procedure for generating MAC-e PDUs, which is Generated by quantizing the maximum amount of non-scheduled data that allows multiplexing, which is based on another embodiment of this creation; Figure 6 shows a method for generating MAC-e PDUs by reducing multiplexing data The program flow chart, which is based on another embodiment of this creation; Figure 7 shows a schematic diagram of using the procedure of Figure 6 to generate MAC-e PDU; Figure 8A shows a method by adding additional MAC- d flow data block to generate MAC-e PDU process flow chart, which is based on another embodiment of the present creation; Figure 8B shows an additional MAC-d flow data block to generate MAC-e PDU program flow chart, which is based on a different program from Figure 8A; Figure 9 shows a program that uses Figure 8A and Figure 8B to generate MAC-e Schematic diagram of PDU; Figure 10A and Figure 10B show a program flowchart for multiplexing, which is based on another embodiment of this creation; Figure 11A and Figure 11B show a MAC-d stream multiplexing is a program flow chart of MAC-e PDUs; Figure 12 shows a block diagram of a simple structure of EU multiplexing; Figure 13A and Figure 13B show a multiplexing program A flowchart, which is another embodiment according to this creation; and Figure 14 is a flowchart of a multiplex processing program, which is another embodiment according to this creation.