Methods and systems for handling requests regarding zero-rating

Methods and systems for processing requests by a computing device (e.g., a user device) are disclosed. The user device is coupled to a server system (e.g., a proxy server). The user device detects a DNS lookup request including a domain name and generates a first response to the DNS lookup request. The first response includes a synthesized IP address associated at the computing device with the domain name. The user device detects a connection request subsequent to the first response. The connection request includes the synthesized IP address. The user device modifies the connection request. In some embodiments, the user device replaces the synthesized IP address in the connection request with the domain name. The user device further forwards the connection request to a server.

TECHNICAL FIELD

This relates generally to network communications, including but not limited to processing requests by a computing device to identify destination domain names of respective requests to avoid paid data leakage.

BACKGROUND

Mobile devices have become an increasingly dominant means through which consumers access, download, and consume electronic content over the Internet.

Despite substantial advancements in telecommunications technology, however, affordable access to the Internet remains relatively low. Considering the limited affordability of Internet access in certain geographic regions, such as developing countries, consumers often have difficulty accessing the Internet and therefore are often left frustrated when using mobile devices. Recently, zero-rated Internet service has become an increasingly popular option to improve the affordability of Internet access. It is beneficial to serve the zero-rated content efficiently and effectively to the consumers.

SUMMARY

Accordingly, there is a need for methods, devices, and systems for improving network operability, for managing data exchanged between user devices and web servers, and for avoiding data leakage (e.g., a paid data leakage). Embodiments set forth herein are directed to methods, devices, and systems for processing requests by a user device. Zero-rated (e.g., free) access to certain content (e.g., zero-rated content) on the Internet may be provided to users at no cost, while non-zero-rated (e.g., paid) access to other content (e.g., non-zero-rated content) on the Internet may also be offered on other terms. By having a proxy server route traffic exchanged between user devices and web servers, the user devices can access the Internet at predetermined rates or at no cost.

Because a single IP address may correspond to a plurality of domain names that provide content with different pricing policies, it may not be conclusive, by using an IP address solely, to check the pricing policies of the content requested by a user device. For example, “www.google.com” and “www.youtube.com” may be hosted by a same web server, and thus may share the same IP address. However, content provided by Google.com and YouTube.com may not be identically rated. For example, text content from “www.google.com” may be zero-rated, whereas video content from “www.youtube.com” may be non-zero-rated. Accordingly, there is a need to identify the domain name to which each request is directed and to check the domain name against a whitelist of content approved for zero-rating to make sure that only zero-rated content is provided during a zero-rated session.

By using the methods, devices, and systems for processing requests discussed in the present disclosure, a unique synthesized IP address is assigned to each domain name for distinguishing respective domain names from each other, such as “www.google.com” and “www.youtube.com.” The synthesized IP can be used in conjunction with the existing Internet communication protocol (e.g., TCP/IP) to pass the domain name information to the proxy server. The proxy server then can check the domain name to understand which domain the user is requesting content from (instead of only seeing the IP address). Furthermore, all requests from the user device can be guaranteed to be forwarded to the proxy server for checking the requested domain names against a whitelist for zero-rating to avoid paid data leakage.

In accordance with some other embodiments, a computer-implemented method is performed at a computing device (e.g., a user device) with one or more processors and memory storing instructions for execution by the one or more processors. The user device is coupled to a server system (e.g., a proxy server). The method includes detecting a DNS lookup request including a domain name. The method further includes generating a first response to the DNS lookup request. The first response includes a synthesized IP address associated at the computing device with the domain name. The method includes detecting a connection request subsequent to the first response. The connection request includes the synthesized IP address. The user device modifies the connection request. In some embodiments, the user device replaces the synthesized IP address in the connection request with the domain name. The user device further forwards the connection request to a server.

In accordance with some embodiments, a server system (e.g., a proxy server) may include one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for performing the operations of the above method. In accordance with some embodiments, a non-transitory computer-readable storage medium has stored therein instructions that, when executed by the electronic device, cause the electronic device to perform the operations of the above method.

In accordance with some embodiments, a computer-implemented method is performed at a server system (e.g., a proxy server) with one or more processors and memory storing instructions for execution by the one or more processors. The proxy server is coupled to a plurality of client devices and a plurality of web servers. The method includes receiving a request from a client device, wherein the request includes a domain name. The method also includes validating whether the domain name corresponds to a zero-rated web site. In accordance with a determination that the domain name corresponds to a zero-rated web site, the proxy server forwards the request to a web server in accordance with the domain name.

In accordance with some embodiments, a computing device (e.g., a user device) may include one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for performing the operations of the above method. In accordance with some embodiments, a non-transitory computer-readable storage medium has stored therein instructions that, when executed by the electronic device, cause the electronic device to perform the operations of the above method.

DESCRIPTION OF EMBODIMENTS

It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first application could be termed a second application, and, similarly, a second application could be termed a first application, without departing from the scope of the various described embodiments. The first application and the second application are both applications, but they are not the same application.

As used herein, the term “exemplary” is used in the sense of “serving as an example, instance, or illustration” and not in the sense of “representing the best of its kind.”

FIG. 1illustrates a network architecture100in accordance with some embodiments. The network architecture100allows mobile carriers (and/or network providers) to provide one or more subscribers (e.g., users) Internet service with one or more pricing policies, e.g., for free (e.g., zero-rated), at special pricing, or at regular pricing. For example, a mobile carrier assigns respective pricing policies to IP addresses or domain names (e.g., domain addresses, host names, host addresses, URLs) associated with one or more web servers that provide Internet content to subscribers. The creation of the pricing policies also takes into consideration subscriber account types (e.g., pre-paid, zero-balanced, etc.), subscriber phone numbers, subscriber IP addresses, requested content types, applications running on subscriber devices, and/or other device features.

The network architecture100routes the traffic from one or more subscriber devices to destination IP addresses using predetermined pricing policies (e.g., free, special pricing, or regular pricing). The network architecture100thus provides various products and/or functionalities (e.g., a Free Basics user interface for zero-rated content) to the subscribers.

In some embodiments, a subscriber device can access one or more predetermined IP addresses or one or more predetermined domain names in accordance with predetermined pricing policies. For example, for zero-rating service, a subscriber device can download, upload, and/or view a webpage or use an application associated with a predetermined IP address or a predetermined domain name for free, without being charged for network access. Thus these types of predetermined IP addresses or domain names are called zero-rated content providers. The content from zero-rated web pages and/or applications is called zero-rated content.

In another example, for specially priced services, a network operator may provide promotions, such as discounted pricing, for accessing certain IP addresses or certain domain names, and/or certain content types (e.g., texts and/or images) from certain IP addresses or certain domain names. The specially priced services may be provided to certain subscribers as selected by the network operator.

In yet another example, for regularly priced services, a subscriber device can access one or more IP addresses or one or more domain names that are not zero-rated or specially priced by paying regular service fees. In some embodiments, one or more IP addresses or one or more domain names that are neither zero-rated nor specially priced are treated as regularly priced. The IP addresses or domain names that require paid network access are called non-zero-rated content providers, which include regular-priced content providers and special-priced content providers. The content provided by the non-zero-rated content providers is called non-zero-rated content, which includes regular-priced content and special-priced content.

The network architecture100includes client-side modules (e.g., as discussed with reference toFIG. 2) executed on a number of user devices (also called “client devices,” “client systems,” “client computers,” “subscriber devices,” or “clients”)102-1. . .102-i. . .102-m. . .102-nand server-side modules (e.g., as discussed with reference toFIG. 3) executed on one or more server systems, such as a proxy server140and/or one or more web servers150-1,150-2. . .150-p. The user devices102communicate with the server systems (e.g., the proxy server140and/or the one or more web servers150) through one or more networks130(e.g., the Internet, cellular telephone networks, mobile data networks, other wide area networks, local area networks, metropolitan area networks, and so on). Client-side modules provide client-side functionalities for the network service platform (e.g., zero-rated Internet service, special priced Internet service, and regularly priced Internet service) and communications with server-side modules. Server-side modules provide server-side functionalities for the network service platform (e.g., routing network traffic, serving internet content with specific pricing policies, and/or managing user account information) for any number of user devices102.

In some embodiments, the user devices102are mobile devices and/or fixed-location devices. The user devices102are associated with subscribers (not shown) who employ the user devices102to access one or more IP addresses or domain names (e.g., including zero-rated content providers and/or non-zero-rated content providers). The user devices102execute web browser applications and/or other applications that can be used to access the one or more IP addresses or domain names. In some embodiments, a user device102processes requests for network services and forwards the requests from the user device102to the proxy server140. The requests for network services include, but are not limited to, one or more Domain Name System (DNS) requests and one or more Transmission Control Protocol (TCP) requests.

Examples of the user devices102include, but are not limited to, feature phones, smart phones, smart watches, personal digital assistants, portable media players, tablet computers, 2D gaming devices, 3D (e.g., virtual reality) gaming devices, laptop computers, desktop computers, televisions with one or more processors embedded therein or coupled thereto, in-vehicle information systems (e.g., an in-car computer system that provides navigation, entertainment, and/or other information), wearable computing devices, personal digital assistants (PDAs), enhanced general packet radio service (EGPRS) mobile phones, media players, navigation devices, game consoles, smart televisions, remote controls, combinations of any two or more of these data processing devices or other data processing devices, and/or other appropriate computing devices that can be used to communicate with the proxy server140.

In some embodiments, the network architecture100includes one or more base stations120-1. . .120-jfor carrier networks that provide cellular service to the user devices102. One or more network operators (e.g., network service providers, network carriers, or cellular companies) own or control the one or more base stations120and related infrastructure. For example, the base station120communicably connects one or more user devices102(e.g.,102-1) to one another (e.g.,102-i) and/or to the networks130. In some embodiments, the network architecture100includes one or more gateways122-1. . .122-kconnected to one or more wireless access points124-1. . .124-qrespectively for providing Wi-Fi networks to the user devices102(e.g.,102-m,102-n). The base stations120and the gateways122are responsible for routing traffic between the networks130and the user device102.

In some embodiments, the proxy server140is implemented on one or more standalone computers or on a distributed network of computers. In some embodiments, the proxy server140also employs various virtual devices and/or services of third party service providers (e.g., cloud computing) to provide the underlying computing resources and/or infrastructure resources of the proxy server140. The proxy server140includes one or more processors142and one or more databases144. The one or more processors142process requests for respective network services from the user devices102, and route or forward requests to corresponding web servers150to provide the network services with corresponding pricing policies. The database144stores various information, including but not limited to information related to subscribers, information related to network operators, and/or pricing policies.

In some embodiments, the one or more web servers150-1,150-2. . .150-pinclude social networking servers configured to host various social networking functionalities. In some embodiments, the one or more web servers150-1,150-2. . .150-pinclude third-party servers configured to provide other types of services. Exemplary third-party services include social networking, book sales, book reviews sharing, business, communication, contests, education, entertainment, fashion, finance, food and drink, games, health and fitness, lifestyle, local information, movies, television, music and audio, news, photos, video, productivity, reference material, security, shopping, sports, travel, utilities, and the like. In some embodiments, a given web server150hosts a website that provides web pages to user devices102. Alternatively or additionally, a given web server150hosts an application that is used by user devices102. As discussed above, the proxy server140may route or redirect requests from user devices102to respective web servers150. In some embodiments, the proxy server140uses inline frames (“iframes”) to nest independent websites within a web page (e.g., a zero-rated, a regular-priced, or a special-priced web page). In some embodiments, the proxy server140uses iframes to enable third-party developers to create applications that are hosted separately by a web server150(e.g., a third-party server), but operate within a user session and are accessed through the user's profile in the proxy server140. In some embodiments, a given web server150is used to provide third-party content (e.g., news articles, reviews, message feeds, etc.). In some embodiments, a given web server150is a single computing device, while in other embodiments, a given web server150is implemented by multiple computing devices working together to perform the actions of a server system (e.g., cloud computing).

In some embodiments, respective IP addresses or respective domain names associated with one or more web servers150are predetermined to be zero-rated content providers that are configured to provide zero-rated content to the user devices102. A user device102does not need to pay data usage fees to a network provider for viewing, downloading, and/or uploading data to or from the one or more zero-rated content providers. In some embodiments, respective IP addresses or respective domain names associated with one or more web servers150are non-zero-rated content providers (e.g., regular-priced or special-priced) that provide non-zero-rated (e.g., paid) content. A user device102pays a data usage fee to a network provider for viewing, downloading, and/or uploading data to or from the one or more non-zero-rated content providers.

In some embodiments, a single web server150, e.g., web server150-1, is configured to host two or more domain names, e.g., www.google.com and www.youtube.com. In some embodiments, a first domain name (e.g., www.google.com) is configured to provide zero-rated content to one or more user devices102and a second domain name (e.g., www.youtube.com) is configured to provide non-zero-rated content to one or more user devices102. The single web server150is configured to host the functionalities and content of the respective two or more domain names. The single web server150is assigned with a single IP address. Under certain communication protocols (e.g., TCP/IP), IP addresses are used for identifying the destinations of requests (e.g., packets). Thus, there is a need for a process to distinguish requests from user devices102for different domain names that may have the same IP address to avoid inadvertent paid data leak on the user devices102.

FIG. 2is a block diagram illustrating an exemplary user device102(e.g., one of the user devices102-1through102-n,FIG. 1) in accordance with some embodiments. The user device102typically includes one or more central processing units (CPU(s)) (e.g., processors or cores)202, one or more network (or other communications) interfaces210, memory212, and one or more communication buses214for interconnecting these components. The communication buses214optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.

The user device102includes a user interface204, including output device(s)206and input device(s)208. In some embodiments, the input devices include a keyboard or a track pad. Alternatively, or in addition, the user interface204includes a display device that includes a touch-sensitive surface, in which case the display device is a touch-sensitive display. In user devices that have a touch-sensitive display, a physical keyboard is optional (e.g., a soft keyboard may be displayed when keyboard entry is needed). The output devices206also optionally include speakers and/or an audio output connection (i.e., audio jack) connected to speakers, earphones, or headphones. Optionally, the user device102includes an audio input device (e.g., a microphone) to capture audio (e.g., speech from a user). Furthermore, some user devices102use a microphone and voice recognition software to supplement or replace the keyboard. Optionally, the user device102includes a location-detection device, such as a GPS (global positioning satellite) or other geo-location receiver, and/or location-detection software for determining the location of the user device102.

In some embodiments, the one or more network interfaces210include wireless and/or wired interfaces for receiving data from and/or transmitting data to other user devices102, the proxy server140, the web servers150, and/or other devices or systems. In some embodiments, data communications are carried out using any of a variety of custom or standard wireless protocols (e.g., NFC, RFID, IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth, ISA100.11a, WirelessHART, MiWi, etc.). Furthermore, in some embodiments, data communications are carried out using any of a variety of custom or standard wired protocols (e.g., USB, Firewire, Ethernet, etc.). For example, in some embodiments, the one or more network interfaces210includes a wireless LAN (WLAN) interface211for enabling data communications with other WLAN-compatible devices and/or the proxy server140(via the one or more network(s)130,FIG. 1).

Memory212includes high-speed random-access memory, such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory212may optionally include one or more storage devices remotely located from the CPU(s)202. Memory212, or alternately, the non-volatile memory solid-state storage devices within memory212, includes a non-transitory computer-readable storage medium. In some embodiments, memory212or the non-transitory computer-readable storage medium of memory212stores the following programs, modules, and data structures, or a subset or superset thereof:an operating system216that includes procedures for handling various basic system services and for performing hardware dependent tasks;network communication module(s)218for connecting the user device102to other computing devices (e.g., the proxy server140, the web servers150, other user devices102, and/or other devices) via the one or more network interface(s)210(wired or wireless);a user interface module220that receives commands and/or inputs from a user via the user interface204(e.g., from the input devices208, which may include keyboards, touch screens, microphones, eye tracking components, three-dimensional gesture tracking components, and the like), and provides user interface objects and other outputs for display on the user interface204(e.g., the output devices206, which may include a display screen, a touchscreen, a speaker, etc.);one or more client application modules222, including the following modules (or sets of instructions), or a subset or superset thereof:a web browser module224(e.g., Internet Explorer by Microsoft, Firefox by Mozilla, Safari by Apple, Opera by Opera Software, or Chrome by Google) for accessing, viewing, and interacting with web sites (e.g., zero-rated and/or non-zero rated web sites), which includes:scripts226for the network service platform provided by the proxy server140(e.g., as embedded in a web page) and executed by the web browser module224; anda network service application module230for providing one or more functionalities related to network services provided by the proxy server140. For example, the application module230may process a request generated by another application (e.g., Application I242) running on the user device102, and may forward the request to the proxy server140. The network service application module230includes:data manager module231for exchanging data packets between the operating system kernel (e.g., kernel404,FIG. 4A) and the network service application230;application identification module232for checking an application ID associated with a packet to identify which application the packet originated from;proxy/drop determination module233for determining whether to proxy or to drop a packet by checking against predetermined rules (e.g., proxy/drop rules256);domain tag module234for generating synthesized IP addresses in association with domain names respectively and for storing mappings between synthesized IP addresses and domain names in the client database250(e.g., domain tag repository254);DNS response generation module235for generating DNS response messages using synthesized IP addresses;request checking module236for checking the cached mappings between synthesized IP addresses and domain names to identify a certain domain name for a given synthesized IP address;request processing module237for processing connection requests by replacing a synthesized IP address in the connection request with a domain name associated with the synthesized IP address; andlocal proxy238for forwarding processed requests (e.g., packets) from the user device102to the proxy server140; andother optional client application modules240, such as applications for social networking, word processing, calendaring, mapping, weather, stocks, time keeping, virtual digital assistant, presenting, number crunching (spreadsheets), drawing, instant messaging, e-mail, telephony, video conferencing, photo management, video management, a digital music player, a digital video player, 2D gaming, 3D (e.g., virtual reality) gaming, electronic book reader, and/or workout support. The other client application modules240includes:Application I module242is associated with a first domain name that is configured to provide zero-rated content; andApplication II module244is associated with a second domain name that is configured to provide non-zero-rated content. In some embodiments, Application I242and Application II244correspond to distinct domain names for hosting different contents and/or features. The first and second domain names are provided by a single server system (e.g., web server150-1) corresponding to the same IP address; andclient database250for storing data associated with the network service platform, including, but is not limited to:user profile252storing a user profile associated with the user of a client device102including, but not limited to, user account information, login credentials to the network service platform, payment data (e.g., linked credit card information, app credit or gift card balance, billing address, shipping address, etc.), bookmarked links (including zero-rated and/or non-zero rated), custom parameters (e.g., age, location, hobbies, etc.) of the user, contacts of the user, and identified trends and/or likes/dislikes of the user. For a given user, the user account information may include, for example, the user's name, profile picture, contact information, birth date, sex, marital status, family status, employment, education background, preferences, interests, and/or other demographic information;domain tag repository254storing mappings between synthesized IP addresses and domain names respectively; andproxy/drop rules256storing rules that can be used to determine whether to process or to drop a packet; andoptionally, domain whitelist(s)258storing one or more domains that are predetermined to provide zero-rated content to the user device102-1.

Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions as described above and/or in the methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments.

FIG. 3is a block diagram illustrating an exemplary proxy server140in accordance with some embodiments. The proxy server140includes one or more processing units (processors or cores)142, one or more network or other communications interfaces304, memory306, and one or more communication buses308for interconnecting these components. The communication buses308optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. The proxy server140optionally includes a user interface (not shown). The user interface, if provided, may include a display device and optionally includes inputs such as a keyboard, mouse, trackpad, and/or input buttons. Alternatively or in addition, the display device includes a touch-sensitive surface, in which case the display is a touch-sensitive display.

Memory306includes high-speed random-access memory, such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, and/or other non-volatile solid-state storage devices. Memory306may optionally include one or more storage devices remotely located from the processor(s)142. Memory306, or alternately the non-volatile memory device(s) within memory306, includes a non-transitory computer-readable storage medium. In some embodiments, memory306or the computer-readable storage medium of memory306stores the following programs, modules and data structures, or a subset or superset thereof:an operating system310that includes procedures for handling various basic system services and for performing hardware dependent tasks;a network communication module312that is used for connecting the proxy server140to other computers via the one or more communication network interfaces304(wired or wireless) and one or more communication networks (e.g., the one or more networks130);a network service database144for storing data associated with the network service platform, which includes:pricing policies320, including but not limited to:IP addresses322including, but not limited to, one or more predetermined zero-rated IP addresses, special-priced IP addresses, and/or regular-priced IP addresses;domain names324including, but not limited to, one or more predetermined zero-rated domain names, special-priced domain names, and/or regular-priced domain names; andcontent types326including, but not limited to, one or more content types (e.g., texts, images, and/or videos) for retrieval by the user devices102with predetermined pricing policies; andnetwork operator management information330including network operator information such as network segment information, network type, IP addresses and/or IP address blocks hosted by a respective network operator, etc.;user management information350, including but not limited to:user information352such as user profiles, login information, privacy and other preferences, biographical data, and the like. In some embodiments, for a given user, the user information352includes data associated with the user's name, profile picture, contact information, birth date, sex, marital status, family status, employment, education background, preferences, interests, and/or other demographic information;user device information354including, but not limited to, user device type, user device MAC address, Electronic Serial Number (ESN), International Mobile Station Equipment Identity (IMEI), Mobile Equipment Identifier (MEID), and/or other type(s) of user device identifier(s); andtransaction data356including, but not limited to, payment data (such as account balance, credit card information, app credit or gift card balance, billing address, shipping address, etc.) and/or purchased items (such as a network service type, data pack, etc.); anddomain whitelist(s)360storing one or more lists of domain names that are determined to provide zero-rated content to one or more user devices102; andIP addresses lookup list(s)364storing IP addresses used on the Internet for respective domain names; anda request handling module370for handling and responding to requests from user devices102, and for forwarding and routing requests or packets to corresponding web servers150;a network service module376for providing network service (e.g., Free Basics service) with various pricing policies and related features (e.g., in conjunction with browser module224or application module230on the user device102,FIG. 2);a domain validation module380for validating the domain names included in the requests against the domain whitelist(s)360;an IP identification module384for identifying IP addresses for respective domain names included in the requests by checking the IP address lookup list(s)364; anda social networking module390for providing social-networking services and related features (e.g., in conjunction with web browser module224or a social network application client module on the client device102,FIG. 2).

In some embodiments, the network service module376includes web or Hypertext Transfer Protocol (HTTP) servers, File Transfer Protocol (FTP) servers, as well as web pages and applications implemented using Common Gateway Interface (CGI) script, PHP Hyper-text Preprocessor (PHP), Active Server Pages (ASP), Hyper Text Markup Language (HTML), Extensible Markup Language (XML), Java, JavaScript, Asynchronous JavaScript and XML (AJAX), XHP, Javelin, Wireless Universal Resource File (WURFL), and the like.

Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions as described above and/or in the methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments.

FIG. 4Ais a diagram illustrating a packet transmission process400, in accordance with some embodiments.FIG. 4Bis a flow diagram illustrating a process450for processing a DNS request at the user device102-1, in accordance with some embodiments.FIG. 4Cis a flow diagram illustrating a process480for processing a connection request at the user device102-1, in accordance with some embodiments. One or more steps of the process400, process450, and process480are performed by a user device102(e.g., user device102-1,FIGS. 1-2), the proxy server140(FIGS. 1 and 3), and a web server150(e.g., web server150-1,FIG. 1). Operations performed in process400, process450, and process480correspond to instructions stored in computer memories (e.g., memories212,FIG. 2and memories306,FIG. 3) or other computer-readable storage mediums.

A process for handling a DNS request at the user device102-1is discussed with reference toFIGS. 4A-4B. In some embodiments, an application running on the user device102-1(e.g., Application I module242,FIG. 2) issues (452,FIG. 4B) a request412for obtaining an IP address of a domain name. For example, in order to establish a connection session between the user device102-1and the domain “www.example.com” hosted by the web server150-1, Application I242issues the request412to obtain an IP address of the domain “www.example.com.” In some embodiments, the request412is a DNS request.

Application I242sends the request412to kernel404of the operating system running on the user device102-1. In some embodiments, the operating system on the user device102-1is Android system. Kernel404is in charge of, among other features, managing input/output requests from software programs running on the user device102-1, translating the requests into data processing instructions for the CPU(s)202, and managing memories212, the output device(s)206, and the input device(s)208of the user device102-1. In some embodiments, kernel404generates (454,FIG. 4B) a packet414in accordance with the request412. In some embodiments, packet414is a DNS lookup request (e.g., a DNS query) that has a format that is in consistent with and supported by the DNS protocol. The DNS lookup request is used for obtaining the IP address of the domain “www.example.com” which is hosted by the web server150-1. Packet414includes a field specifying the destination domain name “www.example.com.” In some embodiments, the domain “www.example.com” is a zero-rated domain, and the request412/packet414is related to a zero-rated connection session, e.g., including downloading and/or uploading zero-rated content. In some embodiments, packet414is a User Datagram Protocol (UDP) packet/UDP request.

In some embodiments, the network service application230(e.g., the data manager module231,FIG. 2) intercepts (456,FIG. 4B) packet414from kernel404before packet414leaves the user device102-1. In some embodiments, the network service application230(e.g., the application identification module232,FIG. 2) identifies (458,FIG. 4B) from which application the request412/packet414originated. In some embodiments, the application identification module232checks an application ID included in packet414. For example, the application identification module232recognizes that the request412/packet414is issued by Application I module242by identifying an application ID of Application I242.

In some embodiments, the network service application230(e.g., proxy/drop determination module233,FIG. 2) determines (460,FIG. 4B) whether to proxy (e.g., by a synthesized IP address) packet414or to drop packet414. In some embodiments, the proxy/drop determination module233checks against the proxy/drop rules256(FIG. 2) to determine whether to proxy or to drop packet414.

In some embodiments, the proxy/drop determination module233determines whether packet414is a DNS query. When the proxy/drop determination module233determines that packet414is not a DNS query, the proxy/drop determination module233further determines whether packet414is a TCP packet. When the proxy/drop determination module233determines that packet414is neither a DNS request nor a TCP packet, packet414is dropped (460—Drop,FIG. 4B), and the current session initiated from Application I242is terminated (462,FIG. 4B). In some embodiments, when the proxy/drop determination module233determines that packet414is a DNS query, the network service application230proceeds to proxy packet414(460—Proxy,FIG. 4B)

Optionally, in some embodiments, the proxy/drop determination module233checks against the domain whitelist(s)258in the client database250to determine whether content provided by the identified domain name in packet414(e.g., www.example.com) is zero-rated. When the proxy/drop determination module233determines that the domain name is included in the domain whitelist(s)258, packet414is not dropped. However, when the proxy/drop determination module233determines that domain name is not included in the domain whitelist(s)258, packet414is dropped, and the current session is terminated. Optionally, in other embodiments, the user device102-1does not store any domain whitelist or blacklist, and whether the requested domain is zero-rated or not is not checked at the user device102-1.

In accordance with a determination that packet414is to be proxied (460—Proxy,FIG. 4B), the network service application230(e.g., domain tag module234) generates (464,FIG. 4B) a synthesized IP address to be associated with the domain name. For example, the domain tag module234generates a synthesized IP address of 10.11.12.13 to be associated with the domain name www.example.com. In some embodiments, the synthesized IP address is randomly generated. The synthesized IP address complies with Internet Protocol. In some embodiments, the synthesized IP address uses 32-bit numbers and complies with the IPv4 protocol. Alternatively, the synthesized IP address uses 128-bit numbers and complies with IPv6 protocol. The domain tag module234also stores a relationship mapping between the generated synthesized IP address and the domain name, e.g., www.example.com=10.11.12.13, in the domain tag repository254(FIG. 2). In some embodiments, the synthesized IP address is marked as a synthesized IP address, (e.g., a fake IP address, a tag, or a proxy), as opposed to a real IP address used on Internet to be associated with the domain name. In some embodiments, the synthesized IP address is generated and stored locally on the user device102-1. In some embodiments, the synthesized IP address is associated with the domain name locally on the user device102-1. For example, when later another DNS request is initiated on the user device102-1and inquires about the IP address for the same domain name, e.g., www.example.com, the same synthesized IP address, e.g., 10.11.12.13, is used. However, the synthesized IP address is not associated with the domain name at DNS level outside the user device102-1.

In response to the DNS query414, the network service application230(e.g., DNS response generation module235) generates (466,FIG. 4B) a DNS response416using the synthesized IP address. The generated DNS response416has a certain field specifying the synthesized IP address, e.g., 10.11.12.13. The network service application230responds (468,FIG. 4B) to the DNS query414using the generated DNS response416. The generated DNS response416is returned to Application I242via kernel404.

A process for handling a connection request at the user device102-1is discussed with reference toFIGS. 4A and 4C. In some embodiments, after Application I242receives the DNS response, Application I242initiates (482,FIG. 4C) a connection request418for establishing a connection session with a server associated with the synthesized IP address. For example, the connection request418is related to downloading content from or uploading content to the synthesized IP address. The connection request418is directed to the synthesized IP address, e.g., 10.11.12.13.

The network service application230(e.g., the data manager module231,FIG. 2) intercepts (486,FIG. 4C) packet420before it leaves the user device102-1. In some embodiments, the network service application230(e.g., proxy/drop determination module233,FIG. 2) determines (488,FIG. 4C) whether to drop packet414. In some embodiments, the proxy/drop determination module233checks against the proxy/drop rules256(FIG. 2) to determine whether to drop packet420.

In some embodiments, when the proxy/drop determination module233determines that packet420is neither a TCP packet nor a DNS packet, packet420is dropped (488—Yes,FIG. 4C), and the current session initiated from the Application I242is terminated (490,FIG. 4C). In some embodiments, when the proxy/drop determination module233determines that packet420is a connection request, e.g., a TCP request, the network service application230proceeds to check whether packet420includes a destination field which specifies a synthesized IP address. For example, the network service application230(e.g., the request checking module236,FIG. 2) checks packet420to identify the IP address, e.g., 10.11.12.13, listed in the destination address field. The network service application230may check the identified IP address against the synthesized IP addresses listed in the domain tap repository254to determine whether the identified IP address is a synthesized IP address. The network service application230may also check whether the identified IP address is marked as a synthesized IP address. When the network service application230determines that the identified IP address is not a synthesize IP address, packet420is dropped (488—Yes,FIG. 4C). When the network service application230determines that the identified IP address, e.g., 10.11.12.13, is a synthesized IP address, the network service application230proceeds to process packet420(488—No,FIG. 4C).

In some embodiments, the network service application230(e.g., the request processing module237,FIG. 2) checks the domain tag repository254to identify (492,FIG. 4C) a domain name associated with the synthesized IP address. For example, the request processing module237identifies that the domain “www.example.com” corresponds to the synthesized IP address “10.11.12.13.” The request processing module237processes packet420by replacing (494,FIG. 4C) the synthesized IP address with the identified domain name to generate a packet422. For example, the request processing module237replaces the synthesized IP address of “10.11.12.13” with the domain “www.example.com” in the destination address field. The network service application230(e.g., local proxy238,FIG. 2) sends (496,FIG. 4C) packet422to the proxy server140.

Referring toFIG. 4A, the proxy server140receives packet422. The proxy server140(e.g., domain validation module380,FIG. 3) checks whether the domain name included in packet422is zero-rated. For example, the domain validation module380compares the domain name www.example.com identified from packet422against the domain whitelist(s)360stored at the proxy server140. When the domain validation module380determines that the domain name is not included in the domain whitelist(s)360, the proxy server140drops packet422. In some embodiments, the proxy server140may send a notification message to the user device102-1to notify the user that the attempt to connect to domain www.example.com failed, because www.example.com is not a zero-rated content provider.

When the domain validation module380determines that the domain name is included in the domain whitelist(s)360, the proxy server140(e.g., IP identification module384,FIG. 3) checks the IP addresses lookup list(s)364to identify the real IP address for the domain name in packet422. For example, based on the IP address lookup list(s)364, a real IP address for the domain www.example.com on the Internet is 24.235.16.178. The proxy server140(e.g., the request handling module370,FIG. 3) then forwards packet422to the IP address 24.235.16.178 that hosts the domain www.example.com on Internet.

FIGS. 5A-5Care a flow diagram illustrating a method500for handling requests at the user device102, in accordance with some embodiments. The method500is performed by a user device (e.g., a user device102-1,FIGS. 1-2). Operations performed inFIGS. 5A-5Ccorrespond to instructions stored in computer memories (e.g., memories212,FIG. 2) or other computer-readable storage mediums. In some embodiments, the server system described in method500is the proxy server140(FIGS. 1 and 3). In some embodiments, the web server described in method500is any web server150(FIG. 1).

In some embodiments, the user device102detects (502) a DNS lookup request including a domain name. In some embodiments, the user device102-1(e.g., kernel404,FIG. 4A) generates (528) a first packet corresponding to the DNS lookup request. In some embodiments, the first packet is a UDP packet. For example as illustrated inFIGS. 4A-4B, kernel404generates a packet414corresponding to the lookup request412. The network service application230detects that packet414is a DNS lookup request that asks for an IP address of a domain name www.example.com.

In some embodiments, the DNS lookup request is initiated from (e.g., generated from) (516) a first application running on the user device102. For example as shown inFIG. 4A, the DNS request412is initiated from the first application, e.g., Application I242. In some embodiments, the network service application230(e.g., application identification module232,FIG. 2) checks (518) an application ID included in the DNS lookup request (e.g., packet414corresponding to the request412) to identify that the DNS lookup request is generated by the first application.

In some embodiments, the network service application230(e.g., DNS response generation module235,FIG. 2) generates (504) a first response (e.g., packet416,FIG. 4A) to the DNS lookup request. In some embodiments, the first response includes a synthesized IP address associated at the computing device with the domain name. For example, the response packet416includes the synthesized IP address 10.11.12.13 that is associated with the domain www.example.com locally at the user device102-1. The synthesized IP address 10.11.12.13 is not associated with the domain name www.example.com at the DNS level outside of the user device102-1.

In some embodiments, the DNS lookup request is (532) a first request of a plurality of DNS lookup requests including respective domain names. In some embodiments, the network service application230(e.g., DNS response generation module235,FIG. 2) responds (532) to the plurality of DNS lookup requests with responses including respective synthesized IP addresses associated at the user device102-1with the respective domain names. In some embodiments, within the user device102-1, each synthesized IP address is (532) unique to a respective domain name.

In some embodiments, the first response is (520) generated by a second application running on the user device102. The second application is distinct from the first application. For example, the second application is the network service application230, and the first application is Application I242. The second application sends (520) the first response from the second application, e.g., the network service application230, to the first application, e.g., Application I242. In some embodiments, the second application, such as the network service application230, provides access to zero-rated web services.

In some embodiments, the second application generates (524) the synthesized IP address. For example, the network service application230(e.g., domain tag module234,FIG. 2) generates the synthesized IP address 10.11.12.13 to be associated with the domain name www.example.com. In some embodiments, the second application stores (524) the synthesized IP address in the user device102. For example, the network service application230(e.g., domain tag module234,FIG. 2) stores the synthesized IP address 10.11.12.13 in association with the domain www.example.com in the domain tag repository254. In some embodiments, the synthesized IP address is (526) generated randomly at the user device102-1.

In some embodiments, the user device102detects (506) a connection request subsequent to the first response. The connection request includes the synthesized IP address. In some embodiments, the user device102-1(e.g., kernel404,FIG. 4A) generates (530) a second packet corresponding to the connection request. In some embodiments, the second packet is a TCP packet. For example as illustrated inFIGS. 4A-4B, kernel404generates a packet420corresponding to the connection request418. In some embodiments, the connection request is initiated from (e.g., generated from) (516) the first application running on the user device102. For example as shown inFIG. 4A, the connection request418is initiated from the first application, e.g., Application I242.

In some embodiments, the network service application230(e.g., request processing module237,FIG. 2) modifies (508) the connection request. The network service application230(e.g., request processing module237,FIG. 2) replaces the synthesized IP address in the connection request with the domain name. For example, as illustrated inFIGS. 4A and 4C, the request processing module237replaces the synthesize IP address 10.11.12.13 in packet420with the domain name www.example.com to obtain packet422. The network service application230(e.g., local proxy238,FIG. 2) forwards (510) the connection request to a server. In some embodiments, the user device102is (512) coupled to the proxy server140as shown inFIG. 1. In some embodiments, the local proxy238forwards (514) the connection request (e.g., packet422) to the proxy server140.

In some embodiments, the connection request is (534) a first connection request. The user network service application230(e.g., request checking module236,FIG. 2) detects (536) a second connection request including an IP address that is not one of the synthesized IP addresses. In accordance with a determination that the second connection request does not include one of the synthesized IP addresses, the second connection request is (538) dropped.

FIGS. 6A-6Bare a flow diagram illustrating a method600for handling requests at a proxy server coupled to a user device, in accordance with some embodiments. The method600is performed by a server system, (e.g., the proxy server140,FIGS. 1 and 3). The proxy server140is coupled to a plurality of user devices102and a plurality of web servers150. Operations performed inFIGS. 6A-6Bcorrespond to instructions stored in computer memories (e.g., memories306,FIG. 3) or other computer-readable storage mediums. In some embodiments, the user device described in method600is a user device102(FIGS. 1-2). In some embodiments, the web server described in method600is any web server150(FIG. 1).

In some embodiments, the proxy server140(e.g., the request handling module370,FIG. 3) receives (602) a request from a user device. The request includes a domain name. For example, as illustrated inFIGS. 4A and 4C, the proxy server140receives a request packet422from the user device102-1. The request packet422includes a domain name www.example.com in the destination address field.

In some embodiments, the proxy server140(e.g., the domain validation module380,FIG. 3) validates (604) whether the domain name in the request corresponds to a zero-rated web site. In some embodiments, the proxy server stores (616) a whitelist (e.g., the domain whitelist(s)360,FIG. 3) including one or more domain names that are zero-rated in the proxy server140. In some embodiments, the whitelist further stores (624) one or more synthesized IP addresses associated with respective domain names. In some embodiments, the domain validation module380determines (618) whether the domain name in the request is included in the whitelist for zero-rating. For example, the domain validation module380compares the domain www.example.com included in the request against the domain whitelist(s)360to determine whether the domain www.example.com is a zero-rated content provider.

In some embodiments, in accordance with a determination that the domain name corresponds to a zero-rated web site, the proxy server140(e.g., the request handling module370,FIG. 3) forwards (606) the request to a web server in accordance with the domain name. For example, when the domain validation module380determines that the domain name www.example.com is included in the domain whitelist(s)360, the request handling module370forwards the request to the web server150-1associated with the domain name www.example.com.

In some embodiments, in accordance with a determination that the domain name in the request is included in the whitelist for zero-rating, the proxy server140(e.g., the IP identification module384,FIG. 3) identifies (620) an IP address of the domain name. In some embodiments, the request handling module370sends (622) the request to the IP address of the domain name. For example, the IP identification module looks up the IP addresses lookup list(s)364for a real IP address, e.g., 24.235.16.178, for the domain www.example.com. The request handling module370then sends packet422to the web server150-1associated with the identified real IP address.

In some embodiments, the request is (608) a first request including a first domain name, e.g., www.example.com. The proxy server140(e.g., the request handling module370,FIG. 3) receives (610) a second request from a client device (e.g., the user device102-i). The second request includes (610) a second domain name that is distinct from the first domain name (e.g., www.example.com). In some embodiments, in accordance with a determination that the second domain name does not correspond to a zero-rated web site, the second request is (612) dropped. For example, when the domain validation module380determines that the second domain name is not included in the domain whitelist(s)360, the second request is related to a request for non-zero-rated content, thus the second request is dropped. In some embodiments, in accordance with a determination that the second domain name does not correspond to a zero-rated web site, the proxy server140(e.g., the request handling module370,FIG. 3) sends (614) a notification of violation of zero-rating to the user device102-ithat sent the second request.

Although some of various drawings illustrate a number of logical stages in a particular order, stages which are not order dependent may be reordered and other stages may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be apparent to those of ordinary skill in the art, so the ordering and groupings presented herein are not an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.