# US 10,320,943 B2 · Geography based HTML5 content redirection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,320,943 B2
- Document ID: US10320943B2
- Status: Granted
- Kind: B2
- Application number: 14/812,642
- Filed: 2015-07-29
- Published: 2017-02-02
- Granted: 2019-06-11
- Earliest claimed: 2015-07-29
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Ramanujam Kaniyar Venkatesh
- Web page: https://patentgrep.com/patent/US10320943B2

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/63: Routing a service request depending on the request content or context
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Certain information and data, such as HTML5 content, may be stored at a cloud server. A client may establish a connection with the server whereupon the server redirects the HTML5 content to the client. The HTML5 content may not be accessible by the client due to geographic or other location restrictions on placed on the HTML5 content. The client may request that the server fetch the desired HTML5 content from the source whereupon the server transmits the encoded HTML5 content to the client. The client renders the encoded HTML5 content. The client receives seamless HTML5 content redirection irrespective of geography and website.

## Claims

### Claim 1

A method comprising:
receiving, by a server, a request by a client to establish a connection to the server, wherein the connection comprises at least a tunnel and a remote desktop protocol connection;
receiving, by the server, a request for hypertext extensive markup language (HTML) 5 content for a particular website from the client;
loading, by the server, in a browser executing on the server and displayed on the client, a webpage comprising HTML5 content associated with the request for HTML5 content for the particular website;
redirecting, by the server, the HTML5 content of the webpage loaded in the browser of the server to the client, wherein the HTML5 content is encoded;
determining if the client is restricted from rendering the HTML5 content based, at least in part, on a physical geographic location of the client;
receiving, by the server, a fetch request for encoded HTML5 content from the client;
fetching, by the server, the encoded HTML5 content for the webpage; and
sending the encoded HTML5 content to the client, wherein the HTML5 content comprises a plurality of HTML5 content items of the webpage.

### Claim 2 (depends on 1)

The method of claim 1, wherein the HTML5 content is fetched from an HTML5 content server by the server.

### Claim 3 (depends on 2)

The method of claim 2, wherein the HTML5 content server is located in a different geographic region from the client.

### Claim 4 (depends on 1)

The method of claim 1, wherein the HTML5 content comprises video.

### Claim 5 (depends on 1)

The method of claim 1, wherein the connection is a remote desktop connection.

### Claim 6 (depends on 1)

The method of claim 1, wherein the server and the client are located in different geographic regions.

### Claim 7

A method comprising:
requesting, at a client, a connection to a server, wherein the connection comprises at least a tunnel and a remote desktop protocol connection;
requesting, by the client, hypertext extensive markup language (HTML)5 content for a particular webpage from a server, wherein the HTML5 content comprises a plurality of HTML5 content items of the webpage;
requesting an HTML5 redirection browser at the client to display HTML5 content;
receiving redirected HTML5 content at the client from a browser executing on the server that has loaded the particular webpage comprising the requested HTML5 content;
determining, at the client, if the client has access to the HTML5 content based, at least in part, on a physical geographic location of the client;
sending a request, by the client, for the server to fetch encoded HTML5 content;
receiving at the client the encoded HTML5 content; and
decoding and rendering the HTML5 content at the client, wherein decoding and rendering the HTML5 content comprises displaying the HTML5 content at the client.

### Claim 8 (depends on 7)

The method of claim 7, wherein the HTML5 content is received from an HTML5 content server by the server.

### Claim 9 (depends on 8)

The method of claim 8, wherein the HTML5 content server is located in a different geographic region from the client.

### Claim 10 (depends on 7)

The method of claim 7, wherein the HTML5 content comprises video.

### Claim 11 (depends on 7)

The method of claim 7, wherein the connection is a remote desktop connection.

### Claim 12 (depends on 7)

The method of claim 7, wherein the server and the client are located in different geographic regions.

### Claim 13

One or more computer-readable non-transitory storage media embodying software that is operable when executed to:
receive, by a server, a request by a client to establish a connection to the server, wherein the connection comprises at least a tunnel and a remote desktop protocol connection;
receive, by the server, a request for hypertext extensive markup language (HTML)5 content for a particular website from the client, wherein the HTML5 content comprises a plurality of HTML5 content items of the webpage;
load, by the server, in a browser, executing on the server and for displaying on the client, a webpage comprising HTML5 content associated with the request for HTML5 content for the particular website;
redirect, by the server, the HTML5 content of the webpage loaded in the browser of the server to the client;
determine if the client is restricted from rendering the HTML5 content based, at least in part, on a physical geographic location of the client;
receive, by the server, a fetch request for encoded HTML5 content from the client;
fetch, by the server, the encoded HTML5 content for the webpage; and
send the encoded HTML5 content to the client for decoding and displaying at the client.

### Claim 14 (depends on 13)

The media of claim 13, wherein the HTML5 content is received from an HTML5 content server by the server.

### Claim 15 (depends on 14)

The media of claim 14, wherein the HTML5 content server is located in a different geographic region from the client.

### Claim 16 (depends on 13)

The media of claim 13, wherein the HTML5 content comprises video.

### Claim 17 (depends on 13)

The media of claim 13, wherein the connection is a remote desktop connection.