MAC MULTIPLEXING AND TFC SELECTION PROCEDURE FOR ENHANCED UPLINK

FIELD OF INVENTION

[0001] The present invention is related to a wireless communications.

More particularly, the present invention is related enhanced uplink (EU) transmission.

BACKGROUND

[0002] In a Third Generation (3G) cellular system, such as the system 100 shown in Figure 1, EU provides improvements to uplink (UL) data throughput and transmission latency. The system 100 includes a Node-B 102, an RNC 104 and a wireless transmit/receive unit (WTRU) 106.

[0003] As shown in Figure 2, the WTRU 106 includes a protocol architecture 200 which includes higher layers 202 and an EU medium access control (MAC), (MAC-e) 206, used to support EU operation between a dedicated channel MAC, (MAC-d) 204, and a physical layer (PHY) 208. The MAC-e 206 receives data for EU transmission from channels known as MAC-d flows. The MAC-e 206 is responsible for multiplexing data from MAC-d flows into MAC-e protocol data units (PDUs) for transmission, and for selecting proper EU transport format combinations (E-TFCs) for EU transmissions. [0004] To allow for EU transmissions, physical resource grants are allocated to the WTRU 106 by the Node-B 102 and the RNC 104. WTRU UL data channels that require fast dynamic channel allocations are provided with fast "scheduled" grants provided by the Node-B 102, and channels that require continuous allocations are provided with "non-scheduled" grants by the RNC 106. The MAC-d flows provide data for UL transmission to the MAC-e 206. The MAC-d flows are either configured as scheduled or non-scheduled MAC-d flows. [0005] A "serving grant" is the grant for scheduled data. A "non-scheduled grant" is the grant for non-scheduled data. The serving grant is the power ratio that is converted to a corresponding amount of scheduled data that can be

multiplexed, thus resulting in the scheduled data grant.

[0006] The RNC 104 configures non-scheduled grants for each MAC-d flow using radio resource control (RRC) procedures. Multiple non-scheduled MAC-d flows can be configured simultaneously in the WTRU 106. This configuration is typically performed upon radio access bearer (RAB) establishment, but may be reconfigured when necessary. The non-scheduled grant for each MAC-d flow specifies the number of bits that can be multiplexed into a MAC-e PDU. The WTRU 106 is then allowed to transmit non-scheduled transmissions up to the sum of non-scheduled grants, if multiplexed in the same transmission time interval (TTI).

[0007] Based on scheduling information sent in rate requests from the

WTRU 106, the Node-B 102 dynamically generates scheduling grants for scheduled MAC-d flows. Signaling between the WTRU 106 and the Node-B 102 is performed by fast MAC layer signaling. The scheduling grant generated by the Node-B 102 specifies the maximum allowed EU dedicated physical data channel (E-DPDCH) / dedicated physical control channel (DPCCH) power ratio. The WTRU 106 uses this power ratio and other configured parameters to determine the maximum number of bits that can be multiplexed from all scheduled MAC-d flows into a MAC-e PDU.

[0008] Scheduled grants are "on top of and mutually exclusive of non- scheduled grants. Scheduled MAC-d flows can not transmit data using a non- scheduled grant, and non-scheduled MAC-d flows can not transmit data using a scheduled grant.

[0009] The EU transport format combination set (E-TFCS) comprising all possible E-TFCs is known to the WTRU 106. For each EU transmission, an E- TFC is selected from a set of supported E-TFCs within the E-TFCS. [0010] Since other UL channels take precedence over EU transmissions, the power available for EU data transmission on E-DPDCH is the remaining power after the power required for DPCCH, dedicated physical data channel (DPDCH), high speed dedicated physical control channel (HS-DPCCH) and EU dedicated physical control channel (E-DPCCH) is taken into account. Based on

the remaining transmit power for EU transmission, blocked or supported states of E-TFCs within the E-TFCS are continuously determined by the WTRU 106. [0011] Each E-TFC corresponds to a number of MAC layer data bits that can be transmitted in an EU transmission time interval (TTI). Since there is only one MAC-e PDU per E-TFC that is transmitted in each EU TTI, the largest E-TFC that is supported by the remaining power defines the maximum amount of data, (i.e., the number of bits), that can be transmitted within a MAC-e PDU. [0012] Multiple scheduled and/or non-scheduled MAC-d flows may be multiplexed within each MAC-e PDU based on absolute priority. The amount of data multiplexed from each MAC-d flow is the miiώnum of the current scheduled or non-scheduled grant, the available MAC-e PDU payload from the largest supported TFC, and the data available for transmission on the MAG-d flow. [0013] Within the supported E-TFCs, the WTRU 106 selects the smallest

E-TFC that maximizes the transmission of data according to the scheduled and non-scheduled grants. When scheduled and non-scheduled grants are fully utilized, available MAC-e PDU payload is fully utilized, or the WTRU 106 has no more data available and allowed to be transmitted, MAC-e PDUs are padded to match the next largest E-TFC size. This multiplexed MAC-e PDU and corresponding TFC are passed to the physical layer for transmission. [0014] The serving and non-serving grants specify the maximum amount of data that can be multiplexed from specific MAC-d flows into MAC-e PDUs each EU TTI. Since the scheduled grants are based on the E-DPDCH/DPCCH ratio, the number of data bits allowed to be multiplexed per MAC-e PDU can not be explicitly controlled only to allow certain sizes which match the limited number of data sizes of the supported E-TFCs within the E-TFCS. [0015] The remaining transmit power for EU data transmission determines the list of supported E-TFCs within the E-TFCS. Since the supported E-TFCs are determined from a limited number of E-TFCs in the TFCS, the granularity of allowed MAC-e PDU sizes will not allow for all possible MAC-d flow and MAC-e header combinations. Therefore, since the amount of MAC-d flow data allowed by the grants to be multiplexed into a MAC-e PDU will frequently not match the

size of one of the supported E-TFCs, padding will be applied to the MAC-e PDU to match the smallest possible E-TFC size within the list of supported E-TFCs. [0016] It is expected that when EU cells are operating at maximum capacity the MAC-e PDU multiplexing is frequently limited by the serving and non-serving grants, and not limited by the largest supported E-TFC or the WTRU EU data available for transmission. In this case, depending on the granularity of specified E-TFCs within the E-TFCS padding required to match the selected E- TFC may exceed the multiplexing block size of MAC-d flow data including associated MAC-e header information. In this case, the effective data rate is unnecessarily reduced from what is allowed by the selected E-TFC and the physical resources required for its transmission.

[0017] Figure 3 illustrates a MAC-e PDU 300. A MAC-e PDU header 302 and MAC-d flow data 304 allowed by scheduling and non-scheduling grants are multiplexed. Among a set of supported E-TFCs, the WTRU 106 selects the smallest E-TFC from a list of supported E-TFCs that is larger than MAC-e PDU header 302 and MAC-d flow data 304. Padding 306 is then applied to the MAC-e PDU to match the selected E-TFC size. However, the padding 306 may exceed the multiplexing block size of MAC-d flow data. In this case, physical resources used in the EU transmission are under utilized and the effective WTRU data rate is unnecessarily reduced. Accordingly, it is desirable to have alternate approaches to multiplexing EU data.

SUMMARY

[0018] The present invention is related to quantizing the amount of multiplexed data allowed by grants to closely match a selected E-TFC transport block size is disclosed. The amount of scheduled and/or non-scheduled data allowed to be transmitted is either increased or decreased relative to the grants so that the amount of data multiplexed into a MAC-e PDU more closely matches the selected E-TFC transport block size.

[0019] When the amount of scheduled data is adjusted to more closely match a selected E-TFC ₅ the maximum amount of scheduled data to multiplex, the scheduled payload to transmit, is determined by the sum of the scheduled and non-scheduled data available to be transmitted and allowed by the grants quantized to the next larger or smaller E-TFC size, minus the amount of available to be transmitted non-scheduled data that is allowed by the non- scheduled grants.

[0020] This quantization is applied when multiplexing is grant limited, and not limited by the maximum E-TFC size resulting from E-TFC restriction or limited by E-DCH data available for transmission.

BRIEF DESCRIPTION OF THE DRAWINGS [0021] Figure 1 shows a 3G cellular system.

[0022] Figure 2 shows an EU protocol architecture in a WTRU.

[0023] Figure 3 illustrates a MAC-e PDU generation.

[0024] Figure 4 is a flow diagram of a process for generating MAC-e PDUs by quantizing the maximum amount of scheduled and/or non-scheduled data allowed to be transmitted in accordance with a first embodiment. [0025] Figure 5 is a block diagram of a process for generating MAC-e PDUs by quantizing the maximum amount of non-scheduled data allowed to be multiplexed in accordance with another embodiment.

[0026] Figure 6 is a flow diagram of a process for generating a MAC-e PDU by reducing multiplexed data in accordance with another embodiment. [0027] Figure 7 illustrates MAC-e PDU generation using the process of

Figure 6.

[0028] Figure 8A is a flow diagram of a process for generating a MAC-e

PDU by adding additional MAC-d flow data blocks in accordance with yet another embodiment.

[0029] Figure 8B is a flow diagram of a process for generating a MAC-e

PDU by adding additional MAC-d flow data blocks in accordance an alternative to the process of Figure 8A.

[0030] Figure 9 illustrates MAC-e PDU generation using the processes of

Figures 8A and 8B.

[0031] Figures 1OA and 1OB, taken together, is a flow diagram of an exemplary procedure for multiplexing in accordance with another embodiment.

[0032] Figure 11A and HB is a flow diagram of a process for multiplexing

MAC-d flows into MAC-e PDUs.

[0033] Figure 12 is a block diagram illustrating a simplified architecture for EU multiplexing.

[0034] Figures 13A and 13B, taken together, is a flow diagram of a multiplexing procedure in accordance with another embodiment.

[0035] Figure 14 is a flow diagram of an exemplary multiplexing procedure in accordance with another embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0036] Hereafter, the terminology "WTRU" includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, or any other type of device capable of operating in a wireless environment. When referred to hereafter, the terminology "Node-B" includes but is not limited to a base station, a site controller, an access point or any other type of interfacing device in a wireless environment. One potential system where the WTRU and Node-B are used is the wideband code division multiple access (W-CDMA) frequency division duplex (FDD) communication system, although these embodiments can be applied to other communication systems. [0037] The features of the present invention may be incorporated into an integrated circuit (IC) or be configured in a circuit comprising a multitude of interconnecting components.

[0038] The following modifications to MAC-e PDU multiplexing logic are proposed for more efficient data multiplexing and improved radio resource utilization for the cases where MAC-e PDU multiplexing is limited by scheduled and/or non-scheduled grants, and not limited by the largest supported E-TFC or available EU data for transmission. The amount of data allowed to be

multiplexed from MAC-d flows into MAC-e PDUs according to the scheduled and non-scheduled grants is either increased or decreased to more closely match the next smaller or next larger E-TFC size relative to the amount of data allowed to be multiplexed by the scheduled and non-scheduled grants [0039] Figure 4 is a flow diagram of a process 400 for generating MAC-e

PDUs in accordance with an embodiment. In step 405, a WTRU receives a scheduled data grant from a Node-B and/or non-scheduled grants from an RNC. In step 410, an E-TFC transport block size is selected based on the amount of data allowed to be multiplexed according to the scheduled and non-scheduled grants. In step 415, the maximum amount of scheduled and/or non-scheduled data allowed to be transmitted according to the scheduled and non-scheduled grants is quantized so that the amount of data multiplexed into each MAC-e PDU more closely matches the selected E-TFC transport block size. [0040] Figure 5 is a flow diagram of a process 500 for generating MAC-e

PDUs in accordance with another embodiment. In step 505, a WTRU receives a scheduled data grant from a Node-B and/or non-scheduled grants from an RNC. In step 510, an E-TFC transport block size is selected based on the amount of data allowed to be multiplexed according to the scheduled and non-scheduled grants. In step 515, the amount of buffered WTRU data allowed to be multiplexed by the at least one grant is quantized so that the sum of scheduled and non-scheduled data (including MAC header and control information) multiplexed into each EU MAC-e PDU more closely matches the selected E-TFC transport block size.

[0041] Alternatively, in a separate embodiment, granularity of E-TFC sizes is defined within the E-TFCS so that the difference between E-TFC sizes is not greater than one MAC-d PDU and the associated MAC-e header overhead. E- TFCs are defined for each possible MAC-d flow multiplexing combination and associated MAC-e header overhead. By optimizing the E-TFCS in this way, the padding required after MAC-d flow data is multiplexed according to the scheduled and non-scheduled grants will not exceed the size of possible MAC-d flow multiplexing block sizes.

[0042] Figure 6 is a flow diagram of a process 600 for generating a MAC-e

PDU in accordance with another embodiment. A largest E-TFC is selected from a set of supported E-TFCs that is smaller than the size of MAC-d flow data and MAC-e control signaling allowed by current grants 602. As a result, the selected E-TFC permits a decreased amount of data to be multiplexed onto the MAC-e PDU relative to the amount allowed by the grants, to more closely match the largest E-TFC size that is smaller than the amount required by scheduled and non-scheduled grants. The MAC-d flow data (scheduled and/or non scheduled) is multiplexed into a MAC-e PDU in accordance with an absolute priority until no more MAC-d flow data blocks can be added within the limit of the selected E-TFC 604. The MAC-e PDU is padded to match the selected E-TFC size 606. [0043] Figure 7 illustrates the decreased MAC-e PDU 700B size that more closely matches a selected E-TFC size in accordance with the embodiment of Figure 6. A MAC-e PDU header 702 and MAC-d flow data blocks 704a-704c are supported by the current scheduled and non-scheduled grants. Referring to Figures 6 and 7, the largest E-TFC that is smaller than the size of MAC-d flow data allowed by current grants is selected from the set of supported E-TFCs (step 602). MAC-d flow data blocks, (in this example, the two MAC-d flow data blocks, 704a, 704b), are multiplexed into the MAC-e PDU 700B in accordance with an absolute priority until no more MAC-d flow data blocks can be added within the limit of the selected E-TFC size (step 604). MAC-d flow data block 704c is not multiplexed since it will exceed the limit of the selected E-TFC. Preferably, only the amount of multiplexed scheduled data is adjusted to more closely match the selected E-TFC size. Padding 706 is then applied to the MAC-e PDU 700B to match the selected E-TFC size (step 606). One technique for the padding is accomplished implicitly by insertion of an erid-of-data indicator in the MAC-e PDU header information.

[0044] Figure 8A is a flow diagram of a process 800 for generating a MAC-e

PDU where the smallest E-TFC size is selected from the set of supported E-TFCs that supports the amount of data allowed to be multiplexed according to the current scheduled and non-scheduled grants. MAC-d flow data blocks are

multiplexed into a MAC-e PDU in accordance with an absolute priority until the maximum amount of data allowed by current scheduled and non-scheduled grants is reached 802. The smallest possible E-TFC is selected from a set of supported E-TFCs that is larger than the size of the multiplexed MAC-e PDU 804. If the selected E-TFC size exceeds the size of the multiplexed MAC-d flow data blocks and the MAC-e header by more than the smallest MAC-d flow multiplexing block size, add one or more additional MAC-d flow data blocks in accordance with the absolute priority until no further MAC-d flow data blocks and associated MAC-e header information can fit within the selected E-TFC size. [0045] In an alternative process 850 shown in Figure 8B, the smallest E-

TFC that supports the amount of data allowed to be multiplexed according to the current scheduled and non-scheduled grants is selected from the set of supported E-TFCs 852. MAC-d flow data blocks are then multiplexed into a MAC-e PDU in the order of absolute priority until the maximum amount of data allowed by the selected E-TFC size is reached 854. Preferably only the amount of scheduled data allowed by the grant is adjusted to more closely match the selected E-TFC, Non-scheduled MAC-d flow data that is multiplexed maybe restricted to the non- scheduled grant. Padding is then applied to match the selected E-TFC size 856. With this scheme, data can be transmitted exceeding the scheduled and/or non- scheduled grants.

[0046] Figure 9 illustrates an increased size MAC-e PDU 900 that fully utilizes a selected E-TFC size that supports the current grants. A MAC-e PDU header 902 and MAC-d flow data blocks 904a-904c are supported by the current scheduled and non-scheduled grants. Referring to Figures 8A, 8B and 9, the MAC-d flow data blocks 904a-904c are multiplexed into a MAC-e PDU in accordance with an absolute priority until the maximum amount of data allowed by the current scheduled and non-scheduled grants is reached. As shown in Figure 9, three (3) MAC-d flow data blocks 904a-904c are multiplexed as an example, and any number of MAC-d flow data blocks may be multiplexed. The smallest possible E-TFC is selected from a set of supported E-TFCs that is larger than the size of the multiplexed MAC-e 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 by more than the smallest MAC-d flow multiplexing block size, one or more additional MAC-d flow data blocks 904d are added as shown in Figure 9 in accordance with the absolute priority until no further MAC-d flow data blocks and associated MAC-e header information can fit within the selected E-TPC size. Preferably, only scheduled MAC-d flow data is added exceeding the current grant, but non-scheduled MAC-d flow data may also be added. Padding 906 is then applied to match the selected E-TPC size. With this scheme, MAC-d flow multiplexing is optimized to take advantage of unused data bits that would have been filled with padding bits.

[0047] Figures 1OA and 1OB, taken together, is a flow diagram of a procedure 1000 for multiplexing whereby, in advance of MAC-e PDU multiplexing, the amount of data to multiplex according to the scheduled and/or non-scheduled grants is adjusted to more closely match the next larger or next smaller E-TFC size relative to the amount of data allowed to be multiplexed by the scheduled and/or non-scheduled grants. Figure 1OA identifies a method where only the amount of scheduled data to multiplex is adjusted to more closely match the selected E-TFC.

[0048] Referring to Figure 1OA, an E-TFC restriction procedure is performed (step 1005) to determine the set of supported E-TFCs including the largest possible E-TFC size (step 1010) by considering MAC-d flow power offset of the highest priority data available for transmission.

[0049] Still referring to Figure 1OA, if the largest possible E-TFC size resulting from E-TFC restriction, (considering remaining power and the highest priority MAC-d flow power offset), is determined in step 1015 to be less than the amount of data allowed by the scheduled and non-scheduled grants (remaining power limited case), the maximum possible payload for MAC-e PDU multiplexing is set to the largest possible E-TFC size (step 1020) whereby the maximum amount of scheduled data to multiplex is set to the amount of data specified by the scheduled grant (step 1025) and the maximum amount of non-scheduled data to multiplex is set to the amount of data specified by the non-scheduled grant

(step 1030).

[0050] Still referring to Figure 1OA, if the largest possible E-TFC size resulting from E-TFC restriction is determined in step 1015 greater than the amount of data allowed by the scheduled and non-scheduled grants (the grant limited case), the maximum amount of scheduled to multiplex is adjusted to match either the next larger or next smaller E-TFC size relative to the amount of available data allowed by the scheduled and non-scheduled grants (steps , 1040, 1045).

[0051] For example, rather than setting the maximum amount of scheduled data to multiplex to the amount of data allowed by the scheduled grant, the maximum amount of scheduled data is set to the selected E-TFC size minus the amount of available data allowed to be transmitted by the non-scheduled grants (step 1040), and the maximum amount of non-scheduled data to multiplex is set to the non-scheduled grant (step 1045) for each non-scheduled data flow. These methods, or other similar methods, result in setting the amount of multiplexed scheduled and non-scheduled data to match the selected E-TFC size, rather than setting the amount of multiplexed scheduled and non-scheduled data according to the associated grants.

[0052] Preferably, only the amount of data allowed to be multiplexed from scheduled MAC-d flows is increased or decreased to more closely match the selected E-TFC size. Optionally, the maximum possible payload for MAC-e PDU multiplexing is set to the size of the selected E-TFC. Other sequences of operation to pre-deteπnine the optimal amount of multiplexed scheduled and/or non-scheduled data in advance of multiplexing are also possible. [0053] Referring to Figure 1OB, MAC-d flows are then multiplexed in order of priority into the MAC-e PDU until the largest supported E-TFC size, the amount of data allowed by the scheduled and non-scheduled grants is reached, or all data available data for transmission on the MAC-d flow is multiplexed. In step 1050, the remaining total payload is set to the maximum possible MAC-e PDU payload, the remaining scheduled payload is set to the maximum scheduled data to multiplex, and the remaining non-scheduled payload is set to the

maximum non-scheduled data to multiplex.

[0054] The "remaining total payload" is the maximum possible payload resulting from E-TFC restriction, (i.e., the largest supported E-TFC). But it is important to note that this parameter is reduced for each multiplexed data block within the multiplexing loop in step 1060. When in the maximum E-TFC limited case, this parameter will cause the exit from the multiplexing loop in step 1065. The "remaining scheduled payload" and the "remaining non-scheduled payload" are the remaining scheduled and non-scheduled data that are initially set to the maximum allowed to multiplex for that type of data. Then these parameters are reduced each time data of that type is multiplexed. They will also cause an exit from the multiplexing loop in step 1065 for the grant limited case. The highest priority data available is selected for transmission.

[0055] In step 1055, for each scheduled channel of this priority, the minimum of the remaining total payload, the remaining scheduled payload and the available data on this channel is multiplexed. The remaining total payload and the remaining scheduled payload is decreased by the amount of the data multiplexed. In step 1060, for each non-scheduled channel of this priority, the minimum of the remaining total payload, the remaining non-scheduled payload and the available data on this channel is multiplexed. The remaining total payload and the remaining scheduled payload is decreased by the amount of the data multiplexed.

[0056] If it is determined in step 1065 that the remaining total payload is zero, or the remaining scheduled payload and the remaining non-scheduled payload is zero, or there is no more data available for transmission, the smallest possible E-TFC size that supports the size of the multiplexed data is selected, and padding is added to the MAC-e PDU to match this size if necessary (step 1070). Otherwise, the next lower priority data available for transmission is selected in step 1075. It should be noted that rather then selecting the next lower priority in step 1075, it is also possible just to select the highest priority logical channel that has not been serviced, and continue the multiplexing loop until all logical channels are serviced.

[0057] In another embodiment as illustrated in Figures HA and HB taken together, a power offset of the selected MAC-d flow is identified, step 1301. Using the power offset, a maximum supported payload, such as the largest supported E- TFC that can be sent by the WTRU based on the offset and the remaining power allowed for E-DCH data is identified. This can be referred to as the E-TFC restriction procedure, step 1302. A variable, "Remaining Payload", is initially set to the maximum supported payload, step 1303. Based on the scheduled grant, a variable, "Remaining Scheduled Payload", is set to the largest payload that can be transmitted according to the scheduled grant and the power offset, step 1304. For each MAC-d flow with a non-scheduled grant, a variable, "Remaining Non- scheduled Payload", is set to the value of the grant, step 1305. A variable, "Non- scheduled Payload", is the amount of non-scheduled data that can be transmitted and is based on a sum of non-serving grants and the available data on each of these non-scheduled MAC-d flows, step 1306.

[0058] If the "Remaining Payload" is larger than the sum of the amount of available data allowed to be transmitted by the "Remaining Scheduled Payload", "Remaining Non-scheduled Payload" including any MAC header information and control signaling overhead, the next smaller supported E-TFC is selected based on the sum, step 1307. If the "Remaining Payload" is not larger than the sum, the largest supported E-TFC is used to limit the amount of multiplexed data. In the case that there is no "Scheduled Payload", the selected E-TFC will be the largest supported E-TFC, as the "Remaining Payload" will not be larger than the sum. This allows for the transfer of all "Non-Scheduled" payload unless the E- TFC is restricted to not permit this transfer.

[0059] The next smaller supported E-TFC is the largest supported E-TFC that does not carry more data than the sum. In other words, the selected E-TFC is the next smaller E-TFC based on the serving grant, non-scheduled grants, the power offset, available data, including any MAC header information and control signaling overhead, such as scheduling information. The "Remaining Scheduled Payload" is set to the size of the selected E-TFC, which can also be referred to as a "quantized sum", minus the "Non-scheduled Payload" and any MAC header

information and control signaling overhead, step 1308. By setting the "Remaining Scheduled Payload this way, only the scheduled data is quantized. The "Non-scheduled Payload" is reserved within the selected E-TFC according to the non-scheduled grants. Based on its priority, each logical channel and their associated MAC-d flow is multiplexed on to the MAC-e/es PDU, step 1309. [0060] If the MAC-d flow of the logical channel applies to a non-scheduled grant, the MAC-e/es PDU is filled with the MAC-d flow data from this logical channel up to the minimum of "Remaining Non-scheduled Payload", "Remaining Payload" or the available MAC-d flow data for that logical channel is filled, step 1310. The bits used to fill the MAC-e/es PDU are subtracted from the "Remaining Payload" and the "Remaining Non-scheduled Payload", taking into account any MAC header information and control signaling overhead. If the MAC-d flow applies to a scheduled grant, the MAC-e/es PDU is filled with the MAC-d flow data from this logical channel up to the minimum of "Remaining Scheduled Payload", "Remaining Payload" or the available MAC-d flow data for that logical channel is filled, step 1311. The bits used to fill the MAC-e/es PDU are subtracted from the "Remaining Payload" and "Remaining Scheduled Payload", taking into account any MAC header information and control signaling overhead, step 1312. The process is repeated for all logical channels, or until the "Remaining Non-scheduled Payload" and "Remaining Scheduled Payload" are both used up, or "Remaining Payload" is used up, or there is no more available data to transmit step 1313. The MAC control signaling overhead such as scheduling information is added to the PDU and the PDU is padded to the selected E-TFC size, step 1314.

[0061] This procedure allows the UE operation to be "deterministic" and the Node-B scheduler can therefore accurately predict how resource grants will be used by the UE. As a result, the Node-B can more efficiently allocate resources. It is desirable to have the amount of multiplexed data adjusted (quantized) so that: first, physical resources are more efficiently utilized and second increased data rates are achieved. In order to accomplish this, it is necessary in the grant limited case that the E-TFC is selected based on the

current grants, and this payload size is used to quantize the amount of scheduled data allowed by the grant before multiplexing of the MAC-e/es PDU. Better physical resource utilization and increased data rates is achieved by effecting the E-TFC selection and the multiplexing algorithm.

[0062] Figure 13 is a block diagram illustrating a simplified architecture for EU multiplexing. At the WTRU 1414, MAC-d flows 1403 for various logical channels 1402 are provided to the MAC-e/es 1404 by the MAC-d 1401. An E-TFC selection device 1405 selects an E-TFC for EU transmissions, such as on a enhanced dedicated channel (E-DC) TTI basis. The E-TFC selection device 1405 receives inputs, such as scheduled grants (SG) 1406, non-scheduled grants (NSG) 1407, power offsets (PO) 1408, MAC header information and control signaling overhead (MAC CONTROL) 1409, buffer occupancy 1422 of MAC-d flows mapped to the E-DCH, and supported E-TFCs (or remaining E-DCH power to perform the E-TFC restriction procedure). Also, "Grant Quantization" that adjusts the maximum amount of multiplexed data allowed by the resource grants can occur between E-TFC selection 1405 and the multiplexer (MUX) 1410. A multiplexer (MUX) 1410 multiplexes the MAC-d flows 1403 for transmission according to the grants that have been quantized to more closely match the selected E-TFC . The MUX 1410 multiplexes the MAC-d flows 1403 adds header information 1409 and adds padding, if needed, to match the selected E-TFC size. The MAC-e/es PDUs 1411 produced by the MUX 1410, the selected E-TFC and power offset are provided to a physical layer device (PHY) 1412 for transmission over the E- DPCH(s) 1413 using the selected E-TFC.

[0063] At the base station/Node-B and Radio Network Controller (RNC)

1415, the E-DPCH(s) 1413 are received and processed by a PHY 1416 of the base station/Node-B 1415. The MAC-e/es PDUs 1417 as produced by the PHY 1416 are demultiplexed into the constituent MAC-d flows 1419 and logical channels 1420 by a demultiplexer (DEMUX) 1418 of the MAC-e/es 1420. The MAC-d flows 1419 are delivered to the MAC-d 1421.

[0064] Figures 13A and 13B, taken together, is a flow diagram of a multiplexing procedure 1100 in which the amount of multiplexed scheduled

and/or non-scheduled data is adjusted to more closely match the next higher or next lower E-TFC size while performing data multiplexing. Within the order of priority multiplexing loop shown in Figure 1OB, if the amount of data to multiplex is limited by the grant, the amount of data to multiplex is adjusted according to the next larger or smaller E-TFC size according the amount of data allowed to be multiplexed by the sum of the grants.

[0065] Referring to Figure 13A, in step 1105, the remaining total payload is set to the maximum possible MAC-e PDU payload, the remaining scheduled payload is set to the maximum scheduled data to multiplex, and the remaining non-scheduled payload is set to the maximum non-scheduled data to multiplex. [0066] If the remaining scheduled payload is less than or equal to the remaining total payload, as determined in step 1110 and, optionally, the remaining non-scheduled payload and non-scheduled data is greater than zero (step 1115), the next smaller or larger E-TFC size is selected relative to the amount of data already multiplexed (including MAC header overhead) plus the remaining scheduled payload (step 1120). The remaining scheduled payload is equal to the selected E-TFC size minus the amount of data already multiplexed (including MAC header overhead).

[0067] In step 1125, for each scheduled channel of this priority, the minimum of the remaining total payload, the remaining scheduled payload and the available data on this channel is multiplexed. The remaining total payload and the remaining scheduled payload is decreased by the amount of the data multiplexed.

[0068] Referring to Figure 13B, in step 1130, for each non-scheduled channel of this priority, the minimum of the remaining total payload, the remaining non-scheduled payload and the available data on this channel is multiplexed. The remaining total payload and the remaining scheduled payload is decreased by the amount of the data multiplexed.

[0069] If it is determined in step 1135 that the remaining total payload is zero, or the remaining scheduled payload and the remaining non-scheduled payload is zero, or there is no more data available for transmission, the smallest

possible E-TFC size that supports the size of the multiplexed data is selected, and padding is added to the MAC-e PDU to match this size if necessary (step 1140). Otherwise, the next lower priority data available for transmission is selected in step 1145. It should be noted that rather then selecting the next lower priority in step 1145, it is also possible just to select the highest priority logical channel that has not been serviced.

[0070] Figure 14 is a flow diagram of a multiplexing procedure 1200 in accordance with another embodiment. In the grant limited case, MAC-d flow data is multiplexed in to a MAC-e PDU until the amount of data allowed to be multiplexed by the scheduled or non-scheduled grant associated with each MAC- d flow is reached.

[0071] Before padding the MAC-e PDU to match the selected E-TFC size, more MAC-d flow data is multiplexed if the multiplexing block size, (the MAC-d PDU size), is less than the amount of padding required to match the next larger E-TFC size relative to the amount of data allowed by the scheduled and non- scheduled grants. Preferably for the additional multiplexing, only scheduled data of the highest priority that is available for transmission is used, and non- scheduled multiplexed data remains limited by the non-scheduled grants. [0072] Alternatively, multiplexed data is reduced to support the next lower

E-TFC size relative to the amount of data allowed by the scheduled and non- scheduled grants, if the multiplexing block size, (the MAC-d PDU size), is less than the amount of needed padding to the next higher E-TFC size. Optionally padding thresholds other than the multiplexing block size for reducing the E-TFC size can also be considered, or the required padding to match the next lower E- TFC size being less than the larger E-TFC by some margin could be used as a criteria for reducing the E-TFC size.

[0073] References to the amount of data multiplexed according to grants, and the amount of data that can be multiplexed according to a selected E-TFC takes into account MAC header information and other control signaling overhead required in the formatting of a MAC-e PDU. [0074] Referring to Figure 14, the smallest possible E-TFC size is selected

that supports the size of the already multiplexed data (including MAC header overhead) (step 1205). If the remaining scheduled payload and the remaining non-scheduled payload is equal to zero (optional step 1210), the remaining total payload is equal to the selected E-TFC size minus the amount of the data already multiplexed (including MAC header overhead) (step 1215).

[0075] If the remaining total payload is greater than or equal to the multiplexing block size of each MAC-d flow, as determined in step 1220, for each scheduled channel of this priority, the minimum of the remaining total payload and the available data on this channel is multiplexed, and the remaining total payload and the remaining scheduled payload is decreased by the amount of data multiplexed (step 1225). In step 1230, the next lower priority scheduled data available for transmission is selected. In step 1235, padding is added to the

MAC-e PDU if necessary to match the size of the selected E-TFC.

[0076] Any combination of the above embodiments may also be applied to achieve improved multiplexing efficiency and radio resource utilization.

[0077] Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention.

[0078] EMBODIMENTS

[0079] First Group

[0080] A method comprising quantizing data so that the quantized data more closely matches a block size.

[0081] The method of any prior first group embodiment wherein the block size is a transport block size.

[0082] The method of any prior first group embodiment wherein the block size is an enhance uplink transport block size (E-TFC).

[0083] The method of any prior first group embodiment wherein the quantized data is based on a scheduled grant.

[0084] The method of any prior first group embodiment wherein the

quantized data is based on a non-scheduled grant.

[0085] The method of any prior first group embodiment wherein the quantized data is based on a serving grant.

[0086] The method of any prior first group embodiment wherein the quantized data is scheduled data.

[0087] The method of any prior first group embodiment wherein the quantized data is non-scheduled data.

[0088] The method of any prior first group embodiment wherein the data is medium access control dedicated channel (MAC-d) flows.

[0089] The method of any first group embodiment wherein the data is packet data units (PDUs).

[0090] The method of any prior first group embodiment wherein the data is medium access control dedicated channel (MAC-d) packet data units (PDUs).

[0091] The method of any prior first group embodiment wherein the quantized data is based on a power offset.

[0092] The method of any prior first group embodiment wherein the quantized data is based on scheduling information.

[0093] The method of any prior first group embodiment wherein the quantized data is based on medium access control header information.

[0094] The method of any prior first group embodiment comprising selecting a block size.

[0095] The method of any prior first group embodiment comprising selecting a block size associated with a transport format combination (TFC).

[0096] The method of any prior first group embodiment comprising selecting a block size associated with an enhanced uplink transport format combination (E-TFC).

[0097] The method of any prior first group embodiment wherein a selected block size is based on a scheduled grant.

[0098] The method of any prior first group embodiment wherein a selected block size is based on a non-scheduled grant.

[00991 The method of any prior first group embodiment wherein a selected

block size is based on a serving grant.

[00100] The method of any prior first group embodiment wherein a selected block size is based on medium access control header information.

[00101] The method of any prior first group embodiment wherein a selected block size is based on scheduling information.

[00102] The method of any prior first group embodiment wherein a selected block size is based on a power offset.

[00103] The method of any prior first group embodiment wherein a selected block size is based on a buffer occupancy.

[00104] The method of any prior first group embodiment wherein a selected block sized is selected from a plurality of block sizes and the selected block size is a next smaller block size.

[00105] The method of any prior first group embodiment wherein a selected block sized is selected from a plurality of block sizes and the selected block size is a next larger block size.

[00106] The method of any prior first group embodiment wherein a selected block sized is selected from a plurality of block sizes and the selected block size is based on an amount of data to be transmitted and is the block size out of the plurality of block sized that is a largest that does not exceed the amount of data.

[00107] The method of any prior first group embodiment wherein a selected block sized is selected from a plurality of block sizes and the selected block size is based on an amount of data to be transmitted and is the block size out of the plurality of block sized that is a smallest that exceeds the amount of data.

[00108] The method of any prior first group embodiment wherein padding is added to the quantized data.

[00109] The method of any prior first group embodiment wherein the quantized data is transmitted.

[00110] The method of any prior first group embodiment wherein the quantized data is transmitted on an enhanced dedicated channel.

[00111] The method of any prior first group embodiment being performed for a code division multiple access air interface.

[00112] The method of any prior first group embodiment being performed for a frequency division duplex code division multiple access enhance uplink communication.

[00113] The method of any prior first group embodiment being performed by a wireless transmit/receive unit.

[00114] The method of any prior first group embodiment being performed by a user equipment.

[00115] The method of any prior first group embodiment wherein the quantized data is received by a base station.

[00116] The method of any prior first group embodiment wherein the quantized data is received by a node-B.

[00117] The method of any prior first group embodiment wherein the quantized data is received by a radio network controller.

[00118] Second Group

[00119] A wireless transmit/receive unit (WTRU) comprising a physical layer.

[00120] The WTRU of any prior embodiment of the second group wherein the WTRU is a user equipment.

[00121] The WTRU of any prior embodiment of the second group comprising a medium access control - dedicated channel (MAC-d) means.

[00122] The WTRU of any prior embodiment of the second group comprising a multiplexing means.

[00123] The WTRU of any prior embodiment of the second group wherein a multiplexing means multiplexes medium access control - dedicated channel

(MAC-d) flows into medium access control - enhanced uplink (MAC-e) packet data units (PDUs).

[00124] The WTRU of any prior embodiment of the second group comprising an e-TFC selection means.

[00125] The WTRU of any prior embodiment of the second group comprising an e-TFC selection means for selecting an E-TFC out of a plurality of E-TFCs.

[00126] The WTRU of any prior embodiment of the second group comprising

a MAC-e/es.

[00127] The WTRU of any prior embodiment of the second group wherein a

MAC-e/es comprises a multiplexing means and an E-TFC selection means.

[00128] The WTRU of any prior embodiment of the second group wherein the physical layer produces an enhanced dedicated physical channel for transmission.

[00129] The WTRU of any prior embodiment of the second group for performing steps of methods out of the embodiments of the first group, excluding the embodiments involving the base station, Node-B or RNC.

[00130] The WTRU of any prior embodiment of the second group comprising means for performing the steps of methods out of the embodiments of the first group, excluding the embodiments involving the base station, Node-B or RNC.

[00131] Third Group

[00132] An infrastructure component comprising a physical layer.

[00133] The infrastructure component of any prior embodiment of the third group wherein the infrastructure component comprises a base station.

[00134] The infrastructure component of any prior embodiment of the third group wherein the infrastructure component comprises a Node-B.

[00135] The infrastructure component of any prior embodiment of the third group wherein the infrastructure component comprises a Node-B and a RNC.

[00136] The infrastructure component of any prior embodiment of the third group comprising a demultiplexing means.

[00137] The infrastructure component of any prior embodiment of the third group comprising a demultiplexing means for demultiplexing enhance uplink medium access control packet data units into medium access control- dedicated channel flows.

[00138] The infrastructure component of any prior embodiment of the third group comprising a medium access control - dedicated channel means.

[00139] The infrastructure component of any prior embodiment of the third group comprising a medium access control - dedicated channel means for receiving medium access control — dedicated channel flows.

[00140] The infrastructure component of any prior embodiment of the third group wherein the physical layer receives an enhanced dedicated physical channel.

[00141] The infrastructure component of any prior embodiment of the third group comprising demultplexing means for demultiplexing receiving medium access control enhanced uplink packet data units as produced by embodiments of the first group.