US20160112577A1 - Managing network data transfers in view of multiple data usage plans - Google Patents

Abstract

Embodiments manage data transfers using a plurality of data usage plans available to a computing device. Each of the data usage plans has data usage statistics representing an amount of network data consumed under the data usage plan. For each data transfer request received from applications executing on the computing device, a service executing on the computing device or in a cloud defines a network data transfer configuration for performing the data transfer request. The network data transfer configuration is defined based on, for example, the data usage plans, the data usage statistics, and the data transfer request to reduce transfer costs and/or provide a particular quality of service (QoS).

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
• This application claims the benefit of U.S. application Ser. No. 13/721,058 filed Dec. 20, 2012, which claims the benefit of U.S. Provisional Application No. 61/696,472 filed Sep. 4, 2012; U.S. Provisional Application No. 61/591,503 filed Jan. 27, 2012; and U.S. Provisional Application No. 61/591,509 filed Jan. 27, 2012. The entirety of these applications is hereby incorporated by reference herein.
• This application is related to the following U.S. applications: U.S. patent application Ser. No. 13/721,023 filed Dec. 20, 2012; U.S. patent application Ser. No. 13/721,029 filed Dec. 20, 2012; U.S. patent application Ser. No. 13/721,032 filed Dec. 20, 2012 and issued as U.S. Pat. No. 9,049,589; U.S. patent application Ser. No. 13/721,041 filed Dec. 20, 2012; U.S. patent application Ser. No. 14/642,378 filed Mar. 9, 2015, which is a continuation application of U.S. patent application Ser. No. 13/721,053 filed Dec. 20, 2012 and issued Mar. 10, 2015 as U.S. Pat. No. 8,977,231; U.S. patent application Ser. No. 13/721,066 filed Dec. 20, 2012; U.S. patent application Ser. No. 13/721,069 filed Dec. 20, 2012; and U.S. patent application Ser. No. 13/721,083 filed Dec. 20, 2012. The entirety of these applications is hereby incorporated by reference herein.
BACKGROUND
• With the increased popularity of smart telephones, tablets, and other mobile devices, there has been a similar increase in the amount of data handled by the networks of mobile operators. To reduce the strain on network infrastructure and to reduce network transfer costs, mobile operators are shifting from offering unlimited mobile data plans to offering capped and metered plans. With some of the capped and metered plans, the fees for exceeding the allotted data caps may be significant. While some existing web browsers attempt to optimize data traffic, the existing systems generally lack mechanisms for balancing specific needs of each user with data transfer costs. Further, existing systems fail to consider the multiple mobile data plans that may be available to the user.
• As a result, with the existing systems, users can unknowingly exceed the allotted data caps and experience bandwidth throttling (e.g., a reduction or limit placed upon the rate of consumption) and/or be presented with a much larger than normal monthly bill, resulting in “bill shock.” Throttling and bill shock can impact the user experience, leading to dissatisfied customers, increased customer service calls, and negative impressions of the mobile operators.
SUMMARY
• Embodiments of the disclosure manage a plurality of data usage plans available to a computing device for data transfer. Each of the plurality of data usage plans has data usage statistics representing an amount of network data consumed under the data usage plan. Upon receipt of a data transfer request from an application executing on the computing device, a mobile operator and network connection are selected based at least on the plurality of data usage plans, the associated data usage statistics, and the received data transfer request. The data transfer request is initiated using the selected mobile operator and network connection.
• This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is an exemplary block diagram illustrating a mobile computing device with multiple available data usage plans.
• FIG. 2 is an exemplary flow chart illustrating operation of the computing device to select a network data transfer configuration based on estimated transfer costs and/or quality of service metrics using a plurality of data usage plans.
• FIG. 3 is an exemplary flow chart illustrating operation of the computing device to present offers to a user for adjusting a network data transfer.
• FIG. 4 is an exemplary flow chart illustrating operation of the computing device to adjust a network data transfer configuration during performance of a data transfer request.
• Corresponding reference characters indicate corresponding parts throughout the drawings.
DETAILED DESCRIPTION
• Referring to the figures, embodiments of the disclosure provide efficient routing of network data traffic overmultiple networks109 using multipledata usage plans116 to manage data consumption. In particular, plan aware routing selections are made by determining which data usage plan116 to leverage for which network data traffic. Aspects of the disclosure operate as a service executing on amobile computing device102 and/or as a cloud service. Based at least on the factors, preferences, criteria, or other inputs, the service identifies at least onedata usage plan116, at least one of thenetworks109, and mobile operator credentials to present to the identifiednetwork109 for a particulardata transfer request115, in some embodiments.
• While some existing systems may make routing decisions based solely on internally sourced measures (e.g., power consumption), aspects of the present disclosure balance externally sourced, relatively static information (e.g., thedata usage plans116 from mobile operators111) with dynamic runtime information to make routing decisions that are in the best interest of theuser104. The dynamic runtime information may be measurable on the device, highly variable over time, and device-specific. For example, the dynamic runtime information may change over time depending on the device's relationship with the network connections130 (e.g., in view of thedata usage plan116 of theuser104, and the cost of each network connection130). In some embodiments, the service performs operations to calculate or estimate the amount of power and network data to be consumed by adata transfer request115 over multipledifferent networks109 each having different data usage plans116 (e.g., usage allotments, tariffs, etc.). As an example, the financial cost (e.g., dollars) or resource cost (e.g., power consumption) to connect to one cellular tower may differ from the cost to connect to another cellular tower.
• Aspects of the disclosure are operable with emerging tariff models such as where traffic is prorated and even subsidized bydifferent applications114 on different mobile operators111 (or different plans from the same mobile operators111). The service is also operable with shareddata usage plans116, such as family plans, and in environments in whichapplications114 and services share connections. The service is also operable in embedded subscriber identity module (SIM) environments in whichdata usage plans116 are dynamically activated as needed, or thedata usage plan116 of a proximate or neighboring device is used. In some embodiments, an embedded SIM is a software-based SIM residing possibly on the motherboard of the computing device, rather than a SIM residing on the universal integrated circuit card (UICC) in the computing device.
• Referring next toFIG. 1, an exemplary block diagram illustrates themobile computing device102 with multiple availabledata usage plans116 performing network data transfers via thenetwork109. Aspects of the disclosure manage data transfers using the plurality ofdata usage plans116. User computing devices include, for example, themobile computing device102 andother computing devices106. The user computing devices communicate over one or more of thenetworks109. In some embodiments, one or more of the user computing devices are associated with one of thedata usage plans116. Thedata usage plan116 represents the terms and/or conditions (e.g., network data consumption allotment) under which themobile operator111 provides data transfer services to the user computing devices. For example, a plurality of the user computing devices may share network data consumption allotted under the same or commondata usage plan116.
• The user computing devices include any device executing instructions (e.g., as application programs, operating system functionality, or both) to implement operations and functionality. The user computing devices may include, for example, themobile computing device102 or any other portable device. In some embodiments, themobile computing device102 includes a mobile telephone (e.g., mobile telephone602 inFIG. 6), laptop, tablet, computing pad, netbook, gaming device, e-reader, and/or portable media player. Theother computing devices106 may include less portable devices such as desktop personal computers, kiosks, and tabletop devices that have network connectivity capabilities. Additionally, each user computing device may represent a group of processing units. While aspects of the disclosure may be described herein with reference to themobile computing device102, the descriptions are applicable to any of the user computing devices.
• Communication to/from the user computing devices may occur using any protocol or mechanism over one or more of thenetworks109. Thenetworks109 represent any infrastructure or other means for sending and/or receiving data. Thenetworks109 may include wired and/or wireless networks.
• One or more of themobile operators111 communicate with theweb service108 and/or the user computing devices via thenetwork109. Further, the user computing devices communicate with theweb service108, or other entity that performs the operations described herein as being associated with theweb service108.
• In some embodiments, themobile computing device102 and theother computing devices106 are associated with a commondata usage plan116 of theuser104. For example, themobile computing device102 may represent the mobile telephone602 of theuser104, while theother computing devices106 may include a tablet and a laptop associated with theuser104. In other embodiments, themobile computing device102 and each of theother computing devices106 are associated with separate data usage plans116.
• In some embodiments, each of the user computing devices collectsdata usage statistics120 relating thereto. For example, a data transfer service, or other entity executing on themobile computing device102, generates, monitors, collects, compiles, and/or receives thedata usage statistics120 relating to network data consumption by theapplications114 executing on themobile computing device102. Thedata usage statistics120 represent an amount of network data consumed by themobile computing device102 under thedata usage plan116. Alternatively or in addition, thecentralized web service108 interacts with the user computing devices and themobile operators111 to collect thedata usage statistics120 on each of the user computing device. Theweb service108 may further aggregate thedata usage statistics120, such as for shared data usage plans116. In such embodiments, theweb service108 may receive a schema populated with data relating to thedata usage plan116 from themobile operator111, and distribute the populated schema to one or more of the user computing devices associated with the samedata usage plan116.
• In some embodiments, themobile computing device102 has at least one or more SIMs113 (e.g., dual SIMs), oneprocessor110, amemory area112, and at least one user interface (not shown). Theprocessor110 includes any quantity of processing units, and is programmed to execute computer-executable instructions for implementing aspects of the disclosure. The instructions may be performed by theprocessor110 or by multiple processors executing within themobile computing device102, or performed by a processor external to themobile computing device102. In some embodiments, theprocessor110 is programmed to execute instructions such as those illustrated in the figures.
• In some embodiments, theprocessor110 represents an implementation of analog techniques to perform the operations described herein. For example, the operations may be performed by an analog computing device and/or a digital computing device.
• Themobile computing device102 further has one or more computer readable media such as thememory area112. Thememory area112 includes any quantity of media associated with or accessible by themobile computing device102. Thememory area112 may be internal to the mobile computing device102 (as shown inFIG. 1), external to the mobile computing device102 (not shown), or both (not shown). In some embodiments, thememory area112 includes read-only memory and/or memory wired into an analog computing device.
• Thememory area112 stores, among other data, one ormore applications114. Theapplications114, when executed by theprocessor110, operate to perform functionality on themobile computing device102.Exemplary applications114 include mail application programs, web browsers, calendar application programs, address book application programs, messaging programs, media applications, location-based services, search programs, and the like. Theapplications114 may communicate with counterpart applications or services such as theweb services108 accessible via thenetwork109. For example, theapplications114 may represent downloaded client-side applications that correspond to server-side services executing in a cloud.
• Themobile computing device102 further establishes and maintains one ormore network connections130 representing communication channels or other means for sending and/or receiving data over thenetwork109.Exemplary network connections130 include, but are not limited to, Wi-Fi, cellular, tethered, BLUETOOTH brand communication, near-field communication (NFC), and more. Thenetwork connections130 may also be categorized into voice, text, data, or other categories or types of network traffic.
• Thememory area112 further stores a plurality of data transfer requests115 received from one or more of theapplications114. The data transferrequests115 represent requests by theapplications114 for use of at least one of thenetwork connections130. For example, the data transfer requests115 represent requests from theapplications114 to upload and/or download data.
• Thememory area112 further stores data describing at least onedata usage plan116 associated with theuser104. In some embodiments, thememory area112 stores a plurality of data usage plans116. The data describing the data usage plans116 may be received from themobile operators111 offering the data usage plans116. For example, there may be multiple data usage plans116 active pernetwork connection130.
• The different data usage plans116 embody different cost attributes and tariff models. In some embodiments, themobile operators111 may havecertain applications114 subsidize the data traffic overcertain networks109. For example, network traffic for Application A may be paid, all or in part, by the developer/owner/publisher of Application A. In another example, Application A may be free on onenetwork109 while Application B is free on adifferent network109. Themobile computing device102 works with micro-tariffing models such as per-minute charges or per kilobyte charges, as well as per-session charges such as a video call in which the call is metered at a flat rate regardless of the duration of the call. Other billing models are contemplated, such as per-day. The tariff models may differ fromnetwork109 tonetwork109, fromdata usage plan116 todata usage plan116, and fromuser104 touser104.
• Themobile computing device102 considers the subsidy data, limits, current consumption, and more of each of the data usage plans116 as input to make a routing selection that reduces network transfer charges to theuser104. Themobile computing device102 is aware of whichapplication114 is requesting a network transfer, and matches the request to thenetwork109 that results in the lowest cost and/or best quality of service (QoS) for the user104 (e.g., as specified byuser104 or application preferences, or by other entities). In such embodiments, themobile computing device102 may switch and route rapidly to address each of the network transfer requests, as further described below.
• Some of the data usage plans116 may be dynamic. Such dynamic data usage plans116 adapt and change based on usage in multi-SIM environments or in shared environments such as with a familydata usage plan116. The dynamic data usage plans116 are adjusted over time.
• Thedata usage plan116 may be represented by a schema (e.g., an extensible markup language schema) or other data structure. For example, theuser104 has contracted with themobile operator111 to receive network data transfer services from themobile operator111. Thedata usage plan116 describes the services provided by themobile operator111, such as the amount of network data theuser104 can consume during a particular duration (e.g., a billing time period). For example, thedata usage plan116 describes threshold values118 associated with thenetwork connections130 of one or more devices of theuser104. The threshold values118 represent a maximum amount of network data consumption allotted under thedata usage plan116 for thenetwork connections130. For example, onethreshold value118 may indicate a maximum amount of network data consumption for a Wi-Fi connection, while anotherthreshold value118 indicates a maximum amount of network data consumption for a cellular data connection.
• The schema or other data structure representing thedata usage plan116 may be defined by theweb service108, by themobile operator111, or by another entity. In some embodiments, each of the various data usage plans116 subscribed to by themobile computing device102 and theother computing devices106 use the same common schema. In general, the schema enables descriptions of the parts, components, services, features, or other aspects of thedata usage plan116 including, but not limited to, multi-rate data plans, peak times, roaming rates, allotted network data consumption pernetwork connection130, etc. In some embodiments, use of the schema allows themobile operators111 to send out updated portions of the schema corresponding to updated parts of a particulardata usage plan116.
• In some embodiments, the schema includes a plurality of fields. Each of the threshold values118 may be associated with one or more of the fields. For example, the fields may correspond to one or more of the following: peak times, off-peak times, peak time network data consumption quota, off-peak time network data consumption quota, peak time network data consumption remaining, off-peak time network data consumption remaining, a roaming rate, rules, a mobile operator name, a billing cycle type, a network connection type, identification of free hosts available for connection, a list of mobile hotspots, and any other elements or information pertaining to thedata usage plan116. The list of free hosts represents zero-rated or reduced cost hosts (e.g., visiting particular web sites does not count against the data usage plan116).
• The schema may also include fields supporting different billing rates per host accessed, per weekend, per night, friends and family rates, peak and off-peak rates, and more. The schema also allows eachmobile operator111 the flexibility to define complex plans including broadly offered plans, and dynamic, short-term offers tospecific users104 likely to use a specific part or parts of the overall services. Other offers based on any combination of the metrics obtained are available to themobile operator111.
• The schema stored by themobile computing device102 may also include fields corresponding to thedata usage statistics120 collected, generated, or received by themobile computing device102 and/or themobile operators111. For example, to facilitate sharing thedata usage statistics120 among themobile operators111,web service108, and/or user computing devices, themobile operators111,web service108, and the user computing devices may populate the schema with thedata usage statistics120.
• Thememory area112 further stores thedata usage statistics120 relating to one or more of the data usage plans116. Thedata usage statistics120 may be viewed as a current or instant snapshot of the amount of network data transmitted and/or received (e.g., or otherwise consumed) by themobile computing device102. For example, themobile computing device102 collects ongoing usage data relating to network data transfers, such as from device radios, drivers, and accelerometers of themobile computing device102. Thedata usage statistics120 identify, to a granularity of time (e.g., per minute) or data (e.g., per kilobyte), how much data has been sent and/or received by themobile computing device102, the time and date of usage (e.g., start and end times), the location of usage, network interface used (e.g., over which network connections130), roaming state, data usage plan information, theSIM113 card or other user identity module used for dual SIM scenarios, the international mobile station equipment identity (IMEI) or other device identifier for multi-device scenarios, the Internet protocol (IP) address or other address of the access point used for Wi-Fi scenarios, the IP address or other address of the target computer (e.g., for whitelist/blacklists in data usage), the application responsible for the data transfer, and the like. In a further example, information relating to text messages, data, voice calls, minutes used, voice over Internet Protocol (VoIP) usage, and any other element of usage consumed by, or that impacts, themobile computing device102 is collected to produce thedata usage statistics120. Otherdata usage statistics120 are also contemplated.
• Thedata usage statistics120 may be collected by themobile computing device102, theweb service108, and/or themobile operators111. For example, thedata usage statistics120 may be compiled directly (e.g., by monitoring network traffic) and/or by collecting thedata usage statistics120 from other devices that perform the collection. In embodiments such as those described below with reference toFIG. 2,FIG. 3, and/orFIG. 4, thedata usage statistics120 corresponding to a plurality of data usage plans116 are collected such that there may be a plurality of sets of collected data usage statistics120 (e.g., one set for eachdata usage plan116 or user104).
• Alternatively or in addition, themobile computing device102 receives updates of network data consumption by theother computing devices106 sharing the samedata usage plan116. For example, thedata usage statistics120 may represent the network data collectively consumed by the mobile telephone602, tablet, and laptop of theuser104.
• Thememory area112 further stores exemplary computer-executable components such as amemory component128, acommunications interface component126, aprediction component122, and afilter component124. Operation of the computer-executable components, when executed, is described below with reference toFIG. 2.
• Themobile computing device102 may have any quantity ofSIMs113 associated therewith. For example, each of theSIMs113 may be embedded and implemented as an application program performing operations to implement functionality associated with theSIM113. In some embodiments, themobile computing device102 hasdual SIMs113 with one of theSIMs113 in standby mode (e.g., dual SIM dual standby). Alternatively or in addition, themobile computing device102 hasdual SIMs113 with both of theSIMs113 being independently active (e.g., dual SIM dual active). Additional examples include virtual SIMs, universal integrated circuit cards (UICCs), and other variants of user identity modules.
• Each of theSIMs113 is associated with at least one of the plurality of data usage plans116. Aspects of the disclosure operate to leverage the available data usage plans116 to route network traffic over thenetwork connections130 using one or more of theSIMs113. For example, themobile computing device102 makes a decision as to whichSIM113 gets attached to which radio in software based upon a data costing analysis. Themobile computing device102 relies on the data costing analysis (e.g., a comparison of the costs of using thedifferent SIMs113 on the different radios in view of the data usage plans116 for each) to determine which of theSIMs113 should be active to handle thedata transfer request115.
• As an example, one of the data transfer requests115 may represent an incoming voice call on a first data usage plan associated with a first SIM. Aspects of the disclosure may determine to answer the incoming voice call with a second data usage plan of a second SIM. For example, the second data usage plan may provide a reduced cost for the data transfer, and/or a better QoS.
• Themobile computing device102 is further operable with more than one cellular radio. For example, themobile computing device102 may include a plurality of radios with at least two of those radios consuming battery power at different rates. In such environments, themobile computing device102 selects themobile operator111 andnetwork connection130 for eachdata transfer request115 to balance network data usage against battery usage. In an example in which themobile computing device102 has a single radio, actively selecting different networks109 (e.g., via different data usage plans116) may cause themobile computing device102 to connect to different cell towers, which in turn may impact battery usage. For example, connecting to one cell tower may consume more battery power than connecting to another cell tower, which affects the amount of power anticipated to be consumed when performing the data transfer requests115 over thevarious network connections130.
• Themobile computing device102 represents an example of a computing device programmed to perform operations to manage network data transfers using a plurality of data usage plans116 available to theuser104. For example, and as described further with reference to the flowcharts, the computing device receives or accesses at least one of the data transfer requests115 and defines a network data transfer configuration for performing the selecteddata transfer request115. For example, the computing device selects one or more of the following: at least one of the data usage plans116, themobile operator111, and at least one of theavailable network connections130. Selecting themobile operator111 includes, for example, selecting mobile operator credentials to present to the selectednetwork109 when initiating the data transfer. In some embodiments, selecting themobile operator111 includes selecting the international mobile subscriber identity (IMSI) in theSIM113.
• The network data transfer configuration is defined based on, for example, the particulardata transfer request115, the available data usage plans116 (e.g., data transfer costs, etc.), and thedata usage statistics120 associated with each of the data usage plans116 (e.g., the amount of network transfer data consumed and/or remaining, etc.). The computing device proceeds to initiate thedata transfer request115 using the defined network data transfer configuration.
• Referring next toFIG. 2, an exemplary flow chart illustrates operation of the computing device to select the network data transfer configuration for performing data transfer requests115 based on estimated transfer costs and/or quality of service metrics using a plurality of data usage plans116. While the operations illustrated inFIG. 2 are performed by amobile computing device102 in some embodiments, one or more of the operations may be performed by other devices, including any computing device local to, or remote from, theuser104. For example, the operations may be performed by theweb service108, or by a proxy device in communication with theweb service108 and themobile computing device102. Further, in some embodiments, the operations illustrated inFIG. 2 are performed by an operating system executing on themobile computing device102.
• The operations illustrated inFIG. 2 may be described as mapping the data transferrequests115 to the detectednetwork connections130 using the plurality of available data usage plans116 to reduce or minimize data transfer costs and/or provide a QoS suitable for the data transfer requests115. For example, the computing device works to prevent incurring expensive network transfer costs for theuser104.
• In some embodiments, the computing device may store, or have access to, the computer-executable components stored in thememory area112 to implement one or more of the operations illustrated inFIG. 2. For example, thememory component128, when executed by the computing device, causes at least oneprocessor110 to store a plurality of the data usage plans116 available to the computing device. Each of the data usage plans116 hasdata usage statistics120 associated therewith representing an amount of network data consumed under the data usage plan116 (e.g., during the current billing cycle).
• At202, the computing device accesses the data usage plans116 stored by thememory component128. Thecommunications interface component126, when executed by the computing device, causes at least oneprocessor110 to determine whether at least one of the data transfer requests115 has been received from at least one of a plurality ofapplications114 executing on the computing device at204. In some embodiments, thecommunications interface component126 accesses thememory area112 to retrieve or obtain the data transfer requests115 that have been stored or queued there by theapplications114. In some embodiments, thecommunications interface component126 includes a network interface card and/or computer-executable instructions (e.g., a driver) for operating the network interface card. In some embodiments, the communications interface is operable with near-field communication (NFC) tags.
• On receipt of at least one of the data transfer requests115, theprediction component122, when executed by the computing device, causes at least oneprocessor110 to calculate an estimated transfer cost for thedata transfer request115 using each of the data usage plans116 at206. For example, theprediction component122 uses the terms and conditions (e.g., rates, surcharges, etc.) of each of the data usage plans116 to estimate the cost of transferring data specified by thedata transfer request115.
• In some embodiments, the computing device further executes theprediction component122 to calculate an estimated QoS for thedata transfer request115 using each of the plurality of data usage plans116 at208. For example, theprediction component122 uses the terms and conditions (e.g., rates, surcharges, etc.) of each of the data usage plans116 to estimate the QoS that would be realized when transferring data specified by thedata transfer request115. The QoS may be defined by latency, throughput, etc. The QoS analysis enables thefilter component124 to meet or exceed user experience immediacy expectations by differentiating the urgency of network traffic. The user experience immediacy expectations may be defined by theusers104, theapplications114, the computing device, themobile operator111, and/or theweb service108, in some embodiments. For example, the computing device may receive or access data indicating that while Network A may be cheaper than Network B, the reception on Network A is poor whereas the reception on Network B is good. As such, thefilter component124 may choose to route the traffic on Network B to meet QoS criteria.
• Thefilter component124, when executed by the computing device, causes at least oneprocessor110 to define the network data transfer configuration for thedata transfer request115. For example, thefilter component124 selects at least one of the data usage plans116 and at least one of a plurality ofnetwork connections130 available to the computing device at210. In some embodiments, thefilter component124 determines whichSIM113 or other credential is attached in a multi-SIM environment. Thefilter component124 may implement a best-fit, binary search, neural feedback, or any other algorithm or set of algorithms to produce the output routing decisions or recommendations.
• In some embodiments, thefilter component124 selects from a plurality ofmobile operators111. For example, thefilter component124 selects onemobile operator111 over the others based on the network transfer cost associated with the selectedmobile operator111. In such embodiments, thefilter component124 accesses or receives data describing the availablemobile operators111 in a given locale or area, as well as the costs associated with using each of the mobile operators111 (e.g., defined in the data usage plans116 of the mobile operators111).
• Thecomputing device102 detects, or is informed of, theavailable network connections130. For example, thecomputing device102 may determine whether thenetwork connection130 has been established and/or has not expired. As another example, thecomputing device102 may send a test packet (e.g., a ping) over eachopen network connection130 to confirm the availability of eachnetwork connection130. In some embodiments, thecomputing device102 may further classify each of the detectednetwork connections130. For example, thenetwork connections130 may be classified according to type, speed, cost, and/or other factors or criteria.
• The network data transfer configuration is defined based at least on the estimated transfer costs using the different data usage plans116 and/or the estimated QoS using the different data usage plans116. The defined network data transfer configuration, or the mapping between thedata transfer request115 and thenetwork connection130 may be stored, for example, in a file, table, database, or other data structure.
• In a cost-based example, the cost of the duration of the transfer with Network B may ultimately exceed a flat rate cost associated with Network A. In such an example, thefilter component124 calculates an estimated transfer cost over eachnetwork109 and routes the traffic on thelower cost network109.
• Thefilter component124 may also consider speed or data transfer rates when defining the network data transfer configuration. For example, if it takes five seconds to transfer two gigabytes of data over Network A but two hours over Network B, thefilter component124 may opt to incur charges with Network A to complete the data transfer faster if completion is a priority or preference for theuser104 or requestingapplication114.
• Thedata transfer request115 is then initiated at212 using the defined network data transfer configuration (e.g., the selecteddata usage plan116,network connection130, and/or mobile operator111). For example, thecomputing device102 directly initiates thedata transfer request115, or thecomputing device102 may notify theapplication114 that submitted thedata transfer request115 of the defined network data transfer configuration to enable thatapplication114 to initiate thedata transfer request115.
• In some embodiments, thefilter component124 performs, or relies on the output of, a cost-benefit analysis based on the estimated transfer cost and/or the estimated QoS. For example, thefilter component124 selects thedata usage plan116, thenetwork connection130, and/or themobile operator111 with the lowest estimated transfer cost and/or highest estimated QoS. In general, thefilter component124 determines whichnetwork connection130 to use for whichdata transfer request115 and for what duration.
• In an example in which a first data usage plan has additional network data consumption available while a second data usage plan has no additional network data consumption available without incurring excess charges fees, thefilter component124 selects the first data usage plan to prevent overage charges. The first data usage plan may represent a familydata usage plan116, or other shareddata usage plan116.
• In some embodiments, thecomputing device102 tracks a cumulative amount of data transfers occurring under each of the data usage plans116 to identify data usage plans116 with remaining capacity. Thecomputing device102 compares the tracked, cumulative amounts to the corresponding threshold values118 associated with the data usage plans116. Thecomputing device102 maps the data transferrequests115 to the data usage plans116 based on the comparison. For example, thecomputing device102 determines whether the tracked, cumulative amounts for eachdata usage plan116 are less than the corresponding threshold values118 for thatdata usage plan116. If thecomputing device102 determines that there is remaining network data consumption available under a particular one of the data usage plans116 (e.g., the cumulative amounts are less than the threshold values118 for that data usage plan116), thecomputing device102 may match the data transfer request to that particulardata usage plan116. For the data usage plans116 under which no further data consumption is available or under which the estimated transfer cost is above a pre-defined threshold, thecomputing device102 removes those data usage plans116 from consideration when mapping the data transferrequests115 to the data usage plans116. In a further embodiment, the data usage plans116 with remaining capacity may be ranked or sorted according to remaining capacity.
• Some embodiments evaluate the data transfer statistics associated with each of the data usage plans116 to determine whether theuser104 is Off Track, On Track, Under Track, or Over Limit for usage compared to the consumption allotted under each of the data usage plans116. For example, given the day of the billing cycle and the current or up-to-date data consumption for the billing period, an extrapolation or projection is performed to predict the consumption associated with the end of the billing cycle. In some embodiments, Off Track may be defined as theuser104 being on or above the projected limit (e.g., the value of the curve) given the day of the billing cycle and the current or up-to-date data consumption for the billing period. On Track may be defined, in some embodiments, as theuser104 being at least 5% below the projected limit given the day of the billing cycle and the current or up-to-date data consumption for the billing period. Under Track may be defined, in some embodiments, as theuser104 being at least 20% below the projected limit given the day of the billing cycle and the current or up-to-date data consumption for the billing period. Some embodiments contemplate an “Over Limit” category that allowsusers104 to opt out of data consumption by background transfers unless the background transfers are user-initiated or deemed critical.
• In some embodiments, themobile computing device102 further includes a user interface component that includes a graphics card for displaying data to theuser104 and for receiving data from theuser104. The user interface component may also include computer-executable instructions (e.g., a driver) for operating the graphics card. Further, the user interface component may include a display (e.g., a touch screen display or natural user interface) and/or computer-executable instructions (e.g., a driver) for operating the display. The user interface component may also include one or more of the following to provide data to theuser104 or receive data from the user104: speakers, a sound card, a camera, a microphone, a vibration motor, one or more accelerometers, a BLUETOOTH brand communication module, global positioning system (GPS) hardware, and a photoreceptive light sensor. For example, theuser104 may input commands or manipulate data by moving themobile computing device102 in a particular way. In some embodiments, the user interface component executes to present offers for adjusting a particular network data transfer configuration, such as described with reference toFIG. 3.
• Thecommunications interface component126 may execute independently of the other computer-executable components (e.g., not sequentially, or without interaction or dependency on another component). For example, thecommunications interface component126 may be executed by a thread separate from other thread(s) executing thememory component128, theprediction component122, and thefilter component124.
• The defined network data transfer configuration represents a network transfer decision made by the computing device or other entity (e.g., the web service108). In some embodiments, such network transfer decisions by a plurality of the computing devices may be crowdsourced to, for example, theweb service108 or a particular one of the computing devices. In this manner, the crowdsourced network data transfer decisions may be analyzed to identify patterns therein.
• In a crowdsourcing embodiment, theweb service108 observes and crowdsources the network transfer decisions and/or behavior/patterns of theusers104. For example, theweb service108 crowdsources data aboutusers104, such as the network transfers decisions made by the devices of theusers104, to then automate future network transfer decisions by the devices. For example, theweb service108 may conclude, across a plurality ofusers104, that theusers104 tend to preferparticular network connections130 ormobile operators111 in particular situations. Alternatively or in addition, theweb service108 analyzes the crowdsourced data to determine which decisions worked best for the users104 (e.g., was the call completed or disconnected, and in which areas), and/or which data usage plans116 were frequently selected by theuser104. The analysis may include a neural network or a Bayesian analysis to base future routing decisions on past input, decisions, or other patterns or behavior of theuser104. In some embodiments, theweb service108 prioritizesparticular networks109 andmobile operators111 in each of the situations (e.g., areas) observed by theweb service108. Theweb service108 then applies these conclusions and analysis to future routing decisions for any of theusers104. For example, theweb service108 distributes the information to the user computing devices for application.
• Referring next toFIG. 3, an exemplary flow chart illustrates operation of the computing device to present offers to theuser104 for adjusting a network data transfer. While the operations illustrated inFIG. 3 are performed by themobile computing device102 in some embodiments, one or more of the operations may be performed by other devices, including any computing device local to, or remote from, theuser104. For example, the operations may be performed by theweb service108, or by a proxy device in communication with theweb service108 and themobile computing device102. Further, in some embodiments, the operations illustrated inFIG. 3 are performed by an operating system executing on themobile computing device102.
• In general, the computing device surfaces offers from themobile operators111 that may be of interest to theuser104, at a time when theuser104 may opt for the offer. The service may make recommendations to accept the offer based on cost, QoS, user preferences, application preferences, timeliness, and/or relevancy of the data (e.g., stock quotes), etc.
• At302, the computing device accesses a plurality of the data usage plans116 available to the computing device (e.g., stored in the memory area112). On determining that at least one of the data transfer requests115 from at least one of the data usage plans116 has been received at304, the computing device selects an offer based on the received data usage request at306 and based on thedata usage plan116 selected to implement thedata transfer request115. The selected offer is thus relevant to thedata transfer request115. For example, if thedata transfer request115 is to stream a movie, the computing device may select an offer that includes a temporary but instant increase in a data transfer rate to enable streaming of a high-definition version of the movie, in return for a one-time fee from theuser104.
• The offer is selected from a plurality of offers provided by themobile operators111. The plurality of offers may be stored in thememory area112, or in another memory accessible to the computing device (e.g., in the cloud service). In general, the offers adjust the selecteddata usage plan116 for performance of thedata transfer request115.
• The computing device may perform an analysis on each of the offers available for the selecteddata usage plan116. For example, a cost-benefit analysis may be performed to estimate the transfer costs and/or QoS characteristics associated with performance of thedata transfer request115 after a simulated application of each of the offers. In this manner, the computing device is able to determine whether to recommend acceptance or rejection by theuser104 to the offer.
• At308, the selected offer is presented to theuser104 for review and authorization. For example, the computing device may display a popup, tile, or toast to theuser104. In some embodiments, tiles represent tile user interface elements. On receiving acceptance of the offer from theuser104 at310, the computing device applies the approved offer to thedata usage plan116 selected for performance of thedata transfer request115 at312. At314, the computing device performs thedata transfer request115 using the selecteddata usage plan116 with the offer applied thereto. If theuser104 declines the offer at310, the computing device performs thedata transfer request115 at313 using the selecteddata usage plan116 without the offer being applied thereto.
• In some embodiments, the computing device presents “turbo” offers to theuser104 to instantly increase the data transfer rate of thecurrent network connection130. The offer may, for example, boost the speed of thenetwork connection130 for some cost (e.g., a dollar, quarter, etc.) for some duration (e.g., a couple of hours, an afternoon, a day).
• Referring next toFIG. 4, an exemplary flow chart illustrates operation of the computing device to adjust a network data transfer configuration during performance of one of the data transfer requests115. While the operations illustrated inFIG. 4 are performed by amobile computing device102 in some embodiments, one or more of the operations may be performed by other devices, including any computing device local to, or remote from, theuser104. For example, the operations may be performed by theweb service108, or by a proxy device in communication with theweb service108 and themobile computing device102. Further, in some embodiments, the operations illustrated inFIG. 4 are performed by an operating system executing on themobile computing device102.
• On determining that at least one of the data transfer requests115 has been received from at least one of theapplications114 at402, the computing device defines the network data transfer configuration. For example, the computing device de-queues at least one of the queued data transfer requests115 and selects one of the data usage plans116 (e.g., associated with one of the mobile operators111) and one of thenetwork connections130 at404. At406, the computing device initiates or performs thedata transfer request115 using the defined network data transfer configuration.
• During performance of thedata transfer request115, the computing device determines if another network data transfer configuration is more suitable for completing the in-progressdata transfer request115. For example, if anotherdata usage plan116 becomes available, if the computing device detects a Wi-Fi access point, or if the current time moves from a peak period to an off-peak period, the computing device may conclude that thedata transfer request115 should be completed under another one of the plurality of data usage plans116 available to the computing device. Continuing the above example, the computing device may select one of the data usage plans116 that offers a lower transfer cost, free Wi-Fi, or free off-peak transfers, respectively.
• On determining that a different network data transfer configuration should be selected to reduce transfer costs or improve QoS at408, the computing device changes from the current network transfer configuration to the newly-selected network data transfer configuration during performance of thedata transfer request115. That is, the computing device continues performance of thedata transfer request115 at410 using the newly-selected network data transfer configuration.
• The operations illustrated inFIG. 4 execute to, for example, perform in-call switching to reduce costs and/or improve QoS. In such an example, the computing device performs an in-call switchover or handoff by selecting a second data usage plan after initiation of thedata transfer request115 on a first data usage plan. The switchover may occur after the computing device determines that an estimated transfer cost of the second data usage plan is less than an estimated transfer cost of the first data usage plan. For example, the computing device may switch a call from a cellular network connection to a Voice Over Internet Protocol (VoIP) call over a Wi-Fi connection.
• In another example, theuser104 may receive a voice call over a cellular network connection. The computing device determines that the call is international, and switches the call to one of the data usage plans116,network connection130, andmobile operator111 that is less expensive for international calls.
• Aspects of the disclosure are operable with the computing device or other connection management service performing operations to transparently (to the user104) change data usage plans116 during performance of thedata transfer request115. In event-driven models, the connection management service notifies theapplication114 associated with the in-progressdata transfer request115 that theapplication114 should reconnect using anotherdata usage plan116. In still other embodiments, the connection management service relies on a published protocol recognizable by both endpoints to implement the switchover.
ADDITIONAL EXAMPLES
• In one example, Mobile Operator A may offer a free month of Internet while Mobile Operator B may not. Aspects of the disclosure route data traffic via Mobile Operator A during that free month, but then automatically switch to Mobile Operator B at the end of the first month to avoid incurring charges from Mobile Operator A, which is more expensive than Mobile Operator B. To switch to Mobile Operator B, themobile computing device102 orweb service108 handling the data transfer requests115 identifies anotherSIM113 available on the device, dynamically switches to Mobile Operator B, and applies the data usage plan116 (e.g., tariffs) associated with Mobile Operator B.
• In another example, theuser104 lands in a foreign country and the user's mobile telephone connects to a service (e.g., the web service108) that determines that data transfer may be expensive in that country based on the currentdata usage plan116 of theuser104. Theweb service108 tells the mobile phone of an embedded SIM enablement that may offer cheaper, faster, or otherwise better network transfers. The embedded SIM enablement is software capable of being installed on the mobile telephone upon arrival in the foreign country, and upon consent from theuser104, that enables the mobile telephone to connect to networks of localmobile operators111.
• Alternatively or in addition, the mobile telephone may present and/or recommend a particular offer or package from one of the availablemobile operators111 that the service concludes is the most cost effective or otherwise “better” based on the user's historical data use, anticipated data use, or both. The service considers anticipated multimedia messaging service (MMS), short message service (SMS), and other traffic when determining whichdata usage plan116 and/ormobile operator111 to recommend to theuser104 in that foreign country.
• In some embodiments, an event scheduler and a core networking component implement aspects of the disclosure. The event scheduler executes on the computing device to assign the data transfer requests115 to the data usage plans116. In such an environment, one or more of theapplications114 registers with the event scheduler. The core networking component executes on thecomputing device102 to detect thenetwork connections130 available to thecomputing device102, analyze each of thenetwork connections130 continuously (e.g., without interruption) or continually (e.g., periodically), such as every minute. In other embodiments, the core networking component analyzes each of thenetwork connections130 upon receiving thedata transfer request115 from one of theapplications114. The core networking component may also have different schedules for checkingdifferent network connections130. For example, the core networking component may check the availability of a Wi-Fi connection less frequently than the availability of a roaming cellular connection. The core networking component notifies the event scheduler of the presence and/or absence of thenetwork connections130. Upon receipt of this notification, the event scheduler maps or matches the queued data transfer requests115 to one of the data usage plans116 that use theavailable network connections130.
• In one scenario, an enterprise information technology entity pushes down policies governing enterprise preferences relating to connectivity. For example, the entity transmits the policies to each of the devices associated with the enterprise. The policies may be based on enterprise agreements with particular carriers. Aspects of the disclosure then operate to prefer those particular carriers when selecting carriers for initiation of the data transfer requests, in accordance with the policies. The policies may also interrelate to other policies that define constraints or preferences, such as those associated with security. For example, a government contractor may be required to route secure network traffic over one particular carrier.
• At least a portion of the functionality of the various elements inFIG. 1 may be performed by other elements inFIG. 1, or an entity (e.g., processor, web service, server, application program, computing device, etc.) not shown inFIG. 1.
• In some embodiments, the operations illustrated in the flowcharts may be implemented as software instructions encoded on a computer readable medium, in hardware programmed or designed to perform the operations, or both. For example, aspects of the disclosure may be implemented as a system on a chip or other circuitry including a plurality of interconnected, electrically conductive elements.
• Embodiments have been described with reference to data monitored and/or collected fromusers104. In some embodiments, notice may be provided to theusers104 of the collection of the data (e.g., via a dialog box or preference setting) andusers104 are given the opportunity to give or deny consent for the monitoring and/or collection. The consent may take the form of opt-in consent or opt-out consent.
• Input from theuser104 may be explicit (e.g., user-specified preferences or consent) or implicit (e.g., the computing device makes intelligent decisions for the user104). In some embodiments, the computing device obtains the user's consent to operate. The user preferences indicate, for example, whether theuser104 prefers onenetwork109 over another, onemobile operator111 over another, quality over cost, speed over duration, etc.
• After obtaining the user's consent to execute and to obtain the data usage plans116 of theuser104, the service in some embodiments pulls all the necessary information (e.g., data usage plans116, deals, offers, etc.) from third parties such as themobile operators111, a cloud service, or other entity, without involving theuser104 to ensure a seamless user experience. In such embodiments, the service may further switch among data usage plans116 andmobile operators111 to best meet the specified or default preferences of theuser104.
• The computing device may present the routing decisions to theuser104 for approval or selection before implementing the routing decisions. In some embodiments, theuser104 may not yet have any of the data usage plans116, or may be open to other data usage plans116. In such embodiments, the computing device may present data usage plan offers from the availablemobile operators111 to theuser104 for selection.
Exemplary Operating Environment
• Aspects of the disclosure are capable of operation and/or display on any computing device or screen. For example, theuser104 may move between a mobile device, a gaming console, an in-vehicle computing system (e.g., entertainment and/or navigation), a portable media player, and a laptop.
• Exemplary computer readable media include flash memory drives, digital versatile discs (DVDs), compact discs (CDs), floppy disks, and tape cassettes. By way of example and not limitation, computer readable media comprise computer storage media and communication media. Computer storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media are tangible and are mutually exclusive to communication media. In some embodiments, computer storage media are implemented in hardware. Exemplary computer storage media include hard disks, flash drives, and other solid-state memory. In contrast, communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information delivery media.
• Although described in connection with an exemplary computing system environment, embodiments of the disclosure are capable of implementation with numerous other general purpose or special purpose computing system environments, configurations, or devices.
• Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with aspects of the invention include, but are not limited to, mobile computing devices, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, gaming consoles, microprocessor-based systems, set top boxes, programmable consumer electronics, mobile telephones, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. Such systems or devices may accept input from theuser104 in any way, including from input devices such as a keyboard or pointing device, via gesture input, and/or via voice input.
• Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. The computer-executable instructions may be organized into one or more computer-executable components or modules. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the invention may be implemented with any number and organization of such components or modules. For example, aspects of the invention are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Other embodiments of the invention may include different computer-executable instructions or components having more or less functionality than illustrated and described herein.
• Aspects of the invention transform a general-purpose computer into a special-purpose computing device when configured to execute the instructions described herein.
• The term “roaming” as used herein refers, in some embodiments, to connectivity provided outside a subscriber's home zone that may be subject to additional tariffs, fees, or constraints. Roaming service may or may not be provided by the samemobile operator111. The term “tethered” as used herein refers, in some embodiments, to situations where one device acts as an access point for another device for network access. A tethered connection may occur over a wired connection or a wireless connection. The term “Wi-Fi” as used herein refers, in some embodiments, to a wireless local area network using high frequency radio signals for the transmission of data. The term “BLUETOOTH” as used herein refers, in some embodiments, to a wireless technology standard for exchanging data over short distances using short wavelength radio transmission. The term “cellular” as used herein refers, in some embodiments, to a wireless communication system using short-range radio stations that, when joined together, enable the transmission of data over a wide geographic area. The term “NFC” as used herein refers, in some embodiments, to a short-range high frequency wireless communication technology for the exchange of data over short distances.
• The embodiments illustrated and described herein as well as embodiments not specifically described herein but within the scope of aspects of the invention constitute exemplary means for selecting among the plurality of data usage plans116 available to themobile computing device102 for performing network data transfers.
• The order of execution or performance of the operations in embodiments of the invention illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and embodiments of the invention may include additional or fewer operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the invention.
• When introducing elements of aspects of the invention or the embodiments thereof, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. The term “exemplary” is intended to mean “an example of” The phrase “one or more of the following: A, B, and C” means “at least one of A and/or at least one of B and/or at least one of C.”
• Having described aspects of the invention in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the invention as defined in the appended claims. As various changes could be made in the above constructions, products, and methods without departing from the scope of aspects of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.

Claims (20)

What is claimed is:

1. A system for managing data transfers with a plurality of data usage plans, said system comprising:

a memory area associated with a mobile computing device, said memory area storing a plurality of data usage plans available to the mobile computing device, each of the plurality of data usage plans having data usage statistics associated therewith representing an amount of network data consumed under the data usage plan; and

a processor programmed to:

receive a data transfer request from at least one of a plurality of applications executing on the mobile computing device; and

select, based at least on the plurality of data usage plans, the associated data usage statistics, and the received data transfer request, a mobile operator and at least one network connection available to the mobile computing device to initiate the received data transfer request.

2. The system ofclaim 1, wherein the processor is programmed to select the mobile operator by selecting mobile operator credentials to present to the selected network for the received data transfer request.

3. The system ofclaim 1, wherein the mobile computing device has dual subscriber identity modules (SIMs) with one of the SIMs in standby mode, and wherein the processor is programmed to select at least one of the SIMs to initiate the received data transfer request.

4. The system ofclaim 1, wherein the mobile computing device has dual subscriber identity modules (SIMs) with both of the SIMs being independently active, and wherein the processor is programmed to select at least one of the SIMs to initiate the received data transfer request.

5. The system ofclaim 1, wherein the received data transfer request represents an incoming voice call on a first data usage plan of a first subscriber identity module (SIM), and wherein the processor is programmed to answer the incoming voice call on a second data usage plan of a second SIM.

6. The system ofclaim 1, wherein the mobile computing device has a plurality of radios with at least two of the plurality of radios consuming a battery at differing rates, and wherein the processor is programmed to select the mobile operator and the network connection to balance network data usage against battery usage.

7. The system ofclaim 1, further comprising means for selecting among the plurality of data usage plans available to the mobile computing device for performing network data transfers.

8. A method comprising:

accessing a plurality of data usage plans available to a computing device, each of the plurality of data usage plans having data usage statistics associated therewith representing an amount of network data consumed under the data usage plan;

receiving a data transfer request from at least one of a plurality of applications executing on the computing device; and

selecting, based at least on the accessed plurality of data usage plans, the associated data usage statistics, and the received data transfer request, at least one of the accessed plurality of data usage plans and at least one network connection available to the computing device to initiate the received data transfer request.

9. The method ofclaim 8, further comprising presenting, to a user of the computing device based on the received data transfer request, at least one offer from a mobile operator to adjust the selected data usage plan for performance of the received data transfer request.

10. The method ofclaim 9, further comprising performing a cost-benefit analysis of the presented offer, and determining whether to recommend to the user that the user accept the presented offer based the performed cost-benefit analysis.

11. The method ofclaim 9, wherein presenting the offer includes presenting an offer to instantly increase a data transfer rate for the received data transfer request.

12. The method ofclaim 8, wherein selecting the data usage plan and the network connection represents a network transfer decision for the computing device, and further comprising crowdsourcing the network transfer decisions of a plurality of computing devices to identify patterns in the network transfer decisions.

13. The method ofclaim 8, wherein the plurality of data usage plans includes a first data usage plan with additional network data consumption available and a second data usage plan without additional network data consumption available, and wherein selecting the data usage plan comprises selecting the first data usage plan to prevent overage charges.

14. The method ofclaim 13, wherein the first data usage plan is associated with a family data usage plan.

15. The method ofclaim 8, wherein the selected data usage plan represents a first data usage plan, and further comprising performing an in-call switch over by selecting a second data usage plan after initiation of the received data transfer request on the first data usage plan on determining that an estimated transfer cost of the second data usage plan is less than an estimated transfer cost of the first data usage plan.

16. One or more computer storage media embodying computer-executable components, said components comprising:

a memory component that when executed causes at least one processor to store a plurality of data usage plans available to a computing device, each of the plurality of data usage plans having data usage statistics associated therewith representing an amount of network data consumed under the data usage plan;

a communications interface component that when executed causes at least one processor to receive a data transfer request from at least one of a plurality of applications executing on the computing device;

a prediction component that when executed causes at least one processor to calculate an estimated transfer cost for the data transfer request received by the communications interface component using each of the data usage plans stored by the memory component; and

a filter component that when executed causes at least one processor to select, based at least on the estimated transfer cost calculated by the prediction component, one of the data usage plans stored by the memory component and one of a plurality of network connections available to the computing device to initiate the data transfer request received by the communications interface component.

17. The computer storage media ofclaim 16, wherein the prediction component further estimates a quality of service (QoS) associated with each of the plurality of data usage plans, and wherein the filter component further selects the one of the data usage plans and the one of a plurality of network connections based on the QoS estimated by the prediction component.

18. The computer storage media ofclaim 17, wherein the filter component performs a cost-benefit analysis for each of the data usage plans based on the estimated transfer cost and/or the estimated QoS.

19. The computer storage media ofclaim 18, wherein the filter component selects the data usage plan and the network connection with the lowest estimated transfer cost and/or highest estimated QoS.

20. The computer storage media ofclaim 16, wherein the filter component further selects one of a plurality of mobile operators based at least on the estimated transfer cost calculated by the prediction component.

Images