TWI510127B - MAC and RLC architecture and method that allows reception from multiple transmission points - Google Patents

Description

MAC and RLC architecture and method that allows reception from multiple transmission points

In version 7 of the Universal Mobile Telecommunications System (UMTS), the Single Cell Downlink Machine Input Machine Output (SC-MIMO) feature was introduced. SC-MIMO allows Node B to transmit two transport blocks to a single wireless transmit/receive unit (WTRU) from the same magnetic region on a pair of transmit antennas, thereby increasing the data rate at higher geometries and for lower geometry A WTRU under structural conditions provides beamforming advantages.

In Release 8 and Release 9 of UMTS, dual-channel high-speed downlink packet access (DC-HSDPA) and dual-band DC-HSDPA features were introduced. These features allow Node B to serve one or more users by simultaneously performing HSDPA operations on two different frequency channels of the same magnetic zone, thereby improving the overall cell experience. A common part of these characteristics is that they allow simultaneous downlink reception of two independent transport blocks at the WTRU, where the transport block is transmitted by a single Node B magnetic zone on a High Speed Downlink Shared Channel (HS-DSCH).

Another technique based on simultaneous reception of two or more transport blocks from different cells at the same or different frequencies is a multi-point operation. The multipoint operation consists in transmitting two independent transport blocks to the WTRU, wherein the transport blocks are transmitted from different Node B magnetic regions or cells and geographically independent points on the same frequency or on different frequencies. This can be seen as the expansion of DC-HSDPA on geographically independent cells at the same or different frequencies. exhibition.

Multipoint transmission operates with two cells located on two different Node Bs or at two different sites (hereinafter referred to as inter-site multi-stream operation), and the Radio Network Controller (RNC) will be in two The data is divided between Node Bs. Each Node B then performs MAC and PHY layer operations, such as segmentation and TSN generation of the packet before being transmitted to the WTRU. Since the packet originates from two Node Bs, the existing MAC and entity layer procedures at the WTRU cannot process and reconstruct the packets in order. The MAC DC-HSDPA architecture in the WTRU is not designed to receive data from different sites. In addition, reception from different sites may increase and introduce the possibility of receiving out of sequence, causing potential data to be lost in the MAC-ehs entity and premature RLC status reporting in the RLC entity. There is therefore a need for methods that allow intersite operations and reordering in several layers.

The present application claims the benefit of U.S. Provisional Application No. 61/388,976, filed on Jan. 1, 2010, the content of which is hereby incorporated by reference.

A method for use in a wireless transmit receive unit (WTRU) for two-order reordering of received protocol data units (PDUs). The method includes receiving PDUs from a plurality of Node Bs, wherein each received PDU has a Transmission Sequence Number (TSN); using a TSN in the MAC layer in each of the plurality of Node Bs in a different reordering queue The received PDUs of the Node B are reordered; the received PDUs from the plurality of reordered queues are passed to one of the logical channels in the RLC layer; the received numbers are received in the RLC layer based on the sequence number (SN) PDU into Row reordering; starting a timer when at least the RLC PDU is lost based on the SN of the RLC PDU; and transmitting, based on the SN of the RLC PDU, a missing RLC based on the expiration of the timer A status report of the PDU, wherein the transmission of the status report is delayed under the condition that the RLC PDU is lost based on the SN of the RLC PDU and the timer is running.

100‧‧‧Communication system

102a, 102b, 102c, 102d‧‧‧ wireless transmit/receive unit (WTRU)

104, 142a, 142b‧‧‧ Radio Access Network (RAN)

106‧‧‧core network

108‧‧‧Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧Intermediate mediation

118‧‧‧Processor

120‧‧‧ transceiver

122‧‧‧transmit/receive components

124‧‧‧Speaker/Microphone

126‧‧‧ keyboard

128‧‧‧Display/Touchpad

130‧‧‧Cannot remove memory

132‧‧‧Removable memory

134‧‧‧Power supply

136‧‧‧Global Positioning System (GPS) chipset

138‧‧‧ Peripherals

140a, 140b, 140c‧‧‧ Node B

144‧‧‧Media Gateway (MGW)

146‧‧‧Mobile Exchange Center (MSC)

148‧‧‧Serving GPRS Support Node (SGSN)

150‧‧‧Gateway GPRS Support Node (GGSN)

201‧‧‧MAC-ehs-1

202‧‧‧MAC-ehs-2

203, 303, 806‧‧‧ Logical Channel ID (LCH-ID) solution multiplex entity

204, 304, 504, 807 ‧ ‧ reorganized entities

205, 702, 802, 808‧‧‧ reordering entities

206, 307, 507, 809‧‧‧ reordering array distribution

207, 308, 508, 703, 803, 810 ‧ ‧ decomposition entities

208, 309, 509, 811‧‧‧Hybrid Automatic Repeat Request (HARQ) entities

210, 211, 310, 510, 812‧‧‧High Speed Downlink Shared Channel (HS-DSCH)

301, 501, 601, 804, 805‧‧‧ MAC-ehs entities

305, 505‧‧‧Reorder-1 entity

306, 506‧‧‧Reorder-2 entities

401, 402‧‧‧MAC-hs/ehs

403, 602, 701, 801‧‧‧ MAC-sf entities

404, 603‧‧‧MAC-d

405‧‧‧MAC-is/i

407, 606‧‧‧MAC-c/sh/m

502‧‧‧Global reordering entity

503‧‧‧LCH-ID solution multiplex entity, logical channel entity

902‧‧‧SNsf

903‧‧‧MAC-sf header

904‧‧‧MAC-sf Service Data Unit (SDU)

905‧‧‧MAC-sf load

Next_expected_SNsf‧‧‧Next_Expected _SNsF

The invention may be understood in more detail from the following description, which is given by way of example, and which can be understood in conjunction with the accompanying drawings, in which: FIG. 1A shows that one or more of the disclosed embodiments may be implemented therein. A schematic diagram of a system of an exemplary communication system; FIG. 1B is a system diagram showing an example wireless transmit/receive unit (WTRU), wherein the WTRU may be used in a communication system as shown in FIG. 1A; To illustrate a system diagram of an example radio access network and an example core network, which may be used in a communication system as shown in FIG. 1A; An example of a MAC architecture for a WTRU with dual MAC-ehs entities; Figure 3 shows an example MAC-ehs entity on the WTRU side and two sets of reordered queues, where each group is reordered Includes two queues; Figure 4 shows an example of a MAC architecture for a WTRU with dual MAC-ehs entities and one MAC-sf entity; Figure 5 shows an example with two global reordering sub-entities Global MAC-ehs in the WTRU An example of an entity; Figure 6 shows an example of a MAC-sf entity located on the UTRAN side; Figure 7 shows an example of a MAC-sf entity located on the WTRU side; Figure 8 shows an example of the MAC-sf entity located on the WTRU side Example of a MAC-sf entity and a dual MAC-ehs entity; Figure 9 shows an example MAC-sf PDU for a PDU; Figures 10A and 10B are diagrams showing the replacement of using only one Tsf timer at a given time Flowchart of an embodiment; Figures 11A and 11B are flow diagrams showing an alternative embodiment of using one Tsf timer for each lost PDU; Figures 12A and 12B are diagrams showing the use of one timing for each missing serial number A flowchart of an alternative embodiment of the device; and Figures 13A and 13B are flow diagrams showing RLC behavior.

FIG. 1A is an example communication system 100 in which one or more of the disclosed embodiments may be implemented. Communication system 100 may be a multiple access system that provides content such as voice, material, video, messaging, broadcast, etc. to multiple wireless users. Communication system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 100 may use one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Quadrature FDMA (OFDMA), single carrier. FDMA (SC-FDMA) and so on.

As shown in FIG. 1A, communication system 100 can include a wireless transmit/receive unit (WTRU) 102a, 102b, 102c, 102d, radio access network (RAN) 104, core network 106, public switched telephone network (PSTN) 108, internet 110, and other networks 112, but it will be understood The disclosed embodiments may encompass any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in wireless communication. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals, and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, pagers, mobile phones, personal digital assistants ( PDA), smart phones, portable computers, netbooks, personal computers, wireless sensors, consumer electronics, and more.

Communication system 100 can also include a base station 114a and a base station 114b, each of which can be configured to wirelessly interact with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or Any type of device of multiple communication networks (e.g., core network 106, internet 110, and/or network 112). For example, base stations 114a, 114b may be base station transceiver stations (BTS), node B, eNodeB, home node B, home eNodeB, site controller, access point (AP), wireless router, and the like. Device. Although base stations 114a, 114b are each depicted as a single element, it will be understood that base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements such as a site controller (BSC), a radio network controller (RNC), a relay node ( Not shown). Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic area, which may be referred to as cells (not shown). Cells can also be divided into cell domains. For example, with base station 114a Associated cells can be divided into three magnetic regions. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each of the magnetic regions of the cell. In another embodiment, base station 114a may use multiple input multiple output (MIMO) technology, and thus multiple transceivers for each magnetic zone of cells may be used.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via an empty intermediation plane 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, Infrared (IR), ultraviolet (UV), visible light, etc.). The empty intermediaries 116 can be established using any suitable radio access technology (RAT).

More specifically, as previously discussed, communication system 100 can be a multiple access system and can employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 104 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may be established using Wideband CDMA (WCDMA) Empty mediation plane 116. WCDMA may include, for example, High Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) and/or High Speed Uplink Packet Access (HSUPA).

In another embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and/or Advanced LTE (LTE-A) is used to establish an empty intermediate plane 116.

In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement, for example, IEEE 802.16 (ie, Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution ( EDGE), radio technology such as GSM EDGE (GERAN).

For example, the base station 114b in FIG. 1A can be a wireless router, a home Node B, a home eNodeB, or an access point, and any suitable RAT can be used for facilitating, for example, a company, a home, a vehicle, A local area communication connection such as a campus. In one embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d may use cell-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish picocell cells and femtocells. Yuan (femtocell). As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114b does not have to access the Internet 110 via the core network 106.

The RAN 104 can be in communication with a core network 106, which can be configured to provide voice, data, application, and/or voice over Internet Protocol (VoIP) services to the WTRUs 102a, 102b, 102c, 102d. Any type of network of one or more. For example, core network 106 may provide call control, billing services, mobile location based services, prepaid calling, internetworking, video distribution, etc., and/or perform advanced security functions such as user authentication. Although not shown in FIG. 1A, it is to be understood that the RAN 104 and/or the core network 106 can communicate directly or indirectly with other RANs that can use the same RAT as the RAT 104 or a different RAT. For example, in addition to being connected to a RAN that can employ E-UTRA radio technology 104. Core network 106 can also communicate with other RANs (not shown) that employ GSM radio technology.

The core network 106 can also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include a circuit switched telephone network that provides Plain Old Telephone Service (POTS). The Internet 110 can include a global system of interconnected computer networks and devices that use public communication protocols, such as Transmission Control Protocols in the Transmission Control Protocol (TCP)/Internet Protocol (IP) Internet Protocol Suite. (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP). Network 112 may include a wireless or wired communication network that is owned and/or operated by other service providers. For example, network 112 may include another core network connected to one or more RANs that may use the same RAT as RAN 104 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may be configured to communicate with different wireless networks over different communication links. Multiple transceivers for communication. For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with a base station 114a that can use a cell-based radio technology and with a base station 114b that can use an IEEE 802 radio technology.

FIG. 1B is a system diagram of an example WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keyboard 126, a display/touch pad 128, a non-removable memory 130, and a removable Memory 132, power supply 134, global positioning system chipset 136, and other peripheral devices 138. It is to be understood that the WTRU 102 may include any of the above elements while consistent with the embodiments. set.

The processor 118 can be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with the DSP core, a controller, Microcontrollers, Specific Function Integrated Circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), state machine, etc. Processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although processor 118 and transceiver 120 are depicted as separate components in FIG. 1B, it will be appreciated that processor 118 and transceiver 120 can be integrated together into an electronic package or wafer.

The transmit/receive element 122 can be configured to transmit signals to the base station (e.g., base station 114a) via the null plane 116 or to receive signals from the base station (e.g., base station 114a). For example, in one embodiment, the transmit/receive element 122 can be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 122 may be a transmitter/detector configured to transmit and/or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit/receive element 122 can be configured to transmit and receive both RF signals and optical signals. It is to be understood that the transmit/receive element 122 can be configured to transmit and/or receive any combination of wireless signals.

Moreover, although the transmit/receive element 122 is depicted as a single element in FIG. 1B, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for intermediation through nulls. Face 116 transmits and receives wireless signals.

Transceiver 120 may be configured to modulate a signal to be transmitted by transmit/receive element 122 and configured to demodulate a signal received by transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 can include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.

The processor 118 of the WTRU 102 may be coupled to a speaker/microphone 124, a keyboard 126, and/or a display/touch pad 128 (eg, a liquid crystal display (LCD) unit or an organic light emitting diode (OLED) display unit), and may be The above device receives user input data. Processor 118 may also output data to speaker/microphone 124, keyboard 126, and/or display/touchpad 128. Moreover, processor 118 can access information from any type of suitable memory and store the data in any type of suitable memory, such as non-removable memory 130 and/or Memory 132 is removed. Non-removable memory 130 may include random access memory (RAM), readable memory (ROM), hard disk, or any other type of memory storage device. The removable memory 132 can include a Subscriber Identity Module (SIM) card, a flash memory card, a secure digital (SD) memory card, and the like. In other embodiments, processor 118 may access data from memory that is not physically located on WTRU 102 and located on a server or home computer (not shown), and store the data in the memory.

The processor 118 can receive power from the power source 134 and can be configured to distribute the power to other components in the WTRU 102 and/or to control power to other elements in the WTRU 102. Power source 134 can be any device suitable for powering up WTRU 102. For example, the power source 134 can include one or more dry cells (nickel cadmium (NiCd), nickel zinc (NiZn), nickel hydride (NiMH), lithium ion (Li-ion), etc., solar cells, fuel cells, and the like.

The processor 118 may also be coupled to a GPS die set 136 that may be configured to provide location information (eg, longitude and latitude) with respect to the current location of the WTRU 102. Additionally or alternatively to the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base station 114a, 114b) via an empty intermediation plane 116, and/or based on two or more adjacent base stations. The timing of the received signal determines its position. It is to be understood that the WTRU may obtain location information by any suitable location determination method while consistent with the embodiments.

The processor 118 can also be coupled to other peripheral devices 138, which can include one or more software and/or hardware modules that provide additional features, functionality, and/or wireless or wired connections. For example, peripheral device 138 may include an accelerometer, an electronic compass (e-compass), a satellite transceiver, a digital camera (for photo or video), a universal serial bus (USB) port, a vibrating device, a television transceiver. Hands-free headsets, Bluetooth R modules, FM radio units, digital music players, media players, video game console modules, Internet browsers, and more.

1C is a system diagram of RAN 104 and core network 106, in accordance with an embodiment. As mentioned above, the RAN 104 can communicate with the WTRUs 102a, 102b, and 102c over the null plane 116 using UTRA radio technology. The RAN 104 can also communicate with the core network 106. As shown in FIG. 1C, the RAN 104 can include Node Bs 140a, 140b, 140c, which can each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the null plane 116. Node Bs 140a, 140b, 140c may be associated with special cells (not shown) in RAN 104, respectively. The RAN 104 may also include RNCs 142a, 142b. Worth note It is intended that the RAN 104 can include any number of Node Bs and RNCs while remaining consistent with the implementation.

As shown in FIG. 1C, Node Bs 140a, 140b can communicate with RNC 142a. Additionally, Node B 140c can communicate with RNC 142b. Node Bs 140a, 140b, 140c can communicate with respective RNCs 142a, 142b via the Iub interface. The RNCs 142a, 142b can communicate with each other through the Iur interface. The RNCs 142a, 142b, respectively, can be configured to control the respective connected Node Bs 140a, 140b, 140c. In addition, RNCs 142a, 142b, respectively, can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, and the like.

The core network 106 shown in FIG. 1C may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and/or a Gateway GPRS Support Node (GGSN) 150. . While each of the foregoing elements is described as being part of core network 106, it will be understood that any of these elements may be owned and/or operated by entities other than the core network operator.

The RNC 142a in the RAN 104 can be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 can be connected to the MSW 144. The MSC 146 and MGW 144 may provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network, such as the PSTN 108, facilitating communication between the WTRUs 102a, 102b, 102c and conventional landline communication devices.

The RNC 142a in the RAN 104 can also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 can be connected to the GGSN 150. The SGSN 148 and GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to a packet switched network, such as the Internet 110, thereby facilitating communication between the WTRUs 102a, 102b, 102c and the IP enabled devices. Communication.

As mentioned above, the core network 106 can also be connected to the network 112, where the network 112 can include other wired or wireless networks that are owned and/or operated by other service providers.

A two-order reordering procedure can be used to allow the WTRU to process and reconstruct packets transmitted from two or more Node Bs. The two-stage reordering procedure ensures that packets are delivered to higher layers in sequence by establishing multiple MAC-ehs entities in the WTRU (one for each Node B). The two-stage reordering program performs packet reordering only on new MAC entities. The two-stage reordering procedure also establishes multiple MAC-ehs entities in the WTRU and performs packet reordering at the MAC and RLC. The single-order ordering of packets may also be used to distribute the logical channels between Node Bs to allow the WTRU to process and reconstruct packets from two or more Node Bs, thereby ensuring that packets are delivered in order to higher layers. .

The term MAC-ehs can be used to refer to the functionality performed in the Release 7 MAC-ehs sublayer running on the HS-DSCH transport channel, including but not limited to: Hybrid Automatic Repeat Request (HARQ), Decomposition, Reordering Distribution, reordering, reassembly, and logical channel ID demultiplexing (LCH-ID demultiplexing).

For intersite operations, a new MAC architecture can be established. In an alternative, there may be multiple MAC-ehs entities. For example, there is a MAC-ehs in the WTRU that is configured to perform HSDPA operations for each site. For example, there may be a MAC-ehs entity that performs a multipoint operation for each Node B. Thus, the data is split at the MAC level and there is one RLC entity per WTRU.

For intra-site operations (eg, cells belonging to the same Node B), there may be one MAC-ehs entity in the WTRU. For inter-site scenarios (eg, cells belong to different Node Bs), There may be one MAC-ehs entity in the WTRU for each Node B. If the WTRU is configured for multi-cell reception, there is an identifier transmitted by the network to inform the WTRU whether the configuration is intra-site, inter-site, or a combination of both, whereby the WTRU can determine how many MACs are needed -ehs entity. This identifier may be a simple Boolean (eg, intra-site or inter-site indication), may be an explicit number and parameter of the MAC-ehs entity that the WTRU is configured, or may be between the cell and the Node B. Mapping (eg, cells 1 and 2 may belong to node B1, cell 3 may belong to node B2, etc.).

The WTRU may use other signaling mechanisms such as Transmit Power Control (TPC) combined index or associated grant (RG) combined index to determine if an independent MAC-ehs entity is available. The functionality of the WTRU may also be established for a particular Node B. More specifically, if the WTRU is receiving an HS-DSCH from a cell having the same index, the WTRU may determine that the cell belongs to the same Node B, thereby having only one MAC-ehs entity or a set of cells for these cells The priority order is listed. Otherwise, if the indices are different, the WTRU may assume that there should be a MAC-ehs entity for HS-DSCH cells configured with different indices. Some Node B implementations may not allow sharing of resources in the magnetic interval, in which case it may be assumed that for each cell in such Node B, each WTRU may configure one MAC-ehs entity.

On the network side, for each WTRU, each Node B can maintain one MAC-ehs entity, and at each Node B, the packets are independently assigned a Transmission Sequence Number (TSN). For each WTRU, each Node B may also maintain one MAC-ehs entity per cell, or alternatively for a WTRU within the site, each Node B may maintain one MAC for all configured cells. -ehs entity.

Figure 2 shows the MAC shelf for a WTRU with dual MAC-ehs entities Construct an example. As shown in Figure 2, the MAC architecture includes dual MAC-ehs entities in which the full MAC-ehs functionality can be repeated. This may result in having different HARQ entities for each MAC-ehs, and it may be assumed that the WTRU is configured to receive data from two different cells. The architecture shown in Figure 2 can be extended for situations where the WTRU can receive HS-DSCH from more than two Node Bs. In FIG. 2, MAC-ehs-1 201 may be established for receiving HS-DSCH 210 from Node B1, and MAC-ehs-2 may be established for receiving HS-DSCH 211 from Node B2. The MAC-ehs-1 and MAC-ehs-2 may also include an LCH-ID demultiplexing entity 203, a reassembly entity 204, a reordering entity 205, a reordering queue distribution 206, a decomposition entity 207, and a HARQ entity 208.

The LCH-ID demultiplexing entity 203 can be used to route a MAC-ehs Service Data Unit (SDU) to the correct logical channel based on the received logical channel identification word. The reassembly entity 204 can be used to reassemble the split MAC-ehs SDU and forward the MAC Protocol Data Unit (PDU) to the LCH-ID Demultiplexing Entity 203. The reordering entity 205 can organize the received reordering PDUs according to the received sequence number. The reordered queue distribution 206 can route the received reordering PDUs to the correct reordering queue based on the received logical channel identification words. The decomposition entity 207 can decompose the MAC-ehs PDU by removing the MAC-ehs header. The HARQ entity 208 processes the HARQ protocol.

In another MAC architecture example for a WTRU, only one MAC-ehs entity is configured with each cell or a set of reordered queues per Node B. Reordering a column distribution You can use one or a combination of the following methods to determine which queue to transfer data to.

The first way to determine which queue to transfer data to is that each HARQ ID program is mapped to a specific MAC-ehs entity. This can be achieved by having different MAC-ehs entities use different HARQ program ID ranges. Optionally, in addition to HARQ In addition to the sequence ID, new fields (eg, MAC-ehs ID) can be configured and used to identify a particular MAC-ehs entity. Different MAC-ehs entities can continue to use the same HARQ program ID range.

A second way to determine which queue to transfer data to is that each cell or Node B has a predefined range of queue distribution IDs, thereby enabling the WTRU to distinguish between the two. Alternatively, each Node B or cell can maintain a queue ID.

A third way to determine which queue to transfer data to is to signal the mapping between the queue ID and the MAC-ehs entity by the network. For example, the network can signal the MAC-ehs ID for each queue ID.

A fourth way to determine which queue to transfer data to is to use the new identifier in the MAC-ehs Protocol Data Unit (PDU) header to indicate to the WTRU which MAC-ehs entity the MAC-ehs PDU should be delivered to.

A fifth way to determine which queue to transmit data to is that the WTRU uses physical layer identification (eg, the scrambling code of the cell) to determine to which MAC-ehs entity the MAC-ehs PDU should be delivered.

The sixth way to determine which queue to transfer data to can be based on the received HS-DSCH channel. The reordering queue can be mapped to the HS-DSCH transmission channel or the HS-DPSCH channel.

A seventh way to determine which queue to transmit data to is that the new Node B identification word can be defined so that the network can indicate to the WTRU the mapping between the queue ID and the Node B ID. In particular, the new Node B ID identification word map may include which Node B ID each queue ID is mapped to.

Figure 3 shows an example MAC-ehs entity on the WTRU side and two sets of reordering sequences, where each set of reordering sequences includes two sequences. Each MAC-ehs entity or reordering entity group in the WTRU may be configured to reorder packets for reordering queues belonging to a particular Node B. The MAC-ehs entity 301 may include an LCH-ID demultiplexing entity 303, a reassembly entity 304, a reordering-1 entity 305, a reordering-2 entity 306, a reordering queue distribution 307, a decomposing entity 308, and a HARQ entity 309.

The LCH-ID demultiplexing entity 303 can be used to route the MAC-ehs SDU to the correct logical channel based on the received logical channel identification word. The reassembly entity 304 can be used to reassemble the split MAC-ehs SDU and forward the MAC PDU to the LCH-ID demultiplexing entity 303. Reorder-1 entity 305 and reorder-2 entity 306 may organize the received reordering PDUs according to the received sequence number. The reordered queue distribution 307 can route the received reordering PDUs to the correct reordering queue based on the received logical channel identification words. The decomposition entity 308 can decompose the MAC-ehs PDU by removing the MAC-ehs header. The HARQ entity 309 processes the HARQ protocol.

Reordering of packets received from different Node Bs or replaceable cells may be implemented, for example, in one of the following ways: (1) performing two-order reordering in the MAC by establishing a new MAC entity; or (2) Perform two-order reordering in the RLC.

For two-order reordering in the MAC layer, packets passed by two MAC-ehs entities or public MAC-ehs entities may not be in order, since packets from different Node Bs may not have to be received at the same time. Since RLC functionality may rely on MAC-ehs entities to deliver RLC PDUs in order, this may affect existing programs such as RLC status reporting. With a MAC architecture with dual MAC-ehs entities, the RLC entity may receive out-of-order packets, which may trigger premature RLC status reports from the WTRU side, and thus unnecessarily retransmitted may not be lost only It is delayed information. In order to avoid or minimize the impact on the RLC entity, the MAC architecture can ensure that packets from both Node Bs are properly reordered before being transmitted to the RLC or higher layer of the WTRU. This new MAC functionality can be found in the MAC-sf entity.

Figure 4 shows an example of a MAC architecture for a dual MAC-ehs entity and a MAC-sf entity. Each WTRU may be configured with one MAC-sf entity. The new MAC-sf entity can be found on top of one or more MAC-ehs entities or on top of a public MAC-ehs entity. In the Universal Terrestrial Radio Access Network (UTRAN), there is one MAC-sf entity for each WTRU.

As shown in FIG. 4, the MAC-sf 403 can communicate with the MAC-ehs entity 401 or the public MAC-ehs entity 402 and with the MAC-d as shown in FIG.

The MAC-c/sh/m 407 can control access to all common transmission channels except the HS-DSCH transmission channel and the E-DCH transmission channel. The MAC-d 404 can control access to all dedicated transport channels, access to MAC-c/sh/m 407 and MAC-hs/ehs 401 and 402. The MAC-c/sh/m 407 can also control access to the MAC-is/i 405. The MAC-hs/ehs 401 and 402 can also handle HSDPA specific functions and control access to the HS-DSCH transmission channel. MAC-es/e or MAC-is/i 405 can control access to the E-DCH transmission channel.

Figure 5 shows an example of a global MAC-eh entity in a WTRU with two global reordering sub-entities. All MAC-sf functionality may be incorporated into the global MAC-ehs entity or in a new MAC entity with MAC-ehs functionality on the WTRU side. The MAC-sf functionality may exist in a new sub-entity, which may be referred to as a global reordering entity 502. There may be one global reordering entity 502 per logical channel entity 503. The MAC-ehs entity 501 may include an LCH-ID solution multiplex entity 503, a reassembly entity 504, a reorder-1 entity 505, and a reorder-2 Body 506, reordering queue distribution 507, decomposition entity 508, and HARQ entity 509. As shown in Figure 5, there can be two reordering queues per Node B, and each Node B can use the same two logical channels. MAC-sf functionality may also be included in the MAC-d sublayer.

The LCH-ID demultiplexing entity 503 can be used to route the MAC-ehs SDU to the correct logical channel based on the received logical channel identification word. The reassembly entity 504 can be used to reassemble the split MAC-ehs SDU and forward the MAC PDU to the LCH-ID demultiplexing entity 503. Reorder-1 entity 505 and reorder-2 entity 506 may organize the received reordering PDUs according to the received sequence number. The reordered queue distribution 507 can route the received reordering PDUs to the correct reordering queue based on the received logical channel identification words. The decomposition entity 508 can decompose the MAC-ehs PDU by removing the MAC-ehs header. The HARQ entity 509 processes the HARQ protocol.

Figure 6 shows an example of a MAC-sf entity located on the UTRAN side. On the UTRAN side, a new MAC-sf entity 602 can be located in the RNC and can communicate with both the MAC-ehs entity 601 in Node B and the MAC-d 603 in the RNC. Figure 6 shows that a new MAC-sf entity 602 can be located in the RNC and can communicate with both the MAC-ehs entity 601 in the Node B and the MAC-d 603 in the RNC.

The MAC-c/sh/m 606 may be located in the controlling RNC and the MAC-d 603 may be located in the serving RNC. MAC-hs/ehs 601 can be located in Node B. The MAC-d PDU to be transmitted may be transferred from the MAC-c/sh/m 606 or from the MAC-d 603 to the MAC-hs/ehs 601 via the Iub interface or via the Iur/Iub interface.

In the WTRU, each MAC-ehs entity may be configured to pass each Node B or alternatively a reordering packet for each cell to a MAC-sf entity, which may pass the packet to the RLC They were previously reordered by using the new serial number SNsf.

Figure 7 shows an example of a MAC-sf entity located on the WTRU side. The MAC-sf entity can be identified for each logical channel, including decomposed entities and reordered entities. In Fig. 7, for example, a total of four logical channels can be assumed. Figure 7 shows a MAC-sf entity 701 comprising a reordering entity 702 and a decomposing entity 703. The reordering entity 702 can organize the received reordering PDUs according to the received sequence number. The decomposition entity 703 can decompose the MAC-ehs PDU by removing the MAC-ehs header.

Figure 8 shows an example of a MAC-sf entity and a dual MAC-eh entity located on the WTRU side. As shown in FIG. 8, the MAC-sf entity may be represented by one of the MAC-ehs entities described above, where two independent MAC-ehs entities may coexist. The MAC-sf entity 801 can be located above the two MAC-ehs entities 804 and 805 and can receive packets that have been demultiplexed according to the logical channel to which they may be mapped. The MAC-sf entity 801 can include a reordering entity 802 and a decomposition entity 803. Each MAC-ehs entity 804 and 805 may include an LCH-ID demultiplexing entity 806, a reassembly entity 807, a reordering entity 808, a reordering queue distribution 809, a decomposition entity 810, and a HARQ entity 811.

The reordering entity 802 can organize the received reordering PDUs according to the received sequence number. The decomposition entity 803 can decompose the MAC-ehs PDU by removing the MAC-ehs header.

The LCH-ID demultiplexing entity 806 can be used to route the MAC-ehs SDU to the correct logical channel based on the received logical channel identification word. The reassembly entity 807 can be used to reassemble the split MAC-ehs SDU and forward the MAC PDU to the LCH-ID demultiplexing entity 806. The reordering entity 808 can organize the received reordering PDUs according to the received sequence number. The reordered queue distribution 809 can route the received reordering PDUs to the correct reordering queue based on the received logical channel identification words. Decomposition entity 810 can remove the MAC-ehs header by Decompose the MAC-ehs PDU. The HARQ entity 811 processes the HARQ protocol.

Figure 9 shows an example MAC-sf for a PDU. In Fig. 9, it can be assumed that only two logical channels have been configured, and data for two logical channels has been transmitted by each Node B. Packets belonging to the same logical channel can be transmitted to the same decomposition and reordering entity. Figure 9 is by way of example only, and the MAC-sf entity can coexist with all of the other architectures described above.

In the MAC-ehs entity, the existing functionality of "LCH-ID Demultiplexing" may be updated so that the MAC-ehs solution multiplex entity will base the MAC-sf PDU based on the received logical channel identification word (eg MAC-ehs SDU) Routed to the correct decomposition and reordering entity of the MAC-sf entity. In other words, the MAC-ehs solution multiplex entity can be configured to transmit MAC-sfSDUs belonging to the same logical channel to the same decomposition and reordering entity.

In the RNC, a new MAC sequence number SNsf may be added as a header to each MAC-sf PDU to assist the MAC-sf entity in the WTRU in reordering the packets. The MAC-sf entity in the RNC can be responsible for managing and setting the serial number of each MAC-d stream or each logical channel. Each MAC-d PDU can be given a serial number. The data can then be transmitted to the MAC-ehs entity of one or more Node Bs in the configured HS-DSCH Node B.

The MAC-sf PDU may be defined with a payload 905 and a header 903. The MAC-sf payload 905 may correspond to a MAC-sf Service Data Unit (SDU) 904, and the header 903 may include a new SF sequence number, such as SNsf 902 as shown in FIG. Figure 9 can also be displayed on the transmitter side, for example UTRAN, MAC-d can transmit MAC-d PDU to MAC-sf entity, MAC-sf entity can receive it as MAC-sf SDU, MAC-sf entity can transmit it To the MAC-ehs entity, the MAC-ehs entity can receive it as a MAC-ehs SDU.

On the WTRU side, the MAC-sf decomposition entity may receive MAC-sf PDUs out of order from two MAC-ehs entities or from a public MAC-ehs entity. The MAC-sf decomposition entity may remove the MAC-sf header and may pass the MAC-sf reordering PDU to the MAC-sf reordering entity. There may be one reordering entity per logical channel or MAC-d flow. Optionally, there may be one decomposition entity per logical channel. The MAC-sf reordering entity may reorder the packets to the correct logical channel according to the SNsf included in the header before passing the packet (eg, the MAC-ehs SDU is equivalent to the MAC-ehs PDU) to the MAC-d.

Additional functionality may be defined for the MAC-sf entity to properly reorder the MAC-sf PDUs. Furthermore, the reordering entity may not wait for the lost MAC-sf PDU for a certain period of time because this PDU may be lost, or the Node B may be too out of sync to compare the delay between packets from one Node B. The delay for packets from other Node Bs is unacceptable.

Figures 10A and 10B are flow diagrams showing an alternative embodiment using only one Tsf timer at a given time. The following terms are used herein. "Next_expected_SNsf" may be the SF-DC sequence number (SNsf) of the SNsf following the received previous in-order MAC-sf PDU. The initial value of Next_expected_SNsf can be zero. "Tsf" may be an SF-DC lost PDU timer. There may be a running timer Tsf at a given time.

As shown in Figures 10A and 10B, the following describes how the SF-DC reordering entity uses Tsf, Next_expected_SNsf, and reordering buffers to reorder the received packets. A determination is made as to whether the Tsf has expired or whether a PDU has been received. If a PDU is received, it is determined if the received PDU is within range 1001. If the received PDU is in range, ie SNsf Next_expected_SNsf, it is determined whether Tsf is running 1002, if Tsf is not running and the MAC-sf PDU is received 1003 in sequence (SNsf=Next_expected_SNsf), the SF-DC reordering entity can pass this PDU 1004 to MAC-d and Increase the value of Next_expected_SNsf by one increment by 1005. If the WTRU detects that the lost PDU 1003 (the MAC-sf PDU with SNsf > Next_expected_SNsf is received) and no timer Tsf has been run, Tsf may be initiated 1006 and the received PDU may be stored 1007 in the reordering buffer. At the location indicated by its SNsf.

When Tsf is running 1002, the reordering entity may store the received PDUs in the reordering buffer 1018 in their SNsf order. If 1009 is received in time to the detected missing PDU (the MAC-sf PDU with SNsf=Next_expected_SNsf is received before the Tsf expires), the timer Tsf may be stopped 1010. The received PDU may be stored 1011 at the location indicated by its SNsf in the reorder buffer. If one or more PDUs in the reordering buffer are still missing 1012, Tsf can be restarted 1013, Next_expected_SNsf can be set 1014 to the smallest SNsf of all lost PDUs, and PDUs with SNsf<Next_expected_SNsf can be passed 1015 to MAC -d. If no PDU is lost 1012 in the reordering buffer, Next_expected_SNsf can be set to 1016 as the SNsf of the PDU with the highest SNsf in the reordering buffer plus one (Next_expected_SNsf=highest SNsf+1), and all PDUs stored in the buffer Can be passed 1017 to MAC-d.

If Tsf expires 1000 and there is at least one other missing PDU 1020 in the reordering buffer, Tsf can be restarted and Next_expected_SNsf can be set 1021 to the SNsf of the lost PDU with the smallest SNsf. If there are no other missing PDUs 1020 in the reordering buffer, Next_expected_SNsf can be set to 1022 as the highest in the reordering buffer. The SNsf of the SNsf PDU is incremented by one (Next_expected_SNsf=highest SNsf+1). The MAC-sf PDU that has been stored in the reordering buffer and the MAC-sf PDU with SNsf<Next_expected_SNsf may be passed 1019 to MAC-d. If the SF-DC reordering entity receives 1000 PDUs with SNsf<Next_expected_SNsf 1001, it may discard the PDU 1008.

11A and 11B are flow diagrams showing an alternative embodiment of using one Tsf timer for each lost PDU. The following variables can be defined as follows. "Next_SNsf" is the SF-DC sequence number (SNsf) of the SNsf following the received or lost previous MAC-sf PDU. The initial value of Next_SNsf can be zero. "Tsf(SNsf)" is the SF-DC lost PDU timer. Each lost PDU can have a timer. "Missing_Pdu(SN)" is the SN of the lost PDU with the sequence number SN. There can be one variable for each lost PDU.

As shown in Figures 11A and 11B, how the SF-DC reordering entity uses the Tsf (SNsf) timer, different variables and reordering buffers to reorder the received packets is described below. A determination is made as to whether the Tsf has expired or whether a PDU has been received. If a PDU is received, it is determined if the received PDU is within range 1101. If the received PDU is in range, ie SNsf The minimum Missing_Pdu(SN) determines if Tsf(SNsf) is running 1102. If no Tsf (SNsf) is running and the MAC-sf PDU is received 1103 in sequence (SNsf = Next_SNsf), the SF-DC reordering entity may pass 1104 to MAC-d and increment the value of Next_SNsf by one. 1105. If the WTRU detects a missing PDU 1103 (the MAC-sf PDU with SNsf > Next_SNsf is received), the new variable "Missing_Pdu (SNsf)" may be set 1106 to the value of Next_SNsf. A Tsf (SNsf) instance can initiate 1107 for this missing PDU. The received PDU may be stored 1108 at the location indicated by its SNsf in the reordering buffer. The value of Next_SNsf can be incremented by 1109 until its value is different from the SNsf of the most recently received PDU. The above can be done in any combination and in any order. If one or more Tsf (SNsf) instances are running 1102, the reordering entity may store the received PDUs in reorder buffer 1117 in SNsf order. If the lost PDU detected by 1111 is received in time (if the MAC-sf PDU having one of SNsf equals one of the Missing_Pdu (SNsf) variables is received before the corresponding Tsf (SNsf) expires, the corresponding timer Tsf (SNsf) Can be stopped 1112. The received PDU may be stored 1113 at the location indicated by its SNsf in the reorder buffer. If Missing_Pdu(SN) is the only missing PDU 1114 (if no more timer Tsf is running), all stored PDUs may be passed 1116 to MAC-d. In the case of multiple lost PDUs 1114 (if at least one timer Tsf (SNsf) is still running) and if Missing_Pdu (SNsf) is the smallest of all Missing_Pdus (SNsf), the stored ones have SNsf < next Missing_Pdu ( The SN) PDU can be passed 1115 to MAC-d. The above can be done in any combination and in any order.

If the instance Tsf (SNsf) expires 1100 and no other Tsf timer is running 1114, all stored PDUs may be passed 1119 to MAC-d. If this Tsf(SNsf) corresponds to 1116 at the minimum Missing_Pdu(SNsf), the stored PDU with SNsf < next Missing_Pdu(SN)-1 may be passed 1120 to MAC-d. If Next_SNsf is equal to this Missing_Pdu(SNsf)+1, Next_SNsf can be incremented by 1118. The above can be done in any combination and in any order. If the SF-DC receives the PDU 1100 with SNsf < Minimum Missing_Pdu (SN) 1101, it may discard the PDU 1110.

The value of Tsf may be fixed and may be determined by the WTRU or may be configured by the network. The network can signal the minimum and maximum values of Tsf. If the value of Tsf is configured by the network, it can be based on network knowledge about the synchronization level of the two Node Bs. For example, if you are aware of the Internet To Node B, which is sent at almost the same time, it can configure the WTRU with a lower value of Tsf. If the network knows that a Node B is transmitting data for a long time after another Node B, it can configure the WTRU with a longer value of Tsf. In the case where the secondary single frequency HS-DSCH serving cell is deactivated, the MAC-sf entity can be removed. The value of the timer Tsf can be set to zero.

The MAC layer second order reordering may be based on the MAC-ehs transmission sequence number (TSN) by dividing the TSN range allowed by each Node B (or alternative transmitting cell). The RNC may forward the sequence block of the MAC-d PDU to the Node B and may assign a non-overlapping range of TSN values, where the range of TSN values may indicate a sequence of blocks between the plurality of Node Bs.

In one example implementation, the RNC may transmit ten consecutive MAC-d PDUs of the first sequence to node B2 with allowed TSN ranges 101-200. When reordering at the WTRU, the WTRU may first reorder the PDUs within each TSN range (first order reordering) and then reorder based on the TSN range (second order reordering). In this example, the WTRU may first pass all data blocks using the TSN range 1-100 to the RLC, and then the data blocks using the TSN range 101-200 may be passed to the RLC.

Alternatively or additionally, reordering can be performed in the RLC. The RLC may receive packets reordered per Node B (or alternatively each cell) only from the MAC, and may perform global reordering of packets from different MAC instances. If the WTRU has been configured with multiple MAC-ehs entities, the RLC may be configured with a new option indicating that the WTRU must reorder in the RLC Answer Mode (AM). For example, a MAC may no longer be needed to ensure in-order delivery of RLC PDUs from different sites. If the RLC detects the missing sequence number, it can itself wait for a given period of time before triggering the RLC status report to ensure that the lost PDU is not transmitted by the other Node B. The RLC reordering process can be applied to pass RLC SDUs to higher layers and / Or pass a status report to the transmitter side for RLC AM.

The process in the RLC can be performed for the acknowledge mode (AM) logical channel and the optional non-acknowledge mode RLC. Figures 12A and 12B are flow diagrams showing an alternative embodiment in which one timer is used for each missing serial number. For example, a new timer called Timer_Am_Reordering can be defined and used to delay the transmission of a Status PDU (STATUS PDU) in the event that an AM Data (AMD) PDU is lost. The following definitions can be used. "Timer_Am_Reordering" can be a missing PDU timer. There may be a timer running at a given time. "VR(AM_NEXT)" may be the sequence number of the next desired PDU, such as the SN of the SN following the last received PDU. This variable can be initialized to zero. "Reordering_Window_Size" may be the size of the receive window of the WTRU RLC receivable PDU. If a PDU with an SN before the start of the window is received, the RLC should discard it. "VR(BW)" is the beginning of the window. This variable can be initialized to zero. "VR(EW)" can be the end of the window. This variable can be initialized to Reordering_Window_Size minus 1. All operations can be calculated with the largest SN as the modulus.

The RLC behavior of this solution as illustrated in Figures 12A and 12B is described below. A determination is made 1200 as to whether Timer_Am_Reordering has expired or if a PDU has been received. If a PDU is received, it is determined if the received PDU is within range 1201. If the received PDU is in range, ie SN VR(BW) determines if Timer_Am_Reordering is running 1202. If Timer_Am_Reordering is not running and the RLC receives the PDU 1203 in sequence order (the SN of the received PDU is equal to VR(AM_NEXT)), the RLC may store 1204 this location in the reordering buffer indicated by its SN and Increase by 1205 VR (AM_NEXT). If the RLC reassembles the RLC SDU by using the in-order PDU from the reordering entity, it can pass the 1204 SDU to the higher entity. If the RLC detects gap 1203 in reception (the received PDU has SN > VR (AM_NEXT)) and if Timer_Am_Reordering is not running, it may start 1206 Timer_Am_Reordering. The received PDU may store 1207 at the location indicated by the SN in the reordering buffer. When Timer_Am_Reordering is at runtime 1202, the RLC may store the received PDUs in the reordering buffer in their SN order, leaving a gap 1217 in the event that the PDU is lost.

If the detected missing PDU 1209 is received immediately (if a PDU having an SN equal to VR (AM_Next) is received before the Timer_Am_Reordering expires), Timer_Am_Reordering may be stopped 1210. The received PDU may be stored 1211 at a location indicated by its SN in the reorder buffer. A 1212 acknowledgement (ACK) can be transmitted to the network for this PDU. If one or more PDUs in the reordering buffer are still missing 1213 (there is a gap in the SN), Timer_Am_Reordering can be restarted 1214 or VR (AM_Next) can be set to 1215 into the smallest of all missing PDUs in the reordering buffer. SN. If there is no PDU loss 1213 in the reordering buffer (there is no gap in the SN): VR (AM_Next) can be set to 1216 into the reordering buffer with the highest SN PDU plus one (VR(AM_Next)=maximum SN+1). If the RLC can reassemble the RLC SDU from the stored PDUs, the SDU can be delivered to a higher layer (eg, receiving all RLC PDUs for a given RLC SDU). The above can be done in any combination and in any order.

If Timer_Am_Reordering expires 1200, the status PDU may be transmitted 1218 to the network to indicate a negative acknowledgement (NACK) for the SN equal to VR (AM_Next), and if there are other SNs in the reordering buffer that are less than VR (AM_Next) PDU legacy Loss, NACK may also be indicated in the status PDU for the lost SN, and optionally an ACK for all received PDUs may also be reported. If there is at least one other lost PDU 1220 located in the receive window in the reordering buffer, Timer_Am_Reordering may be restarted 1221 or VR (AM_Next) may be set 1222 to the SN of the lost PDU. If the PDU Loss 1220 no longer exists in the reordering buffer, VR(AM_Next) may be set 1223 to SN plus one of the PDU with the highest SN (VR(AM_Next) = highest SN+1). The above can be done in any combination and in any order.

If the RLC receives the PDU 1200 having the SN (SN < VR (BW)) 1201 before the start of the reception window, it may discard the PDU 1208. If the WTRU receives a PDU 1200 with a SN 1201 higher than the VR (EW), the WTRU may move the receive window up to this SN 1224, ie VR(BW)=VR(BW)+(SN-VR(EW) And VR(EW)=SN. If possible, the WTRU may reassemble the RLC SDU with the PDUs stored in the reordering buffer and communicate the SDU to the higher entity 1225. The WTRU may remove the PDU 1226 whose SN is lower than the receive window from the reordering buffer. The above can be done in any combination and in any order.

Alternatively or additionally, a timer can be used for each lost PDU. Each lost PDU can initiate a new reordering timer instance. The following definitions are used here. "Timer_SR(SNm)" may be a missing PDU timer. There may be one instance of Timer_SR for each lost PDU. "Missing_Var(SNm)" may be the serial number of the lost PDU, and one Missing_Var (SNm) instance exists for each lost APADU. "VR(NEXT)" may be the sequence number of the PDU with the highest SN plus one. This variable can be initialized to zero. "Reordering_Window_Size" may be the size of the receive window of the WTRU RLC receivable PDU. If a PDU with an SN before the start of the window is received, the RLC can discard it. "VR(BW)" can be the beginning of the window. This variable can be initialized to zero. "VR(EW)" can be the end of the window. This variable can be initialized to Reordering_Window_Size minus 1.

Figures 13A and 13B are flow diagrams showing RLC behavior. A determination is made 1300 as to whether Timer_SR (SNm) has expired or if a PDU has been received. If a PDU is received, it is determined if the received PDU is within range 1301. If the received PDU is in range, ie SN V(BW) determines if Timer_SR(SNm) is running 1302. If no Timer_SR instance is running 1302 and the RLC receives the PDU 1303 in sequence order (the SN of the received PDU is equal to VR(NEXT)), the RLC may store 1304 the location indicated by its SN in the reordering buffer. And increment by 1305 VR (NEXT). The RLC may pass the SDU to the higher entity each time the RLC reassembles the RLC SDU by using the in-order PDU from the reordering entity. If the RLC detects gap 1303 in reception (the received PDU has SN > VR(NEXT)), a 1306 Timer_SR (SNm) instance may be initiated for the lost PDU. The SNm of this lost PDU can hold 1307 in the instance of the variable Missing_Var (SNm). The received PDU may store 1308 at the location indicated by the SN in the reordering buffer. VR(NEXT) can be set equal to the lost PDU SNm plus one (VR(NEXT)=Missing_Var(SNm)+1). The above can be done in any combination and in any order.

If one or more Timer_SR instances are running 1302, the reordering entity may store the received PDUs in order (without gaps) in the reordering buffer in their SN order and may increment VR(NEXT) 1316 by one. If the lost PDU detected by 1311 is received in time (if a PDU having one of SN equals one of the Missing_Var (SNm) instances is received before the corresponding Timer_SR (SNm) expires, the corresponding timer Timer_SR (SNm) may To be stopped 1312. The received PDU may be stored 1313 at the location indicated by its SN in the reorder buffer. A 1314 ACK can be transmitted to the network for the PDU. If the RLC reassembles the RLC SDU from the stored PDU, the SDU can pass 1315 to the higher layer. The above can be done in any combination and in any order.

If one of the Timer_SR (SNm) instances expires 1300, a status PDU indicating that the NACK for Missing_Var (SNm) with the SN equal to this missing PDU may be transmitted 1317 to the network. The RLC can restart the 1318 Timer_SR (SNm). If the RLC receives 1300 a PDU with SN (SN < VR(BW)) 1301 before the start of the receive window, it may discard 1310 the PDU. If the WTRU receives 1300 PDUs with SN 1301 higher than VR (EW), the receive window can be moved up 1319 to this SN (VR(BW)=VR(BW)+(SN-VR(EW)) and VR (EW) = SN). The corresponding instance of the Timer_SR whose Missing_Var value is lower than the new window may be stopped and the instance of the corresponding Missing_Var variable may be deleted 1320. If possible, the RLC SDUs with the PDUs stored in the reordering buffer can be reassembled and the SDUs can be transmitted to the higher entity 1321. A PDU with a SN below the receive window can be removed 1322 from the reorder buffer. The above can be done in any combination and in any order. The Timer_SR may have a fixed value, possibly determined by the WTRU, or configured by the network in a Radio Resource Control (RRC) message.

There may be a limit on the wait duration and a limit on the number of requests for lost packets. After the maximum number of retransmissions for a particular PDU, the network side RLC can be reset. However, some controls may also be implemented on the WTRU side as follows. The WTRU RLC may limit its number of request retransmissions for the same lost PDU according to the following.

Each lost PDU definition, for example, called V_RN, can be initialized to A new variable of zero, and this new variable can be used to track how many Timer_SRs have been initiated for a particular PDU identified by the SN. If the RLC transmits a STATUS_PDU due to the lost PDU, it may start the Timer_SR again for the PDU and may increment the new variable V_RN by one for this PDU. The maximum number of retries can be defined and can be referred to as MAX_RN. If the V_RN becomes larger than MAX_RN for a particular lost PDU and the Timer_SR expires and the PDU is still not received, then the PDU may be considered lost and the RLC may drop the same as the missing PDU. All PDUs of the SDU, and optionally a STATUS_PDU indicating the SN of the PDU that is no longer waiting for this PDU or another type of identification word to the network. MAX_RN may be a fixed value and may be determined by the WTRU or configured by the network. Additionally, MAX_RN may depend on the value of the existing variable MaxDAT, which represents the maximum number of retransmissions of the AMD PDU plus one. For example, MAX_RN can be equal to MaxDAT or can be equal to MaxDAT minus a fixed value. V_RN can be a static or dynamic value. If a lost PDU is received or if the maximum value of V_RN(MAX_RN) is reached, V_RN may be reset to zero.

Additionally, there is a maximum number of lost PDUs that the RLC can wait for at the same time. This translates to the maximum number of Timer_SRs that can run simultaneously. For example, if the RLC detects a missing PDU, it may only start a new Timer_SR if the maximum number of Timer_SRs has not been reached. Otherwise, the RLC may treat this PDU as lost and discard all PDUs belonging to the same SDU, and the RLC may optionally transmit a STATUS_PDU or another type of identification indicating that the SN of the PDU is no longer waiting for this PDU. Word to the peer RLC on the network side.

Alternatively, another timer, such as Timer_MaxRN, can be specified Righteousness. The time Timer_MaxRN may take a value that does not depend on the Timer_SR or a multiple of the Timer_SR. One of the minimum conditions for the Timer_MaxRN setting may be that Timer_MaxRN must be longer than Timer_SR. The WTRU RLC may start the Timer_MaxRN while starting the Timer_SR for the particular lost PDU when the PDU is lost for the first time. This can be done not when the retransmitted PDU is still lost. If T_RN expires, Timer_MaxRN can still run. If the lost PDU arrives, T_RN and T_MaxRN can be stopped. If the Timer_MaxRN expires, the WTRU may treat the lost PDU as lost, stop the Timer_SR, discard all PDUs belonging to the same SDU as the lost PDU, and optionally transmit the PDU including the PDU indicating that the WTRU is no longer waiting for this PDU. SN's STATUS_PDU to the network.

When the WTRU transmits a STATUS_PDU to indicate to the network that it is no longer waiting for a lost PDU or a few lost PDUs with a particular SN, the new Super Field (SUFI) type can be used by using the reserved SUFI between 1001-1111 One of the type bit combinations is defined. This new SUFI type can be referred to as, for example, "No More Retries." The "no more attempted" SUFI may include a lost PDU that the WTRU RLC will no longer wait for retransmissions or an SN of a list of lost PDUs. If the network receives the indication from the WTRU, it can initiate an RLC reset procedure.

If two MAC-ehs entities are configured, a non-acknowledgement mode (UM) can be used, where the existing "out of order SDU delivery" functionality of the RLC UM can be re-ordered to reorder the PDUs received from the MAC. This may allow the RLC UM on the WTRU and on the UTRAN side to be configured with "out of order SDU delivery" for DCCH and DTCH logical channels other than the MCCH logical channel.

In the absence of second-order reordering, logical channels can be divided between Node Bs. cloth. Node Bs transmitting to the same WTRU are only transmitting on different logical channels. For example, one Node B can transmit control information using a Signaling Radio Bearer (SRB), while other Node Bs can transmit data using Radio Bearers (RBs). Another example may be that one Node B can utilize RB1 to transmit data, while other Node Bs can utilize RB2 to transmit data (such as VoIP and web page views). Since each logical channel has a reordering queue, existing MAC and RLC procedures can be used in this scheme.

When dynamic handover and synchronization are used between Node Bs, Node B may not simultaneously transmit data to the WTRU. Alternatively, the transmitting Node B can be dynamically switched, which means that the Node B can transmit one after the other every x number of Transmission Time Intervals (TTIs). In this case, in order to minimize the impact on the WTRU (in order to minimize the required changes in the MAC), some synchronization with respect to the TSN can be designed between the two Node Bs. Instead of independently generating a transmission sequence number on each Node B, the transmission sequence number can be synchronized between Node Bs so that there is a common sequence numbering between Node Bs. For example, the TSN received at the WTRU may be unique within the MAC-ehs entity, with different Node Bs transmitting in time.

In another alternative, if a Node B completes its current transmission, it can indicate to the other Node Bs through the Iub or Iur that it has used the previous TSN so that other Node Bs can utilize the received from other Node Bs. The TSN after the TSN initiates its new transmission.

If the WTRU detects a command or indication that Node B is changing, the WTRU may signal each reordering queue in the uplink (UL) direction using a MAC PDU (eg, a MAC-i PDU or a Control MAC PDU). The last TSN number received.

Alternatively or additionally, each Node B may reset its TSN when it initiates a new retransmission. If the WTRU detects a change on Node B or a cell, the WTRU is at each When it detects that it is receiving data from different Node Bs, it can reset its next_expected_TSN variable, reinitialize the RcvWindow_UpperEdge (receive window upper boundary) variable, or stop timer T1 if timer T1 is running. The WTRU may detect whether it is receiving from a particular Node B and optionally flush its HARQ buffer as described above.

Different HARQ architectures can be defined according to the transmission design chosen for the SF-DC. If two Node Bs transmit the same set of data, a soft combination can be implemented at the WTRU. One HARQ entity may be required in the MAC-ehs entity on the WTRU side. If two Node Bs transmit different sets of data simultaneously, two HARQ entities can be designed in the WTRU as shown in Figures 2-9. It is also possible to configure two sets of HARQ programs (for example, 12, 6 HARQ programs per cell), but the HARQ program can be shared among all cells.

In the case of dynamic handover as described above (each Node B transmits a different set of data but not simultaneously), there may be two HARQ entities in the MAC or one common HARQ entity shared by the two Node Bs, which may allow The packet transmitted by one Node B is retransmitted by another Node B. In the case of a public HARQ entity, Node Bs must synchronize their NDI.

In one example, if a Node B completes its current transmission, it can indicate to other Node Bs the last value of the new Data Identification Word (NDI) it uses on each HARQ program so that other Node Bs can properly Set the value of the NDI it transmits to the WTRU.

Alternatively or additionally, each Node B may reset its NDI to zero if a new transmission is initiated, and if the WTRU detects that it is receiving from a different Node B, the WTRU may treat it as being in the HARQ procedure. The first transmission.

Example

1. A type used in a wireless transmit and receive unit (WTRU) for A received protocol data unit (PDU) performs a two-stage reordering method, the method comprising: receiving PDUs from a plurality of Node Bs, wherein each received PDU has a transmission sequence number (TSN).

2. The method of embodiment 1, further comprising: using the TSN in the MAC layer to weight the received PDUs from each of the plurality of Node Bs in different reordering queues Sort.

3. The method of any one of embodiments 1-2, further comprising: communicating the received PDUs from the plurality of reordering queues to a logical channel in the RLC layer.

4. The method of any one of embodiments 1-3, further comprising: reordering the received PDUs based on a sequence number (SN) in the RLC layer.

5. The method of any one of embodiments 1-4, further comprising: initiating a timer when at least the RLC PDU is lost based on the SN of the RLC PDU.

6. The method of any one of embodiments 1-5, further comprising: transmitting, based on the SN of the RLC PDU, a missing RLC PDU based on the expiration of the timer A status report in which the transmission of the status report is delayed under the condition that the RLC PDU is lost based on the SN of the RLC PDU and the timer is running.

7. The method of any one of embodiments 1-6, further comprising: restarting the timer if the timer expires and at least another RLC PDU is lost; and The SN of a desired RLC PDU is set to the SN of the lost RLC PDU.

8. The method of any one of embodiments 1-7, further comprising: The SN of the next desired RLC PDU is set to the SN plus of the RLC PDU having the highest SN, on the condition that the timer expires and no other RLC PDUs are lost.

9. The method of any of embodiments 1-8, wherein the transmitted status report is reported if another RLC PDU having a SN less than the SN of the next desired RLC PDU is lost in the reordering buffer Indicates a negative acknowledgement (NACK).

10. A method for second order reordering of received protocol data units (PDUs) for use in UTRAN, the method comprising: receiving PDUs from a plurality of Node Bs, wherein each received PDU has a transmission sequence number (TSN).

11. The method of embodiment 10, further comprising: using the TSN in the MAC layer to weight the received PDUs from each of the plurality of Node Bs in different reordering queues Sort.

12. The method of any one of embodiments 10-11, further comprising: communicating the received PDUs from the plurality of reordering queues to a logical channel in the RLC layer.

13. The method of any one of embodiments 10-12, further comprising: reordering the received PDUs based on a sequence number (SN) in the RLC layer.

14. The method of any one of embodiments 10-13, further comprising: initiating a timer when at least the RLC PDU is lost based on the SN of the RLC PDU.

15. The method of any one of embodiments 10-14, further comprising: transmitting, based on the SN of the RLC PDU, a missing RLC PDU based on the expiration of the timer A status report in which the transmission of the status report is delayed under the condition that the RLC PDU is lost based on the SN of the RLC PDU and the timer is running.

16. The method of any one of embodiments 10-15, further comprising: restarting the timer if the timer expires and at least another RLC PDU is lost; and The SN of a desired RLC PDU is set to the SN of the lost RLC PDU.

17. The method of any one of embodiments 10-16, further comprising: setting the SN of the next desired RLC PDU under the condition that the timer expires and no other RLC PDUs are lost The SN of the RLC PDU with the highest SN is incremented by one.

The method of any one of embodiments 10-17, wherein if the other RLC PDUs of the SN having less than the SN of the next desired RLC PDU are lost in the reordering buffer, the transmitted The status report indicates a negative acknowledgement (NACK).

19. A wireless transmit receive unit (WTRU) for performing two-order reordering of received protocol data units (PDUs), the WTRU comprising: a receiver configured to receive PDUs from a plurality of Node Bs, wherein each The received PDU has a Transmission Sequence Number (TSN).

20. The method of embodiment 19, further comprising: a first reordering entity configured to use the TSN in the MAC layer in different reordering queues The received PDUs from each of the plurality of Node Bs are reordered.

The method of any one of embodiments 19-20, further comprising: a processor configured to pass the received PDUs from the plurality of reordering queues to a logical channel of the RLC layer .

The method of any one of embodiments 19-21, further comprising: a second reordering entity configured to perform on the received PDU based on a sequence number (SN) in the RLC layer Reorder.

23. The method of any one of embodiments 19-22, further comprising: a timer configured to start when at least the RLC PDU is lost based on the SN of the RLC PDU.

The method of any one of embodiments 19-23, further comprising: a transmitter configured to transmit, based on the SN of the RLC PDU, for the expiration of the timer, A status report indicating the lost RLC PDU, wherein the transmission of the status report is delayed if the RLC PDU is lost based on the SN of the RLC PDU and the timer is running.

The method of any one of embodiments 19-24, further comprising: ???said timer is further configured to restart under the condition that the timer expires and at least another RLC PDU is lost ;as well as The processor is further configured to set the SN of the next desired RLC PDU to the SN of the lost RLC PDU.

The method of any one of embodiments 19-25, further comprising the processor being further configured to, under the condition that the timer expires and no other RLC PDUs are lost, The SN of a desired RLC PDU is set to the SN plus one of the RLC PDUs with the highest SN.

The method of any one of embodiments 19-26, wherein the transmitted status report is reported if another RLC PDU having a SN less than the SN of the next desired RLC PDU is lost in the reordering buffer Indicates a negative acknowledgement (NACK).

Although the features and elements of the present invention have been described above in terms of specific combinations, those skilled in the art will understand that each feature or element can be used alone or in the absence of other features and elements. Other features and elements of the invention are used in combination in various situations. Moreover, the method provided by the present invention can be implemented in a computer program, software or firmware executed by a computer or processor, wherein the computer program, software or firmware is embodied in a computer readable medium. Examples of computer readable media include electronic signals (transmitted over a wired or wireless connection) and computer readable storage media. Examples of computer readable storage media include, but are not limited to, read only memory (ROM), random access memory (RAM), scratchpad, cache memory, semiconductor storage devices, such as internal hard drives and removable Magnetic media such as disks, magneto-optical media, and optical media such as CD-ROMs and digital audio and video discs (DVDs). The software related processor can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

801‧‧‧MAC-sf entity

802, 808‧‧‧ reordering entities

803, 810‧‧‧ Decomposed entities

804, 805‧‧‧MAC-ehs entity

806‧‧‧Logical Channel ID (LCH-ID) solution to multiplex entity

807‧‧‧Reorganized entity

809‧‧‧Reordering array distribution

811‧‧‧Hybrid Automatic Repeat Request (HARQ) entity

812‧‧‧High Speed Downlink Shared Channel (HS-DSCH)

Claims (12)

A method for use in a wireless transmit receive unit (WTRU) for two-order reordering of received protocol data units (PDUs), the method comprising: receiving PDUs from a plurality of Node Bs, wherein each received The PDU has a Transmission Sequence Number (TSN); the received PDUs from each of the plurality of Node Bs are reordered in a different reordering queue using a TSN in a MAC layer; The received PDUs of the reordered queue are passed to a logical channel in an RLC layer; the received PDUs are reordered based on a sequence number (SN) in the RLC layer; when at least one RLC PDU is based on the RLC PDU When the SN is lost, a timer is started; and, under the condition that the timer expires, a status report for indicating a lost RLC PDU is transmitted based on the SN of the RLC PDU, wherein an RLC PDU is based on the The transmission of the status report is delayed under the condition that the SN of the RLC PDU is lost and the timer is running. The method of claim 1, wherein the method further comprises: restarting the timer; and, under the condition that the timer expires and at least another RLC PDU is lost, an SN of a desired RLC PDU is next Set to the SN of the lost RLC PDU. The method of claim 1, wherein the method further comprises: after the expiration of the timer and no other RLC PDUs are lost, the next expectation is An SN of the RLC PDU is set to SN plus one of the RLC PDUs having the highest SN. The method of claim 1, wherein if the other RLC PDU of a SN having a SN less than the next expected RLC PDU in a reordering buffer is lost, the transmitted status report indicates a negative response ( NACK). A method for performing two-stage reordering of received protocol data units (PDUs) in a UTRAN, the method comprising: receiving PDUs from a plurality of Node Bs, wherein each received PDU has a transmission sequence number (TSN); reordering received PDUs from each of the plurality of Node Bs in different reordering queues using a TSN in a MAC layer; The received PDU is delivered to a logical channel in an RLC layer; the received PDU is reordered based on a sequence number (SN) in the RLC layer; when at least one RLC PDU is lost based on the SN of the RLC PDU, Generating a timer; and transmitting, after the expiration of the timer, a status report indicating a lost RLC PDU based on the SN of the RLC PDU, wherein an RLC PDU is lost based on the SN of the RLC PDU The transmission of the status report is delayed under the condition that the timer is running. The method of claim 5, the method further comprising: restarting the timer if the timer expires and at least another RLC PDU is lost; An SN of a desired RLC PDU is set to the SN of the lost RLC PDU. The method of claim 5, further comprising: setting an SN of a desired RLC PDU to have a highest SN under the condition that the timer expires and no other RLC PDUs are lost. The SN of the RLC PDU is incremented by one. The method of claim 6 wherein if the other RLC PDU of a SN having a SN less than the next expected RLC PDU in a reordering buffer is lost, the transmitted status report indicates a negative acknowledgement ( NACK). A wireless transmit receive unit (WTRU) for performing two-order reordering of received protocol data units (PDUs), the WTRU comprising: a receiver configured to receive PDUs from a plurality of Node Bs, wherein each received PDU has a transmission sequence number (TSN); a first reordering entity configured to use a TSN in a MAC layer in a different reordering queue for each node B from the plurality of Node Bs Receiving PDUs for reordering; a processor configured to pass received PDUs from the plurality of reordering queues to a logical channel in an RLC layer; a second reordering entity configured to be Retrieving received PDUs based on a sequence number (SN) in the RLC layer; a timer configured to be activated when at least one RLC PDU is lost based on the SN of the RLC PDU; and a transmitter configured to Transmitting, based on the SN of the RLC PDU, a status report indicating the missing RLC PDU, wherein an RLC PDU is lost based on the SN of the RLC PDU and the timer is running, under the condition that the timer expires Under the condition The transmission of the report is delayed. The WTRU as claimed in claim 9, the WTRU further comprising: the timer is further configured to restart; and the processor is further configured if the timer expires and at least another RLC PDU is lost An SN that sets a desired RLC PDU is set to the SN of the lost RLC PDU. The WTRU as claimed in claim 9, the WTRU further comprising: the processor further configured to: after the timer expires and no other RLC PDUs are lost, an SN of a desired RLC PDU is taken The SN of the RLC PDU set to have a highest SN is incremented by one. The WTRU as claimed in claim 11, wherein if the other RLC PDU of a SN having a SN less than the next expected RLC PDU in a reordering buffer is lost, the transmitted status report indicates a negative acknowledgement ( NACK).