Toll-free data simulation via an HTTP connect tunnel

Patent metadata

Field	Value
Publication number	US-10645084-B2
Application number	US-201615378725-A
Country	US
Kind code	B2
Filing date	Dec 14, 2016
Priority date	Dec 14, 2016
Publication date	May 5, 2020
Grant date	May 5, 2020

Abstract

A device may receive, from a user device, a hypertext transfer protocol (HTTP) CONNECT request that includes a uniform resource locator (URL). The device may determine, using a data structure, whether the URL is a sponsored URL or a non-sponsored URL. The data structure may include one or more sponsored URLs associated with a toll-free data service campaign. The device may establish an HTTP CONNECT tunnel for transferring traffic, associated with the URL, between the user device and another device. The device may monitor data use, associated with the HTTP CONNECT tunnel, based on determining whether the URL is a sponsored URL or a non-sponsored URL. The device may generate a traffic information record based on monitoring the data use, and the device may provide the traffic information record to the user device.

First claim

What is claimed is:

1. A device, comprising:
a memory; and
one or more processors to:
receive, from a user device associated with a content provider and for a data use simulation, an authorization request that includes a token associated with a toll-free data service campaign;
obtain an authorization response based on providing the authorization request to an authorization device,
the authorization response including one or more sponsored URLs associated with the toll-free data service campaign;

store the one or more sponsored URLs in a data structure based on the authorization response;
send an acknowledgement to the user device indicating a status of the authorization request;
receive, from the user device and as part of the data use simulation to test data use, a hypertext transfer protocol (HTTP) CONNECT request that includes a uniform resource locator (URL);
determine, using the data structure, whether the URL is a sponsored URL, associated with a toll-free data service campaign, or a non-sponsored URL,
the data structure including the one or more sponsored URLs, and
the URL being a sponsored URL when the URL includes a signature appended to an end of the URL;

establish an HTTP CONNECT tunnel for transferring traffic, associated with the URL, between the user device and the content provider in a restricted operating system environment to verify accuracy of the toll-free data service campaign;
analyze data use, associated with the HTTP CONNECT tunnel, based on determining whether the URL is a sponsored URL or a non-sponsored URL;
generate a traffic information record based on analyzing the data use;
provide the traffic information record to the user device,
the traffic information record being used to verify whether the content provider is correctly charged for the data use by the user device;

generate, based on the data use simulation, a model to determine that the toll-free data service campaign includes one or more errors; and
automatically send error correction information to one or more devices that store information associated with the toll-free data service campaign based on determining that the toll-free data service campaign includes the one or more errors.

2. The device of claim 1 , where the URL identifies a domain name or a host name associated with the toll-free data service campaign.

3. The device of claim 1 , where the one or more processors, when determining whether the URL is a sponsored URL or a non-sponsored URL, are to:
compare the URL and the one or more sponsored URLs stored by the data structure; and
determine whether the URL is a sponsored URL or a non-sponsored URL based on a result of the comparing.

4. The device of claim 1 , where the one or more processors, when determining whether the URL is a sponsored URL or a non-sponsored URL, are to:
determine that the URL is a sponsored URL; and
where the one or more processors, when analyzing data use associated with the HTTP CONNECT tunnel, are to:
count a quantity of bytes of traffic that pass through the HTTP CONNECT tunnel;

and
where the one or more processors, when generating the traffic information record, are to:
indicate the quantity of bytes as sponsored data in the traffic information record.

5. The device of claim 1 , where the one or more processors, when determining whether the URL is a sponsored URL or a non-sponsored URL, are to:
determine that the URL is a non-sponsored URL; and
where the one or more processors, when analyzing data use associated with the HTTP CONNECT tunnel, are to:
count a quantity of bytes of traffic that pass through the HTTP CONNECT tunnel;

and
where the one or more processors, when generating the traffic information record, are to:
indicate the quantity of bytes as non-sponsored data in the traffic information record.

6. The device of claim 5 , where the one or more processors, when generating the traffic information record associated with the HTTP CONNECT tunnel, are further to:
generate a different traffic information record associated with a different HTTP CONNECT tunnel;
aggregate byte count information from the traffic information record and the different traffic information record; and
indicate the aggregate byte count information in a total traffic information record.

7. The device of claim 1 , where the one or more processors are further to:
determine whether the authorization response includes a success indicator; and
where the one or more processors, when storing one or more sponsored URLs in the data structure, are to:
store the one or more sponsored URLs in the data structure based on determining that the authorization response includes the success indicator.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
receive, from a user device associated with a content provider and for a data use simulation, an authorization request that includes a token associated with a toll-free data service campaign;
obtain an authorization response based on providing the authorization request to an authorization device,
the authorization response including one or more sponsored URLs associated with the toll-free data service campaign; and

store the one or more sponsored URLs in a data structure based on the authorization response;
send an acknowledgement to the user device indicating a status of the authorization request;
receive, from the user device and as part of the data use simulation to test data use, a hypertext transfer protocol (HTTP) CONNECT request that includes a uniform resource locator (URL);
determine, using the data structure, whether the URL is a sponsored URL or a non-sponsored URL,
the data structure including the one or more sponsored URLs, and
the URL being a sponsored URL when the URL includes a signature appended to an end of the URL;

establish an HTTP CONNECT tunnel for transferring traffic, associated with the URL, between the user device and the content provider in a restricted operating system environment to verify accuracy of the toll-free data service campaign;
monitor data use, associated with the HTTP CONNECT tunnel, based on determining whether the URL is a sponsored URL or a non-sponsored URL;
generate a traffic information record based on monitoring the data use;
provide the traffic information record to the user device,
the traffic information record being used to verify whether the content provider is correctly charged for the data use by the user device;
generate, based on the data use simulation, a model to determine that the toll-free data service campaign includes one or more errors; and
automatically send error correction information to one or more devices that store information associated with the toll-free data service campaign based on determining that the toll-free data service campaign includes the one or more errors.

9. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, that cause the one or more processors to determine whether the URL is a sponsored URL or a non-sponsored URL, cause the one or more processors to:
determine that the URL matches a URL of the one or more sponsored URLs stored by the data structure; and
determine that the URL is a sponsored URL based on determining that the URL matches the URL of the one or more sponsored URLs stored by the data structure.

10. The non-transitory computer-readable medium of claim 9 , where the one or more instructions, that cause the one or more processors to monitor data use associated with the HTTP CONNECT tunnel, cause the one

Assignees

• Verizon Patent & Licensing Inc

Inventors

• AKMAL Mohammad Zohaib
• Huang Jian
• Bongu Huma Shankar Rao Fnu

Classifications

• H04M15/84

  Types of notifications · CPC title

• H04M15/41

  Billing record details, i.e. parameters, identifiers, structure of call data record [CDR] · CPC title

• H04M15/83

  Notification aspects · CPC title

• H04M15/08

  Metering calls to called party {, i.e. B-party charged for the communication} · CPC title

• H04L12/1475

  the splitting involving a third party · CPC title