Adding a unique identification header to non-operator network communication

Patent metadata

Field	Value
Publication number	US-9848309-B2
Application number	US-201615395854-A
Country	US
Kind code	B2
Filing date	Dec 30, 2016
Priority date	Jan 21, 2015
Publication date	Dec 19, 2017
Grant date	Dec 19, 2017

Abstract

A device may receive an identifier for a subscriber of a first network. The subscriber may be associated with the device. The device may store the identifier and receive a request for content. The device may generate a modified request by adding the identifier to the request. The device may send the modified request using a network communication. The network communication may communicate via a second network without using the first network, and the first network may be different than the second network. The device may receive the content and targeted content based on the modified request. The targeted content may be targeted to the subscriber based on the identifier.

First claim

What is claimed is:

1. A computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to:
receive an identifier for a subscriber of an operator network,
the subscriber being associated with the device;

store the identifier;
receive a request for content;
generate a modified request by adding the identifier to the request;
send the modified request to a server via a first mode of network communication,
the first mode of network communication communicating without using the operator network, and
the device being capable of communicating using a second mode of network communication that communicates with the server via the operator network; and

receive the content and targeted content based on the modified request,
the targeted content being targeted to the subscriber and being selected based on the identifier.

2. The computer-readable medium of claim 1 , where the one or more instructions, that cause the one or more processors to generate the modified request, further cause the one or more processors to:
generate the modified request based on an address included in the request,
the address indicating a destination to which the request for the content is to be sent.

3. The computer-readable medium of claim 1 , where the one or more instructions, that cause the one or more processors to generate the modified request, further cause the one or more processors to:
generate the modified request based on a type of message indicated by the request for the content.

4. The computer-readable medium of claim 1 , where the one or more instructions, that cause the one or more processors to generate the modified request, further cause the one or more processors to:
generate the modified request based on an application that generated the request for the content.

5. The computer-readable medium of claim 1 , where the one or more instructions, that cause the one or more processors to generate the modified request, further cause the one or more processors to:
generate the modified request based on the request for the content being generated based on a user input.

6. The computer-readable medium of claim 1 , where the one or more instructions, that cause the one or more processors to generate the modified request, further cause the one or more processors to:
generate the modified request based on the device being in the first mode of network communication.

7. The computer-readable medium of claim 1 , where the identifier is associated with the subscriber without identifying an identity of the subscriber.

8. A method comprising:
receiving, by a device, an identifier for a subscriber of an operator network,
the subscriber being associated with the device;

storing, by the device, the identifier;
receiving, by the device, a request for content;
generating, by the device, a modified request by adding the identifier to the request;
sending, by the device and using a network communication, the modified request to a server,
the network communication communicating independent of the operator network;

receiving, by the device and from the server, the content and targeted content based on the modified request,
the targeted content being targeted to the subscriber and being selected based on the identifier.

9. The method of claim 8 , further comprising:
providing the request for content to a proxy application based on the device being in a mode for communicating using the network communication, and
where generating the modified request includes the proxy application adding the identifier to the content request.

10. The method of claim 9 , where storing the identifier further comprises:
storing the identifier to be accessible only by the proxy application.

11. The method of claim 8 , where the identifier is generated based on a mobile device identifier associated with the subscriber.

12. The method of claim 8 , further comprising:
sending an identifier request for the identifier,
the identifier request being sent independent of and prior to receiving the request for the content.

13. The method of claim 8 , where generating the modified request further comprises:
determining a communication mode of the device; and
selectively generating the modified request based on the communication mode.

14. A device, comprising:
one or more processors to:
receive an identifier for a subscriber of an operator network,
the subscriber being associated with the device;

store the identifier;
receive a request for content;
generate a modified request by adding the identifier to the request;
send the modified request to a server via a first mode of network communication,
the first mode of network communication communicating independent of the operator network,
the device being capable of communicating using a second mode of network communication that communicates with the server via the operator network; and

receive the content and targeted content based on the modified request,
the targeted content being targeted to the subscriber based on the identifier.

15. The device of claim 14 , where the one or more processors are further to:
send an identifier request to the operator network that requests the identifier; and
where the one or more processors, when receiving the identifier, are further to:
receive the identifier via the operator network based on sending the identifier request.

16. The device of claim 15 , where the one or more processors, when sending the identifier request, are further to:
send the identifier request at a scheduled time that is based on how often the identifier for the subscriber is updated by the operator network.

17. The device of claim 15 , where the one or more processors, when sending the identifier request, are further to:
send the identifier request based on the device connecting to the operator network.

18. The device of claim 14 , where the identifier is generated based on a key and information associated with the subscriber.

19. The device of claim 14 , where the one or more processors are further to:
determine that the device is in the first mode of network communication that communicates independent of the operator network, and
where the one or more processors, when generating the modified request, are further to:
add the identifier to the request based on the device being determined to be in the first mode of network communication that communicates independent of the operator network.

20. The device of claim 14 , where the one or more processors are further to:
provide the content and the targeted content for presentation.

Assignees

• Verizon Patent & Licensing Inc

Inventors

• Libonate Brian
• Morrison Stephen D
• Gupta Gaurav

Classifications

• H04W4/206 Primary

  Electricity · mapped topic

• H04W8/18

  Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data · CPC title

• H04L67/00

  Network arrangements or protocols for supporting network services or applications (user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00) · CPC title

• H04W88/06

  adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals · CPC title

• H04W8/22 Primary

  Processing or transfer of terminal data, e.g. status or physical capabilities · CPC title