# US 11,910,070 B2 · Fast direct resource allocation identifier

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

- Number: US 11,910,070 B2
- Document ID: US11910070B2
- Status: Granted
- Kind: B2
- Application number: 17/888,332
- Filed: 2022-08-15
- Published: 2022-12-08
- Granted: 2024-02-20
- Earliest claimed: 2020-11-06
- Assignees: Conviva Inc.
- Applicants: Conviva Inc.
- Inventors: Biplab Chattopadhyay; Weijia Li; Sudhi Nada
- Web page: https://patentgrep.com/patent/US11910070B2

## CPC

- H04N 21/812: {involving advertisement data (advertising per se G06Q30/02)}
- H04N 21/84: Generation or processing of descriptive data, e.g. content descriptors {(systems specially adapted for using meta-information in broadcast systems H04H60/73)}
- G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q 30/0251: Targeted advertisements
- G06Q 30/0275: {Auctions}
- H04N 21/262: Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists {(scheduling strategies for dispatcher in multiprogramming arrangements G06F9/4881; arrangements for scheduling broadcast services or broadcast-related services H04H60/06; flow control in packet networks H04L47/10; establishing a time schedule or organising the servicing of application requests H04L67/62)}
- H04N 21/845: Structuring of content, e.g. decomposing content into time segments
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Resource allocation includes generating a resource allocation identifier corresponding to a resource allocation request. The resource allocation request pertains to allocation of a resource associated with streaming of an audiovisual content item. The resource allocation identifier comprises a first portion and a second portion, the first portion comprising a key, and the second portion comprising information associated with contextual metadata pertaining to the corresponding resource allocation request. It further includes performing a first transmission of a first message including the resource allocation identifier. The first message including the resource allocation identifier is directed to a first address associated with a first entity. It further includes performing a second transmission of a second message. Transmission of the second message causes transmission of the resource allocation request. The second message is directed to a second address associated with a second entity. The first address and the second address are different. Resource allocation includes receiving a first message comprising a resource allocation identifier. It further includes, at a time subsequent to receiving the first message, receiving a second message comprising a resource allocation request pertaining to allocation of a resource associated with streaming of an audiovisual content item. It further includes matching the resource allocation request with the resource allocation identifier. It further includes, based at least in part on the match, receiving contextual metadata associated with the resource allocation request. It further includes facilitating resource allocation at least in part by using the contextual metadata.

## Claims

### Claim 1

A system, comprising:
a processor configured to:
receive a first message comprising a resource allocation identifier;
associate the resource allocation identifier with a time-to-live window;
at a time subsequent to receiving the first message, receive a second message comprising a resource allocation request pertaining to allocation of a resource associated with streaming of an audiovisual content item;
based at least in part on delivery of the second message within the time-to-live window associated with the resource allocation identifier comprised in the first message, match the resource allocation request comprised in the second message with the resource allocation identifier comprised in the first message;
based at least in part on the matching, receive contextual metadata associated with the resource allocation request; and
facilitate fulfilling of the resource allocation request at least in part by using the contextual metadata; and
a memory coupled to the processor and configured to provide the processor with instructions.

### Claim 2 (depends on 1)

The system recited in claim 1, wherein the resource allocation identifier comprises a first portion and a second portion, the first portion comprising a key, and the second portion comprising information associated with the contextual metadata pertaining to the resource allocation request.

### Claim 3 (depends on 2)

The system recited in claim 2, wherein the second portion comprises the contextual metadata.

### Claim 4 (depends on 2)

The system recited in claim 2, wherein the second portion comprises a contextual metadata identifier.

### Claim 5 (depends on 4)

The system recited in claim 4, wherein the processor is further configured to fetch the contextual metadata at least in part by performing a query of a data store using the contextual metadata identifier.

### Claim 6 (depends on 1)

The system recited in claim 1, wherein subsequent to receiving the first message comprising the resource allocation identifier, the processor is further configured to store the resource allocation identifier to a data store based at least in part on a key included in the resource allocation identifier.

### Claim 7 (depends on 1)

The system recited in claim 1, wherein subsequent to receiving the second message comprising the resource allocation request, the processor is further configured to determine a key from at least a portion of the resource allocation request.

### Claim 8 (depends on 7)

The system recited in claim 7, wherein performing the match comprises using the key to perform a query of a data store for the resource allocation identifier.

### Claim 9 (depends on 8)

The system recited in claim 8, wherein the resource allocation identifier is identified in response to performing the query.

### Claim 10 (depends on 9)

The system recited in claim 9, wherein the contextual metadata is received in response to identifying the resource allocation identifier.

### Claim 11 (depends on 9)

The system recited in claim 9, wherein in response to identifying the resource allocation identifier, the processor is further configured to:
receive a contextual metadata identifier; and
receive the contextual metadata at least in part by performing a lookup using the contextual metadata identifier.

### Claim 12 (depends on 1)

The system recited in claim 1, wherein the first message was transmitted from a client device comprising a content player, and wherein the resource allocation identifier was generated at the client device.

### Claim 13

A method, comprising:
receiving a first message comprising a resource allocation identifier;
associating the resource allocation identifier with a time-to-live window;
at a time subsequent to receiving the first message, receiving a second message comprising a resource allocation request pertaining to allocation of a resource associated with streaming of an audiovisual content item;
based at least in part on delivery of the second message within the time-to-live window associated with the resource allocation identifier comprised in the first message, matching the resource allocation request comprised in the second message with the resource allocation identifier comprised in the first message;
based at least in part on the matching, receiving contextual metadata associated with the resource allocation request; and
facilitating fulfilling of the resource allocation request at least in part by using the contextual metadata.

### Claim 14 (depends on 13)

The method of claim 13, wherein the resource allocation identifier comprises a first portion and a second portion, the first portion comprising a key, and the second portion comprising information associated with the contextual metadata pertaining to the resource allocation request.

### Claim 15 (depends on 14)

The method of claim 14, wherein the second portion comprises the contextual metadata.

### Claim 16 (depends on 14)

The method of claim 14, wherein the second portion comprises a contextual metadata identifier.

### Claim 17 (depends on 16)

The method of claim 16, further comprising fetching the contextual metadata at least in part by performing a query of a data store using the contextual metadata identifier.

### Claim 18 (depends on 13)

The method of claim 13, wherein subsequent to receiving the first message comprising the resource allocation identifier, further comprising storing the resource allocation identifier to a data store based at least in part on a key included in the resource allocation identifier.

### Claim 19 (depends on 13)

The method of claim 13, wherein subsequent to receiving the second message comprising the resource allocation request, further comprising determining a key from at least a portion of the resource allocation request.

### Claim 20 (depends on 19)

The method of claim 19, wherein performing the match comprises using the key to perform a query of a data store for the resource allocation identifier.

### Claim 21 (depends on 20)

The method of claim 20, wherein the resource allocation identifier is identified in response to performing the query.

### Claim 22 (depends on 21)

The method of claim 21, wherein the contextual metadata is received in response to identifying the resource allocation identifier.

### Claim 23 (depends on 21)

The method of claim 21, wherein in response to identifying the resource allocation identifier, further comprising:
receiving a contextual metadata identifier; and
receiving the contextual metadata at least in part by performing a lookup using the contextual metadata identifier.

### Claim 24 (depends on 13)

The method of claim 13, wherein the first message was transmitted from a client device comprising a content player, and wherein the resource allocation identifier was generated at the client device.

### Claim 25

A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receiving a first message comprising a resource allocation identifier;
associating the resource allocation identifier with a time-to-live window;
at a time subsequent to receiving the first message, receiving a second message comprising a resource allocation request pertaining to allocation of a resource associated with streaming of an audiovisual content item;
based at least in part on delivery of the second message within the time-to-live window associated with the resource allocation identifier comprised in the first message, matching the resource allocation request comprised in the second message with the resource allocation identifier comprised in the first message;
based at least in part on the matching, receiving contextual metadata associated with the resource allocation request; and
facilitating fulfilling of the resource allocation request at least in part by using the contextual metadata.
