# US 11,310,271 B2 · Using secure web sockets to extend reach of conditional access systems

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

- Number: US 11,310,271 B2
- Document ID: US11310271B2
- Status: Granted
- Kind: B2
- Application number: 16/795,235
- Filed: 2020-02-19
- Published: 2020-08-20
- Granted: 2022-04-19
- Earliest claimed: 2019-02-20
- Assignees: ARRIS Enterprises LLC
- Applicants: ARRIS Enterprises, LLC
- Inventors: Luke Smyth; Derek Gilmore
- Web page: https://patentgrep.com/patent/US11310271B2

## CPC

- H04L 63/168: {above the transport layer}
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/102: {Entity profiles}
- H04L 63/166: {at the transport layer}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 69/162: {involving adaptations of sockets based mechanisms (secure socket layer H04L63/168)}
- H04L 69/329: in the application layer [OSI layer 7]
- H04N 21/26606: {for generating or managing entitlement messages, e.g. Entitlement Control Message [ECM] or Entitlement Management Message [EMM] (arrangements for conditional access to broadcast information or to broadcast-related services H04H60/14)}
- H04N 21/42684: {Client identification by a unique number or address, e.g. serial number, MAC address, socket ID (network arrangements, protocols or services for addressing or naming H04L61/00)}
- H04N 21/4623: Processing of entitlement messages, e.g. ECM [Entitlement Control Message] or EMM [Entitlement Management Message] {(arrangements for conditional access to broadcast information or to broadcast-related services H04H60/14)}
- H04L 2463/101: applying security measures for digital rights management
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

A system and method for securely and bi-directionally transmitting information including conditional access private data between a client and a headend is disclosed. In an exemplary embodiment, the method includes: establishing a hypertext transfer protocol secure (HTTPs) connection, establishing a hypertext transfer protocol secure (HTTPs) connection; upgrading the HTTPs connection to a persistent bi-directional connection, accepting a first message from a client via the web socket connection, wherein the first message comprises an identifier of the client, parsing the message for the identifier of the client, associating the identifier of the client with the secure web socket connection, and transmitting a second message notifying the headend of the secure web site that connection, the message comprising the identifier of the client.

## Claims

### Claim 1

A method of securely and bi-directionally transmitting information comprising conditional access private data between a client and a headend, the method comprising:
establishing a hypertext transfer protocol secure (HTTPs) connection;
upgrading the HTTPs connection to a persistent bi-directional connection;
accepting a first message from the client via the persistent bi-directional connection, wherein the first message comprises an identifier of the client;
parsing the first message for the identifier of the client;
associating the identifier of the client with the persistent bi-directional connection; and
transmitting a second message notifying the headend of the persistent bi-directional connection, the second message comprising the identifier of the client.

### Claim 2 (depends on 1)

The method of claim 1, wherein establishing an HTTPs connection comprises transmitting an HTTPs connect message from the client to a web server.

### Claim 3 (depends on 1)

The method of claim 1 wherein the persistent bi-directional connection is a secure web socket connection.

### Claim 4 (depends on 3)

The method of claim 3, further comprising upstreaming the secure web socket connection to a server side application.

### Claim 5 (depends on 3)

The method of claim 3, wherein:
the first message further comprises a state of the client; and
wherein the second message further comprises the state of the client.

### Claim 6 (depends on 3)

The method of claim 3, wherein a server side application manages the secure web socket connection.

### Claim 7 (depends on 3)

The method of claim 3, further comprising:
receiving an entitlement request via the secure web socket connection;
looking up the identifier of the client based upon the secure web socket connection;
providing the entitlement request received via the secure web socket connection and the identifier of the client to the headend;
receiving an entitlement response from the headend;
up the secure web socket connection based upon the identifier of the client; and
providing the entitlement response to the client via the secure web socket connection.

### Claim 8

An apparatus for securely and bi-directionally transmitting information comprising conditional access private data between a client and a headend, the apparatus comprising:
a processor;
a memory, communicatively coupled to the processor, the memory comprising processor instructions comprising instructions for:
establishing a hypertext transfer protocol secure (HTTPs) connection;
upgrading the HTTPs connection to a persistent bi-directional connection;
accepting a first message from the client via the persistent bi-directional connection, wherein the first message comprises an identifier of the client;
parsing the first message for the identifier of the client;
associating the identifier of the client with the persistent bi-directional connection; and
transmitting a second message notifying the headend of the persistent bi-directional connection, the second message comprising the identifier of the client.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein establishing an HTTPs connection comprises transmitting an HTTPs connect message from the client to a web server.

### Claim 10 (depends on 8)

The apparatus of claim 8 wherein the persistent bi-directional connection is a secure web socket connection.

### Claim 11 (depends on 10)

The apparatus of claim 10, further comprising upstreaming the secure web socket connection to a server side application.

### Claim 12 (depends on 10)

The apparatus of claim 10, wherein:
first message further comprises a state of the client; and
wherein the second message further comprises the state of the client.

### Claim 13 (depends on 10)

The apparatus of claim 10, wherein a server side application manages the secure web socket connection.

### Claim 14 (depends on 10)

The apparatus of claim 10, further comprising:
receiving an entitlement request via the secure web socket connection;
looking up the identifier of the client based upon the secure web socket connection;
providing the entitlement request received via the secure web socket connection and the identifier of the client to the headend;
receiving an entitlement response from the headend;
looking up the secure web socket connection based upon the identifier of the client; and
providing the entitlement response to the client via the secure web socket connection.
