Adding a unique identification header to non-operator network communication

Patent metadata

Field	Value
Publication number	US-9602992-B2
Application number	US-201514601490-A
Country	US
Kind code	B2
Filing date	Jan 21, 2015
Priority date	Jan 21, 2015
Publication date	Mar 21, 2017
Grant date	Mar 21, 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 device, comprising:
one or more processors to:
receive, from a first network, an identifier for a subscriber of the first 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 using a network communication,
the network communication communicating via a second network without using the first network,
the first network being different than the second 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.

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

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

4. The device of claim 2 , where the one or more processors, when sending the identifier request, are to:
send the identifier request based on the device connecting to the first network.

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

6. The device of claim 1 , where the one or more processors are further to:
determine that the device is in a mode that communicates using the network communication, and
where the one or more processors, when generating the modified request, are to:
add the identifier to the request for content based on the device being determined to be in the mode that communicates using the network communication.

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

8. A non-transitory 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, from a first network, an identifier for a subscriber of the first 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 using a network communication,
the network communication communicating via a second network without using the first network,
the first network being different than the second 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.

9. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, when executed by the one or more processors of the device, further cause the one or more processors to:
send an identifier request to the first network that requests the identifier; and
where the one or more instructions, that cause the one or more processors to receive the identifier, cause the one or more processors to:
receive the identifier via the first network based on sending the identifier request.

10. The non-transitory computer-readable medium of claim 9 , where the one or more instructions, that cause the one or more processors to send the identifier request, cause the one or more processors to:
send the identifier request at a scheduled time that is based on how often the identifier for the subscriber is updated by the first network.

11. The non-transitory computer-readable medium of claim 9 , where the one or more instructions, that cause the one or more processors to send the identifier request, cause the one or more processors to:
send the identifier request based on the device connecting to the first network.

12. The non-transitory computer-readable medium of claim 8 , where the identifier is generated based on a key and information associated with the subscriber.

13. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, when executed by the one or more processors of the device, cause the one or more processors to:
determine that the device is in a mode that communicates using the network communication, and
where the one or more instructions, that cause the one or processors to generate the modified request, cause the one or more processors to:
add the identifier to the request for content based on the device being determined to be in the mode that communicates using the network communication.

14. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, when executed by the one or more processors of the device, further cause the one or more processors to:
provide the content and the targeted content for presentation.

15. A method, comprising:
receiving, by a device, from a first network, an identifier for a subscriber of the first 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, the modified request using a network communication,
the network communication communicating via a second network without using the first network,
the first network being different than the second network; and

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

16. The method of claim 15 , further comprising:
sending an identifier request to the first network that requests the identifier, and
where receiving the identifier comprises:
receiving the identifier via the first network based on sending the identifier request.

17. The method of claim 16 , where sending the identifier request comprises:
sending the identifier request at a scheduled time that is based on how often the identifier for the subscriber is updated by the first network.

18. The method of claim 16 , where sending the identifier request comprises:
sending the identifier request based on the device connecting to the first network.

19. The method of claim 15 , where the identifier is generated based on a key and information associated with the subscriber.

20. The device of claim 1 , where the device is a user device.

Assignees

• Verizon Patent & Licensing Inc

Inventors

• Libonate Brian
• Morrison Stephen D
• Gupta Gaurav

Classifications

• 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

• H04W4/206 Primary

  Electricity · mapped topic

• H04W88/06

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

• H04W4/21 Primary

  for social networking applications · CPC title

• H04L67/561

  Adding application-functional data or data for application control, e.g. adding metadata · CPC title