Techniques for managing radio link failure recovery for user equipment connected to wwan and wlan
Abstract
Problem to be solved.To provide a technique for managing wireless link failure recovery for WWAN and a user device (UE) connected to WLAN. Communication is established using a first radio access technology (RAT) and a second RAT. At least one data flow is transmitted via each of the first RAT and the second RAT. Whether at least one data flow through the second RAT should be maintained when a radio link failure (RLF) is detected in the UE and / or at least one data flow through the second RAT during RLF recovery. A decision is made regarding whether to resume. The decision is made in the UE, in the network entity communicating with the UE, or in some combination thereof. [Selection diagram] Fig. 13

Term
10.8 yearsto projected expiry
Projected expiry 28 July 2037, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
38 claims: 14 independent, 24 dependent
- 1無線リンク障害回復を管理するための方法であって、 第1の無線アクセス技術および第2の無線アクセス技術を用いて通信を確立することと、 前記第1の無線アクセス技術を介して少なくとも1つのデータフローを、および前記第2の無線アクセス技術を介して少なくとも1つのデータフローを送信することと、 ユーザ機器と前記第1の無線アクセス技術との間の無線リンク障害を検出することと、 前記無線リンク障害が検出されたとき、前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローを維持すべきかどうかを決定することと を備える、方法。
- 2前記第1の無線アクセス技術がワイヤレスワイドエリアネットワーク(WWAN)に関連し、前記少なくとも1つのデータフローが、ベアラ、トラフィックフローテンプレート(TFT)、伝送制御プロトコル(TCP)接続、およびサービス品質(QoS)クラスのうちの少なくとも1つである、請求項1に記載の方法。
- 3前記WWANがロングタームエボリューション(LTE)ネットワークまたはユニバーサルモバイルテレコミュニケーションシステム(UMTS)である、請求項1に記載の方法。
- 4前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローを維持すべきかどうかを決定することが、前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの1つまたは複数のデータフローの送信を中断することを決定することを備え、前記第2の無線アクセス技術を介した前記1つまたは複数のデータフローの前記送信を中断することをさらに備える、請求項1に記載の方法。
- 5前記無線リンク障害からの回復を検出することと、 前記回復を検出したことに応答して、前記第2の無線アクセス技術を介した前記1つまたは複数の中断されたデータフローの前記送信を再開することと をさらに備える、請求項4に記載の方法。
- 6前記無線リンク障害からの回復を検出することと、 前記回復を検出したことに応答して、前記第1の無線アクセス技術を介した前記1つまたは複数の中断されたデータフローの前記送信を再開することと をさらに備える、請求項4に記載の方法。
- 7前記無線リンク障害からの回復を検出することと、 前記第1の無線アクセス技術から前記回復に関連する構成を受信することと、 前記構成に基づいて、前記第2の無線アクセス技術を介した前記1つまたは複数の中断されたデータフローの前記送信を再開することと をさらに備える、請求項4に記載の方法。
- 8前記第2の無線技術に関係する情報を前記第1の無線アクセス技術に送信することをさらに備え、 ここにおいて、前記第1の無線アクセス技術から前記構成を受信することが、前記第2の無線技術に関係する前記情報を送信することに応答する、請求項7に記載の方法。
- 9前記情報が測定報告を備える、請求項8に記載の方法。
- 10前記情報は複数の指示を備え、前記指示の各々は、前記ユーザ機器が前記無線リンク障害中に前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの特定の1つのための前記送信を中断したかどうかを示し、ここにおいて、前記複数の指示の各々が、前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの特定の1つに関連する、請求項8に記載の方法。
- 11前記情報は複数の指示を備え、前記指示の各々は、前記ユーザ機器が前記第1の無線アクセス技術または前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの特定の1つのための前記送信を再開すべきかどうかを示し、ここにおいて、前記複数の指示の各々が、前記第1の無線アクセス技術を介した前記少なくとも1つのデータフローの特定の1つに関連する、請求項8に記載の方法。
- 12前記決定することが、前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの前記送信を維持することを決定することを備える、請求項1に記載の方法。
- 13前記決定することが、前記ユーザ機器において受信されたネットワーク構成、アクセスネットワーク発見および選択機能(ANDSF)ポリシー、サービス品質(QoS)パラメータ、または前記ユーザ機器の実装形態のうちの少なくとも1つに基づく、請求項1に記載の方法。
- 14前記無線リンク障害中に前記第2の無線アクセス技術を介して制御シグナリングを送信することをさらに備える、請求項1に記載の方法。
- 15前記制御シグナリングが無線リソース制御シグナリングまたは非アクセス層シグナリングの一方または両方を備える、請求項14に記載の方法。
- 16前記無線リンク障害中に前記第2の無線アクセス技術を介して制御シグナリングを受信することをさらに備える、請求項1に記載の方法。
- 17前記制御シグナリングが無線リソース制御シグナリングまたは非アクセス層シグナリングの一方または両方を備える、請求項16に記載の方法。
- 18コンピュータ実行可能コードを記憶する非一時的コンピュータ可読媒体であって、 少なくとも1つのコンピュータに、第1の無線アクセス技術および第2の無線アクセス技術を用いて通信を確立させるためのコードと、 前記少なくとも1つのコンピュータに、前記第1の無線アクセス技術を介して少なくとも1つのデータフローを、および前記第2の無線アクセス技術を介して少なくとも1つのデータフローを送信させるためのコードと、 前記少なくとも1つのコンピュータに、ユーザ機器と前記第1の無線アクセス技術との間の無線リンク障害を検出させるためのコードと、 前記少なくとも1つのコンピュータに、前記無線リンク障害が検出されたとき、前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローを維持すべきかどうかを決定させるためのコードと を備える、非一時的コンピュータ可読媒体。
- 19無線リンク障害回復を管理するための装置であって、 第1の無線アクセス技術および第2の無線アクセス技術を用いて通信を確立するための手段と、 前記第1の無線アクセス技術を介して少なくとも1つのデータフローを、および前記第2の無線アクセス技術を介して少なくとも1つのデータフローを送信するための手段と、 ユーザ機器と前記第1の無線アクセス技術との間の無線リンク障害を検出するための手段と、 前記無線リンク障害が検出されたとき、前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローを維持すべきかどうかを決定するための手段と を備える、装置。
- 20無線リンク障害回復を管理するための装置であって、 第1の無線アクセス技術および第2の無線アクセス技術を用いて通信を確立するように構成されたコントローラと、 前記第1の無線アクセス技術を介して少なくとも1つのデータフローを送信するように構成されたワイヤレスワイドエリアネットワーク(WWAN)無線機と、 前記第2の無線アクセス技術を介して少なくとも1つのデータフローを送信するように構成されたワイヤレスローカルエリアネットワーク(WLAN)無線機と、 ユーザ機器と前記第1の無線アクセス技術との間の無線リンク障害を検出するように構成された無線リンク障害(RLF)構成要素と、 前記無線リンク障害が検出されたとき、前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローを維持すべきかどうかを決定するように構成されたRLFデータフロー決定構成要素と を備える、装置。
- 21無線リンク障害回復を管理するための方法であって、 第1の無線アクセス技術を介してユーザ機器との第1の通信接続を確立することと、 第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信することと、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローを送信する、 前記第1の通信接続の無線リンク障害の後に、前記ユーザ機器から前記第1の通信接続の無線リンク障害回復指示を受信することと、 無線リンク障害中に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが維持され得るかどうかを決定することと、 前記第2の無線アクセス技術を介して前記第2の通信接続上で、データフローごとに、前記少なくとも1つのデータフローの前記送信を維持すべきかどうかを前記ユーザ機器に示すことと を備える、方法。
- 22前記確立することが、前記ユーザ機器がアイドル状態から接続状態に移動することにより、または前記ユーザ機器がハンドオーバされることにより生じる、請求項21に記載の方法。
- 23前記示すことが、前記ユーザ機器に構成メッセージまたはデータメッセージのうちの少なくとも1つを送ることを備える、請求項21に記載の方法。
- 24前記構成メッセージが無線リソース制御メッセージである、請求項23に記載の方法。
- 25前記送ることが、前記第2の無線アクセス技術を介して前記第2の通信接続上で前記ユーザ機器に構成メッセージまたはデータメッセージのうちの少なくとも1つを送ることを備える、請求項23に記載の方法。
- 26コンピュータ実行可能コードを記憶する非一時的コンピュータ可読媒体であって、 少なくとも1つのコンピュータに、第1の無線アクセス技術を介してユーザ機器との第1の通信接続を確立させるためのコードと、 前記少なくとも1つのコンピュータに、第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信させるためのコードと、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローを送信する、 前記少なくとも1つのコンピュータに、前記第1の通信接続の無線リンク障害の後に、前記ユーザ機器から前記第1の通信接続の無線リンク障害回復指示を受信させるためのコードと、 前記少なくとも1つのコンピュータに、無線リンク障害中に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが維持され得るかどうかを決定させるためのコードと、 前記少なくとも1つのコンピュータに、前記第2の無線アクセス技術を介して前記第2の通信接続上で、データフローごとに、前記少なくとも1つのデータフローの前記送信を維持すべきかどうかを前記ユーザ機器に示させるためのコードと を備える、非一時的コンピュータ可読媒体。
- 27無線リンク障害回復を管理するための装置であって、 第1の無線アクセス技術を介してユーザ機器との第1の通信接続を確立するための手段と、 第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信するための手段と、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローを送信する、 前記第1の通信接続の無線リンク障害の後に、前記ユーザ機器から前記第1の通信接続の無線リンク障害回復指示を受信するための手段と、 無線リンク障害中に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが維持され得るかどうかを決定するための手段と、 前記第2の無線アクセス技術を介して前記第2の通信接続上で、データフローごとに、前記少なくとも1つのデータフローの前記送信を維持すべきかどうかを前記ユーザ機器に示すための手段と を備える、装置。
- 28無線リンク障害回復を管理するための装置であって、 少なくとも1つのメモリと、 前記少なくとも1つのメモリと通信しており、 第1の無線アクセス技術を介してユーザ機器との第1の通信接続を確立することと、 第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信することと、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローを送信する、 前記第1の通信接続の無線リンク障害の後に、前記ユーザ機器から前記第1の通信接続の無線リンク障害回復指示を受信することと、 無線リンク障害中に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが維持され得るかどうかを決定することと、 前記第2の無線アクセス技術を介して前記第2の通信接続上で、データフローごとに、前記少なくとも1つのデータフローの前記送信を維持すべきかどうかを前記ユーザ機器に示すことと を行うように構成された無線リンク障害(RLF)データフロー構成要素と を備える、装置。
- 29無線リンク障害回復を管理するための方法であって、 ユーザ機器から、第1の通信接続についての無線リンク障害回復指示を受信することと、 第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信することと、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローに関連する、 前記無線リンク障害回復の後に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが再開され得るかどうかを決定することと、 前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローの前記送信を再開すべきかどうかを前記ユーザ機器に示すことと を備える、方法。
- 30前記第2の無線アクセス技術に関係する少なくとも1つの測定報告を受信することと、 前記少なくとも1つの測定報告に少なくとも部分的に基づいて、前記ユーザ機器が前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの前記送信を再開することができるかどうかを決定することと をさらに備える、請求項29に記載の方法。
- 31複数の指示を受信することと、前記指示の各々は、前記ユーザ機器が前記無線リンク障害中に前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの特定の1つの前記送信を中断したかどうかを示し、ここにおいて、前記複数の指示の各々が、前記少なくとも1つのデータフローの特定の1つに関連する、 前記ユーザ機器から、前記第2の無線アクセス技術に関係する少なくとも1つの測定報告を受信することと、 前記第1の通信接続が再確立されたことを検出することと、 前記少なくとも1つの測定報告に基づいて、前記検出することに応答して、前記第2の無線アクセス技術を介した送信を再開すべきかどうかを決定することと をさらに備える、請求項29に記載の方法。
- 32前記少なくとも1つの測定報告が無線リソース制御(RRC)接続再確立メッセージの一部として受信される、請求項31に記載の方法。
- 33前記第2の無線アクセス技術を介した前記少なくとも1つのデータフローの前記送信が前記無線リンク障害中に維持されたというさらなる指示を受信することと、 前記第1の通信接続が再確立されたことを検出することと、 前記検出することに応答して、前記無線リンク障害中に前記第2の無線アクセス技術を介して維持された前記少なくとも1つのデータフローを前記第1の無線アクセス技術を介して送信すべきかどうかを決定することと をさらに備える、請求項32に記載の方法。
- 34前記指示が、前記第2の無線アクセス技術に関係する測定報告中に含まれる、請求項33に記載の方法。
- 35前記指示が無線リソース制御(RRC)接続再確立メッセージの一部として受信される、請求項33に記載の方法。
- 36コンピュータ実行可能コードを記憶する非一時的コンピュータ可読媒体であって、 少なくとも1つのコンピュータに、ユーザ機器から、第1の通信接続についての無線リンク障害回復指示を受信させるためのコードと、 前記少なくとも1つのコンピュータに、第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信させるためのコードと、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローに関連する、 前記少なくとも1つのコンピュータに、前記無線リンク障害回復の後に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが再開され得るかどうかを決定させるためのコードと、 前記少なくとも1つのコンピュータに、前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローの前記送信を再開すべきかどうかを前記ユーザ機器に示させるためのコードと を備える、非一時的コンピュータ可読媒体。
- 37無線リンク障害回復を管理するための装置であって、 ユーザ機器から、第1の通信接続についての無線リンク障害回復指示を受信するための手段と、 第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信するための手段と、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローに関連する、 前記無線リンク障害回復の後に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが再開され得るかどうかを決定するための手段と、 前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローの前記送信を再開すべきかどうかを前記ユーザ機器に示すための手段と を備える、装置。
- 38無線リンク障害回復を管理するための装置であって、 少なくとも1つのメモリと、 前記少なくとも1つのメモリと通信しており、 ユーザ機器から、第1の通信接続についての無線リンク障害回復指示を受信することと、 第2の無線アクセス技術を介して前記ユーザ機器との第2の通信接続が確立されるという指示を受信することと、ここにおいて、前記第2の通信接続が少なくとも1つのデータフローに関連する、 前記無線リンク障害回復の後に前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローが再開され得るかどうかを決定することと、 前記第2の無線アクセス技術を介して前記第2の通信接続上で前記少なくとも1つのデータフローの前記送信を再開すべきかどうかを前記ユーザ機器に示すことと を行うように構成された無線リンク障害(RLF)データフロー構成要素と を備える、装置。
Independent claims38
133 paragraphs, as filed
Priority claim [0001] This patent application is transferred to the assignee of this application and is expressly incorporated herein by reference, filed on July 30, 2014, "Techniques for Managing Radio Link Failure Recovery for a User." Non-provisional application No. 14 / 447,331 entitled "Equipment Connected to a WWAN and a WLAN" and "Techniques for Managing Radio Link Failure Recovery for a User Equipment Connected to a WWAN and" filed on August 16, 2013. Claim the priority of provisional application No. 61 / 866,862 entitled "WLAN".
[0002] Aspects of the present disclosure generally relate to wireless communication and, more particularly, are wireless links for user equipment (UE) connected to both a wireless wide area network (WWAN) and a wireless local area network (WLAN). Radio link failure (RLF) A technique for managing recovery.
[0003] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, and broadcasting. These wireless networks can be multiple access networks that can support 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 ( There is a SC-FDMA) network.
[0004] A wireless communication network may include several extended nodes B (also referred to as e-node B or eNB) that can support communication for some user equipment (UE). The UE may communicate with e-node B over the downlink and uplink. A downlink (or forward link) refers to a communication link from e-node B to UE, and an uplink (or reverse link) refers to a communication link from UE to e-node B.
[0005] The major extension introduced in the current 3rd Generation Partnership Project (3GPP) specification (or standard) family is Wireless Wide Area Network (WWAN) (eg, Long Term Evolution (LTE). Registered Trademarks): For UEs with both Long Term Evolution) or Universal Mobile Telecommunications System (UMTS) and Wireless Local Area Networks (WLAN) (eg Wi-Fi®) Dual connectivity. Therefore, the UE may be communicating with both e-node B and the WLAN access point (AP).
[0006] Given this dual connectivity, WWAN congestion is mitigated by sending data traffic over the WLAN (eg, offloading from LTE to the WLAN) to improve overall system capacity. obtain. To this end, Radio Access Network (RAN) -based traffic aggregation between cellular RANs and WLANs has been introduced into the 3GPP® family of standards. This technique uses traffic to offload traffic to the WLAN (for example, when the cellular RAN is congested) or (for example, when the WLAN radio condition is poor and / or cellular congestion is reduced). The Radio Resource Controller (RRC) command signaled by the cellular RAN is used to steer (for example, fall back) to the cellular RAN.
[0007] When the radio frequency (RF) environment between the UE and a WWAN access node (eg, e-node B in LTE) becomes poor, the UE may enter a radio frequency link failure (RLF). Generally, when LTE RLF occurs, the RRC connection for the UE is interrupted until the UE recovers from the RLF (eg, completes the RLF recovery process). Therefore, some LTE Signaling Radio Bearers (eg, SRB1) are not available during this time. In addition, data flow for WWAN (for example, data radio for LTE (DRB: data radio) All data traffic, sometimes called bearer)), is interrupted and the WLAN report entry in the RRC is cleared by the UE. For UEs communicating with both e-node B and the WLAN access point, the behavior between LTE and WLAN is irrelevant, but (1) WLAN offloading and / or fallback decisions are made by the cellular RAN. , (2) LTE RLF can have a serious impact on cellular RAN-based WLAN interactions, as WLAN measurement reports from UEs are performed via RRC messages.
[0008] Currently, under the 3GPP standard family, LTE RLF processing includes three aspects: (a) RLF detection, (b) cell reselection, and (c) RRC connection reestablishment. However, none of these aspects include guidance on how to handle WLAN data flows during recovery from LTE RLF. In view of the above, it can be understood that there may be significant issues and disadvantages associated with current RLF processing when the UE is interacting between LTE and WLAN.
[0009] Therefore, improvements in managing RLF recovery for UEs connected to both cellular and WLAN networks are desired.
[0010] In the following, in order to give a basic understanding of one or more aspects, a simplified overview of such aspects is presented. This overview is not a comprehensive overview of all intended aspects, nor does it identify the major or important elements of all aspects, nor does it define the scope of any or all aspects. Its sole purpose is to present some concepts in one or more embodiments in a simplified form as an introduction to a more detailed description presented later.
[0011] In one aspect, an exemplary method for managing wireless link failure recovery will be described. The method may include establishing communication using a first radio access technique and a second radio access technique. Further, the method may include transmitting at least one data flow via the first wireless access technology and at least one data flow via the second wireless access technology. The method may further include detecting a wireless link failure between the user equipment and the first wireless access technology. Further, the method may include determining whether at least one data flow via a second radio access technique should be maintained when a radio link failure is detected.
[0012] In one aspect, a computer-readable medium for managing wireless link failure recovery will be described. The computer-readable medium may store on at least one computer a computer executable code that can establish communication using a first wireless access technique and a second wireless access technique. In addition, the code may cause at least one computer to transmit at least one data flow via a first wireless access technology and at least one data flow via a second wireless access technology. In addition, the code may allow at least one computer to detect a wireless link failure between the user equipment and the first wireless access technology. The code may also allow at least one computer to decide whether to maintain at least one data flow through a second wireless access technology when a wireless link failure is detected.
[0013] In one aspect, an exemplary device for managing wireless link failure recovery will be described by the present disclosure. The device may include means for establishing communication using the first radio access technology and the second radio access technology. The device may include means for transmitting at least one data flow via the first wireless access technology and at least one data flow via the second wireless access technology. The device may include means for detecting a wireless link failure between the user equipment and the first wireless access technology. The device may include means for determining whether at least one data flow via a second radio access technology should be maintained when a radio link failure is detected.
[0014] In one aspect, a device for managing wireless link failure recovery will be described. The device may include a controller configured to establish communication using a first wireless access technique and a second wireless access technique. The device may include a wireless wide area network (WWAN) radio configured to transmit at least one data flow via a first wireless access technology. The device may include a wireless local area network (WLAN) radio that is configured to transmit at least one data flow via a second wireless access technology. The device may include a radio link fault (RLF) component configured to detect a radio link fault between the user equipment and the first radio access technology. The apparatus may include an RLF data flow determination component configured to determine whether at least one data flow should be maintained via a second wireless access technology when a wireless link failure is detected.
[0015] In one aspect, a method for managing wireless link failure recovery will be described. The method may include establishing a first communication connection with the user equipment via the first wireless access technology. The method may include receiving an instruction that a second communication connection with the user equipment is established via the second wireless access technology. A second communication connection may transmit at least one data flow. The method may include receiving a wireless link failure recovery instruction for the first communication connection from the user equipment. The method may include determining whether at least one data flow 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 equipment whether at least one data flow transmission should be maintained for each data flow over the second communication connection via the second wireless access technology.
[0016] In one aspect, a computer-readable medium for managing wireless link failure recovery will be described. The computer-readable medium may store computer executable code. The code may allow at least one computer to establish a first communication connection with a user device via a first wireless access technology. The code may cause at least one computer to receive instructions that a second communication connection with the user equipment will be established via the second wireless access technology. A second communication connection may transmit at least one data flow. The code may cause at least one computer to receive a wireless link failure recovery instruction for the first communication connection from the user equipment. The code may allow at least one computer to determine whether at least one data flow can be maintained on the second communication connection via the second wireless access technology during a wireless link failure. The code may cause at least one computer to indicate to the user equipment whether at least one data flow transmission should be maintained for each data flow over the second communication connection via the second wireless access technology. ..
[0017] In one aspect, a device for managing wireless link failure recovery will be described. The device may include means for establishing a first communication connection with a user device via a first wireless access technology. The device may include means for receiving an instruction that a second communication connection with the user equipment is established via the second wireless access technology. A second communication connection may transmit at least one data flow. The device may include means for receiving a wireless link failure recovery instruction for the first communication connection from the user equipment. The device may include means for determining whether at least one data flow 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 at least one data flow transmission should be maintained for each data flow over the second communication connection via the second wireless access technology.
[0018] In one aspect, a device for managing wireless link failure recovery will be described. The device may include at least one memory and RLF data flow components communicating with at least one memory. The RLF data flow component may be configured to establish a first communication connection with the user equipment via the first wireless access technology. The RLF data flow component may be configured to receive an instruction to establish a second communication connection with the user equipment via the second radio access technology, where the second communication connection is at least. Send one data flow. The RLF data flow component may be configured to receive a wireless link failure recovery instruction for the first communication connection from the user equipment. The RLF data flow component may be configured to determine whether at least one data flow can be maintained on the second communication connection via the second radio access technology during a radio link failure. The RLF data flow component is configured to indicate to the user equipment whether at least one data flow transmission should be maintained for each data flow over the second communication connection via the second wireless access technology. obtain.
[0019] In one aspect, a method for managing wireless link failure recovery will be described. The method may include receiving a wireless link failure recovery instruction for the first communication connection from the user equipment. The method may include receiving an instruction that a second communication connection with the user equipment is established via the second wireless access technology. The second communication connection can be associated with at least one data flow. The method may include determining whether at least one data flow can be resumed on the second communication connection via the second radio access technology after radio link failure recovery. The method may include indicating to the user equipment whether to resume transmission of at least one data flow over the second communication connection via the second wireless access technology.
[0020] In one aspect, a computer-readable medium for managing wireless link failure recovery will be described. The computer-readable medium may store computer executable code. The code may cause at least one computer to receive a wireless link failure recovery instruction for the first communication connection from the user equipment. The code may cause at least one computer to receive instructions that a second communication connection with the user equipment will be established via the second wireless access technology. The second communication connection can be associated with at least one data flow. The code may allow at least one computer to determine whether at least one data flow can be resumed on the second communication connection via the second wireless access technology after wireless link failure recovery. The code may cause the user equipment to indicate whether at least one computer should resume transmission of at least one data flow over the second communication connection via the second wireless access technology.
[0021] In one aspect, a device for managing wireless link failure recovery will be described. The device may include means for receiving a wireless link failure recovery instruction for the first communication connection from the user equipment. The device may include means for receiving an instruction that a second communication connection with the user equipment is established via the second wireless access technology. The second communication connection can be associated with at least one data flow. The device may include means for determining whether at least one data flow can be resumed on the second communication connection via the second radio access technology after wireless link failure recovery. The device may include means for indicating to the user equipment whether transmission of at least one data flow should be resumed over the second communication connection via the second wireless access technology.
[0022] In one aspect, a device for managing wireless link failure recovery will be described. The device may include at least one memory and RLF data flow components communicating with at least one memory. The RLF data flow component may be configured to receive a wireless link failure recovery instruction for the first communication connection from the user equipment. The RLF data flow component may be configured to receive instructions that a second communication connection with the user equipment will be established via the second wireless access technology. The second communication connection can be associated with at least one data flow. The RLF data flow component may be configured to determine if at least one data flow can be resumed on the second communication connection via the second radio access technology after radio link failure recovery. The RLF data flow component may be configured to indicate to the user equipment whether to resume transmission of at least one data flow over the second communication connection via the second wireless access technology.
[0023] In order to achieve the above and related objectives, one or more embodiments include features that are fully described below and pointed out in particular in the claims. The following description and accompanying drawings detail some exemplary features of one or more embodiments. However, these features represent only a few of the various methods in which the principles of the various aspects can be adopted, and this description shall include all such aspects and their equivalents.
[0024] To allow a more complete understanding of the present disclosure, the accompanying drawings are then referred to, in which similar elements are referred to using similar numbers. These drawings should not be construed as limiting this disclosure and are merely exemplary.
<figref num="1">[0025] A block diagram conceptually showing an example of a telecommunications system described herein that has an aspect configured to manage wireless link failure recovery for a user device.</figref><figref num="2">[0026] A block diagram conceptually showing an example of a bearer architecture in a wireless communication system having an aspect configured to manage wireless link failure recovery for a user device as described herein.</figref><figref num="3">[0027] A block diagram conceptually illustrating an exemplary e-node B and an exemplary user device having an aspect configured to manage wireless link failure recovery for a user device as described herein.</figref><figref num="4">[0028] A block diagram conceptually illustrating the aggregation of LTE and WLAN wireless access technologies in a user device having an embodiment configured to manage wireless link failure recovery for the user device as described herein.</figref><figref num="5A">[0029] Conceptually an example of a data path between a packet data network (PDN) and a user device, described herein, having an aspect configured to manage wireless link failure recovery for the user device. The block diagram shown in.</figref><figref num="5B">A block that conceptually illustrates an example of a data path between a packet data network (PDN) and a user device that has an aspect configured to manage wireless link failure recovery for the user device as described herein. Figure.</figref><figref num="6">[0030] A block diagram conceptually illustrating a particular aspect of a network entity configured to manage wireless link failure recovery for a user device as described herein.</figref><figref num="7">[0031] A call flow diagram illustrating communication between a user device and an e-node B and a WLAN access point according to a first aspect for managing wireless link failure recovery for a user device as described herein. ..</figref><figref num="8">[0032] A call flow diagram illustrating communication between a user device and an e-node B and a WLAN access point according to a second aspect for managing wireless link failure recovery for the user device as described herein. ..</figref><figref num="9">[0033] A call flow diagram illustrating communication between a user device and an e-node B and a WLAN access point according to a third aspect for managing wireless link failure recovery for the user device described herein. ..</figref><figref num="10">[0034] A call flow diagram illustrating communication between a user device and an e-node B and a WLAN access point according to a fourth aspect for managing wireless link failure recovery for the user device as described herein. ..</figref><figref num="11">[0035] A call flow diagram illustrating communication between a user device, e-node B, and a WLAN access point according to a fifth aspect for managing wireless link failure recovery for the user device described herein. ..</figref><figref num="12">[0036] A call flow diagram illustrating communication between a user device, e-node B, and a WLAN access point according to a sixth aspect for managing wireless link failure recovery for the user device, as described herein. ..</figref><figref num="13">[0037] A block diagram illustrating a method for managing wireless link failure recovery by a user device as described herein.</figref><figref num="14">[0038] A block diagram illustrating a method for managing wireless link failure recovery in a user device by a first e-node B, described herein.</figref><figref num="15">[0039] A block diagram illustrating a method for managing wireless link failure recovery in a user device by a second e-node B, described herein.</figref><figref num="16">[0040] The figure which shows an example of the hardware implementation form for the apparatus which employs the processing system which has the aspect configured to manage the wireless link failure recovery for a user equipment which is described herein.</figref>
[0041] The embodiments for carrying out the invention described below with respect to the accompanying drawings describe various configurations and do not represent only configurations in which the concepts described herein can be implemented. The embodiments for carrying out the invention include specific details to give a complete understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be implemented without these specific details. In some examples, well-known structures and components are shown in the form of block diagrams so as not to obscure such concepts.
[0042] The techniques described herein can be used for a variety of wireless communication networks, including CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes wideband CDMA (WCDMA®: Wideband CDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. TDMA networks can implement wireless technologies such as the Global System for Mobile Communications (GSM). OFDMA networks include advanced UTRA (E-UTRA: Evolved UTRA) and ultra mobile broadband (UMB: Ultra Mobile). Wireless technologies such as Broadband), IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX®), IEEE802.20, and Flash-OFDMA can be implemented. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE Advanced (LTE-A: LTE-Advanced) are new releases of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are listed in documents from an organization called the "Third Generation Partnership Project" (3GPP). cdma2000 and UMB are "3rd Generation Partnership Project 2" (3GPP2: 3rd Generation Partnership Project) It is described in a document from an organization called 2). The techniques described herein can be used for the wireless networks and wireless technologies described above, as well as other wireless networks and wireless technologies. For clarity, some aspects of the technique are described below with respect to LTE, and LTE terminology is used for most of the description below.
[0043] Both a wireless wide area network (WWAN) and a wireless local area network (eg, Wi-Fi network) according to this embodiment, for example, Long Term Evolution (LTE) or Universal Mobile Telecommunications System (UMTS). Devices and methods are presented that provide new techniques for managing radio link failure (RLF) recovery in user equipment (UE) connected to a network. More particularly, RLF detection and recovery pro various aspects are described for processing WLAN data flow throughout process.
[0044] Table 1 summarizes various aspects of the techniques described herein for managing data flow during RLF recovery. With respect to RLF behavior, in all aspects the WWAN (eg LTE) data flow (sometimes referred to as the Data Radio Bearer (DRB)) is interrupted or stopped. Some of the aspects (eg, second and third aspects) include interrupting both cellular (eg LTE) and WLAN data flows. In addition, some embodiments (eg, first, fourth, and fifth embodiments) include optionally interrupting the WLAN data flow along with the cellular (eg LTE) data flow. A sixth aspect comprises interrupting only the cellular (eg LTE) data flow. In addition, Table 1 summarizes the actions associated with RLF recovery for each aspect.
<tables num="1"><img id="000003" he="156" wi="170" file="JP2017225146A_D0001.tif" img-format="tif" img-content="drawing" /></tables>
The data flow may accommodate any transmission of data between two network entities, for example UE and eNodeB, or UE and WLAN access point (AP). Data flows are sometimes referred to, for example, as data traffic, traffic, and / or data paths. WWAN data flows may include or be associated with, for example, bearers, traffic flow templates (TFTs), transmission control protocol (TCP) connections, and / or quality of service (QoS) classes. WLAN data flows can include or relate to, for example, transmit requests (RTS), transmittable (CTS), other signaling, and / or user data.
[0046] Various aspects described herein may be described with respect to LTE as an example of the WWAN with which the UE is communicating with it. However, it will be appreciated that at least some of these embodiments may apply to other WWANs, including UMTS and / or other wireless access technologies (RATs).
[0047] FIG. 1 is a conceptual example of an telecommunications system 100 having an aspect contained therein configured to manage a WWAN (eg LTE) radio link fault (RLF) according to this aspect. It is a block diagram shown in. For example, telecommunications system 100 can be an LTE network or a UMTS network. The telecommunications system 100 may include several advanced nodes B (e-node B) 110, user equipment (UE) 120, and other network entities. The e-node B110 can be a station that communicates with the UE 120 to provide access to the WWAN, and is sometimes referred to as a base station, access point, or the like. Node B is another example of a station communicating with UE120. Although not shown, one or more WLAN (or Wi-Fi) APs also communicate with the UE 120 to provide access to a wireless local area network (WLAN) or some other type of local area network (LAN). I have something to do.
[0048] Each e-node B110 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the coverage area of e-node B110 and / or the e-node B subsystem servicing this coverage area, depending on the context in which this term is used.
The e-node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. The macrocell can cover a relatively large geographic area (eg, a few miles or kilometers in radius) and can allow unlimited access by the UE 120 with a subscription to wireless services associated with the macrocell. Picocell can cover a relatively small geographic area and allow unlimited access by UE120 with a service subscription. The femtocell can cover a relatively small geographic area (eg, home) and allow restricted access by the UE120 that has an association with the femtocell (eg, UE120 may be UE120, for example, home or office). Limited Subscriber Group (CSG: Closed Subscriber) set up for use by one of the UE120s in the primary location of one of the users Can be subscribed to Group)). The e-node B110 for the macro cell is sometimes referred to as the macro e-node B. The e-node B110 for the pico cell is sometimes referred to as the pico e-node B. The e-node B110 for the femtocell is sometimes referred to as the femto e-node B or the home e-node B.
[0050] In the example shown in FIG. 1, e-nodes B 110a, 110b, and 110c can be macro e-nodes B for macro cells 102a, 102b, and 102c, respectively. The e-node B 110x can be a pico e-node B for the pico cell 102x. e-nodes B 110y and 110z can be femto e-nodes B for femtocells 102y and 102z, respectively. The e-node B110 may provide communication coverage for one or more (eg, three) cells.
[0051] The telecommunications system 100 may include one or more relay stations 110r and 120r, sometimes referred to as relay e-node B, relay, and the like. The relay station 110r receives the transmission of data and / or other information from the upstream station (eg, e-node B110 or UE120) and the received transmission of the data and / or other information to the downstream station (eg UE120 or UE120). It can be a station that sends to e-node B110). The relay station 120r can be a UE that relays transmission to another UE (not shown). In the example shown in FIG. 1, the relay station 110r may communicate with the e-nodes B110a and UE120r to allow communication between the e-nodes B110a and the UE120r.
[0052] Telecommunications 100 is a heterogeneous network that includes different types of e-nodes B110, such as macro e-nodes B110a, 110b, and 110c, pico e-nodes B110x, femto e-nodes B110y and 110z, relay stations 110r, and the like. obtain. These different types of e-nodes B110 can have different transmit power levels, different coverage areas, and different effects on interference in telecommunications 100. For example, macro e-nodes B110a, 110b, and / or 110c can have high transmit power levels (eg, 20 watts), while pico e-nodes B110x, femto e-nodes B110y and 110z and / or relay station 110r It can have lower transmission power levels (eg 1 watt).
[0053] The telecommunications system 100 may support synchronous or asynchronous operation. For synchronous operation, the e-node B110 may have similar frame timings and transmissions from different e-nodes B110 may be approximately time-matched. For asynchronous operation, the e-node B110 may have different frame timings and transmissions from different e-nodes B110 may not be time aligned. The techniques described herein can be used for both synchronous and asynchronous operations.
[0054] The network controller 130 may be coupled to a set of e-nodes B110 to coordinate and control the e-nodes B110. The network controller 130 may communicate with the e-node B110 via a backhaul (not shown). The e-node B110 may also communicate with each other directly or indirectly, for example, via a wireless or wireline backhaul (eg, an X2 interface) (not shown). In one aspect in which the telecommunications system 100 includes an e-node B and one or more WLAN APs, these two types of access nodes may or may not be connected to each other through a backhaul. However, if the e-node B and the WLAN AP are not connected via a backhaul, the e-node B and the WLAN AP may communicate with each other through an intermediary such as one of the UE 120s.
[0055] UE 120s can be distributed throughout the telecommunications system 100, and each UE 120 can be fixed or mobile. UE120 is sometimes referred to as a terminal, mobile station, subscriber unit, station, etc. In one example, each of the UE120s is a cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet, netbook, It can be a smart book or the like. The UE 120 may be able to communicate with macro e-nodes B110a, 110b, and 110c, pico e-node B110x, femto e-nodes B110y and 110z, relay stations 110r, and / or other network entities. For example, in Figure 1, the solid line with a double-headed arrow is its serving enode on the downlink and / or uplink, which is the particular UE120 and the enode B110 designated to serve the particular UE120. It may indicate the desired transmission to and from B110. A dashed line with a double-headed arrow may indicate interfering transmission between a particular UE 120 and e-node B110 (eg, non-serving e-node B).
[0056] LTE telecommunications networks may 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 divide system bandwidth into multiple (K) orthogonal subcarriers, commonly referred to as tones, bins, and so on. Each subcarrier can be modulated with data. In general, modulated symbols can be sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed and the total number of subcarriers (K) can depend on system bandwidth. For example, the subcarrier spacing can be 15kHz and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180kHz). Therefore, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024 or 2048 for a system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz (MHz), respectively. System bandwidth can be subdivided into subbands. For example, a subband can cover 1.08MHz (ie, 6 resource blocks), with 1, 2, 4, 8 or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10 or 20MHz, respectively. There can be.
[0057] FIG. 2 is a block conceptually showing an example of a bearer (eg, data flow) architecture in a wireless communication system 200 according to this aspect, which is configured to manage a WWAN (eg, LTE) RLF. It is a figure. The bearer architecture can be used to provide end-to-end service 235 between UE 215, which can be one of UE 120 in Figure 1, and peer entity 230, which can be addressed over the network. The peer entity 230 can be a server, another UE, or another type of network addressable device. The end-to-end service 235 may transfer data between the UE 215 and the peer entity 230 according to a set of characteristics (eg, quality of service (QoS)) associated with the end-to-end service 235. The end-to-end service 235 includes at least UE215, e-node B205 (for example, one of e-node B110 in Figure 1), serving gateway (SGW) 220, and packet data network (PDN) gateway (PGW:). PDN gateway) 225, and can be implemented by peer entity 230. The UE 215 and e-node B205 can be components of the evolved UMTS terrestrial radio access network (E-UTRAN) 208, which is the air interface for LTE / LTE-A systems. The serving gateway 220 and PDN gateway 225 can be components of the evolved packet core (EPC) 209, which is the core network architecture of LTE / LTE-A systems. Peer entity 230 can be an addressable node on PDN 210 communicatively coupled to PDN gateway 225.
[0058] The end-to-end service 235 is provided by the evolved packet system (EPS) bearer 240 between the UE 215 and the PDN gateway 225, and between the PDN gateway 225 and the peer entity 230 via the SGi interface. Can be implemented by the external bearer 245 of. The SGi interface may expose UE215's Internet Protocol (IP) or other network layer addresses to PDN210.
[0059] The EPS bearer 240 can be an end-to-end tunnel defined for a particular QoS. Each EPS bearer 240 has multiple parameters, such as QoS class identifier (QCI), allocation and retention priority (ARP), guaranteed bit rate (GBR), and agri. Gate maximum bit rate (AMBR: aggregate maximum bit) rate) can be related. The QCI can be an integer that indicates the QoS class associated with the predefined packet forwarding process in terms of latency, packet loss, GBR, and priority. In some examples, QCI can be an integer from 1 to 9. In addition, ARP can be used by the e-node B205 scheduler to give preemption priority in the case of contention between two different bearers for the same resource. The GBR may specify separate downlink guaranteed bit rates and uplink guaranteed bit rates. Some QoS classes can be non-GBRs for which no guaranteed bit rate is defined for bearers of those classes.
[0060] The EPS bearer 240 is an E-UTRAN radio access bearer (E-RAB) 250 between the UE 215 and the serving gateway 220, and a serving gateway 220 and PDN via an S5 or S8 interface. It can be implemented by the S5 / S8 bearer 255 to and from the gateway. S5 refers to the 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-RAB250 is implemented by the wireless bearer 260 between UE215 and enode B205 via the LTE-Uu air interface and by the S1 bearer 265 between enode B and the serving gateway 220 via the S1 interface. obtain.
[0061] Figure 2 shows the bearer hierarchy in the context of an example of end-to-end service 235 between UE 215 and peer entity 230, but some bearers have data that is not related to end-to-end service 235. It will be understood that it can be used to carry. For example, a wireless bearer 260 or other type of bearer can be established to send control data unrelated to end-to-end service 235 data between two or more entities.
[0062] As described above, in some configurations, such as the wireless communication system 200 of FIG. 2, the system may include cellular (eg LTE) and WLAN (eg Wi-Fi) interactions. Therefore, data related to one or more EPS bearers 240 (eg, cellular or LTE data) can be offloaded from the e-node B205 to the WLAN AP (not shown), thereby the bearer via an alternative route. Divert traffic from EPC212 to PDN210. Additional aspects related to LTE data offloading and / or fallback from the EPC212 to the PDN210 via a WLAN AP are described with reference to FIGS. 5A and 5B.
[0063] It will be understood that bearers are sometimes referred to as data flows. The term "bearer" is commonly used to describe LTE (or other WWAN) data flows (eg, data wireless bearers or DRBs) and other wireless access, such as WLAN (or Wi-Fi). Data flows for technology (RAT) are less likely to be called "bearers", but rather a generic term is used rather than "data flows".
[0064] FIG. 3 is an exemplary e-node B310 (eg, e-node B110 of FIG. 1 and / or FIG. 2) having an aspect configured to manage a WWAN (eg LTE) RLF according to this aspect. It is a block diagram conceptually showing an exemplary UE320 (for example, one of UE120 in FIG. 1 and / or UE215 in FIG. 2).
[0065] e-node B310 has antenna 334<sub>1 ~ t</sub>Can be equipped with UE320 is antenna 352<sub>1 ~ r</sub>Can be equipped, where t and r are integers greater than or equal to 1. In the e-node B310, 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 is therefore also referred to as a base station processor 340 or a base station controller / processor 340. Control information can be carried over PBCH, PCFICH, PHICH, PDCCH, etc. Data can be carried on PDSCH and the like. Base station transmission processor 322 may process data and control information (eg, coding and symbol mapping) to obtain data symbols and control symbols, respectively. The base station transmit processor 322 also includes, for example, PSS, SSS, and cell-specific reference signals (RS: reference). Can generate a reference symbol for signal). Base Station Transmission (TX) Multi-Input Multi-Output (MIMO) Processor 330 may, where applicable, perform spatial processing (eg, precoding) on data symbols, control symbols, and / or reference symbols and output. Base station modulator / demodulator (MOD / DEMOD) 332<sub>1 ~ t</sub>Can be given to. Each base station modulator / demodulator 332 may process its own output symbol stream (for example, for OFDM, etc.) in order to obtain an output sample stream. Each base station modulator / demodulator 332 may further process the output sample stream (eg, convert to analog, amplify, filter, and upconvert) to obtain the downlink signal. Modulator / Demodulator 332<sub>1 ~ t</sub>Downlink signals from are antennas 334 respectively<sub>1 ~ t</sub>Can be transmitted via.
[0066] In UE320, UE antenna 352<sub>1 ~ r</sub>Can receive downlink signals from e-node B310 and receive signals as UE modulator / demodulator (MOD / DEMOD) 354, respectively.<sub>1 ~ r</sub>Can be given to. Each UE modulator / demodulator 354 may tune (eg, filter, amplify, downconvert, and digitize) its received signal to obtain an input sample. Each UE modulator / demodulator 354 may further process the input sample (for example, for OFDM) to obtain the received symbol. UE MIMO Detector 356 is for all UE modulators / demodulators 354<sub>1 ~ r</sub>The received symbol can be obtained from, perform MIMO detection on the received symbol if applicable, and give the detected symbol. The UE receiving processor 358 may process the detected symbols (eg, demodulate, deinterleave, and decode), feed the decrypted data of the UE 320 to the UE data sink 360, and feed the decoded control information to the UE controller 380. In one aspect, the UE controller 380 may include a processor and is therefore also referred to as the UE processor 380 or UE controller / processor 380.
[0067] On the uplink, in the UE 320, the UE transmit processor 364 may receive and process data from the UE data source 362 (eg for PUSCH) and from the UE controller 380 (eg for PUCCH). ) Can receive and process control information. The UE transmit processor 364 may also generate a reference symbol for the reference signal. Symbols from UE transmit processor 364 are precoded by UE TX MIMO processor 366 where applicable, and further (for example, for SC-FDM) UE modulator / demodulator 354.<sub>1 ~ r</sub>Can be processed by and sent to e-node B310. At e-node B310, the uplink signal from UE320 is received by base station antenna 334, processed by base station modulator / demodulator 332, detected by base station MIMO detector 336 if applicable, and further base. The decrypted data and control information sent by the UE 320, processed by the station receiving processor 338, can be obtained. 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.
[0068] The base station controller 340 and the UE controller 380 may direct operations on the e-nodes B310 and UE320, respectively. Base station controller 340 and / or other processors and modules in e-node B310 may, for example, perform or direct various processes for the techniques described herein. The UE controller 380 and / or other processors and modules in the UE 320 are also functional blocks shown in Figure 6 and / or for UEs communicating with both cellular and WLAN (or Wi-Fi) networks. It may be configured to perform or direct the execution of other processes for the techniques described herein for managing RLF recovery. Base station memory 342 and UE memory 382 may store data and program code for e-nodes B310 and UE320, respectively. The scheduler 344 may schedule the UE 320 for data transmission on the downlink and / or the uplink.
[0069] In one configuration, the UE 320 provides a means for establishing communication using a first radio access technology (RAT) and a second RAT, and at least one data flow through the first RAT. And a means for transmitting at least one data flow via the second RAT, a means for detecting a radio link failure between the user equipment and the first RAT, and a radio link failure detected. When it may include a means for deciding whether to maintain at least one data flow via a second RAT. In one aspect, the means described above are configured to perform the functions specified by the means described above: UE controller 380, UE memory 382, UE receiving processor 358, UE MIMO detector 356, UE modulator / It can be a demodulator 354 and a UE antenna 352. In another aspect, the means described above may be modules, components, or any device configured to perform the functions specified by the means described above.
[0070] In one configuration, the e-node B310 is a means for establishing a first communication connection with the user equipment via the first RAT and a second with the user equipment via the second RAT. A means for receiving an instruction that a communication connection is established and, here, a wireless link of the first communication connection from a user device (eg, UE320) to which the second communication connection transmits at least one data flow. A means for receiving failure recovery instructions and a second RAT during a wireless link failure where communication connections are established between the user equipment and the local area network and between the user equipment and the WWAN. A means for determining whether at least one data flow can be maintained over the second communication connection via the second communication connection and at least one per data flow over the second communication connection via the second communication connection. It may include means for indicating to the user equipment whether the transmission of one data flow should be maintained. In another configuration, the e-node B310 is, for example, a means for receiving a radio link failure recovery instruction for the first communication connection from the UE 320 and a second communication with the user equipment via the second RAT. Means for receiving instructions that a connection will be established and, where the second communication connection is associated with at least one data flow, a second communication via a second RAT after wireless link failure recovery. A means for determining if at least one data flow can be resumed on the connection and whether the user should resume sending at least one data flow on the second communication connection via the second RAT. It may include means for indicating to the device. In one aspect, the means described above are a base station controller 340, a base station memory 342, a base station transmitting processor 322, a base station modulator / demodulator, configured to perform the functions specified by the above means. It can be 332, and base station antenna 334. In another aspect, the means described above may be modules, components, or any device configured to perform the functions specified by the means described above.
[0071] FIG. 4 has an embodiment in which the UE 415, e-node B405-a, and / or WLAN AP 405-b according to this aspect are configured to manage WWAN (eg LTE) RLF recovery, UE415. It is a block diagram which conceptually shows the carrier aggregation of LTE wireless access technology (RAT) and WLAN RAT in. Aggregation is one or more component carriers 1 ~ N (CC)<sub>1</sub>~ CC<sub>N</sub>) Can be used to communicate with the e-node B405-a and the WLAN carrier 440 to communicate with the WLAN (or Wi-Fi) AP405-b, which can be done in system 400 including multimode UE415. .. UE415 can be an example of one or more of UE120 in FIG. 1, UE215 in FIG. 2, and UE320 in FIG. The e-node B405-a can be an example of one or more of the e-node B110 of FIG. 1, the e-node B205 of FIG. 2, and the e-node B310 of FIG. Figure 4 shows only one UE415, one e-node B405-a, and one WLAN AP405-b, but the system 400 has any number of UE415, e-node B405-a, and / Or WLAN Please understand that AP405-b can be included.
[0072] e-node B405-a is an LTE component carrier CC<sub>1</sub>~ CC<sub>N</sub>Information can be sent to UE415 via forward (downlink) channels 432-1 to 432-N on the 430. In addition, UE415 is an LTE component carrier CC<sub>1</sub>~ CC<sub>N</sub>Information can be sent to e-node B405-a via the above reverse (uplink) channels 434-1 to 434-N. Similarly, the WLAN AP405-b may transmit information to the UE 415 via forward (downlink) channel 452 on the WLAN carrier 440. In addition, the UE 415 may transmit information to the WLAN AP405-b over the reverse (uplink) channel 454 of the WLAN carrier 440.
[0073] When describing the various entities in FIG. 4, names associated with 3GPP LTE or LTE-A wireless networks are used for purposes of description. However, please understand that System 400 can operate in other networks, such as, but not limited to, UMTS networks, OFDMA wireless networks, CDMA networks, and 3GPP2 CDMA2000 networks.
[0074] During multicarrier operation, downlink control information (DCI) messages associated with different UE415s may be carried on multiple component carriers. For example, DCI on the PDCCH can be contained on the same component carrier configured to be used by UE415 for PDSCH transmission (eg, same carrier signaling). As an alternative or addition, DCI can be carried on a different component carrier than the target component carrier used for PDSCH transmission (eg, cross-carrier signaling). In some embodiments, a carrier indicator field (CIF), which can be semi-statically enabled, allows the transmission of PDCCH control signaling from carriers other than the target carrier for PDSCH transmission. , May be included in some or all DCI formats (eg, cross-carrier signaling).
[0075] In this example, UE415 may receive data from one e-node B405-a. However, users on the cell edge may experience high cell-to-cell interference that can limit the data rate. Multi-flow allows the UE to receive data from two e-nodes B405-a at the same time. Multiflow works by sending and receiving data from two e-nodes B405-a in two completely separate streams when the UE415 is in the range of two cell towers in two adjacent cells at the same time. To do. UE415 communicates with two e-nodes B at the same time when the device is on the edge of the reach of either of the two e-nodes B405-a. By simultaneously scheduling two independent data streams from two different eNodeBs to UE415, Multiflow takes advantage of non-uniform loading in the HSPA network. This helps improve the cell edge user experience while increasing network capacity. In one example, the throughput data rate for the user at the cell edge can be doubled. "Multi-flow" is a feature of LTE / LTE-A similar to dual-carrier HSPA, but with differences. For example, dual carrier HSPA does not allow connectivity to multiple towers for connecting to devices at the same time.
[0076] Prior to the LTE-A standardization, the LTE component carrier 430 was backward compatible, which allowed a smooth transition to new releases. However, due to this feature, the LTE component carrier 430 continuously transmitted a common reference signal (CRS, also known as a cell-specific reference signal) over the bandwidth in every subframe. Most cell site energy consumption is caused by the amplifier, as the cell remains on even when only limited control signaling is being transmitted, which causes the power amplifier to continue to consume energy. CRS was introduced in Release 8 of the LTE standard and is the most basic downlink reference signal in LTE. CRS is transmitted in every resource block in the frequency domain and in every downlink subframe. The CRS in the cell may be for one, two, or four corresponding antenna ports. CRS can be used by remote terminals to estimate channels for coherent demodulation. New Carrier Type (NCT: New Carrier) Type) allows cell switching off temporarily by removing CRS transmissions in four of the five subframes. This feature reduces the power consumed by the power amplifier, as well as overhead and interference from the CRS, as the CRS is no longer transmitted continuously across every subframe over the bandwidth. In addition, the new carrier type allows the downlink control channel to operate using UE-specific demodulation reference symbols. The new carrier type can be operated as a type of expansion carrier with another LTE / LTE-A carrier, or as a stand-alone non-backward compatible carrier instead.
[0077] FIGS. 5A and 5B show UE515 and PDN (eg, for example) in wireless communication systems 500-a and 500-b having an aspect configured to manage WWAN (eg LTE) RLF recovery according to this aspect. , The Internet) is a block diagram conceptually showing examples of data paths 545 and 550. Data paths 545 and 550 are within the context of wireless communication system 500-a in Figure 5A and wireless communication system 500-b in Figure 5B, which aggregates WLAN wireless access technology (RAT) and cellular (eg LTE) RAT. It is indicated by. In each example, the wireless communication systems 500-a and 500-b are multi-mode UE515, e-node B505-a, and WLAN. May include AP505-b. UE515 can be an example of one or more of UE120 in FIG. 1, UE215 in FIG. 2, UE320 in FIG. 3, and UE415 in FIG. The e-node B505-a can be an example of one or more of the e-node B110 of FIG. 1, the e-node B205 of FIG. 2, the e-node B310 of FIG. 3, and the e-node B405-a of FIG. The WLAN AP505-b can be an example of the WLAN AP405-b in FIG.
[0078] The wireless communication systems 500-a and 500-b may also include advanced packet core (EPC) 512, PDN510, and peer entity 530, each of which is EPC212, PDN210, and peer in FIG. 2, respectively. Can be similar to entity 230. The EPC 512 in 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 PGW 525 may be similar to the SGW 220 and PGW 225 in FIG. .. The home subscriber system (HSS) 535 may be communicatively coupled to the MME 530. The UE 515 of each example may include an LTE radio 520 and a WLAN radio 525. E-node B505-a and WLAN, especially with reference to Figure 5A AP505-b may be able to give UE515 access to PDN510 using the aggregation of one or more LTE component carriers or one or more WLAN component carriers. Using this access to PDN510, UE515 may communicate with peer entity 530. e-node B505-a may provide access to PDN510 through advanced packet core 512 (eg through data path 545) and WLAN AP505-b may provide direct access to PDN510 (eg through data path 550). .. In one aspect, LTE and WLAN data flows can flow through data paths 545 and 550.
[0079] MME530 may be a control node that handles signaling between UE515 and EPC512. In general, the MME530 can perform bearer and connection management. The MME530 can therefore be responsible for idle mode UE tracking and paging, bearer activation and deactivation, and SGW selection for UE515. The MME530 may communicate with the e-node B505-a via the S1-MME interface. The MME530 may further authenticate the UE515 and implement non-access stratum (NAS) signaling with the UE515.
[0080] HSS535, among other features, stores subscriber data, manages roaming restrictions, manages access point names (APNs) for subscribers, and associates subscribers with MME530. obtain. The HSS535 can communicate with the MME530 via the S6a interface defined by the Advanced Packet System (EPS) architecture standardized by the 3GPP organization.
[0081] All user IP packets transmitted over LTE may be forwarded to the SGW220 through the e-node B505-a, which is connected to the PDN gateway 525 via the S5 signaling interface and through the S11 signaling interface. Can be connected to MME530. The SGW220 resides in the user plane and can act as a mobility anchor for handovers between e-node Bs and between different access technologies. PDN gateway 525 may provide UE IP address allocation as well as other functions.
[0082] The PDN gateway 525 may provide connectivity to one or more external packet data networks, such as PDN510, via the SGi signaling interface. PDN510 may include Internet, Intranet, IP Multimedia Subsystem (IMS), Packet-Switched Streaming Service (PSS), and / or other types of PDN. ..
[0083] In this example, the user plane data between the UE 515 and the EPC 512 is one or more, regardless of whether the traffic flows through the LTE link route 545 or the WLAN link route 550. Can traverse the same set of EPS bearers (or data flows). Signaling or control plane data related to one or more sets of EPS bearers may be transmitted between the LTE radio 520 of UE515 and the MME530 of EPC512-b via the e-node B505-a.
[0084] Figure 5B shows an exemplary wireless communication system 500-b in which the e-node B505-a and WLAN AP505-b are colocated or otherwise in high speed communication with each other. In this example, EPS bearer relationship data between UE515 and WLAN AP505-b can be routed to e-node B505-a and then to EPC512. In this way, all EPS bearer relationship data can be forwarded along the same path between the e-node B505-a, the EPC512, the PDN510, and the peer entity 530.
[0085] With reference to FIG. 6, the e-node B605-a and the e-node B605-a in the wireless communication system 600 having an embodiment in which the multimode UE615 is configured to manage RLF recovery for the user equipment described herein. Communicating with WLAN (eg Wi-Fi) AP605-b. UE615 can be an example of one or more of UE120 in FIG. 1, UE215 in FIG. 2, UE320 in FIG. 3, UE415 in FIG. 4, and UE515 in FIGS. 5A and 5B. The e-node B605-a is the e-node B110 in FIG. 1, the e-node B205 in FIG. 2, the e-node B310 in FIG. 3, the e-node B405-a in FIG. 4, and the e-node B505-a in FIGS. 5A and 5B. It can be one or more of them. WLAN AP605-b can be an example of one or more of the WLAN AP405-b of FIG. 4 and the WLAN AP505-b of FIGS. 5A and 5B. As described above with respect to FIGS. 5A and 5B, the wireless communication system 600 has UE615 with e-node B605-a and WLAN. It can include WWAN (eg LTE or UMTS) RAT and WLAN (eg Wi-Fi) RAT so that it can communicate with both AP605-b, with WWAN and WLAN dataflows through various communication paths. To enable. This scenario is sometimes referred to as "dual connectivity" for UE615, with simultaneous or concurrent connections with both e-node B605-a and WLAN AP605-b.
[0086] UE615, e-node B605-a, and WLAN AP605-b perform WWAN (eg LTE) RLF recovery in UE615 according to different techniques (eg, 6 different aspects, as shown in Table 1 above). Can be configured to manage. More specifically, six aspects for processing WLAN data flow throughout the LTE RLF detection and recovery process will be described. Although these embodiments will be described separately, it will be appreciated that some or all of the embodiments may be configured to work with each other in any number of combinations in series and / or in parallel. Therefore, the combination of these embodiments can result in different alternative forms for WLAN data flow processing during LTE RLF.
[0087] UE615 includes WWAN radio 620 and WLAN radio 625, which may be the same as or similar to LTE radio 520 and WLAN radio 525 of UE515 as shown in FIGS. 5A and 5B. The WWAN radio 620 may be configured to provide communication between the UE 615 and the e-node B605-a over the WWAN radio link 661 (eg, via route 545 in Figures 5A and 5B), and the WLAN radio. The 625 may be configured to provide communication between the UE 615 and the WLAN AP605-b over the WLAN wireless link 662 (eg, via the data path 550 in FIGS. 5A and 5B). Each of the WWAN radio link 661 and the WLAN radio link 662 contains at least one data flow (eg, signaling data flow, user data flow, and so on). UE615 is LTE in UE615 An RLF configuration that detects RLF and is configured to handle all aspects related to RLF processing that are described in the 3GPP standard family, including, for example, RLF detection, cell reselection, and RRC connection reestablishment. Contains element 630. When the RLF of WWAN radio link 661 is detected, for example due to a bad RF condition, the RLF component 630 may be configured to communicate the RLF instruction 651 to the RLF data flow determination component 640.
[0088] The RLF data flow decision component 640 receives the RLF instruction 651 and, based on it, decides how to handle the LTE and WLAN data flows during the (upcoming) RLF recovery procedure. It is composed of. In some cases, in various aspects, the RLF data flow decision component 640 may include decision module 641, network configuration module 642, and / or rerouting module 643, for each of which each entity makes an RLF data flow decision. This will be described in detail according to the embodiments contained in the component 640. In all aspects described herein, the RLF dataflow determination component 640 is configured to suspend LTE dataflow upon detection of RLF and / or in response to RLF instruction 651, WWAN dataflow interruption. Includes module 644. The WWAN data flow suspend module 644 generates a suspend / resume instruction 655 to indicate whether the LTE data flow should be suspended and / or resumed and when it should be suspended and / or resumed. , Can be configured to transmit to WWAN radio 620. In some of the embodiments described herein, the RLF data flow decision component 640 includes a WLAN data flow interrupt module 645 configured to interrupt the WLAN data flow upon detection of the RLF. WLAN Radio Data Flow Suspend Module 645 Suspends to indicate if WLAN data flow should be suspended, maintained, and / or resumed and when it should be suspended, maintained, and / or resumed. It can be configured to generate a / maintain / resume instruction 657 and send it to the WLAN radio 625.
[0089] In addition, UE615 receives report instruction 653 from RLF dataflow decision component 640 and responds to generate measurement report 652 (s) to generate e-node B605-a and / or WLAN. Includes measurement reporting component 635 configured to send to AP605-b. The reporting instruction 653, depending on the particular embodiment, for example, which parameters and / or radio signal states should be measured, when and how often the measurements should be performed, which measurements should be reported, when and It may include instructions on how often measurements should be reported, where (s) measurement reports should be sent, and so on. Reporting instruction 653 may also include instructions from RLF data flow determination component 640 to remove or maintain all current WLAN measurement entries from the measurement report upon RLF detection. The measurement report 652 (s) may contain information relating to the radio signal status of the UE 615 on the LTE and / or WLAN networks measured by WWAN radio 620 and / or WLAN radio 625, respectively. .. The measurement reporting component 635 may operate in conjunction with WWAN radio 620 and / or WLAN radio 625 to execute reporting instruction 653. The measurement report component 635 may then communicate the measurement report 652 (s) to the WWAN radio 620 for transmission to the e-node B605-a. In one aspect (not shown), the measurement report component 635 may communicate the measurement report 652 (s) to the WLAN radio 625 for transmission to the WLAN AP605-b.
[0090] In some cases, in some of the aspects described herein, the e-node B605-a is configured to generate configuration 654 and send it to UE615, RLF data flow component 610. including. Configuration 654 can be any information, instructions, etc. that can be used to instruct the UE 615 on how to handle LTE and / or WLAN data flows during RLF recovery. For example, configuration 654 may be a quality of service (QoS) parameter that may allow the RLF data flow determination component 640 to determine the configuration based on it, and / or the QoS parameter may be an LTE data flow during RLF processing. And may include explicit instructions on how to handle WLAN data flows. In another example, configuration 654 is an access network discovery and selection (ANDSF) flag that indicates whether the WLAN data flow should be interrupted during the RLF, or may include it. function) Can be a policy. The RLF data flow decision component 640 on UE615 determines the decision module 641, network configuration module 642, and / or rerouting in deciding how to process LTE and WLAN data flows during RLF processing. To receive and utilize configuration 654 to determine which of Module 643 should be adopted (eg, which of the six aspects described herein should apply to this scenario). Can be configured in.
[0091] In some cases, in some of the aspects described herein, WLAN AP605-b allows LTE data flow to be maintained (eg, uninterrupted) during RLF recovery in UE615. Includes WWAN forwarding component 612 configured to do so. More specifically, the WWAN forwarding component 612 communicates with both UE615 and e-node B605-a (via communication connection 614) during RLF processing, receives LTE data flow from UE615, and e-nodes them. It may be configured to forward to B605-a and vice versa.
For various aspects of managing RLF recovery and the corresponding components of UE615, e-node B605-a, and WLAN AP605-b, with respect to FIGS. 7-12, which are call flow diagrams showing each aspect in turn. This will be further described.
[0093] With reference to FIG. 7, the call flow 700 is between the UE 615 and the e-node B605-a and the WLAN AP605-b in FIG. 6 according to the first aspect for managing RLF recovery for the UE. Indicates communication. In particular, in this first aspect, the device and method stop the LTE data flow when it detects an RLF, and in some cases stop the WLAN data flow and reestablish the data flow when recovering from the RLF. Keep the data flow mapping before the RLF for use. The action of the call flow 700 is performed by the UE 615, which includes the RLF component 630, the measurement reporting component 635, the WWAN radio 620, the WLAN radio 625, and the RLF data flow determination component 640. According to the first aspect, the RLF data flow decision component 640 includes a WWAN data flow break module 644, a WLAN data flow break module 645, and a decision module 641.
In 701, UE615's RLF component 630 detects RLF according to current 3GPP standards. At 702, the WWAN dataflow interruption module 644 suspends all LTE dataflows from being transmitted over the WWAN radio link 661 over the WWAN radio 620 to the e-node B605-a. Although not shown, the WWAN data flow interruption module 644 also indicates in measurement report component 652 that it deletes all WLAN measurement entry in the existing measurement report via report instruction 653. In 703, the decision module 641 has WLAN data flow on WLAN wireless link 662 via WLAN radio 625. Determine if transmission to AP605-b should be interrupted. If decision module 641 decides to suspend the WLAN data flow, as shown in the example of call flow 700 in 703a, the WLAN data flow is interrupted. If decision module 641 decides not to interrupt the WLAN data flow (not shown), the WLAN data flow is maintained during RLF processing (or resumed if it is temporarily interrupted after RLF detection). ).
[0095] At 704, RLF component 630 executes the cell reselection procedure according to the current 3GPP standard, sends an RRC connection reestablishment request message at 705, and receives an RRC connection reestablishment message at 706. Reestablish the connection between UE615 and e-node B605-a or another e-node B by doing so and sending an RRC connection reestablishment completion message at 707. In 708, the WLAN data flow is UE615 and WLAN if decision module 641 decides to suspend the WLAN data flow. Resumed with AP605-b. At 709, UE615 and e-node B605-a execute the RRC connection reconfiguration procedure according to the current 3GPP standard. Decision module 641 determines that RLF component 630 is executing the RRC connection reconfiguration procedure and, in response, commands measurement report component 635 to measure various network conditions. It may be configured to give report instruction 653 to component 635. The measurement report component 635 may do so and transmit the WLAN measurement report 652 to the e-node B605-a. At 710, WWAN dataflow interruption module 644 indicates to WWAN radio 620 that LTE dataflow should be resumed, at least in part, based on WLAN measurement report 652.
[0096] With reference to FIG. 8, the call flow 800 is between the UE 615 and the e-node B605-a and the WLAN AP605-b in FIG. 6 according to a second aspect for managing RLF recovery for the UE. Indicates communication. In particular, in this second aspect, the device and method stop the LTE data flow and the WLAN data flow when it detects an RLF. The action of call flow 800 is performed by UE 615, which includes RLF component 630, measurement reporting component 635, WWAN radio 620, WLAN radio 625, and RLF data flow determination component 640. According to the second aspect, the RLF data flow determination component 640 includes a WWAN data flow interruption module 644, a WLAN data flow interruption module 645, and a network configuration module 642.
In [0097] 801 the RLF component 630 of UE615 detects RLF according to the current 3GPP standard. At 802, the WWAN data flow interruption module 644 suspends all LTE data flows from being transmitted over the WWAN radio link 661 via the WWAN radio 620 to the e-node B605-a. Although not shown, the RLF data flow determination component 640 issues a report command 653 to the measurement report component 635 so that the measurement report component 635 can delete all the WLAN measurement report entities in the existing measurement report. give away. In the 803, the WLAN data flow interrupt module 645 allows the WLAN data flow to LAN over the WLAN wireless link 662 via the WLAN radio 625. Suspend sending to AP605-b. In 804, RLF component 630 executes the cell reselection procedure according to the current 3GPP standard, sends an RRC connection reestablishment request message in 805, and receives an RRC connection reestablishment message in 806. , 807, reestablish the connection between UE615 and e-node B605-a by sending an RRC connection reestablishment completion message. At 808, UE615 and e-node B605-a perform the RRC connection reconfiguration procedure for LTE according to the current 3GPP standard.
[0098] Network configuration module 642, at 809, detects that RLF component 630 is executing the RRC connection reconfiguration procedure and notifies WWAN data flow interruption module 644 that it will resume LTE data flow. Can be configured in. The network component 642 may also be configured to give the measurement report component 635 a report command 653 to instruct the measurement report component 635 to measure various network conditions. In the 810, the measurement reporting component 635 is sometimes referred to as a triggering event, the quality of the WLAN wireless link 662 is configurable and / or is given to the UE 615 by the network, as determined by the threshold value If it is determined to be greater than the static threshold), at 811 the measurement report component 635 sends the WLAN measurement report 652 to the e-node B605-a. In 812, the RLF data flow component 610 of e-node B605-a determines whether it is acceptable for WLAN wireless link 662 to resume WLAN data flow, at least in part, based on WLAN measurement report 652. To do. This is sometimes referred to as interaction determination because e-node B605-a determines whether UE615 can perform interactions, eg, dual connectivity between WLAN and LTE. In 813, UE615 and e-node B605-a perform the RRC connection reconfiguration procedure for WLAN according to the current 3GPP standard. The network configuration module 642 receives the instruction to determine the interaction of e-node B605-a, and therefore, at 814, instructs the WLAN data flow interruption module 645 to restart the WLAN data flow. In response, the WLAN data flow suspend module 645 may give the WLAN radio 625 a resume instruction 655 to resume the WLAN data flow over the WLAN radio link 662.
[0099] With reference to FIG. 9, the call flow 900 is between the UE 615 and the e-node B605-a and the WLAN AP605-b in FIG. 6 according to a third aspect for managing RLF recovery for the UE. Indicates communication. In particular, in this third aspect, the device and method stop the LTE data flow and the WLAN data flow when it detects an RLF. The action of call flow 900 is performed by UE 615, which includes RLF component 630, measurement reporting component 635, WWAN radio 620, WLAN radio 625, and RLF data flow determination component 640. According to the third aspect, the RLF data flow determination component 640 includes a WWAN data flow interruption module 644, a WLAN data flow interruption 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 regarding when the WLAN measurement report 652 is generated and sent to the e-node B605-a.
In [00100] 901, UE615's RLF component 630 detects RLF according to current 3GPP standards. At 902, the WWAN data flow interruption module 644 suspends all LTE data flows from being transmitted over the WWAN radio link 661 to the e-node B605-a via the WWAN radio 620. In this aspect (not shown), the RLF data flow determination component 640 is directed to the measurement report component 635 via report command 653 to maintain any existing WLAN measurement report entity in the measurement report. Command. In the 903, the WLAN data flow interrupt module 645 has the WLAN data flow on the WLAN wireless link 662 via the WLAN radio 625. Suspend sending to AP605-b. In 904, RLF component 630 executes the cell reselection procedure according to the current 3GPP standard, sends an RRC connection reestablishment request message in 905, and receives an RRC connection reestablishment message in 906. , 807, reestablish the connection between UE615 and e-node B605-a by sending an RRC connection reestablishment completion message.
[00101] In this aspect, the network configuration module 642 is measured to measure various network conditions once the network configuration module 642 determines that the RRC connection reestablishment process is underway by the RLF component 630. In order to command the reporting component 635, the measurement reporting component 635 may be configured to give the reporting command 653. The measurement report component 635 may be configured in 907 to generate and transmit a WLAN measurement report 652 as part of the RRC connection reestablishment completion message. In another aspect, the maintained existing measurement report may be sent as part of the RRC connection reestablishment completion message. At 908, e-node B605-a has received a WLAN measurement report 652, and based on it, at least in part, the RLF dataflow component 610 may make an interaction decision, eg, in UE615 Can be configured to determine if to resume. In 909, UE615 and e-node B605-a perform the RRC connection reconfiguration procedure for WLAN and LTE according to the current 3GPP standard if the interaction decision is to resume the WLAN data flow. If the interaction decision is not to resume the WLAN data flow (not shown), the RRC connection reconfiguration procedure in 909 may be for LTE only. Network configuration module 642 detects in 910 that RLF component 630 is executing the RRC connection reconfiguration procedure and sends a suspend / resume instruction 655 to WWAN radio 620 and on WWAN radio link 661. It may be configured to notify the WWAN data flow interruption module 644 that the LTE data flow will be resumed by resuming the LTE data flow. In 911, based on the interaction decision in 908, network configuration module 642 also conducts WLAN data flow over WLAN wireless link 662.
[00102] With reference to FIG. 10, the call flow 1000 communicates between the UE 615 of FIG. 6 and the e-node B605-a and the WLAN AP605-b according to a fourth aspect for managing the RLF for the UE. Is shown. In particular, in this fourth aspect, the device and method may stop the LTE data flow upon detection of the RLF and, in some cases, the WLAN data flow. The actions of the call flow 1000 are performed by the UE 615, including the RLF component 630, the measurement reporting component 635, the WWAN radio 620, the WLAN radio 625, and the RLF data flow determination component 640. According to the fourth aspect, the RLF data flow determination component 640 includes a WWAN data flow interruption module 644, a WLAN data flow interruption module 645, and a determination module 641.
[00103] In 1001, RLF component 630 of UE615 detects RLF according to the current 3GPP standard. At 1002, the WWAN data flow interruption module 644 suspends all LTE data flows from being transmitted over the WWAN radio link 661 over the WWAN radio 620 to the e-node B605-a. In 1003 (similar to the first aspect of call flow 700), the decision module 641 allows the WLAN data flow to LAN over WLAN wireless link 662 via WLAN radio 625. Determine if transmission to AP605-b should be interrupted. If the decision module 641 decides to suspend the WLAN data flow, as shown in the example of call flow 1000 in 1003a, the WLAN data flow is interrupted. If decision module 641 decides not to interrupt the WLAN data flow (not shown), the WLAN data flow is maintained during RLF processing (or if the WLAN data flow is temporarily interrupted when the RLF is detected). Will be restarted). At 1004, RLF component 630 executes the cell reselection procedure according to the current 3GPP standard, sends an RRC connection reestablishment request message at 1005, and receives an RRC connection reestablishment message at 1006. , 1007, reestablish the connection between UE615 and e-node B605-a by sending an RRC connection reestablishment completion message.
[00104] Decision module 641 is asked to measure report component 635 to measure various network conditions when network component 642 determines that the RRC connection reestablishment process is underway by RLF component 630. To order, the measurement reporting component 635 may be configured to give reporting order 653. The measurement report component 635 may be configured in 1007 to generate and send a WLAN measurement report 652 as part of the RRC connection reestablishment completion message. At 1008, e-node B605-a has received a WLAN measurement report 652, and based on it, at least in part, the RLF dataflow component 610 may make an interaction decision, eg, at UE615, a WLAN dataflow. Can be configured to determine if to resume. More specifically, the RLF dataflow component 610 in e-node B605-a may be configured to determine whether UE615's decision on whether to resume WLAN dataflow should be maintained or overridden. In 1009, UE615 and e-node B605-a perform the RRC connection reconfiguration procedure for WLAN and LTE according to the current 3GPP standard if the interaction decision is to resume the WLAN data flow. If the interaction decision is not to restart the WLAN data flow (not shown), the RRC connection reconfiguration procedure in 1009 may be for LTE only.
[00105] At 1010, network configuration module 642 detects that LTE component 630 is executing the RRC connection reconfiguration procedure and sends a resume instruction 655 to WWAN radio 620 and over WWAN radio link 661. It may be configured to notify the WWAN data flow interruption module 644 that the LTE data flow will be resumed by resuming the LTE data flow of. At 1011 the network configuration module 642 also resumes the WLAN data flow by sending a resume instruction 656 to the WLAN radio 625 to resume the WLAN data flow on the WLAN radio link 662 based on the interaction decision 1008. It may be configured to notify the WLAN Data Flow Interruption Module 645 of what to do.
[00106] With reference to FIG. 11, the call flow 1100 communicates between the UE 615 of FIG. 6 and the e-node B605-a and the WLAN AP605-b according to a fifth aspect for managing the RLF for the UE. Is shown. In particular, in this fifth aspect, the device and method stop the LTE data flow when it detects an RLF. The action of call flow 1100 is performed by UE 615, which includes RLF component 630, measurement reporting component 635, WWAN radio 620, WLAN radio 625, and RLF data flow determination component 640. According to the fifth aspect, the RLF data flow determination component 640 includes a WWAN data flow interruption module 644, a WLAN data flow interruption module 645, and a network configuration module 642.
[00107] In 1101, the RLF data flow component 610 of e-node B605-a commands the UE 615 as to whether to suspend or maintain the WLAN data flow during RLF processing in an RRC connection reconfiguration message (eg, for example). Send configuration 654) to UE615. In the call flow 1100 example, the RRC connection reconfiguration message sent at 1101 instructs UE615 to maintain the WLAN data flow during RLF processing. In another example (not shown), the RRC connection reconfiguration message sent at 1101 may instruct UE615 to interrupt the WLAN data flow during RLF processing.
[00108] In 1102, RLF component 630 of UE615 detects RLF according to the current 3GPP standard. At 1103, the WWAN data flow interruption module 644 suspends all LTE data flows from being transmitted over the WWAN radio link 661 over the WWAN radio 620 to the e-node B605-a. In 1104, RLF component 630 executes the cell reselection procedure according to the current 3GPP standard, sends an RRC connection reestablishment request message in 1105, and receives an RRC connection reestablishment message in 1106. , 1107 reestablishes the connection between UE615 and e-node B605-a by sending an RRC connection reestablishment completion message. At 1108, UE615 and e-node B605-a perform an RRC connection reconfiguration procedure for LTE according to the current 3GPP standard. Network configuration module 642 is configured in 1109 to detect that RLF component 630 is executing the RRC connection reconfiguration procedure and notify WWAN data flow interruption module 644 to resume LTE data flow. obtain. In a mode in which e-node B605-a configures UE615 to interrupt the WLAN data flow during RLF processing for each RRC connection reconfiguration message (not shown), in 1101, network configuration module 642 provides WLAN data. The WLAN data flow interruption module 645 may be notified that the flow will be resumed.
[00109] With reference to FIG. 12, the call flow 1200 communicates between the UE 615 of FIG. 6 and the e-node B605-a and the WLAN AP605-b according to a sixth aspect for managing the RLF for the UE. Is shown. In particular, in this sixth aspect, the device and method optionally reroute LTE data flow upon detection of RLF. The action of call flow 1200 is performed by UE 615, which includes RLF component 630, measurement reporting component 635, WWAN radio 620, WLAN radio 625, and RLF data flow determination component 640. According to the sixth aspect, the RLF data flow determination component 640 includes a WWAN data flow interruption module 644, a WLAN data flow interruption module 645, and a rerouting module 643.
In [00110] 1201, RLF component 630 detects RLF according to the current 3GPP standard and gives RLF indication 651 to RLF data flow determination component 640. At 1202, the LTE data flow interruption module may be configured to send an interruption instruction 655 to the WWAN radio 620. In addition, the rerouting module 643 reroutes the signaling radio bearer (eg SRB1) to WLAN AP605-b via WLAN radio 625 until the LTE connection can be reestablished between UE615 and enode B605-a. Route and reroute all LTE data flows (for example, offload). At 1203, RLF component 630 performs a cell reselection process as a result of detecting RLF according to the current 3GPP standard. In 1204, the RLF data flow determination component 640 generates a WLAN measurement report 652 on the measurement report component 635 via report command 653 and a WLAN measurement report 652 on the WLAN AP605-b via the WLAN radio 625. Instruct to send.
[00111] In 1205, the WWAN forwarding component 612 of the WLAN AP605-b forwards the WLAN measurement report 652 to the e-node B605-a via the backhaul. In 1206, the RLF dataflow component 610 of e-node B605-a has the LTE dataflow WLAN until the RLF recovery process is complete and LTE communication is reestablished (for example, until the LTE dataflow can be resumed). Make an interaction decision as to whether it should be rerouted via AP605-b. At 1207, e-node B605-a sends its interaction determination to WLAN AP605-b. In the call flow 1200 example, the e-node B605-a is a WLAN Decide to continue rerouting LTE data flow through AP605-b. In 1208, WLAN AP605-b forwards WLAN interaction commands (eg, interaction determination) to UE615. In 1209, rerouting module 643 notifies WWAN dataflow interruption module 644 and WLAN dataflow interruption module 645 to resume LTE dataflow and continue WLAN dataflow over WLAN wireless link 662, respectively. To do. Both the LTE data flow and the WLAN data flow are transmitted over the WLAN wireless link 662 via the WLAN radio 625.
[00112] On the other hand, the RLF component 630 sends an RRC connection reestablishment request message at 1210, receives an RRC connection reestablishment message at 1211, and sends an RRC connection reestablishment completion message at 1212. By doing so, the connection between UE615 and e-node B605-a is reestablished. Rerouting module 643 commands measurement reporting component 635 to measure various network conditions when network configuration module 642 determines that the RRC connection reestablishment process is underway by RLF component 630. Therefore, it may be configured to give reporting instruction 653 to measurement reporting component 635. The measurement report component 635 may be configured in 1212 to generate LTE and / or WLAN measurement report 652 and send the WLAN measurement report as part of the RRC connection reestablishment completion message.
[00113] When the reestablishment procedure is complete, UE615 and e-node B605-a communicate again over LTE and SRB1 is reestablished. Therefore, at 1213, e-node B605-a determines whether the LTE data flow currently being transmitted over WLAN radiolink 662 should be rerouted (eg, fallback) to WWAN radiolink 661. Therefore, RLF data flow component 610 makes interaction decisions based at least in part on WLAN measurement report 652. In 1214, UE615 and e-node B605-a perform an RRC connection reconfiguration procedure for LTE according to the current 3GPP standard if the interaction decision is to resume LTE data flow. If the interaction decision is not to restart the LTE data flow (not shown), the RRC connection reconfiguration procedure in 1214 may not be done at this point. The rerouting module 643 resumes the LTE data flow by sending a resume instruction 655 to the WWAN radio 620 and resuming the LTE data flow on the WWAN radio link 661 in 1215. 644 can be notified.
[00114] With reference to FIG. 13, for example, among UE120 in FIG. 1, UE215 in FIG. 2, UE320 in FIG. 3, UE415 in FIG. 4, UE515 in FIGS. 5A and 5B, and UE615 in FIGS. 6-12. One way to manage wireless link failure recovery by user equipment, such as 1300. For simplicity, aspects of Method 1300 will be described as being performed by UE615 communicating with e-node B605-a and / or WLAN AP605-b, which is outlined by FIG. More specifically, aspects of method 1300 may be performed, for example, by RLF component 630, measurement reporting component 635, RLF data flow determination component 640, WWAN radio 620, and / or WLAN radio 625.
[00115] In 1305, method 1300 comprises establishing communication using a first radio access technology (RAT) and a second RAT. For example, UE615 and / or WWAN radio 620 and WLAN radio 625 communicate with the e-node B605-a via the first RAT of WWAN (eg LTE), respectively, and WLAN (eg Wi-). It can be configured to establish communication with the WLAN AP605-b via a second RAT in Fi).
[00116] In 1310, method 1300 comprises transmitting at least one data flow via a first RAT and at least one data flow via a second RAT. For example, UE615 and / or WWAN radio 620 sends LTE data flow to e-node B605-a over WWAN radio link 661, and UE615 and / or WLAN radio 625 is WLAN AP605 over WLAN radio link 662. Send WLAN data flow to -b. In one aspect, WWAN (eg LTE) data flows can be, or are associated with, bearers, traffic flow templates (TFTs), transmission control protocol (TCP) connections, and / or quality of service (QoS) classes. obtain.
[00117] In 1315, method 1300 comprises detecting a radio link failure (RLF) between the user equipment and the first RAT. For example, UE615 and / or RLF component 630 may be configured to detect RLF according to the procedures described in the 3GPP standard.
[00118] In 1320, method 1300 involves determining whether at least one data flow via a second RAT should be maintained when RLF is detected. For example, whether the RLF data flow decision component 640 receives the RLF instruction 651 from the RLF component 630 and responds to the RLF detection to maintain the WLAN data flow during the RLF recovery process (eg, should it be interrupted?). , Should not be interrupted).
[00119] According to the second and third aspects, and in some cases in the first, fourth, and fifth aspects, method 1300 is one or more data flows via a second RAT. For example, deciding to suspend the transmission of a WLAN data flow) may include suspending the transmission of one or more data flows (eg, a WLAN data flow) via a second RAT. In some embodiments, Method 1300 includes detecting recovery from RLF and resuming transmission of one or more data flows (eg, WLAN data flows) via a second RAT. obtain. In some embodiments, method 1300 detects recovery from RLF and resumes transmission of one or more interrupted data flows (eg, LTE data flow) via a first RAT. And can be included. In some embodiments, method 1300 detects recovery from the RLF, receives configuration 654 from the first RAT (eg e-node B605-a), and second RAT (eg WLAN). Resuming the transmission of one or more interrupted data flows (eg, LTE data flow) over the first RAT (eg, LTE) and information related to the second RAT (eg, WLAN) ) May include sending to. In this case, the configuration may be received from the first RAT in response to transmitting the information. The information can be a measurement report for LTE and / or WLAN. The information can be one indication per WLAN data flow that indicates whether the UE has interrupted transmission for a particular data flow (eg, WLAN data flow) via a second RAT RLF. The information is per LTE data flow as to whether the UE will resume sending for each of the data flows over the first RAT (eg LTE) or the second RAT (eg WLAN). There can be one instruction per and one instruction per WLAN data flow.
[00120] According to a sixth aspect, and in some cases in the first, fourth, and fifth aspects, method 1300 is at least one data flow via a second RAT (eg, WLAN data flow). ) May include deciding to keep the transmission. In some aspects, the decisions that are made in the UE are the network configuration received in the UE (eg, configuration 654), the access network discovery and selection function (ANDSF) policy (eg, flags), quality of service (QoS) parameters, and /. Or based on at least one of the UE implementations.
[00121] According to a sixth aspect, method 1300 may include transmitting control signaling (eg, LTE RRC signaling, NAS signaling, etc.) via a second RAT (eg, WLAN) during RLF. ..
[00122] Referring to FIG. 14, the method 1400 for managing wireless link failure recovery in the user equipment is, for example, e-node B110 in FIG. 1, e-node B205 in FIG. 2, e-node B310 in FIG. 3, FIG. Can be executed by the first e-node B, which can be one of the e-node B405-a of FIG. 5A, the e-node B505-a of FIGS. 5A and 5B, and the e-node B605-a of FIGS. 6-12. .. For simplicity, aspects of Method 1400 will be described as being performed by the e-node B605-a communicating with UE615 and / or WLAN AP605-b, which is outlined by FIG. In the method 1400 example, the e-node B605-a configures UE615 to process the WLAN data flow during RLF processing.
[00123] In 1405, method 1400 comprises establishing a first communication connection with a user device via a first radio access technology (RAT). For example, e-node B605-a is configured to establish a first communication connection with UE615 over LTE. In one aspect, establishing a first communication connection is the result of UE615 moving from idle to connected, or as a result of UE615 being handed over from another enode B to enode B605-a. Can be.
[00124] In 1410, method 1400 includes receiving an instruction that a second communication connection with the user equipment is established via the second RAT, wherein the second communication connection is at least one. Send two data flows. For example, e-node B605-a receives an instruction from UE615 that UE615 is also communicating with WLAN AP605-b and that UE615 is sending at least one WLAN data flow to WLAN AP605-b over WLAN. It is configured to do.
[00125] In 1415, method 1400 comprises receiving a radio link failure (RLF) recovery instruction for the first communication connection from the user equipment after the radio link failure for the first communication connection. For example, e-node B605-a, from UE615, UE615 is RLF, just as UE615 is communicating with e-node B605-a over LTE and UE615 is communicating with WLAN AP605-b over WLAN. It may be configured to receive instructions that it is recovering from.
[00126] In 1420, method 1400 comprises determining whether at least one data flow can be maintained on the second communication connection via the second RAT during a radio link failure. For example, the RLF data flow component 610 of e-node B605-a may be configured so that UE 615 determines whether the WLAN data flow should be maintained or interrupted during the RLF.
[00127] In 1425, method 1400 comprises indicating to the user equipment whether at least one data flow transmission should be maintained for each data flow over the second communication connection via the second RAT. .. For example, the e-node B605-a may be configured to indicate to UE615 (eg, via configuration 654) whether the WLAN data flow should be interrupted or maintained for each data flow. The e-node B605-a may direct the UE 615 via a configuration message (eg, an RRC message) or a data message sent by the e-node B605-a to the UE 615.
[00128] With reference to FIG. 15, the method 1500 for managing wireless link failure recovery in the user equipment is, for example, e-node B110 in FIG. 1, e-node B205 in FIG. 2, e-node B310 in FIG. 3, FIG. Can be executed by a second e-node B, which can be one of the e-node B405-a of, the e-node B505-a of FIGS. 5A and 5B, and the e-node B605-a of FIGS. 6-12. .. For simplicity, aspects of Method 1500 will be described as being performed by the e-node B605-a communicating with UE615 and / or WLAN AP605-b, which is outlined by FIG. In the method 1500 example, e-node B605-a handles RLF recovery for UE615. The first e-node B described as performing aspects of method 1400 may or may not be the same as the second e-node B described as performing aspects of method 1500.
[00129] In 1505, method 1500 includes receiving a wireless link failure recovery instruction for the first communication connection from the user equipment. For example, e-node B605-a receives an instruction that UE615 is recovering from LTE RLF.
[00130] In 1510, method 1500 includes receiving an instruction that a second communication connection with the user equipment is established via the second RAT, wherein the second communication connection is at least one. Related to one data flow. For example, e-node B605-a receives an instruction from UE615 that UE615 is communicating with WLAN AP605-b over WLAN wireless link 662 and the WLAN data flow is being sent by UE615 to WLAN AP605-b. To do.
[00131] In 1515, method 1500 includes determining whether at least one data flow can be resumed on the second communication connection via the second RAT after wireless link failure recovery. For example, the RLF dataflow component 610 of e-node B605-a may be configured to determine if WLAN dataflow can be resumed on the WLAN after UE615 recovers from the RLF.
[00132] In 1520, method 1500 includes indicating to the user equipment whether transmission of at least one data flow should be resumed over the second communication connection via the second RAT. For example, e-node B605-a may be configured to indicate to UE615 (eg, via configuration 654) whether to resume sending WLAN dataflows over the WLAN.
[00133] According to the first, second, third, fourth, and sixth aspects, Method 1500 may in some cases provide at least one measurement report relating to a second RAT (eg, WLAN). Whether the UE 615 can resume sending at least one data flow (eg, WLAN data flow) over the second RAT based on the reception and at least partly based on at least one measurement report. Including to decide.
[00134] According to some embodiments, the method 1500 comprises receiving multiple instructions, each of which the UE 615 has at least one data via a second RAT during the RLF. Indicates whether a particular transmission of a flow (eg, WLAN data flow) has been interrupted, where each of the instructions is at least one data flow via a second RAT (eg, WLAN data flow). ) Is associated with a particular one. In addition, Method 1500 may in some cases receive at least one measurement report (eg, WLAN measurement report) related to the second RAT from UE615 and the first communication connection (eg, LTE) may be re-established. It involves detecting that it has been established and deciding whether to resume transmission over a second RAT (eg WLAN) based on at least one measurement report. In one example, the measurement report (s) may be sent as part of an RRC connection reestablishment message.
[00135] According to some embodiments, Method 1500 further indicates that, in some cases, transmission of at least one data flow (eg, LTE data flow) via a second RAT was maintained during the RLF. To receive, detect that the first communication connection (eg LTE) has been reestablished, and at least one data flow maintained on the second RAT (eg WLAN) during RLF Includes determining whether an LTE data flow (eg, LTE data flow) should be transmitted via a first RAT (eg, LTE). In one example, the further instruction could be, for example, a second RAT-related measurement report (eg, a WLAN measurement report) that could be sent as part of an RRC connection reestablishment message.
[00136] With reference to FIG. 16, hardware for apparatus 1600 that employs processing system 1614, described herein, that comprises an embodiment configured to allocate user equipment processing power among a plurality of access nodes. An example of the implementation is shown. In this example, processing system 1614 can be implemented using the bus architecture schematically represented by bus 1602. Bus 1602 may include any number of interconnect buses and bridges, depending on the particular application of processing system 1614 and overall design constraints. Bus 1602 links to each other various circuits, including one or more processors, schematically represented by processor 1604, and a computer-readable medium, roughly represented by computer-readable media 1606. In one aspect in which device 1600 adopting processing system 1614 is, for example, e-node B605-a, bus 1602 also links RLF data flow component 610. The device 1600 that employs the processing system 1614 is, for example, WLAN. In one aspect, AP605-b, bus 1602 also links WWAN forwarding component 612. In one aspect in which the device 1600 that employs the processing system 1614 is, for example, UE615, the bus 1602 includes the RLF component 630, the measurement reporting component 635, the RLF data flow determination component 640, and the WWAN radio 620. , Also links with WLAN radio 625. Note that transceiver 1610 can be part of WWAN radio 620 and WLAN radio 625 and vice versa. Bus 1602 can also link a variety of other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, but these circuits are well known in the art and therefore no more. I will not explain. It should be understood that any aspect of FIG. 16 can be implemented by hardware, software, and / or a combination thereof. In one example, any of the operations or functions configured for the device of FIG. 16 to support it may be implemented using the processor 1604 and / or the computer-readable medium 1606.
[00137] Bus interface 1608 provides an interface between bus 1602 and transceiver 1610. Transceiver 1610 provides a means for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 1612 (eg, keypad, display, speaker, microphone, joystick) may also be provided.
[00138] Processor 1604 is responsible for managing bus 1602 and for general processing, including execution of software stored on the computer-readable medium 1606. When executed by processor 1604, the software causes processing system 1614 to perform the various functions described herein for allocating user equipment processing power among multiple access nodes for a particular device. The computer-readable medium 1606 can also be used to store data manipulated by processor 1604 when running software.
[00139] Terms such as "components", "modules", and "systems" used in this application are not limited, but include hardware, firmware, hardware-software combinations, software, or running software. , Computer-related entities shall be included. For example, components can be, but are not limited to, processes, processors, objects, executables, threads of execution, programs, and / or computers that run on the processor. As an example, both an application running on a computing device and that computing device can be components. One or more components can reside within a process and / or execution thread, one component can be located on one computer, and / or distributed among two or more computers. Moreover, these components can be executed from various computer-readable media that store various data structures. These components are one, such as data from one component that interacts over a signal with another component in a local system, in a distributed system, and / or on a network such as the Internet with other systems. Or it can communicate via local and / or remote processes, such as by signals with multiple data packets.
[00140] Further, the present specification describes various aspects relating to a terminal which can be a wired terminal or a wireless terminal. The terminal is a system, device, subscriber unit, subscriber station, mobile station, mobile, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, communication device, user agent, user device, or user device ( Sometimes called UE). Wireless terminals can be cellular phones, satellite phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless connectivity, computing devices, or wireless. It can be another processing device connected to the modem. Moreover, various aspects of the base station are described herein. Base stations can be used to communicate with (s) wireless terminals and are sometimes referred to as access points, node B, or some other term.
[00141] Moreover, the term "or" shall mean a comprehensive "or" rather than an exclusive "or". That is, unless otherwise specified, or unless otherwise apparent from the context, the phrase "X uses A or B" shall mean either a natural, comprehensive permutation. That is, the phrase "X adopts A or B" is satisfied by either X adopts A, X adopts B, or X adopts both A and B. .. In addition, the articles "a" and "an" used in this application and the appended claims are unless otherwise specified or unless it is clear from the context that they should cover the singular. It should be interpreted as generally meaning "one or more".
[00142] The techniques described herein can be used in a variety of wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA) and cdma2000. UTRA includes wideband CDMA (W-CDMA®) and other variants of CDMA. In addition, cdma2000 covers IS-2000, IS-95 and IS-856 standards. TDMA systems can implement wireless technologies such as Global Systems for Mobile Communications (GSM). OFDMA systems include advanced UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802.20, Flash-OFDM® and other wireless. The technology can be implemented. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE and GSM are listed in documents from an organization called the "Third Generation Partnership Project" (3GPP). In addition, cdma2000 and UMB are mentioned in a document from an organization called "3rd Generation Partnership Project 2" (3GPP2). In addition, such wireless communication systems have an unqualified spectrum, 802.
[00143] Various aspects or features are presented with respect to a system that may include several devices, components, modules, and the like. It should be understood and understood that various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. described with reference to the figures. A combination of these techniques can also be used.
[00144] The various exemplary logics, logic blocks, modules, and circuits described with respect to the embodiments disclosed herein are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), fields. Implemented using a programmable gate array (FPGA) or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. Or can be executed. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. Processors are also implemented as a combination of computing devices, such as a combination of DSP and microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. obtain. In addition, at least one processor may include one or more modules that can operate to perform one or more of the steps and / or actions described above.
[00145] Further, the steps and / or actions of the methods or algorithms described with respect to the aspects disclosed herein are performed directly in hardware, in software modules executed by a processor, or the like. It can be carried out in combination of the two. Software modules are RAM memory, flash memory, ROM memory, EPROM memory, EEPROM® memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage known in the art. Can be resident in the medium. An exemplary storage medium may be coupled to the processor so that the processor can read information from the storage medium and write the information to the storage medium. Alternatively, the storage medium can be integrated into the processor. Moreover, in some embodiments, the processor and storage medium may reside in the ASIC. In addition, the ASIC can reside in the user terminal. Alternatively, the processor and storage medium may reside as individual components in the user terminal. Moreover, in some embodiments, the steps and / or actions of the method or algorithm may be one or any combination of code and / or instructions on a machine-readable medium and / or computer-readable medium that may be incorporated into a computer program product. Or can be resident as a set thereof.
[00146] In one or more aspects, the functionality described may be implemented in hardware, software, firmware, or a combination thereof. When implemented in software, a function may be stored on a computer-readable medium as one or more instructions or codes, or transmitted on a computer-readable medium. Computer-readable media include both computer storage media and computer communication media, including any medium that allows the transfer of computer programs from one location to another. The storage medium can be any available medium that can be accessed by a computer. By way of example, but not by limitation, such computer-readable media are RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage or other magnetic storage device, or any desired form of instruction or data structure. Any other medium that can be used to carry or store program code and can be accessed by a computer can be provided. Also, any connection may be referred to as a computer-readable medium. For example, software sends from a website, server, or other remote source using coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL), or wireless technology such as infrared, wireless, and microwave. Where so, coaxial cables, fiber optic cables, twisted pairs, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the definition of medium. The discs and discs used herein are compact discs (CDs), laser discs (registered trademarks) (discs), optical discs, and digital versatile discs (DVDs). ), Flop (registered trademark) disc (disk) and blu-ray (registered trademark) (disc), the disc (disk) usually plays back data magnetically, and the disc (disc) is a disk. The data is optically regenerated with a laser. The above combinations should also be included within the scope of computer readable media.
[00147] The above disclosure discusses exemplary embodiments and / or embodiments, but varies without departing from the scope of the described embodiments and / or embodiments defined by the appended claims. It should be noted that changes and modifications may be made herein. In addition, the elements of the described embodiments and / or embodiments may be described or claimed in the singular, but the plural is contemplated unless a limitation to the singular is explicitly stated. Moreover, all or part of any other aspect and / or embodiment may be utilized with all or part of any other aspect and / or embodiment, unless otherwise specified.
19 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19
Every citation, both ways
| Document | Relation | Office | Category | Cited during | Relevant claims |
|---|---|---|---|---|---|
| US12367031B2 | Cited by | United States of America | – | Applicant | – |
| WO2013019501A1 | Cites | World Intellectual Property Organization (WIPO) | X | Search report | 1-38 |
| JP2014524685A | Cites | Japan | A | Search report | – |
17 members in 7 offices
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 201361866862 | United States of America | P | |
| 201361866862 | United States of America | P | |
| 61866862 | United States of America | – | |
| 14447331 | United States of America | – | |
| 201414447331 | United States of America | A | |
| 201414447331 | United States of America | A | |
| 14447331 | – | – | – |
| 61866862 | – | – | – |
| US201361866862P | – | – | – |
| US201414447331 | – | – | – |
Members17
| Document | Office | Kind | |
|---|---|---|---|
| US2015049707A1 | United States of America | A1 | |
| WO2015023449A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2015023449A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CN105474738A | China | A | |
| KR20160042915A | Republic of Korea | A | |
| EP3033918A2 | European Patent Office (EPO) | A2 | |
| US9414430B2 | United States of America | B2 | |
| JP2016530811A | Japan | A | |
| KR101728644B1 | Republic of Korea | B1 | |
| JP2017225146AThis record | Japan | A | |
| JP6522612B2 | Japan | B2 | |
| CN105474738B | China | B | |
| CN110049576A | China | A | |
| EP3033918B1 | European Patent Office (EPO) | B1 | |
| JP6752763B2 | Japan | B2 | |
| ES2843530T3 | Spain | T3 | |
| CN110049576B | China | B |
15 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Re-examination (zenchi) completed and case transferred to appeal boardAppealJAPANESE INTERMEDIATE CODE: A912A912 | A912 | |
| Transfer to examiner for re-examination before appeal (zenchi)AppealJAPANESE INTERMEDIATE CODE: A911A911 | A911 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 2017225146
- Publication, DOCDB
- 2017225146
- Publication, EPODOC
- JP2017225146
- Application
- 146702
- Application, DOCDB
- 2017146702
- Application, EPODOC
- JP20170146702
Titles2
- Japanese
- WWANおよびWLANに接続されたユーザ機器のための無線リンク障害回復を管理するための技法
- English
- Techniques for managing wireless link failure recovery for WWAN and user equipment connected to WLAN
Classification
- CPC, 9
- H04W76/19
- H04W76/25
- H04W76/16
- H04W76/34
- H04W76/15
- H04W76/20
- H04W88/06
- H04W24/10
- H04W36/22
- IPC, 2
- H04W24 04
- H04W4 00