Systems, methods, and computer programs for detecting carrier-controlled requests for a web site

• US 8,539,101 B2
• Filed: 09/14/2011
• Issued: 09/17/2013
• Est. Priority Date: 08/12/2008
• Status: Active Grant

• Current Assignee: Disney Enterprises Incorporated (The Walt Disney Company)
• Original Assignee: Disney Enterprises Incorporated (The Walt Disney Company)
• Inventors: Christianson, Ryan D., Kehle, John A.
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): Williams, Clayton R
• Application Number:
  US13/232,239
• Publication Number:
  US 20120042008A1
• Time in Patent Office: 734 Days
• Field of Search: None
• US Class Current: 709/238
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

Various embodiments of systems, methods, and computers are disclosed for detecting and/or managing carrier-controlled requests for a web site. One embodiment is a method system for providing a web site to mobile communication devices. The system comprises a mobile communication device and a server. The mobile communication device is configured to communicate with the server via a communication network and comprises a carrier-controlled user interface for accessing a web site. The server is configured to provide the web site to the mobile communication device and comprises an on-deck detection system and an on-deck/off-deck management system embodied in a memory and executed by a processor. The on-deck detection system detects requests for the web site from the carrier-controlled user interface, and the on-deck/off-deck management system manages the requests.

Claims

1. A method to minimize a number of requests to a web site from a mobile communication device fulfilled using on-deck browsing sessions, the method comprising:

providing a user interface on the mobile communication device, the user interface including a first link to a web site of an associated content provider, the first link specifying a first URL to the web site, wherein the user interface is provided by a first carrier, of a plurality of carriers;

receiving a first request for the web site from the mobile communication device, wherein the first request specifies the first URL;

upon determining that the first request originated from the user interface and specifies the first URL;

accessing carrier-specific data specifying, for the first carrier, a mapping between the first URL and a second URL to the web site;

redirecting the first request to the second URL; and

presenting the web site to the mobile communication device in an on-deck browsing session consistent with terms of a relationship between the first carrier and the associated content provider;

after the on-deck browsing session, receiving a second request for the web site from the mobile communication device, wherein the second request specifies the second URL; and

upon determining that the second request originated from a source other than the user interface and specifies the second URL, presenting the web site to the mobile communication device in an off-deck browsing session without regard to the terms of the relationship between the first carrier and the associated content provider to reduce the number of on-deck browsing sessions.

2. The method of claim 1, wherein the first URL further specifies a carrier identifier for the first carrier, wherein the carrier-specific data further specifies:

(i) carrier identifiers, and (ii) mappings for each of the plurality of carriers.

3. The method of claim 2, wherein determining that the first request originated from the user interface further comprises identifying the carrier identifier for the first carrier in the first URL.

4. The method of claim 3, wherein the on-deck browsing session is presented according to a presentation scheme associated with the first carrier.

5. The method of claim 4, wherein presenting the web site to the mobile communication device in the off-deck browsing session comprises presenting the web site according to a different presentation scheme.

6. The method of claim 5, further comprising providing a cookie to the mobile communication device during the first browsing session, and wherein determining that the second request originated from the source other than the user interface comprises identifying the cookie.

7. The method of claim 6, wherein the user interface comprises one of a menu associated with an electronic app store, an in-app advertisement, and a carrier deck.

8. A system for providing a web site to mobile communication devices, the system comprising:

one or more computer processors; and

a memory containing a program, which when executed by the one or more computer processors, performs an operation to minimize a number of requests to a web site from a mobile communication device fulfilled using on-deck browsing sessions, the operation comprising;

providing a user interface on the mobile communication device, the user interface including a first link to a web site of an associated content provider, the first link specifying a first URL to the web site, wherein the user interface is provided by a first carrier, of a plurality of carriers;

receiving a first request for the web site from the mobile communication device, wherein the first request specifies the first URL;

upon determining that the first request originated from the user interface and specifies the first URL;

accessing carrier-specific data specifying, for the first carrier, a mapping between the first URL and a second URL to the web site;

redirecting the first request to the second URL; and

presenting the web site to the mobile communication device in an on-deck browsing session consistent with terms of a relationship between the first carrier and the associated content provider;

receiving, after the on-deck browsing session, a second request for the web site from the mobile communication device, wherein the second request specifies the second URL; and

upon determining that the second request originated from a source other than the user interface and specifies the second URL, presenting the web site to the mobile communication device in an off-deck browsing session provider to reduce the number of on-deck browsing session, wherein the web site is presented with a different presentation scheme.

9. The system of claim 8, wherein the second request is initiated by the mobile communication device from one or more of a browser, a bookmark, a user input, and a search engine results page.

10. The system of claim 9, wherein the first URL further specifies a carrier identifier for the first carrier, wherein the carrier-specific data further specifies:

(i) carrier identifiers, and (ii) mappings for each of the plurality of carriers.

11. The system of claim 10, wherein the user interface comprises one of a carrier deck, an electronic app store, and an in-app link in an app downloaded from the electronic app store.

12. A computer program embodied in a non-transitory computer-readable medium to minimize a number of requests to a web site from a mobile communication device fulfilled using on-deck browsing sessions, the computer program comprising:

providing a user interface on the mobile communication device, the user interface including a first link to a web site of an associated content provider, the first link specifying a first URL to the web site, wherein the user interface is provided by a first carrier, of a plurality of carriers;

receiving a first request for a web site from the mobile communication device, wherein the first request specifies the first URL;

upon determining that the first request originated from the user interface and specifies the first URL;

accessing carrier-specific data specifying, for the first carrier, a mapping between the first URL and a second URL to the web site;

redirecting the first request to the second URL; and

presenting the web site as an on-deck browsing session;

receiving, after the first request, a second request for the web site from the mobile communication device, wherein the second request is initiated from a source other than the carrier-controlled user interface and specifies the second URL; and

upon determining that the second request originated from the source other than the user interface and specifies the second URL, presenting the web site to the mobile communication device in an off-deck browsing session without regard to the terms of the relationship between the first carrier and the associated content provider to reduce the number of on-deck browsing sessions.

13. The computer program of claim 12, wherein the second request is initiated by the mobile communication device from one or more of a browser, a bookmark, a user input, and a search engine results page.

14. The computer program of claim 13, wherein the first URL further specifies a carrier identifier for the first carrier, wherein the carrier-specific data further specifies:

(i) carrier identifiers, and (ii) mappings for each of the plurality of carriers.

15. The computer program of claim 14, wherein the user interface comprises one of a carrier deck, an electronic app store, and an app provided via the electronic app store, and wherein the user interface further comprises providing a cookie to the mobile communication device during the on-deck browsing session, and wherein determining that the second request originated from the source other than the user interface comprises identifying the cookie.