System and methods for enabling sponsored data access across multiple carriers

Abstract

A service and system for providing sponsored data, wherein the data usage is not charged to a mobile subscriber but, rather, paid for by a sponsor. The system and service is mobile-operator neutral and exists separate and apart from any given mobile network. The system provides, to mobile network operators and sponsoring entities, a single domain name (TLD). The TLD is white-listed, in wild-card form, by the mobile network operator so that the operator will know to zero rate any data traffic associated with the TLD. Sponsoring entities are also provided with a unique identifier. The unique identifier is concatenated, as a pre-pend, to the TLD, thereby generating a FQDN that (1) identifies associated data traffic as being sponsored and (2) identifies the entity sponsoring the data. The system monitors data usage associated with each FQDN and prepares a bill that charges each sponsoring entity for the data usage associated with the particular FQDN.

Claims

1. A method for providing access to sponsored data, wherein the method comprises: on-boarding a first mobile network operator (MNO) by transmitting an MNO-independent top level domain (TLD) from a first server to the first MNO, wherein the TLD is associated with sponsored data and is used by the first MNO to zero rate any data passing through the first mobile network that is associated with the address, and wherein, if any further MNOs are on-boarded, the first server transmits to said further MNOs the same MNO-independent TLD that was transmitted to the first MNO, thereby enabling said further MNOs to zero rate any data associated with the MNO-independent TLD to the extent such data is passim through respective networks of the further MNOs; on-boarding a first sponsor by transmitting a first unique identifier and the TLD from the first server to the first sponsor, wherein the first unique identifier and the TLD are concatenated, the first unique identifier as a pre-pend, generating a first fully qualified domain name (FQDN), and wherein the first FQDN is not provided to the first mobile network operator; monitoring, at a second server, usage of data associated with the first FQDN; and preparing, at a third server, a bill, wherein the bill is based on the monitored usage.

2. The method of claim 1 wherein the monitored usage is chargeable to the first sponsor and the bill is transmitted from the third server to the first mobile network operator.

3. The method of claim 1 wherein the monitored usage is chargeable to the first sponsor and the bill is transmitted from the third server to the first sponsor.

4. The method of claim 1 wherein on-boarding the first sponsor further comprises generating the first unique identifier.

5. The method of claim 4 wherein on-boarding the first sponsor further comprises generating the first unique identifier at the first server.

6. The method of claim 1 wherein the first server concatenates the first unique identifier and the TLD.

7. The method of claim 1 and further comprising: on-boarding a second sponsor by transmitting a second unique identifier and the TLD from the first server to the second sponsor, wherein the second unique identifier and the TLD are concatenated, generating a second FQDN, wherein the second FQDN is not provided to the first mobile network operator; monitoring, at the second server, usage of data associated with the second FQDN; and preparing, at the third server, a bill, wherein the bill is based on the monitored usage associated with the second FQDN.

8. The method of claim 7 wherein the second sponsor is on-boarded after the first mobile network operator is on-boarded.

9. The method of claim 1 and further comprising transmitting the TLD from the first server to a second mobile network operator, wherein the TLD is associated with sponsored data and is used by the second mobile network operator to zero rate any data passing through the second mobile network that is associated with the TLD.

10. A method for providing access to sponsored data, wherein the method comprises: on-boarding plural mobile network operators by transmitting a top level domain (TLD) that is the same for each of said operators from a first server to each of the plural mobile network operators, wherein the TLD is associated with sponsored data and is used by the plural mobile network operators to zero rate any data passing through the networks thereof that is associated with the TLD; on-boarding plural sponsors by transmitting to each such sponsor, from the first server, the TLD and an identifier that is unique to each sponsor, wherein the unique identifier is concatenated, as a pre-pended, to the TLD, thereby generating unique FQDNs for each of the sponsors, wherein each unique FQDN is indicative of sponsored data and the sponsor thereof, and wherein the FQDNs are not provided to the plural mobile network operators; monitoring, at a second server, usage of data associated with the FQDNs; and preparing, at a third server, bills, wherein each bill is associated with one of the FQDNs and is based on the monitored usage associated therewith.

11. A method for providing access to sponsored data comprising: receiving, at a proxy server, a request for first sponsored data from a first mobile subscriber and a request for second sponsored data from a second mobile subscriber, wherein a first sponsor is associated with the first sponsored data and a second sponsor is associated with the second sponsored data; serving, from the proxy server, the first sponsored data to the first mobile subscriber and the second sponsored data to the second mobile subscriber; monitoring, in the proxy server, a first amount of the first sponsored data being served and a second amount of the second sponsored data being served, wherein associated with the first and second sponsored data is (1) a common TLD, which is the same for both the first and the second sponsored data; and (2) a unique pre-pend, which is different for the first and the second sponsored data and that identifies the first sponsor and the second sponsor.

12. The method of claim 11 wherein the serving further comprises the proxy server requesting the first sponsored data from a first content server and the proxy server requesting the second sponsored data from a second content server.

13. The method of claim 11 wherein the first content server is accessible via a first internet service provider and the second content server is accessible via a second internet service provider.

14. The method of claim 11 wherein the proxy server is a replica server and further wherein, when the first sponsored data is available in a cache accessible to the replica server, the replica server serves the first sponsored data to the first mobile subscriber.

15. The method of claim 11 wherein the serving further comprises the proxy server requesting the first sponsored data from a first content server and receiving the first sponsored data from a replica server that is part of a content delivery network.

16. The method of claim 11 wherein the first mobile subscriber is a subscriber of a first mobile network and the second mobile subscriber is a subscriber of a second mobile network.

17. The method of claim 1 wherein the TLD is a mobile network operator-independent IP address.

18. The method of claim 10 wherein the TLD is a mobile network operator-independent IP address.

19. The method of claim 11 wherein the TLD is a mobile network operator-independent IP address.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 depicts a sponsored data service in the prior art.

(2) FIG. 2 depicts an architecture for a sponsored data service/system in accordance with the present teachings.

(3) FIG. 2A depicts an embodiment of a sponsored data service/system in accordance with the present teachings.

(4) FIG. 2B depicts a method for operating the system of FIG. 2A.

(5) FIG. 3A depicts an embodiment of a sponsored data service/system in accordance with the present teachings.

(6) FIG. 3B depicts a method for operating the system of FIG. 3A.

(7) FIG. 4 depicts an embodiment of a sponsored data service/system in accordance with the present teachings.

(8) FIG. 5A depicts an embodiment of a sponsored data service/system in accordance with the present teachings.

(9) FIG. 5B depicts a method for operating the system of FIG. 5A.

(10) FIG. 6 depicts an embodiment of a sponsored data service/system in accordance with the present teachings.

(11) FIG. 7 depicts an embodiment of a sponsored data service/system in accordance with the present teachings.

(12) FIG. 8 depicts a block flow diagram of a method for accessing sponsored data in accordance with the present teaching.

DETAILED DESCRIPTION

(13) The term sponsor is explicitly defined for use herein and in the appended claims to mean: an entity associated with sponsored data, which can be, without limitation, an enterprise, an enterprise offering split billing to its employees, a third party, such as an advertiser, an Ad network, or a collection of destinations. Typically, a sponsor is any entity that pays for at least some of the cost of sponsored data. Yet, the sponsor might not offer any content at all.

(14) The term sponsored data is explicitly defined for use herein and in the appended claims to mean: data usage by a mobile subscriber that is not charged to the subscriber's mobile data plan.

(15) The various embodiments of the sponsored data service/system (SDS) all provide at least several functions from a basic suite thereof. This suite of functions is presented below and briefly discussed. Asset Management: The assets are the URL(s) and IP addresses that are used to identify sponsored data. They need to be securely managed internally, in known fashion, and then provided to an MNO for white-listing when they are on-boarded to the system. In the illustrative embodiment, the SDS will use a single domain name, although optionally, additional sponsored-data domains names can be used. MNO Onboarding: Initial contact information, qualification analysis, service parameters, and a verification of the sponsor list and content with MNO. Once the information is gathered, certain preliminary functions are performed depending on whether there are existing Sponsor relationships with the MNO or SDS. These functions include, among any other tasks, whitelisting. Sponsor Onboarding: SDS receives at least some of the following information from the sponsor: a) contact list, b) list of MNOs they want or do not want to do business with, c) a description of content type. SDS provides the sponsored data TLD or IP address to the sponsor with a unique identifier that is then pre-pended to the TLD. Data Monitoring: The MNO begins monitoring a mobile subscriber's activity as soon as the subscriber launches a mobile app or clicks on a link to request access to sponsored content. The MNO counts data usage for sponsored as well as un-sponsored content. The SDS counts data usage for all sponsored content. All content that falls within the address range provided by the SDS that corresponds to the sponsored URL(s) or IP addresses in the whitelist will be zero-rated. In other words, it will be counted and reported, but not charged to the subscriber. When a mobile subscriber has been approved with a sponsor, monitoring of that subscriber's activities on the specified sponsored URL or IP address begins. The SDS receives all of the sponsored data traffic to and from the subscriber. The mobile app or browser web page on the subscriber's phone will be instructed to communicate with a URL (or IP address) internal to the SDS. The URL or IP address acts as a proxy (or CDN) for the final destination at the sponsor. This enables the monitoring function at SDS to see all sponsored traffic and monitor the data sent to and from the mobile subscriber. Billing Settlement: In hub-based embodiments, the SDS monitors the usage of data and helps the MNO prepare a bill that the MNO ultimately sends to the sponsor. The SDS bills the MNO for its data monitoring and billing service. In hub-exchange based embodiments, the MNO will bill the SDS based on negotiated rates and the MNO's byte count (reconciled with the SDS's own byte count), and the SDS bills sponsors based on SDS's byte counts at its negotiated rates.

(16) As previously noted, in some embodiments, the service provided by the SDS is established via registration. Registration may be accomplished, for example, via intelligence placed in a phone application (App) provided by the sponsor, or when a subscriber visits the sponsor's web site. After registration is complete, the subscriber's phone will be permitted access to certain free URLs on the Internet, as sponsored by that sponsor. The service involves a number of tasks, such as acquiring the App user onboarding, user authentication, determination of sponsor offerings, etc. The end-to-end method for accessing sponsored data is discussed later in this disclosure in conjunction with FIG. 8 after a number of embodiments of the SDS are presented.

(17) FIG. 2 depicts an illustrative embodiment of the SDS in accordance with the illustrative embodiment of the present invention. FIG. 2 depicts the equipment/functionality required of the SDS. In the figures that follow, which show various embodiments of an SDS, only the pertinent functionality of the SDS will be depicted.

(18) As depicted in FIG. 2, SDS 200 includes database 220, on-boarding & authorization subsystem 230, proxy server and data metering subsystem 240, billing & reporting subsystem 250, and various routers, load balancers, a firewall, on other equipment/functionality for interfacing with other networks (e.g., ISPs, MNOs, etc.) shown collectively as subsystem 260.

(19) In light of the present disclosure, those skilled in the art will be familiar the various subsystems composing SDS 200 and the functioning thereof. As a consequence, such subsystems will be discussed only briefly.

(20) Database 220 is populated with information concerning the sponsors and MNOs (e.g., sponsor IDs, sponsor billing address, contact names, call detail records/session detail records, content source URLs, and the like.

(21) On-boarding & authorization subsystem 230 includes business logic server 232, App server w/APIs 234, and on-boarding portal 236. Business logic server 232 provides any business logic and decision making processes that are implemented (e.g., rules engines for sponsorship approval, etc.). App server w/APIs 234 is a set of web applications and APIs that are available to MNOs and sponsors for automated reading/writing data (e.g., reading rate tables, requesting reports, etc.). Among other tasks, business logic server 232 and App server 234 (which can be combined into a single server) provide the domain name (e.g., .TATA_SponData.com to MNO(s) that are partnering with SDS 200. For a sponsor, a sponsor identifier is provided, which is concatenated (as a pre-pended) to the domain name, thereby generating a fully qualified domain name (FQDN). On-boarding portal 236 can be, for example, an interactive web site that MNOs and sponsors use to on-board to SDS 200.

(22) Proxy & Metering subsystem 240 comprises a proxy server that receives the sponsored content from a source thereof and delivers it to a subscriber. The proxy server includes a byte counting function to keep track of the amount of data passing through it. FIG. 2 depicts three different types of proxy servers: HTTP proxy server 242A, HTTPs proxy server 242B, and VPN proxy server 242C. HTTP proxy server 242A handles proxying and byte counting for HTTP session, HTTPs proxy server 242B handles proxying and byte counting for HTTPs sessions, and VPN proxy server 242C handles proxying and byte counting for VPN sessions. It will be understood that while SDS 200 might include multiple proxy servers of the same type, in some embodiments, all three of the proxy servers referenced might be present in SDS 200 depending on the type of service provided to the MNO.

(23) Billing & reporting subsystem 250 includes billing servers 252. The billing servers receive information concerning the amount of sponsored data consumed by one or more sponsors and prepares invoices based on that consumption. The billing servers also deal with MNO payments, mediation, reporting, etc. As discussed later in this specification, the bill can be sent to the MNO or can be sent directly to the sponsors, depending on the embodiment.

(24) Subsystem 260 includes routers, load balancers, a firewall, and other functionality required for interfacing with other networks, such as ISPs or MNOs.

(25) FIG. 2A depicts a hub-based sponsored data service/system SDS.sub.h 200 in accordance with the present teachings. In this embodiment, SDS.sub.h 200 provides onboarding of MNOs and Sponsors, monitoring (byte counting) of sponsored data sessions, and billing services. With regard to the billing services, SDS.sub.h 200 prepares a bill for the MNO that the MNO then sends to the sponsor. As previously discussed, the bill will be prepared on the MNOs stationary and the presence of SDS.sub.h 200 can remain hidden from the sponsor(s). In some embodiments, SDS.sub.h can police access and can redirect or refuse access to sponsored data based on various rules/criteria.

(26) In FIG. 2A, SDS.sub.h 200 is depicted as being used in conjunction with two MNOs 102A and 102B, two ISPs 108A and 108B, and two sponsors A and B, each represented by content/control servers 212 and 214, accessible via one or the other of the ISPs. It is to be understood that SDS.sub.h 200 can, more generally, be used in conjunction with one or more MNOs, each telecommunicating with one or more ISPs, each of which ISPs provide access to one or more sponsors. In fact, each of such sponsors can be associated with plural content providers. This is true, as well, for all embodiments of SDS.sub.h and SDS.sub.h.e. discussed herein.

(27) The flow of information (e.g., requests, control, sponsored data, etc.) is identified in this embodiment, and for all other embodiments, via telecommunication links (hereinafter com links), which appear as dashed lines. It is to be understood that the com links can represent any number of physical/logical channels and are merely intended to be indicative of a flow of one or more types of information between locations. It is to be understood that the subscribers can access both sponsored and unsponsored data via the SDS, but to maintain focus on what is germane to the invention, access to sponsored data only is discussed.

(28) FIG. 2B depicts method 201 for operating SDS.sub.h 200. Before any of the activity depicted in FIG. 2A can occur, both sponsors and MNOs must be on-boarded, per operations 203 and 205. The on-boarding process involves a number of activities that will be familiar to those skilled in the art (exchange of certain information, etc.). What is unique, and germane to hub-based embodiments of the invention, is that for MNO on-boarding (task 203), in some embodiments: SDS.sub.h 200 provides a single domain name (TLD) for the white-listing; The MNO enters a wild-carded version of the single domain name into its white-list.
For sponsor on-boarding (task 205), in some embodiments: SDS.sub.h 200 provides to the sponsor a sponsor IDa label, that is concatenated, as a pre-pended, to the domain name.
As indicated by the arrows associate with task 205, a very advantageous feature of the embodiments of the invention is that additional sponsors can be on-boarded without having to update the MNO's white-list. That is, MNO on-boarding and white-listing of the sponsored domain can be a one-time process, even if additional sponsors are added or new links are added by a sponsor. This is not possible in prior-art solutions.

(29) SDS.sub.h 200 possesses most if not all of the equipment/functional elements depicted in FIG. 2. However, as previously noted, to keep the focus of the disclosure on what is germane to the invention, FIG. 2 depicts the SDS.sub.h 200 as including proxy server 242A having data counter 244.

(30) Referring now to FIGS. 2A and 2B, access to sponsored data in the context of this embodiment occurs as follows.

(31) Subscriber 104A makes a request to control server 270A, over com links 11A and 13A, for sponsored data. In some embodiments, the request is byte-counted by MNO 102A and will be charged against the subscriber's data plan. In some other embodiments, the request itself is sponsored and is not charged against the subscriber.

(32) Assuming the request is granted, control server 270A returns, to subscriber 104A over com links 13A and 11A, a redirect to proxy server 242A in SDS.sub.h 200. In some embodiments, this response is byte counted by MNO 102A and will be charged against the mobile subscriber's data plan; in some other embodiments, the response is not charged against the subscriber.

(33) Subscriber makes request for sponsored content to proxy server 242A over com links 11A, 17A (see task 207). This request is zero rated by MNO and byte counted by data counter 244 in the proxy server. At task 209, proxy server 242A makes a request for content to content Server 272A over com link 15A. Per task 211, content server 272A returns content to proxy server 242A over com link 15A. The proxy server then serves the sponsored content to subscriber 104A over com links 17A and 11A, per task 213.

(34) Data usage is monitored (byte counted) in data counter 244 in accordance with task 215. The sponsored content is zero rated by MNO 102A so there is no charge to subscriber 104A. It will be appreciated that data monitoring, per task 215, occurs as content is being served; that is, no order of tasks is implied by the relative reference numerals of the tasks (i.e., 213 versus 215). This is true for all the following embodiments as well.

(35) In accordance with task 217, billing and reporting subsystem 250 of SDS.sub.h 200 prepares an invoice for MNO 102A reflecting usage of sponsored data and transmits it, over com link 21A, to GGSN 106A in MNO 102A. The bill is typically prepared on the MNO's billing stationary and is then sent from MNO 102A to Sponsor A.

(36) SDS.sub.h 200 interacts with subscriber 104B, MNO 102B, ISP 108B, and sponsor B in the same fashion as discussed above with respect to subscriber 104A, MNO 102A, ISP 108A, and sponsor A to provide subscriber 104B with access to sponsored data.

(37) FIG. 3A depicts a hub-and-exchange based sponsored data service/system SDS.sub.h.e. 300 in accordance with the present teachings. FIG. 3B depicts method 301 for operating SDS.sub.h.e. 300. Although the architecture of SDS.sub.h.e. 300 (and that of other embodiments of SDS.sub.h.e. depicted later in this specification) is mostly the same as that of the illustrative embodiment of SDS.sub.h, the mode of operation is somewhat different. Chief among such differences is that in embodiments of the SDS.sub.h.e., the operator of the SDS.sub.h.e. negotiates with the MNO(s) for the data usage and then charges the sponsors directly at rates that the SDS.sub.h.e. negotiates with the sponsors. In contrast, the SDS.sub.h does not purchase data from the MNO nor (typically) charge the sponsor directly. Rather, the sponsor is charged at the rates agreed to with the MNO and the SDS.sub.h charges the MNO a fee for its services.

(38) In FIG. 3A, SDS.sub.h.e. 300 is used in conjunction with two MNOs 102A and 102B, two ISPs 108A and 108B, and two sponsors A and B. Sponsor A has control server 270A and content server 272A. Sponsor B has control server 270B and content server 272B. Access to the information of sponsor A is via ISP 108A and access to the information of sponsor B is via ISP 108B.

(39) Referring now to FIGS. 3A and 3B, as per method 301, SDS.sub.h.e. 300 on-boards MNOs at task 303 and Sponsors at task 305, to the extent this has not been performed. In addition to the tasks performed during on-boarding for hub-based embodiments (i.e., SDS.sub.h 200), for MNO on-boarding, the SDS enters into a wholesale data arrangement with the MNO wherein it purchases data from the MNO. And for sponsor on-boarding, the SDS and sponsor agree on a rate at which the SDS will charge the sponsor for the sponsored data.

(40) Access to sponsored data in the context of this embodiment occurs as follows.

(41) Subscriber 104A makes a request to control server 270A, over com links 11A and 13A, for sponsored data. In some embodiments, the request is byte-counted by MNO 102A and will be charged against the subscriber's data plan. In some other embodiments, the request itself is sponsored and is not charged against the subscriber.

(42) Assuming the request is granted, control server 270A returns, to subscriber 104A over com links 13A and 11A, a redirect to proxy server 242A in SDS.sub.h.e. 300. In some embodiments, this response is byte counted by MNO 102A and will be charged against the mobile subscriber's data plan; in some other embodiments, the response is not charged against the subscriber.

(43) Subscriber makes request for sponsored content to proxy server 242A over com links 11A, 17A (see task 207). This request is zero rated by MNO and byte counted by data counter 244 in the proxy server. At task 209, proxy server 242A makes a request for content to content server 272A over com link 15A. Per task 211, content server 272A returns content to proxy server 242A over com link 15A. The proxy server then serves the sponsored content to subscriber 104A over com links 17A and 11A, per task 213.

(44) Data usage is monitored (byte counted) in data counter 244 in accordance with task 215. The sponsored content is zero rated by MNO 102A so there is no charge to subscriber 104A.

(45) Data usage is reported to billing and reporting subsystem 250 over com link 19. A bill is prepared by SDS.sub.h.e. 300 for the amount of sponsored data usage and sent directly to sponsor A over com link 23 (see task 217). Invoicing will occur on some periodic (e.g., monthly, etc.) basis.

(46) SDS.sub.h.e. 300 interacts with subscriber 104B, MNO 102B, ISP 108B, and sponsor B in the same fashion as discussed above with respect to subscriber 104A, MNO 102A, ISP 108A, and sponsor A to provide subscriber 104B with access to sponsored data.

(47) FIG. 4 depicts SDS.sub.h.e. 300 accessing sponsored content from a distributed content delivery network.

(48) In FIG. 4, SDS.sub.h.e. 300 is used in conjunction with two MNOs 102A and 102B, two ISPs 108A and 108B, two sponsors A (control server 270A and content server 272A) and B (control server 270B and content server 272B), and content delivery network (CDN) 474. This CDN is a conventional content delivery network comprising a large distributed system of content servers deployed in multiple data centers across the Internet.

(49) CDN 474 includes a plurality of replica servers, four of which (i.e., 476A through 476D) are depicted in FIG. 4.

(50) The method by which sponsored data is obtained is similar to that depicted in FIG. 3B. However, rather than proxy server 242A receiving content from content server 272A, it receives it from replica server 476A over com link 29A, after the replica server receives the content from content server 272A over com link 27A (if the replica server does not have the content in its data cache).

(51) Replica server 476C is also depicted as providing content to proxy server 242A (over com link 29C). This is simply to illustrate that the content may be provided from multiple replica servers.

(52) SDS.sub.h.e. 300 interacts with subscriber 104B, MNO 102B, ISP 108B, sponsor B, and CDN 474 in the same fashion as discussed above with respect to subscriber 104A, MNO 102A, ISP 108A, and sponsor A to provide subscriber 104B with access to sponsored data.

(53) FIG. 5A depicts a further embodiment of a hub-and-exchange sponsored data service/system SDS.sub.h.e. 500 in accordance with the present teachings. In addition to providing the functionality of SDS.sub.h.e. 300, SDS.sub.h.e. 500 itself functions as a CDN. In some alternative embodiments, the requisite monitoring (e.g., byte counting, etc.) equipment for a SDS is installed in a third party CDN that partners with the operator of the sponsored data service/system.

(54) FIG. 5B depicts method 501 for operating SDS.sub.h.e. 500. As is typical for embodiments of the invention, SDS.sub.h.e. 500 provides onboarding of MNOs and Sponsors, monitoring (byte counting) of sponsored data sessions, and billing services.

(55) In FIG. 5A, SDS.sub.h.e. 500 is used in conjunction with two MNOs 102A and 102B, two ISPs 108A and 108B, two sponsors A (control server 270A and content server 272A) and B (control server 270B and content server 272B). As previously indicated, in addition to providing the functionality of SDS.sub.h.e. 300, SDS.sub.h.e. 500 functions as a content delivery network in this embodiment.

(56) Referring now to FIGS. 5A and 5B, as per method 501, SDS.sub.h.e. 500 on-boards MNOs at task 503 and Sponsors at task 505 to the extent this has not been performed. Access to sponsored data in the context of this embodiment occurs as follows.

(57) Mobile subscriber makes a request to control server 270A, over com links 11A and 13A, for sponsored data. In some embodiments, the request is byte-counted by MNO 102A and will be charged against the subscriber's data plan. In some other embodiments, the request itself is sponsored and is not charged against the subscriber.

(58) Assuming the request is granted, control server 270A returns, to subscriber 104A over com links 13A and 11A, a redirect to replica server 578A in SDS.sub.h.e. 500. In some embodiments, this response is byte counted by MNO 102A and will be charged against the mobile subscriber's data plan; in some other embodiments, the response is not charged against the subscriber.

(59) Subscriber 104A makes request for sponsored content to Replica Server 578A over com links 11A and 17A (see task 507). This request is zero rated by MNO and byte counted by data counter 244 in replica server 578A. Query, at task 509, whether the sponsored content is available in the cache of replica server 578A. If not, at task 511, replica server 578A fetches the sponsored content from content server 272A over corn link 15A.

(60) At task 513, replica server 578A serves the sponsored content to subscriber 104A over corn links 17A and 11A, per task 513.

(61) Data usage is monitored (byte counted) in data counter 244 in accordance with task 515. The sponsored content is zero rated by MNO 102A so there is no charge to subscriber 104A.

(62) Data usage is reported to billing and reporting subsystem 250 over corn link 19A. A bill is prepared by SDS.sub.h.e. 500 for the amount of sponsored data usage and sent directly to sponsor A over corn link 23 (see task 517). Invoicing will occur on some periodic (e.g., monthly, etc.) basis.

(63) SDS.sub.h.e. 500 interacts with subscriber 104B, MNO 102B, ISP 108B, and sponsor B in the same fashion as discussed above with respect to subscriber 104A, MNO 102A, ISP 108A, and sponsor A to provide subscriber 104B with access to sponsored data.

(64) FIG. 6 depicts yet a further embodiment of a hub-and-exchange sponsored data service/system SDS.sub.h.e. 600 in accordance with the present teachings.

(65) In FIG. 6, SDS.sub.h.e. 600 is used in conjunction with two MNOs 102A and 102B, two ISPs 108A and 108B, two sponsors A (control server 270A and secure content server 680A) and B (control server 270B and content server 680B).

(66) In this embodiment, SDS.sub.h.e. 600 is configured to sponsor applications wherein secure HTTP sessions using HTTPs are required (e.g., shopping carts, etc.). Providing the functionality of the other embodiments (e.g., monitoring, billing, etc.) is problematic since the sponsored data service/system will have little or no access to the contents of the secure data stream in order to make decisions on routing, monitoring, billing etc. For HTTPs, the sponsored data service/system only has access to the source and destination IP addresses; everything else is encrypted.

(67) In accordance with some embodiments of the present invention, this problem is addressed by having secure proxy server 242B terminate the original HTTPS session, then originate a new secure session back to the sponsored data origin (i.e., the sponsor's content server) or serve content from local cache (i.e., a replica server in a CDN). This architecture and methodology is effectively the same as presented in conjunction with SDS.sub.h.e. 300 depicted in FIGS. 3A and 3B, with the exception of secure proxy server 242B replacing proxy server 242A.

(68) A security certificate management function (as part of the asset management functionality) is required since the data is arriving at SDS.sub.h.e. 600 as HTTPs. As previously indicated, incoming sponsored data passes is byte counted in data counter 244 and then terminated on secure proxy server 242B. The proxy server then forwards the data to the sponsored data origin or the subscriber depending on the direction of the flow.

(69) In all secure scenarios (i.e., HTTPs or VPN), IP addresses, rather than URLs, must be used to identify sponsored data. In such embodiments, the SDS presents a virtual IP address to the MNO (during on-boarding) that gets white-listed.

(70) It is notable that to provide certain types of sessions, such as a shopping cart, an additional requirement on SDS.sub.h.e. 600 is that it should be PCI compliant so that it does not break the trust relationship between the subscriber and the sponsor.

(71) SDS.sub.h.e. 600 is operated in the same manner as depicted in FIG. 3B for SDS.sub.h.e. 300.

(72) FIG. 7 depicts SDS.sub.h.e. 700, which includes VPN proxy server 242C. Unlike the previous embodiment with HTTPs proxy server 242B, in a VPN, the secure stream is not terminated. In this embodiment, SDS.sub.h.e. 700 effectively functions as a transparent proxy, merely forwarding data and byte count. The VPN may be required for certain B2E applications.

(73) There are basically two application componentsclient side and server sideto a sponsored data session.

(74) On the client side is a software application running on the mobile user's phone. In some embodiments, this is mobile App; in some others, it's a browser. This application is responsible for all user interaction via the SDS and communicates with the server side, to seek approval for data access and to retrieve and display sponsored content. The server side includes the sponsor's web application server and the SDS proxy server. The server side is responsible for authenticating/approving a user and for serving up the sponsored content. Furthermore, the server side is responsible for counting the sponsored data bytes and then billing the sponsors for the requisite amount of data.

(75) FIG. 8 depicts method 801 for conducting a sponsored data session. Task 803 requires obtaining the client side application. This can be accomplished in any one of several ways. In some embodiments, the process begins by opening the browser in the mobile user equipment and visiting the sponsor's website via a published URL. The subscriber then downloads and installs the App on the mobile UE. In some other embodiments, the process begins with the subscriber directly visiting the Android App store or iTunes store and selecting, downloading, and installing the App on the mobile user equipment.

(76) If the mobile user wishes to access sponsored content, then at task 807, the App is launched and a session is initiated. Assuming the App is still active from task 805, information is gathered from the mobile UE (e.g., credentials, etc.) and the request is routed to application server for the sponsored link. The server receives the session request and prepares to authenticate the mobile user in task 809. Alternatively, this could be performed using a cookie.

(77) At task 811, the system determines which content can be sponsored for the subscriber during the session based on certain criteria (e.g., location of user, the home MNO, calendrical time, etc.). It might be that all, some, or none of the content is available to be sponsored for the mobile user. If no sponsored content is available to the mobile user, then the App is either redirected to an unsponsored site or the session is ended. If some or all of the sponsored content is available to the mobile user, they are redirected to a page that provides the desired content or links to options, if they exist.

(78) At task 813, the mobile user loads the redirect page. The content may be delivered from the origin (i.e., the sponsor's server) through the SDS proxy server or from a cached location. At this point, an advertisement could be displayed. If there is only one offer, the mobile user views it; if there are multiple offers, the user selects the desired link.

(79) At task 815, the sponsored content is streamed (from source or cache) to the App on the subscriber's phone. The App renders, for example, video in the phone's display. The content streams until an end session condition is reached. The SDS logs the session and counts bytes. At task 817, the session ends.

(80) It is to be understood that many variations of the invention can easily be devised by those skilled in the art after reading this disclosure and that the scope of the present invention is to be determined by the following claims.