CA2766479A1

CA2766479A1 - Digital radio broadcast receiver, broadcasting methods and methods for tagging content of interest

Info

Publication number: CA2766479A1
Application number: CA2766479A
Authority: CA
Inventors: Steven Andrew Johnson; Robert Michael Dillon; Harvey Chalmers
Original assignee: Ibiquity Digital Corp
Current assignee: Ibiquity Digital Corp
Priority date: 2009-07-31
Filing date: 2010-08-02
Publication date: 2011-02-03
Anticipated expiration: 2030-08-02
Also published as: CA2766479C; CN102549933A; MX2012000800A; BR112012002206A2; WO2011014867A1; CN102549933B

Abstract

A digital radio broadcast system includes a processing system that receives first audio content, first program data identifying a first item for the first audio content, second audio content, and second program data identifying a second item for the second audio content such that a start of the first program data is received at the processing system within 0.5 seconds of a start of the first audio content. A digital radio broadcast signal including the audio content and the program data is processed for digital radio broadcast transmission via a transmitter. The processing system stops delivery of the first program data to the transmitter upon receipt of the second program data, the first program data thereby being truncated, and begins delivery of the second program data to the transmitter. A digital radio broadcast receiver can tag content of interest based on a user command registered at the receiver.

Description

DIGITAL RADIO BROADCAST RECEIVER, BROADCASTING METHODS AND
METHODS FOR TAGGING CONTENT OF INTEREST

This application claims the benefit of U.S. Provisional Patent Application No.
61/213,943 filed July 31, 2009, the entire contents of which are incorporated herein by reference.

FIELD OF THE INVENTION

[0001] This invention relates to digital radio broadcasting receivers, and more particularly to methods and apparatus for receiving digital radio broadcast content and for collecting information pertaining to the content and tagging content of interest.

BACKGROUND

[0002] Digital radio broadcasting technology delivers digital audio and data services to mobile, portable, and fixed receivers. One type of digital radio broadcasting, referred to as in-band on-channel (IBOC) digital audio broadcasting (DAB), uses terrestrial transmitters in the existing Medium Frequency (MF) and Very High Frequency (VHF) radio bands. HD
Radio Technology, developed by iBiquity Digital Corporation, is one example of an IBOC

implementation for digital radio broadcasting and reception.

[0003] IBOC DAB signals can be transmitted in a hybrid format including an analog modulated carrier in combination with a plurality of digitally modulated carriers or in an all-digital format wherein the analog modulated carrier is not used. Using the hybrid mode, broadcasters may continue to transmit analog AM and FM simultaneously with higher-quality and more robust digital signals, allowing themselves and their listeners to convert from analog-to-digital radio while maintaining their current frequency allocations.

[0004] One feature of digital transmission systems is the inherent ability to simultaneously transmit both digitized audio and data. Thus the technology also allows for wireless data services from AM and FM radio stations. The broadcast signals can include metadata, such as the artist, song title, or station call letters. Special messages about events, traffic, and weather can also be included. For example, traffic information, weather forecasts, news, and sports scores can all be scrolled across a radio receiver's display while the user listens to a radio station.

[0005] IBOC DAB technology can provide digital quality audio, superior to existing analog broadcasting formats. Because each IBOC DAB signal is transmitted within the spectral mask of an existing AM or FM channel allocation, it requires no new spectral allocations. IBOC
DAB promotes economy of spectrum while enabling broadcasters to supply digital quality audio to the present base of listeners.

[0006] Multicasting, the ability to deliver several programs or data streams over one channel in the AM or FM spectrum, enables stations to broadcast multiple streams of data on separate supplemental or sub-channels of the main frequency. For example, multiple streams of data can include alternative music formats, local traffic, weather, news, and sports. The supplemental channels can be accessed in the same manner as the traditional station frequency using tuning or seeking functions. For example, if the analog modulated signal is centered at 94.1 MHz, the same broadcast in IBOC DAB can include supplemental channels 94.1-1, 94.1-2, and 94.1-3. Highly specialized programming on supplemental channels can be delivered to tightly targeted audiences, creating more opportunities for advertisers to integrate their brand with program content. As used herein, multicasting includes the transmission of one or more programs in a single digital radio broadcasting channel or on a single digital radio broadcasting signal. Multicast content can include a main program service (MPS), supplemental program services (SPS), program service data (PSD), and/or other broadcast data.

[0007] The National Radio Systems Committee, a standard-setting organization sponsored by the National Association of Broadcasters and the Consumer Electronics Association, adopted an IBOC standard, designated NRSC-5B,. NRSC-5B, the disclosure of which is incorporated herein by reference, sets forth the requirements for broadcasting digital audio and ancillary data over AM and FM broadcast channels. The standard and its reference documents contain detailed explanations of the RF/transmission subsystem and the transport and service multiplex subsystems. Copies of the standard can be obtained from the NRSC at https://www.nrscstandards.org. iBiquity's HD RadioTM Technology is an implementation of the NRSC-5B IBOC standard. Further information regarding HD Radio Technology can be found at www.hdradio.com and www.ibiguity.com.

[0008] Other types of digital radio broadcasting systems include satellite systems such as XM Radio, Sirius and WorldSpace, and terrestrial systems such as Digital Radio Mondiale (DRM), Eureka 147 (branded as DAB), DAB Version 2, and FMeXtra. As used herein, the phrase "digital radio broadcasting" encompasses digital audio broadcasting including in-band on-channel broadcasting, as well as other digital terrestrial broadcasting and satellite broadcasting.

[0009] Various approaches have been proposed for purchasing an item of interest by entering a command at a radio broadcast receiver based on digital data and content received with the receiver. For example, U. S. Patent No. 6,925,489 describes an approach in which identification information is extracted from a current broadcast of a piece of music or other type of information of interest to a user using a digital audio broadcast receiver in response to a user command and stored in a memory or other storage device. The extracted information is then later delivered over a network connection to a server which permits the user to purchase the corresponding item U.S. Patent No. 6,957,041 describes an approach in which a listener can respond to items in a radio broadcast such as music, advertisements, fund raising drives, or interactive listener polls during the broadcast, wherein data such as song title and artist, author or publisher, and IP address for the location of the digital content is transmitted using the RBDS/RDS data stream. Purchase requests can then be transmitted via wireless transmission or by accessing the Internet using a personal computer or wireless phone. U.S.
Patent No. 7,010,263 describes an approach in which a satellite radio receiver accepts user input identifying interest in music or data being played and/or displayed such that an ID
signal is stored on removable media identifying the selection being played and/or displayed.
The user can then download or place an order for the desired selection from a web site.

[0010] The present inventors have observed that in some applications ambiguities may arise in tagging content of interest in digital radio broadcast systems because program service data identifying an item of interest may not be entirely aligned temporally with the audio content heard by the user. The present inventors have identified a need for enhancing the temporal alignment at the receiver of program service data and the audio content (e.g., songs, advertising, etc.) to which the program service data corresponds to reduce ambiguities in identifying content of interest tagged by a user and to improve the user experience in tagging content of interest.

SUMMARY

[0011] According to an exemplary embodiment, a digital radio broadcast system implementing a method for scheduling audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver is described. The system comprises a processing system and a memory coupled to the processing system. The processing system is configured to receive first audio content, first program data, second audio content, and second program data for transmission via digital radio broadcast, the first program data identifying a first item associated with the first audio content, the second program data identifying a second item associated with the second audio content. The processing system is also configured to receive the first program data and the first audio content at the processing system such that a start of the first program data is received at the processing system within 0.5 seconds of a start of the first audio content received at the processing system. The processing system is also configured to generate a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content, and the second program data for transmission via digital radio broadcast. The processing system is also configured to stop delivery of the first program data to the digital radio broadcast transmitter upon receipt of the second program data, the first program data thereby being truncated, and to begin delivery of the second program data to the digital radio broadcast transmitter. A non-transitory computer readable storage medium may contain instructions for causing the processing system to carry out methods of scheduling transmission of the audio content and associated program data.

[0012] According to another exemplary embodiment a digital radio broadcast receiver configured to receive audio content and associated program data via digital radio broadcast and permit user identification of content of interest is described. The digital radio broadcast receiver comprises a processing system, a memory coupled to the processing system, and a user interface for receiving user commands entered thereto. The processing system is configured to process a digital radio broadcast signal received by the receiver, the digital radio broadcast signal comprising first audio content and first program data, the first program data comprising information identifying a first item associated with the first audio content, and second audio content and second program data, the second program data comprising information identifying a second item associated with the second audio content. The processing system is also configured to register a user command entered at a user interface of the receiver during reception of either the first audio content or the second audio content, the user command indicating a user's interest in either the first audio content or the second audio content, respectively.
The processing system is also configured to receive the first audio content and first program data such that a start of the first program data and a start of the first audio content are aligned to within 3 seconds of one another without the digital radio broadcast receiver processing the digital radio broadcast signal to enhance the alignment of the first program data and the first audio content. A non-transitory computer readable storage medium may contain instructions for causing the processing system of the receiver to carry out methods of registering user identification of content of interest.

[0013] According to another exemplary embodiment, a digital radio system for scheduling audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver and for specifying content of interest is described.
The digital radio system comprises a broadcast system comprising a processing system and a memory coupled to the processing system, and a digital radio broadcast receiver. The processing system of the broadcast system is configured to: receive first audio content, first program data, second audio content, and second program data for transmission via digital radio broadcast, the first program data identifying a first item associated with the first audio content, the second program data identifying a second item associated with the second audio content; receive the first program data and the first audio content such that a start of the first program data is received at the processing system within 0.5 seconds of a start of the first audio content received at the processing system; generate a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content, and the second program data for digital radio broadcast transmission via a digital radio broadcast transmitter; and stop delivery of the first program data to the digital radio broadcast transmitter upon receipt of the second program data, the first program data thereby being truncated, and to begin delivery of the second program data to the digital radio broadcast transmitter. The digital broadcast receiver is configured to: process a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content and the first program data, such that a start of the first program data and a start of the first audio content are aligned at the receiver to within 3 seconds of one another without the digital radio broadcast receiver processing the digital radio broadcast signal to enhance the alignment of the first program data and the first audio content;
register a user command entered at a user interface of the receiver during reception of either the first audio content or the second audio content, the user command indicating a user's interest in either the first audio content or the second audio content, respectively; determine whether there is an ambiguity associated with the user's interest in either the first audio content or the second audio content; and if there is an ambiguity, store a first data structure identifying the first item associated with the first audio content and store a second data structure identifying the second item associated with the second audio content. Non-transitory computer readable storage media may contain instructions for causing the processing systems of the broadcast system and the receiver to carry out methods of scheduling transmission audio content and program data and of registering user identification of content of interest.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG. 1 is a block diagram of a transmitter for use in an in-band on-channel digital radio broadcasting system.

[0015] FIG. 2 is a schematic representation of a hybrid FM IBOC waveform.

[0016] FIG. 3 is a schematic representation of an extended hybrid FM IBOC
waveform.

[0017] FIG. 4 is a schematic representation of an all-digital FM IBOC
waveform.

[0018] FIG. 5 is a schematic representation of a hybrid AM IBOC DAB waveform.

[0019] FIG. 6 is a schematic representation of an all-digital AM IBOC DAB
waveform.

[0020] FIG. 7 is a functional block diagram of an AM IBOC DAB receiver.

[0021] FIG. 8 is a functional block diagram of an FM IBOC DAB receiver.

[0022] FIGs. 9a and 9b are diagrams of an IBOC DAB logical protocol stack from the broadcast perspective.

[0023] FIG. 10 is a diagram of an IBOC DAB logical protocol stack from the receiver perspective.

[0024] FIG. 11 illustrates an exemplary digital radio broadcast receiver 300 operating in the context of an overall system for implementing a purchase or request for information related to audio content currently received, according to an exemplary embodiment.

[0025] FIG. 12 illustrates an exemplary screen display associated with software for obtaining information about items of interest according to one example.

[0026] FIG. 13 illustrates another exemplary screen display associated with software for obtaining information about items of interest according to another example.

[0027] FIG. 14 illustrates the format of a general UFID frame that conforms to the ID3 standard (top) and exemplary Owner Identifier and Identifier information (bottom) structured according to one example.

[0028] FIG. 15 illustrates a table that describes various fields of the UFID
illustrated in FIG. 14 according to one example.

[0029] FIG. 16 illustrates an exemplary UFID format containing purchase information with one ID code according to one example.

[0030] FIG. 17 illustrates a table describing various types of purchase codes according to one example.

[0031] FIG. 18 illustrates an exemplary UFID format containing purchase information with multiple ID codes according to another example.

[0032] FIG. 19 schematically illustrates hierarchical encoding of Type and Format information in a UFID according to one example.

[0033] FIG. 20 illustrates exemplary scenarios regarding the relative timing of the start of audio content and the start of the associated PSD data according to one example.

[0034] FIG. 21 illustrates an exemplary method for specifying content of interest using a digital radio broadcast receiver according to one embodiment.

[0035] FIG. 22A illustrates a table describing the field format of an exemplary purchase token as an example of a data structure.

[0036] FIG. 22B illustrates another table describing the field format of alternative exemplary purchase token as another example of a data structure.

[0037] FIG. 23 illustrates another exemplary method for specifying content of interest using a digital radio broadcast receiver according to another embodiment.

[0038] FIG. 24 is a functional block diagram illustrating an exemplary approach for scheduling audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver according to another embodiment.

[0039] FIG. 25 is a functional block diagram illustrating another exemplary approach for scheduling audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver according to another embodiment.

[0040] FIG. 26 illustrates an exemplary method for specifying content of interest using a digital radio broadcast receiver according to another embodiment.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

[0041] FIGs. 1-10 and the accompanying description herein provide a description of an exemplary IBOC system, including broadcasting equipment structure and operation, exemplary receiver structure and operation including functionality for storing information in response to a user command to specify an item of interest related to a received digital radio broadcast, and the structure of IBOC DAB waveforms. FIGs. 11-26 and the accompanying description herein provide further description of exemplary structure and operation of a digital radio broadcast receiver for storing information regarding an item of interest in response to a user command, exemplary data formats at both the broadcast and receiver sides, and exemplary approaches for obtaining information about the item of interest via a network such as the Internet (e.g., for purchasing the item).

IBOC SYSTEM AND WAVEFORMS

[0042] Referring to the drawings, FIG. 1 is a functional block diagram of the relevant components of a studio site 10, an FM transmitter site 12, and a studio transmitter link (STL) 14 that can be used to broadcast an FM IBOC DAB signal. The studio site includes, among other things, studio automation equipment 34, an Ensemble Operations Center (EOC) 16 that includes an importer 18, an exporter 20, an exciter auxiliary service unit (EASU) 22, and an STL
transmitter 48. The transmitter site includes an STL receiver 54, a digital exciter 56 that includes an exciter engine (engine) subsystem 58, and an analog exciter 60.
While in FIG. 1 the exporter is resident at a radio station's studio site and the exciter is located at the transmission site, these elements may be co-located at the transmission site.

[0043] At the studio site, the studio automation equipment supplies main program service (MPS) audio 42 to the EASU, MPS data 40 to the exporter, supplemental program service (SPS) audio 38 to the importer, and SPS data 36 to the importer. MPS
audio serves as the main audio programming source. In hybrid modes, it preserves the existing analog radio programming formats in both the analog and digital transmissions. MPS data, also known as program service data (PSD), includes information such as music title, artist, album name, etc.
Supplemental program service can include supplementary audio content as well as program associated data.

[0044] The importer contains hardware and software for supplying advanced application services (AAS). A "service" is content that is delivered to users via an IBOC
DAB broadcast, and AAS can include any type of data that is not classified as MPS, SPS, or Station Information Service (SIS). SIS provides station information, such as call sign, absolute time, position correlated to GPS, etc. Examples of AAS data include real-time traffic and weather information, navigation map updates or other images, electronic program guides, multimedia programming, other audio services, and other content. The content for AAS can be supplied by service providers 44, which provide service data 46 to the importer via an application program interface (API). The service providers may be a broadcaster located at the studio site or externally sourced third-party providers of services and content. The importer can establish session connections between multiple service providers. The importer encodes and multiplexes service data 46, SPS audio 38, and SPS data 36 to produce exporter link data 24, which is output to the exporter via a data link.

[0045] The exporter 20 contains the hardware and software necessary to supply the main program service and SIS for broadcasting. The exporter accepts digital MPS
audio 26 over an audio interface and compresses the audio. The exporter also multiplexes MPS
data 40, exporter link data 24, and the compressed digital MPS audio to produce exciter link data 52. In addition, the exporter accepts analog MPS audio 28 over its audio interface and applies a pre-programmed delay to it to produce a delayed analog MPS audio signal 30. This analog audio can be broadcast as a backup channel for hybrid IBOC DAB broadcasts. The delay compensates for the system delay of the digital MPS audio, allowing receivers to blend between the digital and analog program without a shift in time. In an AM transmission system, the delayed MPS audio signal 30 is converted by the exporter to a mono signal and sent directly to the STL as part of the exciter link data 52.

[0046] The EASU 22 accepts MPS audio 42 from the studio automation equipment, rate converts it to the proper system clock, and outputs two copies of the signal, one digital (26) and one analog (28). The EASU includes a GPS receiver that is connected to an antenna 25. The GPS receiver allows the EASU to derive a master clock signal, which is synchronized to the exciter's clock by use of GPS units. The EASU provides the master system clock used by the exporter. The EASU is also used to bypass (or redirect) the analog MPS audio from being passed through the exporter in the event the exporter has a catastrophic fault and is no longer operational. The bypassed audio 32 can be fed directly into the STL
transmitter, eliminating a dead-air event.

[0047] STL transmitter 48 receives delayed analog MPS audio 50 and exciter link data 52. It outputs exciter link data and delayed analog MPS audio over STL link 14, which may be either unidirectional or bidirectional. The STL link may be a digital microwave or Ethernet link, for example, and may use the standard User Datagram Protocol or the standard TCP/IP.

[0048] The transmitter site includes an STL receiver 54, an exciter 56 and an analog exciter 60. The STL receiver 54 receives exciter link data, including audio and data signals as well as command and control messages, over the STL link 14. The exciter link data is passed to the exciter 56, which produces the IBOC DAB waveform. The exciter includes a host processor, digital up-converter, RF up-converter, and exgine subsystem 58. The exgine accepts exciter link data and modulates the digital portion of the IBOC DAB waveform.
The digital up-converter of exciter 56 converts from digital-to-analog the baseband portion of the exgine output. The digital-to-analog conversion is based on a GPS clock, common to that of the exporter's GPS-based clock derived from the EASU. Thus, the exciter 56 includes a GPS unit and antenna 57. An alternative method for synchronizing the exporter and exciter clocks can be found in United States Patent No. 7,512,175, the disclosure of which is hereby incorporated by reference in its entirety. The RF up-converter of the exciter up-converts the analog signal to the proper in-band channel frequency. The up-converted signal is then passed to the high power amplifier 62 and antenna 64 for broadcast. In an AM transmission system, the exgine subsystem coherently adds the backup analog MPS audio to the digital waveform in the hybrid mode; thus, the AM transmission system does not include the analog exciter 60. In addition, the exciter 56 produces phase and magnitude information and the analog signal is output directly to the high power amplifier.

[0049] IBOC DAB signals can be transmitted in both AM and FM radio bands, using a variety of waveforms. The waveforms include an FM hybrid IBOC DAB waveform, an FM all-digital IBOC DAB waveform, an AM hybrid IBOC DAB waveform, and an AM all-digital IBOC DAB waveform.

[0050] FIG. 2 is a schematic representation of a hybrid FM IBOC waveform 70.
The waveform includes an analog modulated signal 72 located in the center of a broadcast channel 74, a first plurality of evenly spaced orthogonally frequency division multiplexed subcarriers 76 in an upper sideband 78, and a second plurality of evenly spaced orthogonally frequency division multiplexed subcarriers 80 in a lower sideband 82. The digitally modulated subcarriers are divided into partitions and various subcarriers are designated as reference subcarriers. A
frequency partition is a group of 19 OFDM subcarriers containing 18 data subcarriers and one reference subcarrier.

[0051] The hybrid waveform includes an analog FM-modulated signal, plus digitally modulated primary main subcarriers. The subcarriers are located at evenly spaced frequency locations. The subcarrier locations are numbered from -546 to +546. In the waveform of FIG.
2, the subcarriers are at locations +356 to +546 and -356 to -546. Each primary main sideband is comprised of ten frequency partitions. Subcarriers 546 and -546, also included in the primary main sidebands, are additional reference subcarriers. The amplitude of each subcarrier can be scaled by an amplitude scale factor.

[0052] FIG. 3 is a schematic representation of an extended hybrid FM IBOC
waveform 90. The extended hybrid waveform is created by adding primary extended sidebands 92, 94 to the primary main sidebands present in the hybrid waveform. One, two, or four frequency partitions can be added to the inner edge of each primary main sideband. The extended hybrid waveform includes the analog FM signal plus digitally modulated primary main subcarriers (subcarriers +356 to +546 and -356 to -546) and some or all primary extended subcarriers (subcarriers +280 to +355 and -280 to -355).

[0053] The upper primary extended sidebands include subcarriers 337 through 355 (one frequency partition), 318 through 355 (two frequency partitions), or 280 through 355 (four frequency partitions). The lower primary extended sidebands include subcarriers -337 through -355 (one frequency partition), -318 through -355 (two frequency partitions), or -280 through -355 (four frequency partitions). The amplitude of each subcarrier can be scaled by an amplitude scale factor.

[0054] FIG. 4 is a schematic representation of an all-digital FM IBOC waveform 100.
The all-digital waveform is constructed by disabling the analog signal, fully expanding the bandwidth of the primary digital sidebands 102, 104, and adding lower-power secondary sidebands 106, 108 in the spectrum vacated by the analog signal. The all-digital waveform in the illustrated embodiment includes digitally modulated subcarriers at subcarrier locations -546 to +546, without an analog FM signal.

[0055] In addition to the ten main frequency partitions, all four extended frequency partitions are present in each primary sideband of the all-digital waveform.
Each secondary sideband also has ten secondary main (SM) and four secondary extended (SX) frequency partitions. Unlike the primary sidebands, however, the secondary main frequency partitions are mapped nearer to the channel center with the extended frequency partitions farther from the center.

[0056] Each secondary sideband also supports a small secondary protected (SP) region 110, 112 including 12 OFDM subcarriers and reference subcarriers 279 and -279.
The sidebands are referred to as "protected" because they are located in the area of spectrum least likely to be affected by analog or digital interference. An additional reference subcarrier is placed at the center of the channel (0). Frequency partition ordering of the SP region does not apply since the SP region does not contain frequency partitions.

[0057] Each secondary main sideband spans subcarriers 1 through 190 or -1 through -190. The upper secondary extended sideband includes subcarriers 191 through 266, and the upper secondary protected sideband includes subcarriers 267 through 278, plus additional reference subcarrier 279. The lower secondary extended sideband includes subcarriers -191 through -266, and the lower secondary protected sideband includes subcarriers -267 through -278, plus additional reference subcarrier -279. The total frequency span of the entire all-digital spectrum is 396,803 Hz. The amplitude of each subcarrier can be scaled by an amplitude scale factor. The secondary sideband amplitude scale factors can be user selectable.
Any one of the four may be selected for application to the secondary sidebands.

[0058] In each of the waveforms, the digital signal is modulated using orthogonal frequency division multiplexing (OFDM). OFDM is a parallel modulation scheme in which the data stream modulates a large number of orthogonal subcarriers, which are transmitted simultaneously. OFDM is inherently flexible, readily allowing the mapping of logical channels to different groups of subcarriers.

[0059] In the hybrid waveform, the digital signal is transmitted in primary main (PM) sidebands on either side of the analog FM signal in the hybrid waveform. The power level of each sideband is appreciably below the total power in the analog FM signal.
The analog signal may be monophonic or stereo, and may include subsidiary communications authorization (SCA) channels.

[0060] In the extended hybrid waveform, the bandwidth of the hybrid sidebands can be extended toward the analog FM signal to increase digital capacity. This additional spectrum, allocated to the inner edge of each primary main sideband, is termed the primary extended (PX) sideband.

[0061] In the all-digital waveform, the analog signal is removed and the bandwidth of the primary digital sidebands is fully extended as in the extended hybrid waveform. In addition, this waveform allows lower-power digital secondary sidebands to be transmitted in the spectrum vacated by the analog FM signal.

[0062] FIG. 5 is a schematic representation of an AM hybrid IBOC DAB waveform 120. The hybrid format includes the conventional AM analog signal 122 (bandlimited to about kHz) along with a nearly 30 kHz wide DAB signal 124. The spectrum is contained within a channel 126 having a bandwidth of about 30 kHz. The channel is divided into upper 130 and lower 132 frequency bands. The upper band extends from the center frequency of the channel to about + 15 kHz from the center frequency. The lower band extends from the center frequency to about -15 kHz from the center frequency.

[0063] The AM hybrid IBOC DAB signal format in one example comprises the analog modulated carrier signal 134 plus OFDM subcarrier locations spanning the upper and lower bands. Coded digital information representative of the audio or data signals to be transmitted (program material), is transmitted on the subcarriers. The symbol rate is less than the subcarrier spacing due to a guard time between symbols.

[0064] As shown in FIG. 5, the upper band is divided into a primary section 136, a secondary section 138, and a tertiary section 144. The lower band is divided into a primary section 140, a secondary section 142, and a tertiary section 143. For the purpose of this explanation, the tertiary sections 143 and 144 can be considered to include a plurality of groups of subcarriers labeled 146, 148, 150 and 152 in FIG. 5. Subcarriers within the tertiary sections that are positioned near the center of the channel are referred to as inner subcarriers, and subcarriers within the tertiary sections that are positioned farther from the center of the channel are referred to as outer subcarriers. In this example, the power level of the inner subcarriers in groups 148 and 150 is shown to decrease linearly with frequency spacing from the center frequency. The remaining groups of subcarriers 146 and 152 in the tertiary sections have substantially constant power levels. FIG. 5 also shows two reference subcarriers 154 and 156 for system control, whose levels are fixed at a value that is different from the other sidebands.

[0065] The power of subcarriers in the digital sidebands is significantly below the total power in the analog AM signal. The level of each OFDM subcarrier within a given primary or secondary section is fixed at a constant value. Primary or secondary sections may be scaled relative to each other. In addition, status and control information is transmitted on reference subcarriers located on either side of the main carrier. A separate logical channel, such as an IBOC Data Service (IDS) channel can be transmitted in individual subcarriers just above and below the frequency edges of the upper and lower secondary sidebands. The power level of each primary OFDM subcarrier is fixed relative to the unmodulated main analog carrier.
However, the power level of the secondary subcarriers, logical channel subcarriers, and tertiary subcarriers is adjustable.

[0066] Using the modulation format of FIG. 5, the analog modulated carrier and the digitally modulated subcarriers are transmitted within the channel mask specified for standard AM broadcasting in the United States. The hybrid system uses the analog AM
signal for tuning and backup.

[0067] FIG. 6 is a schematic representation of the subcarrier assignments for an all-digital AM IBOC DAB waveform. The all-digital AM IBOC DAB signal 160 includes first and second groups 162 and 164 of evenly spaced subcarriers, referred to as the primary subcarriers, that are positioned in upper and lower bands 166 and 168. Third and fourth groups 170 and 172 of subcarriers, referred to as secondary and tertiary subcarriers respectively, are also positioned in upper and lower bands 166 and 168. Two reference subcarriers 174 and 176 of the third group lie closest to the center of the channel. Subcarriers 178 and 180 can be used to transmit program information data.

[0068] FIG. 7 is a simplified functional block diagram of an AM IBOC DAB
receiver 200. The receiver includes an input 202 connected to an antenna 204, a tuner or front end 206, and a digital down converter 208 for producing a baseband signal on line 210.
An analog demodulator 212 demodulates the analog modulated portion of the baseband signal to produce an analog audio signal on line 214. A digital demodulator 216 demodulates the digitally modulated portion of the baseband signal. Then the digital signal is deinterleaved by a deinterleaver 218, and decoded by a Viterbi decoder 220. A service demultiplexer 222 separates main and supplemental program signals from data signals. A processor 224 processes the program signals to produce a digital audio signal on line 226. The analog and main digital audio signals are blended as shown in block 228, or a supplemental digital audio signal is passed through, to produce an audio output on line 230. A data processor 232 processes the data signals and produces data output signals on lines 234, 236 and 238. The data output signals can include, for example, a station information service (SIS), main program service data (MPSD), supplemental program service data (SPSD), and one or more auxiliary application services (AAS).

[0069] The receiver 200 also includes a user interface 240 that includes a display and control buttons 242, one of which is enabled for entering a user command that allows the user to register an interest in audio content currently being received (e.g., which may be referred to herein as a "buy" or "tag" button). Such user commands could also be entered via voice recognition for receivers so equipped. The user interface 240 may also include an indicator 244 such as a light emitting diode (LED) to indicate that program data such as program service data PSD (MPSD and/or SPSD) is sufficient to generate a data structure (e.g., a "purchase token"
such as described elsewhere herein) corresponding to the audio content currently received and which identifies an associated item for which the user may desire to purchase or request further information. Such a purchase or request can be filled by a merchant via the World Wide Web (WWW) as further described elsewhere herein. The indicator 244 could also be implemented within the display instead of as a separate indicator such as an LED. The user interface 240 also communicates with the tuner 206 to control and display tuning information. The user interface 240 can include a suitable processing unit configured (e.g., programmed) to interpret SIS, PSD, and AAS signals input thereto so as to display information from those signals on the display of the user interface, e.g., such as artist and title, station identification information, visual advertising information, upcoming program features, weather or safety alerts, etc.

[0070] The receiver 200 also includes a purchase module 246 that receives PSD, AAS
and SIS information to process information for a purchase or request for information. The receiver 200 further includes an output interface 248 such as, for example, a data port (e.g., USB
port, serial port, etc.) and/or a wireless interface (e.g., Bluetooth, WiFi, etc.) for exporting the data structure to a suitable device (e.g., removable memory, personal computer, mobile telephone, personal digital assistant, etc.) to facilitate the purchase or request for information.
The user interface 240 communicates with the data processor 232 to register the user's interest in audio content, and the data processor 232 controls the purchase module 246 to store an appropriate data structure (e.g., purchase token) which is used to implement the purchase or request for information. It will be appreciated that the purchase module 246 can be implemented in data processor 232 or any other suitable processor.

[0071] FIG. 8 is a simplified functional block diagram of an FM IBOC DAB
receiver 250. The receiver includes an input 252 connected to an antenna 254 and a tuner or front end 256. A received signal is provided to an analog-to-digital converter and digital down converter 258 to produce a baseband signal at output 260 comprising a series of complex signal samples.
The signal samples are complex in that each sample comprises a "real"
component and an "imaginary" component, which is sampled in quadrature to the real component.
An analog demodulator 262 demodulates the analog modulated portion of the baseband signal to produce an analog audio signal on line 264. The digitally modulated portion of the sampled baseband signal is next filtered by sideband isolation filter 266, which has a pass-band frequency response comprising the collective set of subcarriers fi-fõ present in the received OFDM signal. Filter 268 suppresses the effects of a first-adjacent interferer. Complex signal 298 is routed to the input of acquisition module 296, which acquires or recovers OFDM symbol timing offset or error and carrier frequency offset or error from the received OFDM symbols as represented in received complex signal 298. Acquisition module 296 develops a symbol timing offset At and carrier frequency offset Af, as well as status and control information. The signal is then demodulated (block 272) to demodulate the digitally modulated portion of the baseband signal. Then the digital signal is deinterleaved by a deinterleaver 274, and decoded by a Viterbi decoder 276. A
service demultiplexer 278 separates main and supplemental program signals from data signals.

A processor 280 processes the main and supplemental program signals to produce a digital audio signal on line 282. The analog and main digital audio signals are blended as shown in block 284, or the supplemental program signal is passed through, to produce an audio output on line 286. A data processor 288 processes the data signals and produces data output signals on lines 290, 292 and 294. The data output signals can include, for example, a station information service (SIS), main program service data (MPSD), supplemental program service data (SPSD), and one or more advanced application services (AAS).

[0072] The receiver 250 also includes a user interface 295 that includes a display and control buttons 296, one of which is enabled for entering a user command that allows the user to register an interest audio content currently being received (e.g., a "buy button" or "tag button").
Such user commands could also be entered via voice recognition for receivers so equipped. The user interface 295 may also include an indicator 297 such as an LED to indicate that program data such as program service data PSD (MPSD and/or SPSD) is sufficient to generate a data structure (e.g., a "purchase token") corresponding to the audio content currently received and which identifies an associated item for which the user may desire to purchase or request further information. Such a purchase or request can be filled by a merchant via the World Wide Web (WWW). The indicator 297 could also be implemented within the display instead of as a separate indicator such as an LED. The user interface 295 also communicates with the tuner 256 to control and display tuning information. The user interface 295 can include a suitable processing unit configured (e.g., programmed) to interpret SIS, PSD, and AAS
signals input thereto so as to display information from those signals on the display of the user interface, e.g., such as artist and title, station identification information, visual advertising information, upcoming program features, weather or safety alerts, etc.

[0073] The receiver 250 also includes a purchase module 298 that receives PSD, AAS
and SIS information to process information for such a purchase or request for information. The receiver 250 further includes an output interface 299 such as, for example, a data port (e.g., USB
port, serial port, etc.) and/or a wireless interface (e.g., Bluetooth, WiFi, etc.) for exporting the data structure to a suitable device (e.g., removable memory, personal computer, mobile telephone, personal digital assistant, etc.) to facilitate the purchase or request for information.
The user interface 299 communicates with the data processor 288 to register the user's interest in audio content, and the data processor 288 controls the purchase module 298 to store an appropriate data structure (e.g., purchase token) which is used to implement the purchase or request for information. It will be appreciated that the purchase module can be implemented in data processor 288 or any other suitable processor.

[0074] In practice, many of the signal processing functions shown in the receivers of FIGs. 7 and 8 can be implemented using one or more integrated circuits.

[0075] FIGs. 9a and 9b are diagrams of an IBOC DAB logical protocol stack from the transmitter perspective. From the receiver perspective, the logical stack will be traversed in the opposite direction. Most of the data being passed between the various entities within the protocol stack are in the form of protocol data units (PDUs). A PDU is a structured data block that is produced by a specific layer (or process within a layer) of the protocol stack. The PDUs of a given layer may encapsulate PDUs from the next higher layer of the stack and/or include content data and protocol control information originating in the layer (or process) itself The PDUs generated by each layer (or process) in the transmitter protocol stack are inputs to a corresponding layer (or process) in the receiver protocol stack.

[0076] As shown in FIGs. 9a and 9b, there is a configuration administrator 330, which is a system function that supplies configuration and control information to the various entities within the protocol stack. The configuration/control information can include user defined settings, as well as information generated from within the system such as GPS
time and position.

The service interfaces 331 represent the interfaces for all services except SIS. The service interface may be different for each of the various types of services. For example, for MPS audio and SPS audio, the service interface may be an audio card. For MPS data and SPS data the interfaces may be in the form of different application program interfaces (APIs). For all other data services the interface is in the form of a single API. An audio codec 332 encodes both MPS
audio and SPS audio to produce core (Stream 0) and optional enhancement (Stream 1) streams of MPS and SPS audio encoded packets, which are passed to audio transport 333.
Audio codec 332 also relays unused capacity status to other parts of the system, thus allowing the inclusion of opportunistic data. MPS and SPS data is processed by program service data (PSD) transport 334 to produce MPS and SPS data PDUs, which are passed to audio transport 333.
Audio transport 333 receives encoded audio packets and PSD PDUs and outputs bit streams containing both compressed audio and program service data. The SIS transport 335 receives SIS
data from the configuration administrator and generates SIS PDUs. A SIS PDU can contain station identification and location information, program type, as well as absolute time and position correlated to GPS. The AAS data transport 336 receives AAS data from the service interface, as well as opportunistic bandwidth data from the audio transport, and generates AAS data PDUs, which can be based on quality of service parameters. The transport and encoding functions are collectively referred to as Layer 4 of the protocol stack and the corresponding transport PDUs are referred to as Layer 4 PDUs or L4 PDUs. Layer 2, which is the channel multiplex layer, (337) receives transport PDUs from the SIS transport, AAS data transport, and audio transport, and formats them into Layer 2 PDUs. A Layer 2 PDU includes protocol control information and a payload, which can be audio, data, or a combination of audio and data. Layer 2 PDUs are routed through the correct logical channels to Layer 1 (338), wherein a logical channel is a signal path that conducts Ll PDUs through Layer 1 with a specified grade of service. There are multiple Layer 1 logical channels based on service mode, wherein a service mode is a specific configuration of operating parameters specifying throughput, performance level, and selected logical channels. The number of active Layer 1 logical channels and the characteristics defining them vary for each service mode. Status information is also passed between Layer 2 and Layer 1. Layer 1 converts the PDUs from Layer 2 and system control information into an AM or FM
IBOC DAB waveform for transmission. Layer 1 processing can include scrambling, channel encoding, interleaving, OFDM subcarrier mapping, and OFDM signal generation.
The output of OFDM signal generation is a complex, baseband, time domain pulse representing the digital portion of an IBOC signal for a particular symbol. Discrete symbols are concatenated to form a continuous time domain waveform, which is modulated to create an IBOC waveform for transmission.

[0077] FIG. 10 shows the logical protocol stack from the receiver perspective.
An IBOC waveform is received by the physical layer, Layer 1 (560), which demodulates the signal and processes it to separate the signal into logical channels. The number and kind of logical channels will depend on the service mode, and may include logical channels P1-P3, PID S, S1-S5, and SIDS. Layer 1 produces L1 PDUs corresponding to the logical channels and sends the PDUs to Layer 2 (565), which demultiplexes the Ll PDUs to produce SIS PDUs, AAS PDUs, PSD PDUs for the main program service and any supplemental program services, and Stream 0 (core) audio PDUs and Stream 1 (optional enhanced) audio PDUs. The SIS PDUs are then processed by the SIS transport 570 to produce SIS data, the AAS PDUs are processed by the AAS transport 575 to produce AAS data, and the PSD PDUs are processed by the PSD transport 580 to produce MPS data (MPSD) and any SPS data (SPSD). The SIS data, AAS
data, MPSD
and SPSD are then sent to a user interface 590. The SIS data, if requested by a user, can then be displayed. Likewise, MPSD, SPSD, and any text based or graphical AAS data can be displayed.
The Stream 0 and Stream 1 PDUs are processed by Layer 4, comprised of audio transport 590 and audio decoder 595. There may be up to N audio transports corresponding to the number of programs received on the IBOC waveform. Each audio transport produces encoded MPS
packets or SPS packets, corresponding to each of the received programs. Layer 4 receives control information from the user interface, including commands such as to store or play programs, and to seek or scan for radio stations broadcasting an all-digital or hybrid IBOC
signal. Layer 4 also provides status information to the user interface.

[0078] FIG. 11 illustrates an exemplary digital radio broadcast receiver 300 operating in the context of an overall system for implementing a purchase or request for information related to audio content currently received. The digital radio broadcast receiver 300 may be an IBOC
receiver, such as described in the examples of FIGs. 7 and 8, or any other suitable type of digital terrestrial broadcast receiver or satellite broadcast receiver. In addition to receiving audio content, the digital radio broadcast receiver 300 receives program data (e.g., PSD in an IBOC
receiver implementation) associated with the audio content. Based on information contained in the program data, the digital radio broadcast receiver 300 exports or directly stores a suitable data structure (e.g., a purchase token as described further herein) to a recipient device such as a mobile telephone 330, a digital media player 332, a personal computer (PC) 334, and a removable memory 336 (e.g., memory card, USB style memory stick, etc.) in response to a user command designating an interest in audio content currently received (e.g., music, talk, advertising, or any other type of audio content). The data structure comprises information identifying an associated item for which the user may desire to purchase or request further information, such as music, video, merchandise, subscriptions, or any other type of item of potential interest to the user. The data structure can then be communicated via a PC 334, Internet enabled mobile phone 330, or other suitable device to a network 340 such as the Internet, and ultimately to a suitable service provider or merchant 342, 344, 346 via any suitable software to obtain the item of interest, e.g., via download to the PC 334, mobile phone 330, or via delivery through other means such as mail or courier. In addition, it is possible for the digital radio broadcast receiver 300 to include suitable hardware including any suitable wired or wireless functionality to connect directly to the network 340 without the need for an intermediary recipient device. For example, the digital radio broadcast receiver 300 could be configured within an Internet enabled mobile telephone.

[0079] The digital radio broadcast receiver 300 includes a user interface 302 that includes a display 304, control buttons 306, memory 310, processing system 312, data port 314, wireless interface 316 and antenna 318. The digital radio broadcast receiver 300 may also include a button 320 for entering a user command that allows the user to register an interest in audio content currently being received. Such user commands could also be entered via voice recognition for receivers so equipped.

[0080] The user interface 302 may also include an indicator 308 such as an LED
to indicate that program data such as program service data PSD (MPSD and/or SPSD) is sufficient to generate a data structure (e.g., a "purchase token") corresponding to the audio content currently received and which comprises information identifying an associated item for which the user may desire to purchase or request further information. The program data can be considered sufficient if it contains both the title and artist information. More preferably, the program data should additionally contain Station Information Service (SIS) Network ID and SIS Facility, program number, a Uniform Resource Locator (URL) identifying where information about an item of interest can be obtained or where it can be purchased, and a Unique File Identifier (UFID) code that further identifies the item. These will be further described herein. The indicator 308 could also be implemented within the display (e.g., display of a message) instead of as a separate indicator such as an LED. Such an indicator can be desirable because, for example, an IBOC digital radio broadcast receiver may receive solely analog information in areas where digital radio broadcast is unavailable. Regular analog transmission does not possess the program data necessary to correctly generate a data structure in response to a user interest command such as to "buy" or "tag" content. Moreover, it is possible, though unlikely, that such program data may become corrupted prior to a "buy" or "tag" command. Without such an indicator, a user may unknowingly issue one or more user commands for content of interest believing that those commands have been registered, to later find when attempting to implement a purchase that the required information is not present. This could result in a very unsatisfying user experience. The digital radio broadcast receiver 300 may also be configured such that the processing system 312 can cause the indicator 308 to blink on and off when the user's command was properly recorded (e.g., when a valid data structure described elsewhere herein was properly stored to memory 310 in response to a user command). Should the indicator fail to blink, the user would understand that there was a problem recording the user command (e.g., insufficient memory, corrupt data, etc.). A properly recorded user command could also be communicated by displaying a corresponding message on the display 304, and a problem with such a user command could also be displayed on the display 304, e.g., with a blinking error message.

[0081] The memory 310 can comprise any suitable type of memory, and the processing system 312 can comprise one or more processing units implementing suitable software and/or firmware, specialized circuitry, or combination thereof The processing system 312 (e.g., implementing a purchase module 246, 298 such as illustrated in FIGs 7 and 8) is configured (e.g., programmed) to store an appropriate data structure (e.g., a purchase token as described elsewhere herein) which is used to implement the purchase or request for information corresponding to audio content currently received. In one example, the memory 310 can possess 32K bytes or more of storage capacity so as to be able to store at least 64 purchase tokens, each having sizes of 512 bytes. As noted above, the data structure comprises information identifying an associated item for which the user may desire to purchase or request further information. The data port 314 can be any suitable data port such as a USB port, serial port, or specialized port compatible with devices such as various types of digital media players.

[0082] The data port 314 can be used to export one or more data structures stored in the digital radio broadcast receiver 300 to recipient devices such as a mobile telephone 330, a digital media player 332, a personal computer (PC) 334, and a removable memory 336 (e.g., memory card, USB style memory stick, etc.) in response to the user command designating an interest in audio content currently received. If a removable memory 336, PC 334, or digital media player 332, for example, are coupled to the digital radio broadcast receiver 300 when the user command is entered, the data structure can be directly stored to those devices rather than storing the data structure in memory 310. The digital radio broadcast receiver 300 may also include a wireless interface 316 such as Bluetooth or WiFi, for example, which can be used to export data structures to such recipient devices. As noted above, it is also possible for the digital radio broadcast receiver 300 to include suitable hardware including any suitable wired or wireless functionality to connect directly to the network 340 without the need for an intermediary recipient device. For example, the digital radio broadcast receiver 300 could be configured within an Internet enabled mobile telephone.

[0083] According to one example, during reception of music, a user may enter a user command at the user interface 302, e.g., by pressing the button 320, to register an interest in the song being played. The processing system 312 registers the user's interest by storing any suitable flag or indicator in memory 310. The user can thus tag content of interest to the user.
The processing system 312 then processes program data corresponding to the audio currently received to generate a data structure such as a purchase token for an item or items of potential interest. If the processing system determines that there is an ambiguity associated with the content in which the user is interested, the processing system 312 can process additional program data associated with additional audio content that preceded or follows the audio content in which the user is purportedly interested in. For purposes of processing such additional program data corresponding to such additional audio content, the processing system 312 can store prior received program data in the memory 310 such that the prior received program data is suitably buffered for further processing, if necessary. Additional exemplary details regarding the handling of ambiguous situations in this regard are described elsewhere herein.

[0084] FIGs. 12 and 13 illustrate examples of screen displays that may be provided at a PC 334, Internet enabled mobile telephone 330, Internet enabled personal digital assistant (PDA), or other suitable device that can communicate with network 340 (e.g., Internet) for purchasing or obtaining information regarding an item or items of interest from service providers or merchants 342, 344, 346. It will be appreciated that such screen displays and associated communication with service providers or merchants 342, 344, 346 can be carried out using suitable software running on a user's local PC or other computing platform and/or a server of a service provider or merchant 342, 344, 346. The implementation of such software is within the purview of one of ordinary skill in the art with knowledge of the format of the data structure generated by the digital radio broadcast receiver 300.

[0085] FIG. 12 illustrates an exemplary screen display 400 following startup of such software and associated processing of the data structure by the software. The software could be started automatically, for example, by docking a digital media player (e.g., MP3 player) containing a stored data structure to a PC. The screen display 400 illustrates "Your Buy List"
with artist and title information 402 for several songs, along with hyperlinks 404 to sources from which those songs may be obtained. In this example, the processing system 312 of digital radio broadcast receiver 300 has identified an ambiguity in the song of interest associated with the user command entered at the digital radio broadcast receiver 300 and has stored a data structure for the purported song of interest as well as program data for a song received immediately adjacent to the purported song of interest. The software processes these data structures and displays both songs to the user, flagging them with flags 406 as being associated with an ambiguous request as to the content of interest, so that the user can choose between them. The user can proceed to obtain further information about any or all songs listed by selecting (e.g., clicking on) the corresponding hyperlinks associated with sources for the desired information, and can purchase a desired selection(s) by following the instructions provided by following the respective hyperlinks. Both the song information (artist, title) and the hyperlink information visible on the screen display 400 are provided in the program data broadcast to the digital radio broadcast receiver 300 and are stored in the associated data structures. This information is then utilized by the software that generates the corresponding screen display 400.

[0086] FIG. 13 illustrates an exemplary screen display 500 in which "Your Buy List"
includes a list 502 of several songs, a list of merchandise available that is associated with one of the songs, and corresponding hyperlinks 506 for obtaining further information about the items or for purchasing the items. In this example, the screen display shows multiple hyperlink sources for one of the songs ("Hound Dog") as well as the option of selecting the studio version and/or the live version of that song. The hyperlink information for the multiple sources of the studio version of the song and the artist, title and hyperlink information for the live version of the song are provided in the program data broadcast to the digital radio broadcast receiver 300 and are stored in the associated data structures. This information is then utilized by the software that generates the corresponding screen display. Likewise, the identifying information for the merchandise associated with the artist Elvis Presley and the corresponding hyperlink for sources for the merchandise are provided in the program data broadcast to the digital radio broadcast receiver 300 and are stored in the associated data structures. This information is then utilized by the software that generates the corresponding screen display 500.

[0087] As referred to herein, program data refers to information broadcast by digital radio broadcast transmission in addition to audio content (e.g., music, talk, advertising, etc.) and visual content (e.g., that can be displayed on a digital radio broadcast receiver such as advertising, upcoming program features, weather and safety alerts, etc.), wherein the program data identifies content such as audio content and may identify one or more items associated with such content that may be of interest to a user. One example of program data is MPSD and/or SPSD (wherein either or both cases may simply be referred to herein as program service data "PSD." Another example of program data is AAS. Exemplary program data formats suitable for implementing the approaches described above for an IBOC receiver context will now be described with reference to FIGs. 14-19. It will be appreciated that these non-limiting examples may be modified as appropriate for implementation in other digital radio broadcast scenarios, such as, for example satellite radio. The examples below relate to transmission of program service data (PSD) for an IBOC transmission, and it should be understood that this description of PSD is intended as a non-limiting example of program data that may be utilized in IBOC or other digital radio broadcast contexts.

[0088] Program service data suitable for implementing the approaches described above can be broadcast via digital radio broadcast in a format comprising ID3 tags with suitably structured Unique File Identifier (UFID) frames associated with corresponding audio content.
The ID3 standard is conventionally used in connection with MP3 and other audio files and is well known to those of ordinary skill in the art such as described in, for example, the "ID3v2.3.0 Informal Standard" available at https://www.id3.org. ID3 tags comprises a plurality of frames, among them the Unique File Identifier (UFID) frame. FIG. 14 (top) illustrates the format of a general UFID frame that conforms to the ID3 standard and which comprises a Header, an Owner identifier field, a Terminator, and an Identifier field. FIG. 14 (bottom) illustrates exemplary Owner Identifier and Identifier fields structured to further support the approaches described herein. It will be appreciated that UFIDs as disclosed herein can be transmitted via any suitable program data including PSD, AAS, or other suitable signal.
Namely, the Owner Identifier field comprises a Frame Type field, a Format field, and a URL field in the form of a text string, with associated delimiters. The Identifier field comprises an ID
Data field (labeled "ID Data") and an optional field reserved for future expansion. The ID Data field includes a merchant specific identifier (which may be referred to herein as an "ID code") that uniquely identifies a particular piece of media content, and such identifiers may be obtained from particular merchants. The table shown in FIG. 15 further describes each of the various fields in the context of the approaches disclosed herein. In particular, the Frame Type indicates the format of the entire UFID frame in terms of all the bytes that follow. UFID
frames are specified to contain valid defined frame types. Several frame types (more generally referred to herein as "type codes") defined by the present inventors include "APC' indicating that the UFID frame contains one or more product codes from one database, "MBC" indicating that the UFID frame contains one or more product codes from a second database, and "SPC"
indicating that the UFID
frame contains one or more codes for subscription services. Other frame types can be defined as desired depending upon the desired application. The ID Data field depends on "Format" as will be described further with reference to the example of FIGs. 16-18.

[0089] FIG. 16 illustrates an exemplary UFID format containing purchase information with one ID code (i.e., purchase information for one item). In this audio purchase example, the Frame Type is "APC," and the format field contains a valid format code as set forth in the table shown in FIG. 17. The APC format codes (01, 02, 03, etc.) refer to particular identifier types associated with various merchants for various items. APC format codes may specify, for example, a merchant database type to which a particular ID code (e.g., for a song) pertains. As another example, an APC format code could refer to the Universal Product Code (UPC) designation generally, wherein a particular ID code for an item (e.g., a song) could be the specific UPC assigned to that song. The text string contains a valid URL that may provide additional information about the service provider or audio purchase. The Identifier field contains an identifier formatted as set forth by the chosen format code from FIG. 17.

[0090] As illustrated in FIG. 18, it may be preferable to have multiple ID
codes in a single UFID. This can be accomplished by setting the Format field within the Owner Identifier to "MC." In this audio purchase example, the Identifier field is a concatenation of multiple song ID codes. Each ID code is a concatenation of a 2-byte Format, a 2-byte ID
Length, and the ID
Data. Exemplary Format codes are set forth in FIG. 17. Multiple song IDs may be sent if, for example, multiple music player types are desired to be supported. If multiple song IDs are sent in a UFID with one URL, all such song IDs will be associated with the same URL. If each song ID is desired to be associated with a different URL, then multiple UFID frames may be stacked into one ID3 tag. It may also be desirable to have multiple item IDs with the same Format code within one Identifier field. For example, it may be useful to include the audio identifier codes for both the live and the studio version of a given song.

[0091] In terms of preferred practices, the PSD should properly implement the title and artist, both of which should not be used for any other purpose, the UFID URL
and the UFID
data. If possible, Album and Genre should also be properly implemented in the PSD.

[0092] FIG. 19 schematically illustrates the hierarchical encoding as reflected in the above-described examples. Namely, the UFID specifies Type of item (e.g., audio, merchandise, subscriptions, etc.), followed by the Format, which is followed by actual data identifying a given item.

[0093] Also pertinent at the broadcast side are practices associated with transmission timing and transmission of other content. As will be discussed further herein, the present inventors have found it desirable to keep the PSD information aligned with its associated audio to within 10 seconds. According to one example this can be achieved in the IBOC context as follows with application to all audio services regardless of service mode or logical channel:

1. PSD messages arrive at the HD Radio broadcast equipment within 0.5 seconds of each new audio segment or song.
2. One PSD message is sent per audio segment or song (e.g., repeated for the duration of the audio.
3. Maintain the size of the ID3 Tag, containing the PSD data, to less than 345 bytes.
4. ID3 UFID frame size is limited to less than 192 bytes

[0094] In addition, Station Information Service (SIS) data should be appropriately transmitted. For example, the FCC Facility ID and Short Station Name can be transmitted. For those stations that use more than four characters in their station names, the Universal Short Name can be used. In addition the following fields should be properly implemented in the SIS
data: Country Code, Long Station Name, ALFN (obtained via a GPS-locked time base, if possible), and Time Lock Status.

[0095] As mentioned previously, the present inventors have observed that ambiguities can arise as to the proper identification of content actually desired by a user in connection with the entering of a user command such as at user interface 302 of FIG. 11. For example, FIG. 20 illustrates possible scenarios in which the start of audio content (e.g., a song or commercial) may precede the start of the associated PSD data (FIG. 20 top) by some time interval, and in which the start of audio content (e.g., a song or commercial) may follow the start of the associated PSD

data (FIG. 20 bottom) by some time interval. Thus, if a user command is entered at a user interface of a digital radio broadcast receiver within such a time interval of a change in the PSD
data from one PSD message to another, the user command may be registered with the PSD
corresponding to the audio content other than that actually desired. In light of this observation, an exemplary approach for mitigating the effects of such ambiguities will be described with reference to FIG. 21 below.

[0096] According to another embodiment, FIG. 21 illustrates an exemplary method 600 for specifying content of interest using a digital radio broadcast receiver, such as but not limited to digital radio broadcast receiver 300 shown in FIG. 11. As shown at step 602, the digital radio broadcast receiver 300 receives a digital radio broadcast signal, wherein the digital radio broadcast signal comprises first audio content (e.g., such as Song 1 in FIG.
20) and first program data (e.g., such as PSD data 1 in FIG. 20). The first program data comprises information identifying a first item (e.g., music, video, merchandise, subscriptions, etc.) associated with the first audio content and may be specified in one or more UFID frames. It is not necessary that all information described previously herein in connection with UFID frames be available. For example, the Type code and the ID code can be sufficient information to identify a music selection, merchandise, subscription, etc. In another example, the Title and Artist fields of the UFID for music content can contain one or more characters, and that information can be sufficient to identify a song insofar as it is envisioned that the software used for receiving the data structure and downloading the song of interest will be able to identify a suitable URL
location for obtaining the song based on artist and title alone. The digital radio broadcast signal also comprises second audio content (e.g., Song 2 in FIG. 20) received after the first audio content, and second program data (e.g., such as PSD data 2 in FIG. 20). The second program data also comprises information identifying a second item associated with the second audio content.

[0097] As shown at step 604, the processing system 312 of digital radio broadcast receiver 300 may optionally activate the indicator 308 such as described previously herein to indicate that the first program data are sufficient to generate the first data structure (e.g., the first program data contains at least title and artist information for music content). At step 606, the processing system 312 registers a user command entered at the user interface 302 of the receiver 300 during reception of either the first audio content or the second audio content. As noted previously, the user command indicates the user's interest in either the first audio content or the second audio content, respectively.

[0098] At step 608, the processing system 312 determines whether there is an ambiguity in the content desired. For example, the processing system 312 can determine whether the user command was entered at the user interface within a predetermined time period from a change between the first program data and second program data. If an ambiguity in content desired is detected, e.g., if the command was entered during the predetermined time period, then at step 610 the processing system 312 stores a first data structure corresponding to the first audio content and a second data structure corresponding to the second audio content, e.g., in either memory 310 or directly to another device coupled to the receiver 300, such as the removable memory 336, the PC 334 or the digital media player 332. The selection of the predetermined time period is within the purview of one of ordinary skill in the art and will depend upon the particular broadcast context and associated circumstances such as the observed lag or lead times between program data and associated audio content. As an example, the present inventors have found a predetermined time period of plus or minus 10 seconds to be useful in an IBOC context in view of the observed arrival times of PSD compared its associated audio content wherein it has been observed that the start of PSD may lead or lag the start of associated audio content by approximately 10 seconds.

[0099] The first data structure comprises the information identifying the first item and the second data structure comprises the information identifying the second item. In this regard, FIG. 22A illustrates a table describing the field format of an exemplary purchase token as an example of a data structure. The processing system 312 can be configured (e.g., programmed) to structure the purchase token in the manner described in the table of FIG.
22A based on mapping corresponding information received from the broadcast PSD and SIS
messages. As reflected in FIG. 22A, the information for various fields may come from either SIS information, PSD information, or from the receiver itself (see "SOURCE" column) in this example. The "OFFSET" column refers to the placement of the particular field within the data structure in this exemplary purchase token structure. Exemplary sizes for the various fields are also listed, but are not limited thereto. In this example, information for certain fields is strongly desired ("core"
under "FIELD TYPE") whereas information for other fields is optional. The exemplary purchase token shown in FIG. 22A includes a plurality of fields (20 in this example). Fields 1-17 are well known to those of ordinary skill in the art. Field 18 is an "ambiguous data" flag that receives the value "1" if the purchase token is stored in connection with a purchase request for which the processing system 312 determines there is an ambiguity in the desired content, and is otherwise "0." Field 19 is a "data from user command" field (or "user command field" for brevity) that receives the value "1" if the purchase token corresponds to the PSD received at the time the user command was entered at the user interface 302 (e.g., when the button 320 was pressed). The ambiguous data flag can be used to flag multiple entries on an item list of a screen display in connection with software for purchasing or obtaining information of interest, such as screen display 400 described previously in connection with FIG. 12. The user command field is useful for listing the ambiguous items in a preferred order, such as illustrated in the list shown in FIG. 12, e.g., wherein the item having the value "1" for the user command field is listed first.

As further shown at step 610, since an ambiguity was detected, the processing system 312 also sets the ambiguity flags to "1" in both the first data structure and the second data structure. In addition, as shown at step 610, the processing system 312 sets the user command field to "1" in the data structure for which the associated program data was received at the time the user command was entered, and sets the user command field for the other data structure to "0." By setting the ambiguity flags and the user command fields in this way, "ambiguous" items can be appropriately flagged and listed in a screen display generated by appropriate software for purchasing an item of interest such as illustrated in FIG. 12.

[00100] FIG. 22B illustrates a table describing the field format of an alternative exemplary purchase token as an example of a data structure. The processing system 312 can be configured (e.g., programmed) to structure the purchase token in the manner described in the table of FIG. 22B based on mapping corresponding information received from the broadcast PSD and SIS messages. As reflected in FIG. 22B, the information for various fields may come from either SIS information, PSD information, or from the receiver itself (see "SOURCE"
column) in this example. The "OFFSET" column refers to the placement of the particular field within the data structure in this exemplary purchase token structure.
Exemplary sizes for the various fields are also listed, but are not limited thereto. The exemplary purchase token shown in FIG. 22B includes a plurality of fields (34 in this example). Fields 1-21 shown in FIG. 22B
all have a fixed size, as indicated by the "SIZE" column and must be populated. Fields 1 and 3-9 are well known to those of ordinary skill in the art. Field 2 contains flags, including an "ambiguous data flag" at bit 0 and a "data from user command flag" ("button pressed") at bit 1.
The ambiguous data flag receives the value "1" if the purchase token is stored in connection with a purchase request for which the processing system 312 determines there is an ambiguity in the desired content, and is otherwise "0." The data from user command flag (button pressed) receives the value of "1" if the purchase token corresponds to the PSD
received at the time the user command was entered at the user interface 302 (e.g., when the button 320 was pressed), and is otherwise "0." Fields 10-21 are offset values that are used to point to the start of the corresponding fields 23-34 shown in FIG. 22B. Fields 22-34, which specify data that are well-known to persons of ordinary skill in the art, can have a variable size, as indicated by the "SIZE"
column, and these fields are only written if they contain valid data. By specifying offset values in fields 11-21 to fields 22-34, which may or may not be populated, this purchase token format is significantly more memory efficient than the format shown in FIG. 22A.

[00101] Referring again to FIG. 21, as shown at step 614, if the processing system 312 identified no ambiguity with regard to the content of interest, the processing system 312 can simply store a single data structure based on the user command. In that instance, that data structure comprises information identifying the first item if the user command was entered during reception of the first program data or identifying the second item if the user command was entered during reception of the second program data. In addition, the processing system 312 can set the ambiguity flag to "0" and the user command field to "0" since no ambiguity was perceived.

[00102] As shown at steps 612, the processing system 312 can generate a message or file for each data structure stored, wherein the message or file is appropriately formatted for a particular merchant(s) or a particular recipient device(s) (e.g., mobile telephone 330, digital media player 332, PC 334, removable memory 336, etc.). Suitable approaches for generating appropriate files or messages in this regard are within the purview of those of ordinary skill in the art and will depend upon the format required by the merchant or recipient device.

[00103] According to an exemplary aspect, the first program data can comprise a Unique File Identifier (UFID) frame that includes data identifying the first item and another item of interest and a Uniform Resource Locator (URL) address for obtaining information about the first item and the other item of interest from a source via the URL. For example, a first item in this regard could be a song, and the other item could be a DVD movie starring the song artist, such as illustrated in the example of FIG. 13. According to another exemplary aspect, the first program data can comprise multiple Unique File Identifier (UFID) frames, each of which includes information identifying the first item and a Uniform Resource Locator (URL) address for obtaining information about the first item of interest, such that information can be obtained about the first item from multiple sources via the corresponding URLs. For example, as illustrated in FIG. 13, multiple URLs can identify different sources from which to obtain the same song according to various song ID codes also transmitted in the UFID
frames that may correspond to various digital media player formats for that song.

[00104] According to another exemplary aspect, the first program data can comprise a Unique File Identifier (UFID) frame, wherein the UFID frame includes multiple ID codes identifying different formats in which the first item (e.g., a song, merchandise, etc.) is available, and wherein the UFID frame includes a Uniform Resource Locator (URL) address for obtaining information about the first item. FIG. 18, illustrates an exemplary UFID frame in accordance with this aspect.

[00105] According to another exemplary aspect, the first program data can comprise one or more Unique File Identifier (UFID) frames including information identifying the first item and other item of interest and including one or more Uniform Resource Locator (URL) addresses for obtaining information about the first item and the other item.
For example, a radio program discussing a topic or item may be broadcast wherein the radio program is also available as a "podcast" (meaning one or more media files for distribution over the Internet using syndication feeds for playback on digital media players and personal computers). One UFID
frame of the first program data in this example could contain an ID code for the podcast, an ID
code for the item being discussed, and a URL address from which information about both the podcast and the item can be obtained. Alternatively, in this example, two UFID
frames could be broadcast, one UFID frame including the podcast ID code and an associated URL, and another UFID frame including the item ID code and an associated URL. In all of the examples discussed in this paragraph, appropriate type codes, e.g., APC, MBC, SPC, etc., can also be broadcast in the associated UFID frames.

[00106] According to a further embodiment, FIG. 23 illustrates an exemplary method 700 for specifying content of interest using a digital radio broadcast receiver, such as but not limited to digital radio broadcast receiver 300 shown in FIG. 11. In this embodiment, steps 702-706 and 708-714 substantially correspond to steps 602-606 and 608-614, respectively, of FIG. 21, and no further description of those steps is required. FIG. 23 presents additional steps 707 and 716, which are now described. In this example, following step 706, the processing system 312 can determine whether there was a station change within a predetermined time period AT after the user command was entered. This time period can be the same predetermined period referred to previously, or a different predetermined time period depending upon the nature of the lead or lag times associated with station changes and associated program data and audio content. Station change refers to the user having selected either a different multicast program on the same frequency or a different frequency. If such a station change is detected, the method 700 proceeds to step 716 wherein the processing system can store a single data structure based on the user command. In that instance, that data structure comprises information identifying the first item if the user command was entered during reception of the first program data or identifying the second item if the user command was entered during reception of the second program data.
In addition, the processing system 312 sets the ambiguity flag to "0" and the user command field to "0" since only one data structure is stored. The method proceeds from step 716 to step 712 wherein the processing system 312 can generate a message or file for the data structure stored, wherein the message or file is appropriately formatted for a particular merchant(s) or a particular recipient device(s) (e.g., mobile telephone 330, digital media player 332, PC 334, removable memory 336, etc.). If no station change was detected within AT after the user command was entered, the method 700 proceeds to step 708, wherein the remaining steps are carried out as previously described in connection with method 600 of FIG. 21.
In this approach, a station change within AT after the user command was entered presents a further type of ambiguity by identifying the content desired. The method resolves that ambiguity by in a simple manner by storing one data structure, without testing for further ambiguity in program data at step 708.

[00107] According to another exemplary embodiment, a method of broadcasting digital radio broadcast data formatted to facilitate specifying content of interest using a digital radio broadcast receiver is provided. The method can be carried out using any suitable broadcasting equipment. For instance, in an IBOC context, such broadcasting equipment may include that such as described in connection with FIGs. 1, 9a and 9b herein, such as an importer, exporter, exciter and/or other suitable equipment. Such broadcast equipment may include one or more software-programmable digital signal processors, programmable/hardwired logic devices, firmware, or any other combination of hardware, software and firmware, which may collectively be referred to as a processing system. Such broadcasting equipment can be used to arrange first audio content and second audio content for broadcast via a digital radio broadcast signal, such as first and second audio content previously described herein. The broadcasting equipment can structure first program data associated with the first audio content, such that the first program data comprise a first Unique File Identifier (UFID) frame comprising a first type code specifying a type of a first item associated with the first audio content, a first ID
code identifying the first item, and a first Uniform Resource Locator (URL) address for obtaining information about the first item. The broadcast equipment can also structure the second program data such that the second program data comprise a second Unique File Identifier (UFID) frame comprising a second type code specifying a type of a second item associated with the second audio content, a second ID code identifying the second item, and a second Uniform Resource Locator (URL) address for obtaining information about the second item. The broadcast equipment can generate a digital radio broadcast signal comprising the first and second audio content and the first and second program data and then transmit the digital radio broadcast signal. The digital radio broadcast signal can then be received and processed by a digital radio broadcast receiver such as described elsewhere herein.

[00108] In one exemplary aspect, the first UFID frame comprises a type code and an ID
code for another item of interest in addition to type code and ID codes associated with the first item, such as previously described herein. In another exemplary aspect, the first UFID frame can comprise multiple ID codes identifying multiple different formats in which the first item is available, such as described previously herein. In another exemplary aspect, wherein the first program data can comprise multiple UFID frames, each of which includes a Uniform Resource Locator (URL) address for obtaining information about the first item of interest, such that information can be obtained about the first item from multiple sources, such as described previously herein. In a further exemplary aspect, the first program data can comprise another UFID frame, the other UFID frame including a type code and an ID code for another item of interest and including a Uniform Resource Locator (URL) address for obtaining information about the another item of interest, such as described previously herein. In another exemplary aspect, the first program data can comprise one or more type codes selected from the group consisting of "APC' indicating that the first program data include one or more product codes from one database, MBC indicating that the first program data include one or more product codes from a second database, and "SPC" indicating that the first program data include one or more codes for subscription services, such as described previously herein.

[00109] According to other exemplary embodiments, the need to address and process potential ambiguities in the items requested can be substantially reduced or substantially eliminated by tailoring transmission side parameters and functions. In particular, a digital radio broadcast system such as described herein with reference to FIGS. 1, 9a and 9b can be configured to schedule audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver such that a start of a given program data message (e.g., main program service data MPSD or supplemental service program data SPSD) and a start of the associated audio content (or other content) are aligned to within 3 seconds of one another at the digital radio broadcast receiver without the digital radio broadcast receiver processing the digital radio broadcast signal to enhance the alignment of the program data and the audio content. As described elsewhere herein in such a digital radio broadcast system can comprise a processing system and a memory coupled to the processing system, wherein the processing system is configured (e.g., specially programmed) to carry out the scheduling functionality.
The functionality may be implemented in the processing system, for example, via a suitable set of computer program instructions in any suitable programming language, such as C, C++, SQL, C#, ASP, Perl, PHP, Java, etc. The programming instructions may be structured in any suitable way such as to provide separate functional modules.

[00110] The processing system can be any suitable processing system, such as one or more conventional computer processors residing in one computing device, such as a personal computer (PC), or the processing system can include multiple processors distributed among multiple computing devices that can communicate via a network. For example, importer 18 shown in FIG. 1 can include a processor, and exporter 20 shown in FIG. 1 can include another processor, e.g., on separate computers. Or alternatively, importer and exporter functions could be carried on a common computer using a single processor or multiple processors.

[00111] The processing system, e.g., associated with exporter 20, can be configured to receive first audio content, first program data, second audio content, and second program data for transmission via digital radio broadcast. The first program data identifies an item associated with the first audio content, and the second program data identifies an item associated with the second audio content, such as previously described herein.

[00112] In addition, the processing system can be configured to receive the first program data and the first audio content, e.g., via service interfaces 331 shown in FIGS. 9a and 9b, such that a start of the first program data is received at the processing system within 0.5 seconds of a start of the first audio content received at the processing system. As shown in FIG. 1, the processing system associated with the importer 18 and/or the exporter 20 receives the program data and the associated audio content from studio automation equipment 34. In this regard, service interfaces 331 can be considered to be part of the processing system associated with either the exporter 20, the importer 18, or both. The studio automation equipment accordingly controls the timing of the submitting the program data and associated audio to the processing system (associated with the importer and/or exporter) so that the processing system receives this information within the 0.5 second timing requirement. The processing system, e.g., associated with exporter 20, can be configured to generate a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content, and the second program data for transmission via digital radio broadcast such as already described. The processing system can also be configured to stop delivery of the first program data to the digital radio broadcast transmitter upon receipt of the second program data, such that the first program data is truncated, and to begin delivery of the second program data (e.g., immediately or within a short time of 1, 5, 10, 20, 30, 50 milliseconds, etc.) to the digital radio broadcast transmitter. In this regard, it will be appreciated that a given PSD message can be transmitted repeatedly while its associated audio is being transmitted, in which case, it is the most recent iteration of the repeated PSD that is truncated. Thus, when a new PSD message is received it is not buffered, but can be transmitted immediately or substantially so upon receipt by the processing system, the prior PSD

message being truncated. If there are no new PSD messages in a queue, the last PSD message processed may continue to be repeated.

[00113] In an exemplary IBOC implementation, keeping the PSD information aligned with its associated audio to within 3 seconds at the receiver can be achieved as follows with application to all audio services regardless of service mode or logical channel:

[00114] 1. PSD messages arrive at the IBOC radio broadcast equipment, in particular, at the processing system associated with the importer or exporter or both (e.g., at service interfaces 331) within 0.5 seconds of each new audio segment or song;

[00115] 2. One PSD message is sent per audio segment or song (e.g., repeated for the duration of the audio);

[00116] 3. Maintain the size of the ID3 Tag, containing the PSD data, to less than 450 bytes.

[00117] 4. PSD messages are not buffered; an existing PSD message is truncated when a new PSD message is received so that the new PSD message can be processed immediately or substantially so for delivery to IBOC broadcast equipment.

[00118] According to one example, the processing and scheduling of main program service (MPS) data and its associated audio can processed at an exporter, such as exporter 20 shown in FIG. 1. FIG. 24 shows a functional block diagram associated with exporter processing in this regard according to one example. As shown in FIG. 24, both PSD
messages and associated audio are sent from studio automation equipment to service interfaces (e.g., analogous to service interfaces 331 shown in FIG. 9a). These may be separate service interfaces as shown in FIG. 24, for example. The audio is transferred to an audio encoder and transport block (e.g., analogous to audio encoder 332 and audio transport 333 in FIG.
9a), and the PSD is transferred to a PSD transport block (e.g., analogous to PSD transport block 334 shown in FIG.
9a). The PSD transport block includes a PSD message queue (not shown). The audio encoder/transport block includes an audio PDU (protocol data unit) buffer (not shown), which may provide, for example, a 1.4 second buffer for PDUs. A second audio buffer of 0.186 seconds can be used for block rate channels, which may be restricted for use with FM all-digital modes in some IBOC broadcasting examples. The service interfaces shown in FIG.
24 receive the program data and associated audio content from the studio automation equipment such that the start of the program data and the start of the associated audio content are within 0.5 seconds of one another as received at the processing system. The scheduling function of the processing system to achieve the ultimately desired 3 second alignment of the PSD and associated audio at the digital radio broadcast receiver can be carried out in PSD transport block. As a general matter, even though the processing system receives the program data and associated audio content such that their respective starts are aligned to within 0.5 seconds at that stage, the program data and the associated audio suffer additional misalignment in processing those components for digital radio broadcast due to the size of the PSD messages.
Referring to FIG.
9a, for example, control signals from PSD transport 334 can be sent to audio transport 333 and audio encoder 332 to accomplish the 3 second alignment between PSD and associated audio.
Insofar as two different service interfaces may be used for audio and PSD as shown in FIG. 24, any differences in delays associated with traversing separate service interfaces are taken into account by the processing system in scheduling the PSD and associated audio to achieve the desired alignment between them. The processing system, e.g., via PSD transport block 334, can control the scheduling of the program data and the associated audio content by controlling the buffering of the audio content and by selecting the timing at which a PSD
message will be forwarded. In this regard, PSD messages do not need to be buffered because they are continually repeated until a new PSD message is received. Thus, to control the timing of the PSD message relative to the audio, the processing system can simply discard repeated occurrences of the same PSD message until the appropriate time is reached for forwarding the PSD message. As will be discussed further below, the timing of the PSD message can also be controlled by changing, e.g., increasing, the bandwidth allocated to the PSD
message. As reflected in both FIGS. 9a and 24, PSD messages are then transferred from the PSD transport (e.g., 334) to the audio transport (e.g., 333), and protocol data units (PDUs) are generated and output as described elsewhere herein. At the stage of outputting PDUs from the audio encoder and transport block, the respective starts of the program data and associated audio content are aligned to within 3 seconds. In such an exporter processing example of an IBOC system, the program data that is processed is main program service (MPS) data, as reflected in FIG. 24.

[00119] According to another example, the processing and scheduling of supplemental program service (SPS) data, advanced application service (AAS) data, and/or other data services and its associated audio or other content can processed at an importer, such as importer 18 shown in FIG. 1. FIG. 25 shows a functional block diagram associated with importer processing in this regard according to one example. As shown in FIG. 25, in response to a data request by the importer, the studio automation equipment may send either a PSD message or associated audio to a service interfaces (e.g., analogous to service interface 331 shown in FIG. 9b). In one example, the audio and PSD message may be sent to the same service interface as shown in the example of FIG. 25. The audio is transferred to an audio encoder (e.g., analogous to audio encoder 332 shown in FIG. 9b) and then to an audio transport block (e.g., analogous to audio transport 333 in FIG. 9b. The PSD is transferred to a PSD transport block (e.g., analogous to PSD transport block 334 shown in FIG. 9b). The audio transport block includes a compressed audio frame buffer that may provide, for example, a 4.5 second buffer for compressed audio frames. The service interface shown in FIG. 25 receives the program data and associated audio content from the studio automation equipment such that the start of the program data and the start of the associated audio content are within 0.5 seconds of one another as received at the processing system. The scheduling function of the processing system to achieve the ultimately desired 3 second alignment of the PSD and associated audio at the digital radio broadcast receiver can be carried out in PSD transport block, such as described above in connection with FIG. 24. For example, referring to FIG. 9b, control signals from PSD transport 334 can be sent to audio transport 333 and audio encoder 332 to accomplish the 3 second alignment between PSD and associated audio. As reflected in both FIGS. 9b and 25, PSD messages are then transferred from the PSD transport (e.g., 334) to the audio transport (e.g., 333), and protocol data units (PDUs) are generated and output as described elsewhere herein. At the stage of outputting PDUs from the transport block, the respective starts of the program data and associated audio content are aligned to within 3 seconds. In such an importer processing example of an IBOC
system, the program data that is processed can be SPS data, AAS data, and/or other data services data as reflected in FIG. 25. In some examples, 7 bytes may be reserved for transmission of PSD information. In other, examples a larger number of bytes may be reserved for PSD
information such as 16 bytes or 22 bytes.

[00120] It will be appreciated that exporter processing and importer processing such as described above in connection with FIGS. 24 and 25 can be combined. In other words, the processing system, implementing both importer and exporter functions via one or more processors, can process a combination of MPS data, SPS data, AAS data, and/or other data services program data, along with associated audio or other content.

[00121] In another example, the processing system can be configured to schedule timing of the delivery of the program data to the digital radio broadcast transmitter based upon timing of delivery of the associated audio content and based upon a size of the first program data. For example, PSD transport 334 can control audio encoder 332 and the audio transport 33 can control the timing of delivery, e.g., using any suitable audio buffering that may be warranted.

[00122] In another example, the processing system can be configured to schedule timing of the delivery of the program data to the digital radio broadcast transmitter for relatively larger program data messages by temporarily reducing the bit rate of the audio encoder based upon the size of the program data and by temporarily increasing the bandwidth allocated to processing the program data. Thus, larger program data messages can be scheduled appropriately so as to avoid increased lag that might otherwise occur.

[00123] In another example, the processing system can be configured to schedule timing of the delivery of the program data to the digital radio broadcast transmitter for relatively larger program data messages by decreasing the bandwidth allocated to opportunistic data based upon the size of the first program data and to allocate additional bandwidth to the program data. Thus, larger program data messages can be scheduled appropriately so as to avoid increased lag that might otherwise occur.

[00124] In another example, the processing system can be configured to schedule timing of the delivery of the program data to the digital radio broadcast transmitter by allocating unused bandwidth for audio packets (e.g., such as may arise during periods of audio silence) to program data messages to increase bandwidth allocated to the program data based upon the size of the program data. Thus, again, larger program data messages can be scheduled appropriately so as to avoid increased lag that might otherwise occur.

[00125] According to another embodiment, FIG. 26 illustrates an exemplary method 800 for specifying content of interest using a digital radio broadcast receiver, such as but not limited to digital radio broadcast receiver 300 shown in FIG. 11. As shown at step 802, the digital radio broadcast receiver 300 receives a digital radio broadcast signal, wherein the digital radio broadcast signal comprises first audio content (e.g., such as Song 1 in FIG.
20) and first program data (e.g., such as PSD data 1 in FIG. 20). The first program data comprises information identifying a first item (e.g., music, video, merchandise, subscriptions, etc.) associated with the first audio content and may be specified in one or more UFID frames. It is not necessary that all information described previously herein in connection with UFID frames be available. For example, the Type code and the ID code can be sufficient information to identify a music selection, merchandise, subscription, etc. In another example, the Title and Artist fields of the UFID for music content can contain one or more characters, and that information can be sufficient to identify a song insofar as it is envisioned that the software used for receiving the data structure and downloading the song of interest will be able to identify a suitable URL
location for obtaining the song based on artist and title alone. The digital radio broadcast signal also comprises second audio content (e.g., Song 2 in FIG. 20) received after the first audio content, and second program data (e.g., such as PSD data 2 in FIG. 20). The second program data also comprises information identifying a second item associated with the second audio content.

[00126] As shown at step 804, the processing system 312 of digital radio broadcast receiver 300 may optionally activate the indicator 308 such as described previously herein to indicate that the first program data are sufficient to generate the first data structure (e.g., the first program data contains at least title and artist information for music content). At step 806, the processing system 312 registers a user command entered at the user interface 302 of the receiver 300 during reception of either the first audio content or the second audio content. As noted previously, the user command indicates the user's interest in either the first audio content or the second audio content, respectively.

[00127] At step 808, the processing system 312 determines whether there is an ambiguity in the content desired. For example, the processing system 312 can determine whether the user command was entered at the user interface within a predetermined time period (e.g., 3 seconds, seconds, etc.) from a change between the first program data and second program data. If an ambiguity in content desired is detected, e.g., if the command was entered during the predetermined time period, then at step 810 the processing system 312 refrains from storing a data structure identifying either the first item or the second item, i.e., no data structure for either the first or second item is stored if there is an ambiguity in the content desired. In addition, as shown at step 810, the processing system 312 can cause information to be rendered at the receiver 300 that the user's attempt to tag the content of interest was not successful so that the user will be informed of such. By informing the user that the tagging attempt was not successful, the user experience is enhanced since the user will not be under a mistaken impression that the tag was achieved. The information indicating that the tag was unsuccessful can be rendered at the receiver in any suitable way. For example, as discussed previously herein a failure to tag the desired content could be indicated with a suitable indicator light or by displaying a suitable error message on the display 304, e.g., a blinking error message.

[00128] The selection of the predetermined time period is within the purview of one of ordinary skill in the art and will depend upon the particular broadcast context and associated circumstances such as the observed lag or lead times between program data and associated audio content. For example, the present inventors have found a predetermined time period of plus or minus 10 seconds, or especially plus or minus 3 seconds, to be useful in an IBOC context in view of the observation that the arrival of PSD may lead or lag the start of associated audio content by such time periods.

[00129] As shown at step 812, if the processing system 312 identified no ambiguity with regard to the content of interest, the processing system 312 can simply store a data structure based on the user command, e.g., in either memory 310 or directly to another device coupled to the receiver 300, such as the removable memory 336, the PC 334 or the digital media player 332. In that instance, that data structure comprises information identifying the first item if the user command was entered during reception of the first program data or identifying the second item if the user command was entered during reception of the second program data. Since there was no ambiguity, the ambiguity flag can be set to "0" and the user command flag can be set to "0" as previously explained herein.

[00130] Such as discussed previously, the data structure comprises the information identifying the item of interest (the first item or the second item). FIG. 22A
illustrates a table describing the field format of an exemplary purchase token as an example of a data structure, as previously explained. The processing system 312 can be configured (e.g., programmed) to structure the purchase token in the manner described in the tables of FIGs.
22A and 22B based on mapping corresponding information received from the broadcast PSD and SIS
messages. As reflected in FIG. 22A, the exemplary purchase token may include a plurality of fields, as previously explained herein.

[00131] As shown at steps 814, the processing system 312 can generate a message or file for each data structure stored, wherein the message or file is appropriately formatted for a particular merchant(s) or a particular recipient device(s) (e.g., mobile telephone 330, digital media player 332, PC 334, removable memory 336, etc.). Suitable approaches for generating appropriate files or messages in this regard are within the purview of those of ordinary skill in the art and will depend upon the format required by the merchant or recipient device.

[00132] According to an exemplary aspect, as previously discussed, the first program data can comprise a Unique File Identifier (UFID) frame that includes data identifying the first item and another item of interest and a Uniform Resource Locator (URL) address for obtaining information about the first item and the other item of interest from a source via the URL. For example, a first item in this regard could be a song, and the other item could be a DVD movie starring the song artist, such as illustrated in the example of FIG. 13.
According to another exemplary aspect, the first program data can comprise multiple Unique File Identifier (UFID) frames, each of which includes information identifying the first item and a Uniform Resource Locator (URL) address for obtaining information about the first item of interest, such that information can be obtained about the first item from multiple sources via the corresponding URLs. For example, as illustrated in FIG. 13, multiple URLs can identify different sources from which to obtain the same song according to various song ID codes also transmitted in the UFID
frames that may correspond to various digital media player formats for that song.

[00133] According to another exemplary aspect, as previously discussed, the first program data can comprise a Unique File Identifier (UFID) frame, wherein the UFID frame includes multiple ID codes identifying different formats in which the first item (e.g., a song, merchandise, etc.) is available, and wherein the UFID frame includes a Uniform Resource Locator (URL) address for obtaining information about the first item. FIG. 18, illustrates an exemplary UFID frame in accordance with this aspect.

[00134] According to another exemplary aspect, as previously discussed, the first program data can comprise one or more Unique File Identifier (UFID) frames including information identifying the first item and other item of interest and including one or more Uniform Resource Locator (URL) addresses for obtaining information about the first item and the other item. For example, a radio program discussing a topic or item may be broadcast wherein the radio program is also available as a "podcast" (meaning one or more media files for distribution over the Internet using syndication feeds for playback on digital media players and personal computers). One UFID frame of the first program data in this example could contain an ID code for the podcast, an ID code for the item being discussed, and a URL
address from which information about both the podcast and the item can be obtained.
Alternatively, in this example, two UFID frames could be broadcast, one UFID frame including the podcast ID code and an associated URL, and another UFID frame including the item ID code and an associated URL. In all of the examples discussed in this paragraph, appropriate type codes, e.g., APC, MBC, SPC, etc., can also be broadcast in the associated UFID frames.

[00135] The methods described herein may be implemented utilizing either a software-programmable digital signal processor, or a programmable/hardwired logic device, firmware, or any other combination of hardware, software and firmware sufficient to carry out the described functionality. In addition, a non-transitory computer readable storage medium may include instructions adapted to cause a processing system to carry out the methods described herein.

The computer readable storage medium can be any suitable non-transitory physical storage medium for storing such instructions, such as but not limited to a hard disk, floppy disk, compact disk (CD), digital versatile disk (DVD), magnetic tape, other magnetic or optical storage medium, random access memory (RAM), read only memory (ROM), flash memory, etc.
Such instructions may also be communicated using modulated waves/signals (such as radio frequency, audio frequency, or optical frequency modulated waves/signals) and can be downloaded to a computer, e.g., onto a non-transitory computer readable storage medium, so as to cause a processing system to carry out the methods described herein.

[00136] While the present invention has been described in terms of exemplary embodiments, it will be understood by those skilled in the art that various modifications can be made thereto without departing from the scope of the invention as set forth in the claims.

Claims

1. A digital radio broadcast system for scheduling audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver, comprising:

a processing system; and a memory coupled to the processing system, the processing system being configured to receive first audio content, first program data, second audio content, and second program data for transmission via digital radio broadcast, the first program data identifying a first item associated with the first audio content, the second program data identifying a second item associated with the second audio content, the processing system being configured to receive the first program data and the first audio content such that a start of the first program data is received at the processing system within 0.5 seconds of a start of the first audio content received at the processing system, the processing system being configured to generate a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content, and the second program data for digital radio broadcast transmission via a digital radio broadcast transmitter, the processing system being configured to stop delivery of the first program data to the digital radio broadcast transmitter upon receipt of the second program data, the first program data thereby being truncated, and to begin delivery of the second program data to the digital radio broadcast transmitter.

2. The system of claim 1, the processing system being configured to schedule timing of the delivery of the first program data to the digital radio broadcast transmitter based upon timing of delivery of the first audio content to the digital radio broadcast transmitter and based upon a size of the first program data.

3. The system of claim 1, comprising an audio encoder wherein the processing system is configured to temporarily reduce a bit rate of the audio encoder based upon a size of the first program data and to temporarily increase a bandwidth allocated to processing the first program data.

4. The system of claim 1, the processing system being configured to decrease a bandwidth allocated to opportunistic data based upon a size of the first program data and to allocate additional bandwidth to the first program data.

5. The system of claim 1, the processing system being configured to allocate unused bandwidth for audio packets to increase bandwidth allocated to the first program data based upon a size of the first program data.

6. The system of claim 1, wherein:

the first program data comprises a first Unique File Identifier (UFID) frame comprising a first type code specifying a type of a first item associated with the first audio content, a first ID
code identifying the first item, and a first Uniform Resource Locator (URL) address for obtaining information about the first item, and the second program data comprises a second Unique File Identifier (UFID) frame comprising a second type code specifying a type of a second item associated with the second audio content, a second ID code identifying the second item, and a second Uniform Resource Locator (URL) address for obtaining information about the second item.

7. A method for scheduling audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver, the method comprising:

receiving at a processing system first audio content, first program data, second audio content, and second program data for transmission via digital radio broadcast, the first program data identifying an item associated with the first audio content, the second program data identifying an item associated with the second audio content;

receiving the first program data and the first audio content at the processing system such that a start of the first program data is received at the processing system within 0.5 seconds of a start of the first audio content received at the processing system;

generating at the processing system a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content, and the second program data for digital radio broadcast transmission via a digital radio broadcast transmitter; and stopping delivery of the first program data to the digital radio broadcast transmitter upon receipt of the second program data, the first program data thereby being truncated, and beginning delivery of the second program data to the digital radio broadcast transmitter.

8. The method of claim 7, comprising scheduling timing of the delivery of the first program data to the digital radio broadcast transmitter based upon timing of delivery of the first audio content to the digital radio broadcast transmitter and based upon a size of the first program data.

9. The method of claim 7, comprising temporarily reducing a bit rate of an audio encoder based upon a size of the first program data and temporarily increasing a bandwidth allocated to processing the first program data.

10. The method of claim 7, comprising decreasing a bandwidth allocated to opportunistic data based upon a size of the first program data and allocating additional bandwidth to the first program data.

11. The method of claim 7, comprising allocating unused bandwidth for audio packets to increase bandwidth allocated to the first program data based upon a size of the first program data.

12. The method of claim 7, wherein:

the first program data comprises a first Unique File Identifier (UFID) frame comprising a first type code specifying a type of a first item associated with the first audio content, a first ID
code identifying the first item, and a first Uniform Resource Locator (URL) address for obtaining information about the first item, and the second program data comprises a second Unique File Identifier (UFID) frame comprising a second type code specifying a type of a second item associated with the second audio content, a second ID code identifying the second item, and a second Uniform Resource Locator (URL) address for obtaining information about the second item.

13. A non-transitory computer readable storage medium comprising programming instructions adapted to cause a processing system to execute the method of claim 7.

14. A digital radio broadcast receiver configured to receive audio content and associated program data via digital radio broadcast and permit user identification of content of interest, the digital radio broadcast receiver, comprising:

a processing system;

a memory coupled to the processing system; and a user interface for receiving user commands entered thereto;
wherein the processing system is configured to:

process a digital radio broadcast signal received by the receiver, the digital radio broadcast signal comprising first audio content and first program data, the first program data comprising information identifying a first item associated with the first audio content, and second audio content and second program data, the second program data comprising information identifying a second item associated with the second audio content; and register a user command entered at a user interface of the receiver during reception of either the first audio content or the second audio content, the user command indicating a user's interest in either the first audio content or the second audio content, respectively, the receiver receiving the first audio content and first program data such that a start of the first program data and a start of the first audio content are aligned at the receiver to within 3 seconds of one another without the digital radio broadcast receiver processing the digital radio broadcast signal to enhance the alignment of the first program data and the first audio content.

15. The digital radio broadcast receiver of claim 14, the processing system being configured to:

determine whether there is an ambiguity associated with the user's interest in either the first audio content or the second audio content;

if there is no ambiguity, store a data structure identifying the first item associated with the first audio content or second item associated with the second audio content; and if there is an ambiguity, refrain from storing a data structure identifying the first item or the second item, and render at the receiver information indicating that the user command was not successful in tagging content of interest.

16. A method for specifying content of interest using a digital radio broadcast receiver, the method comprising:

receiving a digital radio broadcast signal, the digital radio broadcast signal comprising first audio content and first program data, the first program data comprising information identifying a first item associated with the first audio content, the digital radio broadcast signal comprising second audio content and second program data, the second program data comprising information identifying a second item associated with the second audio content;

registering a user command entered at a user interface of the receiver during reception of either the first audio content or the second audio content, the user command indicating a user's interest in either the first audio content or the second audio content;

storing a data structure in memory corresponding to either the first audio content or the second audio content, the data structure comprising the information identifying the first item or the second item, respectively;

the first audio content and first program data being received at the digital radio broadcast receiver such that a start of the first program data and a start of the first audio content are aligned to within 3 seconds of one another without the digital radio broadcast receiver processing the digital radio broadcast signal to enhance the alignment of the first program data and the first audio content.

17. The method of claim 17, comprising:

determining whether there is an ambiguity associated with the user's interest in either the first audio content or the second audio content;

if there is no ambiguity, storing a data structure identifying the first item associated with the first audio content or second item associated with the second audio content; and if there is an ambiguity, refraining from storing a data structure identifying the first item or the second item, and rendering at the receiver information indicating that the user command was not successful in tagging content of interest.

18. A computer readable storage medium comprising programming instructions adapted to cause a processing system to execute the method of claim 16.

19. A digital radio system for scheduling audio content and associated program data for digital radio broadcast to a digital radio broadcast receiver and for specifying content of interest, the digital radio system comprising:

a broadcast system comprising a processing system and a memory coupled to the processing system; and a digital radio broadcast receiver;

wherein the processing system of the broadcast system is configured to:

receive first audio content, first program data, second audio content, and second program data for transmission via digital radio broadcast, the first program data identifying a first item associated with the first audio content, the second program data identifying a second item associated with the second audio content, receive the first program data and the first audio content such that a start of the first program data is received at the processing system within 0.5 seconds of a start of the first audio content received at the processing system, generate a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content, and the second program data for digital radio broadcast transmission via a digital radio broadcast transmitter, and stop delivery of the first program data to the digital radio broadcast transmitter upon receipt of the second program data, the first program data thereby being truncated, and to begin delivery of the second program data to the digital radio broadcast transmitter;

wherein the digital broadcast receiver is configured to:

process a digital radio broadcast signal comprising the first audio content, the first program data, the second audio content and the first program data, such that a start of the first program data and a start of the first audio content are aligned at the receiver to within 3 seconds of one another without the digital radio broadcast receiver processing the digital radio broadcast signal to enhance the alignment of the first program data and the first audio content, and register a user command entered at a user interface of the receiver during reception of either the first audio content or the second audio content, the user command indicating a user's interest in either the first audio content or the second audio content, respectively, determine whether there is an ambiguity associated with the user's interest in either the first audio content or the second audio content, and if there is an ambiguity, store a first data structure identifying the first item associated with the first audio content and store a second data structure identifying the second item associated with the second audio content.