# US 2019/0379756 A1 · Automatically Redirecting Mobile Client Devices to Optimized Mobile Content

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

- Number: US 2019/0379756 A1
- Document ID: US20190379756A1
- Status: Published application
- Kind: A1
- Application number: 16/391,109
- Filed: 2019-04-22
- Published: 2019-12-12
- Earliest claimed: 2018-06-07
- Assignees: Cloudflare, Inc.
- Applicants: Cloudflare, Inc.
- Inventors: Igor Postelnik; Mohd Fairuz Irtefa
- Web page: https://patentgrep.com/patent/US20190379756A1

## CPC

- H04L 67/303: Terminal profiles
- H04L 67/04: specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
- H04L 67/563: Data redirection of data network streams
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A server receives a request for a document from a client device. The server determines from the request that the client device is a mobile client device. The server determines that the requested document is not for an optimized mobile version and that there is an optimized mobile version of the document that is located at a different location. Instead of transmitting the requested document to the client device, the server transmits a redirect message to the client device to the optimized mobile version of the document. The server receives a request for the optimized mobile version of the document, retrieves that version of the document, and transmits that version of the document to the mobile client device.

## Claims

### Claim 1

A method in a server, comprising:
receiving, from a first client device, a first request for a first document;
determining, from the first request, that the first client device is a mobile client device;
determining that the first document requested in the first request is not an optimized mobile version;
determining that there is an optimized mobile version of the first document that is located at a different location from a location of the requested first document;
instead of transmitting the first document requested in the first request to the first client device, transmitting a redirect message to the first client device to the optimized mobile version of the first document that is located at the different location;
receiving, from the first client device, a second request for the optimized mobile version of the first document that is located at the different location;
retrieving the optimized mobile version of the first document; and
transmitting, to the client device, the optimized mobile version of the first document.

### Claim 2 (depends on 1)

The method of claim 1, wherein determining that the first client device is a mobile client device includes examining a user-agent in a header of the first request.

### Claim 3 (depends on 1)

The method of claim 1, wherein determining that there is an optimized mobile version of the first document that is located at a different location includes accessing information stored on the server that indicates that the optimized mobile version of the first document is located at the different location.

### Claim 4 (depends on 1)

The method of claim 1, wherein determining that there is an optimized mobile version of the first document includes:
retrieving the first document requested in the first request; and
analyzing the first document and locating a tag that points to the optimized mobile version of the first document.

### Claim 5 (depends on 1)

The method of claim 1, wherein determining that the first request is for a document that is not optimized for mobile devices includes determining that a uniform resource locator (URL) of the first document does not match a pattern predefined for mobile redirection.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
receiving, from a second client device, a third request for a second document;
determining, from the third request, that the second client device is not a mobile client device;
responsive to determining that the second client device is not a mobile client device,
performing the following:
retrieving the second document; and
transmitting, to the second client device, the second document.

### Claim 7

A non-transitory machine-readable storage medium that provides instructions that, if executed by a processor of a server, will cause said processor to perform operations comprising:
receiving, from a first client device, a first request for a first document;
determining, from the first request, that the first client device is a mobile client device;
determining that the first document requested in the first request is not an optimized mobile version;
determining that there is an optimized mobile version of the first document that is located at a different location from a location of the requested first document;
instead of transmitting the first document requested in the first request to the first client device, transmitting a redirect message to the first client device to the optimized mobile version of the first document that is located at the different location;
receiving, from the first client device, a second request for the optimized mobile version of the first document that is located at the different location;
retrieving the optimized mobile version of the first document; and
transmitting, to the client device, the optimized mobile version of the first document.

### Claim 8 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein determining that the first client device is a mobile client device includes examining a user-agent in a header of the first request.

### Claim 9 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein determining that there is an optimized mobile version of the first document that is located at a different location includes accessing information stored on the server that indicates that the optimized mobile version of the first document is located at the different location.

### Claim 10 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein determining that there is an optimized mobile version of the first document includes:
retrieving the first document requested in the first request; and
analyzing the first document and locating a tag that points to the optimized mobile version of the first document.

### Claim 11 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein determining that the first request is for a document that is not optimized for mobile devices includes determining that a uniform resource locator (URL) of the first document does not match a pattern predefined for mobile redirection.

### Claim 12 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein the operations further comprise:
receiving, from a second client device, a third request for a second document;
determining, from the third request, that the second client device is not a mobile client device;
responsive to determining that the second client device is not a mobile client device,
performing the following:
retrieving the second document; and
transmitting, to the second client device, the second document.

### Claim 13

A server, comprising:
a processor; and
a non-transitory machine-readable storage medium that provides instructions that, if executed by the processor, causes the server to perform operations including:
receive, from a first client device, a first request for a first document;
determine, from the first request, that the first client device is a mobile client device;
determine that the first document requested in the first request is not an optimized mobile version;
determine that there is an optimized mobile version of the first document that is located at a different location from a location of the requested first document;
instead of transmitting the first document requested in the first request to the first client device, transmit a redirect message to the first client device to the optimized mobile version of the first document that is located at the different location;
receive, from the first client device, a second request for the optimized mobile version of the first document that is located at the different location;
retrieve the optimized mobile version of the first document; and
transmit, to the client device, the optimized mobile version of the first document.

### Claim 14 (depends on 13)

The server of claim 13, wherein the determination that the first client device is a mobile client device includes an examination of a user-agent in a header of the first request.

### Claim 15 (depends on 13)

The server of claim 13, wherein the determination that there is an optimized mobile version of the first document that is located at a different location includes the server to access information stored on the server that indicates that the optimized mobile version of the first document is located at the different location.

### Claim 16 (depends on 13)

The server of claim 13, wherein the determination that there is an optimized mobile version of the first document includes:
retrieve the first document requested in the first request; and
analyze the first document and locate a tag that points to the optimized mobile version of the first document.

### Claim 17 (depends on 13)

The server of claim 13, wherein the determination that the first request is for a document that is not optimized for mobile devices includes the server to determine that a uniform resource locator (URL) of the first document does not match a pattern predefined for mobile redirection.

### Claim 18 (depends on 13)

The server of claim 13, wherein the operations further include:
receive, from a second client device, a third request for a second document;
determine, from the third request, that the second client device is not a mobile client device;
responsive to the determination that the second client device is not a mobile client device, perform the following:
retrieve the second document; and
transmit, to the second client device, the second document.
