# US 2024/0187619 A1 · Hardware-based video codec control

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

- Number: US 2024/0187619 A1
- Document ID: US20240187619A1
- Status: Published application
- Kind: A1
- Application number: 18/073,725
- Filed: 2022-12-02
- Published: 2024-06-06
- Earliest claimed: 2022-12-02
- Assignees: ATI Technologies ULC
- Applicants: Ati Technologies Ulc
- Inventors: Xingyue Zhang; Krzysztof Socha; Catalin Beju; Kathirkamanathan Nadarajah; Gia Tung Phan; Weimin Chen; Tow Wang
- Web page: https://patentgrep.com/patent/US20240187619A1

## CPC

- H04N 19/42: characterised by implementation details or hardware specially adapted for video compression or decompression, e.g. dedicated software implementation (H04N19/635 takes precedence)
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

A compute device implements a technique for facilitating selective access to hardware codec resources. The compute device executes, in a trusted execution environment, firmware for controlling graphics hardware of a device that supports a plurality of video codecs. The compute device obtains codec control data specific to the device from a remote system and then configures the firmware to implement a codec policy for selectively providing access to the plurality of video codecs based on the codec control data.

## Claims

### Claim 1

A computer-implemented method comprising:
executing, in a trusted execution environment of a compute system, firmware for controlling graphics hardware of a device that supports a plurality of video codecs;
obtaining, at the device, codec control data specific to the device from a remote system; and
configuring the firmware to implement a codec policy for selectively providing access to the plurality of video codecs based on the codec control data.

### Claim 2 (depends on 1)

The method of claim 1, wherein obtaining the codec control data comprises:
sending a request for a device-specific codec token to a remote system via one or more networks, the request including a data structure including one or more identifiers associated with the device and a first signing key for authenticating the device to the remote system; and
receiving, from the remote system, the requested device-specific codec token, the device-specific codec token including a data structure including the codec control data and a second signing key for verifying the device-specific codec token at the trusted execution environment.

### Claim 3 (depends on 2)

The method of claim 2, wherein:
obtaining the codec control data further comprises storing the device-specific codec token in a file system of the compute system; and
configuring the firmware to implement the codec policy comprises:
accessing the device-specific codec token from the file system;
verifying the device-specific codec token by firmware in the trusted execution environment;
responsive to verifying the device-specific codec token, storing codec control data from the device-specific codec token at a trusted memory region accessible to the firmware executing in the trusted execution environment; and
initializing a codec driver for the graphics hardware of the device from the codec control data in the trusted memory region.

### Claim 4 (depends on 2)

The method of claim 2, wherein the one or more identifiers comprise at least one of: a device identifier, a model identifier, or a stock keeping unit (SKU) identifier.

### Claim 5 (depends on 2)

The method of claim 2, further comprising:
acquiring, through the remote system, access to one or more video codecs for the device prior to sending the request for the device-specific codec token.

### Claim 6 (depends on 1)

The method of claim 1, wherein configuring the firmware to implement the codec policy comprises:
verifying the codec control data by firmware in the trusted execution environment;
responsive to verifying the codec control data, storing the codec control data at a trusted memory region accessible to the firmware executing in the trusted execution environment; and
initializing a codec driver for the graphics hardware of the device from the codec control data in the trusted memory region.

### Claim 7 (depends on 1)

The method of claim 1, wherein:
the codec policy permits access to a first set of one or more video codecs and prohibits access to a second set of one or more video codecs; and
configuring the firmware to implement the codec policy comprises:
configuring the firmware to permit an encode/decode job to be provided to the graphics hardware for processing responsive to the encode/decode job requesting utilization of a video codec of the first set; and
configuring the firmware to block the encode/decode job from being provided to the graphics hardware for processing responsive to the encode/decode job requesting utilization of a video codec of the second set.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
providing, via an application programming interface (API), a representation of codec capabilities available to a video application based on the codec control data.

### Claim 9 (depends on 1)

The method of claim 1, wherein the firmware is accessed from a secure memory associated with a security processor and executed by the security processor.

### Claim 10 (depends on 9)

The method of claim 9, further comprising storing a copy of the codec control data at a non-volatile memory associated with the security processor.

### Claim 11

An apparatus comprising:
a device having a security processor to provide a trusted execution environment and graphics hardware that supports a plurality of video codecs, the device to:
execute firmware at the security processor for controlling the graphics hardware;
obtain codec control data specific to the device from a remote system; and
configure the firmware to implement a codec policy for selectively providing access to the plurality of video codecs at the graphics hardware based on the codec control data.

### Claim 12 (depends on 11)

The apparatus of claim 11, wherein the device is to configure the firmware to implement the codec policy by:
verifying the codec control data using the firmware executed by the security processor;
responsive to verifying the codec control data, storing the codec control data at a trusted memory region accessible to the firmware executing by the security processor; and
initializing, in the trusted execution environment, a codec driver for the graphics hardware from the codec control data in the trusted memory region.

### Claim 13 (depends on 12)

The apparatus of claim 12, wherein:
the codec policy permits access to a first set of one or more video codecs and prohibits access to a second set of one or more video codecs; and
the device is to configure the firmware to implement the codec policy by:
configuring the firmware to permit an encode/decode job to be provided to the graphics hardware for processing responsive to the encode/decode job requesting utilization of a video codec of the first set; and
configuring the firmware to block the encode/decode job from being provided to the graphics hardware for processing responsive to the encode/decode job requesting utilization of a video codec of the second set.

### Claim 14 (depends on 11)

The apparatus of claim 11, wherein the firmware is accessed from a secure memory associated with the security processor.

### Claim 15 (depends on 11)

The apparatus of claim 11, wherein the device further is to:
store a copy of the codec control data at a non-volatile memory associated with the security processor.

### Claim 16 (depends on 11)

The apparatus of claim 11, further comprising:
a central processing unit (CPU); and
system memory coupled to the CPU and storing software to manipulate the CPU to provide, via an application programming interface (API), a representation of codec capabilities available to a video application based on the codec control data.

### Claim 17 (depends on 11)

The apparatus of claim 11, further comprising:
a central processing unit (CPU); and
system memory coupled to the CPU and storing software to manipulate the CPU to:
send a request for a device-specific codec token to a remote system via one or more networks, the request including a data structure including one or more identifiers associated with the device and a first signing key for authenticating the device to the remote system; and
receive, from the remote system, the requested device-specific codec token, the device-specific codec token including a data structure including the codec control data and a second signing key for verifying the device-specific codec token at the trusted execution environment.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein:
the software is further to manipulate the CPU to store the device-specific codec token in a file system of the apparatus; and
the device is to configure the firmware to implement the codec policy by:
accessing the device-specific codec token from the file system;
verifying the device-specific codec token by firmware in the trusted execution environment;
responsive to verifying the device-specific codec token, storing codec control data from the device-specific codec token at a trusted memory region accessible to the firmware executing in the trusted execution environment; and
initializing a codec driver for the graphics hardware of the device from the codec control data in the trusted memory region.

### Claim 19 (depends on 17)

The apparatus of claim 17, wherein the device is to configure the firmware to implement the codec policy by:
verifying the device-specific codec token by firmware in the trusted execution environment;
responsive to verifying the device-specific codec token, storing codec control data from the device-specific codec token at a trusted memory region accessible to the firmware executing in the trusted execution environment; and
initializing a codec driver for the graphics hardware of the device from the codec control data in the trusted memory region.

### Claim 20 (depends on 11)

The apparatus of claim 11, wherein:
the codec policy permits access to a first set of one or more video codecs and prohibits access to a second set of one or more video codecs; and
the device is to configure the firmware to implement the codec policy by:
configuring the firmware to permit an encode/decode job to be provided to the graphics hardware for processing responsive to the encode/decode job requesting utilization of a video codec of the first set; and
configuring the firmware to block the encode/decode job from being provided to the graphics hardware for processing responsive to the encode/decode job requesting utilization of a video codec of the second set.
