IP Library Granted Patent US 9,680,791
Granted Patent B2
US 9,680,791 · App. 13/194,826 · Granted Jun 13, 2017

Facilitating content accessibility via different communication formats

Inventor: Barrett Gibson Lyon (Pacifica, CA)
Assignee: Fortinet, Inc.
H04L61/251H04L43/50H04L67/10H04L67/2814H04L69/167H04L61/6068
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,680,791
App. No.
13/194,826
Granted
Jun 13, 2017
Kind
B2
Abstract

Facilitating content accessibility via different communication formats is disclosed. In some embodiments, in response to receiving a content request from an IPv6 enabled client, the requested content is provided to the IPv6 enabled client in IPv6 format, wherein the requested content is originally obtained in IPv4 format from an IPv4 enabled server and translated into IPv6 format.

Claims (37)

1. A system, comprising:

a processor configured to:

send test content to a client;

determine, based on a response by the client to the test content, the client is an IPv6 (Internet Protocol version 6) enabled client;

receive a content request from the IPv6 enabled client; and

provide the requested content to the IPv6 enabled client in IPv6 format;

wherein the requested content comprises web page content published by a content publisher on a website that is originally obtained at the processor in IPv4 (Internet Protocol version 4) format from an IPv4 enabled server and translated into IPv6 format by the processor prior to receiving any requests for the requested content; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. A system as recited in claim 1 , wherein the processor is dual stack.

3. A system as recited in claim 1 , wherein the processor is natively connected to both an IPv4 network and an IPv6 network.

4. A system as recited in claim 1 , wherein the processor is configured to communicate with the IPv4 enabled server natively via an IPv4 network.

5. A system as recited in claim 1 , wherein the processor is configured to communicate with the IPv6 enabled client natively via an IPv6 network.

6. A system as recited in claim 1 , wherein the processor is further configured to receive a content request from an IPv4 enabled client and provide the requested content to the IPv4 enabled client in IPv4 format based on a response received from the IPv4 enabled client to test content sent to the IPv4 enabled client.

7. A system as recited in claim 1 , wherein the processor is further configured to seed the web page content from the IPv4 enabled server.

8. A system as recited in claim 1 , wherein the system facilitates content from the IPv4 enabled server to be accessible via IPv6.

9. A method, comprising:

sending, by a processor, test content to a client;

determining, by the processor, based on a response by the client to the test content, the client is an IPv6 (Internet Protocol version 6) enabled client;

receiving a content request from the IPv6 enabled client by the processor; and

providing the requested content to the IPv6 enabled client in IPv6 format;

wherein the requested content comprises web page content published by a content publisher on a website that is originally obtained at the processor in IPv4 (Internet Protocol version 4) format from an IPv4 enabled server and translated into IPv6 format by the processor prior to receiving any requests for the requested content.

10. A method as recited in claim 9 , wherein the processor is dual stack.

11. A method as recited in claim 9 , wherein the processor is natively connected to both an IPv4 network and an IPv6 network.

12. A method as recited in claim 9 , wherein the processor is configured to communicate with the IPv4 enabled server natively via an IPv4 network.

13. A method as recited in claim 9 , wherein the processor is configured to communicate with the IPv6 enabled client natively via an IPv6 network.

14. A method as recited in claim 9 , wherein the processor is further configured to receive a content request from an IPv4 enabled client and provide the requested content to the IPv4 enabled client in IPv4 format based on a response received from the IPv4 enabled client to test content sent to the IPv4 enabled client.

15. A method as recited in claim 9 , wherein the processor is further configured to seed the web page content from the IPv4 enabled server.

16. A method as recited in claim 9 , wherein the processor facilitates content from the IPv4 enabled server to be accessible via IPv6.

17. A method as recited in claim 9 , wherein the processor is part of a proxy server.

18. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions, which when executed by one or more processors perform a method comprising:

sending test content to a client;

determining, based on a response by the client to the test content, the client is an IPv6 (Internet Protocol version 6) enabled client;

receiving a content request from the IPv6 enabled client; and

providing the requested content to the IPv6 enabled client in IPv6 format;

wherein the requested content comprises web page content published by a content publisher on a website that is originally obtained in IPv4 (Internet Protocol version 4) format from an IPv4 enabled server and translated into IPv6 format prior to receiving any requests for the requested content.

19. A computer program product as recited in claim 18 , wherein the one or more processors are configured to communicate via both an IPv4 network and an IPv6 network.

20. A computer program product as recited in claim 18 , wherein the method further comprises receiving a content request from an IPv4 enabled client and providing the requested content to the IPv4 enabled client in IPv4 format based on a response received from the IPv4 enabled client to test content sent to the IPv4 enabled client.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 12, 2012
From: XDN, INC.
To: FORTINET, INC.
Reel/Frame 029458/0126 →
CHANGE OF NAME Recorded Dec 12, 2012
From: 3CROWD TECHNOLOGIES, INC.
To: XDN, INC.
Reel/Frame 029458/0205 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 30, 2011
From: LYON, BARRETT GIBSON
To: 3CROWD TECHNOLOGIES, INC.
Reel/Frame 027002/0638 →
Continuity (1)
Related Publication 20130103805A1 · Apr 25, 2013