Source: http://patents.com/us-10178598.html
Timestamp: 2019-01-18 15:41:25
Document Index: 54556386

Matched Legal Cases: ['Application No. 16206330', 'Application No. 2016', 'Application No. 15789478', 'Application No. 15789818', 'Application No. 104110683', 'Application No. 2016133746', 'Application No. 2', 'Application No. 10', 'Application No. 2015256474', 'Application No. 10', 'Application No. 105137651', 'Application No. 201639434', 'Application No. 2', 'Application No. 2015255871', 'Application No. 2016', 'Application No. 2', 'Application No. 2016', 'Application No. 10', 'Application No. 61', 'Application No. 61', 'Application No. 62']

US Patent # 1,017,8598. Systems, devices, and methods for interworking between a universal mobile telecommunications system (UMTS) network and a wireless local area network (WLAN) - Patents.com
United States Patent 10,178,598
Sirotkin , et al. January 8, 2019
Systems, devices, and methods for interworking between a universal mobile telecommunications system (UMTS) network and a wireless local area network (WLAN)
Sirotkin; Alexander (Petach Tikva, IL), Burbidge; Richard (Shrivenham, GB), Fong; Mo-Han (Sunnyvale, CA), Himayat; Nageen (Fremont, CA), Choi; Hyung-Nam (Hamburg, DE)
Family ID: 1000003752399
15/822,368
US 20180077623 A1 Mar 15, 2018
14583057 Dec 24, 2014 9877256
62029936 Jul 28, 2014
61990693 May 8, 2014
61969790 Mar 24, 2014
Current CPC Class: H04W 36/30 (20130101); H04W 48/00 (20130101); H04W 28/18 (20130101); H04W 88/06 (20130101); H04W 36/14 (20130101); H04W 40/12 (20130101); H04W 84/12 (20130101); H04W 36/0066 (20130101)
Current International Class: H04W 36/00 (20090101); H04W 36/30 (20090101); H04W 48/00 (20090101); H04W 36/14 (20090101); H04W 28/18 (20090101); H04W 40/12 (20090101); H04W 84/12 (20090101); H04W 88/06 (20090101)
2013/0242897 September 2013 Meylan et al.
2013/0308445 November 2013 Xiang et al.
2014/0092742 April 2014 Chou
2014/0153511 June 2014 Sirotkin
2015/0195759 July 2015 Sirotkin et al.
2015/0327139 November 2015 Sirotkin et al.
2015/0382281 December 2015 Sirotkin
2016/0021570 January 2016 Sirotkin et al.
2016/0044550 February 2016 Lee et al.
20050104388 Nov 2005 KR
20130094826 Aug 2013 KR
2421941 Jun 2011 RU
2012/040251 Mar 2012 WO
2014/113103 Jul 2014 WO
2014163696 Oct 2014 WO
2014/182341 Nov 2014 WO
Extended European Search Report dated May 18, 2017 from European Divisional Application No. 16206330.9, 15 pages. cited by applicant .
Office Action dated Oct. 17, 2017 from Japanese Patent Application No. 2016-565046, 7 pages. cited by applicant .
Extended European Search Report dated Dec. 14, 2017 from European Patent Application No. 15789478.3, 18 pages. cited by applicant .
Extended European Search Report dated Dec. 13, 2017 from European Patent Application No. 15789818.0, 16 pages. cited by applicant .
Intel Corporation, "Connected mode procedures and RRC signaling of WLAN/3GPP Radio Interworking for LTE," 3GPP TSG-RAN WG2 Meeting #86, R2-142136, Current version: 12.1.0, Work item code: UTRA_LTE_WLAN_interw-Core, May 19-May 23, 2014, Seoul, South Korea, 20 pages. cited by applicant .
Intel Corporation, "Idle mode procedures of WLAN/3GPP Radio Interworking for LTE," 3GPP TSG-RAN WG2 Meeting #86, R2-142130, Current version: 12.1.0, Work item code: UTRA_LTE_WLAN_interw-Core, May 19-May 23, 2014, Seoul, South Korea, 4 pages. cited by applicant .
LG Electronics Inc., "Text proposal on WLAN 3GPP radio interworking solution 2," 3GPP TSG-RAN2 Meeting 083, R2-132849, Agenda Item: 5.1, Aug. 19-Aug. 23, 2013, Barcelona, Spain, 4 pages. cited by applicant .
Intel et al., "Text Proposal on WLAN/3GPP radio interworking solution 1," 3GPP TSG-RAN2 Meeting #83bis, R2-133698, Agenda item: 5.1, Oct. 7-11, 2013, Ljubljana, Slovenia, 4 pages. cited by applicant .
LG Electronics Inc., "Assistance information and signaling procedure," 3GPP TSG-RAN2 Meeting #85, R2-140771, Agenda item: 5.1, Feb. 10-Feb. 14, 2014, Prague, Czech Republic, 4 pages. cited by applicant .
Alcatel-Lucent et al., "RAN parameters for traffic steering," 3GPP TSG-RAN WG RAN3#85, R2-140715, Agenda item: 5.1., Feb. 10-14, 2014, Prague, Czech Republic, 6 pages. cited by applicant .
Intel, "Introduction of WLAN/3GPP radio interworking functionality into specifications for LTE and UMTS," 3GPP TSG-RAN2 Meeting #85bis, R2-141758, Agenda item: 5.1.2, Mar. 31-Apr. 4, 2014, Valencia, Spain, 10 pages. cited by applicant .
Intel, "Proposed way forward on WLAN/3GPP radio interworking," 3GPP TSG-RAN2 Meeting #85, R2-140842, Agenda item: 5.1, Feb. 10-14, 2014, Prague, Czech Republic, 17 pages. cited by applicant .
Intel Corporation, "Connected mode procedures and RRC signaling of WLAN/3GPP Radio Interworking for LTE," 3GPP TSG-RAN WG2 Meeting #85bis, R2-141625, Change Request 36.331, CR CRNum, rev. Current version: 12.1.0, Mar. 31-Apr. 4, 2014, Valencia, Spain, 9 pages. cited by applicant .
Alcatel-Lucent et al., "Stage 3 design considerations for 3GPP-WiFi radio interworking," 3GPP TSG-RAN WG RAN3#85bis, R2-141574, Agenda Item: 5.1.3, Mar. 31-Apr. 4, 2014, Valencia, Spain, 4 pages. cited by applicant .
3GPP, "UTRAN: General Description; Stage 2 (Release 12)," 3GPP TS 25.300 V0.1.0 (Feb. 2014), Feb. 26, 2014, 5 pages. cited by applicant .
3GPP, "Umiversal Terrestrial Radio Access Network (UTRAN); General description; Stage 2 (Release 12)," 3GPP TS 25.300 V12.2.0 (Sep. 2014), Sep. 23, 2014, 12 pages. cited by applicant .
3GPP, "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode Release 12)," 3GPP TS 25.304 V12.1.0 (Mar. 2014), Mar. 19, 2014, 54 pages. cited by applicant .
3GPP, "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode (Release 12)," 3GPP TS 25.304 V12.3.0 (Sep. 2014), Sep. 26, 2014, 58 pages. cited by applicant .
3GPP, "Radio Resource Control (RRC); Protocol specification (Release 12)," 3GPP TS 25.331 V12.1 .0 (Mar. 2014), Mar. 20, 2014, Sections: 8.1.1.1.2, 8.1.1.6.23, 8.2.2.3, 8.3.1.12, 8.5.2, 8.6.7.29, 8.6.7.30, 10.1.1, 10.2.8, 10.2.48.8.26, 10.2.62, 10.3.8.18c, 10.3.9b, 10.3.10, 11.2, 11.3, 11.4, 13.1, 13.4.32, 13.4.69, 13.4.70, 13.5.2; pp. 2,120. cited by applicant .
3GPP, "Radio Resource Control (RRC); Protocol specification (Release 12)," 3GPP TS 25.331 V12.3.0 (Sep. 2014), Sep. 23, 2014, Sections: 8.1.1.1.2, 8.1.1.6.23, 8.2.2.3, 8.3.1.12, 8.5.2, 8.6.7.29, 8.6.7.30, 10.1.1, 10.2.8, 10.2.48.8.26, 10.2.62, 10.3.8.18c, 10.3.9b, 10.3.10, 11.2, 11.3, 11.4, 13.1, 13.4.32, 13.4.69, 13.4.70, 13.5.2; pp. 2,204. cited by applicant .
3GPP, "Study on Wireless Local Area Network (WLAN)--3GPP radio interworking (Release 12)," 3GPP TR 37.834 V12.0.0 (Dec. 2013), Jan. 7, 2014, Lte Advanced, 17 pages. cited by applicant .
International Search Report and Written Opinion dated Aug. 17, 2015 from International Application No. PCT/US2015/029740. cited by applicant .
International Search Report and Written Opinion dated Jul. 31, 2015 from International Application No. PCT/US2015/027123. cited by applicant .
Office Action dated Mar. 28, 2016 from Taiwan Patent Application No. 104110683, 11 pages. cited by applicant .
"3GPP, ""Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 12),"" 3GPP TS 36.331 V12.1.0 (Mar. 2014), Mar. 19, 2014, Lte Advanced, 356 pages". cited by applicant .
"3GPP, ""Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 12),"" 3GPP TS 36.331 V12.3.0 (Sep. 2014), Sep. 23, 2014, Lte Advanced, 221 pages". cited by applicant .
3GPP, "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode Release 12)," 3GPP TS 36.304 V12.0.0 (Mar. 2014), Mar. 19, 2014, Lte Advanced, 34 pages. cited by applicant .
3GPP, "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode (Release 12)," 3GPP TS 36.304 V12.2.0 (Sep. 2014), Sep. 23, 2014, Lte Advanced, 37 pages. cited by applicant .
3GPP, "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 12)," 3GPP TS 36.300 V12.1.0 (Mar. 2014), Mar. 19, 2014, Lte Advanced, 209 pages. cited by applicant .
3GPP, "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 12)," 3GPP TS 36.300 V12.3.0 (Sep. 2014), Sep. 23, 2014, Lte Advanced, 215 pages. cited by applicant .
3GPP, T"echnical Specification Group Radio Access Network; Study on WLAN/3GPP radio interworking (Release 12)," 3GPP TR 37.834 V1.3.0 (Nov. 2013), Feb. 26, 2014, Lte Advanced, 19 pages. cited by applicant .
LG Electronics, Inc., "Comparison of access network selection solutions," 3GPP TSG RAN2 Meeting #82, R2-132055, Agenda item: 5.1.1, May 20-May 24, 2013, Fukuoka, Japan, 6 pages. cited by applicant .
3GPP, "Technical Specification Group Services and System Aspects; 3GPP System Architecture Evolution (SAE); Security architecture (Release 12)," 3GPP TS 33.401 V12.10.0 (Dec. 2013), Dec. 20, 2013, Lte Advanced, 121 pages. cited by applicant .
3GPP, "Technical Specification Group Radio Access Network; Evolved Universal Terrrestial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode (Release 12)," 3GPP TS 36.304 V12.0.0 (Mar. 2014); Mar. 19, 2014, Lte Advanced; 34 pages. cited by applicant .
Intel Corporation, "Stage-2 details of WLAN/3GPP Radio Interworking for LTE," 3GPP TSG-RAN WG2 Meeting #85bis, R2-141617, Current version: 12.1.0, Work item code: UTRA_LTE_WLAN_interw-Core, Mar. 31-Apr. 4, 2014, Valencia, Spain, 8 pages. cited by applicant .
Intel Corporation, "Idle mode procedures of WLAN/3GPP Radio Interworking for LTE" 3GPP TSG-RAN WG2 Meeting #85bis, R2-141756, Current version: 12.0.0, Work item code: UTRA_LTE_WLAN_interw-Core, Mar. 31-Apr. 4, 2014, Valencia, Spain, 4 pages. cited by applicant .
3GPP, "Technical Specification Group Radio Access Network; Study on WLAN/3GPP radio interworking (Release 12)," 3GPP TR 37.834 V1.3.0 (Nov. 2013), Lte Advanced, 20 pages. cited by applicant .
Office Action dated Oct. 27, 2016 from U.S. Appl. No. 14/583,057, 18 pages. cited by applicant .
Office Action dated Mar. 2, 2017 from Russian Patent Application No. 2016133746 , 7 pages. cited by applicant .
Office Action dated May 18, 2017 from U.S. Appl. No. 14/583,057, 25 pages. cited by applicant .
Examiner's Report dated May 29, 2017 from Canadian Patent Application No. 2,937,910, 6 pages. cited by applicant .
Notice of Preliminary Rejection dated Jun. 14, 2017 from Korean Patent Application No. 10-2016-7022635, 15 pages. cited by applicant .
Alcatel-Lucent et al., "RAN parameters for traffic steering," 3GPP TSG-RAN WG RAN3#84, R2-134329, Agenda item: 5.1., Nov. 7-11, 2013, San Francisco, USA, 4 pages. cited by applicant .
LG Electronics Inc., "Handling of the dedicated RAN assistance information," 3GPP TSG-RAN2 Meeting #85bis, R2-141702, Agenda item: 5.1.2, Mar. 31-Apr. 4, 2014, Valencia, Spain, 3 pages. cited by applicant .
Notice of Allowance dated Aug. 28, 2017 from U.S. Appl. No. 14/583,057, 21 pages. cited by applicant .
Examination Report dated Jul. 7, 2017 from Australian Patent Application No. 2015256474, 4 pages. cited by applicant .
Notice of Preliminary Rejection dated Jul. 18, 2017 from Korean Patent Application No. 10-2016-7027715, 21 pages. cited by applicant .
Office Action and Search Report dated Jul. 5, 2017 from Taiwan Divisional Application No. 105137651, 33 pages. cited by applicant .
Office Action dated Aug. 1, 2017 from Russian Patent Application No. 201639434, 7 pages. cited by applicant .
Examiner's Report dated Jul. 17, 2017 from Canadian Patent Application No. 2,945,065, 7 pages. cited by applicant .
Examination Report dated Aug. 21, 2017 from Australian Patent Application No. 2015255871, 8 pages. cited by applicant .
ZTE, "Further Consideration on Offloading Evaluation with RAN Assistance Parameters," 3GPP TSG-RAN WG2 Meeting #85bis, R2-141324, Agenda item: 5.1.2, Mar. 31-Apr. 4, 2014, Valencia, Spain, 4 pages. cited by applicant .
Intel, "Introduction of WLAN/3GPP radio interworking functionality into specifications for LTE and UMTS," 3GPP TSG-RAN2 Meeting #85bis, R2-141627, Agenda item: 5.1.2, Mar. 31-Apr. 4, 2014, Valencia, Spain, 4 pages. cited by applicant .
Alcatel-Lucent et al., "Analysis of Solution 1 ," 3GPP TSG-RAN WG2#82, R2-132018, Agenda Item: 5.1.1, May 20-24, 2013, Fukuoka, Japan, 4 pages. cited by applicant .
Siris et al., "Performance and Energy Efficiency of Mobile Data Offloading with Mobility Prediction and Prefetching," World of Wireless, Mobile and Multimedia Networks (WoWMoM), 2013 IEEE 14th International Symposium and Workshops pm a. IEEE, 2013, Jun. 4-7, 2013 Section I, II, III, 6 pages. cited by applicant .
Notice of Reasons for Rejection dated Sep. 19, 2017 from Japanese Patent Application No. 2016-549356, 16 pages. cited by applicant .
Intel Corporation, "Connected mode procedures and RRC signaling of WLAN/3GPP Radio Interworking for LTE," 3GPP TSG-RAN WG2 Meeting #85bis, R2-141757, Current version: 12.1.0, Work item code: UTRA_LTE_WLAN_interw-Core, Mar. 31-Apr. 4, 2014, Valencia, Spain, 16 pages. cited by applicant .
Mexican Patent Office--Office Action dated Apr. 10, 2018 from Mexican Patent Application No. MX/a/2016/010628, 4 pages. cited by applicant .
Canadian Patent Office--Examiner's Report dated May 14, 2018 from Canadian Patent Application No. 2,937,910, 6 pages. cited by applicant .
Japanese Patent Office--Notice of Reasons for Rejection dated Jun. 26, 2018 from Japanese Patent Application No. 2016-565046, 5 pages. cited by applicant .
Korean Patent Office--Notice of Preliminary Rejection dated Sep. 3, 2018 from Korean Patent Application No. 10-2018-7008074, 7 pages. cited by applicant.
Primary Examiner: Krueger; Kent K
This application is a continuation of U.S. patent application Ser. No. 14/583,057 filed Dec. 24, 2014, entitled "SYSTEMS, DEVICES, AND METHODS FOR INTERWORKING BETWEEN A UNIVERSAL MOBILE TELECOMMUNICATIONS SYSTEM (UMTS) NETWORK AND A WIRELESS LOCAL AREA NETWORK (WLAN)," which claims the benefit of U.S. Provisional Application No. 61/969,790 filed Mar. 24, 2014, entitled "Stage-2 and Stage-3 Details of UMTS/WLAN Radio Interworking," U.S. Provisional Application No. 61/990,693 filed May 8, 2014, entitled "Stage-2 and Stage-3 Details of UMTS/WLAN Radio Interworking," and U.S. Provisional Application No. 62/029,936 filed Jul. 28, 2014, entitled "Amendment to WLAN/3GPP Interworking RAN Rules." The entirety of the above-listed applications are hereby incorporated herein by reference.
1. One or more non-transitory, computer-readable media having instructions, stored thereon, that when executed cause a user equipment (UE) to: obtain, via broadcast signaling on a universal terrestrial radio access network (UTRAN), first radio access network (RAN) assistance parameters for traffic steering between the UTRAN and a wireless local area network (WLAN); obtain, via dedicated signaling on a serving cell of the UTRAN, second RAN assistance parameters for traffic steering between the UTRAN and the WLAN, wherein the second RAN assistance parameters are to be used by the UE for a plurality of cells of the UTRAN when the UE is in a cell dedicated channel (CELL_DCH) state and are to be used by the UE only for the serving cell from which the second RAN assistance parameters were obtained when the UE is in a cell forward access channel (CELL_FACH) state; and when the UE is in the CELL_DCH state, apply the second RAN assistance parameters to steer traffic between the UTRAN and the WLAN, continue to use the second RAN assistance parameters upon handover from the serving cell to a target cell of the plurality of cells of the UTRAN, and discard the second RAN assistance parameters upon a serving radio network subsystem (SRNS) relocation.
2. The one or more media of claim 1, wherein the instructions, when executed, further cause the UE to: when the UE is in the CELL_FACH state with the serving cell of the UTRAN, apply the second RAN assistance parameters to steer traffic between the UTRAN and the WLAN, and discard the second RAN assistance parameters upon cell reselection.
3. The one or more media of claim 1, wherein the instructions, when executed, further cause the UE to: start a timer upon entering a UTRAN idle mode, a UTRAN cell paging channel (CELL_PCH) state, or a UTRAN registration area paging channel (URA_PCH) state; use the second RAN assistance parameters to steer traffic between the UTRAN and the WLAN until expiration of the timer; and upon expiration of the timer, discard the second RAN assistance parameters and use the first RAN assistance parameters to steer traffic between the UTRAN and the WLAN.
4. The one or more media of claim 1, wherein the second RAN assistance parameters include a first WLAN beacon received signal strength indication (RSSI) threshold and a second WLAN beacon RSSI threshold that has a lesser value than the first WLAN beacon RSSI threshold, and wherein the instructions, when executed, further cause the UE to: steer traffic from the UTRAN to the WLAN based on the first WLAN beacon RSSI threshold; and steer traffic from the WLAN to the UTRAN based on the second WLAN beacon RSSI threshold.
5. The one or more media of claim 1, wherein the second RAN assistance parameters include a UTRAN received signal quality threshold, a UTRAN received signal power threshold, a WLAN channel utilization threshold, a WLAN downlink backhaul rate threshold, a WLAN uplink backhaul rate threshold, and a WLAN beacon received signal strength indication (RSSI) threshold, and wherein the instructions, when executed, further cause the UE to: determine that: a received signal code power measurement associated with a serving cell of the UTRAN is less than the UTRAN received signal power threshold or a pilot channel quality measurement associated with the serving cell of the UTRAN is below the UTRAN received signal quality threshold; and a WLAN channel utilization value associated with a target access point of the WLAN is less than the WLAN channel utilization threshold, an available backhaul downlink bandwidth associated with the target access point is greater than the WLAN downlink backhaul rate threshold, an available backhaul uplink bandwidth associated with the target access point is greater than the WLAN uplink backhaul rate threshold, and a WLAN beacon RSSI associated with the target access point is greater than the first WLAN beacon RSSI threshold; and steer traffic from the UTRAN to the WLAN based on the determination.
6. The one or more media of claim 5, wherein the UTRAN received signal quality threshold, the UTRAN received signal power threshold, the WLAN channel utilization threshold, the WLAN downlink backhaul rate threshold, the WLAN uplink backhaul rate threshold, and the WLAN beacon RSSI threshold are different than corresponding thresholds used by the UE to steer traffic from the WLAN to the UTRAN.
7. The one or more media of claim 1, wherein the second RAN assistance parameters further include one or more WLAN identifiers to identify WLAN access points that are available to the UE for traffic steering.
8. The one or more media of claim 1, wherein the dedicated signaling via which the second RAN assistance parameters are obtained is a UTRAN mobility information message or a cell update confirm message.
9. One or more non-transitory, computer-readable media having instructions, stored thereon, that when executed cause a network controller of a universal terrestrial radio access network (UTRAN) to: transmit, to a user equipment (UE) via broadcast signaling, first RAN assistance parameters to be used by the UE for traffic steering between the UTRAN and a wireless local area network (WLAN); and transmit, to the UE via dedicated signaling on a serving cell, second RAN assistance parameters for traffic steering between the UTRAN and the WLAN, wherein the second RAN assistance parameters are to be used by the UE, instead of the first RAN assistance parameters, for a plurality of cells of the UTRAN when the UE is in a cell dedicated channel (CELL_DCH) state and are to be used by the UE only for the serving cell on which the second RAN assistance parameters were transmitted when the UE is in a cell forward access channel (CELL_FACH) state; wherein the second RAN assistance parameters are to be discarded upon a serving radio network subsystem (SRNS) relocation for the UE; wherein the second RAN assistance parameters are to be used by the UE instead of the first RAN assistance parameters after handover from the serving cell to a target cell of the plurality of cells of the UTRAN if the UE is in the CELL_DCH state; and wherein the first RAN assistance parameters are to be used by the UE instead of the second RAN assistance parameters if the UE performs cell reselection and the UE is in the CELL_FACH state.
10. The one or more media of claim 9, wherein the instructions, when executed, further cause the network controller to transmit the second RAN assistance parameters on a first cell, and wherein the second RAN assistance parameters are further to be used by the UE instead of the first RAN assistance parameters when the UE is in a UTRAN idle mode, a UTRAN cell paging channel (CELL_PCH) state, or a UTRAN registration area paging channel (URA_PCH) state until selection or reselection of a cell other than the first cell or until expiration of a timer since the UE entered the idle mode, the CELL_PCH state, or the URA_PCH state.
11. The one or more media of claim 9, wherein the first RAN assistance parameters include a first set of thresholds for the UE to use to steer traffic from the UTRAN to a wireless local area network (WLAN), and a second set of thresholds for the UE to use to steer traffic from the WLAN to the UTRAN, wherein the second set of thresholds is different from the first set of thresholds.
12. The one or more media of claim 11, wherein the first set of thresholds includes a high WLAN beacon received signal strength indicator (RSSI) threshold, a low UTRAN received signal quality threshold, a low UTRAN received signal power threshold, a low WLAN channel utilization threshold, a high WLAN downlink backhaul rate threshold, or a high WLAN uplink backhaul rate threshold, and wherein the second set of thresholds includes a low WLAN beacon RSSI threshold, a high UTRAN received signal quality threshold, a high UTRAN received signal power threshold, a high WLAN channel utilization threshold, a low WLAN downlink backhaul rate threshold, and a low WLAN uplink backhaul rate threshold.
13. The one or more media of claim 9, wherein the instructions, when executed, further cause the network controller to transmit, to the UE, one or more WLAN identifiers to identify one or more WLAN access points that are available to the UE for traffic steering.
14. The one or more media of claim 9, wherein the dedicated signaling via which the second RAN assistance parameters are transmitted is a UTRAN mobility information message or a cell update confirm message.
15. An apparatus to be employed by a user equipment (UE), the apparatus comprising: means to obtain, via broadcast signaling on a universal terrestrial radio access network (UTRAN), first radio access network (RAN) assistance parameters for traffic steering between the UTRAN and a wireless local area network (WLAN); means to obtain, via a UTRAN mobility information message or a cell update confirm message from a serving cell of the UTRAN, second RAN assistance parameters for traffic steering between the UTRAN and the WLAN, wherein the second RAN assistance parameters are to be used by the UE for a plurality of cells of the UTRAN when the UE is in a cell dedicated channel (CELL_DCH) state and are to be used by the UE only for the serving cell from which the second RAN assistance parameters were obtained when the UE is in a cell forward access channel (CELL_FACH) state; and means to, when the UE is in the CELL_DCH state, apply the second RAN assistance parameters to steer traffic between the UTRAN and the WLAN, continue to use the second RAN assistance parameters upon handover from the serving cell to a target cell of the plurality of cells of the UTRAN, and discard the second RAN assistance parameters upon a serving radio network subsystem (SRNS) relocation; means to, when the UE is in the CELL_FACH state with the serving cell of the UTRAN, apply the second RAN assistance parameters to steer traffic between the UTRAN and the WLAN, and discard the second RAN assistance parameters upon cell reselection.
16. The apparatus of claim 15, further comprising: means to start a timer upon entering a UTRAN idle mode, a UTRAN cell paging channel (CELL_PCH) state, or a UTRAN registration area paging channel (URA_PCH) state; means to use the second RAN assistance parameters to steer traffic between the UTRAN and the WLAN until expiration of the timer; and means to, upon expiration of the timer, discard the second RAN assistance parameters and use the first RAN assistance parameters to steer traffic between the UTRAN and the WLAN.
17. The apparatus of claim 15, wherein the second RAN assistance parameters include a UTRAN received signal quality threshold, a UTRAN received signal power threshold, a WLAN channel utilization threshold, a WLAN downlink backhaul rate threshold, a WLAN uplink backhaul rate threshold, and a WLAN beacon received signal strength indication (RSSI) threshold, and wherein the apparatus further comprises: means to determine that: a received signal code power measurement associated with a serving cell of the UTRAN is less than the UTRAN received signal power threshold or a pilot channel quality measurement associated with the serving cell of the UTRAN is below the UTRAN received signal quality threshold; and a WLAN channel utilization value associated with a target access point of the WLAN is less than the WLAN channel utilization threshold, an available backhaul downlink bandwidth associated with the target access point is greater than the WLAN downlink backhaul rate threshold, an available backhaul uplink bandwidth associated with the target access point is greater than the WLAN uplink backhaul rate threshold, and a WLAN beacon RSSI associated with the target access point is greater than the first WLAN beacon RSSI threshold; and means to steer traffic from the UTRAN to the WLAN based on the determination.
As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality.
For example, the first set of thresholds for traffic steering from the UTRAN to the WLAN may include a low UTRAN received signal quality threshold (Thresh.sub.ServingOffloadWLAN, LowQ), a low UTRAN received signal power threshold (Thresh.sub.ServingOffloadWLAN, LowP), a low WLAN channel utilization threshold (Thresh.sub.ChUtiWLAN, Low), a high WLAN downlink backhaul rate threshold (Thresh.sub.BackhRateDlWLAN, High), a high WLAN uplink backhaul rate threshold (Thresh.sub.BackhRateUlWLAN, High), and/or a high beacon received signal strength indicator (RSSI) threshold (Thresh.sub.RSSIWLAN, High). The second set of thresholds for traffic steering from the WLAN to the UTRAN may include a high UTRAN received signal quality threshold (Thresh.sub.ServingOffloadWLAN, HighQ), a high UTRAN received signal power threshold (Thresh.sub.ServingOffloadWLAN, HighP), a high WLAN channel utilization threshold (Thresh.sub.ChUtilWLAN, High), a low WLAN downlink backhaul rate threshold (Thresh.sub.BackhRateDlWLAN, Low), a low WLAN uplink backhaul rate threshold (Thresh.sub.BackhRateUlWLAN, Low), and/or a low beacon RSSI threshold (Thresh.sub.RSSIWLAN, Low). A "high" threshold of one set of thresholds may generally have a greater value than a corresponding "low threshold" of the other set of thresholds. Accordingly, the corresponding thresholds of the two sets of thresholds may have different values to avoid/reduce frequent switching between the UTRAN and the WLAN (e.g., the "ping-pong effect").
In some embodiments, the threshold Thresh.sub.ServingOffloadWLAN, LowP may specify a common pilot channel (CPICH) received signal code power (RSCP) threshold (measured in dBm) for frequency-division duplexing (FDD) cells of the UTRAN and/or a primary common control physical channel (P-CCPCH) RSCP for time-division duplexing (TDD) cells of the UTRAN for use by the UE 104 for traffic steering to the WLAN. The threshold Thresh.sub.ServingOffloadWLAN, HighP may specify the CPICH RSCP for FDD cells and/or a P-CCPCH RSCP for TDD cells for use by the UE 104 for traffic steering to the UTRAN. The threshold Thresh.sub.ServingOffloadWLAN, LowQ may specify the CPICH E.sub.c/N.sub.0 (quality energy per chip over total received power spectral density) for FDD cells for use by the UE 104 for traffic steering to the WLAN. The threshold Thresh.sub.ServingOffloadWLAN, HighQ may specify the CPICH E.sub.c/N.sub.0 for FDD cells for use by the UE 104 for traffic steering to the UTRAN.
In some embodiments, Thresh.sub.ChUtilWLAN, Low may be a WLAN channel utilization (BSS load) threshold used by the UE 104 for traffic steering to WLAN, and Thresh.sub.ChUtilWLAN,High may be a WLAN channel utilization (BSS load) threshold used by the UE 104 for traffic steering to UTRAN. The WLAN channel utilization for an indicated WLAN identifier may correspond to a WLAN channel utilization value from basic service set (BSS) load information element (IE) obtained from IEEE 802.11 (Beacon or Probe Response) signaling for the indicated WLAN identifier.
In some embodiments, Thresh.sub.BackhRateDlWLAN, High corresponds to a backhaul available downlink bandwidth threshold used by the UE 104 for traffic steering to WLAN, and Thresh.sub.BackhRateDlWLAN, Low may be a backhaul available downlink bandwidth threshold used by the UE 104 for traffic steering to UTRAN. The backhaul available downlink bandwidth for the WLAN may be calculated as Downlink Speed*(1-Downlink Load/255), where the Downlink Speed and Downlink Load parameters may be drawn from wide area network (WAN) Metrics element obtained via access network query protocol (ANQP) signaling from Wi-Fi Alliance (WFA) hotspot (HS) 2.0 (based on IEEE 802.11u and WFA extensions).
In some embodiments, Thresh.sub.BackhRateUlWLAN, High may be a backhaul available uplink bandwidth threshold used by the UE 104 for traffic steering to WLAN, and Thresh.sub.BackhRateUlWLAN, Low may be a backhaul available uplink bandwidth threshold used by the UE 104 for traffic steering to UTRAN. The backhaul available uplink bandwidth that may be calculated as Uplink Speed*(1-Uplink Load/255), where the Uplink Speed and Uplink Load parameters may be drawn from the WAN metrics element obtained via ANQP signaling from WFA HS2.0,
In some embodiments, Thresh.sub.RSSIWLAN, High corresponds to a Beacon RSSI threshold used by the UE 104 for traffic steering to WLAN, and Thresh.sub.RSSIWLAN, Low may be a Beacon RSSI threshold used by the UE 104 for traffic steering to UTRAN. The Beacon RSSI for a WLAN may be an RSSI as measured by the UE 104 on the WLAN Beacon.
The first set of traffic steering rules for steering traffic to a WLAN may include UTRAN serving cell conditions and target WLAN conditions. The EUTRAN serving cell conditions may include: Qrxlevmeas<Thresh.sub.ServingOffloadWLAN, LowP; or Qqualmeas<Thresh.sub.ServingOffloadWLAN, LowQ. The value Qrxlevmeas may be a received signal power of the UTRAN cell (e.g., the CPICH RSCP for an FDD cell or the P-CCPCH RSCP for a TDD cell). The value Qqualmeas may be a measured reference signal received quality (RSRQ) (in dB) in the UTRAN cell (e.g., the CPICH E.sub.c/N.sub.0 for an FDD cell). Thus, the control circuitry 108 may determine that the UTRAN serving cell conditions of the first set of traffic steering rules are satisfied if a measured received signal power value of the UTRAN cell is less than the corresponding received signal power threshold or a measured received signal quality value of the UTRAN is less than the corresponding received signal quality threshold. In some embodiments, the received signal power value and/or the received signal quality value may be measured by the UE 104.
The target WLAN conditions may include: ChannelUtilizationWLAN<Thresh.sub.ChUtilWLAN, Low; BackhaulRateDlWLAN>Thresh.sub.BackhRateDlWLAN, High; BackhaulRateUlWLAN>Thresh.sub.BackhRateUlWLAN, High; and BeaconRSSI>Thresh.sub.RSSIWLAN, High, where ChannelUtilizationWLAN may be the WLAN channel utilization value from a BSS IE obtained from IEEE 802.11 (Beacon or Probe Response) signaling for an indicated WLAN identifier, BackhaulRateDlWLAN may be a backhaul available downlink bandwidth that may be calculated as Downlink Speed*(1-Downlink Load/255), where the Downlink Speed and Downlink Load parameters may be drawn from WAN Metrics element obtained via ANQP signaling from WFA HS 2.0 (based on IEEE 802.11u and WFA extensions), BackhaulRateUlWLAN may be a backhaul available uplink bandwidth that may be calculated as Uplink Speed*(1-Uplink Load/255), where the Uplink Speed and Uplink Load parameters may be drawn from the WAN metrics element obtained via ANQP signaling from WFA HS2.0, and BeaconRSSI may be an RSSI as measured by the UE 104 on the WLAN Beacon. Thus, the control circuitry 108 may determine that the WLAN conditions are satisfied if a WLAN channel utilization is less than the corresponding WLAN channel utilization threshold, a WLAN downlink backhaul rate is greater than a corresponding WLAN downlink backhaul rate threshold, a WLAN uplink backhaul rate is greater than a corresponding WLAN uplink backhaul rate threshold, and a beacon RSSI is greater than a corresponding WLAN beacon RSSI threshold.
The second set of traffic steering rules for steering traffic to a WLAN may include WLAN conditions conditions and target UTRAN cell conditions. The WLAN conditions for steering traffic to a target UTRAN cell from the WLAN may include: ChannelUtilizationWLAN>Thresh.sub.ChUtiWLAN, High; BackhaulRateDlWLAN<Thresh.sub.BackhRateDlWLAN, Low; BackhaulRateUlWLAN<Thresh.sub.BackhRateUlWLAN, Low; or BeaconRSSI<Thresh.sub.RSSIWLAN, Low. Thus, the control circuitry 108 may determine the WLAN conditions for steering traffic to the target UTRAN cell are satisfied if a WLAN channel utilization is greater than a corresponding WLAN channel utilization threshold, a WLAN downlink backhaul rate is less than a corresponding WLAN downlink backhaul rate threshold, a WLAN uplink backhaul rate is less than a corresponding WLAN uplink backhaul rate threshold, or a beacon RSSI is less than a corresponding WLAN beacon RSSI threshold.
The UTRAN conditions for steering traffic to a target UTRAN cell from a WLAN may include: Qrxlevmeas>Thresh.sub.ServingOffloadWLAN, HighP; and Qqualmeas>Thresh.sub.ServingOffloadWLAN, HighQ. Thus, the control circuitry 108 may determine the UTRAN conditions for steering traffic to the target UTRAN cell are satisfied if a measured received signal power value of the UTRAN is greater than a corresponding received signal power threshold and a measured received signal quality value of the UTRAN is greater than a corresponding received signal quality threshold.
TABLE-US-00001 TABLE 1 System UE mode/state UE mode/state Modification information Area when block is when block is Scheduling of system block scope valid read information information System Cell Idle mode, Idle mode, Specified by the IE Value tag information CELL_FACH, CELL_FACH, "Scheduling block type 23 CELL_PCH, CELL_PCH, information" URA_PCH URA_PCH System Cell Idle mode, Idle mode, Specified by the IE Value tag information CELL_FACH, CELL_FACH, "Scheduling block type 24 CELL_PCH, CELL_PCH, information" URA_PCH URA_PCH,
TABLE-US-00002 Information Element/Group Type and name Need Multi reference Semantics description Version CHOICE WLAN Offload MP REL-12 Parameters >WLAN Offload Parameters WLAN Offload REL-12 Common Parameters 10.3.3.x1 >WLAN Offload Parameters Per 1 to 6 The number of instances of this REL-12 PLMN List IE is the number of instances of the IE "Multiple PLMNs" in the IE "Multiple PLMN List" of the MIB plus one. The first instance of this IE specifies the WLAN Offload Parameters for UEs which have chosen the PLMN in the IE "PLMN identity" of the MIB, the second instance specifies the WLAN Offload Parameters for UEs which have chosen the first PLMN in the IE "Multiple PLMNs" in the IE "Multiple PLMN List" of the MIB, the third instance specifies the WLAN Offload Parameters for UEs which have chosen the second PLMN in the IE "Multiple PLMNs" in the IE "Multiple PLMN List" of the MIB, and so on. >>WLAN Offload Parameters OP WLAN Offload REL-12 Parameters 10.3.3.x1
TABLE-US-00003 TABLE 3 Information Element/Group Type and name Need Multi reference Semantics description Version WLAN Identifiers Per PLMN List 1 to 6 The number of instances of this REL-12 IE is the number of instances of the IE "Multiple PLMNs" in the IE "Multiple PLMN List" of the MIB plus one. The first instance of this IE specifies the WLAN Identifiers for UEs which have chosen the PLMN in the IE "PLMN identity" of the MIB, the second instance specifies the WLAN Identifiers for UEs which have chosen the first PLMN in the IE "Multiple PLMNs" in the IE "Multiple PLMN List" of the MIB, the third instance specifies the WLAN Identifiers for UEs which have chosen the second PLMN in the IE "Multiple PLMNs" in the IE "Multiple PLMN List" of the MIB, and so on. >WLAN Identifiers OP WLAN REL-12 Identifiers 10.3.3.x2
TABLE-US-00004 TABLE 4 Information Element/Group Type and Semantics name Need Multi reference description Version Message Type MP Message Type UE Information Elements Integrity check info CH Integrity check info 10.3.3.16 RRC transaction identifier MP RRC transaction identifier 10.3.3.36 Integrity protection mode info OP Integrity The UTRAN should protection not include this IE mode info unless it is 10.3.3.19 performing an SRNS relocation Ciphering mode info OP Ciphering The UTRAN should mode info not include this IE 10.3.3.5 unless it is performing an SRNS relocation and a change in ciphering algorithm New U-RNTI OP U-RNTI 10.3.3.47 New C-RNTI OP C-RNTI 10.3.3.8 New H-RNTI OP H-RNTI REL-7 10.3.3.14a New Primary E-RNTI OP E-RNTI REL-8 10.3.3.10a UE Timers and constants in OP UE Timers connected mode and constants in connected mode 10.3.3.43 Dedicated priority information OP Dedicated REL-8 priority information 10.3.2.7 WLAN Offload Parameters OP 10.3.3.x1 REL-12 WLAN Identifiers OP 10.3.3.x2 REL-12 CN Information Elements CN Information info OP CN Information info full 10.3.1.3a UTRAN Information Elements URA identity OP URA identity 10.3.2.6 RNC support for change of UE OP Boolean Should be included REL-7 capability if the message is used to perform an SRNS relocation RB Information elements Downlink counter synchronisation OP info >RB with PDCP information list OP 1 to <maxRBall RABs> >>RB with PDCP information MP RB with This IE is needed PDCP for each RB having information PDCP in the case of 10.3.4.22 lossless SRNS relocation OP REL-5 >>PDCP context relocation info OP PDCP context This IE is needed REL-5 relocation info for each RB having 10.3.4.1a PDCP and performing PDCP context relocation
TABLE-US-00005 TABLE 5 Information Element/Group Type and Semantics name Need Multi reference description Version Message Type MP Message Type UE Information Elements U-RNTI CV-CCCH U-RNTI 10.3.3.47 RRC transaction identifier MP RRC transaction identifier 10.3.3.36 Integrity check info CH Integrity check info 10.3.3.16 Integrity protection mode info OP Integrity The UTRAN should protection not include this IE mode info unless it is 10.3.3.19 performing an SRNS relocation or a cell reselection from GERAN Iu mode Ciphering mode info OP Ciphering The UTRAN should mode info not include this IE 10.3.3.5 unless it is performing either an SRNS relocation or a cell reselection from GERAN Iu mode, and a change in ciphering algorithm. Activation time MD Activation Default value is time 10.3.3.1 "now" New U-RNTI OP U-RNTI 10.3.3.47 New C-RNTI OP C-RNTI 10.3.3.8 New DSCH-RNTI OP DSCH-RNTI Should not be set in 10.3.3.9a FDD. If received, the UE behaviour is unspecified. New H-RNTI OP H-RNTI REL-5 10.3.3.14a New Primary E-RNTI OP E-RNTI REL-6 10.3.3.10a New Secondary E-RNTI OP E-RNTI FDD only REL-6 10.3.3.10a RRC State Indicator MP RRC State Indicator 10.3.3.35a UTRAN DRX cycle length OP UTRAN DRX coefficient cycle length coefficient 10.3.3.49 Wait time OP Wait time 10.3.3.50 RLC re-establish indicator (RB2, MP RLC re- Should not be set to RB3 and RB4) establish TRUE if IE indicator "Downlink counter 10.3.3.35 synchronisation info" is included in message. RLC re-establish indicator (RB5 MP RLC re- Should not be set to and upwards) establish TRUE if IE indicator "Downlink counter 10.3.3.35 synchronisation info" is included in message. WLAN Offload Parameters OP 10.3.3.x1 REL-12 WLAN Identifiers OP 10.3.3.x2 REL-12 CN Information Elements CN Information info OP CN Information info 10.3.1.3 UTRAN Information Elements URA identity OP URA identity 10.3.2.6 RNC support for change of UE OP Boolean Should be included REL-7 capability if the message is used to perform an SRNS relocation RB information elements RAB information for setup CV-CS RAB RAB identity shall information be identical to the for setup one currently 10.3.4.10 configured and UE behaviour is unspecified otherwise. RB information to release list OP 1 to <maxRB> >RB information to release MP RB information to release 10.3.4.19 RB information to reconfigure list OP 1 to <maxRB> >RB information to reconfigure MP RB information to reconfigure 10.3.4.18 RB information to be affected list OP 1 to <maxRB> >RB information to be affected MP RB information to be affected 10.3.4.17 Downlink counter synchronisation OP info >RB with PDCP information list OP 1 to <maxRBall RABs> >>RB with PDCP information MP RB with This IE is needed PDCP for each RB having information PDCP in the case of 10.3.4.22 lossless SRNS relocation OP REL-5 >>PDCP context relocation info OP PDCP context This IE is needed REL-5 relocation info for each RB having 10.3.4.1a PDCP and performing PDCP context relocation PDCP ROHC target mode OP PDCP ROHC REL-5 target mode 10.3.4.2a TrCH Information Elements Uplink transport channels UL Transport channel information OP UL Transport common for all transport channels channel information common for all transport channels 10.3.5.24 Deleted TrCH information list OP 1 to <maxTrCH> >Deleted UL TrCH information MP Deleted UL TrCH information 10.3.5.5 Added or Reconfigured TrCH OP 1 to information list <maxTrCH> >Added or Reconfigured UL TrCH MP Added or information Reconfigured UL TrCH information 10.3.5.2 Downlink transport channels DL Transport channel information OP DL Transport common for all transport channels channel information common for all transport channels 10.3.5.6 Deleted TrCH information list OP 1 to <maxTrCH> >Deleted DL TrCH information MP Deleted DL TrCH information 10.3.5.4 Added or Reconfigured TrCH OP 1 to information list <maxTrCH> >Added or Reconfigured DL TrCH MP Added or information Reconfigured DL TrCH information 10.3.5.1 PhyCH information elements Frequency info OP Frequency info 10.3.6.36 Multi-frequency Info OP Multi- This IE is used for REL-7 frequency 1.28 Mcps TDD Info only 10.3.6.39a DTX-DRX timing information OP DTX-DRX REL-7 timing information 10.3.6.34b DTX-DRX Information OP DTX-DRX REL-7 Information 10.3.6.34a HS-SCCH less Information OP HS-SCCH REL-7 less Information 10.3.6.36ab MIMO parameters OP MIMO REL-7 parameters 10.3.6.41a MIMO mode with four transmit OP MIMO mode REL-11 antennas parameters with four transmit antennas parameters 10.3.6.142 Control Channel DRX information OP Control This IE is used for REL-8 Channel DRX 1.28 Mcps TDD information only 1.28 Mcps TDD 10.3.6.107 SPS Information OP SPS This IE is used for REL-8 information 1.28 Mcps TDD 1.28 Mcps only TDD 10.3.6.110 MU-MIMO info OP MU-MIMO This IE is used for REL-10 info 1.28 1.28 Mcps TDD Mcps TDD only 10.3.6.122 Non-rectangular resource allocation OP Enumerated (TRUE) For 1.28 Mcps TDD REL-12 indicator only. The absence of this IE indicates that the non-rectangular resource allocation is not used. Non-rectangular resource specific CV-Non- Bit string (7) For 1.28 Mcps TDD REL-12 timeslots set rectangular only. ResourceAllocation The value 1 of a bit indicates the corresponding timeslot in which the channelization codes are assigned by physical control channel. The value 0 of a bit indicates the corresponding timeslot in which all channelization codes are assigned when the timeslot is scheduled to the UE. The first/leftmost bit of the bit string is for TS0. Uplink radio resources Maximum allowed UL TX power MD Maximum Default value is the allowed UL existing maximum TX power UL TX power 10.3.6.39
Uplink DPCH info OP Uplink DPCH info 10.3.6.88 E-DCH Info OP E-DCH Info REL-6 10.3.6.97 Uplink secondary cell info FDD OP Uplink FDD only REL-9 secondary cell info FDD 10.3.6.115 Multi-carrier E-DCH Info for LCR OP Multi-carrier 1.28Mcps TDD REL-10 TDD E-DCH Info only for LCR TDD 10.3.6.97a Uplink CLTD info FDD OP Uplink CLTD FDD only REL-11 info FDD 10.3.6.125 Uplink OLTD info FDD OP Uplink OLTD FDD only REL-11 info FDD 10.3.6.126 Downlink radio resources Downlink HS-PDSCH Information OP Downlink REL-5 HS_PDSCH Information 10.3.6.23a Downlink information common for OP Downlink all radio links information common for all radio links 10.3.6.24 Downlink information per radio OP 1 to Send downlink link list <maxRL> information for each radio link to be set- up >Downlink information for each MP Downlink radio link information for each radio link 10.3.6.27 Downlink secondary cell info FDD OP Downlink FDD only REL-8 secondary cell info FDD 10.3.6.31a Additional downlink secondary cell OP 2 REL-10 info list FDD >Downlink secondary cell info OP Downlink FDD only REL-10 FDD secondary cell info FDD 10.3.6.31a Additional downlink secondary cell OP 4 REL-11 info list FDD 2 >Downlink secondary cell info OP Downlink FDD only REL-11 FDD secondary cell info FDD 10.3.6.31a Common E-RGCH info FDD OP Common E- FDD only REL-11 RGCH info FDD 10.3.6.138 MBMS PL Service Restriction OP Enumerated REL-6 Information (TRUE) CELL_DCH measurement occasion OP CELL_DCH REL-9 info LCR measurement occasion info LCR 10.3.7.126
TABLE-US-00006 TABLE 6 Condition Explanation CCCH This IE is mandatory present when CCCH is used and ciphering is not required and not needed otherwise. CS This IE is optionally present only if CS domain RAB mapping is reconfigured between DCH and E-DCH/HS-DSCH and shall not be present otherwise. Non-rectangularResourceAllocation This IE is optionally present if non-rectangular resource allocation is configured. Otherwise, it is not needed.
The RAN assistance parameters included in the system information message, the UTRAN mobility information message, and/or the cell update confirm message may have properties as described in Table 7. The "type and reference" column may indicate the size and/or number of possible values that are indicated by the corresponding threshold. Each of the thresholds may be optionally included (or not included) in the corresponding message.
TABLE-US-00007 TABLE 7 Information Element/Group Type and Semantics name Need Multi reference description Version Thresh.sub.ServingOffloadWLAN, LowP OP Integer (0 . . . 62 RSCP, dB REL-12 by step of 2 Thresh.sub.ServingOffloadWLAN, HighP OP Integer (0 . . . 62 RSCP, dB REL-12 by step of 2 Thresh.sub.ServingOffloadWLAN, LowQ OP Integer Ec/N0, dB REL-12 (0 . . . 31) Thresh.sub.ServingOffloadWLAN, HighQ OP Integer Ec/N0, dB REL-12 (0 . . . 31) Thresh.sub.ChUtilWLAN, Low OP Integer REL-12 (1 . . . 255) Thresh.sub.ChUtilWLAN, High OP Integer REL-12 (1 . . . 255) Thresh.sub.BackhRateDLWLAN, Low OP Integer REL-12 (1 . . . 4194304) Thresh.sub.BackhRateDLWLAN, High OP Integer REL-12 (1 . . . 4194304) Thresh.sub.BackhRateULWLAN, Low OP Integer REL-12 (1 . . . 4194304) Thresh.sub.BackhRateULWLAN, High OP Integer REL-12 (1 . . . 4194304) Tsteering.sub.WLAN OP Integer REL-12 (0 . . . 31)
Previous Patent US 10,178,597 | Next Patent US 10,178,599