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.

Description:
STATEMENT OF RELATED CASES 
       [0001]    This case claims priority of U.S. Patent Application Ser. No. 61/943,454, filed Feb. 23, 2014 and which is incorporated by reference herein. 
     
    
     FIELD OF THE INVENTION 
       [0002]    This invention pertains generally to mobile networks and more particularly to accessing data via a mobile network. 
       BACKGROUND OF THE INVENTION 
       [0003]    Data access in a mobile network is unique in the world in that the operator charges the subscriber per access and by quantity. To that end, a Mobile Network Operator (MNO) keeps a detailed subscriber record in its database. Those records are used to control a mobile subscriber&#39;s ability to access the mobile network and the capabilities available to the user when using the mobile network. For example, subscriber account information can be used to determine if the subscriber can access the mobile network and at what usage level. 
         [0004]    In the current mobile model, all data received and sent by a mobile device user is tracked by the MNO and charged against a pre-agreed data plan. This could be a post-paid plan as is most common in the United States or a prepaid type plan where mobile users pay up-front for a block of data. Once the allowance or quota is used, the mobile user has to pay for the extra amount on their monthly bill or “top up” their phone in the prepaid model if they want to continue using data services. 
         [0005]    Subscribers tend to watch their mobile data usage to avoid charges either by forgoing data usage altogether or by seeking out WiFi networks where a free or flat-rate charge will cover all the data they need to consume. As a consequence, the MNO&#39;s network is underutilized and its potential revenue is reduced. In order to resolve this, the operators need to create a solution that will attract more subscribers and still allow for premium revenue, thus combating the trend towards using WiFi instead. 
         [0006]    One such solution to this problem is for the MNO to ask the source of the data to pay for the subscriber&#39;s data. This approach is termed “Sponsored Data,” wherein instead of the MNO charging the subscriber (e.g., consumer, business person, etc.) for their data usage, some or all of their data is paid for by some entity other than the end consumer; that is, the entity that is the source of the data being accessed. This is advantageous for all involved:
       the subscriber saves money;   the sponsoring entity attracts more customers to its web site, presumably promoting its products or services; and   the MNO is now getting paid for data traffic on its network that, but for the sponsor paying for it, would likely not exist.       
 
         [0010]    In the case of Sponsored Data, the MNO still tracks the data usage of their customers. But the data cost for accessing certain websites or services (i.e., the sponsored services) would be passed back to the sponsor of the content rather than to the mobile subscriber. 
         [0011]      FIG. 1  depicts prior-art sponsored data service/system  100 . MNO  102  provides both sponsored and non-sponsored data to its mobile subscribers ( 104   a  and  104   b ). The data is sourced from Entity  110  and Entity  112 , as accessed via Internet Service Provider (“ISP”)  108 . Entity  110  has not joined sponsored data service/system  100  and, as a consequence, mobile subscribers  104   a  and  104   b  will pay for any data usage (over communications (“com”) links  2  and  4  sourced from enterprise  110 . Entity  112  has joined the sponsored data service  100  and, as such, will itself pay the MNO for the data usage (over com links  3  and  5 ) of subscriber  104   b  of data sourced from Entity  112 . 
         [0012]    MNO  102  must keep track of what particular data is sponsored and what data is not sponsored, such as by using “white-listed” URLs/IP addresses encoded into the MNO&#39;s packet gateway. In this context, white-listed URLs indicate participation in the sponsored data service such that data usage in conjunction with such URLs is not debited against a subscriber&#39;s account. This white-listing process must be performed for each entity that is sponsoring data and it must be performed on a per URL basis. More specifically, the white-listed URLs/IP addresses are retained by, and the data tracking is performed by Gateway GPRS Support Node (GGSN)  106 . In some other embodiments, these functions are handled by the CDMA Packet Data Serving Node (PDSN), 4G Packet Gateway (PGW) element, or packet core enforcement function (PCEF), the latter of which can be in a stand-alone server or incorporated in the GGSN, PDF, or PDSN. 
         [0013]    Consider that a single sponsoring entity could have many thousands of URLs mapping to multiple pages from multiple customers. Every such URL would have to be “white-listed” in order for such access not to be charged to the subscriber. That means encoding the many thousands of URLs in an MNO&#39;s packet gateway. This is significant hardship for an MNO. 
         [0014]    Every time a sponsoring entity adds a new sponsored link, that link has to be white-listed in the MNO&#39;s packet gateway. So in addition to the initial (static) on-boarding white-listing burden, there is a continuing (dynamic) burden, wherein any new sponsored links must be encoded in the MNO&#39;s packet gateway. Not all networks are even capable of doing this. 
         [0015]    The aforementioned and other drawbacks of prior-art sponsored data service  100  are summarized in Table 1, below. 
         [0000]    
       
         
               
               
             
           
               
                   
               
               
                 Feature 
                 Drawback/Disadvantage 
               
               
                   
               
             
             
               
                 URL/IP 
                 The sponsoring entity must provide a server-side function that issues a set of 
               
               
                 Address 
                 white-listed URLs/IP addresses to the MNO for each subscriber for each data 
               
               
                 Provisioning 
                 session. The MNO&#39;s network must be equipped with a policy server that can 
               
               
                   
                 accept dynamic rules in order to provision URLs on the basis indicated above. 
               
               
                 Server-side 
                 Sponsored data service 100 only works for a single mobile network. For data 
               
               
                 Functionality 
                 service 100 to even have a chance of working with multiple mobile networks, 
               
               
                 in Sponsor 
                 each such network would have to implement the sponsoring methodology the 
               
               
                 App 
                 exact same way, or each entity that sponsors data must adapt their interfaces 
               
               
                   
                 with each MNO to meet that MNO&#39;s capabilities. As a consequence, data 
               
               
                   
                 service 100 does not scale beyond use with a single MNO, making the use 
               
               
                   
                 thereof very challenging for entities wishing to sponsor data. 
               
               
                 Sponsor 
                 Each sponsoring entity must be on-boarded with each mobile operator they 
               
               
                 Onboarding 
                 wish to work with on a sponsored plan, which requires negotiating a separate 
               
               
                   
                 deal with each such operator. 
               
               
                 Billing 
                 Each MNO sends a separate bill to the sponsoring entity, requiring the sponsor 
               
               
                   
                 to settle separately with each MNO. And each entity would have to be on- 
               
               
                   
                 boarded and separately provisioned into the MNO&#39;s billing system (billing ID, 
               
               
                   
                 database, reports, record retention, audits, etc.)—a major hardship on the 
               
               
                   
                 MNO. 
               
               
                   
               
             
          
         
       
     
       SUMMARY 
       [0016]    The present invention provides a sponsored data service/system (“SDS”) that avoids some of the drawbacks of the prior art. Unlike the prior art, the SDS is MNO-neutral and exists separate and apart from any given mobile network. 
         [0017]    As noted above, white-listing or “zero-rating” of URLs and IP addresses is currently required to provide sponsored data. This is a primary mechanism for ensuring that subscribers are not charged for the data they consume during a sponsored data session on a mobile network. As indicated in Table 1 above, in the prior art, a sponsoring entity must provide a server-side function that issues a set of URLs/IP addresses to the MNO for each subscriber for each data session. And this must be done for each MNO that the sponsoring entity has a relationship with. It is likely that the methods required will be different for different MNOs. In other words, the prior-art solution is not scalable. 
         [0018]    Unlike the prior art and in accordance with the illustrative embodiment of the invention, the SDS can provide MNOs and sponsoring entities with a single domain name for identifying sponsored data. During on-boarding of an MNO, the SDS provides the top-level domain (TLD) to the MNO; for example, “.TATA_SponData.com”. The MNO then adds a wild-card character(s) to the TLD and encodes it into their packet gateway. The specifics of the wild card are a function of a particular MNO&#39;s system. In the following example, the “asterisk” represents the wild card: *.TATA_SponData.com. 
         [0019]    When a sponsoring entity is on-boarded, they are provided (typically by the SDS) with a unique identifier—a label. The label (as a pre-pend) and the TLD are concatenated; for example: Mr3217.TATA_SponData.com, thus providing a fully qualified domain name (FQDN). The SDS uses the pre-pended label to track which sponsoring entity is associated with the sponsored data usage being monitored (byte counted) via its proxy server. 
         [0020]    Importantly, the MNO does not need any information about the sponsoring entity (i.e., the MNO is “ignorant” of the pre-pend). Once the MNO sees data that has the “sponsored” domain name (the TLD), it knows that any data traffic associated with it is to be zero rated, thus insuring that all access to and from the domain (or any subdomain thereof) is not charged to the subscriber. 
         [0021]    Thus, rather than having to encode countless thousands of addresses to be white-listed, the MNO need only encode a single sponsored domain (TLD). When the MNO&#39;s gateway sees the sponsored domain, it knows to zero-rate the traffic. And because the MNO needs to recognize only the single sponsored domain name, there is no need to update the MNO&#39;s white-list as in the prior art. On-boarding is a one time, single-entry operation. 
         [0022]    For sponsoring entities that use HTTPs data streams or for VPNs, IP addresses are the only means of identifying the source and destination of such streams. Embodiments of the SDS provide a number of dedicated or virtual IP addresses or an entire class of IP addresses that are white-listed by the partnering MNO for such applications. In fact, even for HTTP, use of a virtual IP address (versus a URL) provides protection against hacking. 
         [0023]    There are two basic scenarios for the SDS. In a first scenario, there is a direct, pre-existing business relationship between the MNOs and the sponsoring entities (which the MNO does not wish to alter in any fashion). In this scenario, the SDS helps the MNO settle the bill with sponsoring entity, but the SDS&#39;s presence typically remains hidden from the sponsoring entity. Embodiments of the SDS for use in the first scenario are referred to herein as “hub-based” or identified as “SDS h ”. 
         [0024]    In accordance with the illustrative embodiment of a hub-based SDS, the SDS h  handles data-monitoring (byte counting). To accomplish this data-monitoring functionality, sponsored data traffic passes through the SDS h . The SDS h  tracks the usage of sponsored data and prepares a bill that the MNO will send to the sponsoring entity. Typically, the bill appears on the MNO&#39;s own billing stationary. The MNO then bills the sponsoring entity. The SDS h  charges a fee to the MNO for this service. The MNO sets rates for the sponsoring entities. The SDS h  provides the following core functionality:
       MNOs and sponsoring entities are on-boarded to the SDS h ;   a single, common domain name is provided to all MNOs for whitelisting;   for HTTPs, IP addresses are provided for white-listing;   sponsored data traffic passes through the SDS h  network for monitoring; and   a bill is prepared for the MNO to deliver to the sponsoring entity.       
 
         [0030]    In the second scenario, in which there is often no pre-existing business relationship between an MNO and sponsoring entities (or if there is, the MNO is willing to alter it), the SDS functions as a full service exchange. In such embodiments, referred to herein as “hub and exchange-based” or identified as “SDS h.e. ”, the system provides the following core functionality:
       MNOs and sponsoring entities are on-boarded to the SDS h.e. ;   a single, common domain name is provided to all MNOs for whitelisting;   for HTTPs, IP addresses are provided for white-listing;   sponsored data traffic passes through the SDS h.e.  network for monitoring;   data rates are negotiated with MNOs and provided to the sponsoring entities;   MNO bills the SDS h.e.  for sponsored data usage in its network at the negotiated (wholesale) rates; and   the SDS h.e.  bills sponsoring entities for sponsored data usage based on data counts from monitoring performed by the SDS h.e. .       
 
         [0038]    In some embodiments, the service provided by the SDS is established via registration. Registration may be accomplished, for example, via intelligence (an “App”) placed in a phone, tablet, pad, etc. (hereinafter simply “phone”) provided by the sponsoring entity, or when a subscriber visits the sponsoring entity&#39;s web site. The subscriber can be, for example, an individual or an entity that wants to enable certain things for its employees, etc. 
         [0039]    After registration is complete, the subscriber&#39;s phone will be permitted access to data associated with the whitelisted domain name, at the discretion of the sponsoring entity. This “free” URL (or virtual IP address range) is kept in the MNO&#39;s internet packet gateway as a white-listed URL, as previously discussed. This single static entry serves for all subscribers and all URLs having the whitelisted domain name, as opposed to requiring thousands of unique dynamic entries per subscriber. 
         [0040]    The phone App or browser that is used to access the free URL will be routed to the SDS h.e. . Using the information extracted from the phone App or browser, the SDS can permit access to the sponsored data and track its utilization. 
         [0041]    On a periodic basis, the operator of the SDS h.e.  pays the MNO for the sponsored data tracked through the SDS h.e.  and reconciles billing records with the MNO to ensure that there is no fraud or mischarges. 
         [0042]    A benefit of this sponsored data service is that the MNO always gets paid for the sponsored data usage. And, most importantly, on-boarding of the MNO is a one time, single-entity operation. It is not a complex process that requires entries for hundreds or thousands of potential sponsoring entities, nor does it require any updates. 
         [0043]    In addition, the SDS can apply policy services to the traffic being consumed on behalf of the MNO or the sponsoring entity. The policy can pertain, for example and without limitation, to one or more of the following:
       Customer standing (new, established, premium, etc.)   Customer Location (country, state, town, street corner, etc.)   Time of Day (happy hours, off-hours, busy hours, scheduled, etc.)   Network Conditions (congested, open, etc.)   Content type (video, text, applications, porn, business content, etc.)   Customer age/Parental controls   Operator Network (MNO A vs. MNO B)   Existing Quality of Service or Quality of Experience (from subscriber&#39;s view)   Network type (WiFi, Wireline, Mobile, 3G, 4G)       
 
         [0053]    It is notable that, unlike the prior art, a wireless user who does not have a data plan can be given access to sponsored data. 
         [0054]    In some embodiments, the sponsored data service can work with advertisers who wish to sponsor various data content. Thus, an advertiser can underwrite some or all of the cost of the sponsored data for the sponsoring entity. Sponsorship can also depend on many of the aforementioned parameters. 
         [0055]    Embodiments of the present invention can be used in situations when there are:
       multiple mobile operator networks; and/or   multiple sponsors per ISP; and/or   multiple content providers per sponsor; and/or   multiple content providers across multiple ISPs for a single sponsor; and/or   sponsor(s) directing locally cached content to be inserted; and/or   sponsor(s) directing remotely cached content to be inserted.       
 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0062]      FIG. 1  depicts a sponsored data service in the prior art. 
           [0063]      FIG. 2  depicts an architecture for a sponsored data service/system in accordance with the present teachings. 
           [0064]      FIG. 2A  depicts an embodiment of a sponsored data service/system in accordance with the present teachings. 
           [0065]      FIG. 2B  depicts a method for operating the system of  FIG. 2A . 
           [0066]      FIG. 3A  depicts an embodiment of a sponsored data service/system in accordance with the present teachings. 
           [0067]      FIG. 3B  depicts a method for operating the system of  FIG. 3A . 
           [0068]      FIG. 4  depicts an embodiment of a sponsored data service/system in accordance with the present teachings. 
           [0069]      FIG. 5A  depicts an embodiment of a sponsored data service/system in accordance with the present teachings. 
           [0070]      FIG. 5B  depicts a method for operating the system of  FIG. 5A . 
           [0071]      FIG. 6  depicts an embodiment of a sponsored data service/system in accordance with the present teachings. 
           [0072]      FIG. 7  depicts an embodiment of a sponsored data service/system in accordance with the present teachings. 
           [0073]      FIG. 8  depicts a block flow diagram of a method for accessing sponsored data in accordance with the present teaching. 
       
    
    
     DETAILED DESCRIPTION 
       [0074]    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. 
         [0075]    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&#39;s mobile data plan. 
         [0076]    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&#39;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&#39;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&#39;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&#39;s byte count (reconciled with the SDS&#39;s own byte count), and the SDS bills sponsors based on SDS&#39;s byte counts at its negotiated rates.       
 
         [0083]    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&#39;s web site. After registration is complete, the subscriber&#39;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. 
         [0084]      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. 
         [0085]    As depicted in  FIG. 2 , SDS  200  includes database  220 , on-boarding &amp; authorization subsystem  230 , proxy server and data metering subsystem  240 , billing &amp; 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 . 
         [0086]    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. 
         [0087]    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. 
         [0088]    On-boarding &amp; 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 . 
         [0089]    Proxy &amp; 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  242 A, HTTPs proxy server  242 B, and VPN proxy server  242 C. HTTP proxy server  242 A handles proxying and byte counting for HTTP session, HTTPs proxy server  242 B handles proxying and byte counting for HTTPs sessions, and VPN proxy server  242 C 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. 
         [0090]    Billing &amp; 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. 
         [0091]    Subsystem  260  includes routers, load balancers, a firewall, and other functionality required for interfacing with other networks, such as ISPs or MNOs. 
         [0092]      FIG. 2A  depicts a hub-based sponsored data service/system SDS h    200  in accordance with the present teachings. In this embodiment, SDS 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 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 h    200  can remain “hidden” from the sponsor(s). In some embodiments, SDS h  can “police” access and can redirect or refuse access to sponsored data based on various rules/criteria. 
         [0093]    In  FIG. 2A , SDS h    200  is depicted as being used in conjunction with two MNOs  102 A and  102 B, two ISPs  108 A and  108 B, 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 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 h  and SDS h.e.  discussed herein. 
         [0094]    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. 
         [0095]      FIG. 2B  depicts method  201  for operating SDS 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 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 h    200  provides to the sponsor a “sponsor ID”—a 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&#39;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.
       
 
         [0099]    SDS 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 h    200  as including proxy server  242 A having data counter  244 . 
         [0100]    Referring now to  FIGS. 2A and 2B , access to sponsored data in the context of this embodiment occurs as follows. 
         [0101]    Subscriber  104 A makes a request to control server  270 A, over com links  11 A and  13 A, for sponsored data. In some embodiments, the request is byte-counted by MNO  102 A and will be charged against the subscriber&#39;s data plan. In some other embodiments, the request itself is sponsored and is not charged against the subscriber. 
         [0102]    Assuming the request is granted, control server  270 A returns, to subscriber  104 A over com links  13 A and  11 A, a redirect to proxy server  242 A in SDS h    200 . In some embodiments, this response is byte counted by MNO  102 A and will be charged against the mobile subscriber&#39;s data plan; in some other embodiments, the response is not charged against the subscriber. 
         [0103]    Subscriber makes request for sponsored content to proxy server  242 A over com links  11 A,  17 A (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  242 A makes a request for content to content Server  272 A over com link  15 A. Per task  211 , content server  272 A returns content to proxy server  242 A over com link  15 A. The proxy server then serves the sponsored content to subscriber  104 A over com links  17 A and  11 A, per task  213 . 
         [0104]    Data usage is monitored (byte counted) in data counter  244  in accordance with task  215 . The sponsored content is zero rated by MNO  102 A so there is no charge to subscriber  104 A. 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. 
         [0105]    In accordance with task  217 , billing and reporting subsystem  250  of SDS h    200  prepares an invoice for MNO  102 A reflecting usage of sponsored data and transmits it, over com link  21 A, to GGSN  106 A in MNO  102 A. The bill is typically prepared on the MNO&#39;s billing stationary and is then sent from MNO  102 A to Sponsor A. 
         [0106]    SDS h    200  interacts with subscriber  104 B, MNO  102 B, ISP  108 B, and sponsor B in the same fashion as discussed above with respect to subscriber  104 A, MNO  102 A, ISP  108 A, and sponsor A to provide subscriber  104 B with access to sponsored data. 
         [0107]      FIG. 3A  depicts a hub-and-exchange based sponsored data service/system SDS h.e.    300  in accordance with the present teachings.  FIG. 3B  depicts method  301  for operating SDS h.e.    300 . Although the architecture of SDS h.e.    300  (and that of other embodiments of SDS h.e.  depicted later in this specification) is mostly the same as that of the illustrative embodiment of SDS h , the mode of operation is somewhat different. Chief among such differences is that in embodiments of the SDS h.e. , the operator of the SDS h.e.  negotiates with the MNO(s) for the data usage and then charges the sponsors directly at rates that the SDS h.e.  negotiates with the sponsors. In contrast, the SDS 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 h  charges the MNO a fee for its services. 
         [0108]    In  FIG. 3A , SDS h.e.    300  is used in conjunction with two MNOs  102 A and  102 B, two ISPs  108 A and  108 B, and two sponsors A and B. Sponsor A has control server  270 A and content server  272 A. Sponsor B has control server  270 B and content server  272 B. Access to the information of sponsor A is via ISP  108 A and access to the information of sponsor B is via ISP  108 B. 
         [0109]    Referring now to  FIGS. 3A and 3B , as per method  301 , SDS 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 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. 
         [0110]    Access to sponsored data in the context of this embodiment occurs as follows. 
         [0111]    Subscriber  104 A makes a request to control server  270 A, over com links  11 A and  13 A, for sponsored data. In some embodiments, the request is byte-counted by MNO  102 A and will be charged against the subscriber&#39;s data plan. In some other embodiments, the request itself is sponsored and is not charged against the subscriber. 
         [0112]    Assuming the request is granted, control server  270 A returns, to subscriber  104 A over com links  13 A and  11 A, a redirect to proxy server  242 A in SDS h.e.    300 . In some embodiments, this response is byte counted by MNO  102 A and will be charged against the mobile subscriber&#39;s data plan; in some other embodiments, the response is not charged against the subscriber. 
         [0113]    Subscriber makes request for sponsored content to proxy server  242 A over com links  11 A,  17 A (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  242 A makes a request for content to content server  272 A over com link  15 A. Per task  211 , content server  272 A returns content to proxy server  242 A over com link  15 A. The proxy server then serves the sponsored content to subscriber  104 A over com links  17 A and  11 A, per task  213 . 
         [0114]    Data usage is monitored (byte counted) in data counter  244  in accordance with task  215 . The sponsored content is zero rated by MNO  102 A so there is no charge to subscriber  104 A. 
         [0115]    Data usage is reported to billing and reporting subsystem  250  over com link  19 . A bill is prepared by SDS 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. 
         [0116]    SDS h.e.    300  interacts with subscriber  104 B, MNO  102 B, ISP  108 B, and sponsor B in the same fashion as discussed above with respect to subscriber  104 A, MNO  102 A, ISP  108 A, and sponsor A to provide subscriber  104 B with access to sponsored data. 
         [0117]      FIG. 4  depicts SDS h.e.    300  accessing sponsored content from a distributed content delivery network. 
         [0118]    In  FIG. 4 , SDS h.e.    300  is used in conjunction with two MNOs  102 A and  102 B, two ISPs  108 A and  108 B, two sponsors A (control server  270 A and content server  272 A) and B (control server  270 B and content server  272 B), 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. 
         [0119]    CDN  474  includes a plurality of replica servers, four of which (i.e.,  476 A through  476 D) are depicted in  FIG. 4 . 
         [0120]    The method by which sponsored data is obtained is similar to that depicted in  FIG. 3B . However, rather than proxy server  242 A receiving content from content server  272 A, it receives it from replica server  476 A over com link  29 A, after the replica server receives the content from content server  272 A over com link  27 A (if the replica server does not have the content in its data cache). 
         [0121]    Replica server  476 C is also depicted as providing content to proxy server  242 A (over com link  29 C). This is simply to illustrate that the content may be provided from multiple replica servers. 
         [0122]    SDS h.e.    300  interacts with subscriber  104 B, MNO  102 B, ISP  108 B, sponsor B, and CDN  474  in the same fashion as discussed above with respect to subscriber  104 A, MNO  102 A, ISP  108 A, and sponsor A to provide subscriber  104 B with access to sponsored data. 
         [0123]      FIG. 5A  depicts a further embodiment of a hub-and-exchange sponsored data service/system SDS h.e.    500  in accordance with the present teachings. In addition to providing the functionality of SDS h.e.    300 , SDS 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. 
         [0124]      FIG. 5B  depicts method  501  for operating SDS h.e.    500 . As is typical for embodiments of the invention, SDS h.e.    500  provides onboarding of MNOs and Sponsors, monitoring (byte counting) of sponsored data sessions, and billing services. 
         [0125]    In  FIG. 5A , SDS h.e.    500  is used in conjunction with two MNOs  102 A and  102 B, two ISPs  108 A and  108 B, two sponsors A (control server  270 A and content server  272 A) and B (control server  270 B and content server  272 B). As previously indicated, in addition to providing the functionality of SDS h.e.    300 , SDS h.e.    500  functions as a content delivery network in this embodiment. 
         [0126]    Referring now to  FIGS. 5A and 5B , as per method  501 , SDS 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. 
         [0127]    Mobile subscriber makes a request to control server  270 A, over com links  11 A and  13 A, for sponsored data. In some embodiments, the request is byte-counted by MNO  102 A and will be charged against the subscriber&#39;s data plan. In some other embodiments, the request itself is sponsored and is not charged against the subscriber. 
         [0128]    Assuming the request is granted, control server  270 A returns, to subscriber  104 A over com links  13 A and  11 A, a redirect to replica server  578 A in SDS h.e.    500 . In some embodiments, this response is byte counted by MNO  102 A and will be charged against the mobile subscriber&#39;s data plan; in some other embodiments, the response is not charged against the subscriber. 
         [0129]    Subscriber  104 A makes request for sponsored content to Replica Server  578 A over com links  11 A and  17 A (see task  507 ). This request is zero rated by MNO and byte counted by data counter  244  in replica server  578 A. Query, at task  509 , whether the sponsored content is available in the cache of replica server  578 A. If not, at task  511 , replica server  578 A fetches the sponsored content from content server  272 A over corn link  15 A. 
         [0130]    At task  513 , replica server  578 A serves the sponsored content to subscriber  104 A over corn links  17 A and  11 A, per task  513 . 
         [0131]    Data usage is monitored (byte counted) in data counter  244  in accordance with task  515 . The sponsored content is zero rated by MNO  102 A so there is no charge to subscriber  104 A. 
         [0132]    Data usage is reported to billing and reporting subsystem  250  over corn link  19 A. A bill is prepared by SDS 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. 
         [0133]    SDS h.e.    500  interacts with subscriber  104 B, MNO  102 B, ISP  108 B, and sponsor B in the same fashion as discussed above with respect to subscriber  104 A, MNO  102 A, ISP  108 A, and sponsor A to provide subscriber  104 B with access to sponsored data. 
         [0134]      FIG. 6  depicts yet a further embodiment of a hub-and-exchange sponsored data service/system SDS h.e.    600  in accordance with the present teachings. 
         [0135]    In  FIG. 6 , SDS h.e.    600  is used in conjunction with two MNOs  102 A and  102 B, two ISPs  108 A and  108 B, two sponsors A (control server  270 A and secure content server  680 A) and B (control server  270 B and content server  680 B). 
         [0136]    In this embodiment, SDS 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. 
         [0137]    In accordance with some embodiments of the present invention, this problem is addressed by having secure proxy server  242 B terminate the original HTTPS session, then originate a new secure session back to the sponsored data origin (i.e., the sponsor&#39;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 h.e.    300  depicted in  FIGS. 3A and 3B , with the exception of secure proxy server  242 B replacing proxy server  242 A. 
         [0138]    A security certificate management function (as part of the asset management functionality) is required since the data is arriving at SDS 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  242 B. The proxy server then forwards the data to the sponsored data origin or the subscriber depending on the direction of the flow. 
         [0139]    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. 
         [0140]    It is notable that to provide certain types of sessions, such as a “shopping cart,” an additional requirement on SDS 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. 
         [0141]    SDS h.e.    600  is operated in the same manner as depicted in  FIG. 3B  for SDS h.e.    300 . 
         [0142]      FIG. 7  depicts SDS h.e.    700 , which includes VPN proxy server  242 C. Unlike the previous embodiment with HTTPs proxy server  242 B, in a VPN, the secure stream is not terminated. In this embodiment, SDS h.e.    700  effectively functions as a transparent proxy, merely forwarding data and byte count. The VPN may be required for certain B2E applications. 
         [0143]    There are basically two application components —client side and server side- to a sponsored data session. 
         [0144]    On the client side is a software application running on the mobile user&#39;s phone. In some embodiments, this is mobile App; in some others, it&#39;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&#39;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. 
         [0145]      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&#39;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. 
         [0146]    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. 
         [0147]    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. 
         [0148]    At task  813 , the mobile user loads the redirect page. The content may be delivered from the origin (i.e., the sponsor&#39;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. 
         [0149]    At task  815 , the sponsored content is streamed (from source or cache) to the App on the subscriber&#39;s phone. The App renders, for example, video in the phone&#39;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. 
         [0150]    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.