BR112016016480B1 - TECHNIQUES FOR SWITCHING SUPPORTS BETWEEN RADIO ACCESS TECHNOLOGIES (RATS) - Google Patents

Abstract

TECHNIQUES FOR SWITCHING SUPPORTS BETWEEN RADIO ACCESS TECHNOLOGIES (RATS). A method, apparatus, and computer program product for wireless communication are provided. The apparatus serves data to a UE or receives data from the UE over a first communication link using a first RAT, transmits a configuration message to the UE indicating that the data will be served or received over a second communication link that uses a second RAT, and initiates a configuration procedure to switch service or data reception from the first communication link using the first RAT to the second communication link using the second RAT.

Description

Cross Reference to Related Orders

[0001] This application claims the benefits of provisional application U.S. No. 61/928,947, entitled "TECHNIQUES FOR SWITCHING BEARERS BETWEEN RADIO ACCESS TECHNOLOGIES (RATS)" and filed on January 17, 2014, and U.S. patent application No. 14/ 598,170, entitled "TECHNIQUES FOR SWITCHING BEARERS BETWEEN RADIO ACCESS TECHNOLOGIES (RATS)" and filed January 15, 2015, which are expressly incorporated by reference herein in their entirety.

Fundamentals Field

[0002] The present description generally refers to communication systems, and more particularly, to techniques for switching media between radio access technologies (RATs).

Fundamentals

[0003] Wireless communication systems are widely developed to provide various telecommunication services such as telephony, video, data, messaging and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (eg, bandwidth, transmission power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, frequency division multiple access systems frequency division multiple access (OFDMA), single-bearer frequency division multiple access (SC-FDMA) systems, and time-division synchronized code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that allows different wireless devices to communicate on a city, national, regional and even global level. An example of an emerging telecommunication standard is Long Term Evolution (LTE). LTE is a suite of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard enacted by the 3rd Partnership Project. Generation (3GPP). LTE is designed to better support mobile broadband Internet access by providing spectral efficiency, reducing costs, improving services, making use of new spectrum and improving integration with other open standards using OFDMA downlink (DL), SC-FDMA in uplink (UL) and multiple-input, multiple-output (MIMO) antenna technology. However, as the demand for mobile broadband access continues to increase, there is a need to create further enhancements to LTE technology. Preferably, these enhancements should be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

summary

[0005] In one aspect of the description, techniques for switching bearers between radio access technologies (RATs) are provided. In one aspect of the description, a method, a computer program product, and an apparatus are provided. In one aspect, a method performed by an apparatus includes serving data to a user equipment (UE) or receiving data from the UE over a first communication link utilizing a first RAT, transmitting a configuration message to the UE indicating that the data will be served or received through a second communication link that uses a second RAT, and initiate a configuration procedure to switch the service or reception of data from the first communication link that uses the first RAT to the second communication link that uses the second RAT.

[0006] The method additionally includes the determination of data without acknowledgment of receipt of data served using the first RAT.

[0007] In one aspect, the method further includes sending data without acknowledgment to be served using the second RAT.

[0008] In one aspect, the configuration message may comprise a data status report and a request for a data status report from the UE.

[0009] In one aspect, the method further includes determining to serve the data using the second RAT based on at least one condition.

[0010] In an aspect, the at least one condition comprises receiving a physical layer acknowledgment for the UE configuration message, receiving a radio resource control (RRC) message in response to the UE configuration message, settings.

[0011] In one aspect, the method further includes reconfiguration of a radio link control (RLC) layer after determining to serve the data using the second RAT.

[0012] In an aspect, the method further includes receiving at least one protocol layer status report from the UE, the at least one protocol layer status report identifying data received by the UE via the first RAT, where unacknowledged data is determined based on at least one protocol layer status report.

[0013] In an aspect, the at least one protocol layer status report is received through the first RAT.

[0014] In an aspect, the at least one protocol layer status report comprises at least one of a packet data convergence protocol (PDCP) layer status report or a data control layer status report link (RLC).

[0015] In an aspect, the method further includes receiving an acknowledgment message from the UE for the configuration message over the first communication link using the first RAT, where at least one layer status report protocol is received from the UE simultaneously with the acknowledgment message or within the acknowledgment message.

[0016] In one aspect, the method further includes receiving an acknowledgment from the UE for the configuration message, where the unacknowledged data is sent to the second RAT in response to the received acknowledgment.

[0017] In an aspect, the method further includes detecting a physical layer acknowledgment for the configuration message, where the unacknowledged data is sent in response to the detected physical layer acknowledgment.

[0018] In an aspect, the method further includes sending at least one protocol layer status report to the UE.

[0019] In an aspect, the at least one protocol layer status report is sent to the UE concurrently with the configuration message or within the configuration message or other signaling message.

[0020] In an aspect, the method further includes sending at least one protocol layer status report on a data carrier being switched.

[0021] In one aspect, the method further includes sending at least one protocol layer situation report or other data carrier that is not being switched and that is served by the first communication link that uses the first RAT or the second communication link that uses the second RAT.

[0022] In an aspect, the at least one protocol layer status report is sent via the first RAT or the second RAT.

[0023] In an aspect, the at least one protocol layer status report is sent to the UE via the first RAT concurrently with the configuration message, upon receipt of a physical layer acknowledgment from the UE for the message configuration message, or upon receipt of an acknowledgment message from the UE for the configuration message.

[0024] In an aspect, the at least one protocol layer status report comprises at least one of a packet data convergence protocol (PDCP) layer status report or a data control layer status report radio link (RLC).

[0025] In one aspect, the method further includes receiving feedback from an access point (AP), where the feedback information indicates the status for successfully or unsuccessfully transmitted data packets.

[0026] In one aspect, the method further includes storing a copy of the data to be served over the second communication link using the second RAT in a store.

[0027] In an aspect, the method further includes receiving feedback from an AP or UE for a success situation in the transmission of packets, determining, based on the feedback information, whether an amount of sent data that is waiting in a storage of the UE or the AP exceeds a limit, and not sending further data to the AP when the amount of data in the storage of the AP exceeds the limit.

[0028] In an aspect, the method further includes stopping sending data to the AP or UE when the number of failed packets due to transmission errors in the second RAT exceeds a threshold.

[0029] In an aspect, the method further includes sending and receiving at least one protocol layer status report to and from the UE via the first communication link that uses the first RAT or the second communication link that uses the second RAT.

[0030] In an aspect, the at least one protocol layer status report is received via an AP or the UE when the at least one protocol layer status report is received via the second RAT.

[0031] In an aspect, the method further includes stopping sending data to the AP or UE when the number of failed packets due to transmission errors on the second communication link using the second RAT exceeds a threshold.

[0032] In one aspect, the method further includes receiving data served from a network or data transmitted to the network via a first communication link utilizing a first RAT, receiving a configuration message from the network indicating that data will be served from the network or transmitted to the network via a second communication link using a second RAT, the configuration of at least one protocol layer based on the received configuration message to receive data served from the network or transmitting data to the network via the second communication link using the second RAT, receiving data served from the network or transmitting data to the network via the second communication link using the second RAT.

[0033] In an aspect, the method further includes transmitting at least one of a physical layer negative acknowledgment for the configuration message or a radio resource control (RRC) message in response to the configuration message.

[0034] In an aspect, the method further includes transmitting at least one physical layer acknowledgment for the configuration message or a radio resource control (RRC) message in response to the configuration message.

[0035] In an aspect, the method further includes starting a timer after transmitting the physical layer acknowledgment, waiting for receipt of at least one protocol layer status report until the timer expires, and resetting one or more protocol layers after the timer expires.

[0036] In one aspect, the method additionally includes the release of a storer for storing the data received through the second communication link that uses the second RAT after the configuration of at least one protocol layer.

[0037] In an aspect, the method further includes transmitting at least one protocol layer status report to the network, the at least one protocol layer status report identifying data received by the UE via the first RAT or second RAT.

[0038] In an aspect, the method further includes sending at least one protocol layer status report in a configuration acknowledgment message or other signaling message.

[0039] In an aspect, the method further includes sending at least one protocol layer status report on a data carrier being switched.

[0040] In one aspect, the method further includes sending at least one protocol layer situation report on another data carrier that is not being contacted and that is served by the first communication link that uses the first RAT or the second communication link that uses the second RAT.

[0041] In an aspect, the at least one protocol layer status report is transmitted over the first communication link that uses the first RAT.

[0042] In an aspect, the at least one protocol layer status report comprises at least one of a packet data convergence protocol (PDCP) layer status report or a data control layer status report radio link (RLC).

[0043] In an aspect, the method further includes transmitting an acknowledgment message to the network for the received configuration message simultaneously with at least one protocol layer status report over the first communication link using the first RAT, or by transmitting an acknowledgment message that includes the at least one protocol layer status report to the network for the configuration message received over the first communication link using the first RAT.

[0044] In an aspect, the method further includes receiving at least one protocol layer status report.

[0045] In an aspect, the at least one protocol layer status report is received concurrently with the configuration message or within the configuration message.

[0046] In an aspect, the at least one protocol layer status report is received via the first RAT or second RAT.

[0047] In an aspect, the at least one protocol layer status report is received via the first RAT concurrently with the configuration message, after transmission of a physical layer acknowledgment to the network for the configuration message , or after transmitting an acknowledgment message to the network for the configuration message.

[0048] In an aspect, the at least one protocol layer status report comprises at least one of a Packet Data Convergence Protocol (PDCP) layer status report or a data control layer status report radio link (RLC).

[0049] In one aspect, the method further includes transmitting the feedback information to the network through an AP using the second communication link, where the feedback information indicates the status for successfully transmitted and failed data packets.

[0050] In one aspect, the method additionally includes transmitting information back to the network for a successful packet transmission situation.

[0051] In one aspect, the method further includes sending and receiving at least one protocol layer status report to and from the network via the first communication link using the first RAT or the second communication link using the second RAT.

[0052] In an aspect, the at least one protocol layer status report is sent to the network via an AP when the at least one protocol layer status report is sent via the second communication link utilizing the second RAT.

[0053] In an aspect, a method performed by an apparatus includes serving data sent over a network to a UE over a first communication link utilizing a first RAT, receiving a message from the network indicating that the data will be served to the UE through a second communication link that uses a second RAT, no longer serving the data to the UE through the first communication link that uses the first RAT after receiving the message.

[0054] In one aspect, the method further includes deletion of unacknowledged data stored in a buffer after receipt of the message.

[0055] In an aspect, the method further includes not serving more data sent over the network to the UE when an amount of failed data arising from transmission errors in the first RAT exceeds a threshold.

[0056] In an aspect, the method further includes receiving at least one protocol layer status report from the UE over the first communication link utilizing the first RAT, and sending the at least one status report network protocol layer.

[0057] In an aspect, an apparatus for wireless communication includes means for serving data to a UE or receiving data from the UE over a first communication link utilizing a first RAT, means for transmitting a configuration message to the UE indicating that data will be served or received over a second communication link using a second RAT, and means for initiating a configuration procedure to switch service or reception of data from the first communication link using the first RAT to the second link of communication that uses the second RAT.

[0058] In one aspect, the apparatus further includes means for determining data without acknowledgment of receipt of data served using the first RAT.

[0059] In an aspect, the apparatus further includes means for sending the unacknowledged data to be served using the second RAT.

[0060] In an aspect, the configuration message may comprise a data status report and a request for a data status report from the UE.

[0061] In one aspect, the apparatus further includes means for determining to serve the data using the second RAT based on at least one condition.

[0062] In an aspect, the at least one condition comprises receiving a physical layer acknowledgment for the UE configuration message, receiving a radio resource control (RRC) message in response to the UE configuration message, settings.

[0063] In an aspect, the apparatus further includes means for reconfiguring a radio link control (RLC) layer after determining to serve the data using the second RAT.

[0064] In an aspect, the apparatus further includes means for receiving at least one protocol layer status report from the UE, the at least one protocol layer status report identifying data received by the UE via the first RAT, where the unacknowledged data is determined based on at least one protocol layer status report.

[0065] In an aspect, the at least one protocol layer status report is received through the first RAT.

[0066] In an aspect, the at least one protocol layer status report comprises at least one packet data convergence protocol (PDCP) layer status report or a data link control layer status report radio (RLC).

[0067] In an aspect, the apparatus further includes means for receiving an acknowledgment message from the UE for the configuration message via the first communication link using the first RAT, where at least one protocol layer status report is received from the UE simultaneously with the acknowledgment message or within the acknowledgment message.

[0068] In an aspect, the apparatus further includes means for receiving an acknowledgment from the UE for the configuration message, wherein the unacknowledged data is sent to the second RAT in response to the received acknowledgment.

[0069] In an aspect, the apparatus further includes means for detecting a physical layer acknowledgment for the configuration message, where the unacknowledged data is sent in response to the detected physical layer acknowledgment.

[0070] In an aspect, the apparatus further includes means for sending at least one protocol layer status report to the UE.

[0071] In an aspect, the at least one protocol layer status report is sent to the UE concurrently with the configuration message or within the configuration message or other signaling message.

[0072] In one aspect, the apparatus further includes means for sending the at least one protocol layer status report on a data carrier being switched.

[0073] In one aspect, the apparatus further includes means for sending the at least one protocol layer status report on another data carrier that is not being switched and that is served by the first communication link that uses the first RAT or the second communication link that uses the second RAT.

[0074] In an aspect, the at least one protocol layer status report is sent via the first RAT or the second RAT.

[0075] In an aspect, the at least one protocol layer status report is sent to the UE via the first RAT concurrently with the configuration message, upon receipt of a physical layer acknowledgment from the UE for the message configuration message, or upon receipt of an acknowledgment message from the UE for the configuration message.

[0076] In an aspect, the at least one protocol layer status report comprises at least one of a Packet Data Convergence Protocol (PDCDP) layer status report or a data control layer status report radio link (RLC).

[0077] In an aspect, the apparatus further includes means for receiving feedback from the AP, where the feedback information indicates the status for successfully or unsuccessfully transmitted data packets.

[0078] In one aspect, the apparatus further includes means for storing a copy of the data to be served over the second communication link using the second RAT in a store.

[0079] In an aspect, the apparatus further includes means for receiving feedback from an AP or the UE for a successful packet transmission situation, means for determining, based on the feedback information, whether an amount of data sent that is waiting in a storage of the UE or AP exceeds a threshold, and means to stop further sending data to the AP when the amount of data in the AP storage exceeds the threshold.

[0080] In an aspect, the apparatus further includes means for not sending more data to the AP or UE when the number of failed packets arising from transmission errors in the second RAT exceeds a threshold.

[0081] In an aspect, the apparatus further includes means for sending and receiving at least one protocol layer status report to and from the UE via the first communication link using the first RAT or the second communication link using the second RAT.

[0082] In an aspect, the at least one protocol layer status report is received via an AP or UE when the at least one protocol layer status report is received via the second RAT.

[0083] In one aspect, the apparatus further includes means for no longer sending data to the AP or UE when the amount of failed packets arising from transmission errors on the second communication link using the second RAT exceeds a threshold.

[0084] In one aspect, an apparatus for wireless communication includes means for receiving data served from a network or transmitting data to the network via a first communication link using a first RAT, means for receiving a configuration message of the network indicating that the data will be served from the network or transmitted to the network via a second communication link utilizing a second RAT, means for configuring at least one protocol layer based on the received configuration message to receive the served data from the means for receiving the served data from the network or transmitting the data to the network via the second communication link using the second RAT.

[0085] In an aspect, the configuration message comprises at least one of a data status report or a request for a data status report.

[0086] In an aspect, the apparatus further includes means for transmitting at least one of a physical layer acknowledgment for the configuration message or a radio resource control (RRC) message in response to the configuration message.

[0087] In an aspect, the apparatus further includes means for starting a timer after transmission of the physical layer acknowledgment, means for waiting for receipt of at least one protocol layer status report until the timer expires, means to reconfigure one or more protocol layers upon timer expiration.

[0088] In one aspect, the apparatus additionally includes means for releasing a buffer for storing data received over the second communication link using the second RAT after configuring at least one protocol layer.

[0089] In an aspect, the apparatus further includes means for transmitting at least one protocol layer status report to the network, the at least one protocol layer status report identifying data received by the UE via the first or second RAT RAT.

[0090] In one aspect, the apparatus further includes means for sending the at least one protocol layer status report in a configuration acknowledgment message or other signaling message.

[0091] In one aspect, the apparatus further includes means for sending the at least one protocol layer status report on a data carrier being switched.

[0092] In one aspect, the apparatus further includes means for sending the at least one protocol layer status report on another data carrier that is not being switched and that is served by the first communication link that uses the first RAT or the second communication link that uses the second RAT.

[0093] In an aspect, the at least one protocol layer status report is transmitted over the first communication link that uses the first RAT.

[0094] In an aspect, the at least one protocol layer status report comprises at least one of a packet data convergence protocol (PDCP) layer status report or a data control layer status report radio link (RLC).

[0095] In an aspect, the apparatus further includes means for transmitting an acknowledgment message to the network for the received configuration message simultaneously with at least one protocol layer status report over the first communication link using the first RAT, or means for transmitting an acknowledgment message that includes the at least one protocol layer status report to the network for the configuration message received over the first communication link using the first RAT.

[0096] In an aspect, the apparatus further includes means for receiving at least one protocol layer status report.

[0097] In an aspect, the at least one protocol layer status report is received concurrently with the configuration message or within the configuration message.

[0098] In an aspect, the at least one protocol layer status report is received via the first RAT or the second RAT.

[0099] In an aspect, the at least one protocol layer status report is received via the first RAT concurrently with the configuration message, after transmission of a physical layer acknowledgment to the network for the configuration message , or after transmitting an acknowledgment message to the network for the configuration message.

[00100] In one aspect, the at least one protocol layer status report comprises at least one of a packet data convergence protocol (PDCP) layer status report or a data control layer status report radio link (RLC).

[00101] In one aspect, the apparatus additionally includes means for transmitting the return information to the network through an AP using the second communication link, where the return information indicates the status for successfully or unsuccessfully transmitted data packets .

[00102] In an aspect, the apparatus further includes means for transmitting the information back to the network for a successful packet transmission situation.

[00103] In one aspect, the apparatus further includes means for sending and receiving at least one protocol layer status report to and from the network via the first communication link using the first RAT or the second communication link using the second RAT.

[00104] In one aspect, the at least one protocol layer status report is sent to the network via an AP when the at least one protocol layer status report is sent via the second communication link using the second RAT.

[00105] In one aspect, an apparatus for wireless communication includes means for serving data sent over a network to a UE via a first communication link utilizing a first RAT, means for receiving a message from the network indicating that the data will be served to the UE via a second communication link using a second RAT, and means for no longer serving the data to the UE via the first communication link using the first RAT after receipt of the message.

[00106] In one aspect, the apparatus further includes means for deleting the data without acknowledgment of receipt in a store after receipt of the message.

[00107] In an aspect, the apparatus further includes means for no longer serving data sent over the network to the UE when an amount of failed data arising from transmission errors in the first RAT exceeds a threshold.

[00108] In an aspect, the apparatus further includes means for receiving at least one protocol layer status report from the UE over the first communication link using the first RAT, and means for sending the at least one status report protocol layer for the network.

[00109] In one aspect, an apparatus for wireless communication includes a memory and at least one processor coupled to the memory. The at least one processor is configured to serve data to a UE or receive data from the UE over a first communication link utilizing a first RAT, transmits a configuration message to the UE indicating that the data will be served or received over a second communication link using a second RAT, and initiates a configuration procedure to switch service or data reception from the first communication link using the first RAT to the second communication link using the second RAT.

[00110] In one aspect, an apparatus for wireless communication includes a memory and at least one processor coupled to the memory. The at least one processor is configured to receive data served from a network or transmit data to the network over a first communication link utilizing a first RAT, receiving a configuration message from the network indicating that the data will be served from the network or transmitted to the network over a second communication link using a second RAT, configure at least one protocol layer based on the received configuration message to receive served data from the network or transmit data to the network over the second link communication link that uses the second RAT, and receive the served data from the network or transmit data to the network through the second communication link that uses the second RAT.

[00111] In one aspect, an apparatus for wireless communication includes a memory and at least one processor coupled to the memory. The at least one processor is configured to serve data sent over a network to a UE over a first communication link utilizing a first RAT, receiving a message from the network indicating that the data will be served to the UE over a second link communication link that uses a second RAT, and no longer serve the data to the UE over the first communication link that uses the first RAT after receiving the message.

[00112] In one aspect, a computer program product includes a computer-readable medium that includes a code for serving data to a UE or receiving data from the UE over a first communication link that uses a first RAT, transmitting a message configuration procedure for the UE indicating that data will be served or received over a second communication link using a second RAT, and initiating a configuration procedure to switch the service or reception of data from the first communication link using the first RAT for the second communication link that uses the second RAT.

[00113] In one aspect, a computer program product includes a computer-readable medium that includes a code for receiving served data from a network or transmitting data to the network via a first communication link that uses a first RAT , receiving a configuration message from the network indicating that data will be served from the network or transmitted to the network over a second communication link using a second RAT, configuring at least one protocol layer based on the received configuration message for receiving the served data from the network or transmitting data to the network via the second communication link using the second RAT, and receiving the served data from the network or transmitting the data to the network via the second communication link using the second RAT uses the second RAT.

[00114] In one aspect, a computer program product includes a computer-readable medium that includes a code for serving data sent over a network to a UE via a first communication link using a first RAT, receiving a message from the network indicating that the data will be served to the UE via a second communication link using a second RAT, and no longer serve the data to the UE via the first communication link using the first RAT after receiving the message.

[00115] Various aspects and features of the description are described in greater detail below with reference to various examples as illustrated in the accompanying drawings. While the present description is described below with reference to various examples, it should be understood that the present description is not limited thereto. Those skilled in the art having access to the teachings presented herein will recognize further implementations, modifications and examples, as well as other fields of use, which are within the scope of the present description as described herein, and in connection with which the present description can be of significant utility. .

Brief Description of the Drawings

[00116] Figure 1 is a diagram illustrating an example of a network architecture, in accordance with the various aspects of the present description;

[00117] Figure 2 is a diagram illustrating an example of an access network, in accordance with various aspects of the present description;

[00118] Figure 3 is a diagram illustrating an example of a DL frame structure in LTE, in accordance with various aspects of the present description;

[00119] Fig. 4 is a diagram illustrating an example of a UL frame structure in LTE, in accordance with various aspects of the present description;

[00120] Figure 5 is a diagram illustrating an example of a radio protocol architecture for the user and control planes, in accordance with various aspects of the present description;

[00121] Figure 6 is a diagram illustrating an example of an evolved Node B and user equipment in an access network, in accordance with various aspects of the present description.

[00122] Fig. 7A is a block diagram conceptually illustrating an example of data paths between a UE and a PDN in accordance with an aspect of the present description in accordance with various aspects of the present description.

[00123] Fig. 7B is a block diagram conceptually illustrating another example of data paths between a UE and a PDN in accordance with an aspect of the present description in accordance with various aspects of the present description.

[00124] Fig. 8 is a diagram illustrating a message flow between a UE, an eNB, and an access point (AP) in accordance with an aspect of the present description.

[00125] Fig. 9 is a diagram illustrating a message flow between a UE, an eNB and an AP in accordance with an aspect of the present description;

[00126] Figures 10A and 10B illustrate a flowchart of a wireless communication method in accordance with an aspect of the present description;

[00127] Figure 11 is a conceptual data flowchart illustrating the flow of data between different modules/media/components, in accordance with various aspects of the present description;

[00128] Figure 12 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system, in accordance with various aspects of the present description;

[00129] Figures 13A and 13B illustrate a flowchart of a wireless communication method in accordance with an aspect of the present description;

[00130] Figure 14 is a conceptual data flowchart illustrating the flow of data between different modules/media/components, in accordance with various aspects of the present description;

[00131] Figure 15 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system, in accordance with various aspects of the present description;

[00132] Fig. 16 is a flowchart of a wireless communication method according to an aspect of the present description;

[00133] Figure 17 is a conceptual data flowchart illustrating the flow of data between different modules/media/components, in accordance with various aspects of the present description;

[00134] Fig. 18 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system, in accordance with various aspects of the present description.

Detailed Description

[00135] The detailed description presented below with respect to the attached drawings is intended to serve as a description of various settings and is not intended to represent the only settings in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing an in-depth understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are illustrated in block diagram form in order to avoid obscuring such concepts.

[00136] Various aspects of telecommunication systems will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in the following detailed description and illustrated in the attached drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and the design constraints imposed on the system as a whole.

[00137] By way of example, an element, or any part of an element, or any combination of elements may be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate assemblies (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, or other suitable hardware configured to perform the various functionalities described throughout this description. One or more processors in the processing system can run software. Software shall be broadly considered to mean instructions, sets of instructions, applications, software applications, software packages, routines, subroutines, objects, executable elements, execution sequences, procedures, functions, etc. whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise.

[00138] Accordingly, in one or more illustrative embodiments, the functions described may be implemented in hardware, software, firmware or any combination thereof. If implemented in software, functions may be stored in or encoded as one or more instructions or code on a computer-readable medium. Computer readable medium includes computer storage medium. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable medium may comprise random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to port or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Combinations of the above shall also be included within the scope of machine-readable media.

[00139] Figure 1 is a diagram illustrating an LTE 100 network architecture, in accordance with various aspects of the present description. The LTE network architecture 100 may be referred to as an Evolved Packet System (EPS) 100. EPS 100 may include one or more user equipment (UE) 102, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 104 , an Evolved Packet Core (EPC) 110, and Operator Internet Protocol (IP) Services 122. EPS 100 can interconnect with other access networks, but for simplicity these entities/interfaces are not illustrated. As illustrated, EPS provides packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this description can be extended to networks providing circuit-switched services.

[00140] E-UTRAN 104 includes Evolved B Node (eNB) 106 and other eNBs 108, and may include a Multicast Coordination Entity (MCE) 128. The eNB 106 provides user plane protocol terminations and control in the direction of UE 102. The eNB 106 may be connected to other eNBs 108 via a return access channel (e.g., an X2 interface). MCE 128 allocates time and frequency radio resources for the Evolved Multimedia Broadcasting and Multicast Service (MBMS) (eMBMS) and determines the radio configuration (eg, a modulation and coding scheme (MCS)) for eMBMS. The MCE 128 can be a base station, a Node B, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), a extended service (ESS), or some other suitable terminology. The eNB 106 provides an access point to the EPC 110 for a UE 102. Examples of UEs 102 include a cell phone, a smartphone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA ), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (for example, MP3 player), a camera, a game console, a tablet, or any other similar operating device. UE 102 may also be referred to by those skilled in the art as a station (STA), mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, device wireless, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, an apparatus, a user agent, a mobile client, a customer, or some other suitable terminology.

[00141] The eNB 106 is connected to the EPC 110. The EPC 110 may include a Mobility Management Entity (MME) 112, a Home Subscriber Server (HSS) 120, other MMEs 114, an Access Circuit Server 116, a Multimedia Broadcast and Multicast Service Access Circuit (MBMS) 124, a Broadcast and Multicast Service Center (BM-SC) 126, and a Packet Data Network (PDN) Access Circuit 118. The MME 112 it is the control node that processes the signaling between the UE 102 and the EPC 110. Generally, the MME 112 provides support and connection management. All user IP packets are transferred through the Server Access Circuit 116, which itself is connected to the PDN Access Circuit 118. The PDN Access Circuit 118 provides UE IP address allocation in addition to other functions. PDN Access Circuit 118 and BM-SC 126 are connected to IP Services 122. IP Services 122 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Sequencing Service (PSS), and /or other IP services. The BM-SC 126 can provide functions for providing and distributing MBMS user service. BM-SC 126 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS Support Services within a PLMN, and can be used to schedule and distribute MBMS transmissions. The MBMS Access Circuit 124 can be used to distribute MBMS traffic to the eNBs (e.g. 106, 108) belonging to a Single Frequency Broadcast and Multicast Network (MBSFN) area broadcasting a particular service, and can be responsible for session management (start/end) and for collecting eMBMS related to billing information.

[00142] Figure 2 is a diagram illustrating an example of an access network 200 in an LTE network architecture, in accordance with various aspects of the present description. In this example, the access network 200 is divided into a number of cellular regions (cells) 202. One or more lower power class eNBs 208 may have cellular regions 210 that overlap one or more cells 202. 208 lower power cells can be a femto cell (eg home eNB (HeNB)), a pico cell, a micro cell, or a remote radio head (RRH). The macro eNBs 204 are each assigned to a respective cell 202 and are configured to provide an access point to the EPC 110 for all UEs 206 in cells 202. There is no centralized controller in this example of an access network 200, but a centralized controller can be used in alternative configurations. The eNBs 204 are responsible for all radio related functions including radio bearer control, admission control, mobility control, scheduling, security and connectivity to the server access circuit 116. An eNB can support one or several (for example, three) cells (also referred to as sectors). The term "cell" can refer to the smallest coverage area of an eNB and/or an eNB subsystem serving a particular coverage area. Additionally, the terms "eNB", "base station" and "cell" may be used interchangeably herein.

[00143] The modulation and multiple access scheme employed by the access network 200 may vary depending on the particular telecommunication standard being developed. In LTE applications, OFDM is used in DL and SC-FDMA is used in UL to support both frequency division duplexing (FDD) and time division duplexing (TDD). As those skilled in the art will readily appreciate from the detailed description that follows, the various concepts presented here are well suited for LTE applications. However, these concepts can readily be extended to other telecommunication standards employing other modulation and multiple access techniques. By way of example, these concepts can be extended to Evolution Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Partnership Project. Generation 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. These concepts can also be extended to Universal Terrestrial Radio Access (UTRA) employing Broadband CDMA (W-CDMA) and other variations of CDMA such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash OFDM employing OFDMA. UTRA, E-UTRA, UMTS, LTE and GSM are described in 3GPP organization documents. CDMA2000 and UMB are described in 3GPP2 organization documents. The actual wireless communication standard and multiple access technology employed will depend on the specific application and design constraints placed on the overall system.

[00144] The eNBs 204 can have multiple antennas supporting MIMO technology. The use of MIMO technology allows the eNBs 204 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmission diversity. Spatial multiplexing can be used to transmit different data streams simultaneously on the same frequency. Data streams can be transmitted to a single UE 206 to increase the data rate or to multiple UEs 206 to increase the overall system capacity. This is achieved by spatially precoding each data stream (ie, applying scaling to an amplitude and a phase) and then transmitting each spatially precoded stream across multiple DL transmit antennas. The spatially precoded data streams arrive at the UE 206 with different spatial signatures, which allows each UE 206 to retrieve one or more data streams destined for that UE 206. In the UL, each UE 206 transmits a precoded data stream spatially coded, which allows the eNB 204 to identify the source of each spatially precoded data stream.

[00145] Spatial multiplexing is generally used when channel conditions are good. When channel conditions are less favorable, beamforming can be used to focus transmission energy in one or more directions. This can be achieved by spatially precoding data for transmission across multiple antennas. To achieve good coverage at the cell edges, a single sequence beamforming transmission can be used in combination with transmission diversity.

[00146] In the detailed description that follows, various aspects of an access network will be described with reference to a MIMO system supporting OFDM in DL. OFDM is a spread-spectrum technique that modulates data across multiple subcarriers within an OFDM symbol. The subcarriers are spaced at precise frequencies. Spacing provides "orthogonality" that allows a receiver to retrieve data from subcarriers. In the time domain, a guard interval (e.g., cyclic prefix) can be added to each OFDM symbol to combat OFDM intersymbol interference. The UL can utilize SC-FDMA in the form of a DFT spread OFDM signal to compensate for the high peak-to-average power ratio (PAPR).

[00147] Fig. 3 is a diagram 300 illustrating an example of a DL frame structure in LTE, in accordance with various aspects of the present description. A frame (10ms) can be divided into 10 subframes of the same size. Each subframe can include two consecutive time slices. A resource facility can be used to represent two time slices, each time slice including a resource block. The feature installation is divided into multiple feature elements. In LTE, for a normal cyclic prefix, a resource block contains 12 consecutive subcarriers in the frequency domain and 7 consecutive OFDM symbols in the time domain, for a total of 84 resource elements. For an extended cyclic prefix, a feature block contains 12 consecutive subcarriers in the frequency domain and 6 consecutive OFDM symbols in the time domain, for a total of 72 feature elements. Some of the resource elements, indicated as R 302, 304, include DL reference signals (DL-RS). DL-RS includes Cell-Specific RS (CRS) (also sometimes called Common RS) 302 and UE-Specific RS (UE-RS) 304. UE-RS 304 is transmitted only in resource blocks where the shared channel of Corresponding physical DL (PDSCH) is mapped. The number of bits carried by each resource element depends on the modulation scheme. Thus, the more resource blocks a UE receives and the higher the modulation scheme, the higher the data rate for the UE.

[00148] Fig. 4 is a diagram 400 illustrating an example of a UL frame structure in LTE. The resource blocks available for UL can be divided into a data section and a control section. The control section can be formed on two edges of the system bandwidth and can have a configurable size. Resource blocks in the control section can be assigned to UEs for transmission of control information. The UL frame structure results in the data section including contiguous subcarriers, which can allow a single UE to receive all contiguous subcarriers in the data section.

[00149] A UE may receive resource blocks 410a, 410b in the control section to transmit control information to an eNB. The UE may also receive resource blocks 420a, 420b in the data section for transmitting data to the eNB. The UE may transmit control information on a physical UL control channel (PUCCH) in resource blocks designated in the control section. The UE can transmit data only or data and control information on a physical UL shared channel (PUSCH) in the resource blocks designated in the data section. A UL transmission can span both partitions of a subframe and can hop across the frequency.

[00150] A set of resource blocks can be used to perform initial access to the system and achieve UL synchronization on a physical random access channel (PRACH) 430. The PRACH 430 carries a random sequence and cannot carry any UL data /signaling. Each random access preamble occupies a bandwidth corresponding to six consecutive resource blocks. The starting frequency is specified by the network. That is, the transmission of the random access preamble is restricted to certain time and frequency resources. There is no frequency hopping for PRACH. The PRACH attempt is carried over a single subframe (1ms) or a sequence of few contiguous subframes, and a UE can only perform a single PRACH attempt per frame (10ms).

[00151] Figure 5 is a diagram 500 illustrating an example of a radio protocol architecture for the user and control planes in LTE, in accordance with various aspects of the present description. The radio protocol architecture for UE and eNB is illustrated with three layers: Layer 1, Layer 2 and Layer 3. Layer 1 (Layer L1) is the lowest layer and implements various layer signal processing functions. physical. L1 layer will be referred to here as physical layer 506. Layer 2 (L2 layer) 508 is above physical layer 506 and is responsible for the link between UE and eNB through physical layer 506.

[00152] In the user plane, the L2 layer 508 includes a medium access control (MAC) sublayer 510, a radio link control (RLC) sublayer 512, and a packet data convergence protocol sublayer (PDCP) 514, which are terminated in the eNB on the network side. Although not illustrated, the UE may have several upper layers above the L2 layer 508 including a network layer (e.g., IP layer) that is terminated in the PDN access circuit 118 on the network side, and an application layer that is terminated at the other end of the connection (for example, far-end UE, server, etc.).

[00153] The PDCP sublayer 514 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 514 also provides header compression for the upper layer data packets to reduce radio transmission overhead, security by encrypting the data packets, and transfer support for UEs between eNBs. RLC sublayer 512 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception arising from hybrid automatic repeat request (HARQ). MAC sublayer 510 provides multiplexing between the logical and transport channels. MAC sublayer 510 is also responsible for allocating various radio resources (e.g. resource blocks) in a cell among UEs. MAC sublayer 510 is also responsible for HARQ operations.

[00154] In the control plane, the radio protocol architecture for the UE and eNB is substantially the same for the physical layer 506 and the L2 layer 508 with the exception that there is no header compression function for the control plane . The control plane also includes a radio resource control (RRC) sublayer 516 at Layer 3 (Layer L3). The RRC sublayer 516 is responsible for obtaining radio resources (e.g., radio bearers) and for configuring lower layers using RRC signaling between the eNB and the UE.

[00155] Fig. 6 is a block diagram of an eNB 610 in communication with a UE 650 in an access network, in accordance with various aspects of the present description. In DL, the core network upper layer packets are provided to a controller/processor 675. The controller/processor 675 implements the functionality of the L2 layer. In DL, controller/processor 675 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations to UE 650 based on various priority metrics. Controller/processor 675 is also responsible for HARQ operations, retransmission of lost packets, and signaling to UE 650.

[00156] The transmit (TX) processor 616 implements various signal processing functions for the L1 layer (i.e. the physical layer). Signal processing functions include encoding and interleaving to facilitate forward error correction (FEC) in UE 650 and mapping into signal constellations based on various modulation schemes (e.g., binary phase shift keying ( BPSK), quadrature phase shift keying (QPSK), M phase shift keying (M-PSK), M quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols are then divided into parallel sequences. Each sequence is then mapped onto an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a sequence of time-domain OFDMA symbols. The OFDM sequence is spatially precoded to produce multiple spatial sequences. The channel estimates from a channel estimator 674 can be used to determine the coding and modulation scheme, in addition to spatial processing. The channel estimate may be derived from a reference signal feedback and/or channel condition transmitted by UE 650. Each spatial sequence may then be provided to a different antenna 620 via a separate transmitter 618TX. Each 618TX transmitter can modulate an RF carrier with a respective spatial sequence for transmission.

[00157] At UE 650, each receiver 654RX receives a signal through its respective antenna 652. Each receiver 654RX retrieves the modulated information on an RF bearer and provides the information to the receive (RX) processor 656. The RX processor 656 implements various L1 layer signal processing functions. The RX processor 656 may perform spatial processing on the information to retrieve any one of the spatial sequences destined for the UE 650. If multiple spatial sequences are destined for the UE 650, they may be combined by the RX processor 656 into a single sequence of OFDM symbol. The RX processor 656 then converts the OFDM symbol sequence from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol sequence for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the eNB 610. These soft decisions may be based on channel estimates computed by the channel estimator 658. decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the eNB 610 on the physical channel. Data and control signals are then provided to the 659 controller/processor.

[00158] The 659 controller/processor implements the L2 layer. The controller/processor may be associated with a memory 660 which stores program codes and data. Memory 660 may be referred to as a computer-readable medium. In UL, the 659 controller/processor provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing for recovery of upper layer packets from the core network . The upper layer packets are then provided to a data bucket 662, which represents all protocol layers above the L2 layer. Various control signals may also be provided to data warehouse 662 for L3 processing. The 659 controller/processor is also responsible for error detection using an acknowledgment of receipt (ACK) and/or negative acknowledgment (NACK) protocol to support HARQ operations.

[00159] In UL, a data source 667 is used to deliver upper layer packets to the controller/processor 659. Data source 667 represents all protocol layers above the L2 layer. Similar to the functionality described with respect to DL transmission by eNB 610, controller/processor 659 implements the L2 layer for the user plane and control plane by providing header compression, encryption, packet segmentation and reordering, and multiplexing. between logical and transport channels based on radio resource allocations by the eNB 610. The controller/processor 659 is also responsible for HARQ operations, retransmission of lost packets, and signaling for the eNB 610.

[00160] The channel estimates derived by a channel estimator 658 from a reference signal or transmitted back by the eNB 610 can be used by the TX processor 668 to select suitable coding and modulation schemes, and to facilitate spatial processing. The spatial sequences generated by the TX processor 668 can be provided to different antennas 652 via separate transmissions 654TX. Each 654TX transmitter can modulate an RF carrier with a respective spatial sequence for transmission.

[00161] The UL transmission is processed in the eNB 610 similarly to that described with respect to the receiver function in the UE 650. Each receiver 618RX receives a signal through its respective antenna 620. Each receiver 618RX retrieves the modulated information on an RF carrier and provides information for an RX 670 processor. RX 670 processor can implement L1 layer.

[00162] The 675 controller/processor implements the L2 layer. Controller/processor 675 may be associated with a memory 676 that stores program code and data. Memory 676 may be referred to as a computer-readable medium. In UL, controller/processor 675 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer packets from UE 650. higher layer controller/processor 675 can be provided to the core network. Controller/processor 675 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

[00163] Fig. 7A is a diagram of a wireless communication system 700-a illustrating an example of data paths 745 and 750 between a UE 715 and a PDN 740 (e.g., Internet) in accordance with an aspect of the present description. In one aspect, data paths 745 and 750 are configured to allow aggregation of data from radio access technologies (RATs) WWAN (eg, LTE network) and WLAN (eg, WiFiO network). As illustrated in FIG. 7A, the wireless communication system 700-a may include a UE 715 (also referred to as a multi-mode UE 715), an eNB 705-a, a WLAN AP 705-b, an evolved packet core (EPC) 780, a PDN 740, and a peer-to-peer entity 755. EPC 780 may include a mobility management entity (MME) 730, a server access circuit (SGW) 732, and a PDN access circuit (PGW) 734. A Home Subscriber System (HSS) 735 may be communicatively coupled to the MME 730. The UE 715 may include an LTE radio 720 and a WLAN radio 725.

[00164] The eNB 705-a and the WLAN AP 705-b may have the same location or may otherwise be in high-speed communication (for example, via a fiber connection) with each other via connection 756 In the configuration of Fig. 7A, EPS support related data between the UE 715 and the WLAN AP 705-b can be routed to the EPC 780 through the eNB 705-a. In this way, all EPS support related data can be sent along the same path between the eNB 705-a, the EPC 780, the PDN 740 and the peer entity 755.

[00165] As illustrated in Fig. 7A , the eNB 705-a and the WLAN AP 705-b may be able to provide the UE 715 with access to the PDN 740 using the aggregation of one or more LTE component bearers or one or more WLAN component bearers . Using that access to PDN 740, UE 715 can communicate with peer entity 755.

[00166] The MME 730 can be the control node that processes the signaling between the UE 715 and the EPC 780. Generally, the MME 730 can provide support and connection management. The MME 730 may therefore be responsible for idle UE tracking and paging, bearer enabling and disabling, and SGW selection for the UE 715. The MME 730 may communicate with the eNB 705-a via an S1-a interface. MME. MME 730 may further authenticate UE 715 and implement Extract No Access (NAS) signaling with UE 715.

[00167] HSS 735 can, among other functions, store subscriber data, manage roaming restrictions, manage Accessible Access Point Names (APNs) for a subscriber, and associate subscribers with the MME 730. HSS 735 can communicate with the MME 730 through an S6a interface defined by the Evolved Packet System (EPS) architecture standardized by the 3GPP organization.

[00168] As illustrated in figure 7A, SGW 732 can be connected to the MME 730 through an S11 signaling interface and can be connected to the PDN access circuit 734 through an S5 signaling interface. All user IP packets transmitted over LTE can be transferred through eNB 705-a to SGW 732 through MME 730. SGW 732 can reside in the user plane and act as a mobility anchor for inter-eNB transfers and inter-eNB transfers. different access technologies. PDN access circuit 734 can provide UE IP address allocation in addition to other functions.

[00169] The PDN access circuit 734 may provide connectivity to one or more external packet data networks, such as PDN 740, via an SGi signaling interface. PDN 740 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) Sequencing Service (PSS), and/or other types of PDNs.

[00170] In the present example, the user plane data between the UE 715 and the EPC 780 can traverse the same set of one or more EPS bearers, regardless of whether the traffic flows through the LTE link data path 745 or the LTE path. data rate 750 of the WLAN link. Signaling or control plane data relating to the set of one or more EPS bearers may be transmitted between LTE radio 720 of UE 715 and MME 730 of EPC 780, via eNB 705-a.

[00171] As illustrated in Fig. 7A, the UE is simultaneously connected to the eNB 705-a and WLAN AP 705-b, which provide radio access links for carrying user signaling and data traffic. Therefore, in the aspect of Fig. 7A, user data or signaling support can be served over WLAN or LTE radio links.

[00172] Fig. 7B is a diagram of a wireless communication system 700-b illustrating an example of data paths 745 and 752 between UE 715 and PDN 740 in accordance with an aspect of the present description. Data paths 745 and 752 are illustrated in the context of a wireless communication system 700-b for aggregating data from WLAN and WWAN radio access technologies, which is substantially similar to the wireless communication system 700-a of Fig. 7A . As illustrated in the configuration of Fig. 7B, the eNB 705-a and WLAN AP 705-b in Fig. 7B may not be in the same location or may otherwise not be in communication with each other.

[00173] In an aspect, one or more bearers may be established for the UE 715 and a bearer serving data for the UE 715 may be switched between a first communication link that uses a first RAT (e.g., LTE or UMTS) and a second communication link that uses a second RAT (e.g. WiFiO, LTE or UMTS) so that there is minimal disruption to sense data served to UE 715. For example, support can be switched on a time basis at least in part on measurements provided by UE 715 and/or WLAN AP 705-b. Measurements provided by UE 715 and/or WLAN AP 705-b may include received signal quality, store status, channel quality indicator (CQI) and MCS, total radio resource utilization (e.g. frequency components and/or time of a WWAN resource) and per-user radio resource utilization, and/or hardware and return access channel loading for WWAN. When switching support from the first RAT to the second RAT, data packets that were not transmitted using a first RAT (e.g. LTE) can be sent for transmission using a second RAT (e.g. WiFiÔ).

[00174] When the UE 715 is operating in an RLC Acknowledgment (AM) Mode, DL transmissions carried by a bearer may include return messages for UL transmissions carried by the bearer, and UL transmissions carried by the bearer may include return and/or control messages for DL streams ported by support. In one aspect, such feedback and/or control messages may be delivered using the WWAN link 746 without using the WLAN link 751, or using the WLAN link 751 without using the WWAN link 746. feedback and/or control are distributed on WLAN link 751, feedback and/or control messages in support can be sent from WLAN AP 705-b to eNB 705-a when transmitted from UE 715, and from eNB 705- a to WLAN AP 705-b when transmitted from eNB 705-a.

[00175] Fig. 8 is a diagram 800 illustrating a message flow between the UE 715, the eNB 705-a and the WLAN AP 705-b in accordance with an aspect of the present description. As illustrated in Fig. 8, eNB 705-a can receive information from UE 715 (e.g., channel state information) via interwork message 802 and/or information from WLAN AP 705-b (e.g., AP statistics ) via interworking message 804. The eNB 705-a may determine (e.g., bearer switching decision 806) whether to move a bearer serving data to UE 715 of a first communication link that uses a first RAT (e.g. , LTE) to a second communication link that uses a second RAT (e.g. WiFiÔ) based on the received information. For example, the information received may include CQI, Received Signal Strength Indicator (RSSI), Received Reference Signal Power (RSRP), MCS, storage size (e.g., per carrier), storage status report (BSR ), channel load for each UE and/or AP RAT. The received information may also include transmitted and received traffic, failed and/or dropped data packets, retransmission attempts, channel load and/or other information from UE 715 and/or WLAN AP 705-b. In such an aspect, the eNB 705-a may initiate a configuration procedure (e.g., an RRC connection reconfiguration procedure) between the eNB 705-a and the UE 715 by sending a configuration message 808 (e.g., RRCConnectionReconfigurationMessage) to the UE 715. When the successful transmission of data packets carrying the configuration message 808 is confirmed by the MAC layer in eNB 705-a upon receipt of a HARQ ACK, the RLC layer in eNB 705-a for support may be reconfigured and the support can be switched to the second communication link that uses the second RAT (eg WiFiÔ). The UE 715 can reconfigure the RLC layer in the UE 715 when it receives the configuration message 808 and can be configured to accept data packets over the second communication link that uses the second RAT (e.g. WiFi Ô) for that support.

[00176] In one aspect, when a carrier is switched from a first communication link that uses a first RAT (for example, LTE) to a second communication link that uses a second RAT (for example, WiFiÔ), the eNB 705 -a sends all PDCP packets that were not received by UE 715 to WLAN AP 705-b. For example, eNB 705-a may send unacknowledged downlink PDCP packets to WLAN AP 705-b and UE 715 may send unacknowledged uplink PDCP packets to WLAN AP 705-b. In one aspect, the eNB 705-a can send the downlink PDCP packets unacknowledged to the WLAN AP 705-b after the RLC layer is reconfigured in the eNB 705-a and the RLC layer is reconfigured in the UE 715 (e.g., the RLC layer in eNB 705-a and RLC layer in UE 715 can be reconfigured simultaneously). For example, UE 715 can reconfigure the RLC layer after applying the configuration change. In another example, the eNB 704-a may reconfigure the RLC layer after receiving the reconfiguration complete message 824 (e.g., RRCConnectionReconfigurationComplete) from the UE 715 for the configuration change. In other examples, the eNB 705-a can reconfigure the RLC layer after the communication link switching determination.

[00177] In one aspect, for a support using AM RLC, the eNB 705-a can optimize the selection of PDCP packets that must be transmitted. In one aspect, when the eNB 705-a determines to switch a carrier from a first communication link that uses a first RAT (e.g., LTE) to a second communication link that uses a second RAT (e.g., WiFiÔ), the eNB 705-a may send a PDCP status report 810 to UE 715 over the first communication link using the first RAT before switching bearer to the second communication link using the second RAT. For example, the eNB 705-a can initiate the switching of the bearer from the first communication link that uses the first RAT to the second communication link that uses the second RAT by sending an 816 or 826 command to the WLAN AP 705-b . In another aspect, the PDCP status report 810 may be sent before the configuration message 808, in the configuration message 808, after receiving ACK 812 for the configuration message 808, or after receiving the reconfiguration complete message 824 (e.g. example, an RRC Connection Reset Complete message). For example, ACK 812 may be an acknowledgment received at a physical layer (PHY) of eNB 705-a.

[00178] In one aspect, the UE 715 may send a PDCP status report 822 over the first communication link that uses the first RAT (e.g., LTE) after receipt of the 808 configuration message (e.g., an RRCConnectionReconfiguraion message ). In such an aspect, eNB 705-a may wait for PDCP status report 822 before sending a command (e.g., command 826) to WLAN AP 705-b to switch bearer. In another aspect, the UE 715 can send the PDCP status report 822 in the reconfiguration complete message 824. In another aspect, the UE 715 can send a PDCP status report (e.g., the PDCP status report 828) after switching the support of the first communication link that uses the first RAT (for example, LTE) to the second communication link that uses the second RAT (for example, WiFiÔ). In such a case, the eNB 705-a can receive the PDCP report from the UE 715 via the WLAN AP 705b. As illustrated in Fig. 8, UE 715 can send a PDCP report (e.g., PDCP status report 830) to WLAN AP 705-b.

[00179] In one aspect, the eNB 705-a may send an RLC status report 814 to the UE 715 after receiving the ACK 812 for configuration message 808. In another aspect, the eNB 705-a may send the status report RLC status report 814 to UE 715 concurrently with the 808 configuration message. In one aspect, the UE 715 may send an RLC status report 820 at any time after sending the ACK 812 for the 808 configuration message.

[00180] As illustrated in Figure 8, in one aspect, the eNB 705-a can switch a support from a first communication link that uses a first RAT (for example, LTE) to a second communication link that uses a second RAT (eg, WiFiÔ) by sending command 816 after receipt of ACK 812 for configuration message 808. The eNB 705-a may then forward all packets without acknowledgment 818 to the WLAN AP 705-b. In another aspect, the eNB 705-a can switch a support from a first communication link that uses a first RAT (e.g. LTE) to a second communication link that uses a second RAT (e.g. WiFiÔ) by sending the command 826 upon receipt of the reconfiguration complete message 824 (eg, RRCConnectionReconfigurationCompleteMessage) from the UE 715. The eNB 705-a may then forward all packets without acknowledgment 827 to the WLAN AP 705-b. In one aspect, the UE 715 can switch the support of the first communication link that uses the first RAT (e.g., LTE) to the second communication link that uses the second RAT (e.g., WiFiÔ) after receiving the message of 808 configuration or after receipt of an RLC status report (for example, RLC 814 status report) and/or a PDCP status report (for example, PDCP 810 status report). A timer may be started by the UE 715 after sending the ACK 812 such that the UE 715 waits for the RLC status report (e.g., the RLC status report 814) and/or the PDCP status report until the expiration of the timer before RLC and/or PDCP reset.

[00181] Fig. 9 is a diagram 900 illustrating a message flow between the UE 715, the eNB 705-a and the WLAN AP 705-b in accordance with an aspect of the present description. As illustrated in Fig. 9, the eNB 705-a can receive information from the UE 715 (e.g., channel status information) via interwork message 902 and/or information from the WLAN AP 705-b (e.g., AP statistics) via interwork message 904. eNB 705-a may determine (e.g., bearer switching decision 906) whether to move a bearer serving data to UE 715 of a first communication link that uses a first RAT (e.g., WiFiÔ) to a second communication link that uses a second RAT (e.g. LTE) based on the received information. For example, the information received may include CQI, RSSI, RSRP, MCS, store size (e.g., by bearer), store status report (BSR), channel load for each UE 715 RAT and/or WLAN AP 705-b. The received information may also include transmitted and received traffic, failed and/or dropped data packets, retransmission attempts, channel load and/or other information from UE 715 and/or WLAN AP 705-b. In such an aspect, the eNB 705-a may initiate a configuration procedure (e.g., an RRC Connection Reconfiguration procedure) between the eNB 705-a and the UE 715 by sending a configuration message 908 (e.g., RRCConnectionReconfigurationMessage) to the UE 715. When the successful transmission of data packets carrying the configuration message 908 is configured by the MAC layer in eNB 705-a after receipt of a HARQ ACK, the RLC layer in eNB 705-a for support can be reconfigured and support can be switched to the second communication link using the second RAT (eg LTE). The UE 715 can reconfigure the RLC layer in the UE 715 when it receives the configuration message 908 and can be configured to accept the data packets over the second communication link that uses the second RAT (e.g., LTE) for that bearer.

[00182] In one aspect, the UE 715 can reconfigure the RLC layer after applying the configuration change. In another example, eNB 705-a may reconfigure the RLC layer after receiving confirmation (eg RRCConnectionReconfigurationComplete 924) from UE 715 for the configuration change. In other examples, the eNB 705-a can reconfigure the RLC layer after the communication link switching determination.

[00183] In one aspect, for a support using AM RLC, the eNB 705-a can optimize the selection of PDCP packets that must be transmitted. In one aspect, when the eNB 705-a determines to switch a carrier from a first communication link that uses a first RAT (e.g., WiFiÔ) to a second communication link that uses a second RAT (e.g., LTE), the eNB 705-a may send a PDCP status report 910 to UE 715 over the first communication link using the first RAT before switching the support to the second communication link using the second RAT. For example, the eNB 705-a can initiate switching support from the first communication link using the first RAT to the second communication link using the second RAT by sending a command 916 or 926 to the WLAN AP 705-b . The WLAN AP 705-b may stop data transmission upon receipt of command 916 or 926. In another aspect, PDCP status report 910 may be sent before configuration message 908, configuration message 908 after receipt from ACK 912 to setup message 908, or after receipt of reset complete message 924 (for example, an RRC Connection Reset Complete message). For example, ACK 912 may be an acknowledgment received at a physical layer (PHY) of eNB 705-a.

[00184] In one aspect, the UE 715 may send a status report PDCP 922 over the first communication link that uses the first RAT (e.g., WiFiÔ) after receipt of the configuration message 908 (e.g., an RRCConnectionReconfiguration message ). In such an aspect, eNB 705-a may wait for PDCP status report 922 before sending a command (eg command 926) to WLAN AP 705-b for bearer switching. In another aspect, the UE 715 can send the PDCP status report 922 in the complete reconfiguration message 924. In another aspect, the UE 715 can send a PDCP status report after the bearer switch from the first communication link it uses the first RAT (eg WiFiÔ) to the second communication link that uses the second RAT (eg LTE). In such a case, the eNB 705-a can receive the PDCP report from the UE 715 via the WLAN AP 705-b.

[00185] In one aspect, the eNB 750-a may send an RLC status report 914 to the UE 715 after receiving the ACK 912 for the configuration message 908. In another aspect, the eNB 705-a may send the report status report 914 to UE 715 concurrently with the setup message 908. In one aspect, the UE 715 may send an RLC status report 920 at any time after sending the ACK 912 for the setup message 908.

[00186] As illustrated in figure 9, in one aspect, the eNB 705-a can switch a support from a first communication link that uses a first RAT (for example, WiFiÔ) to a second communication link that uses a second RAT (e.g., LTE) by sending command 916 after receipt of ACK 912 for configuration message 908. In one aspect, the eNB 705-a can switch a support of a first communication link that uses a first RAT (e.g., LTE) eg WiFiÔ) to a second communication link utilizing a second RAT (e.g. LTE) by sending command 926 upon receipt of complete reconfiguration message 924 (e.g. RRCConnectionReconfigurationCompleteMessage) from UE 715. In one aspect, the UE 715 may switch support of the first communication link using the first RAT (e.g. WiFiO) to the second communication link using the second RAT (e.g. LTE) after receiving the configuration message 908 or after the receipt of an RLC status report (eg RLC 914 status report) and/or a PDCP status report (eg PDCP 910 status report). A timer can be started by UE 715 after sending ACK 912 such that UE 715 waits for RLC status report (e.g. RLC status report 914) and/or a PDCP status report until timer expires before RLC and/or PDCP reconfiguration.

[00187] In one aspect, when the eNB 705-a determines to switch a support from a first communication link that uses a first RAT (for example, WiFiÔ) to a second communication link that uses a second RAT (for example, LTE ), the eNB 705-a can forward all PDCP packets that were not pushed to the trigger of the first RAT (e.g. WiFiÔ) to the second RAT (e.g. LTE). In another aspect, when the eNB 705-a determines to switch a support from a first communication link that uses a first RAT (for example, WiFiÔ) to a second communication link that uses a second RAT (for example, LTE), the eNB 705-a can store local copies of PDCP packets. In such an aspect, the eNB 705-a can retransmit the PDCP packets that were not successfully transmitted on the first communication link that uses the first RAT (for example, WiFiÔ) on the second communication link that uses the second RAT (for example, LTE) after switching. In such an aspect, a feedback mechanism from the WLAN AP 705-b to the eNB 705-a can be implemented for unacknowledged packets.

[00188] In one aspect, the duplicate PDCP packets can reach the UE 715 if the WLAN AP 705-b continues to transmit the PDCP packets on its stores after the bearer is switched to the second RAT. In such a respect, duplication can be corrected by higher protocol layers (e.g. higher than PDCP layer) or by signaling in an interconnect between LTE and WiFiÔ) within the eNB 705-a/AP WLAN 705-b or an interconnect between LTE and WiFiÔ within UE 715 to cease transmissions to switched bearers.

[00189] In one aspect, the eNB 705-a can determine to switch support from a first communication link that uses a first RAT, such as WiFiÔ, to a second communication link that uses a second RAT, such as LTE. In such an aspect, PDCP status reports can be exchanged between the UE 715 and the eNB 705-a using a WiFi Ô link before the data bearer is switched. In this regard, RLC status reports can be exchanged using either an LTE link or a WiFiÔ link. In one aspect, RRC messages can be exchanged between UE 715 and eNB 705-a using only the LTE link. In another aspect, RRC messages can be exchanged between the UE 715 and the eNB 705-a using the LTE link and/or the WiFiÔ link.

[00190] In the aspects discussed above, bearer switching can be performed by the eNB 705-a above the PDCP layer. In other aspects, bearer switching can be performed by the eNB 705-a in the PDCP layer. The RLC layer for a support can be used on both RAT links or it can be used only on the LTE link.

[00191] Figures 10A and 10B illustrate a flowchart 1000 of a wireless communication method in accordance with an aspect of the present description. The method can be performed by an eNB, such as the eNB 705-a. It should be understood that the steps indicated by dotted lines in Figures 10A and 10B represent optional steps. In step 1002, the eNB serves data (e.g., data packets) to a UE, such as UE 715, or receives data from the UE over a first communication link using a first RAT (e.g., LTE).

[00192] In step 1004, the eNB stores a copy of data to be served through a communication link that uses a second RAT (for example, WiFiÔ) in a storage.

[00193] In step a1005, the eNB stores a sequence number assigned to each data packet to be served through the second communication link that uses the second RAT. For example, the eNB may assign a sequence number to the data packet to be served over a first communication link using the first RAT and a sequence number to the data packet to be served over the second communication link. which uses the second RAT. The eNB can map the sequence number of the data packet to be served over the first communication link using the first RAT to the sequence number of the data packet to be served over the second communication link using the second RAT.

[00194] In step 1006, the eNB transmits a configuration message to the UE indicating that the data will be served or received through the second communication link that uses the second RAT. In one aspect, the configuration message includes a request for a status report (e.g., an RLC layer status report and/or a PDCP layer status report) from the UE.

[00195] In step 1008, the eNB sends at least one protocol layer status report to the UE. In one aspect, the eNB sends at least one protocol layer status report to the UE over the first communication link using the first RAT or the second communication link using the second RAT. For example, the at least one protocol layer status report may be a PDCP layer status report or an RLC layer status report. In one aspect, the at least one protocol layer status report is sent to the UE concurrently with the configuration message or within the configuration message.

[00196] In step 1010, the eNB receives an acknowledgment message from the UE for the configuration message over the first communication link that uses the first RAT. In one aspect, the UE acknowledgment message may indicate that a reconfiguration of an RRC layer of the UE has been completed and that the UE has been configured to receive data via the second RAT. In one aspect, the eNB may perform step 1008 after step 1010. For example, the eNB may send at least one protocol layer status report to the UE after receiving an acknowledgment message from the UE for the message configuration.

[00197] In step 1012, the eNB detects a physical layer acknowledgment for the configuration message. In one aspect, the eNB may perform step 1008 after step 1012. For example, the eNB may send at least one protocol layer status report to the UE after detecting a physical layer acknowledgment from the UE to the configuration message.

[00198] In step 1014, the eNB sends and receives at least one status report from the UE protocol layer over the first communication link that uses the first RAT or the second communication link that uses the second RAT. In one aspect, the at least one protocol layer status report is received via an AP when the at least one protocol layer status report is received via the second RAT.

[00199] In step 1016, the eNB determines to serve the data to the UE using the second communication link that uses the second RAT (eg WiFiÔ) based on at least one condition. In one aspect, the at least one condition may be receipt of a physical layer acknowledgment, receipt of an RRC message in response to the configuration message, or expiration of a timer that is started after transmission of the configuration message.

[00200] In step 1018, the eNB reconfigures an RLC layer after determining to serve the data to the UE using the second RAT.

[00201] In step 1020, the eNB determines the unacknowledged data (for example, unacknowledged data packets) from the served data using the first RAT. In one aspect, the at least one protocol layer status report received from the UE in step 1014 identifies the data received by the UE through the first RAT, where the unacknowledged data is determined based on the at least one status report protocol layer.

[00202] In step 1022, the eNB starts a configuration procedure to switch the service or data reception from the first communication link that uses the first RAT to the second communication link that uses the second RAT.

[00203] In step 1024, the eNB sends the data without acknowledgment of receipt to be served through the second communication link that uses the second RAT. In one aspect, the unacknowledged data is sent in response to the acknowledgment message received in step 1010. In another aspect, the unacknowledged data is sent in response to the physical layer acknowledgment detected in step 1012 .

[00204] In step 1026, the eNB receives feedback from the AP or the UE. In one aspect, the feedback information indicates a number of successfully and failed data packets transmitted. In one aspect, the return from the WLAN AP 705-b can include one or more sequence numbers of packets that were successfully transmitted. In such an aspect, the eNB can use the feedback to identify packets that were not successfully transmitted by the AP.

[00205] In step 1028, the eNB determines, based on the feedback information, whether an amount of sent data that is waiting in a UE or AP store exceeds a threshold.

[00206] In step 1030, the eNB does not send more data to the AP when the amount of data in the UE or AP store exceeds the limit.

[00207] Finally, in step 1032, the eNB does not send more data to the AP or the UE when the number of failed packets due to transmission errors on the second communication link using the second RAT exceeds a threshold.

[00208] Figure 11 is a conceptual data flowchart 1100 illustrating data flow between different modules/media/components in an illustrative apparatus 1102 in accordance with various aspects of the present description. The apparatus may be an eNB. The apparatus includes a receiver module 1104 that receives an acknowledgment message from the UE for the configuration message over the first communication link using the first RAT, receives at least one status report from the UE protocol layer (e.g. , UE 1150) over the first communication link using the first RAT or the second communication link using the second RAT, and receives feedback information (e.g. return 1122) from the AP (e.g. AP 1152) or the UE, a module 1106 that determines the data service for the UE over a second communication link using a second RAT (e.g. WiFiÔ) based on at least one condition, determines the data without acknowledgment of receipt (e.g. data packets with no acknowledgment of receipt) of the data served over the first communication link using the first RAT, determines, based on the return information (e.g. return 1122) whether an amount of data sent (e.g. sent data 1124) that is waiting in the UE or AP store exceeds a threshold, and detects a physical layer acknowledgment for the configuration message, a module 1107 transmits a configuration message to the UE indicating that the data will be served over a second configuration link to the UE indicating that the data will be served over a second communication link using a second RAT, a module 1108 that initiates a configuration procedure to switch the data service of the first communication link that uses the first RAT for the second communication link that uses the second RAT, a module 1110 that serves the data (e.g. data packets) to the UE via a first communication link that uses a first RAT (e.g. , LTE), a module 1112 that reconfigures an RLC layer after determining to serve the data to the UE using the second RAT, a module 1114 that stores a copy of the data to be served over the second communication link using the second RAT in a buffer, a module 1116 that no longer sends data to the AP when the amount of data in the AP buffer exceeds the threshold and no longer sends data to the AP or UE when the amount of failed packets due to transmission errors on the second communication link using the second RAT exceeds a limit, a module 1118 sending the acknowledgment data (e.g. sent data 1124) to be served using the second RAT, and a transmission module 1120 which sends at least one protocol layer status report to the UE using either the first RAT or the second RAT.

[00209] The apparatus may include additional modules that perform each of the steps of the algorithm in the flowchart mentioned above in figures 10A and 10B. As such, each step in the aforementioned flowcharts of Figures 10A and 10b can be performed by a module and the apparatus can include one or more such modules. Modules may be one or more hardware components specifically configured to perform the foregoing processes/algorithms, implemented by a processor configured to perform the foregoing processes/algorithms, stored within a computer-readable medium for implementation by a processor, or some combination of the same.

[00210] Fig. 12 is a diagram 1200 illustrating an example of a hardware implementation for an apparatus 1102' employing a processing system 1214 in accordance with various aspects of the present disclosure. Processing system 1214 may be implemented with a bus architecture, represented generally by bus 1224. Bus 1224 may include any number of buses and interconnecting bridges depending on the specific application of the processing system 1214 and design constraints as a whole. . Bus 1224 connects various circuits including one or more processors and/or hardware modules, represented by processor 1204, modules 1104, 1106, 1107, 1108, 1112, 1114, 1116, 1118, and 1120, and computer-readable medium/ memory 1206. Bus 1224 may also connect various other circuits such as timing supplies, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described further here.

[00211] The processing systems 1214 can be coupled to a transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other appliances via a transmission medium. Transceiver 1210 receives a signal from one or more antennas 1220, extracts information from the received signal, and provides extracted information to processing system 1214, specifically receiving module 1104. Additionally, transceiver 1210 receives information from processing system 1214, specifically the transmitting module 1120, and based on the information received, generates a signal to be applied to one or more antennas 1220. The processing system 1214 includes a processor 1204 coupled to a computer readable medium/memory 1206. The processor 1205 is responsible for general processing, including execution of software stored on computer-readable medium/memory 1206. The software, when executed by processor 1204, causes processing system 1214 to perform the various functions described above for any particular apparatus. Computer-readable medium/memory 1206 may also be used to store data that is manipulated by processor 1204 when executing the software. The processing system further includes at least one of modules 1104, 1106, 1107, 1108, 1110, 1112, 1114, 1116, 1118, and 1120. The modules can be software modules running on processor 1204, resident/stored on computer-readable/memory medium 1206, one or more hardware modules coupled to processor 1204, or some combination thereof. Processing system 1214 may be a component of eNB 610 and may include memory 676 and/or at least one of TX processor 616, RX processor 670, and controller/processor 675.

[00212] In one configuration, the apparatus 1102/1120' for wireless communication includes means for serving data to a UE through a first communication link that uses a first RAT, means for transmitting a configuration message to the UE indicating that data will be served over a second communication link using a second RAT, means for initiating a configuration procedure to switch data service from the first communication link using the first RAT to the second communication link using the second RAT, means for determining the unacknowledged data serviced data using the first RAT, means for sending the unacknowledged data to be served using the second RAT, means for determining the data service using the second RAT based on the in at least one condition, means for reconfiguring a radio link control (RLC) layer after determining to serve the data using the second RAT, means for receiving at least one protocol layer status report from the UE, means for receiving a UE acknowledgment message for the configuration message, means for detecting a physical layer acknowledgment for the configuration message, means for sending at least one protocol layer status report to the UE, means for receiving return information from the AP, where the return information indicates the status for successfully or unsuccessfully transmitted data packets, means for storing a copy of the data to be served over the second communication link using the second RAT in a store, means for receiving feedback from an AP or the UE for a successful packet transmission situation, means for determining, based on the feedback information, whether an amount of sent data is waiting in a buffer of the UE or AP exceeds a limit, means for not sending more data to the AP when the amount of data in the AP store exceeds the limit, means for sending and receiving at least one status report from the protocol layer and from the UE over the first communication link that uses the first RAT or the second communication link that uses the second RAT, means to no longer send data to the AP or UE when the number of failed packets due to transmission errors on the second communication link that uses the second RAT exceeds a threshold. The above-mentioned means may be one or more of the above-mentioned modules of the apparatus 1102 and/or the processing system 1214 of the apparatus 1002' configured to perform the functions mentioned by the above-mentioned means. As described above, processing system 1214 may include TX processor 616, RX processor 670, and controller/processor 675. As such, in one configuration, the aforementioned means may be TX processor 616, RX processor 670 and controller/processor 675 configured to perform the aforementioned functions by the aforementioned means.

[00213] Figures 13A and 13B are a flowchart 1300 of a wireless communication method in accordance with an aspect of the present description. It should be understood that the steps indicated by dotted lines in Figures 13A and 13B represent optional steps. The method may be performed by a UE (e.g. UE 715, apparatus 1402/1402'). In step 1302, the UE receives served data from a network (e.g. eNB 705-a) or transmits data to the network (e.g. eNB 705-a) via a first communication link that uses a first RAT (e.g. example, LTE).

[00214] In step 1304, the UE receives at least one protocol layer status report. For example, with reference to Fig. 8 the UE 715 may receive PDCP status report 810. In one aspect, the at least one protocol layer status report is received via the first communication link utilizing a first RAT or a second communication link that uses a second RAT (for example, WiFiÔ). For example, the at least one protocol layer status report may include the PDCP layer status report and/or an RLC layer status report (e.g., RLC status report 814 in Fig. 8 ).

[00215] In step 1306, the UE receives a network configuration message indicating that data will be served from the network or transmitted to the network via a second communication link that uses a second RAT. For example, referring to Fig. 8, UE 715 receives configuration message 808 (eg RRC Connection Reset message). In one aspect, the configuration message includes a data status report and/or a request for a data status report. In one aspect, the at least one protocol layer status report is received concurrently with the configuration message or within the configuration message. In one aspect, the at least one protocol layer status report is received via the first RAT simultaneously with the configuration message, after transmission of a physical layer acknowledgment to the network for the configuration message, or after transmitting an acknowledgment message to the network for the configuration message.

[00216] In step 1308, the UE transmits a physical layer acknowledgment for the configuration message and/or an RRC message in response to the configuration message. For example, referring to Fig. 8 , UE transmits ACK 812 to eNB 705a.

[00217] In step 1310, the UE starts the timer after transmitting the physical layer acknowledgment for the configuration message.

[00218] In step 1312, the UE waits to receive at least one protocol layer status report until the timer expires.

[00219] In step 1314, the UE reconfigures one or more protocol layers after the timer expires.

[00220] In step 1316, the UE transmits an acknowledgment message to the network for the received configuration message simultaneously with at least one protocol layer status report over the first communication link using the first RAT.

[00221] In step 1318, the UE transmits an acknowledgment message that includes the at least one protocol layer status report to the network for the received configuration message over the first communication link that uses the first RAT.

[00222] In step 1320, the UE configures at least one protocol layer based on the received configuration message to receive the served data from the network and transmit data to the network via the second communication link using the second RAT.

[00223] In step 1322, the UE can release a buffer to store the data to be sent over the second communication link that uses the second RAT after configuring at least one protocol layer after which it is switched to the first RAT .

[00224] In step 1324, the UE transmits at least one protocol layer status report to the network. For example, referring to Fig. 8, UE 715 transmits PDCP status report 822. In one aspect, the at least one protocol layer status report identifies data received by the UE via the first RAT. In one aspect, the at least one protocol layer status report is transmitted over the first communication link using the first RAT. In one aspect, the at least one protocol layer status report includes a PDCP layer status report and/or an RLC layer status report. In one aspect, the at least one protocol layer status report is sent to the network via an AP when the at least one protocol layer status report is sent via the second communication link utilizing the second RAT.

[00225] In step 1326, the UE sends and receives at least one protocol layer status report to and from the network via the first communication link using the first RAT or the second communication link using the second RAT.

[00226] In step 1328, the UE transmits the information back to the network via a WLAN AP (eg, WLAN AP 705-b) using the second communication link. In one aspect, feedback information indicates the status of successfully or unsuccessfully transmitted data packets.

[00227] In step 1330, the UE transmits feedback to the network for a successful packet transmission situation.

[00228] Finally, in step 1332, the UE receives the served data from the network or transmits data to the network via the second communication link using the second RAT.

[00229] Fig. 14 is a conceptual data flowchart 1400 illustrating data flow between different modules/media/components in an illustrative apparatus 1402. The apparatus may be a UE. The apparatus includes a module 1404 that receives data served from a network, receives a configuration message from the network indicating that the data will be served from the network or transmitted to the network over a second communication link utilizing a second RAT, receives the data served from the network through the second communication link using the second RAT, receives at least one protocol layer status report.

[00230] The apparatus additionally includes a module 1414 that configures at least one protocol layer based on the configuration message received to receive the served data from the network or transmit data to the network through the second communication link that uses the second RAT.

[00231] The apparatus additionally includes a transmission module 1418 that transmits data to the network through a first communication link that uses a first RAT, transmits at least one of a physical layer acknowledgment for the configuration message or a RRC message in response to the configuration message, transmits at least one protocol layer status report to the network, the at least one protocol layer status report identifying data received by the UE via the first RAT or second RAT, transmits information return to the network through an AP using the second communication link, where the return information indicates the status for data packets successfully transmitted or not, transmits return information to the network for successful transmission status of packets, and sends and receives at least one protocol layer status report to and from the network over the first communication link using the first RAT or the second communication link using the second RAT.

[00232] The apparatus additionally includes a module 1408 that starts a timer after transmission of the physical layer acknowledgment.

[00233] The apparatus additionally includes a module 1410 that waits for the receipt of at least one status report from the protocol layer until the expiration of the timer.

[00234] The apparatus additionally includes a module 1412 that reconfigures one or more protocol layers upon expiration of the timer.

[00235] The apparatus additionally includes a module 1416 that releases a storage to store the data received through the second communication link that uses the second RAT after the configuration of at least one protocol layer.

[00236] The apparatus additionally includes a module 1418 that transmits data to the network through the second communication link that uses the second RAT.

[00237] The apparatus may include additional modules that perform each of the algorithm blocks in the flowchart mentioned above in figures 13A and 13B. As such, each block in the aforementioned flowcharts of Figures 13A and 13B can be realized by a module and the apparatus can include one or more such modules. Modules may be one or more hardware components specifically configured to perform the foregoing processes/algorithms, implemented by a processor configured to perform the foregoing processes/algorithms, stored within a computer-readable medium for implementation by a processor, or some combination of the same.

[00238] Figure 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1402' employing a processing system 1514. The processing system 1514 can be implemented with a bus architecture, generally represented by bus 1524. Bus 1524 may include any number of buses and interconnecting bridges depending on the specific application of processing system 1514 and design constraints as a whole. Bus 1524 connects various circuitry including one or more processors and/or hardware modules, represented by processor 1504, modules 1404, 1406, 1408, 1410, 1412, 1414, 1416, and 1418, and computer/memory readable medium 1506 Bus 1524 can also connect various other circuits such as timing supplies, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described further.

[00239] The processing system 1514 may be coupled to a transceiver 1510. The transceiver 1510 is coupled to one or more antennas 1520. The transceiver 1510 provides means for communicating with various other appliances via a transmission medium. Transceiver 1510 receives a signal from one or more antennas 1520, extracts information from the received signal, and provides the extracted information to processing system 1514, specifically receiver module 1401. Additionally, transceiver 1510 receives information from processing system 1514 , specifically the transmitting module 1418, and based on the received information, generates a signal to be applied to one or more antennas 1520. The processing system 1514 includes a processor 1504 coupled to a computer readable medium/memory 1506. The software , when executed by processor 1504, causes processing system 1514 to perform the various functions described above for any particular apparatus. Computer-readable medium/memory 1506 may also be used to store data that is manipulated by processor 1504 when executing software. The processing system further includes at least one of modules 1404, 1406, 1408, 1410, 1412, 1414, 1416 and 1418. The modules may be software modules running on processor 1504 resident/stored on the computer readable medium/memory 1506, one or more hardware modules coupled to processor 1504, or some combination thereof. Processing system 1514 may be a component of UE 650 and may include memory 660 and/or at least one of TX processor 668, RX processor 656, and controller/processor 659.

[00240] In one configuration, the apparatus 1402/1402' for wireless communication includes means for receiving data served from a network or transmitting data to the network through a first communication link that uses a first RAT, means for receiving a configuration message from the network indicating that data will be served from the network or transmitted to the network via a second communication link utilizing a second RAT, means for configuring at least one protocol layer based in the received configuration message for receiving the served data from the network or transmitting data to the network via the second communication link using the second RAT, means for receiving the served data from the network or transmitting the data to the network via of the second communication link using the second RAT, means for transmitting at least one of a physical layer acknowledgment for the configuration message or an RRC message in response to the configuration message, means for starting a timer after transmission of the configuration message physical layer acknowledgment, means for waiting for receipt of at least one protocol layer status report after timer expiration, means for resetting one or more protocol layers after timer expiration, means for releasing a store for storage of data received over the second communication link using the second RAT after configuring the at least one protocol layer, means for transmitting at least one protocol layer status report to the network, the at least one status report protocol layer identifying data received by the UE via the first RAT or second RAT, means for sending at least one protocol layer status report in a configuration acknowledgment message or other signaling message, means for sending the at least one means for sending the at least one protocol layer status report on a data carrier which is being switched, means for sending the at least one protocol layer status report on another data carrier which is not being switched and which is served by the first link communication link using the first RAT or the second communication link using the second RAT, means for transmitting an acknowledgment message to the network for the received configuration message simultaneously with at least one protocol layer status report via of the first communication link that uses the first RAT, or means for transmitting an acknowledgment message that includes the at least one protocol layer status report to the network for the configuration message received over the first communication link that uses the first RAT, means for receiving at least one protocol layer status report, means for transmitting feedback information to the network through an AP using the second communication link, where the feedback information indicates status for packets of data transmitted successfully or not, means for transmitting the information back to the network for a status of successful transmission of packets, means for sending and receiving at least one protocol layer status report to and from the network via the first communication link using the first RAT or second communication link using the second RAT. The above-mentioned means may be one or more above-mentioned modules of apparatus 1402 and/or processing system 1514 of apparatus 1402' configured to perform the functions mentioned by the above-mentioned means. As described above, processing system 1514 may include TX processor 668, RX processor 656, and controller/processor 659. As such, in one configuration, the aforementioned means may be TX processor 668, RX processor 656 , and the controller/processor 659 configured to perform the aforementioned functions by the aforementioned means.

[00241] Fig. 16 is a flowchart 1600 of a wireless communication method according to an aspect of the present description. The method can be performed by an AP eg WLAN AP 705-b, appliance 1702/1702'). It should be understood that the steps indicated by dotted lines in Figure 16 represent optional steps. In step 1602, the AP serves data sent over a network to a UE over a first communication link using a first RAT (e.g., WiFiÔ).

[00242] In step 1604, the AP receives at least one protocol layer status report from the UE over the first communication link that uses the first RAT.

[00243] In step 1606, the AP sends the at least one UE protocol layer status report over the first communication link that uses the first RAT.

[00244] In step 1608, the AP receives a message from the network indicating that the data will be served to the UE over a second communication link that uses a second RAT (eg, LTE).

[00245] In step 1610, the AP deletes the unacknowledged data stored in a buffer upon receipt of the message.

[00246] In step 1612, the AP no longer serves the data sent over the network to the UE when an amount of failed data due to transmission errors in the first RAT exceeds a threshold.

[00247] Finally, in step 1614, the AP no longer serves the data to the UE over the first communication link that uses the first RAT after receiving the message.

[00248] Fig. 17 is a conceptual data flowchart 1700 illustrating data flow between different modules/media/components in an illustrative apparatus 1702. The apparatus may be an AP. The apparatus includes a receiver module 1704 which receives a message (e.g. message 1716) from the network (e.g. eNB 1752) indicating that data will be served to UE 1750 over a second communication link utilizing a second RAT , and receives at least one protocol layer status report from the UE over the first communication link that uses the first RAT. The apparatus further includes a module 1706 which deletes unacknowledged data stored in a buffer upon receipt of the message. The apparatus further includes a module 1708 that serves data (e.g., data 1718) sent over a network to the UE 1750 via a first communication link that uses a first RAT, no longer serves the data to the UE 1750 via the first communication link that uses the first RAT after receiving the message, and no longer serves the data sent over the network to the UE when an amount of failed data due to transmission errors in the first RAT exceeds a threshold. The apparatus further includes a transmission module 1712 that sends the at least one protocol layer status report (e.g., protocol layer status report 1714) to the network.

[00249] The apparatus may include additional modules that perform each of the blocks of the algorithm in the flowchart mentioned above in Figure 6. As such, each block in the flowchart mentioned above in Figure 16 can be performed by a module and the apparatus may include one or more of these modules. Modules may be one or more hardware components specifically configured to perform the foregoing processes/algorithms, implemented by a processor configured to perform the foregoing processes/algorithms, stored within a computer-readable medium for implementation by a processor, or some combination of the same.

[00250] Figure 18 is a diagram 1800 illustrating an example of a hardware implementation for an apparatus 1702' employing a processing system 1814. The processing system 1814 can be implemented with a bus architecture, generally represented by bus 1824. Bus 1824 may include any number of buses and interconnecting bridges depending on the specific application of processing system 1814 and design constraints as a whole. Bus 1824 connects various circuits including one or more processors and/or hardware modules, represented by processor 1804, modules 1704, 1706, 1708 1710 and 1712, and computer readable medium/memory 1806. Bus 1824 can also connect various other circuits such as timing supplies, peripherals, voltage regulators, and power management circuits, which are all well known in the art, and therefore will not be described further.

[00251] The processing system 1814 may be coupled to a transceiver 1810. The transceiver 1810 is coupled to one or more antennas 1820. The transceiver 1810 provides means of communicating with various other apparatuses via a transmission medium. Transceiver 1810 receives a signal from one or more antennas 1820, extracts information from the received signal, and provides the extracted information to processing system 1814, specifically receiver module 1704. Additionally, transceiver 1810 receives information from processing system 1814 , specifically the transmitting module 1712, and based on the information received, generates a signal to be applied to one or more antennas 1820. The processing system 1814 includes a processor 1804 coupled to a computer readable medium/memory 1806. The processor 1804 is responsible for general processing, including execution of software stored on computer-readable medium//memory 1806. The software, when executed by processor 1804, causes processing system 1814 to perform the various functions described above for any apparatus in particular. Computer-readable medium/memory 1806 may also be used to store data that is manipulated by processor 1804 when executing the software. The processing system further includes at least one of modules 1704, 1706, 1708, 1710 and 1712. The modules may be software modules running on processor 1804, resident/stored on computer readable/memory medium 1806, one or more hardware attached to the 1804 processor, or some combination thereof. Processing system 1814 may be a component of eNB 610 and may include memory 676 and/or at least one of TX processor 616, TX processor 670, and controller/processor 675.

[00252] In one configuration, apparatus 1702/1702' for wireless communication includes means for serving data sent over a network to a UE via a first communication link using a first RAT, means for receiving a message from the network indicating that the data will be served to the UE via a second communication link using a second RAT, means for no longer serving the data to the UE via the first communication link using the first RAT after receiving the message, means for deleting unacknowledged data stored in a buffer after receiving the message, means for no longer serving data sent over the network to the UE when an amount of failed data due to transmission errors in the first RAT exceeds a threshold, means for receiving at least one protocol layer status report from the UE over the first communication link using the first RAT, means for sending the at least one protocol layer status report to the network. The above-mentioned means may be one or more of the above-mentioned modules of apparatus 1702 and/or processing system 1814 of apparatus 1702' configured to perform the functions mentioned by the above-mentioned means. As described above, processing system 1814 may include TX processor 616, RX processor 670, and controller/processor 675. As such, in one configuration, the aforementioned means may be TX processor 616, RX processor 670 , and the controller/processor 675 configured to perform the aforementioned functions by the aforementioned means.

[00253] It should be understood that the specific order or hierarchy of steps in the described processes/flowcharts is an illustration of the illustrative approaches. Based on design preferences, it should be understood that the specific order or hierarchy of steps in processes/flowcharts may be rearranged. Additionally, some steps can be combined or omitted. The appended method claims present elements of the various steps in a sampling order, and are not to be limited to the particular order or hierarchy presented.

[00254] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications of these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Accordingly, the claims must not be limited to the aspects illustrated here, but the full scope consistent with the language claims must be agreed, where reference to an element in the singular must not mean "one and only one" unless specifically mentioned, but rather "one or more." The term "illustrative" is used here to mean "serving as an example, case or illustration". Any aspect described herein as "illustrative" should not necessarily be considered preferred or advantageous over other aspects." Unless specifically noted to the contrary, the term "some" refers to one or more. Combinations such as "at least one of A, B or C", "at least one of A, B and C", and "A, B, C or any combination thereof" include any combination of A, B and/or C, and may include multiples of A , multiples of B or multiples of C. Specifically, combinations such as "at least one of A, B or C", "at least one of A, B and C", and "A, B, C or any combination thereof " can be just A, just B, just C, A and B, A and C, B and C, or A and B and C, where any of these combinations can contain one or more elements of A, B, or C. All Structural and functional equivalences of elements of various aspects described throughout this disclosure that are known today or will become known in the future to those skilled in the art are expressly incorporated herein by reference and are to be encompassed by the claims. Furthermore, nothing described here should be dedicated to the public unless such description is explicitly mentioned in the claims. No claim element shall be considered a means plus function unless the element is expressly mentioned using the phrase "means to".

Claims (15)

1. Method (1000) of wireless communication of a base station, characterized in that it comprises: serving (1002) data to a user equipment, UE, through a first communication link that uses a first access technology of radio, RAT; transmitting (1006) a configuration message to the UE indicating what data will be served or received over a second communication link using a second RAT, wherein the configuration message comprises a protocol layer status report and a request for a protocol layer status report from the UE; determining (1020) unacknowledged data among the data served to the UE using the first RAT based on at least one protocol layer status report received (1014) from the UE that indicates data received by the UE via the first RAT; initiating (1022) a configuration procedure to switch service or data reception from the first communication link using the first RAT to the second communication link using the second RAT; and forwarding (1024) the unconfirmed data to be served using the second RAT. 2. Method according to claim 1, characterized in that it additionally comprises determining (1016) to serve the data using the second RAT based on at least one condition. 3. Method according to claim 2, characterized in that the at least one condition comprises receiving a physical layer acknowledgment for the configuration message from the UE, or receiving a resource control message radio link, RRC, in response to the configuration message, or which further comprises resetting (1018) a radio link control layer, RLC, upon determining to serve the data using the second RAT. 4. Method according to claim 1, characterized in that the at least one protocol layer status report comprises at least one of a packet data convergence protocol layer status report, PDCP, or a Radio Link Control Layer, RLC, status report. 5. Method according to claim 1, characterized in that it further comprises receiving (1010) a confirmation message from the UE for the configuration message via the first communication link using the first RAT, where at least at least one protocol layer status report is received from the UE simultaneously with the acknowledgment message or within the acknowledgment message, or which further comprises receiving an acknowledgment from the UE for the configuration message, wherein data is not acknowledgments are forwarded to the second RAT in response to the received acknowledgment, or further comprising detecting a physical layer acknowledgment for the configuration message, wherein the unacknowledged data is forwarded in response to the detected physical layer acknowledgment, or further comprising not forward more data to an access point, AP, or UE when the number of packets failing due to transmission errors on the second communication link using the second RAT exceeds a threshold. 6. Method according to claim 1, characterized in that the at least one protocol layer status report is a first protocol layer status report, wherein the method further comprises sending a second status report protocol layer to the UE. 7. Method according to claim 6, characterized in that the second protocol layer status report is sent to the UE simultaneously with the configuration message or within the configuration message or another signaling message. 8. Method according to claim 6, further comprising sending the second protocol layer status report on a data bearer being switched, or further comprising sending the second layer status report protocol on another data bearer that is not being switched and that is served by the first communication link using the first RAT or the second communication link using the second RAT. 9. Method according to claim 7, characterized in that the second protocol layer status report is sent via the first RAT or the second RAT. 10. Method according to claim 9, characterized in that the second protocol layer situation report is sent to the UE through the first RAT simultaneously with the configuration message, upon receipt of a physical layer acknowledgment from the UE for the configuration message, or upon receipt of an acknowledgment message from the UE for the configuration message. 11. Method according to claim 7, characterized in that the second protocol layer status report comprises at least one of a packet data convergence protocol layer status report, PDCP, or a report radio link control layer, RLC. 12. Method according to claim 1, characterized in that it further comprises receiving feedback information from an access point, AP, wherein the feedback information indicates a situation for successfully transmitted data packets and faults, or further comprising storing a copy of the data to be served over the second communication link using the second RAT in temporary storage, or further comprising: receiving feedback information from an access point, AP, or from the UE to a packet transmission success situation; determining, based on the feedback information, whether an amount of forwarded data waiting in a temporary storage of the UE or the AP exceeds a threshold; and not forwarding more data to the AP when an amount of the data in an access point, AP, temporary storage exceeds the threshold, or further comprising not forwarding more data to an access point, AP, or UE when an amount of Failed packets due to transmission errors in the second RAT exceeds a threshold. 13. Method according to claim 1, characterized in that the at least one protocol layer status report is a first protocol layer status report, the method further comprising sending a second layer status report protocol layer and receive the first protocol layer status report to and from the UE over the first communication link using the first RAT or the second communication link using the second RAT. 14. Method according to claim 13, characterized in that the at least one protocol layer status report is received via an access point, AP, or UE when the at least one status report protocol layer is received through the second RAT. 15. Base station for wireless communication, characterized in that it comprises means arranged to carry out the steps of the method as defined in any one of claims 1 to 14.