# US 9,883,401 B2 · Differentiating authorization requests for security requirements

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

- Number: US 9,883,401 B2
- Document ID: US9883401B2
- Status: Granted
- Kind: B2
- Application number: 15/093,054
- Filed: 2016-04-07
- Published: 2017-10-12
- Granted: 2018-01-30
- Earliest claimed: 2016-04-07
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: Raymond C. Counterman
- Web page: https://patentgrep.com/patent/US9883401B2

## CPC

- H04W 12/08: Access security
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/18: {using different networks or channels, e.g. using out of band channels (cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215)}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04W 12/71: Hardware identity
- H04W 12/72: Subscriber identity
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A device may receive a request from a mobile device. The device may determine a port identifier for a port of the device. The port may correspond to whether the mobile device used a secure communication path to send the request. The device may determine a mobile device identifier for the mobile device. The device may add the mobile device identifier and the port identifier to the request. The device may send the request to an application device after adding the mobile device identifier and the port identifier to the request. The port identifier may be added to the request to enable the application device to determine whether the request was sent, by the mobile device, over the secure communication path.

## Claims

### Claim 1

A device, comprising:
one or more processors; and
one or more memory devices storing instructions that, when executed by the one or more processors, cause the one or more processors to:
receive, from a mobile device, a request at a port of the device, the port relating to whether the request was sent, by the mobile device, over a secure communication path;
determine a port identifier for the port of the device;
determine a mobile device identifier for the mobile device, the mobile device identifier being determined based on the request;
add, to the request, the mobile device identifier and the port identifier; and
send the request to an application device after adding the mobile device identifier and the port identifier to the request, the port identifier being added to the request to enable the application device to determine whether the request was sent, by the mobile device, over the secure communication path.

### Claim 2 (depends on 1)

The device of claim 1,
where the port is a first port or a second port; and
where the one or more processors, when receiving, from the mobile device, the request at the port, are to:
receive the request at one of the first port or the second port,
the request being received at the first port when the request is sent over the secure communication path, and
the request being received at the second port when the request is sent over an unsecured communication path.

### Claim 3 (depends on 1)

The device of claim 1,
where the one or more processors are further to:
add a header to the request; and
where the one or more processors, when adding, to the request, the mobile device identifier and the port identifier, are to:
add the mobile device identifier and the port identifier to the header.

### Claim 4 (depends on 1)

The device of claim 1,
where the mobile device identifier and the port identifier are included in a JavaScript object notation (JSON) object; and
where the one or more processors, when adding, to the request, the mobile device identifier and the port identifier, are to:
add the JSON object to the request.

### Claim 5 (depends on 1)

The device of claim 1,
where the request is a request for the mobile device to receive at least one of content or a service from the application device.

### Claim 6 (depends on 1)

The device of claim 1, where the one or more processors, when sending the request to the application device, are to:
send the request to the application device using an unsecured communication path.

### Claim 7 (depends on 1)

The device of claim 1, where the one or more processors, when determining the mobile device identifier for the mobile device, are to:
determine the mobile device identifier based on an address associated with the mobile device.

### Claim 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 a request from a mobile device;
determine a port identifier for a port of the device at which the request was received,
the port relating to whether a secure communication path was used, by the mobile device, to send the request;
determine a mobile device identifier for the mobile device,
the mobile device identifier being determined based on the request;
add, to the request, the mobile device identifier and the port identifier; and
send the request to an application device after adding the mobile device identifier and the port identifier to the request,
the port identifier being added to the request to enable the application device to determine whether the request was received, from the mobile device, over the secure communication path.

### Claim 9 (depends on 8)

The non-transitory computer-readable medium of claim 8,
where the port is a first port or a second port; and
where the one or more instructions, that cause the one or more processors to receive the request from the mobile device, cause the one or more processors to:
receive the request at one of the first port or the second port,
the request being received at the first port when the request is received over the secure communication path, and
the request being received at the second port when the request is not received over the secure communication path.

### Claim 10 (depends on 8)

The non-transitory computer-readable medium of claim 8,
where the mobile device identifier and the port identifier are included in a JavaScript object notation (JSON) object; and
where the one or more instructions, that cause the one or more processors to add, to the request, the mobile device identifier and the port identifier, cause the one or more processors to:
add the JSON object to the request.

### Claim 11 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to send the request to the application device, cause the one or more processors to:
send the request to the application device using an unsecured communication path.

### Claim 12 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to determine the mobile device identifier for the mobile device, cause the one or more processors to:
determine the mobile device identifier using an address associated with the mobile device to look up the mobile device identifier in a data structure.

### Claim 13 (depends on 12)

The non-transitory computer-readable medium of claim 12, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
add, to the request, an identifier associated with the data structure.

### Claim 14 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to receive the request from the mobile device, cause the one or more processors to:
receive the request, from the mobile device, over hypertext transfer protocol (HTTP).

### Claim 15

A method, comprising:
receiving, by a device, a request from a mobile device;
determining, by the device, a port identifier for a port of the device,
the port corresponding to whether a secure communication path was used, by the mobile device, to send the request;
determining, by the device, a mobile device identifier for the mobile device;
adding, by the device, the mobile device identifier and the port identifier to the request; and
sending, by the device, the request to an application device after adding the mobile device identifier and the port identifier to the request,
the port identifier being added to the request to enable the application device to determine whether the request was sent, by the mobile device, over the secure communication path.

### Claim 16 (depends on 15)

The method of claim 15,
where the port is a first port or a second port; and
where receiving the request from the mobile device comprises:
receiving the request at one of the first port or the second port,
the request being received at the first port when the request is sent over the secure communication path, and
the request being received at the second port when the request is sent over an unsecured communication path.

### Claim 17 (depends on 15)

The method of claim 15,
where determining the mobile device identifier for the mobile device comprises:
determining the mobile device identifier using an address associated with the mobile device to look up the mobile device identifier in a data structure; and
the method further comprising:
adding, to the request, an identifier associated with the data structure.

### Claim 18 (depends on 15)

The method of claim 15,
where the request is a request for the mobile device to obtain authorization to access at least one of content or a service on the application device.

### Claim 19 (depends on 15)

The method of claim 15, further comprising:
adding a header to the request; and
where adding the mobile device identifier and the port identifier to the request comprises:
adding the mobile device identifier and the port identifier to the header before adding the header to the request.

### Claim 20 (depends on 15)

The method of claim 15, where sending the request to the application device comprises:
sending the request to the application device using an unsecured communication path.