Wireless transmit/receive unit

Wireless transmitting/receiving unit

This application is related to wireless communication.

The wireless communication system following the Universal Mobile Telecommunications System (UMTS) technology has been developed as part of the third generation (3G) radio system and is maintained by the third generation partnership project (3GPP). In Figure 1, a typical UMTS system architecture based on the current 3GPP specifications is described. The UMTS network architecture includes a core network (CN), which is interconnected with the UMTS Terrestrial Radio Access Network (UTRAN) via an Iu interface. UTRAN is configured to use a wireless transmitting/receiving unit (wireless transmitting/receiving unit) called user equipment (UE) in the 3GPP standard to provide users with wireless telecommunication services via the Uu radio interface. The commonly used air interface defined in the UMTS standard is Wideband Code Division Multiple Access (W-CDMA). UTRAN has one or more radio network controllers (RNCs) and base stations. The base stations are called Node Bs by 3GPP, which centrally provide UEs for geographic coverage of wireless communications. Uplink (UL) communication refers to transmission from UE to Node B, and downlink (DL) communication refers to transmission from Node B to UE. One or more Node Bs are connected to each RNC via the Iub interface; multiple RNCs in a UTRAN communicate via the Iur interface.

According to the 3GPP standard version 6 for high-speed uplink packet access (HSUPA), the MAC layer multiplexes higher-layer data into MAC-e PDUs. In a transmission time interval (TTI), the MAC layer sends a MAC-ePDU to the PHY layer. The MAC-e PDU will be transmitted on the enhanced dedicated channel (E-DCH) or dedicated physical data control channel (E-DPDCH). transmission. As part of link adaptation, the MAC layer is based on radio link control (RLC) logical channel priority, RLC buffer occupancy, physical channel conditions, service authorization, non-service authorization, power limitation, and hybrid automatic repeat request (HARQ) characteristics File (porfile) and logical channel multiplexing to perform enhanced transmission format combination (E-TFC) selection.

As part of the E-TFC selection function, the UE initially identifies the higher-level MAC-d stream with the highest priority, which has the data to be transmitted. The UE then identifies one or more MAC-d flows, it is allowed to multiplex with this MAC-d flow and its authorization allows them to be transmitted in the current TTI. Based on the HARQ profile of the selected MAC-d flow, the UE identifies the power offset used for transmission. Based on the power offset and the E-TFC restriction process, the MAC determines the maximum supported MAC-ePDU size or E-TFC that can be sent by the UE for the upcoming transmission, which is called the maximum supported payload, which is based only on the available power , Without considering available services and/or non-service authorizations. Then the E-TFC selection algorithm determines the maximum amount of data that can be transmitted based on the service authorization and the selected power offset, which is called the predetermined payload. In the case of unscheduled flows, the E-TFC selection algorithm considers unscheduled authorizations to determine unscheduled payloads. The total authorized payload is equal to the determined scheduled and unscheduled payloads, and is defined as the amount of data that the UE is allowed to transmit based on service and non-service authorization. However, due to the fact that the UE can have limited power, the amount of available data (available payload) that the UE can transmit is equal to the minimum value between the maximum supported payload and the total authorized payload.

Once the available payload is determined, the MAC layer needs to request information from the corresponding logical channel of the MAC-d flow, which is allowed to be multiplexed into the current TTI in the order of priority. When all the data to fill the MAC-e PDU based on the available payload is available, or when there is no longer RLC data available, the MAC-e PDU is sent to the physical layer together with the selected β factor for transmission on the E-DPDCH, The selected B factor is the gain factor.

According to 3GPP Release 6, the radio link control (RLC) layer can only use a fixed RLC protocol data unit (PDU) size to operate in the confirmed mode. In addition, the high-speed medium access control (MAC-hs) entity in the Node B and the medium access control (MAC-e/es) entity in the UE do not support the segmentation of the service data unit (SDU) from the higher layer. These constraints may lead to performance limitations, especially as high-speed packet access (HSPA) evolves to higher speeds. In order to achieve higher data rates and reduce protocol load and padding, a number of new features have been introduced to the layer 2 (L2) protocol in 3GPP Release 7. In particular, flexible RLC PDU size and MAC segmentation are introduced in the downlink. However, in 3GPP Release 7, no corresponding L2 enhancements have been introduced for uplink operation.

Recently, a new 3GPP work project has been proposed for the improved L2 uplink, thereby introducing enhancements in L2 uplink operation. Some of the goals of the improved L2 uplink include: support for flexible RLC PDU size; support for MAC segmentation of higher-layer PDUs, where the higher-layer PDU includes MAC-d and MAC-c PDUs; in the old and new protocol formats Smooth transitions between CELL_DCH, CELL_FACH, CELL_PCH and URA_PCH states are supported, depending on the potential enhancement of CELL_FACH uplink transmission.

The current E-TFC selection algorithm is designed for the current 3GPP standard version including version 7 or earlier and the current enhanced dedicated channel (E-DCH) function that requires a fixed RLC PDU size. It has been recognized that the current E-TFC selection algorithm used in version 7 or earlier will cause the inefficiency of MAC-e/es PDU generation under the proposed improved layer 2 uplink. This is due to the current E-TFC selection algorithm. The TFC selection algorithm design does not take into account the flexible RLC PDU size based on the number of RLC PDUs in the enhanced MAC-es PDU, the segmentation of the RLC PDU, and the flexible header format size for each logical channel.

Therefore, a new E-TFC selection function is expected, which considers some additional functions when generating a MAC-e PDU with the best RLC PDU size, including flexible RLC PDU size, RLC PDU segmentation, and flexible standardization. Header format size.

A method and apparatus for enhanced transport format combination (E-TFC) for uplink wireless communication are disclosed. The proposed technology for E-TFC selection supports flexible radio link control (RLC) packet data unit (PDU) size, and also supports MAC-d PDU media access control (MAC) layer segmentation. Thus, the generated RLC PDU is completely suitable for the size of the selected E-TFC transport block. Based on the selected E-TFC, the MAC entity and the RLC entity work together on the basis of the transmission time interval (TTI) to generate the RLCPDU size, thereby maximizing the amount of data to be transmitted and reducing the amount of data between the RLC and the MAC agreement. Load.

Provides a method to fill the enhanced MAC-e packet data unit (PDU) with data from the logical channel as part of the E-TFC selection. In one embodiment, the E-TFC selection algorithm uses a separate request from the MAC layer to the RLC layer to request the number of bits allowed to be sent for the logical channel to generate one or more PDUs of possibly different sizes. In another embodiment, the MAC entity performs multiple requests to the RLC entity. In another embodiment, the MAC entity sends a single request to the RLC entity to generate one or more PDUs of a set size. It also provides a technique for maintaining a guaranteed bit rate (GBR) for unscheduled data flows with variable-length headers.

The "wireless transmitting/receiving unit (wireless transmitting/receiving unit)" mentioned below includes but not limited to user equipment (UE), mobile station, fixed or mobile subscriber unit, pager, cellular phone, personal digital assistant (PDA) , Computer or any other type of user equipment capable of operating in a wireless environment. The "base station" mentioned below includes but is not limited to Node-B, site controller, access point (AP) or any other type of interface device capable of operating in a wireless environment.

Efficient Enhanced Transport Format Combination (E-TFC) selection algorithm is provided. The E-TFC selection algorithm takes into account the new functions added to the Layer 2 protocol as the proposed 3GPP improved Layer 2 (L2) uplink Part of the link work project. The proposed implementation for E-TFC selection describes when the wireless transmit/receive unit needs to be filled with data from one or more radio link control (RLC) logical channels or MAC-d and MAC-c data streams. Type of MAC-e packet data unit (PDU), the sequence of events that the wireless transmit/receive unit can follow. The proposed implementation for E-TFC selection can be used alone or in any combination. Although E-TFC selection is described as being performed by a wireless transmit/receive unit or UE for uplink communication, both downlink and uplink communications can apply the teachings here and can be performed by base stations, Node Bs, or Performed by Node B combined with Radio Network Controller (RNC).

Here, enhanced MAC-e, enhanced MAC-es, and enhanced MAC-e/es are used to represent the enhanced version of the existing media access control (MAC) protocol in high-speed packet access (HSPA). The MAAC agreement includes but not limited to MAC-e, MAC-es and MAC-e/es. The remaining available payload refers to the maximum amount of data that can be transmitted due to available licenses, available power, selected power offset, and scheduling information, where available licenses include service or non-service licenses. The remaining authorized payload refers to the remaining unscheduled payload when the unscheduled MAC-d is being processed and the remaining scheduled payload for the scheduled MAC-d flow. Here, the function MIN (A, B) returns the minimum value from the parameters A and B according to the number of bits.

The higher layer PDU refers to MAC-d PDU, MAC-c PDU or RLC PDU. In the implementation proposed here, MAC-d, MAC-c and RLC PDU can be treated equally. The RLC PDU belongs to a dedicated logical channel and is forwarded to the MAC-d entity. Then, the MAC-d entity forwards the data to the enhanced MAC-es entity. The output of MAC-d is called MAC-d PDU. MAC-d PDU includes data received from a dedicated control channel (DCCH) or a dedicated traffic channel (DTCH) logical channel, while MAC-c PDU includes data received from a public channel such as a public control channel (CCCH). For convenience, some implementations here will be described with reference to RLC PDU, however, these implementations can also be applied to MAC-d or MAC-cPDU, and have the same for RLC, MAC-d and MAC-c PDU Function.

Figure 2 shows a block diagram of an enhanced RAC-e/es entity 200 according to the teachings herein. The enhanced RAC-e/es entity 200 multiplexes the data from the logical channels of higher-layer entities into enhanced MAC-e PDUs and provides them in the form of transport blocks (TB) to the physical (PHY) layer entity. Higher layer entities include MAC-d, MAC-c, and Radio Link Control (RLC) entities. The enhanced MAC-e/es entity 210 may include the following entities: a hybrid automatic repeat request (HARQ) entity 222, a segmentation entity 214 including a segment buffer 216, a multiplexer and TSN setting entity 218, a scheduling entity 220, And an enhanced transport format combination (E-TFC) selection entity 212.

The HARQ entity 222 is responsible for processing MAC layer functions related to the HARQ protocol for error correction, including storage and retransmission of enhanced MAC-e payloads. When the higher layer PDU is too large to fit the enhanced MAC-e PDU, the segmentation entity 214 segments the higher layer PDU and then sends the segment to the multiplexer 218. The remaining segments are stored in the segment buffer 216. The multiplexer and TSN setting entity 218 is responsible for sequentially concatenating multiple enhanced MAC-es SDUs including segmented or complete higher layer PDUs into the enhanced MAC-es PDU. The multiplexer and TSN setting entity 218 also multiplex multiple enhanced MAC-es PDUs from the multiplexed logical channels into MAC-e PDUs to provide them to the PHY layer for use in the next transmission time interval ( TTI) The transmission is performed as instructed by the E-TFC selection entity 212. The scheduling entity 220 is responsible for the routing of related uplink signaling. The E-TFC selection entity 212 determines how much data can be sent in a TTI based on scheduling information, relative authorization (RG), absolute authorization (AG), service authorization (SG), and available power resources, and determines E-TFC restrictions The E-TFC limit is used to determine the maximum available data that the UE can send based on the available power. The E-TFC selection entity 212 also controls the multiplexer 218.

In one embodiment, the E-TFC selection algorithm uses a single request from the MAC layer to the RLC layer. The enhanced MAC entity requests from the logical channel the number of bits in a single request that it is allowed to send on the logical channel. Based on the indicated number of bits, the number of available data bits, and the number of new or retransmitted data bits, the RLC entity generates or transmits RLC PDUs to suit the enhanced MAC-e PDU. Based on the scheduling information and the E-TFC restrictions, scheduling authorizations and non-scheduling authorizations of all MAC-d flows, the wireless transmitting/receiving unit determines the maximum amount of data that can be transmitted, which is called the remaining available payload. The remaining available payload can be used to calculate the quantization loss used for scheduled transmission when the logical channel bits are used to fill the enhanced MAC-e PDU. Once the remaining available payload is calculated, if scheduling information needs to be sent, then the schedule information will be subtracted from the remaining available payload.

The E-TFC selection algorithm generates enhanced MAC-e PDUs for each logical channel according to one or more of the following rules. These rules can be used alone or in combination. According to a rule, the bits in the segmented buffer have transmission priority over the RLC PDUs of other logical channels being processed. According to another rule, if the segment in the segmentation entity is greater than the maximum number of data to be transmitted in the logical channel, the wireless transmitting/receiving unit can further segment the MAC segment and send it in the enhanced MAC-e PDU. The maximum amount of data sent, taking into account the enhanced MAC-e/es header.

According to another rule, any remaining segments can be stored in the segment buffer. According to another rule, if there is no segment in the segment buffer, or after adding a segment, there is still free space in the enhanced MAC-e PDU, the MAC entity can request the maximum number of bits allowed to be transmitted from the logical channel. The number of yuan, which is determined by the remaining available payload and the remaining authorized payload minus the size of any added segments. The added segments include any MAC headers that need to be sent if a segment is added Bit. The RLC entity may then provide one or more new RLC PDUs with the optimal selected size and/or one or more retransmitted RLC PDUs equal to or greater than the requested number of bits.

According to another rule, when one or more RLC PDUs are provided, the last RLC PDU will exceed the maximum allowable or usable number of bits for logical channels or MAC-d streams, taking into account the space required by the MAC header. At this time, the higher-layer PDU may be segmented by the segmentation entity, where the higher-layer PDU may be an RLC MAC-d or MAC-c PDU.

According to another rule, the number of data to be transmitted and the corresponding enhanced MAC-e/es header cannot exceed the maximum allowable number of bits for the logical channel. The maximum allowable number of bits is the available remaining payload or available authorization Payload, which is indicated by authorization and/or E-TFC restrictions. Since the enhanced MAC-e/es header is flexible and depends on the number of RLC PDUs in the enhanced MAC-e/es service data unit (SDU), the E-TFC selection entity must also consider additional enhancements Type MAC-es SDU with additional header added. This can be taken into account in the initial request to RLC performed by the enhanced MAC-e/es entity. For example, enhanced MAC-e/es may assume that K RLC PDUs will be received for the number of remaining available bits. Therefore, the enhanced MAC-e/es can calculate the number of bits requested according to the following formula: number of bits requested = (available bits that can be transmitted)-K × (number of additional header bits per RLC PDU )-(The number of fixed header bits used for this logical channel). Alternatively, the RLC entity may consider the number of additional header bits required for each new RLC PDU generated, and the MAC only requests the number of available bits from the logical channel. For example, after receiving a MAC request, for each new RLC generated or transmitted PDU, the RLC entity can subtract additional header bits from the total remaining bits that need to be forwarded to the enhanced MAC-e/es.

Figures 3A and 3B show a flowchart of a process 300 for filling an enhanced MAC-e PDU with data from a logical channel according to one embodiment, the process 300 being part of the E-TFC selection and following the above The rules listed. In Figures 3A and 3B, h1 refers to the number of header bits required by each enhanced MAC-es PDU, and h2 refers to the number of header bits required by each enhanced MAC-es SDU for enhanced The number of header bits of the MAC-e header.

In step 305, in each TTI, each logical channel that is allowed to be transmitted and meets the multiplexing restriction in the current TTI is estimated according to the priority order. In step 310, it is determined whether the segment buffer contains bits or segments to be transmitted. If the segment buffer contains bits or segments to be transmitted, then it is determined in step 315 whether the number of bits in the segment plus the corresponding h1+h2 bit enhanced MAC-e/es header is greater than MIN (Remaining available payload, remaining authorized load). If the result of step 315 is true, then in step 320, the segment is further segmented to generate sub-segments with a quantity equal to MIN (remaining available payload-(h1+h2), remaining authorized Payload-(h1+h2)) bits. In step 325, the sub-segment and the corresponding enhanced MAC-e/es header are added to the enhanced MAC-e PDU, and the number of bits added is subtracted from the remaining authorized payload and remaining available payload . The number of bits added is equal to the number of bits in the sub-segment + h1 + h2. If it is determined in step 328 that there is no more free space in the enhanced MAC-e PDU or the remaining available payload is zero, then the process 300 ends. Otherwise, the process 300 returns to step 305 to repeat the process for the next logical channel.

If, as determined in step 315, the number of bits in the segment + h1 + h2 is less than MIN (remaining available payload, remaining authorized payload), then in step 330 the segment and the corresponding enhanced MAC-e The /es header is added to the enhanced MAC-e PDU, and the number of bits added is subtracted from the remaining authorized payload and remaining available payload. The number of bits added is the number of bits in the segment + h1 + h2. In step 335, if there is still room in the enhanced MAC-e PDU, the bit of MIN (remaining available payload, remaining authorized payload) can be requested from the RLC logical channel. In addition, when the remaining grant payload is greater than zero and there is still room in the enhanced MAC-e PDU, bits can be requested from the RLC logical channel.

Optionally, the enhanced MAC-e/es header may be considered in the request to the RLC entity or the request issued by the RLC entity. More specifically, the RLC entity may only consider the enhanced MAC-e header added in each RLC PDU. When calculating the size of the RLC PDU to be generated, the UE subtracts the enhanced MAC-e header part h2 of each RLC PDU generated or retransmitted by the UE from the number of available bits requested. Alternatively, the RLC entity may also consider adding an enhanced MAC-es header to all RLC PDUs submitted to the enhanced MAC entity. Therefore, initially the RLC entity subtracts h1 from the requested number of bits, and then continues to generate RLC PDUs, where N is also considered for each RLC PDU generated. However, since the RLC entity does not know whether the enhanced MAC entity has segments added from the logical channel and whether the enhanced MAC-es header part for the logical channel has been considered, it is better for the enhanced MAC entity to follow The enhanced MAC-es header is considered before the logical channel requests data.

If it is determined in step 310 that there are no bits to be transmitted in the segmented buffer, then in step 340, a number of bits equal to MIN (remaining authorized payload, remaining available payload) is requested from the RLC logical channel. Optionally, before requesting data from the logical channel, the enhanced MAC entity may subtract the enhanced MAC-es header from the remaining authorized payload and the remaining available payload. With this choice, the RLC entity only needs to consider the enhanced MAC-e header part for each RLC PDU it generates. If the enhanced MAC entity does not subtract the enhanced MAC-es header part, the RLC can take it into consideration when generating the RLC PDU.

After steps 335 and 340, it is determined in step 350 whether an RLC PDU is provided from the requested RLC logical channel. If the requested RLC logical channel does not provide an RLC PDU, the process 300 returns to step 305 for repeating the process for the next logical channel. If the RLC logical channel provides bits, it is determined in step 355 whether the size of the transmitted one or more RLC PDUs plus the MAC-e header part is greater than the requested number of bits. For example, if N RLC PDUs are delivered, where N is greater than or equal to 1, then the enhanced MAC-e header part to be added is equal to N times the number of bits h2, and the sum is compared with the number of bits requested, The number of bits requested may be equal to MIN (remaining authorized payload, remaining available payload). If the number of transfer bits from the RLC logical channel plus the N×h2 bit enhanced MAC-e header part is less than the requested number of bits, then in step 370, the number of bits from the transferred one or more RLCPDUs Bits are added to the enhanced MAC-e PDU until the number of bits is equal to MIN (remaining authorized payload, remaining available payload).

If the number of transfer bits from RLC plus the enhanced MAC-e header part is greater than the number of requested bits, then in step 360, according to the requested number of bits, one or more complete RLC PDUs are added To the enhanced MAC-e PDU, and then according to the remaining available and authorized space, the last RLC PDU is segmented and added to the enhanced MAC-ePDU. More specifically, one or more complete RLC PDUs are added, so that the sum of the RLC PDU plus the enhanced MAC-e header of each RLC PDU is less than the number of request bits. The remaining available space according to the bits used for the last RLC PDU segmented is determined by the minimum of x1 and x2, where x1=remaining grant payload-(the size of the RLC PDU added to the enhanced MAC-e +h2 added for each RLC PDU2-h2 of the segment to be added), and x2=remaining available payload-(RLC PDU added to the enhanced MAC-e+h2 added for each RLC PDU2-segment to be added H2). In step 365, the remaining segments or bits are stored in the segment buffer.

After each of steps 365 and 370, the total number of bits added to the enhanced MAC-e PDU including the bits associated with the header in step 375 is taken from the remaining authorized payload and the remaining available payload Subtracted. In step 380, the remaining available payload is used up, or if there is no more data available in the logical channel of the current TTI, then the process 300 ends for this TTI. If the remaining available payload has not been used up and if there are still available data in the logical channel, the process 300 returns to step 305.

Figure 4 shows a flowchart of a process 400 for filling an enhanced MAC-e PDU with data from a logical channel, which is a part of E-TFC selection, according to another embodiment. According to the process 400, the MAC entity performs multiple requests to the RLC entity. The MAC entity requests the size of the RLC PDU based on the selected E-TFC. If after receiving the requested RLC PDU, there is still space available in the enhanced MAC-e PDU, the MAC entity can request additional RLC PDUs until the number of bits allowed to be transmitted by the logical channel is reached or exceeded. As provided above, the remaining available payload and the remaining authorized payload have the same definition. In addition, the variable h1 refers to the number of additional header bits required to include the first RLC PDU or its segment, and the variable h2 refers to the number of additional header bits required to include the subsequent RLC PDU or its segment belonging to the same logical channel. The number of additional header bits required by the segment. Variable B refers to the number of bits currently available for the logical channel.

Referring to Figure 4, in step 405, for the logical channel allowed to be transmitted in the current TTI, the maximum number of bits B currently available for the logical channel is determined according to the MIN (remaining available payload, remaining authorized payload). As mentioned above, the remaining available payload takes into account the quantitative loss.

In step 410, if the segment buffer contains bits or segments to be transmitted, fill the enhanced MAC-e PDU with as many bits from the segment buffer as possible while leaving space for the header ; If the segment is larger than B-h1, then the segment is divided to be added to the enhanced MAC-e PDU and the remaining bits are stored in the segment buffer. In step 415, the corresponding header is inserted into the enhanced MAC-e PDU, and the number of bits including the header size h1 added to the enhanced MAC-e PDU is subtracted from B.

In step 420, it is determined whether B is greater than zero. If B is not greater than zero, then it is determined in step 428 whether there is space available in the enhanced MAC-e PDU. If there is room in the enhanced MAC-e PDU, the process 400 returns to step 405, and if there are any logical channels allowed to be transmitted in the current TTI, the process 400 is multiplexed to the next logical channel. If there is no more room in the enhanced MAC-e PDU, then the process 400 ends.

If B is greater than zero, then in step 425, the RLC PDU is requested from the RLC entity. If the data is included in the segmented buffer, the RLC PDU size is (B-h2) (in step 410), or if the data is not available Is included in the segment buffer, the RLC PDU size is (B-h1) (in step 410). In step 430, it is determined whether the RLC entity delivers RLC PDUs. If the RLC entity does not deliver the RLC PDU, the process 400 returns to step 405, and if there is any logical channel allowed to be transmitted in the current TTI, the process 400 is re-multiplexed to the next logical channel.

If the RLC entity does deliver the RLC PDU, it is determined in step 435 whether the size of the delivered RLC PDU according to the number of bits is smaller than the requested RLC PDU size. If the size of the transferred RLC PDU is greater than the requested RLC PDU size, then in step 450, fill the enhanced MAC-ePDU with as many bits from the transferred RLC PDU as possible while leaving space for the header; If the delivered RLC PDU must be segmented to fit the enhanced MAC-e PDU, then the remaining bits are stored in the segmented buffer. Subsequently, the process 400 returns to step 405, and if there are any logical channels allowed to be transmitted in the current TTI, the process 400 is multiplexed to the next logical channel.

If the size of the delivered RLC PDU is smaller than the requested RLC PDU size, then in step 440, the enhanced MAC-e PDU is filled with the delivered RLC PDU and the corresponding header, and the RLC PDU and the corresponding header are subtracted from B. The size of the header. Subsequently, the process 400 returns to step 420 to try to fill the remaining space in the MAC-ePDU.

Figure 5 shows a flowchart of a process 500 for filling MAC-e PDUs with data from a logical channel, which is a part of E-TFC selection, according to another embodiment. According to the process 500, the MAC entity makes a single request to the RLC entity to generate one or more PDUs of a set size. The RLC accepts these inputs and sends N RLC PDUs of the requested size based on the amount of available data and the maximum amount of data to be transmitted. If one RLC PDU needs to be retransmitted, the RLC sends one or more retransmitted PDUs, and if there is space available, it also sends N new RLC PDUs with the requested size. When selecting the number of RLC PDUs to be sent to the enhanced MAC-e/es entity, the RLC entity can send a maximum additional PDU, which exceeds the maximum available size to be transmitted.

Referring to Figure 5, in step 505, for the logical channel allowed to be transmitted in the current TTI, the maximum number of bits B currently available for the logical channel is determined according to the MIN (remaining available payload, remaining authorized payload). As mentioned above, the remaining available payload takes into account the quantitative loss.

In step 510, if the segment buffer contains bits or segments to be transmitted, fill the enhanced MAC-e PDU with as many bits from the segment buffer as possible while leaving space for the header ; If the segment is larger than B-h1, then the segment is divided to add it to the enhanced MAC-e PDU and the remaining bits are stored in the segment buffer. In step 515, the corresponding header is inserted into the enhanced MAC-e PDU, and the number of bits added to the enhanced MAC-e PDU including the header size h1 is subtracted from B.

In step 520, it is determined whether B is greater than zero. If B is not greater than zero, then it is determined in step 528 whether there is space available in the enhanced MAC-e PDU. If there is room in the enhanced MAC-e PDU, the process 500 returns to step 505, and if there are any logical channels allowed to be transmitted in the current TTI, the process 500 is multiplexed to the next logical channel. If there is no more room in the enhanced MAC-e PDU, then the process 500 ends.

If B is greater than zero, then in step 525, the RLC PDU is requested from the RLC entity. If the data is included in the segment buffer, the RLC PDU size is (B-h2) bits (in step 510), or if If the data is not included in the segmented buffer, the RLC PDU size is (B-h1) bits (in step 510); if (B-h2) or (B-h1) is greater than the maximum allowable RLC PDU size, Then the PDU with the largest RLC PDU size is requested, and the number of PDUs equal to (B-h2 or h1)/(the largest RLCPDU size) is provided for the RLC entity, or the PDU size and the number of bits allowed to be transmitted are provided. The enhanced MAC entity may consider the size of the header or the RLC may consider the size of the header.

In step 530, it is determined whether the RLC entity delivers RLC PDUs. If the RLC entity does not deliver the RLC PDU, the process 500 returns to step 505, and if there is any logical channel allowed to be transmitted in the current TTI, the process 500 is multiplexed to the next logical channel.

If the RLC entity does transmit the RLC PDU, it is determined in step 535 whether the size of the transmitted RLC PDU is smaller than the available space in the enhanced MAC-ePDU. If the size of the delivered RLC PDU is greater than the available space in the enhanced MAC-e PDU, then in step 550, fill the enhanced MAC-e PDU with as many bits as possible from the delivered RLC PDU, and at the same time Leave room for the header; if the transmitted RLC PDU must be segmented to fit the enhanced MAC-e PDU, then the remaining bits are stored in the segment buffer. Subsequently, the process 500 returns to step 505, and if there are any logical channels that are allowed to be transmitted in the current TTI, the process 500 is multiplexed to the next logical channel.

If the size of the delivered RLC PDU is less than the available space in the enhanced MAC-e PDU, then in step 540, the enhanced MAC-e PDU is filled with the delivered RLC PDU and the corresponding header, and subtracted from B Go to the size of the RLC PDU and header. Subsequently, the process 500 returns to step 510 to fill the remaining space in the MAC-e PDU.

The RLC entity may also set a lower boundary for the size of the RLC PDU that it can generate, such as the minimum RLC size. The size of the minimum RLC PDU may be configured by higher layers, or it may be a static value or a calculated value for optimized transmission. For example, if the number of bits requested by the MAC entity (or the number of bits requested-the number of bits of the retransmitted RLC PDU) is less than the minimum RLC PDU size, then the RLC entity can perform one or a combination of the following: No data may be sent downward to the MAC entity, and a larger RLC PDU may be generated, the size of the larger RLC PDU is equal to or greater than the minimum RLC PDU size, so the MAC entity will have to process the larger PDU.

In an embodiment, the wireless transmitting/receiving unit may be configured to derive the minimum RLC PDU size from the minimum allowable MAC segment size if the minimum allowable MAC segment size is defined. For example, the minimum RLC PDU size may be multiple minimum allowed MAC segment sizes. Alternatively, the minimum RLC PDU size may be a static value pre-configured in the wireless transmitting/receiving unit.

Alternatively, UTRAN may determine the maximum RLC PDU size and use L2 or L3 (RRC) signaling to convey the maximum RLC PDU size value to the wireless transmit/receive unit. For example, UTRAN can use the RRC information element (IE) "RLC info" to configure the wireless transmit/receive unit to use the smallest RLC PDU size and the largest RLC PDU size. Signaling the maximum RLC PDU size can occur during radio bearer configuration or radio bearer reconfiguration. In addition, signaling the maximum RLC PDU size can occur during transmission channel configuration or transmission channel reconfiguration.

According to another embodiment, a technique for maintaining a guaranteed bit rate (GBR) of an unscheduled data stream with a variable-length header is provided. An unscheduled data stream is a data stream with a configured guaranteed bit rate. With the introduction of the enhancement of Layer 2 in the uplink (UL), the enhanced MAC-e/es load becomes dependent on the size of the RLC PDU and depends on the number of RLC PDUs in the enhanced MAC-es PDU. When the network configures the authorization of the unscheduled data flow, the network configures it so that the power used to transmit the data is sufficient to transmit the requested bits plus the enhanced MAC-e/es header bits quantity. Considering that the header field changes based on the number of enhanced MAC-es SDUs, the proposed method ensures the proper amount of data that can be transmitted within the configured authorization. As mentioned above, h1 refers to the number of additional header bits required to include the first RLC PDU or its segment, and h2 refers to the number of additional header bits used to include the subsequent RLC PDU or its segment belonging to the same logical channel. The number of additional header bits requested. B represents the number of bits currently available for the logic channel.

In order to guarantee the bit rate used for non-scheduled data streams, any of the following processes can be used alone or in combination. In a process, considering the worst-case scenario for the enhanced MAC-e/es header space, the network can give a conservative authorization to the non-scheduled data flow. This can be done by signaling or assuming a minimum RLC PDU size, such as 300 bits, so that the size of the RLC PDU generated by the RLC entity is not less than the minimum size, although the MAC entity is allowed to segment these RLC PDUs. This creates a worst-case load for the radio network controller (RNC), which is then used by the RNC to determine non-scheduled authorization. For example, if the desired GBR is equal to X bits/TTI, the network can allocate a non-scheduled authorization of (X+h2+((X/smallest RLC PDU size)-1)*(h1)) bits, Also consider the possibility of segmentation. In an alternative process, as described above, the network can give a conservative authorization, but it is based on the average RLC PDU size. In the case that the RLC PDU is less than the average value, the non-scheduled data flow can use the power of some scheduled data flow to ensure that the requested number of bits is transmitted. In another process, the network can be configured with more flexible non-scheduled authorization. This can be done by giving the wireless transmitting/receiving unit an absolute value and a change value, for example, the wireless transmitting/receiving unit is allowed to use a +/- value.

Figure 6 shows a flowchart of a simplified process 600 as part of the E-TFC selection according to another embodiment, which is used to fill the enhanced MAC-e PDU with data from the logical channel. In step 605, if there is a segment in the segment buffer, the segment is added to the enhanced MAC-e PDU, where the segment can be re-segmented to fit the MAC-ePDU. In step 610, if there is space in the enhanced MAC-e PDU, the maximum number of bits allowed to be transmitted is requested from the RLC entity. In step 615, the received one or more RLC PDUs are added to the MAC-ePDU to fill the available space in the MAC-e PDU, and if necessary, the final RLC PDU can be segmented to fit the MAC-e PDU. In addition, any one of the steps in any one of the procedures described above can be used in combination with the procedure 600 to generate an enhanced MAC-e PDU.

As part of the E-TFC selection, the process 300 in Fig. 3A and Fig. 3B, the process 400 in Fig. 4, the process 500 in Fig. 5, and/or the process 600 in Fig. 6 can be changed from the E- in Fig. 2 The TFC selection entity 212 performs the segmentation of the RLC PDU by the segmentation entity 214 and the segmentation can be stored in the segmentation buffer 216. The bit request from the MAC-c, MAC-d or RLC entity is made by the enhanced MAC-e/es entity 210.

Although the features and elements of this creation are described in specific combinations, each feature or element can be used alone without other features and elements, or used in various situations with or without other features and elements. . The method or flowchart provided here can be implemented in a computer program, software, or firmware executed by a general-purpose computer or processor. Examples of computer-readable storage media include magnetic media such as read-only memory (ROM), random access memory (RAM), registers, buffer memory, semiconductor storage devices, internal hard disks, and removable disks, Magneto-optical media and optical media such as CD-ROM disks and digital versatile discs (DVD).

For example, suitable processors include: general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSP), multiple microprocessors, one or more microprocessors associated with DSP cores, Controller, microcontroller, dedicated integrated circuit (ASIC), field programmable gate array (FPGA) circuit, any kind of integrated circuit (IC) and/or state machine.

The processor associated with the software can be used to implement a radio frequency transceiver for use in a wireless transmitting and receiving unit (wireless transmitting/receiving unit), user equipment (UE), terminal, base station, radio network controller (RNC) or Use it in any host computer. The wireless transmitting/receiving unit can be used in combination with modules implemented in the form of hardware and/or software, such as cameras, camera modules, video phones, speaker phones, vibration devices, speakers, microphones, TV transceivers, hands-free headsets, Keyboard, bluetooth<img file="TWM354953U_D0001.tif" />Module, frequency modulation (FM) wireless unit, liquid crystal display (LCD) display unit, organic light-emitting diode (OLED) display unit, digital music player, media player, video game console module, Internet browser And/or any wireless local area network (WLAN) or ultra-wideband (UWB) module.

<p>UE. . . User equipment</p><p>RNC. . . Radio network controller</p><p>Uu. . . Radio interface</p><p>UTRAN. . . Radio access network</p><p>CN. . . Core network</p><p>RLC. . . Radio link control</p><p>MAC, MAC-e, MAC-e/es. . . Media access control</p><p>PDU. . . Packet data unit</p><p>E-TFC. . . Enhanced transmission format combination</p><p>HARQ. . . Hybrid automatic repeat request</p><p>TSN. . . Set entity</p><p>200. . . Enhanced MAC-e/es entity</p><p>212. . . E-TFC selection entity</p><p>214. . . Segmented entity</p><p>216. . . Segmented buffer</p><p>218. . . Multiplexer and TSN setting entity</p><p>220. . . Scheduling entity</p><p>222. . . HARQ entity</p><p>TTI. . . Transmission time interval</p><p>MIN. . . function</p><p>h1, h2. . . Number of header bits</p><p>300. . . The process of filling the enhanced MAC-e PDU with the data of the logical channel</p>

This creation can be understood in more detail from the following descriptions, which are given in the form of examples combined with diagrams, in which:

Figure 1 shows an overview of the system architecture of the conventional Universal Mobile Telecommunications System (UMTS) network;

Figure 2 shows a block diagram of an enhanced MAC-e/es entity based on this teaching;

Figures 3A and 3B show a flowchart of a process that is part of E-TFC selection according to an embodiment, the process is used to fill an enhanced MAC-e packet data unit (PDU) with data from a logical channel ;

Figure 4 shows a flowchart of a process as part of E-TFC selection according to another embodiment, which is used to fill enhanced MAC-e PDUs with data from a logical channel;

Figure 5 shows a flowchart of a process as part of E-TFC selection according to another embodiment, which is used to fill enhanced MAC-e PDUs with data from logical channels; and

Figure 6 shows a flowchart of a simplified process as part of the E-TFC selection according to another embodiment, which is used to fill the enhanced MAC-e PDU with data from the logical channel;