RDS/RBDS Transmitter Data Storage Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

RF transmitters face challenges in minimizing storage and interaction time with hosts for recurring RDS/RBDS data, leading to increased costs and power consumption due to limited storage capacity and frequent data retrieval.

Innovation Solution

Implementing a transmitter with first circuitry to store a first instance of recurring RDS/RBDS data and prevent subsequent instances from being stored, while generating multiple RDS/RBDS groups using portions of the initial data, thereby minimizing storage needs and interaction time with the host.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the transmitter stores multiple instances of recurring RDS/RBDS data, then data transmission reliability is improved, but storage requirements increase

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The transmitter stores only the first instance of recurring RDS/RBDS data in advance, and uses this stored data to generate subsequent groups through parameter modification. This preliminary storage action eliminates the need to store multiple complete instances, reducing storage requirements while maintaining transmission reliability through intelligent data generation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of storing multiple original instances of RDS/RBDS data, the system creates copies by modifying parameters of the first stored instance. The transmitter generates subsequent data groups by applying different parameters to the stored template, effectively creating needed variations without duplicating the entire data set in storage.

Inventive Principle:
Principle #26Copying

2Loss of information

If the transmitter retrieves RDS/RBDS data frequently from the host, then data freshness is improved, but interaction time with host increases

Engineering Contradiction:
Improvedata freshnessVSAvoidinteraction time with host
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary data retrieval by storing the first instance of RDS/RBDS data when it is initially received from the host. This advance action eliminates the need for frequent real-time interactions with the host, as the transmitter can generate subsequent data groups locally using stored data and parameter updates, significantly reducing interaction time while maintaining data freshness.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The transmitter serves itself by generating subsequent RDS/RBDS data groups internally using the stored first instance and parameter modifications. Instead of continuously requesting data from the host, the system autonomously produces needed data variations, reducing dependency on host interaction while ensuring data remains current through parameter updates.

Inventive Principle:
Principle #25Self-service

3Loss of information

If the transmitter stores complete RDS/RBDS data instances, then data completeness is improved, but storage capacity requirements increase

Engineering Contradiction:
Improvedata completenessVSAvoidstorage capacity
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The system extracts and stores only the essential first instance of RDS/RBDS data, separating it from subsequent redundant instances. By taking out only what is necessary for initial storage and using parameter modifications to generate variations, the transmitter maintains data completeness while minimizing storage capacity requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of storing complete multiple instances, the system stores one complete instance and creates necessary variations through parameter copying and modification. This approach preserves all essential information while avoiding redundant storage of identical or highly similar data sets.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8060066B2System and method for transmitting RDS/RBDS data
Publication Date: 2011.11.15 SKYWORKS SOLUTIONS INC
  • US8060066B2 patent drawing
  • US8060066B2 patent drawing
  • US8060066B2 patent drawing

AI summary

A receiver including first circuitry configured to combine corresponding soft decision values from at least two groups of RDS/RBDS data transmitted as part of a broadcast channel to generate a set of combined values and second circuitry configured to identify a subset of the combined values that indicate a relatively constant subset of the received values from the at least two groups of the RDS/RBDS data is provided.