Method and apparatus for providing error detection in coordination with a radio link layer

An approach includes detecting failure of an error detection scheme relating to transmission of data units of a transport block. A negative acknowledgement message is generated in response to the detection of the failure. The negative acknowledgement message is forwarded to a radio link controller for discarding one or more of the data units.

BACKGROUND

Radio communication systems, such as a wireless data networks (e.g., Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, spread spectrum systems (such as Code Division Multiple Access (CDMA) networks), Time Division Multiple Access (TDMA) networks, WiMAX (Worldwide Interoperability for Microwave Access), etc.), provide users with the convenience of mobility along with a rich set of services and features. This convenience has spawned significant adoption by an ever growing number of consumers as an accepted mode of communication for business and personal uses. To promote greater adoption, the telecommunication industry, from manufacturers to service providers, has agreed at great expense and effort to develop standards for communication protocols that underlie the various services and features. One area of effort involves control signaling to ensure efficient and accurate delivery of data.

SOME EXEMPLARY EMBODIMENTS

Therefore, there is a need for an approach for providing efficient signaling, which can co-exist with already developed standards and protocols.

According to one embodiment of the invention, a method comprises detecting failure of an error detection scheme relating to transmission of data units of a transport block. The method also comprises generating a negative acknowledgement message in response to the detection of the failure. Further, the method comprises forwarding the negative acknowledgement message to a radio link controller for discarding one or more of the data units.

According to another embodiment of the invention, an apparatus comprises logic configured to detect failure of an error detection scheme relating to transmission of data units of a transport block, and to generate a negative acknowledgement message in response to the detection of the failure. The negative acknowledgement message is forwarded to a radio link controller for discarding one or more of the data units.

According to another embodiment of the invention, an apparatus comprises means for detecting failure of an error detection scheme relating to transmission of data units of a transport block. The apparatus also comprises means for generating a negative acknowledgement message in response to the detection of the failure. The apparatus further comprises means for forwarding the negative acknowledgement message to a radio link controller for discarding one or more of the data units.

According to another embodiment of the invention, a method comprises generating, at a radio link control layer, a protocol data unit transporting one or more service data units. The method also comprises forwarding the protocol data unit to an error detection logic configured to execute an error detection scheme relating to transmission of the protocol data unit, and to determine transmission failure of the protocol data unit. Additionally, the method comprises receiving a negative acknowledgement message, at the radio link control layer, from the error detection logic. Further, the method comprises discarding one or more of the service data units in response to the negative acknowledgement message.

According to another embodiment of the invention, an apparatus comprises a radio link controller configured to generate a protocol data unit transporting one or more service data units, and to forward the protocol data unit to an error detection logic configured to execute an error detection scheme relating to transmission of the protocol data unit, and to determine transmission failure of the protocol data unit. The radio link controller is further configured to receive a negative acknowledgement message from the error detection logic, and to discard one or more of the service data units in response to the negative acknowledgement message.

According to yet another embodiment of the invention, an apparatus comprises means for generating, at a radio link control layer, a protocol data unit transporting one or more service data units. The apparatus also comprises means for forwarding the protocol data unit to an error detection logic configured to execute an error detection scheme relating to transmission of the protocol data unit, and to determine transmission failure of the protocol data unit. The apparatus further comprises means for receiving a negative acknowledgement message, at the radio link control layer, from the error detection logic; and means for discarding one or more of the service data units in response to the negative acknowledgement message.

DESCRIPTION OF PREFERRED EMBODIMENTS

An apparatus, method, and software for providing hybrid automatic repeat request (HARQ) interaction with a radio link control (RLC) layer are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It is apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention.

Although the embodiments of the invention are discussed with respect to a wireless network compliant with a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) architecture, it is recognized by one of ordinary skill in the art that the embodiments of the inventions have applicability to any type of communication system and equivalent functional capabilities.

FIG. 1is a diagram of a communication system capable of providing local negative acknowledgement, according to an exemplary embodiment. As shown inFIG. 1, one or more user equipment (UEs)101communicate with a base station103, which is part of an access network (e.g., 3GPP LTE (or E-UTRAN, etc.). Under the 3GPP LTE architecture (as shown inFIGS. 6A-6D), the base station103is denoted as an enhanced Node B (eNB). The UE101can be any type of mobile stations, such as handsets, terminals, stations, units, devices, multimedia tablets, Internet nodes, communicators, Personal Digital Assistants or any type of interface to the user (such as “wearable” circuitry, etc.). The UE101includes a transceiver (not shown) and an antenna system105that couples to the transceiver to receive or transmit signals from the base station103. The antenna system105can include one or more antennas.

As with the UE101, the base station103employs a transceiver (not shown), which transmits information to the UE101. Also, the base station103can employ one or more antennas107for transmitting and receiving electromagnetic signals. For instance, the Node B103may utilize a Multiple Input Multiple Output (MIMO) antenna system107, whereby the Node B103can support multiple antenna transmit and receive capabilities. This arrangement can support the parallel transmission of independent data streams to achieve high data rates between the UE101and Node B103. The base station103, in an exemplary embodiment, uses OFDM (Orthogonal Frequency Divisional Multiplexing) as a downlink (DL) transmission scheme and a single-carrier transmission (e.g., SC-FDMA (Single Carrier-Frequency Division Multiple Access) with cyclic prefix for the uplink (UL) transmission scheme. SC-FDMA can also be realized using a DFT-S-OFDM principle, which is detailed in 3GGP TR 25.814, entitled “Physical Layer Aspects for Evolved UTRA,” v.1.5.0, May 2006 (which is incorporated herein by reference in its entirety). SC-FDMA, also referred to as Multi-User-SC-FDMA, allows multiple users to transmit simultaneously on different sub-bands.

To ensure reliable data transmission, the system100ofFIG. 1, in certain embodiments, uses concatenation of Forward Error Correction (FEC) coding and an Automatic Repeat Request (ARQ) protocol commonly known as Hybrid ARQ (HARQ). Automatic Repeat Request (ARQ) is an error detection mechanism using error detection logic109,111. This mechanism permits the receiver (either UE101or base station103) to indicate to the transmitter (either UE101or base station103) that a packet or sub-packet has been received incorrectly, and thus, the receiver can request the transmitter to resend the particular packet(s). This can be accomplished with a Stop and Wait (SAW) procedure, in which the transmitter waits for a response from the receiver before sending or resending packets. The erroneous packets are used in conjunction with retransmitted packets.

According to certain embodiments, the system100provides synchronous HARQ and asynchronous HARQ. Synchronous HARQ means that the network is restricted in allocation of resources for re-transmission. This suggests that the network needs to re-use current allocation either with (scheduled synchronous) or without (unscheduled synchronous) any changes, at specific time/frequency after the first transmission (new data transmission). By contrast, with asynchronous HARQ, no timing requirements with respect to scheduling of resources to the UE101are needed for the HARQ re-transmission.

From the perspective of the UE101, synchronous HARQ is simple and allows for power saving. However, this scheme does restrict the scheduling freedom of packets in the network, potentially affecting the amount of needed re-transmissions so as to increase UE power consumption (e.g., in the case of unfavorable scheduling options). From the scheduler point of view, the benefit of synchronous re-transmission is that there is no need to use any channel resources for scheduling of re-transmissions.

According to certain embodiments, the system100provides for generating a local negative acknowledgement (NACK) message to a Radio Link Controller (RLC)113,115upon detection of a Hybrid Automatic Repeat Request (HARQ) failure in a sending entity. For example, assuming the NACK is received by the base station103, the RLC115then discards data associated with the data transmission that triggered the HARQ failure if the RLC cannot recover the lost data transmission due to the HARQ failure. Such recovery is not possible, for example, in the case of unacknowledged mode operation, or in the situation involving the last retransmission in the acknowledged mode operation.

The RLC115provides RLC layer functions. For instance, the RLC115provides segmentation and concatenation on the data received from an upper layer. The RLC layer ensures quality of service (QoS) guarantees, and defines the following types of RLC modes of operation: a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). These three RLC modes support different QoS levels. The RLC layer is more fully described below and in 3GPP TS36.300, which is incorporated herein by reference in its entirety.

The system100provides various channel types: physical channels, transport channels, and logical channels. In this example, the physical channels are established between the UE101and the base station103, and transport channels and logical channels are established among the UE101, BS103and a Radio Network Controller (RNC) (not shown). Physical channels can include a physical downlink shared channel (PDSCH), a dedicated physical downlink dedicated channel (DPDCH), a dedicated physical control channel (DPCCH), etc.

The transport channels can be defined by how they transfer data over the radio interface and the characteristics of the data. The transport channels include a broadcast channel (BCH), paging channel (PCH), a dedicated shared channel (DSCH), etc. Other exemplary transport channels are an uplink (UL) Random Access Channel (RACH), Common Packet Channel (CPCH), Forward Access Channel (FACH), Downlink Shared Channel (DSCH), Uplink Shared Channel (USCH), Broadcast Channel (BCH), and Paging Channel (PCH). A dedicated transport channel is the UL/DL Dedicated Channel (DCH). Each transport channel is mapped to one or more physical channels according to its physical characteristics.

Moreover, each logical channel can be defined by the type and required Quality of Service (QoS) of information that it carries. The associated logical channels include, for example, a broadcast control channel (BCCH), a paging control channel (PCCH), Dedicated Control Channel (DCCH), Common Control Channel (CCCH), Shared Channel Control Channel (SHCCH), Dedicated Traffic Channel (DTCH), Common Traffic Channel (CTCH), etc.

According to one embodiment, layer 2 utilized by the system100ofFIG. 1includes the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC) and Packet Data Convergence Protocol (PDCP). Service Access Points (SAP) for peer-to-peer communication are marked with circles at the interface between sublayers. The SAP between the physical layer and the MAC sublayer provides the transport channels. The SAPs between the MAC sublayer and the RLC sublayer provide the logical channels. The multiplexing of several logical channels (i.e., radio bearers) on the same transport channel (i.e. transport block) is performed by the MAC sublayer.

FIG. 2is a diagram of a communication system capable of providing hybrid automatic repeat request (HARQ) interaction with a radio link control (RLC) layer, according to an exemplary embodiment. As seen, a receiver and a transmitter include a radio link control (RLC) layer (or entity) and a HARQ process. In the system100ofFIG. 1, the UE101and the eNB103can assume either role of receiver or transmitter depending on the particular direction of communication. By way of example, the process is explained wherein the UE101behaves as a receiver, while the eNB103is the transmitter. In the TM RLC mode, no overhead is attached to the RLC SDU (Service Data Unit) received from an upper layer protocol when constituting a RLC PDU (Protocol Data Unit). The RLC can pass the SDU in a transparent manner.

The UM RLC and AM RLC modes both entail some overhead that is added at the RLC. The format of RLC PDU is shown inFIG. 4. Segmentation is performed according to the size of the transport block (TB). If an RLC SDU does not fit entirely into the transport block (TB), then the RLC SDU is segmented into variable sized RLC PDUs (which do not include any padding). Data transmission involves adding to each PDU a PDU header that specifies a sequence number (SN), such that the receiving end101can know its order and which PDU had been lost during transmission (i.e., the PDU is missing).

With UM RLC, the transmitter103does not check whether the receiving end properly received the corresponding PDU, and the missing PDUs cannot be recovered. From the receiver side, the particular missing PDUs are determined by referring to the sequence numbers of the received PDUs. The receiver101does not wait for retransmission of the missing PDUs. Given this characteristic, the UM RLC, in the user plane, can support real-time transmissions (e.g., Voice over IP (VoIP), audio and video streaming, etc.).

With AM RLC, unlike UM RLC, the receiver101provides acknowledgement for received PDUs. Thus, missing PDUs are re-transmitted. The AM RLC mode of operation is well-suited for non-real-time packet data transmissions.

In this LTE system ofFIG. 1, Hybrid ARQ (HARQ) interaction with RLC is specified. As mentioned, this mechanism permits the receiver101to indicate to the transmitter103that a packet or sub-packet has been received incorrectly, and thus, requests the transmitter103to resend the particular packet(s). HARQ is performed on each transport block (TB), which is a concatenated block of RLC PDUs belonging to different logical channels. Cyclic Redundancy Check (CRC) is performed by the physical layer on the receiver side to detect an error of the transport block (TB).

Generally, acknowledgement/negative acknowledgement (ACK/NACK) signaling in the HARQ scheme follows with each transmitted packet either by using explicit signalling or implicit signaling. Namely, ACK is used to indicate the correctly received packet. However, a NACK message indicates the packet is not received correctly.

Although HARQ/ARQ is specified in LTE for the error recovery, it is recognized that the information from HARQ is also useful for the SDU discard to achieve better radio utilization. In the unacknowledged mode (UM) operation of radio link controller (RLC), and in the acknowledged mode (AM) operation of RLC when the maximum number of ARQ retransmission is reached, the lost segments due to the HARQ failure cannot be recovered as no ARQ retransmission is performed for them. Furthermore, if a segment of an IP packet is lost, the IP packet cannot be used at all, and is to be discarded on receiver side. Therefore, transmitting the other segments of the same RLC SDU is a waste of radio resource.

In this exemplary scenario, the transmitter Radio Link Control (RLC) entity (e.g., RLC115) signals a sequence number (SN) in the PDU header, which is used by the receiver101to ensure that no PDUs are lost in the transmission. If there are PDUs lost during the transmission, as realized by the out-of-sequence delivery of PDUs, the receiving RLC entity sends a status report PDU to inform the sending RLC entity that certain PDUs are missing. The status report PDU describes the status of the successful and/or unsuccessful data transmissions, identifying the SNs of the PDUs that are lost or received. If a PDU is lost, the sending RLC entity retransmits a duplicate of the lost PDU to the receiving RLC. Although the HARQ operation removes some failed transmissions and increases the probability of successful delivery of data, it is the RLC protocol layer that ultimately ensures successful delivery.

InFIG. 2, the RLC entity115sends, as in step201, a RLC PDU to the HARQ entity111, which in turn, communicates with the HARQ entity109of the receiver101. According to one embodiment, the MAC sublayer (not shown) multiplexes RLC PDUs from different logical channels into a single transport block; the HARQ is performed on the transport block. In this scenario, the HARQ entity111indicates a CRC error, per step203. As such, the HARQ entity109signals a NACK to the HARQ entity111of the transmitter103(step205). At this point the HARQ entity111declares a HARQ failure, resulting in transmission of a local NACK to the local RLC115, as in steps207and209. As noted, the HARQ mechanism is applied to the single transport block. Hence, in such a case, the local NACK pertains to this transport block, and not for each individual RLC PDU.

The local RLC115can then discard, per step211, any RLC SDUs that have yet to be transmitted. This discard process is applicable in the UM or, if the data units are associated with the last retransmission, in the AM. Further details of this process are explained with respect toFIG. 3.

FIG. 3is a flowchart of a process for providing local acknowledgement signaling and discard of associated data units, according to an exemplary embodiment. Continuing with the example ofFIG. 2, if HARQ entity111of the transmitter103(also referred to as “HARQ transmitter”) decides that a HARQ failure has occurred (step301), the HARQ transmitter111generates and effectively provides a local NACK message, as in step303, to the RLC115of the transmitter103. It is noted that this local NACK need not be directed only to HARQ entity111, but also to RLC115in general. If RLC115receives a local NACK (step305), the RLC115checks all UM logical channels that are transmitting RLC PDUs into the corresponding transport block, and all AM logical channels that are transmitting the last retransmission of RLC PDUs into the corresponding transport block. That is, the RLC115notes all the PDUs associated with the failed transport block, per steps307and309.

Subsequently, the RLC discards all the RLC SDUs to which the transmitted RLC PDUs belong, per step311. In addition, in step313, other necessary operation related to the SDU discard such as the reporting to the upper layer, if any, is also performed as usual.

According to various embodiments, the communication system ofFIG. 1utilizes an architecture compliant with the UMTS terrestrial radio access network (UTRAN) or Evolved UTRAN (E-UTRAN) in 3GPP.

FIG. 4is diagram of a protocol data unit (PDU) for a PDU format for supporting acknowledged mode (AM) and unacknowledged mode (UM), according to an exemplary embodiment of the invention. As seen, a RLC PDU structure401includes an RLC header403, which specifies the PDU sequence number. A RLC SDU structure405, in this example, are segmented, n, n+1, n+2, n+3, . . . . Because concatenation is performed in sequence, the content of the RLC PDU401can generally be described by the following relations: {0; 1} last segment of SDUi+[0; n] complete SDUs+{0; 1} first segment of SDUi+n+1; or 1 segment of SDUi.

The described processes, according to certain embodiments, provide efficient use of radio resources by avoiding unnecessary transmissions.

One of ordinary skill in the art would recognize that the processes for providing error correction may be implemented via software, hardware (e.g., general processor, Digital Signal Processing (DSP) chip, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGAs), etc.), firmware, or a combination thereof. Such exemplary hardware for performing the described functions is detailed below with respect toFIG. 5.

FIG. 5illustrates exemplary hardware upon which various embodiments of the invention can be implemented. A computing system500includes a bus501or other communication mechanism for communicating information and a processor503coupled to the bus501for processing information. The computing system500also includes main memory505, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus501for storing information and instructions to be executed by the processor503. Main memory505can also be used for storing temporary variables or other intermediate information during execution of instructions by the processor503. The computing system500may further include a read only memory (ROM)507or other static storage device coupled to the bus501for storing static information and instructions for the processor503. A storage device509, such as a magnetic disk or optical disk, is coupled to the bus501for persistently storing information and instructions.

The computing system500may be coupled with the bus501to a display511, such as a liquid crystal display, or active matrix display, for displaying information to a user. An input device513, such as a keyboard including alphanumeric and other keys, may be coupled to the bus501for communicating information and command selections to the processor503. The input device513can include a cursor control, such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor503and for controlling cursor movement on the display511.

According to various embodiments of the invention, the processes described herein can be provided by the computing system500in response to the processor503executing an arrangement of instructions contained in main memory505. Such instructions can be read into main memory505from another computer-readable medium, such as the storage device509. Execution of the arrangement of instructions contained in main memory505causes the processor503to perform the process steps described herein. One or more processors in a multi-processing arrangement may also be employed to execute the instructions contained in main memory505. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the embodiment of the invention. In another example, reconfigurable hardware such as Field Programmable Gate Arrays (FPGAs) can be used, in which the functionality and connection topology of its logic gates are customizable at run-time, typically by programming memory look up tables. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.

The computing system500also includes at least one communication interface515coupled to bus501. The communication interface515provides a two-way data communication coupling to a network link (not shown). The communication interface515sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information. Further, the communication interface515can include peripheral interface devices, such as a Universal Serial Bus (USB) interface, a PCMCIA (Personal Computer Memory Card International Association) interface, etc.

The processor503may execute the transmitted code while being received and/or store the code in the storage device509, or other non-volatile storage for later execution. In this manner, the computing system500may obtain application code in the form of a carrier wave.

FIGS. 6A-6Dare diagrams of communication systems having exemplary long-term evolution (LTE) architectures, in which the user equipment (UE) and the base station ofFIG. 1can operate, according to various exemplary embodiments of the invention. By way of example (shown inFIG. 6A), a base station (e.g., destination node103) and a user equipment (UE) (e.g., source node101) can communicate in system600using any access scheme, such as Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Orthogonal Frequency Division Multiple Access (OFDMA) or Single Carrier Frequency Division Multiple Access (FDMA) (SC-FDMA) or a combination of thereof. In an exemplary embodiment, both uplink and downlink can utilize WCDMA. In another exemplary embodiment, uplink utilizes SC-FDMA, while downlink utilizes OFDMA.

The communication system600is compliant with 3GPP LTE, entitled “Long Term Evolution of the 3GPP Radio Technology” (which is incorporated herein by reference in its entirety). As shown inFIG. 6A, one or more user equipment (UEs)101communicate with a network equipment, such as a base station103, which is part of an access network (e.g., WiMAX (Worldwide Interoperability for Microwave Access), 3GPP LTE (or E-UTRAN), etc.). Under the 3GPP LTE architecture, base station103is denoted as an enhanced Node B (eNB).

MME (Mobile Management Entity)/Serving Gateways601are connected to the eNBs103in a full or partial mesh configuration using tunneling over a packet transport network (e.g., Internet Protocol (IP) network)603. Exemplary functions of the MME/Serving GW601include distribution of paging messages to the eNBs103, termination of U-plane packets for paging reasons, and switching of U-plane for support of UE mobility. Since the GWs601serve as a gateway to external networks, e.g., the Internet or private networks603, the GWs601include an Access, Authorization and Accounting system (AAA)605to securely determine the identity and privileges of a user and to track each user's activities. Namely, the MME Serving Gateway601is the key control-node for the LTE access-network and is responsible for idle mode UE tracking and paging procedure including retransmissions. Also, the MME601is involved in the bearer activation/deactivation process and is responsible for selecting the SGW (Serving Gateway) for a UE at the initial attach and at time of intra-LTE handover involving Core Network (CN) node relocation.

A more detailed description of the LTE interface is provided in 3GPP TR 25.813, entitled “E-UTRA and E-UTRAN: Radio Interface Protocol Aspects,” which is incorporated herein by reference in its entirety.

InFIG. 6B, a communication system602supports GERAN (GSM/EDGE radio access)604, and UTRAN606based access networks, E-UTRAN612and non-3GPP (not shown) based access networks, and is more fully described in TR 23.882, which is incorporated herein by reference in its entirety. A key feature of this system is the separation of the network entity that performs control-plane functionality (MME608) from the network entity that performs bearer-plane functionality (Serving Gateway610) with a well defined open interface between them S11. Since E-UTRAN612provides higher bandwidths to enable new services as well as to improve existing ones, separation of MME608from Serving Gateway610implies that Serving Gateway610can be based on a platform optimized for signaling transactions. This scheme enables selection of more cost-effective platforms for, as well as independent scaling of, each of these two elements. Service providers can also select optimized topological locations of Serving Gateways610within the network independent of the locations of MMEs608in order to reduce optimized bandwidth latencies and avoid concentrated points of failure.

As seen inFIG. 613, the E-UTRAN (e.g., eNB)612interfaces with UE101via LTE-Uu. The E-UTRAN612supports LTE air interface and includes functions for radio resource control (RRC) functionality corresponding to the control plane MME608. The E-UTRAN612also performs a variety of functions including radio resource management, admission control, scheduling, enforcement of negotiated uplink (UL) QoS (Quality of Service), cell information broadcast, ciphering/deciphering of user, compression/decompression of downlink and uplink user plane packet headers and Packet Data Convergence Protocol (PDCP).

The MME608, as a key control node, is responsible for managing mobility UE identifies and security parameters and paging procedure including retransmissions. The MME608is involved in the bearer activation/deactivation process and is also responsible for choosing Serving Gateway610for the UE101. MME608functions include Non Access Stratum (NAS) signaling and related security. MME608checks the authorization of the UE101to camp on the service provider's Public Land Mobile Network (PLMN) and enforces UE101roaming restrictions. The MME608also provides the control plane function for mobility between LTE and 2G/3G access networks with the S3interface terminating at the MME608from the SGSN (Serving GPRS Support Node)614.

The SGSN614is responsible for the delivery of data packets from and to the mobile stations within its geographical service area. Its tasks include packet routing and transfer, mobility management, logical link management, and authentication and charging functions. The S6ainterface enables transfer of subscription and authentication data for authenticating/authorizing user access to the evolved system (AAA interface) between MME608and HSS (Home Subscriber Server)616. The S10interface between MMEs608provides MME relocation and MME608to MME608information transfer. The Serving Gateway610is the node that terminates the interface towards the E-UTRAN612via S1-U.

The S1-U interface provides a per bearer user plane tunneling between the E-UTRAN612and Serving Gateway610. It contains support for path switching during handover between eNBs103. The S4interface provides the user plane with related control and mobility support between SGSN614and the 3GPP Anchor function of Serving Gateway610.

The S12is an interface between UTRAN606and Serving Gateway610. Packet Data Network (PDN) Gateway618provides connectivity to the UE101to external packet data networks by being the point of exit and entry of traffic for the UE101. The PDN Gateway618performs policy enforcement, packet filtering for each user, charging support, lawful interception and packet screening. Another role of the PDN Gateway618is to act as the anchor for mobility between 3GPP and non-3GPP technologies such as WiMax and 3GPP2 (CDMA 1× and EvDO (Evolution Data Only)).

The S7interface provides transfer of QoS policy and charging rules from PCRF (Policy and Charging Role Function)620to Policy and Charging Enforcement Function (PCEF) in the PDN Gateway618. The SGi interface is the interface between the PDN Gateway and the operator's IP services including packet data network622. Packet data network622may be an operator external public or private packet data network or an intra operator packet data network, e.g., for provision of IMS (IP Multimedia Subsystem) services. Rx+ is the interface between the PCRF and the packet data network622.

As seen inFIG. 6C, the eNB103utilizes an E-UTRA (Evolved Universal Terrestrial Radio Access) (user plane, e.g., RLC (Radio Link Control)615, MAC (Media Access Control)617, and PHY (Physical)619, as well as a control plane (e.g., RRC621)). The eNB103also includes the following functions: Inter Cell RRM (Radio Resource Management)623, Connection Mobility Control625, RB (Radio Bearer) Control627, Radio Admission Control629, eNB Measurement Configuration and Provision631, and Dynamic Resource Allocation (Scheduler)633.

The eNB103communicates with the aGW601(Access Gateway) via an S1interface. The aGW601includes a User Plane601aand a Control plane601b. The control plane601bprovides the following components: SAE (System Architecture Evolution) Bearer Control635and MM (Mobile Management) Entity637. The user plane601bincludes a PDCP (Packet Data Convergence Protocol)639and a user plane functions641. It is noted that the functionality of the aGW601can also be provided by a combination of a serving gateway (SGW) and a packet data network (PDN) GW. The aGW601can also interface with a packet network, such as the Internet643.

In an alternative embodiment, as shown inFIG. 6D, the PDCP (Packet Data Convergence Protocol) functionality can reside in the eNB103rather than the GW601. Other than this PDCP capability, the eNB functions ofFIG. 6Care also provided in this architecture.

In the system ofFIG. 6D, a functional split between E-UTRAN and EPC (Evolved Packet Core) is provided. In this example, radio protocol architecture of E-UTRAN is provided for the user plane and the control plane. A more detailed description of the architecture is provided in 3GPP TS 86.300.

The eNB103interfaces via the S1to the Serving Gateway645, which includes a Mobility Anchoring function647. According to this architecture, the MME (Mobility Management Entity)649provides SAE (System Architecture Evolution) Bearer Control651, Idle State Mobility Handling653, and NAS (Non-Access Stratum) Security655.

FIG. 7is a diagram of exemplary components of an LTE terminal capable of operating in the systems ofFIGS. 6A-6D, according to an embodiment of the invention. An LTE terminal700is configured to operate in a Multiple Input Multiple Output (MIMO) system. Consequently, an antenna system701provides for multiple antennas to receive and transmit signals. The antenna system701is coupled to radio circuitry703, which includes multiple transmitters705and receivers707. The radio circuitry encompasses all of the Radio Frequency (RF) circuitry as well as base-band processing circuitry. As shown, layer-1 (L1) and layer-2 (L2) processing are provided by units709and711, respectively. Optionally, layer-3 functions can be provided (not shown). Module713executes all MAC layer functions. A timing and calibration module715maintains proper timing by interfacing, for example, an external timing reference (not shown). Additionally, a processor717is included. Under this scenario, the LTE terminal700communicates with a computing device719, which can be a personal computer, work station, a PDA, web appliance, cellular phone, etc.