Techniques for contextual mobile data access

Techniques for contextual mobile data access are described. In one embodiment, an apparatus may comprise a mobile device with a local gateway utility. The local gateway utility may be operative to receive a network request on a device, determine that the network request corresponds to a context-specific data plan for the device, the context-specific data plan authorizing performance of the network request through a zero-rated proxy server, and perform the network request for the application using the zero-rated proxy server as an intermediary. Other embodiments are described and claimed.

BACKGROUND

Users may perform network data access using mobile devices connected to cellular data networks. The cellular data networks may use metered data. The amount of data transferred across a cellular data network may be monitored and debited against a user allocation of data. Similarly, the amount of data transferred across a cellular data network may be monitored and the user billed a fee based on the amount. However, some cellular data access may be performed against zero-rated servers, wherein the cellular system does not meter access to the zero-rated servers: the user allocation is not debited and no amount-based fee is generated for the traffic exchanged with the zero-rated servers.

SUMMARY

Various embodiments are generally directed to techniques for contextual mobile data access. Some embodiments are particularly directed to techniques to application-specific and resource-specific data plans for contextual mobile data access. In one embodiment, for example, an apparatus may comprise a mobile device with a local gateway utility. The local gateway utility may be operative to receive a network request on a device, determine that the network request corresponds to a context-specific data plan for the device, the context-specific data plan authorizing performance of the network request through a zero-rated proxy server, and perform the network request for the application using the zero-rated proxy server as an intermediary. Other embodiments are described and claimed.

DETAILED DESCRIPTION

Various embodiments are directed to techniques to offer and implement context-specific data plans for mobile devices on cellular networks. Mobile devices may execute a wide array of mobile applications. Many of these mobile applications may make use of network data in their performance of their operations. Unfortunately, unlike the assigned number of minutes a user may have on a cellular voice plan, users may not have significant awareness of or control over the data access performed by mobile applications. For example, a user may find that a free or low-cost video streaming application is expensive to use due to significant data access, either absorbing much or all of a user's cellular data allocation or alternatively or additionally generating data usage fees. Where a user purchases blocks of cellular data (e.g., purchases a 50 megabyte of cellular data allocation), the user may find themselves frequently purchasing additional blocks in order to allow for a data-intensive application to work. Further, where a data-intensive application has used up a user's allocation, other applications with more modest data usage may be prevented from operating until the user purchases an additional data allocation.

As such, a user may be benefited by being empowered to purchase application-specific or resource-specific data plans that provide unlimited data access for a set period of time. For instance, a user might purchase a data plan that provides unlimited cellular data access to a multiplayer gaming application for thirty days. A user might purchase a data plan that provides unlimited streaming of video for a soccer tournament for the duration of the tournament. A user might purchase a data plan that provides a trial thirty minute unlimited data plan for a Voice over Internet Protocol (VoIP) application during an introductory period with the VoIP application. These plans may work in combination with a conventional data allocation, such that cellular data usage that doesn't correspond to an application or resource with a specific data plan is debited against the data allocation, while cellular data usage that corresponds to an application or resource with a specific data plan is not debited against the data allocation and may proceed even where a data allocation for a mobile device has been expended. It will be appreciated that a plan promoted as unlimited may have a set limit, the limit set above any normal usage under the plan. For example, a video streaming data plan may provide for significant video streaming, but not accommodate 24/7 video streaming.

These data plans may be priced according to a predicted amount of cellular data that will be used if users are allowed unlimited cellular data usage in the context to which the data plans are specific. For example, a data plan for a video streaming application may be priced higher than a data plan for a text-based messaging application for the same length of time due to the greater amount of network traffic expected to be produced by the video streaming application. This may serve to ensure that cellular providers are appropriately compensated for the use of their network while providing transparency and advance notification to users of the cost of using various applications and accessing various resources using a cellular network. Cellular providers may further benefit from increased use of their cellular network, with associated increased revenue, due to increased confidence in their customers in using their network due to the greater knowledge and control the customers have over their data usage.

FIG. 1illustrates a block diagram for a selective zero-rating system100. In one embodiment, the selective zero-rating system100may comprise a computer-implemented system having software applications comprising one or more components. Although the selective zero-rating system100shown inFIG. 1has a limited number of elements in a certain topology, it may be appreciated that the selective zero-rating system100may include more or less elements in alternate topologies as desired for a given implementation.

It is worthy to note that “a” and “b” and “c” and similar designators as used herein are intended to be variables representing any positive integer. Thus, for example, if an implementation sets a value for a=5, then a complete set of components122illustrated as components122-1through122-amay include components122-1,122-2,122-3,122-4and122-5. The embodiments are not limited in this context.

A mobile device120may perform various operation using network data accessed over a network. The mobile device120may access a cellular system130using cellular signals135. The cellular system130may be a cellular network including data access, the cellular system130provided by a cellular provider with which the user of the mobile device120has a service contract, the service contract for cellular data server to the mobile device120. The cellular system130may be a metered network, in which data access is priced, at least in part, according to an amount of data transferred over the network. The cellular data service contract may be a pre-paid contract in that a cellular data allocation is purchased prior to use providing a specific allocation, with general cellular data access (e.g., cellular data access to a non-zero-rated address) cut off once the cellular data allocation is exhausted. The cellular data service contract may be a subscription contract providing longer-term cellular data access. A subscription contract may include a cellular data allocation, but may also allow for cellular data use beyond the exhaustion of the cellular data allocation, with any further use generating additional fees. For example, a cellular data subscription may include 1 GB of cellular data per month, with access to zero-rated resources not debited against the allocation, with an additional charge for each full or partial additional gigabyte of cellular data used each month.

The mobile device120may access one or more Wi-Fi access points140using Wi-Fi signals145. Wi-Fi access points140may be provided by a plurality of different operators. Some of the Wi-Fi access points140may be personal in nature, such as a home Wi-Fi network operated by the user of mobile device120based on a domestic Internet connection. Some of the Wi-Fi access points140may be free of charge or provided as a complimentary portion of a service, such as free Wi-Fi service in coffee shops, hotels, and other public accommodations. Some of the Wi-Fi access points140may require payment for use. However, the Wi-Fi access points140may be generally non-metered networks, in which, whether or not access is free or paid, there are no fees for use of the Wi-Fi access points140generated based on an amount of data transferred over the networks.

The mobile device120may access a network resource180hosted on a network server170. The network resource180may comprise any network-accessible resource. The network resource180may be retrieved by the mobile device120, such as in the reception of a video download, video stream, music download, web page view, or any other reception of data across a network. The network resource180may be stored on the network server170, such as the uploading of an image, video, audio file, text message, or any other transmission of data across a network. Accessing the network resource180may include both transmitting and receiving data, such as the transmission of a request and the reception of a response, the submission of data and the reception of responding data, or any other two-way exchange of data across a network. The mobile device120may, in various circumstances, use either of a cellular system130or Wi-Fi access points140to access the network resource180on the network server170.

The mobile device120may communicate with network server170without the use of any intermediary proxy server. The mobile device120may use either of cellular system130or Wi-Fi access points140to access the network server170without the network transaction being passed through a proxy server. In some embodiments, one or both of the cellular system130and Wi-Fi access points may use a proxy server internal to their operations, in which case direct access to the network server170may be interpreted as access without the use of third-party proxy servers external to the Wi-Fi access points140or cellular system130.

Some cellular access may be “zero rated.” Zero-rated cellular access may not contribute to capped free cellular data communication that may be included in a cellular customer's plan or pre-paid purchase. Zero-rated cellular access may not generate a fee to the cellular customer, even if that customer is over a limited quantity of allocated or pre-paid cellular data access, or where such an allocated or pre-paid cellular data access does not exist. Zero-rated cellular access may be dependent on the specific network accessed, with the cellular carrier having a list of one or more network addresses—such as internet protocol (IP) addresses—to which cellular customers have zero-rated access. This list may vary between cellular carriers.

The network server170may not be zero-rated with the cellular system130. As such, any direct access to the network server170, including network resource180, that uses cellular system130may result in data allocation usage. The mobile device120may therefore be benefited by, where possible, using a zero-rated proxy server150to access the network server170and other non-zero-rated devices. Data access by the mobile device120through the cellular system130to the zero-rated proxy server150will not result in data allocation usage due to the zero-rated proxy server150. The zero-rated proxy server150may be operative to access the network server170and thereby network resource180on behalf of the mobile device120. As the zero-rated proxy server150is outside of the cellular system130, the cellular provider does not bill or debit the operator of the zero-rated proxy server150for the data exchange with the network server170. Because the zero-rated proxy server150is zero-rated with the cellular system130, the cellular provider does not bill or debit the user of mobile device120for the data exchange with the zero-rated proxy server150. If the network exchange with the zero-rated proxy server150allows proxy access to the network server170, then the use of the zero-rated proxy server150may allow for zero-rated access to the network server170—and thereby to the network resource180—by the mobile device120even without the network server170being zero-rated by the cellular system130.

However, the cellular system130may only zero-rate the zero-rated proxy server150if the zero-rated proxy server150agrees to only act as a proxy for network transactions for which the mobile device120has one or more context-specific data plans relevant to the context of the network transactions. The zero-rated proxy server150may therefore serve as the mechanism for implementing context-specific data plans: cellular data traffic provided for under one or more context-specific data plans for the mobile device120may be tunneled through the zero-rated proxy server150to avoid data fees or data allocation debiting while cellular data traffic not provided for under any context-specific data plan for the mobile device120is excluded from using the zero-rated proxy server150.

In some embodiments, the mobile device120may be used with a proxy server whether or not it is on a metered network. A proxy server may provide utility to the mobile device120beyond the benefit of avoiding data fees and data allocation debiting. For example, a proxy server may transcode media to reduce bandwidth, perform caching to increase performance, and provide other benefits. As such, the mobile device120may use a non-zero-rated proxy server160when using a non-metered network such as the networks provided by Wi-Fi access points140. Similarly, the non-zero-rated proxy server160may be used when using a metered network such as the cellular system130for network transactions for which the mobile device120is not authorized to receive the benefit of zero rating (i.e., where no context-specific data plan is relevant to the transaction). These same benefits beyond zero-rating may also be provided by the zero-rated proxy server150when in use for a transaction.

FIG. 2illustrates an embodiment of a mobile device120for use with the selective zero-rating system. The mobile device120may be operative to execute a plurality of applications260, a service management application250, and a local gateway utility210.

Exchanging network traffic, such as performing zero-rated network request165, may comprise transmitting and receiving network traffic via a network interface controller (NIC). A NIC comprises a hardware component connecting a computer device, such as mobile device120, to a computer network. The NIC may be associated with a software network interface empowering software applications to access and use the NIC. Network traffic may be received over the computer network as signals transmitted over data links. The network traffic may be received by capturing these signals and interpreting them. The NIC may receive network traffic over the computer network and transfer the network traffic to memory storage accessible to software applications using a network interface application programming interface (API). The mobile device120may comprise a cellular interface230for access to the cellular system130and a Wi-Fi interface240for access to Wi-Fi access points140.

A local gateway utility210may be present on a mobile device120to empower the mobile device120to make use of the proxy servers and manage the operation of the mobile device120and its applications260with the proxy servers. Network traffic of the mobile device120that is exchanged via the proxy servers may be transmitted through the local gateway utility210. Exchanging network traffic via the local gateway utility210may comprise using a network interface application programming interface (API) generally providing access to networks accessible to the mobile device120. For instance, the client operating system (OS) of the mobile device120may automatically select a network interface from a plurality of network interfaces according to a priority of the network interfaces.

The local gateway utility210may be the highest-priority network interface of the plurality of network interfaces. The local gateway utility210may be of a higher priority than a cellular interface230, but be of lower priority other network interfaces (e.g., a Wi-Fi interface240) access to which is not managed by the local gateway utility210. Alternatively, the local gateway utility210may also be of a higher priority than the Wi-Fi interface240as well, such that all network traffic is channeled through the local gateway utility210. The local gateway utility210may be operative to manage access to selective zero-rating and to ensure that zero-rating via tunneling to non-zero-rated servers through a zero-rated proxy server170is only performed where provided for by a context-specific data plan active for the mobile device120

In some embodiments, applications260using local gateway utility210may first be registered with the client OS or local gateway utility210before the local gateway utility210is a prioritized network interface for the applications260. A user of mobile device120may have to opt-in to a privacy policy associated with local gateway utility210prior to local gateway utility210being used as a network interface for applications260.

Selective zero-rating system100may include an authorization server (or other suitable component(s)) that allows users to opt in to or opt out of having their actions logged by selective zero-rating system100or shared with other systems (e.g., third-party systems), for example, by setting appropriate privacy settings. A privacy setting of a user may determine what information associated with the user may be logged, how information associated with the user may be logged, when information associated with the user may be logged, who may log information associated with the user, whom information associated with the user may be shared with, and for what purposes information associated with the user may be logged or shared. Authorization servers or other authorization components may be used to enforce one or more privacy settings of the users of proxy servers150,160through blocking, data hashing, anonymization, or other suitable techniques as appropriate.

The local gateway utility210may be operative to receive a network request from an application of a plurality of application260on a mobile device120, determine that the network request corresponds to a context-specific data plan for the mobile device120, the context-specific data plan authorizing performance of the network request through a zero-rated proxy server150, and perform the network request for the application using the zero-rated proxy server150as an intermediary. The local gateway utility210and the application may both be locally executed on the mobile device120.

The local gateway utility210may retrieve a plurality of cached context-specific data plans from a data plan cache220on the mobile device120. The data plan cache220may store active context-specific data plans for the mobile device120locally to the mobile device120for fast access without the use of network resources. In some embodiments, the data plan cache220may also comprise inactive context-specific data plans, the inactive context-specific data plans cached on the device in anticipation of potentially offering the inactive context-specific data plans to the user of the mobile device120. The local gateway utility210may match the application against the plurality of cached context-specific data plans to determine the context-specific data plan authorizing performance of the network request through the zero-rated proxy server150. This identified context-specific data plan may comprise an application-specific data plan authorizing zero-rating of the network request through of use of the zero-rated proxy server150, this authorization associated with a specific period of time. The local gateway utility210may be operative to determine that the identified context-specific data plan is active based on a comparison between the active time period for the context-specific data plan and the current date and time as known to the mobile device120. The application performing the request may be identified by, for example, referencing a socket number for the incoming network request against an OS socket table listing the applications responsible for each socket. The network request may be received from the application on the mobile device120, with the context-specific data plan defining a period of time for which the mobile device120is authorized to perform network requests for the application through the zero-rated proxy server150.

The local gateway utility210may retrieve a plurality of cached context-specific data plans from a data plan cache220on the mobile device120, determine a network address associated with the network request, and match the network address against the plurality of cached context-specific data plans to determine the context-specific data plan authorizing performance of the network request through the zero-rated proxy server150. This identified context-specific data plan may comprise a network-address-specific data plan. This may be used where access to a particular type of network resource180, for example streaming video via a particular video streaming service, is authorized independent of the application originating the request. The network request may be addressed to the network address, with the context-specific data plan defining a period of time for which the mobile device120is authorized to perform network requests addressed to the network address through the zero-rated proxy server150.

In some cases, a context-specific data plan may be specific to a particular network resource180, such as a specific video stream or audio stream. For example, a context-specific data plan may be purchased allowing access to a video stream of a concert event. The network request may therefore correspond to the network resource180, with the context-specific data plan defining a period of time for which the mobile device120is authorized to access the network resource180through the zero-rated proxy server150.

In some embodiments, authorization to use the zero-rated proxy server150may be handled remotely. For example, rather than retrieving the context-specific data plan from the data plan cache220, a check may be made against an authorization server. The authorization server may be a same device as the zero-rated proxy server150or may use a distinct device. The authorization server may be zero-rated to avoid data charges or data usage debiting for determining whether access to the zero-rated proxy server150is authorized. The local gateway utility220may determine an application identifier identifying an application associated with the network request and transmit the application identifier to an authorization server, the authorization server operative to determine that the network request corresponds to the context-specific data plan for the mobile device120, the context-specific data plan authorizing access to the network resource through the zero-rated proxy150. The local gateway utility220may determine a network address associated with the network request and transmit the network address to an authorization server, the authorization server operative to determine that the network request corresponds to the context-specific data plan for the mobile device120, the context-specific data plan authorizing access to the network resource through the zero-rated proxy150.

A service management application250on the mobile device120may be operative to manage the active context-specific data plans for the mobile device120. The service management application250may be operative to allow a user to view their currently-active context-specific data plans, select additional currently-active context-specific data plans, and otherwise perform activities related to context-specific data plans.

FIG. 3illustrates an embodiment of a zero-rated proxy server150and a non-zero-rated proxy server160.

The zero-rated proxy server150may have access to a data plan store320. The data plan store320may store context-specific data plans for the mobile device120and other mobile devices served by the zero-rated proxy server150. The data plan store320may store associations between mobile devices and those context-specific data plans which those mobile devices have active. The data plan store320may store a record for each mobile device120served by the zero-rated proxy server150indicating what context-specific data plans are active and authorizing the mobile device120to use the zero-rated proxy server150. The data plan store320may be stored locally to the zero-rated proxy server150or on a separate device, such as on network-accessible storage. For instance, multiple zero-rated proxy servers may be in operation with all of the zero-rated proxy servers operative to access data plan associations for mobile devices form the data plan store320. The zero-rated proxy server150may comprise a data plan cache for mobile devices currently accessing the zero-rated proxy server150, that frequently use the zero-rated proxy server150, that have recently used the zero-rated proxy server150, or that are assigned to the zero-rated proxy server150.

The zero-rated proxy server150and the non-zero-rated proxy server160may each have access to a user data store330. The user data store330may store data related to the users of mobile devices and to the network activities of mobile devices. For example, the user data store330may store information logged by the proxy servers150,160as to what applications are used by mobile devices and what network resources are accessed by mobile devices. A client analysis component360on each of the proxy servers150,160may be operative to monitor network activity by mobile devices being served by the proxy servers150,160and log information related to those network activities in the user data store330.

The mobile device120may be operative to use the zero-rated proxy server150when on a metered network and using an application for which the mobile device120has an active context-specific data plan authorizing use of the zero-rated proxy server150for the activities of that application. The mobile device120may be operative to use the zero-rated proxy server150when on a metered network and accessing a network server170for which the mobile device120has an active context-specific data plan authorizing use of the zero-rated proxy server150for access to that network server170. The mobile device120may be operative to use the zero-rated proxy server150when on a metered network and accessing a network resource180for which the mobile device120has an active context-specific data plan authorizing use of the zero-rated proxy server150for access to that network resource180. The mobile device120may be operative to use the non-zero-rated proxy server160otherwise.

The mobile device120may be operative to use the non-zero-rated proxy server160when not on a metered network, whether or not an active context-specific data plan would authorize use of the zero-rated proxy server150. Alternatively, the zero-rated proxy server150may be used even when on a non-metered network.

The mobile device120may be operative to use the non-zero-rated proxy server when on either a metered network or non-metered network and using an application for which the mobile device120does not have any active context-specific data plan authorizing use of the zero-rated proxy server150for the activities of that application. The mobile device120may be operative to use the non-zero-rated proxy server when on either a metered network or non-metered network and accessing a network server170for which the mobile device120does not have any active context-specific data plan authorizing use of the zero-rated proxy server150for access to the network server170. The mobile device120may be operative to use the non-zero-rated proxy server when on either a metered network or non-metered network and accessing a network resource180for which the mobile device120does not have any active context-specific data plan authorizing use of the zero-rated proxy server150for access to the network resource180.

The proxy servers150,160may comprise a client proxy component350for the performance of proxy services. The proxy servers150,160may be operative to limit access to proxy services through the use of authentication procedures. A mobile device120may authenticate to the client proxy component350to verify its identity and authorization to use the client proxy component350for the tunneling of network activity. In some embodiments, the Socket Secure (SOCKS) protocol may be used to authenticate mobile devices and perform network communication for proxy services.

The client proxy component350for the zero-rated proxy server150may be further operative to only provide proxy tunneling for network traffic with an associated context-specific data plan active on the mobile device120producing the network traffic. The client proxy component350may be operative to identify a network server170or network resource180as the destination of the network traffic and determine that the data plan store320indicates that a context-specific data plan allowing unmetered access to that network server170or network resource180is active for the mobile device120and to forward the network traffic, and any responses to the network traffic, in response to the determination that the data plan store320indicates that the context-specific data plan is active for the mobile device120. Similarly, the client proxy component350may be operative to identify an application responsible for the network traffic and determine that the data plan store320indicates that a context-specific data plan allowing unmetered use of the application is active for the mobile device120and to forward the network traffic, and any responses to the network traffic, in response to the determination that the data plan store320indicates that the context-specific data plan is active for the mobile device120.

In some cases, live determination of the application responsible for network traffic may be impractical. In these cases, the client analysis component360may be operative to retrospectively determine the responsible application after the network activity of the application is completed. While in some cases the responsible application may be clear from the destination of network activity (e.g., to a network server specific to an application), in other cases the application may only be identified based on patterns within the network activity. If the local gateway utility210of a mobile device120attempts to perform network activity via the zero-rated proxy server150that should not have been allowed, this may be interpreted as indicating inappropriate activity on behalf of the user or a developed of an application for the mobile device120and cause an alert to be sent to an administrator of the zero-rated proxy server150for further investigation.

In some embodiments, the local gateway utility210may be provided with a security token for use in accessing the proxy servers150,160. In some embodiments, each purchased context-specific data plan may result in a security token being stored on the mobile device120, with the security token identifying the context-specific data plan with which it associated. In these embodiments, the client proxy component350may require a context-specific security token for access in order to determine what network activity should be allowed. The local gateway utility210may, in response to determining that a cached context-specific data plan is appropriate for a network request, retrieve the context-specific security token and include it with the performance of the network request via the client proxy component350of the zero-rated proxy server150. Where an application is identified by the context-specific security token, the client analysis component360may be operative to compare network activity to known traffic patterns for the application to determine whether the actual application is being used. Where the comparison indicates that a different application is actually being used, this may be indicated in an alert sent to an administrator of the zero-rated proxy server150to identify which application is being spoofed by another application.

FIG. 4illustrates an embodiment of the mobile device120interacting with a commerce server450. The commerce server450may be used by the mobile device120to purchase additional context-specific data plans and activate those context-specific data plans for the mobile device120.

Context-specific data plans may be promoted to the user of the mobile device120through a plurality of channels. In one case, the user of mobile device120may access a service management application250. The service management application250may present the user with a plurality of context-specific data plans available for purchase. The service management application250may receive a user selection of one or more context-specific data plans and carry out the purchase of the selected context-specific data plans on behalf of the user. The service management application250may be specific to the purchasing of data plans, specific to the purchasing of context-specific data plans, or may empower the purchasing of additional goods and services such as applications and devices. Plans may additionally be communicated via interstitial advertisements, banner advertisements, embedded advertisements, SMS message, voice message, Unstructured Supplementary Service Data (USSD), or any other mechanism for communicating promotions

Purchasing context-specific data plans may be performed via interaction with a commerce server450. In some embodiments, the commerce server450may be operated by the operator of the zero-rated proxy server150. In other embodiments, the commerce server450may be operated by the provider of the cellular system130. In either embodiment, the purchasing of context-specific data plans may be performed via joint interaction with the operator of the zero-rated proxy server150and the operator of the cellular system130. A purchased context-specific data plan may be stored in the data plan store320, with the data plan store320serving as the or one of the canonical, trusted stores for context-specific data plans. The purchased context-specific data plan may also be stored in the data plan cache220for local access to the active context-specific data plans of the mobile device120. Purchasing may be performed via credit transactions, debit transactions against a bank account, debit transactions against a user account with the cellular provider, or according to any other technique for purchasing. In some cases, a user may be offered a promotion loan to purchase a context-specific data plan.

In some cases, the service management application250may promote context-specific data plans to the user of mobile device120in response to predicted interest on the part of the user. A proxy server, such as zero-rated proxy server150or non-zero-rated proxy server160, may monitor network traffic for the mobile device120to generate a network usage history for the mobile device120. The proxy server may predict user interest in the context-specific data plan based on the network usage history. The proxy server may offer, such as via the service management application250, the context-specific data plan for the mobile device120based on the predicted user interest.

Context-specific data plans are associated with a price for a given period of time. Network monitoring by proxy servers may also be used to set the pricing for context-specific data plans. This may be used to set a general price for a context-specific data plan or, alternatively or additionally, to set user-specific prices for context-specific data plans. Previous or existing users of an application may provide an example as to the expected network usage for an application. As such, a price for the context-specific data plan may be determined according to a network usage history of a plurality of installations of the application on a plurality of devices, the network usage history generated at one or more proxy servers used by the plurality of devices. Some users, however, may user greater or lesser amounts of data than the average, which may be determined by monitoring their network activity and comparing it to the general population. As such, a price for the context-specific data plan may be determined according to a predicted network usage of the application on the mobile device120, the predicted network usage generated according to a network usage history of the mobile device120, the network usage history generated at one or more proxy servers used by the mobile device120. In some embodiments, monitoring of a user's or users' network activity may be performed by the local gateway utility210on the mobile device120or mobile devices.

In some cases, context-specific data plans may be promoted when launching an application of the plurality of applications260where the launched application does not have an active context-specific data plan. The local gateway utility210may be operative to determine that an application producing a network request has launched on the mobile device120, determine that the mobile device120does not have any active context-specific data plan authorizing the mobile device120to perform network requests for the application through the zero-rated proxy server150, offer a purchase of the context-specific data plan in response to the determination that the mobile device120does not have any active context-specific data plan authorizing the mobile device120to perform network requests for the application through the zero-rated proxy server150. The offer may be presented according to an interstitial displayed prior to the content of the launched application, as a banner ad at the top of a screen of the mobile device120, or through any other form of presentation. The local gateway utility210may receive an acceptance of the purchase of the context-specific data plan, perform the purchase of the context-specific data plan with the commerce server450, and associate the context-specific data plan with the mobile device120based on the purchase of the context-specific data plan. The association of the context-specific data plan with the mobile device120may include the storage of the association in the data plan store320, in the data plan cache220, and with a provider for the cellular system130. Some of the association may be performed on behalf of the mobile device120by the commerce server450.

Introductory context-specific data plans may be offered for new applications. An introductory context-specific data plan may be distinguished through an atypically short period of time and a requirement that the application be new to the user or to the mobile device120. Introductory context-specific data plans may be limited to new users of an application in order to allow a very low rate for the introductory context-specific data plan while avoiding longtime users of the application from merely repeatedly purchasing the introductory context-specific data plan when they use the application. A user that regularly uses a video streaming service may be expected to purchase a long-term plan for use of the service rather than repeatedly purchasing a very-short-term plan immediately prior to streaming video. A very short term plan may be associated with, for example, an introductory period of time comprising at most thirty minutes. As such, the local gateway utility210may determine that the application has launched for a first time on the mobile device120and offer a context-specific data plan with an introductory period in response to the determination that the application launched for the first time.

Context-specific data plans may be offered when the mobile device120transitions from a non-metered network, such as provided by the Wi-Fi access points140, to a metered network, such as the cellular system130. For example, a user may watch a soccer match on their mobile device120while at a café using a Wi-Fi access point provided by the café. The user may wish to then leave the café and take a bus to their place of employment, their home, their school, etc. However, Wi-Fi may not be available while on the bus. If the user does not already have an active context-specific data plan for the network activity they were performing, they may be benefited by being offered an appropriate context-specific data plan to allow them to continue performing the network activity on the metered cellular network without incurring data charges or data allocation debiting. For example, the user watching the soccer match may be offered one or more of a video streaming data plan, a data plan specific to the soccer match they were watching, or a data plan for the application they were using to watch the soccer match.

As such, where the network request is associated with a network resource180, the local gateway utility210may determine that the mobile device120was previously accessing the network resource180on a non-metered network, determine that continued access to the network resource180would use a metered network, determine that the mobile device120does not have any active context-specific data plan authorizing the mobile device120to access the network resource through the zero-rated proxy server150, and offer a purchase of the context-specific data plan in response to the determination that the mobile device120does not have any active context-specific data plan authorizing the mobile device120to access the network resource through the zero-rated proxy server150. The local gateway utility210may receive an acceptance of the purchase of the context-specific data plan, perform the purchase of the context-specific data plan, and associate the context-specific data plan with the mobile device120based on the purchase of the context-specific data plan. The local gateway utility210may thereafter perform the network request on the metered network via the zero-rated proxy server150, thereby avoiding the metering of the metered network. In some embodiments, the network resource may be identified by a network address, such that the purchased context-specific data plan is specific to that network address. It will be appreciated that a network address may correspond to, for example, a plurality of IP addresses to allow the use of multiple IP addresses that a network service may use. Further, the context-specific data plan may be purchased to further the access of a particular network resource180, but be general to an application being used to access to the network resource180and empowering the user to use the application to access other resources without incurring data fees or data allocation debiting.

In general, monitoring a user's network activity on a non-metered network may suggest context-specific data plans appropriate to the user. For example, the local gateway utility210or non-zero-rated proxy server160may determine one or more context-specific data plans that would authorize the mobile device120to use the zero-rated proxy server150to perform network activities on the metered network that they have already performed on a non-metered network. For example, one or more applications may be identified as producing network traffic on a non-metered network, with the mobile device120promoting one or more context-specific data plans to use the one or more applications via the zero-rated proxy server150when on a metered network. One or more network resources may be identified as producing network traffic when accessed on a non-metered network, with the mobile device120promoting one or more context-specific data plans to access the one or more network resources via the zero-rated proxy server150when on a metered network.

Context-specific data plans may also be promoted based on associated activity, wherein interest in one service corresponds to a potential interest in another service. For example, a user of the mobile device120accessing a score for a soccer match may be taken as an opportunity to promote a data plan allowing access to video stream for that soccer match. Similarly, a user's interest in soccer matches (e.g., checking scores, liking on a social network, discussing via messaging) may be used as an opportunity to offer streaming data plans for upcoming matches. In general, any aspect of a user's behavior may be monitored, used to determine a potential interest in a network resource180, and therefore used to generate a promotion for a context-specific data plan allowing access to the network resource180.

A context-specific data plan may be offered for a bundle of applications. For example, a particular corporation may produce a plurality of applications, all of the applications for integration with their services (e.g., a suite of applications for use with a particular social networking service). A common application-bundle-specific data plan may be offered for the plurality of applications. In general, the operator of the zero-rated proxy server150or cellular system130may determine application bundles and offer application-bundle-specific data plans to users.

In some embodiments, the user history for a user of the mobile device120may be used to suggest additional purchases. For example, a user with a history of calling a certain region or country may be promoted a voice plan for that country or region. Alternatively or additionally, the user may be promoted a data-based VoIP application with an associated application-specific data plan that would provide voice service at a lower cost than a voice plan. Similarly, a user with a history of sending short message service (SMS) messages to a certain region or country may be promoted an SMS plan for that country or region. Alternatively or additionally, the user may be promoted a data-based messaging application with an associated application-specific data plan that would provide messaging service at a lower cost than an SMS plan. Further, voice plans, SMS plans, data-based voice alternatives, and data-based messaging alternatives may be promoted prospectively based on the contacts for a user, such as may be stored on a mobile device120.

Similarly, contacts or other user associations of the user may be used to select context-specific data plans for promotion. A user may have a set of user associations defining other users with which they are associated. This may be determined according to user contacts, user chat history, user call history, user messaging history, explicit associations on a social network, or according to any other technique for associating an individual with other individuals. Users may be promoted context-specific data plans for applications and network resources used by other associated users. Users may be promoted context-specific data plans for applications and network resources that may be used for interacting with other associated users. For example, a user may be promoted a multiplayer game and an application-specific data plan for that multiplayer game in response to a determination that the user's friends play the game, with the game and plan promoted as being derived from the user's friends' activity. A user may be promoted a video streaming package for an event that their friends have already purchased a video streaming package for. In general, any purchasing or network activity by a user's associates may be used to generate context-specific data plan promotions for a user.

FIG. 5illustrates one embodiment of a first logic flow500. The logic flow500may be representative of some or all of the operations executed by one or more embodiments described herein.

In the illustrated embodiment shown inFIG. 5, the logic flow500may receive a network request at a local gateway utility210on a mobile device120at block502.

The logic flow500may determine that the network request corresponds to a context-specific data plan for the mobile device120, the context-specific data plan authorizing performance of the network request through a zero-rated proxy server150at block504.

The logic flow500may perform the network request using the zero-rated proxy server150at block506.

The embodiments are not limited to this example.

FIG. 6illustrates one embodiment of a second logic flow600. The logic flow600may be representative of some or all of the operations executed by one or more embodiments described herein.

In the illustrated embodiment shown inFIG. 6, the logic flow600may receive a network request at a zero-rated proxy server150from a mobile device120at block602.

The logic flow600may determine that the network request corresponds to a context-specific data plan for the mobile device120, the context-specific data plan authorizing performance of the network request through the zero-rated proxy server150at block604.

The logic flow600may perform the network request using the zero-rated proxy server150as an intermediary at block606.

The embodiments are not limited to this example.

FIG. 7illustrates a block diagram of a centralized system700. The centralized system700may implement some or all of the structure and/or operations for the selective zero-rating system100in a single computing entity, such as entirely within a single device720.

The device720may comprise any electronic device capable of receiving, processing, and sending information for the selective zero-rating system100. Examples of an electronic device may include without limitation an ultra-mobile device, a mobile device, a personal digital assistant (PDA), a mobile computing device, a smart phone, a telephone, a digital telephone, a cellular telephone, ebook readers, a handset, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a netbook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, game devices, television, digital television, set top box, wireless access point, base station, subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. The embodiments are not limited in this context.

The device720may execute communications operations or logic for the selective zero-rating system100using communications component740. The communications component740may implement any well-known communications techniques and protocols, such as techniques suitable for use with packet-switched networks (e.g., public networks such as the Internet, private networks such as an enterprise intranet, and so forth), circuit-switched networks (e.g., the public switched telephone network), or a combination of packet-switched networks and circuit-switched networks (with suitable gateways and translators). The communications component740may include various types of standard communication elements, such as one or more communications interfaces, network interfaces, network interface cards (NIC), radios, wireless transmitters/receivers (transceivers), wired and/or wireless communication media, physical connectors, and so forth. By way of example, and not limitation, communication media712,742include wired communications media and wireless communications media. Examples of wired communications media may include a wire, cable, metal leads, printed circuit boards (PCB), backplanes, switch fabrics, semiconductor material, twisted-pair wire, co-axial cable, fiber optics, a propagated signal, and so forth. Examples of wireless communications media may include acoustic, radio-frequency (RF) spectrum, infrared and other wireless media.

The device720may communicate with other devices over a communications media712using communications signals714via the communications component740. The devices may be internal or external to the device720as desired for a given implementation. For example, the device720may communicate with the zero-rated proxy server150and the non-zero-rated proxy server160.

FIG. 8illustrates a block diagram of a distributed system800. The distributed system800may distribute portions of the structure and/or operations for the selective zero-rating system100across multiple computing entities. Examples of distributed system800may include without limitation a client-server architecture, a 3-tier architecture, an N-tier architecture, a tightly-coupled or clustered architecture, a peer-to-peer architecture, a master-slave architecture, a shared database architecture, and other types of distributed systems. The embodiments are not limited in this context.

The distributed system800may comprise server devices810,850. In general, the server devices810,850may be the same or similar to the client device720as described with reference toFIG. 7. For instance, the server devices810,850may each comprise a processing component830and a communications component840which are the same or similar to the processing component730and the communications component740, respectively, as described with reference toFIG. 7. In another example, the server devices810,850may communicate over a communications media812using communications signals814via the communications components840.

The server devices810,850may comprise or employ one or more server programs that operate to perform various methodologies in accordance with the described embodiments. In one embodiment, for example, a plurality of zero-rated server devices810may implement a plurality of zero-rated proxy servers150. The plurality of non-zero-rated server devices850may implement a plurality of non-zero-rated proxy servers160. The server devices810,850may exchange signals814over media812to coordinate the providing of proxy services to mobile devices. The server devices810,850may exchange signals814over media812with the user data store330and data plan store320for the storage, analysis, and retrieval of user data and data plans.

FIG. 9illustrates an embodiment of an exemplary computing architecture900suitable for implementing various embodiments as previously described. In one embodiment, the computing architecture900may comprise or be implemented as part of an electronic device. Examples of an electronic device may include those described with reference toFIG. 8, among others. The embodiments are not limited in this context.

The computer902may include various types of computer-readable storage media in the form of one or more lower speed memory units, including an internal (or external) hard disk drive (HDD)914, a magnetic floppy disk drive (FDD)916to read from or write to a removable magnetic disk918, and an optical disk drive920to read from or write to a removable optical disk922(e.g., a CD-ROM or DVD). The HDD914, FDD916and optical disk drive920can be connected to the system bus908by a HDD interface924, an FDD interface926and an optical drive interface928, respectively. The HDD interface924for external drive implementations can include at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.

The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives and memory units910,912, including an operating system930, one or more application programs932, other program modules934, and program data936. In one embodiment, the one or more application programs932, other program modules934, and program data936can include, for example, the various applications and/or components of the selective zero-rating system100.

A monitor944or other type of display device is also connected to the system bus908via an interface, such as a video adaptor946. The monitor944may be internal or external to the computer902. In addition to the monitor944, a computer typically includes other peripheral output devices, such as speakers, printers, and so forth.

When used in a LAN networking environment, the computer902is connected to the LAN952through a wire and/or wireless communication network interface or adaptor956. The adaptor956can facilitate wire and/or wireless communications to the LAN952, which may also include a wireless access point disposed thereon for communicating with the wireless functionality of the adaptor956.

When used in a WAN networking environment, the computer902can include a modem958, or is connected to a communications server on the WAN954, or has other means for establishing communications over the WAN954, such as by way of the Internet. The modem958, which can be internal or external and a wire and/or wireless device, connects to the system bus908via the input device interface942. In a networked environment, program modules depicted relative to the computer902, or portions thereof, can be stored in the remote memory/storage device950. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

FIG. 10illustrates a block diagram of an exemplary communications architecture1000suitable for implementing various embodiments as previously described. The communications architecture1000includes various common communications elements, such as a transmitter, receiver, transceiver, radio, network interface, baseband processor, antenna, amplifiers, filters, power supplies, and so forth. The embodiments, however, are not limited to implementation by the communications architecture1000.

As shown inFIG. 10, the communications architecture1000comprises includes one or more clients1002and servers1004. The clients1002may implement the device720. The servers1004may implement the server devices810,850. The clients1002and the servers1004are operatively connected to one or more respective client data stores1008and server data stores1010that can be employed to store information local to the respective clients1002and servers1004, such as cookies and/or associated contextual information.

The clients1002and the servers1004may communicate information between each other using a communication framework1006. The communications framework1006may implement any well-known communications techniques and protocols. The communications framework1006may be implemented as a packet-switched network (e.g., public networks such as the Internet, private networks such as an enterprise intranet, and so forth), a circuit-switched network (e.g., the public switched telephone network), or a combination of a packet-switched network and a circuit-switched network (with suitable gateways and translators).

FIG. 11illustrates an embodiment of a device1100for use in a multicarrier OFDM system, such as the selective zero-rating system100. Device1100may implement, for example, software components1160as described with reference to selective zero-rating system100and/or a logic circuit1130. The logic circuit1130may include physical circuits to perform operations described for the selective zero-rating system100. As shown inFIG. 11, device1100may include a radio interface1110, baseband circuitry1120, and computing platform1130, although embodiments are not limited to this configuration. The device1100may correspond to the mobile device120.

The device1100may implement some or all of the structure and/or operations for the selective zero-rating system100and/or logic circuit1130in a single computing entity, such as entirely within a single device. Alternatively, the device1100may distribute portions of the structure and/or operations for the selective zero-rating system100and/or logic circuit1130across multiple computing entities using a distributed system architecture, such as a client-server architecture, a 3-tier architecture, an N-tier architecture, a tightly-coupled or clustered architecture, a peer-to-peer architecture, a master-slave architecture, a shared database architecture, and other types of distributed systems. The embodiments are not limited in this context.

In one embodiment, radio interface1110may include a component or combination of components adapted for transmitting and/or receiving single carrier or multi-carrier modulated signals (e.g., including complementary code keying (CCK) and/or orthogonal frequency division multiplexing (OFDM) symbols) although the embodiments are not limited to any specific over-the-air interface or modulation scheme. Radio interface1110may include, for example, a receiver1112, a transmitter1116and/or a frequency synthesizer1114. Radio interface1110may include bias controls, a crystal oscillator and/or one or more antennas1118. In another embodiment, radio interface1110may use external voltage-controlled oscillators (VCOs), surface acoustic wave filters, intermediate frequency (IF) filters and/or RF filters, as desired. Due to the variety of potential RF interface designs an expansive description thereof is omitted.

Baseband circuitry1120may communicate with radio interface1110to process receive and/or transmit signals and may include, for example, an analog-to-digital converter1122for down converting received signals, a digital-to-analog converter1124for up converting signals for transmission. Further, baseband circuitry1120may include a baseband or physical layer (PHY) processing circuit1156for PHY link layer processing of respective receive/transmit signals. Baseband circuitry1120may include, for example, a processing circuit1128for medium access control (MAC)/data link layer processing. Baseband circuitry1120may include a memory controller1132for communicating with processing circuit1128and/or a computing platform1130, for example, via one or more interfaces1134.

In some embodiments, PHY processing circuit1126may include a frame construction and/or detection module, in combination with additional circuitry such as a buffer memory, to construct and/or deconstruct communication frames, such as radio frames. Alternatively or in addition, MAC processing circuit1128may share processing for certain of these functions or perform these processes independent of PHY processing circuit1126. In some embodiments, MAC and PHY processing may be integrated into a single circuit.

The computing platform1130may provide computing functionality for the device1100. As shown, the computing platform1130may include a processing component1140. In addition to, or alternatively of, the baseband circuitry1120, the device1100may execute processing operations or logic for the selective zero-rating system100and logic circuit1130using the processing component1140. The processing component1140(and/or PHY1126and/or MAC1128) may comprise various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

Device1100may be, for example, an ultra-mobile device, a mobile device, a fixed device, a machine-to-machine (M2M) device, a personal digital assistant (PDA), a mobile computing device, a smart phone, a telephone, a digital telephone, a cellular telephone, user equipment, eBook readers, a handset, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a netbook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, game devices, television, digital television, set top box, wireless access point, base station, node B, evolved node B (eNB), subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. Accordingly, functions and/or specific configurations of device1100described herein, may be included or omitted in various embodiments of device1100, as suitably desired. In some embodiments, device1100may be configured to be compatible with protocols and frequencies associated one or more of the 3GPP LTE Specifications and/or IEEE 1102.16 Standards for WMANs, and/or other broadband wireless networks, cited herein, although the embodiments are not limited in this respect.

Embodiments of device1100may be implemented using single input single output (SISO) architectures. However, certain implementations may include multiple antennas (e.g., antennas1118) for transmission and/or reception using adaptive antenna techniques for beamforming or spatial division multiple access (SDMA) and/or using MIMO communication techniques.

It should be appreciated that the exemplary device1100shown in the block diagram ofFIG. 11may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and/or elements for implementing these functions would be necessarily be divided, omitted, or included in embodiments.