Application programming interface gateway for sponsored data services

Patent metadata

Field	Value
Publication number	US-9596606-B1
Application number	US-201615137119-A
Country	US
Kind code	B1
Filing date	Apr 25, 2016
Priority date	Apr 25, 2016
Publication date	Mar 14, 2017
Grant date	Mar 14, 2017

Abstract

A method to facilitate secure access to a sponsored data service (SDS) through an application programming interface gateway includes providing an access token to a content provider device, where the access token authorizes the content provider device to receive sponsored data services (SDSs). The method also includes receiving a first request for an SDS resource from the content provider device; generating a first timestamp associated with the first request; determining a destination for the first request, where the destination specifies a network address corresponding to an SDS resource device; forwarding the first request to the SDS resource device based on the determined destination; receiving a first response from the SDS resource device corresponding to the first request; generating a second timestamp associated with the first response; and forwarding the first response, along with the first timestamp and the second timestamp, to the content provider device.

First claim

What is claimed is:

1. A method, comprising:
providing, from an application programming interface (API) gateway device, an access token to a content provider device, wherein the access token authorizes the content provider device to access resources for sponsored data services (SDSs);
receiving, at the API gateway device, a first request for an SDS resource from the content provider device;
generating, at the API gateway device, a first timestamp associated with the first request;
determining, at the API gateway device, a destination for the first request, wherein the destination specifies a network address corresponding to an SDS resource device;
forwarding, from the API gateway device, the first request to the SDS resource device based on the determined destination;
receiving, at the API gateway device, a first response from the SDS resource device corresponding to the first request;
generating, at the API gateway device, a second timestamp associated with the first response; and
forwarding, from the API gateway device, the first response, along with the first timestamp and the second timestamp, to the content provider device.

2. The method of claim 1 , wherein providing the access token to the content provider device, further comprises:
receiving, at the API gateway device, an authentication request from the content provider device, wherein the authentication request includes credentials of the content provider device;
generating, at the API gateway device, a third timestamp associated with the authentication request;
determining, at the API gateway device, that an authentication device is a destination for the authentication request;
forwarding, from the API gateway device, the authentication request and the credentials of the content provider device to the authentication device;
receiving, at the API gateway device, the access token, wherein the access token is based on the credentials of the content provider device;
generating, at the API gateway device, a fourth timestamp associated with the authentication request; and
forwarding, from the API gateway device, the access token, along with the third timestamp and the fourth timestamp, to the content provider device.

3. The method of claim 2 , further comprising:
caching, at the API gateway device, the access token.

4. The method of claim 2 , wherein receiving the authentication request further comprises:
receiving credentials which include a client identifier and a client secret.

5. The method of claim 1 ,
wherein the receiving the first request further comprises receiving a session timing record manager (STRM) call from the content provider device, wherein the STRM call includes the access token,
wherein the generating the first timestamp further comprises generating the first timestamp associated with the STRM call, and the method further comprises:
determining, at the API gateway device, whether an authentication header associated with the STRM call is valid.

6. The method of claim 5 , further comprising:
sending a request to an authentication device to validate the access token in response to determining that the authentication header is valid.

7. The method of claim 6 , wherein in response to the request to the authentication device to validate the access token, the method further comprises:
receiving a confirmation from the authentication device that the access token is valid;
wherein the determining the destination for the first request further comprises determining the STRM as the destination;
wherein the forwarding the first request further comprises forwarding the STRM call along with the first timestamp and the validated access token to the STRM;
wherein the receiving the first response further comprises receiving an acknowledgement from the STRM corresponding to the STRM call;
wherein the generating a second timestamp further comprises generating the second timestamp in response to the acknowledgement from the STRM; and
wherein the forwarding the first response further comprises forwarding the acknowledgment from the STRM, along with the first timestamp and the second timestamp, to the content provider device.

8. The method of claim 6 , wherein in response to the request to the authentication device to validate the access token, the method further comprises:
receiving an error message indicating the access token is invalid; and
forwarding the error message to the content provider device.

9. The method of claim 5 , wherein upon determining that the authentication header is not valid, the method further comprises:
receiving an error message indicating the authentication header is invalid; and
forwarding the error message to the content provider device.

10. A device, comprising:
an interface configured to communicate with a network;
a memory configured to store instructions; and
a processor, coupled to the interface and the memory, wherein the stored instructions, when executed by the processor, cause the processor to:
provide an access token to a content provider device, wherein the access token authorizes the content provider device to access resources for sponsored data services (SDSs),
receive a first request for an SDS resource from the content provider device,
generate a first timestamp associated with the first request,
determine a destination for the first request, wherein the destination specifies a network address corresponding to an SDS resource device,
forward the first request to the SDS resource device based on the determined destination,
receive a first response from the SDS resource device corresponding to the first request,
generate a second timestamp associated with the first response, and
forward the first response, along with the first timestamp and the second timestamp, to the content provider device.

11. The device of claim 10 , wherein the instructions to provide the access token to the content provider device comprise instructions further causing the processor to:
receive an authentication request from the content provider device, wherein the authentication request includes credentials of the content provider device,
generate a third timestamp associated with the authentication request,
determine that an authentication device is a destination for the authentication request,
forward the authentication request and the credentials of the content provider device to the authentication device,
receive the access token, wherein the access token is based on the credentials of the content provider device,
generate a fourth timestamp associated with the authentication request, and
forward the access token, along with the third timestamp and the fourth timestamp, to the content provider device.

12. The device of claim 11 , wherein the instructions further cause the processor to:
cache the access token.

13. The device of claim 11 , wherein the instructions to receive the authentication request further cause the processor to:
receive credentials which include a client identifier and a client secret.

14. The device of claim 10 ,
wherein the instructions to receive the first request cause the processor to: receive a session timing record manager (STRM) call from the content provider device, wherein the STRM call includes the access token,
wherein the instructions to generate the first timestamp further cause the processor to: generate the first timestamp associated with the STRM call, and
the memory stores instructions further causing the processor to:
determine whether an authentication header associated with the STRM call is valid.

15. The device of

Assignees

• Verizon Patent & Licensing Inc

Inventors

• Palmer Okeno
• Ren Dahai
• Saint-Hilaire Hector
• Wu Shuai

Classifications

• H04W12/08 Primary

  Access security · CPC title

• G06Q20/385 Primary

  using an alias or single-use codes · CPC title

• H04W88/16

  Gateway arrangements · CPC title

• H04L63/0846

  using time-dependent-passwords, e.g. periodically changing passwords · CPC title

• H04W12/06

  Authentication · CPC title