Method and device for managing radio link failure recovery

Method and device for managing radio link failure recovery

[0001] This application is an application with an application date of July 31, 2014, an application number of 201480044786.5 (international application number PCT/US2014/049128), and an application titled "Methods and devices for managing radio link failure recovery" Divisional application.

[0002] Priority Claim

[0003] This patent application requires a "Techniques for Managing Radio Link Failure Recovery for a User Equipment Connected to a WWAN and a WLAN" filed on July 30, 2014. Link Failure Recovery Technology)" non-temporary application No. 14/447,331 and the titled Techniques for Managing Radio Link Failure Recovery for a User Equipment Connected to a WWAN and a WLAN (for management Technology of radio link failure recovery for user equipment connected to WWAN and WLAN)" Provisional Application No. 61/866,862. These two applications have been assigned to the assignee of this application and are hereby expressly adopted by reference Include here.

[0004] Background

[0005] Aspects of the present disclosure generally relate to wireless communications, and in particular, to manage radio link failure (RLF) recovery of user equipment (UE) connected to both a wireless wide area network (WWAN) and a wireless local area network (WLAN) technology.

[0006] Wireless communication networks are widely deployed to provide various communication services, such as voice, video, packet data, messaging, broadcast, and so on. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing available network resources. Examples of such multiple-access networks include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, and single carrier FDMA (SC-FDMA) )The internet.

[0007] A wireless communication network may include a number of enhanced Node Bs (also referred to as eNodeBs or eNBs) capable of supporting communication for a number of user equipment (UE). A UE may communicate with eNodeB nodes via downlink and uplink. The downlink (or forward link) refers to the communication link from the eNodeB node to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the eNodeB node.

[0008] The key introduced into the current 3rd Generation Partnership Project (3GPP) specification family (or standard family) is the UE and the wireless wide area network (WWAN) (for example, Long Term Evolution (LTE) or Universal Mobile Telecommunications System (UMTS)) Dual connectivity with wireless local area network (WLAN) (for example, Wi-Fi). Thus, the UE can be in communication with both the eNodeB node and the WLAN access point (AP).

[0009] Given this dual connectivity, WWAN congestion can be alleviated by sending data traffic over WLAN (for example, offloading from LTE to WLAN) to increase overall system capacity. For this reason, radio access network (RAN)-based traffic aggregation between cellular RAN and WLAN is being introduced into the 3GPP standard family. In this approach, radio resource controller (RRC) commands signaled by the cellular RAN are used to offload traffic to the WLAN (for example, when the cellular RAN is congested) or to transfer traffic back (for example, fall back) ) To cellular RAN (for example, if the WLAN radio condition deteriorates and/or cellular congestion has been reduced).

[0010] When the radio frequency (RF) environment between the UE and the WWAN access node (eg, eNodeB node in LTE) deteriorates, the UE may enter a radio link failure (RLF). Generally speaking, when LTERLF occurs, the UE's RRC connection is suspended until the UE recovers from the RLF (for example, the RLF recovery process is completed). As a result, some LTE signaling radio bearers (eg, SRB 1) are unavailable during this time. In addition, all data traffic for WWAN (which may also be referred to as data flow (for example, Data Radio Bearer (DRB) for LTE)) is suspended and the WLAN report entry in RRC is cleared by the UE. For nodes with eNodeB and

For UEs that are in communication between WLAN access points, although the operation between LTE and WLAN is independent, LTE RLF may have a serious impact on cellular RAN-based WLAN networking because (1) any WLAN offloading and/or The fallback decision is performed by the cellular RAN, and (2) the WLAN measurement report from the UE is performed via RRC messages.

[0011] Currently, under the 3GPP standard family, LTE RLF processing includes three aspects: (a) RLF detection, (b) cell reselection, and (c) RRC connection re-establishment. However, none of these aspects include guidance on how to handle WLAN data streams during recovery from LTE RLF. In view of the foregoing, it can be understood that when the UE is interworking between LTE and WLAN, there may be significant problems and shortcomings associated with the current RLF processing.

[0012] Therefore, it is desirable to improve management of RLF recovery of UEs connected to both cellular and WLAN networks.

[0013] Public Overview

[0014] A brief overview of one or more aspects is given below to provide a basic understanding of these aspects. This overview is not an exhaustive overview of all the conceived aspects, and is neither intended to identify the key or decisive elements of all aspects, nor is it an attempt to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description given later.

[0015] In one aspect, an example method for managing radio link failure recovery is described. The method may include establishing communication with the first radio access technology and the second radio access technology. Additionally, the method may include transmitting at least one data stream on a first radio access technology and transmitting at least one data stream on a second radio access technology. The method may further include detecting a radio link failure between the user equipment and the first radio access technology. Furthermore, the method may include determining whether to maintain the at least one data stream on the second radio access technology when a radio link failure is detected.

[0016] In one aspect, a computer-readable medium for managing radio link failure recovery is described. The computer-readable medium may store computer-executable code, which may cause at least one computer to establish communication with the first radio access technology and the second radio access technology. In addition, the code can cause at least one computer to transmit at least one data stream on the first radio access technology and transmit at least one data stream on the second radio access technology. In addition, the code can enable at least one computer to detect a radio link failure between the user equipment and the first radio access technology. The code may additionally cause at least one computer to determine whether to maintain the at least one data stream on the second radio access technology when a radio link failure is detected.

[0017] In one aspect, an example device for managing radio link failure recovery is described. The device may include means for establishing communication with the first radio access technology and the second radio access technology. The device may include means for transmitting at least one data stream on a first radio access technology and at least one data stream on a second radio access technology. The device may include means for detecting a radio link failure between the user equipment and the first radio access technology. The device may include means for determining whether to maintain the at least one data stream on the second radio access technology when a radio link failure is detected.

[0018] In one aspect, an apparatus for managing radio link failure recovery is described. The apparatus may include a controller configured to establish communication with the first radio access technology and the second radio access technology. The apparatus may include a wireless wide area network (WWAN) radio configured to transmit at least one data stream on a first radio access technology. The apparatus may include a wireless local area network (WLAN) radio configured to transmit at least one data stream on a second radio access technology. The apparatus may include a radio link failure (RLF) component configured to detect a radio link failure between the user equipment and the first radio access technology. The apparatus may include an RLF data flow determining component configured to determine whether to maintain the at least one data flow on the second radio access technology when a radio link failure is detected.

[0019] In one aspect, a method for managing radio link failure recovery is described. The method may include establishing a first communication connection with the user equipment via a first radio access technology. The method may include receiving an indication that a second communication connection is established with the user equipment via a second radio access technology. The second communication connection can transmit at least one data stream. The method may include receiving a radio link failure recovery indication of the first communication connection from the user equipment. The method can include determining whether the at least one data stream can be maintained on the second communication connection via the second radio access technology during a radio link failure. The method may include indicating to the user device whether to maintain the transmission of the at least one data stream on the second communication connection via the second radio access technology on a per-data stream basis .

[0020] In one aspect, a computer-readable medium for managing radio link failure recovery is described. The computer-readable medium can store computer-executable code. The code can cause at least one computer to establish a first communication connection with the user equipment via the first radio access technology. The code can cause at least one computer to receive an indication that a second communication connection is established with the user equipment via the second radio access technology. The second communication connection can transmit at least one data stream. The code can enable at least one computer to receive a radio link failure recovery indication of the first communication connection from the user equipment. The code can cause at least one computer to determine whether the at least one data stream can be maintained on the second communication connection via the second radio access technology during a radio link failure. The code can cause at least one computer to indicate to the user equipment whether to maintain the transmission of the at least one data stream on the second communication connection via the second radio access technology on a per-data stream basis.

[0021] In one aspect, a device for managing radio link failure recovery is described. The device may include means for establishing a first communication connection with user equipment via a first radio access technology. The device may include means for receiving an indication that a second communication connection is established with the user equipment via the second radio access technology. The second communication connection can transmit at least one data stream. The device may include means for receiving a radio link failure recovery indication of the first communication connection from the user equipment. The device may include means for determining whether the at least one data stream can be maintained on the second communication connection via the second radio access technology during a radio link failure. The device may include means for indicating to the user equipment whether to maintain the transmission of the at least one data stream on the second communication connection via the second radio access technology on a per-data stream basis.

[0022] In one aspect, an apparatus for managing radio link failure recovery is described. The apparatus may include at least one memory and an RLF data flow configuration component in communication with the at least one memory. The RLF data stream configuration component may be configured to establish a first communication connection with the user equipment via a first radio access technology. The RLF data stream configuration component may be configured to receive an indication that a second communication connection is established with the user equipment via a second radio access technology, wherein the second communication connection transmits at least one data stream. The RLF data stream configuration component may be configured to receive a radio link failure recovery indication of the first communication connection from the user equipment. The RLF data stream configuration component may be configured to determine whether the at least one data stream can be maintained on the second communication connection via the second radio access technology during a radio link failure. The RLF data stream configuration component may be configured to indicate to the user equipment whether to maintain the transmission of the at least one data stream on the second communication connection via the second radio access technology on a per-data stream basis.

[0023] In one aspect, a method for managing radio link failure recovery is described. The method may include receiving a radio link failure recovery indication of the first communication connection from the user equipment. The method may include receiving an indication that a second communication connection is established with the user equipment via a second radio access technology. The second communication connection may be associated with at least one data stream. The method may include determining whether the at least one data stream can be restored on the second communication connection via the second radio access technology after the radio link failure is restored. The method may include indicating to the user equipment whether to resume transmission of the at least one data stream on the second communication connection via the second radio access technology.

[0024] In one aspect, a computer-readable medium for managing radio link failure recovery is described. The computer-readable medium may include computer-executable code. The code can enable at least one computer to receive a radio link failure recovery indication of the first communication connection from the user equipment. The code can cause at least one computer to receive an indication that a second communication connection is established with the user equipment via the second radio access technology. The second communication connection may be associated with at least one data stream. The code can enable at least one computer to determine whether the at least one data stream can be restored on the second communication connection via the second radio access technology after the radio link failure is restored. The code can cause at least one computer to indicate to the user equipment whether to resume the transmission of the at least one data stream on the second communication connection via the second radio access technology.

[0025] In one aspect, a device for managing radio link failure recovery is described. The device may include means for receiving a radio link failure recovery indication of the first communication connection from the user equipment. The device may include means for receiving an indication that a second communication connection is established with the user equipment via the second radio access technology. The second communication connection may be associated with at least one data stream. The device may include means for determining whether the at least one data stream can be restored on the second communication connection via the second radio access technology after the recovery of the radio link failure. The device may include means for indicating to the user equipment whether to resume the transmission of the at least one data stream on the second communication connection via the second radio access technology.

[0026] In one aspect, an apparatus for managing radio link failure recovery is described. The apparatus may include at least one memory and an RLF data flow configuration component in communication with the at least one memory. The RLF data stream configuration component may be configured to receive a radio link failure recovery indication of the first communication connection from the user equipment. The RLF data stream configuration component may be configured to receive an indication that a second communication connection is established with the user equipment via the second radio access technology. The second communication connection may be associated with at least one data stream. The RLF data flow configuration component may be configured to determine whether the at least one data flow can be restored on the second communication connection via the second radio access technology after the radio link failure is restored. The RLF data stream configuration component may be configured to indicate to the user equipment whether to resume transmission of the at least one data stream on the second communication connection via the second radio access technology.

[0027] In order to achieve the foregoing and related objects, these one or more aspects include the features fully described below and particularly pointed out in the appended claims. The following description and drawings detail certain illustrative features of these one or more aspects. However, these features are merely indicative of a few of the various ways in which the principles of various aspects can be adopted, and this description is intended to cover all such aspects and their equivalents.

[0028] Brief description of the drawings

[0029] In order to facilitate a more comprehensive understanding of the present disclosure, reference is now made to the accompanying drawings, in which similar elements are referenced with similar reference numerals. These drawings should not be construed as limiting the disclosure, but only intended to be illustrative.

[0030] FIG. 1 is a block diagram conceptually illustrating an example of a telecommunications system having various aspects of radio link failure recovery configured to manage user equipment as described herein;

[0031] FIG. 2 is a block diagram conceptually illustrating an example of a bearer architecture in a wireless communication system having various aspects of radio link failure recovery configured to manage user equipment as described herein;

[0032] FIG. 3 is a block diagram conceptually illustrating an exemplary eNodeB node and exemplary user equipment with various aspects of radio link failure recovery configured to manage user equipment as described herein;

[0033] FIG. 4 is a block diagram conceptually illustrating the aggregation of LTE and WLAN radio access technologies at a user equipment with various aspects of radio link failure recovery configured to manage the user equipment as described herein;

[0034] FIGS. 5A and 5B are conceptually illustrated as described herein with a radio link configured to manage user equipment

A block diagram of an example of a data path between a packet data network (PDN) and user equipment in various aspects of failure recovery; [0035] FIG. 6 is a conceptual illustration of radio link failure recovery configured to manage user equipment as described herein Block diagrams of specific aspects of the network entity;

[0036] FIG. 7 is a call flow diagram illustrating the communication between the user equipment, the eNodeB node and the WLAN access point according to the first aspect for managing the recovery of the radio link of the user equipment described herein;

[0037] FIG. 8 is a call flow diagram illustrating the communication between the user equipment, the eNodeB node and the WLAN access point according to the second aspect for managing the recovery of the radio link of the user equipment described herein;

[0038] FIG. 9 is a call flow diagram illustrating the communication between the user equipment, eNodeB node and WLAN access point according to the third aspect for managing the recovery of the radio link of the user equipment described herein;

[0039] FIG. 10 is a call flow diagram illustrating the communication between the user equipment, the eNodeB node and the WLAN access point according to the fourth aspect for managing the recovery of the radio link of the user equipment described herein;

[0040] FIG. 11 is a call flow diagram illustrating the communication between the user equipment, the eNodeB node and the WLAN access point according to the fifth aspect for managing the recovery of the radio link of the user equipment described herein;

[0041] FIG. 12 is a call flow diagram illustrating the communication between the user equipment, eNodeB node and WLAN access point according to the sixth aspect for managing the recovery of the radio link of the user equipment described herein;

[0042] FIG. 13 is a block diagram illustrating a method for managing radio link failure recovery by user equipment as described herein;

[0043] FIG. 14 is a block diagram illustrating a method for managing a radio link failure recovery at a user equipment by a first eNodeB node as described herein;

[0044] FIG. 15 is a block diagram illustrating a method for managing a radio link failure recovery at a user equipment by a second eNodeB node as described herein; and

[0045] FIG. 16 is a block diagram conceptually illustrating an example of a hardware implementation of an apparatus employing a processing system having a processing system configured to manage aspects of radio link failure recovery of user equipment as described herein.

[0046] Detailed description

[0047] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations, and is not intended to represent the only configuration in which the concepts described herein can be practiced. This detailed description includes specific details in order to provide a thorough understanding of various concepts. However, it will be obvious to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0048] The techniques described herein can be used in various wireless communication networks, such as CDMA, TDMA, FDMA, OFDMA, SCFDMA, and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (WCDMA) and other CDMA variants. cdma2000 covers IS-2000, IS-95 and IS-856 standards. TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and EUTRA are parts of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE Advanced (LTE-A) are new UMTS versions that use EUTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are from the company named "3rd Generation Partnership Project 2" (3GPP2) is described in the organization's documents. The technologies described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, some aspects of these technologies are described below for LTE, and

And LTE terminology is used in most of the description below.

[0049] According to various aspects of the present disclosure, there are provided methods for managing connections to wireless wide area networks (WWAN) (such as, for example, Long Term Evolution (LTE) or Universal Mobile Telecommunications System (UMTS)) and wireless local area networks (for example, Wi -Fi network) The new technology device and method of radio link failure (RLF) recovery at the user equipment (UE) of both. More specifically, various aspects for handling WLAN data flow throughout the RLF detection and recovery process are described.

[0050] Table 1 summarizes various aspects of the techniques described herein for managing data flow during RLF recovery. Regarding RLF behavior, in all aspects, suspend or stop WWAN (for example, LTE) data flow (which may also be referred to as data radio bearer (DRB)). Several aspects (eg, the second and third aspects) include both suspended cellular (eg, LTE) and WLAN data flow. In addition, some aspects (eg, the first, fourth, and fifth aspects) include optionally suspending a WLAN data stream along with a cellular (eg, LTE) data stream. The sixth aspect includes suspending only cellular (for example, LTE) data streams. In addition, Table 1 summarizes the actions associated with RLF recovery with respect to each aspect.

<td>aspect</td><td>RLF behavior</td><td>RLF recovery</td>

<td>1</td><td>Stop SRB1 and stop LTE (or LTE and WLAN) data flow</td><td>Keep the data flow mapping before RLF</td>

<td>2</td><td>Stop SRB1 and stop all data flow</td><td>The network decides whether to restart WLAN intercommunication based on the measurement report from the UE</td>

<td>3</td><td>Stop SRB1 and 14 stop all data flow</td><td>Similar to the second aspect, except that WLAN is reported during the connection re-establishment procedure</td>

<td>4</td><td>Stop SRB1 and stop LTE (or LTE and WLAN) data flow on 1.1</td><td>The UE decides whether to return to the previous state or fall back to LTE (instruct the RAN to decide)</td>

<td>5</td><td>Stop SRB1 and stop LTE (or LTE and WLAN) data flow</td><td>Similar to the fourth aspect, but the network configures UE behavior instead of UE decision</td>

<td>6</td><td>Stop only LTE data flow</td><td>Send SRB1 on WLAN (LTE data stream can be moved to WLAN during RLF)</td>

[0052] Table 1: Alternatives for WLAN data stream handling on the occasion of LTE RLF

[0053] A data stream may correspond to any data transmission between two network entities, such as, for example, a UE and an eNodeB node or a UE and a WLAN access point (AP). The data stream may also be referred to as, for example, data traffic, traffic, and/or data path.

For example, WWAN data flow may include or be associated with bearer, traffic flow template (TFT), transmission control protocol (TCP) connection, and/or quality of service (QoS) category. For example, the WLAN data stream may include or be associated with request to send (RTS), permission to send (CTS), other signaling, and/or user data.

[0054] The various aspects described herein can be described with reference to LTE as an example of the WWAN with which the UE is in communication. However, it will be understood that at least some aspects of the present disclosure may be applied to other WWANs (including UMTS) and/or other radio access technologies (RATs).

[0055] FIG. 1 is a block diagram conceptually illustrating an example of a telecommunications system 100 having included therein that is configured to manage aspects of a WWAN (eg, LTE) radio link failure (RLF). For example, the telecommunication system 100 may be an LTE network or a UMTS network. The telecommunication system 100 may include several evolved NodeB (eNodeB) 110, user equipment (UE) 120, and other network entities. The eNodeB node 110 may be a station that communicates with the UE 120 to provide access to the WWAN and may also be referred to as a base station, an access point, or the like. The Node B is another example of a station that communicates with the UE 120. Although not shown, one or more WLAN (or Wi-Fi) APs may also be in communication with the UE 120 to provide access to a wireless local area network (WLAN) or some other type of local area network (LAN).

[0056] Each eNodeB node 110 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of the eNodeB node 110 and/or the eNodeB node subsystem serving the coverage area depending on the context in which the term is used.

[0057] The evolved Node B 110 may provide communication coverage for macro cells, pico cells, femto cells, and/or other types of cells. A macro cell may cover a relatively large geographic area (e.g., an area with a radius of several kilometers), and may allow unrestricted access by UEs 120 that have a subscription to wireless services associated with the macro cell. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 may be subscribed to a closed subscriber group ( CSG), the closed subscriber group (CSG) is established for use by one of the UEs 120 in the home location (such as, for example, a home or an office) of a user of one of the UEs 120. The eNodeB node 110 for the macro cell It may be called a macro eNodeB node. The eNodeB node 110 used for a pico cell may be called a pico eNodeB node. The evolved NodeB 110 used for a femto cell may be called a femto eNodeB node or a home eNodeB node.

[0058] In the example shown in FIG. 1, the evolved Node Bs 110a, 110b, and 110c may be macro eNodeB nodes of the macro cells 102a, 102b, and 102c, respectively. The evolved Node B 110x may be a pico eNodeB for the pico cell 102x. The evolved Node Bs 110y and 110z may be femto eNodeB nodes for femto cells 102y and 102z, respectively. The eNodeB node 110 may provide communication coverage of one or more (for example, three) cells.

[0059] The telecommunications system 100 may include one or more relay stations 110r and 120r, which may also be referred to as relay eNodeB nodes, relays, and so on. The relay station 110r may receive transmission of data and/or other information from an upstream station (for example, eNodeB node 110 or UE 120) and send the data and/or other information to a downstream station (for example, UE 120 or eNodeB node 110). To the transmission station. The relay station 120r may be a UE that relays transmissions for other UEs (not shown). In the example shown in FIG. 1, the relay station 110r may communicate with the eNodeB node 110a and the UE 120r to facilitate communication between the eNodeB node 110a and the UE 120r.

[0060] The telecommunication system 100 may be a heterogeneous network including different types of eNodeB nodes 110 (for example, macro eNodeB nodes 110a, 110b, and 110c, pico eNodeB nodes 110x, femto eNodeB nodes 110y and 110z, relay stations 110r, etc.). These different types of eNodeB nodes 110 may have different transmit power levels, different coverage areas, and

Different effects of interference in the telecommunications system 100. For example, the macro eNodeB nodes 110a, 110b, and/or 110c may have high transmit power levels (for example, 20 watts), while the pico eNodeB nodes 110x, femto eNodeB nodes 110y and 110z, and/or relay stations 110r may have lower transmission power levels. Transmit power level (for example, 1 watt).

[0061] The telecommunications system 100 may support synchronous or asynchronous operation. For synchronization operations, each eNodeB node 110 may have similar frame timing, and transmissions from different eNodeB nodes 110 may be roughly aligned in time. For asynchronous operation, each eNodeB node 110 may have a different frame timing, and transmissions from different eNodeB nodes 110 may not be aligned in time. The techniques described in this article can be used for both synchronous and asynchronous operations.

[0062] The network controller 130 may be coupled to a group of eNodeB nodes 110 and provide coordination and control of these eNodeB nodes 110. The network controller 130 may communicate with the eNodeB node 110 via a backhaul (not shown). The eNodeB nodes 110 may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul (eg, X2 interface) (not shown). In aspects where the telecommunications system 100 includes an eNodeB node and one or more WLAN APs, these two types of access nodes may or may not be connected to each other via a backhaul. However, in a situation where the eNodeB node and the WLAN AP are not connected via a backhaul, the eNodeB node and the WLAN AP may communicate with each other through an intermediary (such as, for example, one of the UE 120).

[0063] The UEs 120 may be dispersed throughout the telecommunications system 100, and each UE 120 may be camped or mobile. The UE 120 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, and so on. In an example, each UE 120 may be a cell phone, a smart phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) Stations, tablet devices, netbooks, smartbooks, etc. The UE 120 may be able to communicate with the macro eNodeB nodes 110a, 110b, and 110c, the pico eNodeB node 110x, the femto eNodeB nodes 110y and 110z, the relay station 110r, and/or any other network entity. For example, in Figure 1, a solid line with a double arrow may indicate a desired transmission between a specific UE 120 and its serving eNodeB node 110. The serving eNodeB node 110 is designated to serve the specific UE on the downlink and/or uplink. The eNodeB node 110 of the UE 120. A dotted line with a double arrow may indicate interference transmission between a specific UE 120 and an eNodeB node 110 (for example, a non-serving eNodeB node).

[0064] LTE telecommunication networks can utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM can reduce the system bandwidth Divided into multiple (K) orthogonal subcarriers, which are also often referred to as tones, frequency slots, and so on. Each subcarrier can be modulated with data. Generally speaking, modulation symbols can be sent in the frequency domain under OFDM, and in the time domain under SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of subcarriers may be 15kHz, and the minimum resource allocation (referred to as "resource block") may be 12 subcarriers (or 180kHz). Therefore, for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can be divided into subbands. For example, a subband may cover 1.08 MHz (ie, 6 resource blocks), and for a system bandwidth of 1.25, 2.5, 5, 10, 15, or 20 MHz, there may be 1, 2, 4, 8, or 16 subbands, respectively.

[0065] FIG. 2 is a block diagram conceptually illustrating an example of a bearer (eg, data flow) architecture in a wireless communication system 200 having various aspects configured to manage WWAN (eg, LTE) RLF according to aspects of the present disclosure. The bearer architecture may be used for end-to-end services 235 between the UE 215 and the addressable peer entity 230 on the network, and the UE 215 may be one of the UEs 120 in FIG. 1. The peer entity 230 may be a server, another UE, or another type of network addressable device. The end-to-end service 235 may forward data between the UE 215 and the peer entity 230 according to a feature set (eg, quality of service (QoS)) associated with the end-to-end service 235. The end-to-end service 235 can be provided by at least the UE 215, the eNodeB node 205 (for example, one of the eNodeB nodes 110 in FIG. 1), the serving gateway (SGW) 220, the packet data network (PDN) gateway (PGW) 225, and peer entities 230 to achieve. The UE 215 and the eNodeB node 205 may be components of an evolved UMTS terrestrial radio access network (E-UTRAN) 208,

E-UTRAN 208 is the air interface of the LTE/LTE-A system. The serving gateway 220 and the PDN gateway 225 may be components of an evolved packet core (EPC) 209, and the EPC 209 is the core network architecture of the LTE/LTE-A system. The peer entity 230 may be an addressable node on the PDN 210 that is communicatively coupled with the PDN gateway 225.

[0066] The end-to-end service 235 can be implemented by an evolved packet system (EPS) bearer 240 between the UE 215 and the PDN gateway 225, and an external bearer 245 on the SGi interface between the PDN gateway 225 and the peer entity 230 . The SGi interface can expose the Internet Protocol (IP) or other network layer addresses of the UE 215 to the PDN 210.

[0067] The EPS bearer 240 may be an end-to-end tunnel defined for a specific QoS. Each EPS bearer 240 can be associated with multiple parameters, such as QoS class identifier (QCI), allocation and retention priority (ARP), guaranteed bit rate (GBR), and aggregate maximum bit rate (AMBR3QCI can be based on latency , Packet loss, GBR, and priority to indicate an integer of the QoS class associated with the predefined packet forwarding treatment. In some examples, QCI can be an integer from 1 to 9. In addition, ARP can be used by eNodeB The scheduler of node 205 is used to provide preemptive priority in the case of contention for the same resource between two different bearers. GBR can specify separate downlink and uplink guaranteed bit rates. Certain QoS classes can be non-GBR, So that no guaranteed bit rate is defined for those types of bearers.

[0068] The EPS bearer 240 can be carried by the E-UTRAN radio access bearer (E-RAB) 250 between the UE 215 and the serving gateway 220, and the S5/S8 on the S5 or S8 interface between the serving gateway 220 and the PDN gateway. 255 to achieve. S5 refers to a signaling interface between the serving gateway 220 and the PDN gateway 225 in a non-roaming scenario, and S8 refers to a similar signaling interface between the serving gateway 220 and the PDN gateway 225 in a roaming scenario. The E-RAB 250 can be implemented by the radio bearer 260 on the LTE-Uu air interface between the UE 215 and the eNodeB node 205, and the S1 bearer 265 on the S1 interface between the eNodeB node and the serving gateway 220.

[0069] It will be understood that although FIG. 2 illustrates the bearer hierarchy in the context of an example of an end-to-end service 235 between the UE 215 and the peer entity 230, certain bearers may be used to communicate with the end-to-end service 235. Irrelevant data. For example, a radio bearer 260 or other type of bearer may be established to transfer control data between two or more entities, where the control data is not related to the end-to-end service 235 data.

[0070] As discussed above, in certain configurations, a system (such as the wireless communication system 200 of FIG. 2) may include cellular (eg, LTE) and WLAN (eg, Wi-Fi) interworking. Thus, data related to one or more EPS bearers 240 (for example, cellular or LTE data) can be offloaded from the eNodeB node 205 to a WLAN AP (not shown), thereby transferring the bearer traffic from the EPC 212 and replacing it. Transfer to PDN 210 on the path. Additional aspects related to offloading and/or fallback of LTE data from EPC 212 to PDN 210 via WLAN AP will be described with reference to FIGS. 5A and 5B.

[0071] It will be understood that the bearer may also be referred to as a data stream. The term "bearer" is often used to describe LTE (or other WWAN) data streams (for example, data radio bearer or DRB); and for other radio access technologies (RAT) (such as, for example, WLAN (or Wi-Fi) )) The data stream is unlikely to be called "bearer", but the more general term "data stream" is used.

[0072] FIG. 3 is a conceptual illustration of an exemplary eNodeB node 310 (e.g., eNodeB node 110 of FIG. 1 and/or of FIG. 2 having various aspects configured to manage WWAN (e.g., LTE) RLF) according to aspects of the present disclosure. One of the eNodeB nodes 205) and a block diagram of an exemplary UE 320 (for example, one of the UE 120 of FIG. 1 and/or one of the UE 215 of FIG. 2).

[0073] The eNodeB node 310 may be equipped with an antenna 3341-t, and the UE 320 may be equipped with an antenna 3521-r, where t and r are integers greater than or equal to 1. At the eNodeB node 310, the base station transmission processor 322 may receive data from the base station data source 312 and control information from the base station controller 340. In one aspect, the base station controller 340 may include a processor, and thus may also be referred to as a base station processor 340 or a base station controller/processor 340. The control information can be carried on PBCH, PCFICH, PHICH, PDCCH, etc. Data can be carried on PDSCH and so on. The base station transmit processor 322 can be

Processing (for example, encoding and symbol mapping) data and control information to obtain data symbols and control symbols, respectively. The base station transmission processor 322 may also generate reference symbols (RS) (for example, for PSS, SSS, and reference signals that vary from cell to cell). The base station transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (for example, precoding) on data symbols, control symbols, and/or reference symbols if applicable, and may output The symbol stream is provided to the base station modulator/demodulator (MOD/DEMOD) 3321-t. Each base station modulator/demodulator 332 may process a respective output symbol stream (for example, for OFDM, etc.) to obtain an output sample stream. Each base station modulator/demodulator 332 may further process (eg, convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulator/demodulator 3321-t may be transmitted via the antenna 3341-t, respectively.

[0074] At the UE 320, the UE antenna 3521-r may receive the downlink signal from the eNodeB node 310 and may respectively provide the received signal to the UE modulator/demodulator (MOD/DEMOD) 3541. Each UE modulator/demodulator 354 can process (eg, filter, amplify, down-convert, and digitize) its respective received signal to obtain input samples. Each UE modulator/demodulator 354 may further process the input samples (eg, for OFDM, etc.) to obtain received symbols. The UE MIMO detector 356 can obtain received symbols from all UE modulators/demodulators 3541-r, perform MIMO detection on these received symbols if applicable, and provide detected symbols. The UE receiving processor 358 may process (for example, demodulate, deinterleave, and decode) these detected symbols, provide the decoded data for the UE 320 to the UE data sink 360, and provide the decoded control information to UE controller 380. In one aspect, the UE controller 380 may include a processor, and thus may also be referred to as a UE processor 380 or a UE controller/processor 380.

[0075] On the uplink, at the UE 320, the UE transmit processor 364 may receive and process data from the UE data source 362 (for example, for PUSCH) and data from the UE controller 380 (for example, for PUCCH) control information. The UE transmit processor 364 may also generate reference symbols of the reference signal. The symbols from the UE transmit processor 364 may be pre-coded by the UE TX MIMO processor 366 where applicable, and further processed by the UE modulator/demodulator 3541-r (for example, for SC-FDM, etc.), and sent to The eNodeB node 310 transmits. At the eNodeB node 310, the uplink signal from the UE 320 can be received by the base station antenna 334, processed by the base station modulator/demodulator 332, detected by the base station MIMO detector 336 if applicable, and by the base station receiving processor 338 is further processed to obtain the decoded data and control information sent by the UE 320. The base station receiving processor 338 may provide the decoded data to the base station data sink 346 and the decoded control information to the base station controller 340.

[0076] The base station controller 340 and the UE controller 380 may direct operations at the eNodeB node 310 and the UE 320, respectively. The base station controller 340 and/or other processors and modules at the eNodeB node 310 may perform or direct the execution of various processes for the techniques described herein. The UE controller 380 and/or other processors and modules at the UE 320 may also be configured to execute or direct the functional blocks illustrated in FIG. 6 and/or for the management and cellular and WLAN (or Wi-Fi) described herein. -Fi) The implementation of other processes of the RLF recovery technology of the UE in communication between the two networks. The base station memory 342 and the UE memory 382 may store data and program codes for the eNodeB node 310 and the UE 320, respectively. The scheduler 344 may schedule the UE 320 for data transmission on the downlink and/or uplink.

[0077] In one configuration, the UE 320 may include means for establishing communication with a first radio access technology (RAT) and a second RAT; for transmitting at least one data stream on the first RAT and for transmitting at least one data stream on the first RAT. A device for transmitting at least one data stream on the second RAT; a device for detecting a radio link failure between the user equipment and the first RAT; and a device for determining whether to maintain the radio link on the second RAT when the radio link failure is detected At least one data stream device. In one aspect, the aforementioned means may be a UE controller 380, a UE memory 382, a UE receiving processor 358, a UE MIMO detector 356, a UE modulator/demodulator 354, and a UE configured to perform the functions recited by the aforementioned means. UE antenna 352. On the other hand, the aforementioned installation

The device may be a module, component, or any device configured to perform the functions recited by the aforementioned means.

[0078] In one configuration, the eNodeB node 310 may include means for establishing a first communication connection with the user equipment via a first RAT; for receiving an indication that a second communication connection is established with the user equipment via a second RAT A device, wherein the second communication connection transmits at least one data stream; a device for receiving a radio link failure recovery indication of the first communication connection from a user equipment (for example, UE 320), wherein the user equipment and the local area network and the user The communication connection between the equipment and the WWAN has been established; means for determining whether the at least one data stream can be maintained on the second communication connection via the second RAT during a radio link failure; and means for indicating to the user equipment whether A device that maintains the transmission of the at least one data stream on a second communication connection via the second RAT on a per data stream basis. In another configuration, the eNodeB node 310 may include means for receiving a radio link failure recovery indication of the first communication connection from, for example, the UE 320; for receiving an indication that a second communication connection is established with the user equipment via the second RAT Means for determining whether the at least one data stream can be restored on the second communication connection via the second RAT after the radio link failure is restored; and means for Indicate to the user equipment whether to pass A device for the second RAT to resume the transmission of the at least one data stream on the second communication connection. In one aspect, the aforementioned means may be a base station controller 340, a base station memory 342, a base station transmission processor 322, a base station modulator/demodulator 332, and a base station antenna 334 configured to perform the functions listed in the aforementioned means. In another aspect, the aforementioned means may be a module, component, or any device configured to perform the functions recited by the aforementioned means.

[0079] FIG. 4 is a block diagram conceptually illustrating carrier aggregation of LTE and WLAN radio access technologies (RAT) at UE 415 according to various aspects of the present disclosure, where UE 415, eNodeB node 405-a and/or WLAN AP 405-b has various aspects configured to manage WWAN (eg, LTE) RLF recovery. This aggregation can occur in a system 400 that includes a multimode UE 415. The UE 415 can use one or more component carriers 1 to N (CC1-CCn) to communicate with the eNodeB node 405-a, and use the WLAN carrier 440 to communicate with the WLAN (or Wi-Fi) AP 405-b communication. UE 415 may be an example of one or more of UE 120 of FIG. 1, UE 215 of FIG. 2, and UE 320 of FIG. 3. The eNodeB node 405-a may be an example of one or more of the eNodeB node 110 of FIG. 1, the eNodeB node 205 of FIG. 2, and the eNodeB node 310 of FIG. Although only one UE 415, one eNodeB node 405-a and one WLAN AP 405-b are illustrated in FIG. 4, it will be appreciated that the system 400 may include any number of UE 415, eNodeB nodes 405-a and/or WLAN AP 405-b.

[0080] The eNodeB node 405-a may transmit information to the UE 415 through the forward (downlink) channels 4321 to 432-N on the LTE component carriers CC1 to CCn 430. In addition, the UE 415 may transmit information to the eNodeB node 405-a through the reverse (uplink) channels 434-1 to 434-N on the LTE component carriers CC1 to CCn. Similarly, the WLAN AP 405-b may transmit information to the UE 415 through the forward (downlink) channel 452 on the WLAN carrier 440. In addition, the UE 415 may transmit information to the WLAN AP 405-b through the reverse (uplink) channel 454 on the WLAN carrier 440.

[0081] In describing the various entities in FIG. 4, for explanatory purposes, the nomenclature associated with the 3GPP LTE or LTE-A wireless network is used. However, it will be appreciated that the system 400 may operate in other networks, such as but not limited to UMTS networks, OFDMA wireless networks, CDMA networks, 3GPP2CDMA2000 networks, and so on.

[0082] In multi-carrier operation, downlink control information (DCI) messages associated with different UEs 415 may be carried on multiple component carriers. For example, the DCI on the PDCCH may be included on the same component carrier configured by the UE 415 for PDSCH transmission (eg, same-carrier signaling). Alternatively or additionally, DCI may be carried on a component carrier different from the target component carrier used for PDSCH transmission (for example, cross-carrier signaling). In some embodiments, a carrier indicator field (CIF) that can be semi-statically enabled can be included in some or all DCI formats to facilitate transmission of PDCCH control signaling from a carrier other than the target carrier used for PDSCH transmission ( For example, cross-carrier signaling).

[0083] In this example, the UE 415 may receive data from an eNodeB node 405-a. However, users at the edge of a cell may experience high inter-cell interference, which can limit the data rate. Multi-streaming allows the UE to receive data from two eNodeB nodes 405-a at the same time. Multi-streaming works by sending and receiving data to and from two eNodeB nodes 405-a in two completely separate streams when the UE 415 is simultaneously in range of two cell towers in two adjacent cells. The UE 415 communicates with the two eNodeB nodes 405-a at the same time when the device is on the edge of the reach of any one of the two eNodeB nodes 405-a. By scheduling two independent data streams from two different eNodeB nodes to the UE 415 at the same time, the multi-stream takes advantage of the uneven load in the HSPA network. This helps to improve the user experience at the edge of the cell while increasing network capacity. In one example, the throughput data speed of users at the edge of the cell can be doubled. Multi-streaming is a feature similar to dual-carrier HSPA in LTE/LTE-A, but there are some differences. For example, dual carrier HSPA does not allow connectivity to multiple towers to connect to one device at the same time.

[0084] Prior to LTE-A standardization, the LTE component carrier 430 was backward compatible, which enabled a smooth transition to the new version. However, this feature causes the LTE component carrier 430 to continuously transmit a common reference signal (CRS, also referred to as a cell-specific reference signal) in each subframe across the bandwidth. The vast majority of cell site energy consumption is caused by power amplifiers, because even when only limited control signaling is being transmitted, the cell remains on, which makes the amplifier continue to consume energy. CRS was introduced in Release 8 of the LTE standard and is the most basic downlink reference signal in LTE. The CRS is transmitted in each resource block in the frequency domain and in each downlink subframe. The CRS in the cell can be used for one, two, or four corresponding antenna ports. CRS can be used by remote terminals to estimate the channel for coherent demodulation. The New Carrier Type (NCT) allows the cell to be temporarily shut down by removing the CRS transmission in four-fifths of the subframe. This feature reduces the power consumed by the power amplifier, as well as the overhead and interference from the CRS, because the CRS is no longer continuously transmitted across the bandwidth in each subframe. In addition, this new carrier type allows the use of UE-specific demodulation reference symbols to operate the downlink control channel. The new carrier type can operate as an extension carrier in conjunction with another LTE/LTE-A carrier or alternatively as a stand-alone non-backward compatible carrier.

[0085] FIGS. 5A and 5B conceptually illustrate UE 515 and PDN in wireless communication systems 500-a and 500-b with various aspects configured to manage WWAN (eg, LTE) RLF recovery according to various aspects of the present disclosure. A block diagram of an example of data paths 545 and 550 between (e.g., the Internet). The data paths 545 and 550 are shown in the context of the wireless communication system 500-a of FIG. 5A and the wireless communication system 500-b of FIG. 5B, which aggregate WLAN and cellular (e.g., LTE) radio access technologies ( RAT). In each example, the wireless communication systems 500-a and 500-b may include a multi-mode UE 515, an eNodeB node 505-a, and a WLAN AP 505-b. The UE 515 may be the UE 120 of FIG. 1 and the UE of FIG. 2. 215. Examples of one or more of UE 320 of FIG. 3 and UE 415 of FIG. 4. The eNodeB node 505-a may be an example of one or more of the eNodeB node 110 of FIG. 1, the eNodeB node 205 of FIG. 2, the eNodeB node 310 of FIG. 3, and the eNodeB node 405-a of FIG. 4, and a WLAN AP 505-b may be an example of the WLAN AP 405-b of FIG. 4. Wireless communication system 500-a and 500-b may also include EPC 512, PDN 510, and peer entities 530, each of which may be similar to the evolved packet core (EPC) 212, PDN 210, and peer entity 230 of FIG. 2, respectively. The EPC 512 of each example may include a mobility management entity (MME) 505, a serving gateway (SGW) 520, and a PDN gateway (PGW) 525, where the SGW 520 and the PGW 525 may be similar to the SGW 220 and PGW 225 of FIG. 2. The home subscriber system (HSS) 535 may be communicatively coupled with the MME 530. The UE 515 of each example may include an LTE radio 520 and a WLAN radio 525. Specifically referring to FIG. 5A, the eNodeB node 505-a and the WLAN AP 505-b may be able to use one or more LTE component carriers or an aggregation of one or more WLAN component carriers to provide the UE 515 with access to the PDN 510. Using this access to the PDN 510, the UE 515 can communicate with the peer entity 530. The eNodeB node 505-a can provide access to the PDN 510 through the evolved packet core 512 (for example, through the data path 545), and

The WLAN AP 505-b may provide direct access to the PDN 510 (for example, through the data path 550). In one aspect, LTE and WLAN data streams can travel on data paths 545 and 550.

[0086] The MME 530 may be a control node that processes the signaling between the UE 515 and the EPC 512. Generally speaking, MME 530 can provide bearer and connection management. The MME 530 can thus be responsible for idle mode UE tracking and paging, bearer activation and deactivation, and SGW selection for the UE 515. The MME 530 can communicate with the eNodeB node 505-a on the S1-MME interface. The MME 530 may additionally authenticate the UE 515 and implement Non-Access Stratum (NAS) signaling with the UE 515.

[0087] The HSS 535 may store subscriber data, manage roaming constraints, manage access point names (APN) accessible by the subscriber, and associate the subscriber with the MME 530, among other functions. The HSS 535 can communicate with the MME 530 on the S6a interface defined by the Evolved Packet System (EPS) architecture standardized by the 3GPP organization.

[0088] All user IP packets transmitted on LTE can be delivered to the SGW 220 through the eNodeB node 505-a, and the SGW 220 can be connected to the PDN gateway 525 on the S5 signaling interface and connected to the MME 5300 on the S11 signaling interface. It can reside in the user plane and act as a mobility anchor point for handover between eNodeB nodes and handover between different access technologies. The PDN gateway 525 can provide UE IP address allocation and other functions.

[0089] The PDN gateway 525 may provide connectivity to one or more external packet data networks (such as PDN 510) on the SGi signaling interface. The PDN 510 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming service (PSS), and/or other types of PDN.

[0090] In this example, the user plane data between the UE 515 and the EPC 512 may pass through the same set of one or more EPS bearers (or data streams), regardless of whether the traffic flow passes through the LTE link path 545 or The data path 550 of the WLAN link. The signaling or control plane data related to the set of one or more EPS bearers can be transmitted between the LTE radio 520 of the UE 515 and the MME 530 of the EPC 512-b by means of the eNodeB node 505-a.

[0091] FIG. 5B illustrates an example wireless communication system 500-b in which the eNodeB node 505-a and the WLAN AP 505-b are co-located or otherwise in high-speed communication with each other. In this example, the EPS bearer related data between the UE 515 and the WLAN AP 505-b may be routed to the eNodeB node 505-a, and then routed to the EPC 512. In this way, all EPS bearer related data can be forwarded along the same path between the eNodeB node 505-a, EPC 512, PDN 510, and peer entity 530.

[0092] Referring to FIG. 6, a multimode UE 615 and an eNodeB node 605-a and a WLAN (eg, Wi-Fi) AP within a wireless communication system 600 having aspects configured to manage RLF recovery of user equipment as described herein 605-b is in communication. UE 615 may be an example of one or more of UE 120 of FIG. 1, UE 215 of FIG. 2, UE 320 of FIG. 3, UE 415 of FIG. 4, and UE 515 of FIGS. 5A and 5B. The eNodeB node 605-a may be the eNodeB node 110 of FIG. 1, the eNodeB node 205 of FIG. 2, the eNodeB node 310 of FIG. 3, the eNodeB node 405-a of FIG. 4, and the eNodeB node 505-a of FIGS. 5A and 5B. Examples of one or more. The WLAN AP 605-b may be an example of one or more of the WLAN AP 405-b of FIG. 4 and the WLAN AP 505-b of FIGS. 5A and 5B. As described above with respect to FIGS. 5A and 5B, the wireless communication system 600 may include a WWAN (for example, LTE or UMTS) and a WLAN (for example, Wi-Fi) RAT, so that the UE 615 can communicate with the eNodeB node 605-a and the WLAN AP 605-b is in communication and realizes WWAN and WLAN data flow through various communication paths. Due to the simultaneous or concurrent connection with the eNodeB node 605a and the WLAN AP 605-b, this scenario can also be referred to as the "dual connectivity" of the UE 615.

[0093] The UE 615, the eNodeB node 605-a, and the WLAN AP 605-b may be configured to manage the WWAN at the UE 615 (e.g., LTE) according to different technologies (e.g., the six different aspects shown in Table 1 above). ) RLF recovery. More specifically, six aspects for handling WLAN data flow throughout the LTE RLF detection and recovery process are described. Although these aspects are described separately, it will be understood that some or all of these aspects may be configured in any number of combinations, serial, and/or

Work with each other in parallel. Accordingly, the combination of these aspects can lead to different alternatives for WLAN data flow handling on the occasion of LTE RLF.

[0094] The UE 615 includes a WWAN radio 620 and a WLAN radio 625, which may be the same as or similar to the LTE radio 520 and the WLAN radio 525 of the UE 515 shown in FIGS. 5A and 5B. The WWAN radio 620 may be configured to provide communication between the UE 615 and the eNodeB node 605-a on the WWAN radio link 661 (for example, on the path 545 of FIGS. 5A and 5B), and the WLAN radio 625 may be configured to communicate on the WLAN radio link The communication between UE 615 and WLAN AP 605-b is provided on path 662 (eg, data path 550 of FIGS. 5A and 5B). Each of the WWAN radio link 661 and the WLAN radio link 662 includes at least one data stream (eg, a signaling data stream, a user data stream, etc.). UE 615 includes an RLF component 630 configured to detect LTE RLF at UE 615 and handle all aspects related to RLF processing, such as RLF detection, cell reselection, and RRC connection reestablishment, as described in the 3GPP family of standards of. When RLF of the WWAN radio link 661 is detected, for example due to poor RF conditions, the RLF component 630 may be configured to communicate the RLF indication 651 to the RLF data flow determination component 640.

[0095] The RLF data flow determination component 640 is configured to receive the RLF indication 651 and determine how to handle LTE and WLAN data flows during the (upcoming) RLF recovery procedure based on the indication. Optionally and in various aspects, the RLF data flow determination component 640 may include a decision module 641, a network configuration module 642, and/or a rerouting module 643, each of which will be included in each entity according to Various aspects of the RLF data flow determination component 640 will be discussed in detail. In all aspects described herein, the RLF data flow determination component 640 includes a WWAN data flow suspension module 6440 WWAN data flow suspension module configured to suspend an LTE data flow upon detection of RLF and/or in response to an RLF indication 651 644 may be configured to generate and transmit a suspend/resume indication 655 to the WWAN radio 620 to indicate whether and when to suspend and/or resume the LTE data stream. In some aspects described herein, the RLF data flow determination component 640 includes a WLAN data flow suspension module 6450 that is configured to suspend a WLAN data flow when RLF is detected, and the WLAN data flow suspension module 645 may be configured to generate and send data to the WLAN The radio 625 transmits a suspend/maintain/resume indication 657 to indicate whether and when to suspend, maintain, and/or resume the WLAN data stream.

[0096] In addition, the UE 615 includes a measurement report configured to receive a report instruction 653 from the RLF data flow determination component 640 and generate a measurement report 652 in response and transmit the measurement report 652 to the eNodeB node 605-a and/or WLAN AP 605-b Components 635. Depending on the specific aspect, the reporting instructions 653 may include, for example, information on what parameters and/or radio signal conditions to measure, when and how frequently to perform the measurements, which measurements to report, when and how often to report the measurements, and where to transmit Instructions for measurement reports, etc. The report instruction 653 may also include an instruction from the RLF data flow determination component 640 to delete or maintain all current WLAN measurement entries from any measurement report on the occasion of RLF detection. The measurement report 652 may include information related to radio signal conditions on the LTE and/or WLAN network measured by the WWAN radio 620 and/or WLAN radio 625 of the UE 615, respectively. The measurement reporting component 635 can operate in conjunction with the WWAN radio 620 and/or the WLAN radio 625 to execute the reporting instructions 653. Subsequently, the measurement report component 635 may communicate the measurement report 652 to the WWAN radio 620 for transmission to the eNodeB node 605-a. In one aspect (not shown), the measurement report component 635 can report to the WLAN The line 625 communicates the measurement report 652 for transmission to the WLAN AP 605-b.

[0097] Optionally and in some aspects described herein, the eNodeB node 605-a includes an RLF data flow configuration component 610 configured to generate and transmit a configuration 654 to the UE 615. The configuration 654 may be any information, instructions, etc. that can be used to instruct the UE 615 on how to handle LTE and/or WLAN data streams during RLF recovery. For example, the configuration 654 may be a quality of service (QoS) parameter, the QoS parameter may allow the RLF data flow determination component 640 to determine the configuration based on the parameter, and/or the QoS parameter may include information on how to handle LTE and WLAN data flows during RLF processing Explicit instructions. In another example

In, the configuration 654 may be an access network discovery and selection function (ANDSF) policy, and the ANDSF policy may be or include a flag indicating whether to suspend the WLAN data stream during the RLF. The RLF data flow determination component 640 on the UE 615 can be configured to receive the configuration 654 and use the configuration 654 to determine how to use the decision module 641, the network configuration module 642, and/or the reconfiguration when determining how to handle LTE and WLAN data streams during RLF processing. Which modules in the routing module 642 (for example, which of the six aspects described herein are applicable to this scenario).

[0098] Optionally and in some aspects described herein, the WLAN AP 605-b includes a WWAN forwarding component 612 configured to allow the LTE data stream to be maintained (eg, not suspended) during RLF recovery at the UE 615. More specifically, the WWAN forwarding component 612 can be configured to communicate with both the UE 615 and the eNodeB node 605-a (via the communication connection 614) during the RLF process and determine whether to receive LTE data streams from the UE 615 and stream these LTE data Send to eNodeB node 605-a or vice versa.

[0099] Various aspects of managing RLF recovery and UE 615, eNodeB nodes will be further described in conjunction with FIGS. 7-12

Corresponding components of 605-a and WLAN AP 605-b, Figure 7-12 is a call flow diagram illustrating each aspect in turn.

[0100] Referring to FIG. 7, a call flow 700 illustrates the communication between the UE 615, the eNodeB node 605-a and the WLAN AP 605-b of FIG. 6 according to the first aspect for managing the RLF recovery of the UE. Specifically, in the first aspect, the apparatus and method of the present disclosure stop LTE data flow and optionally stop WLAN data flow when RLF is detected, and retain the data flow mapping before RLF for the purpose of recovering from RLF. Used in the actual reconstruction of the data stream. The actions of the call flow 700 are executed by the UE 615, and include an RLF component 630, a measurement report component 635, a WWAN radio 620, a WLAN radio 625, and an RLF data flow determination component 640. According to the first aspect, the RLF data flow determining component 640 includes a WWAN data flow suspension module 644, a WLAN data flow suspension module 645, and a decision module 641.

[0101] At 701, the RLF component 630 of the UE 615 detects RLF according to the current 3GPP standard. At 702, the WWAN data stream suspension module 644 suspends all LTE data streams transmitted on the WWAN radio link 661 via the WWAN radio 620 to the eNodeB node 605-a. Although not shown, the WWAN data stream suspension module 644 also instructs the measurement report component 652 via the report instruction 653 to delete all WLAN measurement entries in any existing measurement report. At 703, the decision module 641 determines whether to suspend the WLAN data stream transmitted on the WLAN radio link 662 via the WLAN radio 625 to the WLAN AP 605-b. If the decision module 641 determines that the WLAN data stream is to be suspended (this is shown at 703a in the example of the call flow 700), the WLAN data stream is suspended. If the decision module 641 determines not to suspend the WLAN data stream (not shown), the WLAN data stream is maintained during RLF processing (or resumed in the case of temporary suspension after RLF detection).

[0102] In 704, the RLF component 630 executes the cell reselection procedure according to the current 3GPP standard, and sends an RRC connection re-establishment request message in 705, receives an RRC connection re-establishment message in 706, and sends an RRC connection re-establishment complete message in 707 To reestablish the connection between the UE 615 and the eNodeB node 605-a or another eNodeB node. In the case where the decision module 641 determines that the WLAN data flow is to be suspended, at 708, the WLAN data flow is resumed between the UE 615 and the WLAN AP 605-b. At 709, the UE 615 and the eNodeB node 605-a perform the RRC connection reconfiguration procedure according to the current 3GPP standard. The decision module 641 may be configured to determine that the RLF component 630 is executing an RRC connection reconfiguration procedure and in response to provide a report instruction 653 to the measurement reporting component 635 to instruct the measurement reporting component 635 to measure various network conditions. The measurement report component 635 can do this and transmit a WLAN measurement report 652 to the eNodeB node 605-a. At 710, the WWAN data stream suspension module 644 instructs the WWAN radio 620 to resume the LTE data stream based at least in part on the WLAN measurement report 652.

[0103] Referring to FIG. 8, a call flow 800 illustrates the communication between the UE 615, the eNodeB node 605-a and the WLAN AP 605-b of FIG. 6 according to the second aspect for managing the RLF recovery of the UE. Specifically, in this second aspect, the device and method of the present disclosure stop LTE data flow and WLAN data flow when RLF is detected. The actions of call flow 800 are executed by UE 615, including

Including RLF component 630, measurement report component 635, WWAN radio 620, WLAN radio 625, and RLF data flow determination component 640. According to the second aspect, the RLF data flow determining component 640 includes a WWAN data flow suspension module 644, a WLAN data flow suspension module 645, and a network configuration module 642.

[0104] At 801, the RLF component 630 of the UE 615 detects RLF according to the current 3GPP standard. At 802, the WWAN data stream suspension module 644 suspends all LTE data transmitted over the WWAN radio link 661 via the WWAN radio 620 to the eNodeB node 605-a. Although not shown, the RLF data flow determination component 640 provides a report instruction 653 to the measurement report component 635 so that the measurement report component 635 can delete all WLAN measurement report entries in any existing measurement report. At 803, the WLAN data stream suspension module 645 suspends the WLAN data stream transmitted on the WLAN radio link 662 via the WLAN radio 625 to the WLAN AP 605-b. In 804, the RLF component 630 performs the cell reselection procedure according to the current 3GPP standard, and re-establishes the UE by sending an RRC connection re-establishment request message in 805, receiving an RRC connection re-establishment message in 806, and sending an RRC connection re-establishment complete message in 807 The connection between 615 and eNodeB node 605-a. At 808, the UE 615 and the eNodeB node 605-a perform the RRC connection reconfiguration procedure for LTE according to the current 3GPP standard.

[0105] At 809, the network configuration module 642 may be configured to detect that the RLF component 630 is performing an RRC connection reconfiguration procedure and notify the WWAN data stream suspension module 644 to resume the LTE data stream. The network configuration module 642 may also be configured to provide report instructions 653 to the measurement reporting component 635 to instruct the measurement reporting component 635 to measure various network conditions. At 810, once the measurement reporting component 635 determines that the quality of the WLAN radio link 662 is greater than a threshold (eg, a configurable and/or static threshold determined at the UE 615 or provided by the network to the UE 615), this may be referred to as a trigger Event, at 811, the measurement report component 635 transmits a WLAN measurement report 652 to the eNodeB node 605-a. At 812, the RLF data flow configuration component 610 of the eNodeB node 605-a determines, based at least in part on the WLAN measurement report 652, whether the WLAN radio link 662 is acceptable to restore the WLAN data flow. This may be referred to as an interworking decision because the eNodeB node 605-a determines whether the UE 615 can perform interworking, for example, dual connectivity between WLAN and LTE. At 813, the UE 615 and the eNodeB node 605-a perform an RRC connection reconfiguration procedure for WLAN according to the current 3GPP standard. The network configuration module 642 receives the eNodeB node 605-a indicates the interworking decision and thereby instructs the WLAN data flow suspension module 645 to resume the WLAN data flow at 814. In response, the WLAN data stream suspension module 645 may provide a resume instruction 655 to the WLAN radio 625 to resume the WLAN data stream on the WLAN radio link 662.

[0106] Referring to FIG. 9, a call flow 900 illustrates the communication between the UE 615, the eNodeB node 605-a and the WLAN AP 605-b of FIG. 6 according to the third aspect for managing the RLF recovery of the UE. Specifically, in this third aspect, the device and method of the present disclosure stop LTE data flow and WLAN data flow when RLF is detected. The actions of the call flow 900 are performed by the UE 615, and include an RLF component 630, a measurement report component 635, a WWAN radio 620, a WLAN radio 625, and an RLF data flow determination component 640. According to the third aspect, the RLF data flow determining component 640 includes a WWAN data flow suspension module 644, a WLAN data flow suspension module 645, and a network configuration module 642. The third aspect described with respect to the call flow 900 is similar to the second aspect of FIG. 8 except for the timing of when to generate the WLAN measurement report 652 and transmit the WLAN measurement report 652 to the eNodeB node 605-a.

[0107] In 901, the RLF component 630 of the UE 615 detects RLF according to the current 3GPP standard. At 902, the WWAN data stream suspension module 644 suspends all LTE data transmitted over the WWAN radio link 661 via the WWAN radio 620 to the eNodeB node 605-a. In this aspect (not shown), the RLF data flow determination component 640 instructs the measurement reporting component 635 via the reporting instructions 653 to maintain the WLAN measurement reporting entity in any existing measurement reports. At 903, the WLAN data stream suspension module 645 suspends the WLAN data stream transmitted on the WLAN radio link 662 via the WLAN radio 625 to the WLAN AP 605-b. At 904, the RLF component 630 executes the cell reselection procedure according to the current 3GPP standard, and sends the RRC connection at 905

Receive the reestablishment request message, receive the RRC connection reestablishment message at 906, and send the RRC connection reestablishment complete message at 907 to reestablish the connection between the UE 615 and the eNodeB node 605-a.

[0108] In this aspect, the network configuration module 642 may be configured to provide the measurement report component 635 with a report instruction 653 to instruct the measurement report component 635 to measure each item when it is determined by the network configuration module 642 that the RLF component 630 is undergoing an RRC connection re-establishment process. Kind of network conditions. The measurement report component 635 may be configured to generate a WLAN measurement report 652 and transmit the WLAN measurement report 652 at 907 as part of the RRC connection reestablishment complete message. On the other hand, the maintained existing measurement report can be transmitted as part of the RRC connection re-establishment complete message. At 908, the eNodeB node 605-a has received the WLAN measurement report 652, and based at least in part on the WLAN measurement report 652, the RLF data flow configuration component 610 may be configured to make interworking decisions, such as determining whether to restore the WLAN data at the UE 615 flow. If the interworking decision is to restore the WLAN data flow, then in 909, the UE 615 and the eNodeB node 605-a perform the RRC connection reconfiguration procedure for WLAN and LTE according to the current 3GPP standard. If the interworking decision is not to resume the WLAN data flow (not shown), the RRC connection reconfiguration procedure at 909 can be used only for LTE. The network configuration module 642 may be configured to detect that the RLF component 630 is performing an RRC connection The reconfiguration procedure and the WWAN data stream suspension module 644 are notified to resume the LTE data stream by sending a suspend/resume indication 655 to the WWAN radio 620 and resume the LTE data stream on the WWAN radio link 661 at 910. At 911 and based on the interworking decision at 908, the network configuration module can be similarly configured to notify the WLAN data stream suspension module 645 to resume by sending a resume indication 656 to the WLAN radio 625 to resume the WLAN data stream on the WLAN radio link 662 WLAN data stream. 10, the call flow 1000 illustrates the communication between the UE 615, the eNodeB node 605-a and the WLAN AP 605-b of FIG. 6 according to the fourth aspect for managing the RLF of the UE. Specifically, in this fourth aspect, the apparatus and method of the present disclosure stop LTE data flow and optionally stop WLAN data flow when RLF is detected. The actions of the call flow 1000 are executed by the UE 615, and include an RLF component 630, a measurement report component 635, a WWAN radio 620, a WLAN radio 625, and an RLF data flow determination component 640. According to the fourth aspect, the RLF data flow determination component 640 includes a WWAN data flow suspension module 644, a WLAN data flow suspension module 645, and a decision module 641.

[0110] At 1001, the RLF component 630 of the UE 615 detects RLF according to the current 3GPP standard. At 1002, the WWAN data stream suspension module 644 suspends all LTE data transmitted on the WWAN radio link 661 via the WWAN radio 620 to the eNodeB node 605-a. At 1003 (and similar to the first aspect of the call flow 700), the decision module 641 determines whether to suspend the WLAN data flow transmitted via the WLAN radio 625 on the WLAN radio link 662 to the WLAN AP 605-b. If the decision module 641 determines that the WLAN data stream is to be suspended (this is shown at 1003a in the example of the call flow 1000), the WLAN data stream is suspended. If the decision module 641 determines not to suspend the WLAN data flow (shown), the WLAN data flow is maintained during the RLF process (or resumed if the WLAN data flow is temporarily suspended at the time of RLF detection). At 1004, the RLF component 630 performs the cell reselection procedure according to the current 3GPP standard, and reestablishes the UE by sending an RRC connection reestablishment request message at 1005, receiving an RRC connection reestablishment message at 1006, and sending an RRC connection reestablishment complete message at 1007. The connection between 615 and eNodeB node 605-a.

[0111] The decision module 641 may be configured to provide a report instruction 653 to the measurement reporting component 635 to instruct the measurement reporting component 635 to measure various network conditions when the network configuration module 642 determines that the RLF component 630 is undergoing an RRC connection re-establishment process. The measurement report component 635 may be configured to generate a WLAN measurement report 652 and transmit the WLAN measurement report 652 at 1007 as part of the RRC connection re-establishment complete message. At 1008, the eNodeB node 605-a has received the WLAN measurement report 652, and based at least in part on the WLAN measurement report 652, the RLF data flow configuration component 610 may be configured to make an interworking decision, such as determining whether to restore the WLAN data at the UE 615 flow. More specifically, the RLF data flow configuration component 610 at the eNodeB node 605-a may be configured to determine whether to maintain or override the decision made by the UE 615 regarding whether to resume the WLAN data flow.

Of ok. If the interworking decision is to restore the WLAN data flow, then at 1009, the UE 615 and the eNodeB node 605-a execute the RRC connection reconfiguration procedure for WLAN and LTE according to the current 3GPP standard. If the interworking decision is not to restore the WLAN data stream (not shown), the RRC connection reconfiguration procedure at 1009 can be used only for LTE.

[0112] The network configuration module 642 may be configured to detect that the RLF component 630 is performing an RRC connection reconfiguration procedure and, at 1010, notify the WWAN data by sending a recovery indication 655 to the WWAN radio 620 and restoring the LTE data stream on the WWAN radio link 661 The stream suspension module 644 resumes the LTE data stream. At 1011, the network configuration module 642 may be similarly configured to notify the WLAN data stream suspension module 645 to resume WLAN data by sending a resume indication 656 to the WLAN radio 625 to resume the WLAN data stream on the WLAN radio link 662 based on the interworking decision 1008 flow.

11, the call flow 1100 illustrates the communication between the UE 615, the eNodeB node 605-a and the WLAN AP 605-b of FIG. 6 according to the fifth aspect for managing the RLF of the UE. Specifically, in this fifth aspect, the apparatus and method of the present disclosure stop LTE data flow when RLF is detected. The actions of the call flow 1100 are executed by the UE 615, and include an RLF component 630, a measurement report component 635, a WWAN radio 620, a WLAN radio 625, and an RLF data flow determination component 640. According to the fifth aspect, the RLF data flow determining component 640 includes a WWAN data flow suspension module 644, a WLAN data flow suspension module 645, and a network configuration module 642.

[0114] At 1101, the RLF data flow configuration component 610 of the eNodeB node 605-a transmits an RRC connection reconfiguration message (for example, configuration 654) to the UE 615 to instruct the UE 615 on whether to suspend or maintain the WLAN data flow during RLF processing . In the example of call flow 1100, the RRC connection reconfiguration message sent at 1101 instructs UE 615 to maintain the WLAN data flow during RLF processing. In another example (not shown), the RRC connection reconfiguration message sent at 1101 may instruct the UE 615 to suspend the WLAN data flow during RLF processing.

[0115] At 1102, the RLF component 630 of the UE 615 detects RLF according to the current 3GPP standard. At 1103, the WWAN data stream suspension module 644 suspends all LTE data streams transmitted over the WWAN radio link 661 via the WWAN radio 620 to the eNodeB node 605-a. At 1104, the RLF component 630 performs the cell reselection procedure according to the current 3GPP standard, and reestablishes the UE by sending an RRC connection reestablishment request message at 1105, receiving an RRC connection reestablishment message at 1106, and sending an RRC connection reestablishment complete message at 1107. The connection between 615 and eNodeB node 605-a. At 1108, the UE 615 and the eNodeB node 605-a perform the RRC connection reconfiguration procedure for LTE according to the current 3GPP standard. At 1109, the network configuration module 642 may be configured to detect that the RLF component 630 is performing an RRC connection reconfiguration procedure and notify the WWAN data flow suspension module 644 to resume the LTE data flow. In the aspect (not shown) in which the eNodeB node 605-a configures the UE 615 to suspend the WLAN data flow during RLF processing via the RRC connection reconfiguration message at 1101 (not shown), the network configuration module 642 may notify the WLAN data flow suspension module 645 resumes WLAN data flow.

12, the call flow 1200 illustrates the communication between the UE 615, the eNodeB node 605-a and the WLAN AP 605-b of FIG. 6 according to the sixth aspect for managing the RLF of the UE. Specifically, in this sixth aspect, the device and method of the present disclosure can optionally reroute the LTE data stream when RLF is detected. The actions of the call flow 1200 are executed by the UE 615, and include an RLF component 630, a measurement report component 635, a WWAN radio 620, a WLAN radio 625, and an RLF data flow determination component 640. According to the sixth aspect, the RLF data flow determining component 640 includes a WWAN data flow suspension module 644, a WLAN data flow suspension module 645, and a rerouting module 643.

[0117] At 1201, the RLF component 630 detects RLF according to the current 3GPP standard, and provides an RLF indication 651 to the RLF data flow determination component 640. At 1202, the LTE data stream suspension module may be configured to send a suspension indication 655 to the WWAN radio 620. In addition, the rerouting module 643 reroutes the signaling radio bearer (for example, SRB1) to the WLAN AP 605-b via the WLAN radio 625 and further reroutes (for example, offloads) all LTE data streams until the LTE connection can be in the UE

Re-establish between 615 and eNodeB node 605-a. At 1203, as a result of detecting RLF, the RLF component 630 performs cell reselection processing according to the current 3GPP standard. At 1204, the RLF data flow determination component 640 instructs the measurement report component 635 via the report instruction 653 to generate a WLAN measurement report 652 and transmit the WLAN measurement report 652 to the WLAN AP 605-b via the WLAN radio 625.

[0118] At 1205, the WWAN forwarding component 612 of the WLAN AP 605-b forwards the WLAN measurement report 652 to the eNodeB node 605-a via the backhaul. At 1206, the RLF data flow configuration component 610 of the eNodeB node 605-a makes a decision as to whether the LTE data flow should be rerouted via the WLAN AP 605-b until the RLF recovery process is completed and LTE communication is reestablished (for example, until the LTE data flow can be restored) The intercommunication decision. At 1207, the eNodeB node 605-a transmits its interworking decision to the WLAN AP 605-b. In the example of the call flow 1200, the eNodeB node 605-a determines to continue to reroute the LTE data flow via the WLAN AP 605-b. At 1208, the WLAN AP 605-b forwards the WLAN interworking command (eg, interworking decision) to the UE 615. At 1209, the rerouting module 643 notifies the WWAN data stream suspension module 644 and the WLAN data stream suspension module 645 to resume the LTE data stream via the WLAN radio link 662 and continue the WLAN data stream, respectively. Both the LTE data stream and the WLAN data stream are transmitted on the WLAN radio link 662 via the WLAN radio 625.

[0119] At the same time, the RLF component 630 reestablishes the connection between the UE 615 and the eNodeB node 605-a by sending an RRC connection reestablishment request message at 1210, receiving an RRC connection reestablishment message at 1211, and sending an RRC connection reestablishment complete message at 1212. The rerouting module 643 may be configured to provide a report instruction 653 to the measurement reporting component 635 to instruct the measurement reporting component 635 to measure various network conditions when it is determined by the network configuration module 642 that the RLF component 630 is undergoing an RRC connection re-establishment process. The measurement report component 635 may be configured to generate an LTE and/or WLAN measurement report 652 and transmit the WLAN measurement report at 1212 as part of the RRC connection re-establishment complete message.

[0120] Once the re-establishment procedure is completed, the UE 615 and the eNodeB node 605-a are in communication via LTE again and SRB1 is re-established. Thus, at 1213, the eNodeB node 605-a determines whether to reroute the LTE data stream currently being transmitted on the WLAN radio link 662 back (eg, fall back to) the WWAN radio link 661. Thus, the RLF data flow configuration component 610 makes an interworking decision based at least in part on the WLAN measurement report 652. If the interworking decision is to resume the LTE data stream, then at 1214, the UE 615 and the eNodeB node 605-a perform the RRC connection reconfiguration procedure for LTE according to the current 3GPP standard. If the interworking decision is not to restore the LTE data stream (not shown), the RRC connection reconfiguration procedure at 1214 may not be performed at this time. At 1215, the rerouting module 643 may notify the WWAN data stream suspension module 644 to resume the LTE data stream by sending a resume indication 655 to the WWAN radio 620 and resume the LTE data stream on the WWAN radio link 661.

[0121] Referring to FIG. 13, a method for being used by user equipment (such as, for example, UE 120 in FIG. 1, UE 215 in FIG. 2, UE 320 in FIG. 3, UE 415 in FIG. 4, UE 515 in FIGS. 5A and 5B , And one of UE 615 in Figures 6-12) Method 1300 for managing radio link failure recovery. For simplicity, aspects of the method 1300 are described as being performed by the UE 615 in communication with the eNodeB node 605-a and/or the WLAN AP 605-b, which is generally illustrated in FIG. 6. More specifically, aspects of the method 1300 may be performed by, for example, an RLF component 630, a measurement report component 635, an RLF data flow determination component 640, a WWAN radio 620, and/or a WLAN radio 625.

[0122] At 1305, method 1300 includes establishing communication with a first radio access technology (RAT) and a second RAT. For example, UE 615 and/or WWAN radio 620 and WLAN radio 625 may be configured to establish communication with eNodeB node 605-a via a first RAT of WWAN (eg, LTE) and a second RAT via WLAN (eg, Wi -Fi) Establish communication with WLAN AP 605-b.

[0123] At 1310, method 1300 includes transmitting at least one data stream on a first RAT and transmitting at least one data stream on a second RAT. For example, UE 615 and/or WWAN radio 620 communicates to eNodeB node on WWAN radio link 661

605-a transmits LTE data streams and/or transmits WLAN data streams on WLAN radio link 662 to WLAN AP 605-b. In one aspect, the WWAN (eg, LTE) data flow may be of or associated with a bearer, a traffic flow template (TFT), a transmission control protocol (TCP) connection, and/or a quality of service (QoS) category.

[0124] At 1315, the method 1300 includes detecting a radio link failure (RLF) between the user equipment and the first RAT. For example, the UE 615 and/or the RLF component 630 may be configured to detect RLF according to the procedures described in the 3GPP standard.

[0125] At 1320, the method 1300 includes determining whether to maintain the at least one data stream on the second RAT when the RLF is detected. For example, the RLF data flow determination component 640 may be configured to receive the RLF indication 651 from the RLF component 630 upon RLF detection and in response to determine whether to maintain (eg, suspend or not suspend) the WLAN data flow during the RLF recovery process.

[0126] According to the second and third aspects, and optionally in the first, fourth, and fifth aspects, the method 1300 may include determining to suspend one or more data streams on the second RAT (e.g., WLAN Data stream) and suspend the transmission of one or more data streams (for example, WLAN data stream) on the second RAT. In some aspects, method 1300 may include detecting recovery from RLF and resuming transmission of one or more data streams (eg, WLAN data streams) on the second RAT. In some aspects, method 1300 may include detecting recovery from RLF and resuming transmission of one or more suspended data streams (eg, LTE data streams) on the first RAT. In some aspects, the method 1300 may include detecting recovery from the RLF, receiving the configuration 654 from the first RAT (e.g., eNodeB node 605-a), and resuming one or more suspended data on the second RAT (e.g., WLAN) Transmission of a data stream (for example, an LTE data stream), and transmission of information related to a second RAT (for example, WLAN) to a first RAT (for example, LTE). In this case, the configuration may be received from the first RAT in response to transmitting the information. This information can be a measurement report for LTE and/or WLAN. This information can be indications (one indication per WLAN data stream), these indications indicate whether the UE suspends the second RAT Transmission of specific data stream (for example, WLAN data stream) on RLF. This information may be an indication as to whether the UE will resume the transmission of each data stream on the first RAT (for example, LTE) or the second RAT (for example, WLAN) (one indication per LTE data stream and each WLAN data stream An instruction).

[0127] According to the sixth aspect, and optionally in the first, fourth, and fifth aspects, the method 1300 may include determining to maintain transmission of the at least one data stream (eg, WLAN data stream) on the second RAT . In some aspects, the determination is based on the network configuration (eg, configuration 654) received at the UE, access network discovery and selection function (ANDSF) policies (eg, flags), quality of service (QoS) parameters, and/or UEs At least one of the implementations.

[0128] According to the sixth aspect, the method 1300 may include transmitting control signaling (eg, LTE RRC signaling, NAS signaling, etc.) on a second RAT (eg, WLAN) during RLF.

[0129] Referring to FIG. 14, a method 1400 for managing radio link failure recovery at a user equipment may be executed by a first eNodeB node, and the first eNodeB node may be, for example, the eNodeB node 110 in FIG. 1 or the eNodeB node in FIG. 2. One of the eNodeB node 205, the eNodeB node 310 of FIG. 3, the eNodeB node 405-a of FIG. 4, the eNodeB node 505-a of FIGS. 5A and 5B, and the eNodeB node 605-a of FIG. 612. For the sake of simplicity, aspects of the method 1400 are described as being performed by the eNodeB node 605-a in communication with the UE 615 and/or the WLAN AP 605-b, which is generally illustrated in FIG. 6. In the example of the method 1400, the eNodeB node 605-a configures the UE 615 to handle the WLAN data flow during RLF processing.

[0130] At 1405, method 1400 includes establishing a first communication connection with user equipment via a first radio access technology (RAT). For example, the eNodeB node 605-a is configured to establish a first communication connection with the UE 615 on LTE. In one aspect, the establishment of the first communication connection may be the result of the UE 615 moving from the idle state to the connected state or the result of the UE 615 switching from another eNodeB node to the eNodeB node 605-a.

[0131] At 1410, the method 1400 includes receiving an indication that a second communication connection is established with the user equipment via a second RAT, wherein the second communication connection transmits at least one data stream. For example, the eNodeB node 605-a is configured to receive information from the UE 615.

The UE 615 is also in communication with the WLAN AP 605-b and the UE 615 is transmitting an indication of at least one WLAN data flow to the WLAN AP 605-b on the WLAN.

[0132] At 1415, the method 1400 includes receiving a radio link failure (RLF) recovery indication for the first communication connection from the user equipment after the radio link failure of the first communication connection. For example, the eNodeB node 605-a may be configured to receive information from the UE 615 that the UE 615 is recovering from RLF so that the UE 615 is in communication with the eNodeB node 605-a via LTE and the UE 615 is in communication with the WLAN AP 605-b via WLAN. Instructions.

[0133] At 1420, the method 1400 includes determining whether the at least one data stream can be maintained on the second communication connection via the second RAT during a radio link failure. For example, the RLF data flow configuration component 610 of the eNodeB node 605-a may be configured to determine whether the UE 615 should maintain or suspend the WLAN data flow during RLF.

[0134] At 1425, the method 1400 includes indicating to the user equipment whether to maintain the transmission of the at least one data stream on a second communication connection via the second RAT on a per-data stream basis. For example, the eNodeB node 605-a may be configured (eg, via configuration 654) to indicate to the UE 615 whether to suspend or maintain the WLAN data flow on a per data flow basis. The eNodeB node 605-a may provide this indication to the UE 615 via a configuration message (for example, an RRC message) or a data message sent by the eNodeB node 605-a to the UE 615.

[0135] Referring to FIG. 15, a method 1500 for managing radio link failure recovery at a user equipment may be executed by a second eNodeB node, and the second eNodeB node may be, for example, the eNodeB node 110 of FIG. 1 or the eNodeB node 110 of FIG. 2. One of the eNodeB node 205, the eNodeB node 310 of FIG. 3, the eNodeB node 405-a of FIG. 4, the eNodeB node 505-a of FIGS. 5A and 5B, and the eNodeB node 605-a of FIG. 612. For simplicity, aspects of the method 1500 are described as being performed by the eNodeB node 605-a in communication with the UE 615 and/or the WLAN AP 605-b, which is generally illustrated in FIG. 6. In the example of the method 1500, the eNodeB node 605-a handles the UE 615 RLF recovery. The first eNodeB node described as performing aspects of method 1400 may or may not be the same as the second eNodeB node described as performing aspects of method 1500.

[0136] At 1505, the method 1500 includes receiving a radio link failure recovery indication for the first communication connection from the user equipment. For example, the eNodeB node 605-a receives an indication that the UE 615 is recovering from the LTE RLF.

[0137] At 1510, the method 1500 includes receiving an indication that a second communication connection is established with the user equipment via a second RAT, where the second communication connection is associated with at least one data stream. For example, the eNodeB node 605-a receives an indication from the UE 615 that the UE 615 is in communication with the WLAN AP 605-b on the WLAN radio link 662 and the WLAN data stream is being sent by the UE 615 to the WLAN AP 605-b.

[0138] At 1515, the method 1500 includes determining whether the at least one data stream can be restored on the second communication connection via the second RAT after the radio link failure is restored. For example, the RLF data flow configuration component 610 of the eNodeB node 605-a may be configured to determine whether the WLAN data flow can be resumed on the WLAN after the UE 615 recovers from the RLF.

[0139] At 1520, the method 1500 includes indicating to the user equipment whether to resume transmission of the at least one data stream on the second communication connection via the second RAT. For example, the eNodeB node 605-a may be configured (eg, via configuration 654) to indicate to the UE 615 whether to resume the transmission of the WLAN data stream on the WLAN.

[0140] According to the first, second, third, fourth, and sixth aspects, the method 1500 may optionally include receiving at least one measurement report related to a second RAT (eg, WLAN), and based at least in part on the At least one measurement report is used to determine whether the UE 615 can resume the transmission of the at least one data stream (for example, a WLAN data stream) on the second RAT.

[0141] According to some aspects, the method 1500 may optionally include receiving multiple indications, each of the multiple indications indicating whether the UE 615 suspends the at least one data stream on the second RAT during RLF (eg, WLAN data stream) in the transmission of a specific data stream, wherein each of the multiple indications is associated with the at least one data on the second RAT

A specific data stream in the stream (for example, a WLAN data stream) is associated. In addition, the method 1500 may optionally include receiving at least one measurement report (for example, a WLAN measurement report) related to the second RAT from the UE 615, detecting that the first communication connection (for example, LTE) has been reestablished, and based on the at least one measurement report The measurement report is used to determine whether to resume transmission on the second RAT (eg, WLAN). In one example, the measurement report can be transmitted as part of the RRC connection re-establishment message.

[0142] According to some aspects, the method 1500 can optionally include receiving a further indication that the transmission of at least one data stream (e.g., LTE data stream) on the second RAT has been maintained during RLF, and detecting the first communication connection (e.g., , LTE) has been rebuilt, and it is determined whether to transmit at least one data stream (for example, LTE data stream) maintained on the second RAT (for example, WLAN) during RLF on the first RAT (for example, LTE). In an example, the further indication may be a measurement report related to the second RAT (for example, a WLAN measurement report), which may be transmitted as part of an RRC connection re-establishment message, for example.

[0143] Referring to FIG. 16, there is shown an example of a hardware implementation of an apparatus 1600 employing a processing system 1614 configured for distributing aspects of user equipment processing capabilities among multiple access nodes as described herein. In this example, the processing system 1614 may be implemented to have a bus architecture generally represented by the bus 1602. Depending on the specific application and overall design constraints of the processing system 1614, the bus 1602 may include any number of interconnecting buses and bridges. The bus 1602 links together various circuits including one or more processors (represented generally by the processor 1604) and a computer-readable medium (represented generally by the computer-readable medium 1606). In the aspect where the apparatus 1600 adopting the processing system 1614 is, for example, the eNodeB node 605-a, the bus 1602 also links the RLF data flow configuration component 610. In the aspect where the device 1600 adopting the processing system 1614 is, for example, a WLAN AP 605-b, the bus 1602 also links the WWAN forwarding component 612. In the aspect where the device 1600 adopting the processing system 1614 is, for example, the UE 615, the bus 1602 also links the RLF component 630, the measurement report component 635, the RLF data flow determination component 640, the WWAN radio 620, and the WLNA radio 625. It should be noted that sending and receiving The machine 1610 may be part of the WWAN radio 620 and WLAN radio 625, or vice versa. The bus 1602 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. It should be understood that any aspect of FIG. 16 can be implemented by hardware, software, or a combination thereof. In one example, any operation or function configured to be supported by the apparatus of FIG. 16 may be implemented using the processor 1604 and/or the computer-readable medium 1606.

[0144] The bus interface 1608 provides an interface between the bus 1602 and the transceiver 1610. The transceiver 1610 provides a means for communicating with various other devices through a transmission medium. Depending on the nature of the device, a user interface 1612 (eg, keypad, display, speaker, microphone, joystick) may also be provided.

[0145] The processor 1604 is responsible for managing the bus 1602 and general processing, including the execution of software stored on the computer-readable medium 1606. The software, when executed by the processor 1604, causes the processing system 1614 to perform the various functions described herein related to allocating user equipment processing capabilities among multiple access nodes for any particular device. The computer-readable medium 1606 may also be used to store data that is manipulated by the processor 1604 when executing software.

[0146] As used in this application, the terms "component", "module", "system" and similar terms are intended to include computer-related entities such as but not limited to hardware, firmware, a combination of hardware and software, software, Or the software in execution. For example, a component may be, but is not limited to, a process, a processor, an object, an executable, a thread of execution, a program, and/or a computer running on a processor. As an illustration, both the application running on the computing device and the computing device can be components. One or more components may reside in processes and/or threads of execution, and the components may be localized on one computer and/or distributed between two or more computers. In addition, these components can be executed from various computer readable media having various data structures stored thereon. These components can communicate through local and/or remote processes, such as based on having one or more data points.

Group of signals to communicate, such as data packets from a component that interacts with the local system, another component in a distributed system through the signal, and/or a component that interacts with other systems across a network such as the Internet .

[0147] In addition, this document describes various aspects in conjunction with a terminal, and the terminal may be a wired terminal or a wireless terminal. A terminal may also be referred to as a system, equipment, subscriber unit, subscriber station, mobile station, mobile station, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, communication device, user agent, user equipment, or User Equipment (UE). The wireless terminal can be a cellular phone, a satellite phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless connection capability, a computing device, or Other processing equipment connected to the wireless modem. In addition, this article describes various aspects in conjunction with base stations. A base station can be used to communicate with wireless terminals, and can also be called an access point, a Node B, or some other terminology.

[0148] Furthermore, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, the phrase "X adopts A or B" is intended to mean any natural compatible arrangement. That is, the phrase "X adopts A or B" satisfies any of the following examples: X adopts A; X adopts B; or X adopts both A and B. In addition, the articles "a" and "some" used in this application and the appended claims should generally be understood to mean "one or more" unless otherwise stated or it is clear from the context that it refers to the singular form. .

[0149] The techniques described herein can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SCFDMA, and other systems. The terms "system" and "network" are often used interchangeably. The CDMA system can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes Wideband CDMA (W-CDMA) and other CDMA variants. In addition, cdma2000 covers IS-2000, IS-95 and IS-856 standards. The TDMA system can implement radio technologies such as the Global System for Mobile Communications (GSM). The OFDMA system can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. It uses OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE and GSM It is described in documents from an organization named "3rd Generation Partnership Project (3GPP). In addition, cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2 (3GPP2). In addition, such wireless communication systems may additionally include peer-to-peer (e.g., mobile-to-mobile) self-organization (ad hoc) that often use unpaired unlicensed spectrum, 802.xx wireless LAN, Bluetooth, and any other short-range or long-range wireless communication technologies. )network system.

[0150] Various aspects or features will be presented in the form of a system that may include several devices, components, modules, and the like. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and/or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. A combination of these methods can also be used.

[0151] The various illustrative logics, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein can be designed to perform general-purpose processors, digital signal processors (DSPs), and application-specific integrated circuits ( ASIC), field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration. In addition, at least one processor may include one or more modules that can function to perform one or more steps and/or actions described above.

[0152] In addition, the steps and/or actions of the method or algorithm described in connection with the aspects disclosed herein may be directly implemented in hardware, in a software module executed by a processor, or in a combination of the two. Software modules can reside in RAM

Memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. Furthermore, in some aspects, the processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in the user terminal. In the alternative, the processor and the storage medium may reside as discrete components in the user terminal. In addition, in some aspects, the steps and/or actions of the method or algorithm can reside on a machine-readable medium and/or computer that can be incorporated into a computer program product as one of codes and/or instructions or any combination or collection thereof. On readable media.

[0153] In one or more aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function can be stored as one or more instructions or codes on a computer-readable medium or transmitted through it. Computer-readable media includes both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or can be used to carry or store instructions or data in the form of desired structures. Program code and any other medium that can be accessed by a computer. And, any connection can also be referred to as a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, radio, and microwave , The coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. Disks and discs as used in this article include compact discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy discs, and blue discs. Optical discs, in which disks often reproduce data in a magnetic manner, and discs often use lasers to reproduce data in an optical manner. Combinations of the above should also be included in the scope of computer-readable media.

[0154] Although the foregoing disclosure discusses illustrative aspects and/or embodiments, it should be noted that various changes and modifications can be made therein without departing from the description of these aspects and/or embodiments. The scope defined by the appended claims. In addition, although elements of the described aspects and/or embodiments may be described or claimed in a singular number, plural numbers are also conceived, unless it is explicitly stated that they are limited to the singular number. In addition, all or part of any aspect and/or embodiment may be used in combination with all or part of any other aspect and/or embodiment, unless otherwise stated.