Images

Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/20—Manipulation of established connections
  • H04W76/27—Transitions between radio resource control [RRC] states
• • H04W72/042—
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04B—TRANSMISSION
  • H04B7/00—Radio transmission systems, i.e. using radiation field
  • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
  • H04B7/022—Site diversity; Macro-diversity
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L1/00—Arrangements for detecting or preventing errors in the information received
  • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
  • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
  • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
  • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/50—Queue scheduling
  • H04L47/62—Queue scheduling characterised by scheduling criteria
  • H04L47/624—Altering the ordering of packets in an individual queue
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L5/00—Arrangements affording multiple use of the transmission path
  • H04L5/003—Arrangements for allocating sub-channels of the transmission path
  • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
  • H04L5/0055—Physical resource allocation for ACK/NACK
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/16—Performing reselection for specific purposes
  • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W40/00—Communication routing or communication path finding
  • H04W40/005—Routing actions in the presence of nodes in sleep or doze mode
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/20—Control channels or signalling for resource management
  • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/20—Control channels or signalling for resource management
  • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/20—Control channels or signalling for resource management
  • H04W72/29—Control channels or signalling for resource management between an access point and the access point controlling device
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/08—Access point devices
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/04—Interfaces between hierarchically different network devices
  • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2101/00—Indexing scheme associated with group H04L61/00
  • H04L2101/60—Types of network addresses
  • H04L2101/618—Details of network addresses
  • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
• • H04W76/046—
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/12—Access point controller devices

Definitions

• This application is related to wireless communications.
• An enhanced uplink mechanism has been introduced for the Third Generation Partnership Project (3GPP) standards.
• 3GPP Third Generation Partnership Project
• L2 Layer 2
• new functional entities have been introduced in the medium access control (MAC) including enhanced MAC-e/es entities.
• MAC medium access control
• WTRU wireless transmit/receive unit
• the enhanced MAC-e/es are considered one single sublayer.
• the enhanced MAC-e and the enhanced MAC-es entities may be considered separate, with the enhanced MAC-e residing in the Node-B and the enhanced MAC-es residing in the serving radio network controller (SRNC).
• SRNC serving radio network controller
• One enhanced MAC-e and one enhanced MAC-es entity are present for each WTRU in the Node B and in the SRNC, respectively.
• the entities are separate in the network so that the more real-time critical functionality of enhanced MAC-e may be placed into the Node-B.
• FIG. 1 is a block diagram of an enhanced MAC entity 100 of a WTRU.
• the enhanced MAC in the WTRU comprises a hybrid automatic repeat-request (HARQ) module, a multiplexing and transmission sequence number (TSN) setting module, an enhanced uplink transport format combination (E-TFC) selection module, and two segmentation modules.
• HARQ hybrid automatic repeat-request
• TSN multiplexing and transmission sequence number
• E-TFC enhanced uplink transport format combination
• the HARQ module performs the MAC functions relating to the HARQ protocol, including storing enhanced MAC-e payloads and re-transmitting them.
• the HARQ module determines the E-TFC, the retransmission sequence number (RSN), and the power offset to be used by Layer 1 (L1).
• RSN retransmission sequence number
• L1 Layer 1
• the multiplexing and TSN module concatenates multiple MAC-d protocol data units (PDUs) into enhanced MAC-es PDUs, and multiplexes one or multiple enhanced MAC-es PDUs into a single enhanced MAC-e PDU, to be transmitted in a subsequent transmission time interval (TTI), as instructed by the E-TFC selection module.
• PDUs MAC-d protocol data units
• TTI transmission time interval
• the E-TFC selection module performs E-TFC selection according to scheduling information, relative and absolute grants received from a UMTS Terrestrial Radio Access Network (UTRAN) via L1 signalling, and a serving grant signalled through the RRC for arbitration among the different flows mapped on the E-DCH.
• UTRAN UMTS Terrestrial Radio Access Network
• the segmentation module performs segmenting of the MAC-d PDUs.
• FIGS. 2 and 2A show the enhanced MAC-e and enhanced MAC-es entities located at the Node-B and RNCs, respectively.
• the enhanced MAC-es sublayer manages E-DCH specific functionality.
• the enhanced MAC-es entity comprises a disassembly module, a reordering and queue distribution module, a reordering/combining module, and a reassembly module.
• the reordering queue distribution module routes the enhanced MAC-es PDUs to the correct reordering buffer based on the serving radio network controller (SRNC) configuration and based on the logical channel identity.
• SRNC serving radio network controller
• the reordering/combining module reorders received enhanced MAC-es PDUs according to the received TSN and Node-B tagging, (i.e. CFN, subframe number).
• Enhanced MAC-es PDUs with consecutive TSNs are delivered to the disassembly module upon reception.
• the macro diversity selection module operates in the enhanced MAC-es, in case of soft handover with multiple Node-Bs.
• the disassembly module is responsible for disassembly of enhanced MAC-es PDUs, including removal of the enhanced MAC-es header.
• the reassembly function reassembles segmented MAC-d PDUs, and delivers the MAC-d PDUs to the correct MAC-d entity.
• the enhanced MAC-e entity comprises an E-DCH control module, a de-multiplexing module, and a HARQ entity.
• the E-DCH scheduling module manages E-DCH cell resources between WTRUs. Based on scheduling requests, scheduling grants are determined and transmitted.
• the E-DCH control module is responsible for reception of scheduling requests and transmission of scheduling grants.
• the de-multiplexing module performs the de-multiplexing of enhanced MAC-e PDUs into enhanced MAC-es PDUs.
• Enhanced MAC-es PDUs are forwarded to the SRNC in their associated MAC-d flow.
• the HARQ module may support multiple HARQ processes. Each process is responsible for generating ACKs or NACKs indicating delivery status of E-DCH transmissions.
• FIG. 3 shows the radio resource controller (RRC) service states of a 3GPP WTRU with an enhanced uplink.
• the WTRU may operate in several states which depend on the user activity. The following states have been defined: Idle, Cell_DCH, Cell_FACH, URA_PCH and Cell_PCH.
• the RRC state changes are controlled by the network using RNC parameters, the WTRU does not decide to perform state changes by itself.
• a dedicated physical channel is allocated to the WTRU in the uplink and the downlink.
• the WTRU is known on a cell level according to its current active set.
• the WTRU may use dedicated transport channels, shared transport channels, or a combination of these transport channels.
• a WTRU is in the Cell_FACH state if it has been assigned to use the common control channels (e.g. CPCH).
• the WTRU In the Cell_FACH state, no dedicated physical channel is allocated to the WTRU, and the WTRU continuously monitors a FACH (e.g., S-CCPCH) or a High Speed Downlink Shared Channel (HS-DSCH) in the downlink.
• the WTRU is assigned a default common or shared transport channel in the uplink (e.g. RACH) that it can use anytime according to the access procedure for that transport channel.
• the position of the WTRU is known by the UTRAN on a cell level according to the cell where the WTRU last performed a cell update.
• the WTRU In the Cell_PCH state, no dedicated physical channel is allocated to the WTRU.
• the WTRU selects a PCH, and uses discontinuous reception for monitoring the selected PCH via an associated PICH. No uplink activity is possible.
• the position of the WTRU is known by the UTRAN on a cell level according to the cell where the WTRU last performed a cell update in the CELL_FACH state.
• the WTRU In the URA_PCH state, no dedicated channel is allocated to the WTRU.
• the WTRU selects a PCH, and uses discontinuous reception for monitoring the selected PCH via an associated PICH. No uplink activity is possible.
• the location of the WTRU is known on a UTRAN registration area level according to the URA assigned to the WTRU during the last URA update in the Cell_FACH state.
• E-RACH enhanced random access channel
• E-DCH enhanced dedicated channel
• the only uplink mechanism for a WTRU in the Cell_FACH state was transmission via the RACH using a slotted-Aloha approach with an acquisition indication message.
• the WTRUs and the network may require the introduction of enhanced MAC-e/es entities in order to enable the communication between the WTRU and the network.
• E-DCH MAC resources Due to the nature of the E-DCH operation in the Cell_FACH state, a number of issues may arise with the E-DCH MAC resources.
• One of the issues relates to defining how and when to set up the enhanced MAC-e/es entities.
• rules regarding the location of the enhanced MAC-e/es entities and whether the enhanced MAC-e and/or enhanced MAC-es are common or dedicated entities are desired.
• additional RNC to Node-B interface (Iub) signaling for the setup and management of the MAC entities are desired. Accordingly methods to manage E-DCH resources and to manage TSN numbering are desired.
• Methods and apparatus are disclosed to manage the enhanced MAC-e and enhanced MAC-es resources and respective variables for the E-DCH in the enhanced Cell_FACH state. Due to the nature of the E-DCH transmission in the uplink (UL) in the Cell_FACH state and the fact that the WTRU might set up and release the E-DCH resources more frequently, methods to manage the TSN numbering are described.
• FIG. 1 is a block diagram of a enhanced MAC-e/es entity of a WTRU
• FIGS. 2 and 2A are block diagrams of enhanced MAC-e/es entities of a Node-B and an RNC, respectively;
• FIG. 3 is a block diagram of the RRC states in an HSPA+ system
• FIG. 4 shows an example wireless communication system including a plurality of wireless transmit/receive units (WTRUs), a base station, and a radio network controller (RNC);
• WTRUs wireless transmit/receive units
• RNC radio network controller
• FIG. 5 is a functional block diagram of a WTRU and the base station of FIG. 4 ;
• FIG. 6 is a flow diagram of a method where the enhanced MAC-e and enhanced MAC-es entities are preconfigured as common entities for each enhanced dedicated channel (E-DCH) resource set that may be assigned to the WTRU upon an E-RACH access procedure.
• E-DCH enhanced dedicated channel
• wireless transmit/receive unit includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a wireless environment.
• base station includes but is not limited to a Node-B, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.
• FIG. 4 shows a wireless communication system 400 including a plurality of WTRUs 410 , a Node-B 420 , a CRNC 430 , an SRNC 440 and a core network 450 .
• the WTRUs 410 are in communication with the Node-B 420 , which is in communication with the CRNC 430 and the SRNC 440 .
• three WTRUs 410 , one Node-B 420 , one CRNC 430 , and one SRNC 440 are shown in FIG. 4 , it should be noted that any combination of wireless and wired devices may be included in the wireless communication system 400 .
• the CRNC 430 and the SRNC 440 may be collectively referred to as the UTRAN.
• FIG. 5 is a functional block diagram 500 of a WTRU 410 and the Node-B 420 of the wireless communication system 400 of FIG. 4 .
• the WTRU 410 is in communication with the Node-B 420 and both are configured to perform a method to manage and setup enhanced MAC-e/es resources in a Cell_FACH state.
• the WTRU 410 includes a processor 415 , a receiver 416 , a transmitter 417 , and an antenna 418 .
• the processor 415 is configured to perform a method to manage and setup enhanced MAC-e/es resources in a Cell_FACH state.
• the receiver 416 and the transmitter 417 are in communication with the processor 415 .
• the antenna 418 is in communication with both the receiver 416 and the transmitter 417 to facilitate the transmission and reception of wireless data.
• the Node-B 420 includes a processor 425 , a receiver 426 , a transmitter 427 , and an antenna 428 .
• the processor 425 is configured to perform a method to manage and setup enhanced MAC-e/es resources in a Cell_FACH state.
• the receiver 426 and the transmitter 427 are in communication with the processor 425 .
• the antenna 428 is in communication with both the receiver 426 and the transmitter 427 to facilitate the transmission and reception of wireless data.
• the WTRU 410 may be configured to transmit on the E-RACH to register the WTRU 410 to the network for an initial RRC connection request, cell selection, and reselection.
• the connection requests are transmitted over the common control channel (CCCH).
• the WTRU may transmit Dedicated Traffic Channel (DTCH) or Dedicated Control Channel (DCCH) traffic to the network.
• DTCH Dedicated Traffic Channel
• DCCH Dedicated Control Channel
• the DTCH is a bi-directional channel that carriers user data and DCCH traffic comprises dedicated control information between a WTRU and the UTRAN. It is established through the RRC (Radio Resource Control) connection setup procedure.
• RRC Radio Resource Control
• the enhanced MAC-e and enhanced MAC-es entities may or may not be setup. Accordingly, several alternatives to configuring the enhanced MAC-e and enhanced MAC-es are described in greater detail herein.
• the WTRU 410 may be configured with an enhanced MAC-e/es entity 419 when both the WTRU 410 and the network support the E-RACH, (i.e. capable of using the E-DCH in the CELL_DACH state) and the HS-DSCH.
• the HS-DSCH is a downlink transport channel shared by several WTRUs.
• the HS-DSCH is assoicated with one downlink dedicated physical channel (DPCH) and one or several highspeed shared control channels (HS-SCCHs).
• DPCH downlink dedicated physical channel
• HS-SCCHs highspeed shared control channels
• the enhanced MAC-e/es entity 419 in the WTRU 410 may include a HARQ module, a multiplexing and TSN module, an E-TFC selection module, segmentation modules, a module used to append an E-RNTI, and a module used for CRC calculation for Common Control Channel (CCCH) traffic.
• the CCCH supports common procedures required to establish a dedicated link with the UTRAN.
• the CCCH may include the RACH and E-RACH, the forward access channel (FACH), and the paging channel (PCH).
• the enhanced MAC-e/es entity 419 may also include an access class control module.
• the WTRU 410 may transition to the Cell_FACH state when there is uplink data to transmit, or it is already in the Cell_DCH state and the network moves it to the Cell_FACH state for lack of activity, etc.
• the WTRU 410 may be configured to maintain the enhanced MAC-e/es entity as long as it is able to transmit uplink data on the E-DCH.
• the WTRU 410 may further be configured to maintain the enhanced MAC-e/es entity when operating in idle mode when an RRC connection request is initiated by the WTRU 410 .
• the Node-B 420 may be configured with x enhanced MAC-e entities (enhanced MAC-e 1 to enhanced MAC-e x ), where x is the number of common E-DCH resources for all types of traffic.
• Each enhanced MAC-e entity may include an E-DCH scheduling module, an E-DCH control module, a de-multiplexing module, and a HARQ module.
• the enhanced MAC-e entities may also be configured to read the E-RNTI used for contention resolution.
• the enhanced MAC-e entities may be configured to communicate with WTRUs that have not been assigned a U-RNTI or E-RNTI, in which case the WTRUs will communicate via the CCCH.
• Each enhanced MAC-e entity may be associated to a common E-DCH resource that a WTRU acquires as part of the random access procedure.
• the Node-B 420 may be configured to use an enhanced MAC-e entity while a WTRU is attempting an E-RACH access and/or after the WTRU has performed cell selection/reselection (i.e. DTCH/DCCH traffic).
• the enhanced MAC-e entities may be preconfigured in the Node-B 420 (i.e. setup when the E-DCH resource pool for the CELL_FACH state and idle-mode is provided to the Node B) or it may be setup in response to a signal received from a WTRU or RNC.
• the Node-B 420 may be configured to setup and maintain one dedicated enhanced MAC-e entity for each WTRU, for as long as the WTRU in a given state.
• the CRNC 430 may be configured with y enhanced MAC-es entities (enhanced MAC-es 1 to enhanced MAC-es y ) used only for CCCH traffic, where y is the number of common E-DCH resources in the cell.
• Each enhanced MAC-es entity is associated to a common E-DCH resource set that may be used by a WTRU.
• Each enhanced MAC-es entity may include a disassembly module, a reordering and queue distribution module, a reordering module, a macro-diversity selection module, a reassembly module, and a CRC error correction module.
• Each enhanced MAC-es entity may be used during communications with a WTRU that has not been assigned a U-RNTI or E-RNTI (i.e. for CCCH traffic).
• the CCCH traffic may be terminated in the CRNC 430 such that the CCCH data traffic is not forwarded to the SRNC 440 .
• the CRNC 430 may be configured to setup one dedicated enhanced MAC-es entity for each WTRU, for as long as the WTRU in a given state.
• the SRNC 440 is configured with z enhanced MAC-es entities (enhanced MAC-es 1 to enhanced MAC-es z ) for the DTCH/DCCH traffic, wherein z is the number of WTRUs in the Cell_FACH state.
• Each of the z enhanced MAC-es entities may be associated with the WTRU 410 after its WTRU-id is determined.
• Each enhanced MAC-es entity may comprise a disassembly module, a reordering and queue distribution module, a reordering module, a macro-diversity selection module, and a reassembly module.
• the SRNC 440 may be configured to setup the enhanced MAC-es entity in response to the WTRU entering the Cell_FACH state.
• the DTCH/DCCH traffic terminates in the SRNC 440 .
• the Node-B 420 and the CRNC 430 may be configured to maintain one dedicated enhanced MAC-e and MAC-es entity, respectively, for each WTRU as long as the WTRU is in the Cell_FACH state, independent of the E-DCH resources.
• the Node-B 420 and the CRNC 430 may be configured to setup enhanced MAC-e and enhanced MAC-es entities after the Node-B 420 assigns and transmits an E-DCH radio network temporary identifier (E-RNTI) for the WTRU 410 .
• E-RNTI E-DCH radio network temporary identifier
• the SRNC 440 may not know the WTRU's 410 identity until the first transmission of the WTRU 410 , which is after reception of the acquisition indicator channel (AICH) or the E-AICH. In such a case, the SRNC 440 may be configured to setup the enhanced MAC-es for the WTRU 410 at the time the WTRU-ID is read from the header. Accordingly, a new Iub signaling procedure may be required to indicate to the SRNC 440 to setup the enhanced MAC-es entity for a given WTRU.
• AICH acquisition indicator channel
• common enhanced MAC-e and/or enhanced MAC-es resources When common enhanced MAC-e and/or enhanced MAC-es resources are setup for a given connection, they may be setup as part of the common transport channel setup procedure between an RNC and the Node-B 420 .
• FIG. 6 is a flow diagram of a method where the CRNC 430 pre-configures and stores a common enhanced MAC-es entity and the Node-B 420 pre-configures and stores a common enhanced MAC-e entity for each enhanced dedicated channel (E-DCH) resource set that may be assigned to a WTRU upon an E-RACH access procedure.
• the CRNC determines an E-DCH resource set and signals the Node-B ( 610 ).
• the CRNC and Node-B pre-configure and store common enhanced MAC-es and enhanced MAC-e entities, respectively, for each E-DCH resource set available ( 620 ).
• a WTRU performs a random access procedure obtains an E-DCH resource set ( 630 ).
• An RRC connection request message is received from a WTRU in Idle Mode using the E-DCH set that is obtained using the random access procedure ( 640 ).
• the Node-B allocates an E-RNTI and an enhanced MAC-es entity is setup in the SRNC for the WTRU ( 650 ).
• the enhanced MAC-e and enhanced MAC-es for the CCCH may be configured to operate as common entities that are associated with one WTRU at a time (i.e. for the WTRU that received the E-RACH access).
• the common enhanced MAC-e and MAC-es entities may be used for only the WTRU's initial traffic.
• the enhanced MAC entities may be used throughout the time the WTRU is communicating via the E-DCH resource set corresponding to that enhanced MAC entity.
• An RRC connection setup complete message may then be received indicating that the WTRU is in connected mode ( 660 ).
• the enhanced MAC-es entity in the CRNC may be associated to a common E-DCH resource set used by the WTRU 410 , or a common E-RNTI that is selected by the WTRU 410 .
• the SRNC 440 may be configured to setup a dedicated enhanced MAC-es entity for each WTRU operating in the Cell_FACH state which is registered and has an E-RNTI allocated, and the entity may be maintained at least for the duration of the WTRU being in the Cell_FACH/CELL_PCH state for DTCH/DCCH traffic.
• the data is first received in the common enhanced MAC-e entity associated to the common E-DCH resource being used by the UE and then forwarded to the dedicated enhanced MAC-es entity in the SRNC over the Iub/Iur interface.
• the enhanced MAC-e is a common entity for any WTRU using the set of resources, a process to identify the WTRU-ID over the Iub/Iur frame protocol may be desired.
• the Node-B 420 may be configured to transmit data on a common transport channel (for WTRUs using the E-DCH in the Cell_FACH state) using an Iub flow. Because the Iub is a common flow, the CRNC 430 may receive data from this common flow per WTRU and does not know to which WTRU this data belongs. Therefore, the Node-B 420 may be configured to transmit a WTRU-ID in the header field of the Iub frame when the enhanced MAC-es is associated with a particular WTRU in the Cell_FACH state (i.e. for DTCH/DCCH traffic). Similarly the CRNC 430 may be configured to transmit a WTRU-ID in the header of an Iur frame.
• the WTRU-id may comprise an E-RNTI when transmitted via the Iub interface or an S-RNTI when transmitted via the Iur interface. This would allow the SRNC 440 to know proper forwarding address of the data to the correct dedicated enhanced MAC-es entity for the WTRU.
• the WTRU-id may comprise one or a combination of the E-RNTI, the U-RNTI, or C-RNTI, or the S-RNTI.
• CCCH traffic no WTRU-id is present and thus the Iub frame protocol shall not include an E-RNTI.
• the CRNC 430 may be configured to detect that the traffic belongs to CCCH traffic from the logical channel identifier and forward the data to the correct enhanced MAC-es entity in the CRNC 430 that is associated to the proper E-DCH resource.
• the Node-B 420 may be configured to receive the CCCH traffic and to forward the data to the transport channel associated with the enhanced MAC-e entity in which the data was received.
• the WTRU 410 may be configured to transmit a WTRU-id in an enhanced MAC-es header of an enhanced MAC-es PDU.
• the Node-B 420 may be further configured with a disassembly module capable of to decoding the enhanced MAC-es PDU header and determining the WTRU-id. By transmitting the information in the enhanced MAC-es PDU, the Node-B 420 does not need to transmit an Iub frame with the WTRU-id information.
• the WTRU 410 may be configured to transmit the WTRU-id in the enhanced MAC-es header only during the initial transmissions for contention resolution purposes.
• the Node-B 420 may be configured with an enhanced MAC-e entity that uses the initial transmission to determine forwarding procedures for consecutive data on subsequent transmissions to the RNC.
• the WTRU 410 may transmit the WTRU-id until it receives an absolute grant of the E-DCH channel, at which point the WTRU 410 can stop transmitting the WTRU-id.
• the Node-B 420 may be configured to receive a WTRU-id from a WTRU, and to extract the WTRU-id from the first transmission. The Node-B 420 may then store the WTRU-id and use this information to transmit the WTRU-id to the SRNC 440 or CRNC 430 using Iub signaling during subsequent transmissions. When the WTRU 410 releases the set of E-DCH resources the Node-B 420 may be configured to erase the WTRU-id. Alternatively, if a subsequent E-RACH access attempt is performed and a different WTRU-id is decoded, the Node-B 420 may change the stored WTRU-id information to reflect the new WTRU-id.
• the Node-B 420 may use the first transmission to determine to which WTRU the data belongs. Once the WTRU-id is determined, the Node-B 420 may setup a semi-dedicated flow to the RNC for the duration of the WTRU's connection to the E-DCH resources. This creates a temporary connection flow between the common enhanced MAC-e and the dedicated enhanced MAC-es. This may be setup by transmitting an Iub signal notifying the RNC to initiate the setup a flow between the common enhanced MAC-e and enhanced MAC-es entity corresponding to the WTRU. In this case, the WTRU-id does not have to be specified in the Iub frame protocol because the WTRU-id is present in the enhanced MAC-e header of every transmission and the information is forwarded to the RNC via the Iu frame protocol.
• the functionalities related to the E-DCH may be moved to the Node-B 420 .
• the logical channel flows may be setup between the enhanced MAC-es and the radio link control (RLC) entities.
• the WTRU 410 and the Node-B 420 may establish a common transport channel and the WTRU-id and a linearization channel (LCH)-ID may be transmitted over the Iub and/or Iur frame protocol.
• LCH linearization channel
• ROM read only memory
• RAM random access memory
• register cache memory
• semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
• Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.
• DSP digital signal processor
• ASICs Application Specific Integrated Circuits
• FPGAs Field Programmable Gate Arrays
• a processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer.
• the WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) or Ultra Wide Band (UWB) module.
• WLAN wireless local area network
• UWB Ultra Wide Band

Abstract

Description

Claims (15)

Priority Applications (5)

Applications Claiming Priority (3)

Related Child Applications (1)

Publications (2)

Family

ID=40545932

Family Applications (5)

Family Applications After (4)

Country Status (13)

Cited By (1)

Families Citing this family (28)

Citations (60)

Family Cites Families (37)

• 2008
  • 2008-10-23 EP EP08842707.5A patent/EP2208383B1/en active Active
  • 2008-10-23 EP EP20209621.0A patent/EP3820243A2/en not_active Withdrawn
  • 2008-10-23 KR KR1020107011268A patent/KR101156811B1/en not_active IP Right Cessation
  • 2008-10-23 WO PCT/US2008/080896 patent/WO2009055536A2/en active Application Filing
  • 2008-10-23 BR BRPI0816595-5A2A patent/BRPI0816595A2/en not_active IP Right Cessation
  • 2008-10-23 KR KR1020147008899A patent/KR101568149B1/en active IP Right Grant
  • 2008-10-23 CN CN200880113030.6A patent/CN101999249B/en active Active
  • 2008-10-23 US US12/256,964 patent/US9271280B2/en active Active
  • 2008-10-23 RU RU2010120914/07A patent/RU2447623C2/en not_active IP Right Cessation
  • 2008-10-23 KR KR1020107013843A patent/KR20100089883A/en not_active Application Discontinuation
  • 2008-10-23 KR KR1020167003544A patent/KR101712872B1/en active IP Right Grant
  • 2008-10-23 PL PL08842707T patent/PL2208383T3/en unknown
  • 2008-10-23 KR KR1020157002626A patent/KR101595423B1/en active Application Filing
  • 2008-10-23 DK DK08842707.5T patent/DK2208383T3/en active
  • 2008-10-23 KR KR1020137031592A patent/KR101571134B1/en active IP Right Grant
  • 2008-10-23 JP JP2010531230A patent/JP5372001B2/en not_active Expired - Fee Related
  • 2008-10-24 TW TW97141068A patent/TWI448130B/en active
  • 2008-10-24 TW TW100107814A patent/TW201220799A/en unknown
  • 2008-10-27 TW TW97219166U patent/TWM355522U/en unknown
  • 2008-10-27 AR ARP080104688A patent/AR069059A1/en active IP Right Grant
• 2010
  • 2010-04-22 IL IL205269A patent/IL205269A0/en unknown
• 2013
  • 2013-09-17 JP JP2013191794A patent/JP5744141B2/en not_active Expired - Fee Related
• 2015
  • 2015-04-28 JP JP2015091454A patent/JP6039738B2/en active Active
• 2016
  • 2016-02-22 US US15/049,922 patent/US9374816B1/en active Active
  • 2016-06-14 US US15/182,218 patent/US9844093B2/en active Active
  • 2016-11-04 JP JP2016216562A patent/JP6606485B2/en active Active
• 2017
  • 2017-12-08 US US15/836,302 patent/US10362622B2/en active Active
• 2019
  • 2019-07-19 US US16/516,893 patent/US20190350036A1/en not_active Abandoned

Patent Citations (64)

Non-Patent Citations (77)

Also Published As

Similar Documents

Legal Events