Source: https://patents.google.com/patent/EP2753124B1/en
Timestamp: 2020-08-09 06:37:15
Document Index: 253342129

Matched Legal Cases: ['Application No. 14', 'art 600', 'art 600', 'art 600', 'art 700', 'art 700', 'art 400', 'art 700']

EP2753124B1 - Systems and methods for network discovery and selection using contextual information - Google Patents
EP2753124B1
EP2753124B1 EP14000053.0A EP14000053A EP2753124B1 EP 2753124 B1 EP2753124 B1 EP 2753124B1 EP 14000053 A EP14000053 A EP 14000053A EP 2753124 B1 EP2753124 B1 EP 2753124B1
EP14000053.0A
EP2753124A1 (en
2014-01-08 Application filed by Broadcom Corp filed Critical Broadcom Corp
2014-07-09 Publication of EP2753124A1 publication Critical patent/EP2753124A1/en
2016-06-22 Publication of EP2753124B1 publication Critical patent/EP2753124B1/en
Conventional offloading solutions, such as 3GPP I-WLAN architecture as set forth in the 3GPP TS 23.234 specification, as well as US2012/324100 A1 and EP-2437546 A1 rely on policies stored in mobile devices with pre-configured conditions to effectuate offloading.
According to an aspect, a communication device comprises:
offload communications from the first communication network to the second communication network based on one or more communication parameters defined in the offloading framework, wherein the one or more communication parameters include a parameter that defines a data rate validity condition for the second communication network, wherein the data rate validity condition defines a comparison of a data rate of an active connection of a second communications device on the second communication network with an estimated data rate of a prospective connection of the communications device on the second communication network.
Advantageously, the offloading framework conforms to an Access Network Discovery and Selection Function (ANDSF) framework.
Advantageously, the one or more communication parameters include a parameter that defines a movement state of the communication device.
Advantageously, the movement state includes at least one of: a Pedestrian-A movement state, a Pedestrian-B movement state, and a Vehicular-A movement state.
Advantageously, the one or more communication parameters include a parameter that defines a received signal strength indication (RSSI) threshold or a signal-to-interference-plus-noise ratio (SINR) threshold for the second communication network.
Advantageously, the one or more communication parameters include a parameter that defines a time duration that the communication device or another communication device has previously remained connected to the second communication network.
Advantageously, the one or more communication parameters include a parameter that defines a data rate validity condition for the second communication network, wherein the data rate validity condition defines a comparison of a data rate of an active connection of a second communications device on the second communication network with an estimated data rate of a prospective connection of the communications device on the second communication network. Advantageously, the controller is configured to compare the data rate to the estimated data rate, and offload the communications from the first communication network to the second communication network based on the comparison.
Advantageously, the estimated data rate is estimated by an access point supporting the second communication network.
Advantageously, the one or more communication parameters include a parameter that defines Wi-Fi multimedia (WMM) mapping of the second communication network.
Advantageously, the WMM mapping includes at least one of packet priority information, packet error loss rate information or packet delay budget information.
Advantageously, the first communication network is a Long-Term Evolution (LTE) communication network and the second communication network is a Wi-Fi communication network.
According to an aspect, a communication method comprises:
offloading communications from the first communication network to a second communication network based on a comparison of the operational information and the one or more communication parameters of the offloading framework, wherein the one or more communication parameters include a parameter that defines a data rate validity condition for the second communication network, wherein the data rate validity condition defines a comparison of a data rate of an active connection of a second communications device on the second communication network with an estimated data rate of a prospective connection of the communications device on the second communication network.
Advantageously, the one or more communication parameters include a parameter that defines a received signal strength indication (RSSI) threshold or a signal-to-interference-plus-noise ratio (SINR) threshold of the second communication network.
Advantageously, the one or more communication parameters include a parameter that defines a data rate validity condition of the second communication network.
receive an Access Network Discovery and Selection Function (ANDSF) framework via the first communication network, the ANDSF framework including a movement parameter, a signal quality parameter, a connection duration parameter, a data rate parameter, and a quality of service (QoS) parameter; and
offload communications from the first communication network to the second communication network based on the parameters included in the ANDSF framework.
FIG. 6 illustrates a flowchart of an offloading method according to an exemplary embodiment of the present disclosure.
In the following disclosure, terms defined by the Long-Term Evolution (LTE) standard are sometimes used. For example, the term "eNodeB" or "eNB" is used to refer to what is commonly described as a base station (BS) or a base transceiver station (BTS) in other standards. The term "User Equipment (UE)" is used to refer to what is commonly described as a mobile station (MS) or mobile terminal in other standards. The LTE standard is developed by the 3rd Generation Partnership Project (3GPP) and described in the 3GPP specification and International Mobile Telecomunnications-2000 (IMT-2000) standard. Further, although exemplary embodiments are described with reference to LTE, the more generic terms "mobile device" and "base station" are used herein except where Otherwise noted to refer to the LTE terms "User Equipment (UE)" and "eNodeB/eNB/", respectively.
As will be apparent to one of ordinary skill in the relevant art(s) based on the teachings herein, exemplary embodiments are not limited to the LTE standard, and can be applied to other cellular communication standards, including (but not limited to) Evolved High-Speed Packet Access (HSPA+), Wideband Code Division Multiple Access (W-CDMA), CDMA2000, Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Enhanced Data Rates for GSM Evolution (EDGE), and Worldwide Interoperability for Microwave Access (WiMAX) (IEEE 802.16) to provide some examples. Further, exemplary embodiments are not limited to cellular communication networks and can be used or implemented in other kinds of wireless communication access networks, including (but not limited to) Wi-Fi (IEEE 802.11), Bluetooth, Near-field Communication (NFC) (ISO/IEC 18092), ZigBee (IEEE 802.15.4), and/or Radio-frequency identification (RFID), to provide some examples.
In an exemplary embodiment, the base station 120 includes suitable logic, circuitry, and/or code that is configured for communications conforming to 3GPP's LTE specification (e.g., the base station is an LTE base station), the AP 150 includes suitable logic, circuitry, and/or code that is configured for communications conforming to IEEE's 802.11 Wi-Fi specification (e.g., the AP 150 is a Wi-Fi access point), and mobile device 140 includes suitable logic, circuitry, and/or code that is configured for communications conforming to 3GPP's LTE specification and IEEE's 802.11 Wi-Fi specification. That is, the mobile device 140 is configured to wirelessly communicate with the base station 120 utilizing 3GPP's LTE specification and with the AP 150 utilizing IEEE's 802.11 Wi-Fi specification. Here, the serving cell or sector 110 is an LTE serving cell or sector and the WLAN 112 is a WLAN utilizing the 802.11 Wi-Fi specification.
Examples of the mobile device 140 include (but are not limited to) a mobile computing device-such as a laptop computer, a tablet computer, a mobile telephone or smartphone, a "phablet," a personal digital assistant (PDA), mobile media player, and the like; and a wearable computing device-such as a computerized wrist watch or "smart" watch, computerized eyeglasses, and the like. In some embodiments, the mobile device 140 may be a stationary device, including, for example, a stationary computing device-such as a personal computer (PC), a desktop computer, a computerized kiosk, an automotive/aeronautical/maritime in-dash computer terminal, and the like.
The transceiver 200 includes suitable logic, circuitry, and/or code that is configured to transmit and/or receive wireless communications via one or more wireless technologies within the communication environment 100. In particular, the transceiver 200 can include a transmitter 210 and a receiver 220 that have suitable logic, circuitry, and/or code configured to transmit and receive wireless communications, respectively, via one or more antennas 230. Those skilled in the relevant art(s) will recognize that the processes for transmitting and/or receiving wireless communications can include (but are not limited to) digital signal processing, modulation and/or demodulation of data, digital-to-analog (DAC) and/or analog-to-digital (ADC) conversion, and/or frequency conversion to provide some examples. Further, those skilled in the relevant art(s) will recognize that the antenna 230 may include an integer array of antennas, and that the antenna 230 may be capable of both transmitting and receiving wireless communication signals. For example, the base station 120 can be configured for wireless communication utilizing a Multiple-input Multiple-output (MIMO) configuration.
The transceiver 300 is similar to the transceiver 200 and includes suitable logic, circuitry, and/or code that is configured to transmit and/or receive wireless communications via one or more wireless technologies within the communication environment 100. In particular, the transceiver 300 can similarly include a transmitter 310 and a receiver 320 that have suitable logic, circuitry, and/or code configured to transmit and receive wireless communications, respectively, via one or more antennas 330. Those skilled in the relevant art(s) will recognize that the antenna 330 may include an integer array of antennas, and that the antenna 330 may be capable of both transmitting and receiving wireless communication signals. For example, the AP 150 can be configured for wireless communication utilizing a Multiple-input Multiple-output (MIMO) configuration.
The LTE transceiver 400 includes suitable logic, circuitry, and/or code that is configured for transmitting and/or receiving wireless communications conforming to 3GPP's LTE specification. In particular, the LTE transceiver 400 can include an LTE transmitter 410 and an LTE receiver 420 that have suitable logic, circuitry, and/or code configured for transmitting and receiving wireless communications conforming to 3GPP's LTE specification, respectively, via one or more antennas 435.
In an exemplary embodiment, the one or more offloading policies conform to the Access Network Discovery and Selection Function (ANDSF) framework defined in the 3GPP TS 24.312 specification.
The ANDSF framework is an entity introduced by 3GPP as part of the Release 8 set of specifications, within an Evolved Packet Core (EPC) of the System Architecture Evolution (SAE) for 3GPP compliant communication networks. The ANDSF framework assists the mobile device 140 to discover one or more non-3GPP communication networks (e.g., Wi-Fi, WIMAX, etc.) that can be used for data communications in addition to one or more 3GPP communication networks (e.g., LTE. HSPA, etc.) and to provide the mobile device 140 with rules (e.g., policy conditions) that control the connection to these non-3GPP communication networks.
1. Inter-System Mobility Policy (ISMP)-network selections rules for a mobile device with no more than one active communication network connection (e.g., either LTE or Wi-Fi).
2. Inter-System Routing Policy (ISRP)-network selection rules for the mobile device with potentially more than one active communication network connection (e.g., both LTE and Wi-Fi). Here, the mobile device may employ IP Flow Mobility (IFOM), Multiple Access Packet Data Networks (PDN) Connectivity (MAPCON) or non-seamless Wi-Fi offloading according to operator policy and user preferences.
3. Discovery information-a list of networks that may be available in the vicinity of the mobile device and information assisting the mobile device to expedite the connection to these networks.
Here, the ANDSF framework assists the mobile device 140 to discover communication networks in the vicinity of the mobile device 140 and prioritize/manage connections to the communication networks. The policies set forth in the ANDSF framework can be statically pre-configured on the mobile device or dynamically updated by the service provider and provided to the mobile device 140 via the Open Mobile Alliance (OMA) Device Management (DM) protocol specified by the OMA DM Working Group and the Data Synchronization (DS) Working Group.
The ANDSF Management Objects (MO) include various rules/conditions and information organized into one or more "nodes" each having one or more "leaf objects." The nodes and leaf objects define the various rules and discovery information that are used by the mobile device 140 in governing the ISMP, ISRP, and Discovery processing by the mobile device 140. For example, the ANDSF MO is used by the mobile device 140 to establish communications via one or more non-3GPP communication networks (e.g., Wi-Fi communication network on AP 150) and effectuate offloading of the mobile device's 140 communications via the base station 120 to, for example, the AP 150.
In operation, with reference to FIG. 5, when a condition within the ANDSF MO becomes "active" (e.g., the mobile device 140 moves within range of a communication network serving cell that is specified in a node/leaf of the of the ANDSF MO), the mobile device 140 notifies the event to the ANDSF server and requests the Inter-system Discovery Information based on the preferred access technology recommended in the MO (e.g., Wi-Fi). The ANDSF server will provide the mobile device 140 with the communication network's identification information (e.g., Wi-Fi Hotspot SSIDs) in the vicinity and related access information (e.g., Wi-Fi security keys). The mobile device 140 uses this information to connect to the other communication network. Further, the mobile device 140 can offload communications originally destined for the original serving communication network (e.g., LTE) to the other communication network based on rules set forth in the ANDSF MO.
The ANDSF MO 500 provides an offloading framework that includes various rules/conditions and information organized into one or more "nodes," where each node may have one or more "leaf objects." The nodes are organized into a hierarchy with one or more nodes having one or more decedent nodes. It should also be appreciated that the one or more nodes may not have any decedent nodes. The last node in a hierarchal branch can include one or more leaf objects that define a rule and/or contain information associated with a corresponding communication network. For example, the nodes and leaf objects define the various rules and discovery information that are used by the mobile device 140 in governing the ISMP, ISRP, and Discovery processing by the mobile device 140.
The RoutingCriteria node 502 is a placeholder for validity conditions for one or more flow distribution rules. The ValidityArea node 504 is a placeholder for location conditions for one or more flow distribution rules. The ValidityArea node 504 can include one or more decedent nodes, including (but not limited to): 3GPP_Location, 3GPP2_Location, WiMAX_Location, WLAN_Location, and Geo_Location. For the purposes of this discussion, the decedent nodes of the ValidityArea node 504 can collectively be referred to as "location nodes" 508. Each of the various nodes within the location nodes 508 can further include one or more leaf objects, or one or more decedent nodes having one or more leaf object descending therefrom. For example, the WLAN_Location node can include leaf objects HESSID (homogenous extended service set identifier), BSSID (basic service set identifier), and SSID (service set identifier). The HESSID is a media access control (MAC) address that is the same on all access points belonging to a particular network. Similarly, the BSSID and SSID are identifiers used to identify the basic service set (e.g., an access point and one or more stations). For example, BSSID uniquely identifies the basic service set (BSS) and is a MAC address of the wireless access point generated by combining the 24 bit Organization Unique Identifier (e.g., the manufacturer's identity) and the manufacturer's assigned 24-bit identifier for the radio chipset in the access point. The SSID is 1 to 32 byte string and is typically a human-readable string commonly called the "network name." The HESSID, BSSID and SSID are further defined in the IEEE 802.11 standard, which is incorporated herein in its entity.
The TimeOfDay node 506 indicates the time of day condition. The time of day condition is considered valid ("active") if the time of day in the current time zone, as indicated by the mobile device 140, matches at least one time interval indicated in the TimeOfDay node 510. That is, the time of day satisfies one or more of the leaf objects of the TimeOfDay node 506.
The MovementState leaf 544 defines one or more movement states of the mobile device 140. For example, the movement states can include: stationary, pedestrian (e.g., PA3 or PB3), vehicular (e.g., VA30), high-speed rail, aviation, or any other movement states defined by 3GPP, or as would understood by those skilled in the relevant art(s). The pedestrian states PA3 and PB3 refer to the Pedestrian-A (3 km/h) and Pedestrian-B (3 km/h) movement states, respectively, as defined by 3GPP. Similarly, the vehicular state VA30 refers to the Vehicular-A (30 km/h) movement state as defined by 3GPP. The MovementState leaf 544 is considered active if the mobile device 140 determines, based on the estimated movement speed of the mobile device 140, that the mobile device 140 satisfies one of the various movement states defined in the MovementState leaf 544.
The RSSI leaf 546 and the SINR leaf 548 define validity conditions associated with signal strength and quality information of the other communication network (e.g., Wi-Fi network of the AP 150). The RSSI leaf 546 and the SINR leaf 548 define received signal strength indication (RSSI) and signal-to-interference-plus-noise ratio (SINR) thresholds (dB), respectively, for the wireless connection between the mobile device 140 and the other (prospective) communication network. The RSSI leaf 546 and SINR leaf 548 are considered active if the RSSI and the SINR of the connection is above the dB levels set forth in the respective RSSI and SINR leaves 546, 548. Here, the RSSI and SINR leaves 546, 548 collectively serve as a secondary threshold for the wireless connection. That is, the mobile device 140 may have a minimum RSSI and/or SINR threshold value (i.e., a "connection threshold") used for determining if a wireless connection can be established, according to the device hardware specifications. The thresholds defined in the RSSI and SINR leaves 546, 548 can then serve as threshold values that exceed the minimum (device) threshold and thereby ensure a higher quality connection than one that may be formed if only the connection threshold is satisfied.
The ConnectionDuration leaf 550 defines validity conditions associated with connection information for the other communication network (e.g., Wi-Fi network of the AP 150). In particular, the ConnectionDuration leaf 550 defines the duration in which the mobile device 140 and/or one or more other mobile devices have previously remained connected to the other communication network. The mobile device 140 can be configured to estimate the stability of the connection using the durations of one or more previously established connections to the other communication network. For example, multiple, short connection durations by the mobile device 140 (or other mobile devices) may evidence a wireless connection that repeatedly becomes available and unavailable due to an access point that is subject to, for example, shadowing, slow fading, or any other condition resulting in instability in the connection.
In an exemplary embodiment, the mobile device 140 can be configured to estimate the stability of the connection utilizing a Poisson probability distribution with a fixed but unknown lambda Here, the longer connection duration results in a lower estimated lambda, which results in a longer expected duration until the next disconnection. A longer expected duration may evidence a more stable connection.
The Unutilized Rate leaf 552 defines validity conditions associated with data rate information and/or channel utilization information of the other communication network (e.g., Wi-Fi networks of the AP 150). Here, a "data rate validity condition" can be used to refer to the data rate information, the channel utilization information, or a combination of both. In particular, the UnutilizedRate leaf 552 defines an estimated data rate available to the mobile device 140 on, for example, the Wi-Fi network of the AP 150, and an estimated Wi-Fi channel utilization on the network. The data rate can include the estimated maximum bit rate (MBR) and/or guaranteed bit rate (GBR).
The AP 150 can be configured to estimate the data rate on the Wi-Fi network (i.e., via the wireless medium) and the channel utilization using any well-known date rate and/or channel utilization estimation processes that would be understood by those skilled in the relevant art(s), including, for example, estimations based on the "average cycle time" approach discussed in "Throughput Analysis of IEEE 802.11 Wireless LANs using Average Cycle Time Approach," K. Medepalli and F.A. Tobagi, Proceedings of IEEE Globecom 2005, and discussed in U.S. Patent Application No. 14/149,390. filed January 7, 2014 , entitled "Mobile Device With Cellular-WLAN Offload Using Passive Load Sensing Of WLAN".
In operation, the AP 150 can, for example, analyze the current GBR and/or MBR for ongoing services of the AP 150. Here, the ongoing services of the AP 150 refers to one or more active connections to the AP 150 and the respective data rates of these connections. The AP 150 can then compare the value(s) for ongoing services with an estimation of GBR and/or MBR of the AP 150 that includes a prospective connection of the mobile device 140 to determine if the AP 150 can provide reliable offloading to the mobile device 140. For example, the AP 150 can determine that the AP 150 can provide reliable offloading when the estimated GBR is equal to or greater than the total GBR for ongoing services (e.g., ongoing GBR bearers), and the estimated MBR is equal to or greater than a predetermined percentage of the total MBR for ongoing services (e.g., ongoing MBR bearers). That is, the AP 150 can determine that the AP 150 can provide reliable offloading if the following equations are satisfied: GBR estimate ≥ GBR ongoing
MBR estimate ≥ MBR ongoing × β
Where GBRestimate is the estimated GBR, GBRongoing is the total GBR for ongoing services, MBRestimate is the estimated MBR, MBRongoing is the total MBR for ongoing services, and β is a predetermine value such that 0 < β ≤ 1.
The ActivityMode leaf 556 defines validity conditions associated with activity information of the current serving communication network (e.g., LTE network of base station 120). In particular, the ActivityMode leaf 556 is valid ("active") when there is an active data flow (UL and/or DL) on the current serving network (e.g., LTE network). Using this information, the mobile device 140 can improve the current experience on the LTE network by reducing loss of packets due to a handoff to another communication network during an active data flow on the current network. That is, offloading during a current data flow may impact the application usability and performance of the mobile device 140. For example, if the condition of ActivityMode leaf 556 is valid (i.e., there is an active data flow), the mobile device 140 may determine that is it not an appropriate time to offload communications.
After step 630, the flowchart 600 transitions to step 640, where the mobile device 140 determines whether to offload communications from a current serving network (e.g., LTE) to another communication network (e.g., Wi-Fi) utilizing the determined nodal information from step 620 and the current operational information from step 630. That is, the mobile device 140 can be configured to compare the current operational information to nodal information, and/or to compare detected information for the other communication network to the nodal information, to determine whether to effectuate an offloading of communications to the other communication network. For example, the mobile device 140 can compare the current movement information of the mobile device 140 to the validity conditions defined in the device movement leaves 545 to determine whether the mobile device 140 is traveling at a speed conducive for offloading (e.g., the mobile device 140 is moving slowly or is stationary). Similarly, the mobile device 140 can be configured to detect signal information from the Wi-Fi network and compare it to the validity conditions of the RSSI leaf 546 and/or SINR leaf 548. If the current signal information meets or exceeds the thresholds set forth in the RSSI leaf 546 and/or SINR leaf 548, the mobile device 140 can determine that the signal quality is conducive for offloading.
If the mobile device 140 determines that communications should be offloaded to the other communication network (YES at step 640), the flowchart 600 transitions to step 650, where the communications from the current serving network (e.g., LTE) are offloaded to the other communication network (e.g., Wi-Fi).
FIG. 7 illustrates a flowchart 600 of an offloading method in accordance with an exemplary embodiment of the present disclosure. The method of flowchart 700 is described with continued reference to FIGS. 1-6. The steps of the method of flowchart 700 are not limited to the order described below, and the various steps may be performed in a different order. Further, two or more steps of the method of flowchart 400 may be performed simultaneously with each other.
The method of flowchart 700 begins at step 705 and transitions to step 710, where the mobile device 140 determines whether one or more other (prospective) communication networks (e.g., AP 150) is within range of the mobile device 150. In particular, the mobile device 140 can be configured to determine positional information (e.g., location, movement, etc.) of the mobile device 140 using one or more positional sensors (e.g., GPS, accelerometer, etc.) and/or one or more positional determinations using signal characteristics relative to one or more base stations and/or access points. The mobile device 140 is then configured to determine if one or more other communication networks is within range by comparing the positional information to one or more validity conditions of the ValidityArea node 504. For example, the mobile device 140 can compare the positional information to one or more of the location nodes 508.
At step 730, the mobile device 140 determines whether the signal quality on the other communication network is conducive for the offloading of communication from the current serving network. For example, the mobile device 140 can be configured to analyze the signal quality (e.g., signal strength, noise, etc.) by comparing one or more validity conditions of the RSSI leaf 546 and/or SINR leaf 548 to signal quality information of the other communication network that is detected by the mobile device 140. Here, the mobile device 140 can determine that the signal quality on the other communication network is conducive for the offloading of communications if, for example, the detected RSSI and/or SINR of the other communication network matches or exceeds the corresponding RSSI and SINR thresholds set forth in the RSSI leaf 546 and SINR leaf 548, respectively.
If the mobile device 140 determines that the signal quality is sufficient for offloading (YES at step 730), the flowchart transitions to step 735. Otherwise (NO at step 730), the flowchart transitions to step 760, where the mobile device 140 determines not to offload communications to the other communication network.
The aforementioned description of the specific embodiments will so fully reveal the general nature of the disclosure that others can, by applying knowledge within the skill of the art, readily modify and/or adapt for various applications such specific embodiments, without undue experimentation, without departing from the general concept of the present disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled artisan in light of the teachings and guidance.
References in the specification to "one embodiment," "an embodiment," "an exemplary embodiment," etc indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic Moreover, such phrases are not necessarily preferring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
The exemplary embodiments described herein are provided for illustrative purposes, and are not limiting Other exemplary embodiments are possible, and modifications may be made to the exemplary embodiments within the scope of the disclosure. Therefore, the specification is not meant to limit the disclosure. Rather, the scope of the disclosure is defined only in accordance with the following claims and their equivalents.
Embodiments may be implemented in hardware (e.g., circuits), firmware, software, or any combination thereof Embodiments may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), and others. Further, firmware, software, routines, instructions may be described herein as performing certain actions. However, it should be appreciated that such descriptions are merely for convenience and that such actions in fact results from computing devices, processors, controllers, or other devices executing the firmware, software, routines, instructions, etc. Further, any of the implementation variations may be carried out by a general purpose computer.
A communication device (140), comprising:
a first transceiver (400) configured to communicate with a first communication network (110);
a second transceiver (430) configured to communicate with a second communication network (112); and
a controller (440) configured to: receive an offloading framework via the first communication network; and
offload communications from the first communication network to the second communication network based on one or more communication parameters defined in the offloading framework, wherein
the one or more communication parameters include a parameter that defines a data rate validity condition for the second communication network, wherein the data rate validity condition defines a comparison of a data rate of an active connection of a second communications device on the second communication network with an estimated data rate of a prospective connection of the communications device on the second communication network.
The communication device of claim 1, wherein the data rate of the active connection comprises a current guaranteed bit rate and a current maximum bit rate, and the estimated data rate of the prospective connection comprises an estimated guaranteed bit rate and an estimated maximum bit rate.
The communication device of claim 1 or 2, wherein the one or more communication parameters include a parameter that defines a movement state of the communication device.
The communication device of claim 3, wherein the movement state includes at least one of: a Pedestrian-A movement state, a Pedestrian-B movement state, and a Vehicular-A movement state.
The communication device of any preceding claim, wherein the one or more communication parameters include a parameter that defines a received signal strength indication (RSSI) threshold or a signal-to-interference-plus-noise ratio (SINR) threshold for the second communication network.
The communication device of any preceding claim, wherein the one or more communication parameters include a parameter that defines a time duration that the communication device or another communication device has previously remained connected to the second communication network.
The communication device of claim 1, wherein the controller is configured to compare the data rate to the estimated data rate, and offload the communications from the first communication network to the second communication network based on the comparison.
The communication device of claim 1 or 7, wherein the estimated data rate is estimated by an access point supporting the second communication network.
The communication device of any preceding claim, wherein the one or more communication parameters include a parameter that defines Wi-Fi multimedia (WMM) mapping of the second communication network.
The communication device of any preceding claim, wherein the WMM mapping includes at least one of packet priority information, packet error loss rate information or packet delay budget information.
The communication device of any preceding claim, wherein the first communication network is a Long-Term Evolution (LTE) communication network and the second communication network is a Wi-Fi communication network.
receiving an offloading framework via a first communication network, the offloading framework defining one or more communication parameters; and
offloading communications from the first communication network to a second communication network based on the one or more communication parameters of the offloading framework, wherein
the one or more communication parameters include a parameter that defines a data rate validity condition for the second communication network, wherein the data rate validity condition defines a comparison of a data rate of an active connection of a second communications device on the second communication network with an estimated data rate of a prospective connection of a communications device on the second communication network.
The communication method of claim 12, further comprising:
determining operational information of the communication device configured to operate in the first communication network; and
offloading communications from the first communication network to the second communication network based on a comparison of the operational information and the one or more communication parameters of the offloading framework.
The communication method of claim 12, wherein the data rate of the active connection comprises a current guaranteed bit rate and a current maximum bit rate, and the estimated data rate of the prospective connection comprises an estimated guaranteed bit rate and an estimated maximum bit rate.
The communication device of claim 1, wherein the controller is further configured to:
receive an Access Network Discovery and Selection Function (ANDSF) framework via the first communication network, the ANDSF framework including a movement parameter, a signal quality parameter, a connection duration parameter, the parameter that defines the data rate validity condition, and a quality of service (QoS) parameter; and
EP14000053.0A 2013-01-08 2014-01-08 Systems and methods for network discovery and selection using contextual information Active EP2753124B1 (en)
EP2753124A1 EP2753124A1 (en) 2014-07-09
EP2753124B1 true EP2753124B1 (en) 2016-06-22
EP14000053.0A Active EP2753124B1 (en) 2013-01-08 2014-01-08 Systems and methods for network discovery and selection using contextual information
ES2693463T3 (en) * 2013-05-06 2018-12-11 Intel IP Corporation Discovery and selection of access network
US10673600B2 (en) * 2014-10-30 2020-06-02 Lg Electronics Inc. Method and apparatus for handling abnormal situations at cell of unlicensed carrier in wireless communication system
WO2016071176A1 (en) * 2014-11-07 2016-05-12 Nokia Solutions And Networks Oy Transmission of discovery reference signals on unlicensed carrier in a wireless network
US10433215B2 (en) * 2015-01-06 2019-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Method for controlling multipoint TCP in wireless communications networks and devices for use therein
CN106550400A (en) * 2015-09-23 2017-03-29 上海无线通信研究中心 Interference management method and the flow discharging method and device using the method
CN107046696A (en) * 2017-04-14 2017-08-15 努比亚技术有限公司 The method and mobile terminal of a kind of communication network switching
EP2437546A1 (en) * 2010-10-04 2012-04-04 Alcatel Lucent Device for controlling communication transfers of mobile equipments between wireless access networks having different access technologies, based on a load- balancing
CN102007800B (en) * 2008-04-18 2014-12-10 艾利森电话股份有限公司 Access network selection in a multi-access network environment
JP5809295B2 (en) * 2011-02-24 2015-11-10 インターデイジタル パテント ホールディングス インコーポレイテッド The concept and use of stable local breakout
US9654931B2 (en) * 2011-08-23 2017-05-16 At&T Intellectual Property I, L.P. Mobile device network configuration via speed determination
EP2752055A1 (en) * 2011-08-31 2014-07-09 Telefonaktiebolaget L M Ericsson (publ) Andsf policy controlled access network discovery information
KR20150079995A (en) * 2011-10-03 2015-07-08 인텔 코포레이션 Device to device(d2d) communication mechanisms
US8976663B2 (en) * 2012-04-05 2015-03-10 Telefonaktiebolaget L M Ericsson (Publ) QCI based offloading
US9560584B2 (en) 2013-01-08 2017-01-31 Broadcom Corporation Mobile device with cellular-WLAN offload using passive load sensing of WLAN
US9544808B2 (en) 2017-01-10
TWI568305B (en) 2017-01-21 Systems, devices, and methods for long term evolution and wireless local area interworking
AU2016233959B2 (en) 2019-02-14 Method and apparatus for traffic aggregation setup between WLAN and 3GPP
US9191874B2 (en) 2015-11-17 Advanced network characterization and migration
US20160050698A1 (en) 2016-02-18 System and Method for Obtaining and Using Device-to-Device Frequency-Related Capability and Configuration Preferences
TW201503721A (en) 2015-01-16 Handover of user equipment with non-GBR bearers
WO2014051951A1 (en) 2014-04-03 Method and apparatus for autonomous cluster head selection for machine-type-communications (mtc)
CN109041137B (en) 2020-01-17 Switching method, base station and terminal equipment
US9973980B2 (en) 2018-05-15 Communications methods and apparatus that facilitate handover decisions and related measurements
Ref document number: 808282
Ref document number: 602014002346