# US 2021/0342746 A1 · Methods and apparatus to analyze performance of watermark encoding devices

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

- Number: US 2021/0342746 A1
- Document ID: US20210342746A1
- Status: Published application
- Kind: A1
- Application number: 17/373,616
- Filed: 2021-07-12
- Published: 2021-11-04
- Earliest claimed: 2018-12-21
- Assignees: The Nielsen Company (US), LLC
- Applicants: The Nielsen Company (US), LLC
- Inventors: John T. Livoti; Susan Cimino; Stanley Wellington Woodruff; Rajakumar Madhanganesh; Alok Garg
- Web page: https://patentgrep.com/patent/US20210342746A1

## CPC

- G06N 3/08: Learning methods
- G06N 20/00: Machine learning
- G06F 11/0748: {in a remote unit communicating with a single-box computer node experiencing an error/fault (remote testing G06F11/2294)}
- G06F 11/0754: {by exceeding limits}
- G06F 11/0766: {Error or fault reporting or storing}
- G06F 11/2263: {using neural networks}
- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06N 3/0464: Convolutional networks [CNN, ConvNet]
- G06N 3/09: Supervised learning
- G06N 3/096: Transfer learning
- G06F 11/3065: {Monitoring arrangements determined by the means or processing involved in reporting the monitored data (error or fault reporting or logging G06F11/0766)}
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, apparatus, systems, and articles of manufacture are disclosed that analyze performance of manufacturer independent devices. An example apparatus includes a software development kit (SDK) deployment engine to deploy an SDK to a manufacturer of a device, the SDK to define heartbeat data to be collected from the device and interfacing techniques to transmit the heartbeat data to a measurement entity. In some examples, the apparatus includes a machine learning engine to predict whether the device is associated with one or more failure modes. The example apparatus also includes an alert generator to generate an alert based on a prediction, the alert to indicate at least one of a type of a first one of the failure modes or at least one component of the device to be remedied according to the first one of the one or more failure modes, and transmit the alert to a management agent.

## Claims

### Claim 1

An apparatus to monitor performance of one or more devices, the apparatus comprising:
a software development kit (SDK) deployment engine to deploy an SDK associated with a measurement entity to a manufacturer of a device, the SDK to define heartbeat data to be collected from the device and interfacing techniques to transmit the heartbeat data from the device to the measurement entity, the heartbeat data including time varying data and fixed data;
a data collector to collect, via a network, the heartbeat data from the device;
a machine learning engine to process the heartbeat data to predict whether the device is associated with one or more failure modes; and
an alert generator to:
generate an alert based on a prediction from the machine learning engine associated with a first one of the one or more failure modes, the alert to indicate at least one of (a) a type of the first one of the failure modes or (b) at least one component of the device to be remedied according to the first one of the one or more failure modes; and
transmit the alert to a management agent of the device.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the manufacturer is a first manufacturer, the device is a first device, the heartbeat data is first heartbeat data, the one or more failure modes are one or more first failure modes, the prediction is a first prediction, the alert is a first alert, the management agent is a first management agent, and:
the SDK deployment engine is to deploy the SDK to a second manufacturer of a second device, the SDK to define second heartbeat data to be collected from the second device and interfacing techniques to transmit the second heartbeat data from the second device to the measurement entity, the second manufacturer different from the first manufacturer, the second device different from the first device, the first heartbeat data different than the second heartbeat data;
the data collector is to collect the second heartbeat data from the second device;
the machine learning engine is to process the second heartbeat data to predict whether the second device is associated with one or more second failure modes; and
the alert generator is to:
generate a second alert based on a second prediction from the machine learning engine associated with a first one of the one or more second failure modes, the second alert to indicate at least one of (a) a type of the first one of the second failure modes or (b) at least one component of the second device to be remedied according to the first one of the one or more second failure modes; and
transmit the second alert to a second management agent of the second device.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the alert is a first alert and the alert generator is to generate a second alert based on at least one of the fixed data or the time varying data satisfying a threshold value based on at least one of (a) historical data associated with operation of another device of a similar model to a model of the device or (b) reference data obtained from the manufacturer and specifying operational characteristics of the model of the device.

### Claim 4 (depends on 3)

The apparatus of claim 3, wherein the threshold value is a first threshold value and the alert generator is to generate the alert in response to at least one of a set of probabilities generated by the machine learning engine satisfying a second threshold value based on one or more trained parameters of the machine learning engine.

### Claim 5 (depends on 3)

The apparatus of claim 3, wherein the historical data includes one or more of Pareto chart data, past heartbeat data, or at least one past failure mode.

### Claim 6 (depends on 3)

The apparatus of claim 3, further including:
a failure mode comparator to compare the time varying data to at least one of the historical data or the reference data; and
a report generator to track the time varying data over time.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the device is a watermark encoder.

### Claim 8

An apparatus to monitor performance of one or more devices, the apparatus comprising:
one or more non-transitory computer readable media;
instructions in the apparatus; and
processor circuitry to execute the instructions to at least:
deploy an SDK associated with a measurement entity to a manufacturer of a device, the SDK to define heartbeat data to be collected from the device and interfacing techniques to transmit the heartbeat data from the device to the measurement entity, the heartbeat data including time varying data and fixed data;
collect, via a network, the heartbeat data from the device;
process the heartbeat data to predict whether the device is associated with one or more failure modes;
generate an alert based on a prediction associated with a first one of the one or more failure modes, the alert to indicate at least one of (a) a type of the first one of the failure modes or (b) at least one component of the device to be remedied according to the first one of the one or more failure modes; and
transmit the alert to a management agent of the device.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the manufacturer is a first manufacturer, the device is a first device, the heartbeat data is first heartbeat data, the one or more failure modes are one or more first failure modes, the prediction is a first prediction, the alert is a first alert, the management agent is a first management agent, and the processor circuitry is to:
deploy the SDK to a second manufacturer of a second device, the SDK to define second heartbeat data to be collected from the second device and interfacing techniques to transmit the second heartbeat data from the second device to the measurement entity, the second manufacturer different from the first manufacturer, the second device different from the first device, the first heartbeat data different than the second heartbeat data;
collect the second heartbeat data from the second device;
process the second heartbeat data to predict whether the second device is associated with one or more second failure modes;
generate a second alert based on a second prediction associated with a first one of the one or more second failure modes, the second alert to indicate at least one of (a) a type of the first one of the second failure modes or (b) at least one component of the second device to be remedied according to the first one of the one or more second failure modes; and
transmit the second alert to a second management agent of the second device.

### Claim 10 (depends on 8)

The apparatus of claim 8, wherein the alert is a first alert and the processor circuitry is to generate a second alert based on at least one of the fixed data or the time varying data satisfying a threshold value based on at least one of (a) historical data associated with operation of another device of a similar model to a model of the device or (b) reference data obtained from the manufacturer and specifying operational characteristics of the model of the device.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein the threshold value is a first threshold value and the processor circuitry is to generate the alert in response to at least one of a set of probabilities generated by a machine learning model satisfying a second threshold value based on one or more trained parameters of the machine learning model.

### Claim 12 (depends on 10)

The apparatus of claim 10, wherein the historical data includes one or more of Pareto chart data, past heartbeat data, or at least one past failure mode.

### Claim 13 (depends on 10)

The apparatus of claim 10, wherein the processor circuitry is to:
compare the time varying data to at least one of the historical data or the reference data; and
track the time varying data over time.

### Claim 14 (depends on 8)

The apparatus of claim 8, wherein the device is a watermark encoder.

### Claim 15

At least one non-transitory computer readable medium comprising instructions that, when executed, cause at least one processor to at least:
deploy an SDK associated with a measurement entity to a manufacturer of a device, the SDK to define heartbeat data to be collected from the device and interfacing techniques to transmit the heartbeat data from the device to the measurement entity, the heartbeat data including time varying data and fixed data;
collect, via a network, the heartbeat data from the device;
process the heartbeat data to predict whether the device is associated with one or more failure modes;
generate an alert based on a prediction associated with a first one of the one or more failure modes, the alert to indicate at least one of (a) a type of the first one of the failure modes or (b) at least one component of the device to be remedied according to the first one of the one or more failure modes; and
transmit the alert to a management agent of the device.

### Claim 16 (depends on 15)

The at least one non-transitory computer readable medium of claim 15, wherein the manufacturer is a first manufacturer, the device is a first device, the heartbeat data is first heartbeat data, the one or more failure modes are one or more first failure modes, the prediction is a first prediction, the alert is a first alert, the management agent is a first management agent, and the instructions, when executed, cause the at least one processor to:
deploy the SDK to a second manufacturer of a second device, the SDK to define second heartbeat data to be collected from the second device and interfacing techniques to transmit the second heartbeat data from the second device to the measurement entity, the second manufacturer different from the first manufacturer, the second device different from the first device, the first heartbeat data different than the second heartbeat data;
collect the second heartbeat data from the second device;
process the second heartbeat data to predict whether the second device is associated with one or more second failure modes;
generate a second alert based on a second prediction associated with a first one of the one or more second failure modes, the second alert to indicate at least one of (a) a type of the first one of the second failure modes or (b) at least one component of the second device to be remedied according to the first one of the one or more second failure modes; and
transmit the second alert to a second management agent of the second device.

### Claim 17 (depends on 15)

The at least one non-transitory computer readable medium of claim 15, wherein the alert is a first alert and the instructions, when executed, cause the at least one processor to generate a second alert based on at least one of the fixed data or the time varying data satisfying a threshold value based on at least one of (a) historical data associated with operation of another device of a similar model to a model of the device or (b) reference data obtained from the manufacturer and specifying operational characteristics of the model of the device.

### Claim 18 (depends on 17)

The at least one non-transitory computer readable medium of claim 17, wherein the threshold value is a first threshold value and the instructions, when executed, cause the at least one processor to generate the alert in response to at least one of a set of probabilities generated by a machine learning model satisfying a second threshold value based on one or more trained parameters of the machine learning model.

### Claim 19 (depends on 17)

The at least one non-transitory computer readable medium of claim 17, wherein the historical data includes one or more of Pareto chart data, past heartbeat data, or at least one past failure mode.

### Claim 20 (depends on 17)

The at least one non-transitory computer readable medium of claim 17, wherein the instructions, when executed, cause the at least one processor to:
compare the time varying data to at least one of the historical data or the reference data; and
track the time varying data over time.
