# Patent

## Title
Method and system for transmitting radio data system (RDS) data

## Abstract

A host system for transmitting radio data system (RDS) data includes a host processor and a data processor. The data processor is configured to receive RDS data from the host processor. The data processor is further configured to convert the RDS data into RDS group type data or to store the RDS data. The data processor is further configured to transmit the RDS data to one or more devices outside the host system. The data processor is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data. A method is also provided for transmitting RDS data from a host system.

## Background
BACKGROUND
1. Field
The subject technology relates generally to radio transmissions or reception, and more specifically to methods and systems for transmitting radio data system (RDS) data.
2. Background
Broadcast radio data is typically used in FM radio stations, which transmit stereo-multiplex signals in the VHF frequency band. Broadcast radio data can be used by the FM radio stations to display information relating to their radio broadcast. An FM radio, which receives the broadcast radio data, can reproduce that data on a display. The raw broadcast radio data itself is passed to the host processor of the FM radio. The host processor then typically processes the raw broadcast radio data, so that the data can be reproduced on the display. In this regard, the host processor must typically handle numerous interrupts associated with the broadcast radio data, thus causing the host processor to use more power, memory and processing cycles. As such, there is a need in the art for a system and methodology to improve power and memory efficiency of the host processor.
SUMMARY
In one aspect of the disclosure, a host system for transmitting radio data system (RDS) data is provided. The host system includes a host processor and a data processor. The data processor is configured to receive RDS data from the host processor. The data processor is further configured to convert the RDS data into RDS group type data or to store the RDS data. The data processor is further configured to transmit the RDS data to one or more devices outside the host system. The data processor is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data.
In a further aspect of the disclosure, a data processor for a host system for transmitting radio data system (RDS) data is provided. The data processor includes a receive module configured to receive RDS data from a host processor of the host system. The data processor further includes a processing module configured to convert the RDS data into RDS group type data or to store the RDS data. In addition, the data processor includes a transmit module configured to transmit the RDS data to one or more devices outside the host system. The processing module is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data.
In yet a further aspect of the disclosure, a host system for transmitting radio data system (RDS) data is provided. The host system includes a host processor and a data processor. The data processor includes means for receiving RDS data from the host processor, and means for converting the RDS data into RDS group type data or means for storing the RDS data. The data processor further includes means for transmitting the RDS data to one or more devices outside the host system. The means for storing is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data.
In yet a further aspect of the disclosure, a method of transmitting radio data system (RDS) data from a host system comprising a host processor and a data processor is provided. The method includes receiving, by the data processor, RDS data from the host processor. The method further includes converting, by the data processor, the RDS data into RDS group type data or storing, by the data processor, the RDS data. In addition, the method includes transmitting, by the data processor, the RDS data to one or more devices outside the host system. The step of storing is performed if the RDS data comprises a plurality of raw RDS group data.
In yet a further aspect of the disclosure, a machine-readable medium encoded with instructions for transmitting radio data system (RDS) data from a host system comprising a host processor and a data processor is provided. The instructions include code for receiving, by the data processor, RDS data from the host processor. The instructions further include code for converting, by the data processor, the RDS data into RDS group type data or storing, by the data processor, the RDS data. In addition, the instructions include code for transmitting, by the data processor, the RDS data to one or more devices outside the host system. The step of storing is performed if the RDS data comprises a plurality of raw RDS group data.
It is understood that other configurations of the subject technology will become readily apparent to those skilled in the art from the following detailed description, wherein various configurations of the subject technology are shown and described by way of illustration. As will be realized, the subject technology is capable of other and different configurations and its several details are capable of modification in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram illustrating an example of a radio network in which a host system can be used.
FIG. 2 is a conceptual block diagram illustrating an example of a hardware configuration for a host system.
FIG. 3 is a conceptual block diagram illustrating an example of a hardware configuration for transceiver core of FIG. 2.
FIG. 4 is a conceptual block diagram illustrating examples of different implementations for a transceiver core.
FIG. 5 is a conceptual block diagram illustrating an example of benefits provided by using a transceiver core with a host processor.
FIG. 6 is a conceptual block diagram illustrating an example of the structure of the baseband coding of the RDS standard.
FIG. 7 is a conceptual block diagram illustrating an example of a message format and address structure for RDS data.
FIG. 8 is a conceptual block diagram illustrating an example of an RDS group data structure.
FIG. 9 is a conceptual block diagram illustrating a core digital component and core firmware component of a transceiver core.
FIG. 10 is a sequence chart illustrating an example of a host receiving RDS Block-B data.
FIG. 11 is a conceptual block diagram illustrating an example of an RDS group filter.
FIG. 12 is a conceptual block diagram illustrating an example of RDS basic tuning and switching information for a group type 0A.
FIG. 13 is a conceptual block diagram illustrating an example of RDS basic tuning and switching information for a group type 0B.
FIG. 14 is a conceptual block diagram illustrating an example of a format for a program service (PS) name table.
FIG. 15 is a conceptual block diagram illustrating an example of generating a PS name table.
FIG. 16 is a conceptual diagram illustrating an example of PS name data and corresponding text displayed on a receiving unit.
FIG. 17 is a sequence chart illustrating an example of processing RDS data with group type 0.
FIGS. 18A to 18J are conceptual diagrams illustrating an example of dynamic PS name data and corresponding display text on a host processor.
FIGS. 19A to 19B are conceptual diagrams illustrating an example of static PS name data and corresponding display text on a host processor.
FIG. 20 is a conceptual block diagram illustrating an example of an alternative frequency (AF) list format.
FIG. 21 is a conceptual block diagram illustrating an exemplary format of RDS radio text for group type 2A.
FIG. 22 is a conceptual block diagram illustrating an exemplary format of RDS radio text for group type 2B.
FIG. 23 is a sequence chart illustrating an example of the RDS group type 2 data processing.
FIG. 24 is a conceptual block diagram illustrating an example of RDS group buffers.
FIG. 25 is a sequence chart illustrating an example of buffering and processing RDS group data.
FIG. 26 is a conceptual block diagram illustrating an example of a configuration for a transceiver core for performing various levels of RDS data processing.
FIG. 27 is a conceptual diagram illustrating an example of data pipes between a transceiver core and a host processor for transmitting RDS data.
FIG. 28 is a conceptual diagram illustrating an exemplary table of data pipes between a transceiver core and a host processor for transmitting RDS data.
FIG. 29 is a conceptual diagram illustrating an example of interleaving RDS data of different types.
FIG. 30 is a state machine diagram illustrating exemplary events and states for transmitting RDS data.
FIG. 31 is a sequence chart illustrating an example of transmitting raw RDS data on a “one-shot” basis.
FIG. 32 is a sequence chart illustrating an example of transmitting raw RDS data on a continuous basis.
FIGS. 33A to 33H are conceptual diagrams illustrating an example in which a host processor requests for all groups of raw RDS data to be transmitted on a “one-shot” basis.
FIGS. 34A to 34E are conceptual diagrams illustrating an example in which a host processor requests for all groups of raw RDS data to be transmitted continuously.
FIG. 35 is a sequence chart illustrating an example of transmitting RDS data with program service (PS) information.
FIG. 36 is a sequence chart illustrating an example of transmitting RDS data with radio text (RT) information.
FIG. 37 is a conceptual block diagram illustrating an exemplary interface format of RDS radio text for group type 2A with a host processor.
FIG. 38 is a flowchart illustrating an exemplary operation of transmitting RDS data from a host system.
FIG. 39 is a conceptual block diagram illustrating an example of the functionality of a host system for transmitting RDS data.



DETAILED DESCRIPTION
The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology may be practiced. The appended drawings and attached Appendix are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. However, it will be apparent to those skilled in the art that the subject technology may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology.
FIG. 1 is a diagram illustrating an example of a radio network 100 in which a host system can be used. As seen in FIG. 1, radio network 100 includes host system 200 for transmitting an FM radio signal. Host system 200 can transmit the radio signal in the VHF frequency band, and can specify the transmit frequency for the radio signal. A radio receiver 104 which tunes to that specified transmit frequency can receive the radio signal via antenna 106.
In this regard, the transmitted radio signal can include radio data system (RDS) data, which is typically used to display information relating to the radio signal. For example, the station name, song title, and/or artist can be included in the RDS data. In addition or in the alternative, the RDS data can provide other services, such as showing messages on behalf of advertisers.
An exemplary utilization of the RDS data of this disclosure is for the European RDS standard, which is defined in the European Committee for Electrotechnical Standardization, EN 50067 specification. Another exemplary utilization of the RDS data of this disclosure is for the North American radio broadcast data system (RBDS) standard (also referred to as NRSC-4), which is largely based on the European RDS standard. As such, the RDS data of this disclosure is not limited to one or more of the above standards/examples. The RDS data can include, additionally or alternatively, other suitable information related to a radio transmission.
In addition, although host system 200 is depicted as a cellular phone in FIG. 1, it should not be limited as such. Host system 200 can represent, for example, a computer, a laptop computer, a telephone, another type of mobile phone, a personal digital assistant (PDA), an audio player, a game console, a camera, a camcorder, an audio device, a video device, a multimedia device, a component(s) of any of the foregoing (such as a printed circuit board(s), an integrated circuit(s), and/or a circuit component(s)), or any other device capable of supporting RDS. Host system 200 can be stationary or mobile, and it can be a digital device.
In one aspect of the disclosure, host system 200 is not a base station. In another aspect, host system 200 may be a base station. In yet another aspect, host system 200 may be a device that is configured to receive RDS data from a device outside host system 200 (e.g., receive RDS data over-the-air from a remote device) and is also configured to transmit RDS data to one or more devices outside host system 200 (e.g., transmit RDS data over-the-air to one or more remote devices). In yet another aspect, host system 200 may be a device that contains RDS data (e.g., RDS data has been copied onto host system 200) and is configured to transmit RDS data to one or more devices outside host system 200.
FIG. 2 is a conceptual block diagram illustrating an example of a hardware configuration for a host system. Host system 200 includes transceiver core 202, which interfaces with host processor 204. Host processor 204 may correspond with a primary processor for host system 200.
Transceiver core 202 can send/receive Inter-IC Sound (I2s) information with audio component 218, and can send left and right audio data output to audio component 218. Transceiver core 202 can also receive FM radio information, which may include RDS data, through antenna 206. In addition, transceiver core 202 can transmit FM radio information, which may include RDS data, through antenna 208.
With reference to FIGS. 1 and 2, host processor 204 can tune transceiver core 202 to a specified transmit frequency and pass audio data to transceiver core 202 along with RDS data (e.g., program service names, radio text data, song title, artist information). Transceiver core 202 can convert into a specific format, store, interleave and/or transmit the RDS data, and this will be discussed in greater detail below with reference to FIGS. 27 to 38. A user can tune radio receiver 104 to the specified transmit frequency, and if radio receiver 104 is RDS capable, the RDS data can appear on the display of radio receiver 104.
In one aspect of the disclosure, RDS data can be transmitted by transceiver core 202 through antenna 208. This RDS data can be formatted, stored, and/or interleaved by transceiver core 202 before transmission, so as to reduce the amount of processing to be performed by host processor 204. According to another aspect of the disclosure, antenna 206, which is used for receiving data, is not necessary for interaction between transceiver core 202 and host processor 204 to reduce the amount of processing to be performed by host processor 204.
In another aspect of the disclosure, RDS data received by transceiver core 202 through antenna 206 can be processed by transceiver core 202, so as to reduce the number of interrupts sent to host processor 204.
Host system 200 may also include a display module 220 for displaying, among other things, RDS data received through antenna 206. Host system may also include keypad module 222 for user input, as well as program memory 224, data memory 226 and communication interfaces 228. Communication between audio module 218, display module 220, keypad module 222, host processor 204, program memory 224, data memory 226 and communication interfaces 228 may be possible via a bus 230.
In addition, host system 200 can include various connections for input/output with external devices. These connections include, for example, speaker output connection 210, headphone output connection 212, microphone input connection 214 and stereo input connection 216.
FIG. 3 is a conceptual block diagram illustrating an example of a hardware configuration for transceiver core 202 of FIG. 2. As noted above, transceiver core 202 can receive FM radio information, including RDS data, through antenna 206 and can transmit FM radio information through antenna 208. Transceiver core 202 can also send/receive Inter-IC Sound (I2s) data, and can send left and right audio output via audio interface 304 to other parts of host system 200.
Transceiver core 202 may include FM receiver 302 for receiving a FM radio signal, which may include RDS data. FM demodulator 308 can be used to demodulate the FM radio signal, and RDS decoder 320 can be used to decode encoded RDS data within the FM radio signal.
Transceiver core 202 may also include RDS encoder 324 for encoding RDS data of an FM radio signal, FM modulator 316 for modulating the FM radio signal, and FM transmitter 306 for transmitting the FM radio signal via antenna 208. As noted above, according to one aspect of the disclosure, receiving an FM radio signal by transceiver core 202 is not necessary for interaction between transceiver core 202 and host processor 204 or for reducing the amount of processing to be performed by host processor 204 when transmitting a radio signal.
Transceiver core 202 also includes microprocessor 322 which, among other things, is capable of processing received RDS data (e.g., formatting, storing and/or interleaving RDS data). Microprocessor 322 can access program read only memory (ROM) 310, program random access memory (RAM) 312 and data RAM 314. Microprocessor 322 can also access control registers 326, each of which includes at least one bit. When handling RDS data, control registers 326 can provide at least an indication(s) whether host processor 204 should receive an interrupt(s) by, for example, setting a bit(s) in a corresponding status register(s).
In addition, control registers 326 can be seen to include parameters to filter RDS data and to reduce the number of interrupts to host processor 204. According to one aspect, these parameters are configurable (or controllable) by host processor 204, and depending on the parameter(s), transceiver core 202 can filter some or all of RDS data or not filter the RDS data. Furthermore, depending on the parameter(s), the number of interrupts to host processor 204 can be reduced or not reduced.
In addition, transceiver core 202 may include a control interface 328 which, among other things, is used in asserting host interrupts to host processor 204. In this regard, control interface 328 can access the control registers 326, since these registers are used for determining which interrupts are to be received by host processor 204.
FIG. 4 is a conceptual block diagram illustrating examples of different implementations of transceiver core 202. As shown in this diagram, transceiver core 202 can be integrated into various targets and platforms. These targets/platforms include, but are not limited to, a discrete product 402, a die inside a System in Package (SIP) product 404, a core integrated on-chip in discrete radio frequency integrated circuit (RF IC) 406, a core integrated on-chip in radio front end base band system-on-chip (RF/BB SOC) 408 and a core-integrated on-chip in die 410. As such, transceiver core 202 and host processor 204 can be implemented on a single chip or a single component, or can be implemented on separate chips or separate components.
FIG. 5 is a conceptual block diagram illustrating an example of benefits provided by using a transceiver core with a host processor. As shown in FIG. 5, host processor 204 can offload processing to transceiver core 202. Such offload processing can include, for example, formatting, storing, interleaving and/or transmitting RDS data. In addition, the number of interrupts asserted to host processor 204 can be reduced, since transceiver core 202 can, for example, filter the RDS data and/or include a buffer for the RDS data. In addition, the amount of traffic to host processor 204 can be reduced. As such, power and memory efficiency of the host processor is seen to be improved.
FIG. 6 is a conceptual block diagram illustrating an example of the structure of the baseband coding of RDS data. RDS data may include one or more RDS groups. Each RDS group may have 104 bits. Each RDS group 602 may include 4 blocks, each block 604 having 26 bits each. More particularly, each block 604 may include an information word 606 of 16 bits and a checkword 608 of 10 bits.
FIG. 7 is a conceptual block diagram illustrating an example of a message format and address structure for RDS data. Block 1 of every RDS group may include a program identification (PI) code 702. Block 2 may include a 4-bit group type code 706, which generally specifies how the information within the RDS group is to be applied. Groups are typically referred to as type 0 to 15 according to binary weighting A3=8, A2=4, A1=2, A0=1. Further, for each type 0 to 15, a version A and a version B may be available. This version may be specified by a bit 708 (i.e., B0) of block 2, and a mixture of version A and version B groups may be transmitted on a particular FM radio station. In this regard, if B0=0, the PI code is inserted in block 1 only (version A) and if B0=1, the PI code is inserted in block 1 and block 3 for all group types (version B). Block 2 also may include 1 bit for a traffic code 710, and 4 bits for a program type (PTY) code 712.
FIG. 8 is a conceptual block diagram illustrating an example of an RDS group data structure. Each RDS group data structure 802 may correspond to an RDS group 602 including plural blocks 604. For each of the plural blocks 604, the RDS group data structure may store the least significant bits (LSB) and most significant bits (MSB) of the information word 606 as separate bytes. In addition, RDS group data structure 802 may include a block status byte 804 for each block, where the block status byte 804 may indicates a block identification (ID) and whether there are uncorrectable errors in the block.
The RDS group data structure 802 represents an exemplary data structure which can be processed by transceiver core 202. In this regard, transceiver core 202 includes a core digital component and a core firmware component, which are described in more detail below with reference to FIG. 9. The core digital component correlates each block 604 of an RDS group 602 with the associated checkword 608, and generates a block status byte 804 indicating the block ID and whether there are any uncorrectable errors in the block 604. The 16 bits of the information word 606 are also placed in the RDS group data structure 802. The core firmware typically receives RDS group data 802 from the core digital component approximately every 87.6 msec.
It should be understood that the structures of RDS data described above are exemplary, and the subject technology is not limited to these exemplary structures of RDS data and applies to other structures of data.
FIG. 9 is a conceptual block diagram illustrating a core digital component and core firmware component of transceiver core 202. As noted above, core firmware component 904 can receive RDS group data 802 from core digital component 902 approximately every 87.6 msec. The filtering and data processing performed by core firmware component 904 can potentially reduce the number of host interrupts and improve host processor utilization.
Core firmware component 904 may include host interrupt module 936 and interrupt registers 930 for asserting interrupts to host processor 204. Interrupt registers 930 may be controllable by host processor 204. Core firmware component 904 may also include filter module 906, which may include RDS data filter 908, RDS program identification (PI) match filter 910, RDS Block-B filter 912, RDS group filter 914 and RDS change filter 916. In addition, core firmware component 904 may include group processing component 918. Core firmware component 904 may also include RDS group buffers 924, which may be utilized to reduce the number of interrupts to host processor 204. The filtering of RDS data, processing of group types 0 and 2, and use of RDS group buffers 924 will be described later in more detail. Core firmware component 904 may also include data transfer registers 926 and RDS group registers 928, each of which may be controllable by host processor 204.
Core digital component 902 may provide data 932 including mono-stereo, RSSI level, interference (IF) count and sync detector information to core firmware component 904. This data 932 is receivable by status checker 934 of core firmware component 904. Status checker 934 processes data 932, and the processed data may result in an interrupt being asserted to host processor 204 via host interrupt module 936.
Filter module 906, which may include various filter components, will now be described in greater detail. RDS data filter 908 of filter module 906 can filter out an RDS group having either an uncorrectable error or a Block-E group type. Host processor 204 can enable transceiver core 202 so that RDS data filter 908 discards erroneous or unwanted RDS groups from being processed further. As previously noted, RDS data filter 908 may receive a group of RDS blocks approximately every 87.6 msec.
If the block ID (which is correlated into the block status for a particular block) within an RDS group is “Block-E” and the RDSBLOCKE is not set in an ADVCTRL register of transceiver core 202, the RDS data group is discarded. If, however, the RDSBLOCKE is set in the ADVCTRL register, the data group is placed in RDS group buffer 924, thus bypassing any further processing. In this regard, block-E groups may be used for paging systems in the United States. They may have the same modulation and data structure as RDS data but may employ a different data protocol.
If block status 804 (see FIG. 8) of an RDS group is marked as “Uncorrectable” or “Undefined” and the RDSBADBLOCK is not set in the ADVCTRL register, the RDS data group is discarded. Otherwise, the data group is placed directly into RDS Group buffer 924. All other data groups are forwarded on through filter module 906 for further processing.
The next filter within filter module 906 is RDS PI match filter 910. RDS PI match filter 910 may determine whether an RDS group has a program identification (ID) which matches a given pattern, so that an interrupt to host processor 204 can be asserted. Host processor 204 can enable transceiver core 202 to assert an interrupt whenever the program ID in block 1 and/or the bits in block 2 match a given pattern.
RDS PI match filter 910 is enabled when host processor 204 writes the PICHK bytes in the RDS_CONFIG data transfer (XFR) mode of transceiver core 202. When RDS PI match filter 910 receives an RDS data group, it will compare the program identification (PI) in block 1 with the PICHK word provided by host processor 204. If the PI words match, then the PROGID interrupt status bit is set, and an interrupt is sent to host processor 204, if the PROGIDINT interrupt control bit of transceiver core 202 is enabled.
The PI can be a 4-digit Hex code unique for each station/program. As such, the capability of RDS PI match filter 910 could be used, for example, in cases where host processor 204 wants to know immediately whether a currently tuned channel is the program that it desires.
The next filter of filter module 906 is RDS Block-B filter 912. RDS Block-B filter 912 may determine whether an RDS group has a block 2 (i.e., Block-B) entry which matches a given Block-B parameter, so that an interrupt to host processor 204 can be asserted. RDS Block-B filter 912 can provide a quick route of specific data to host processor 204. If block 2 of the RDS data group matches the host processor defined Block-B filter parameters, then the group data is immediately made available for host processor 204 to process. No further processing of the RDS group data is performed in transceiver core 202.
For example, FIG. 10 is an exemplary sequence chart illustrating one case of a host receiving RDS Block-B data. As can be seen in FIG. 10, host processor 204 can communicate with transceiver core 202. In this example, a Block-B match is detected in transceiver core 202, and host processor 204 becomes aware that a Block-B match has occurred.
Referring back to FIG. 9, the next filter of filter module 906 is RDS group filter 914. RDS group filter 914 can filter out an RDS group having a group type which is not within a given one or more group types. In other words, RDS group filter 914 can provide a means for host processor 204 to select which RDS group types to store into RDS group buffers 924, so that host processor 204 only has to process the data in which it is interested. Thus, host processor 204 can enable transceiver core 202 to only pass selected RDS group types.
In this regard, core firmware component 904 can be configured (e.g., by host processor 204) to filter out, if so desired, or not to filter out RDS group data for group type 0 or group type 2. FIG. 9 depicts that RDS group data 802 with either a group type 0 or group type 2 are processed by group processing component 918, if RDSRTEN, RDSPSEN, and/or RDSAFEN are set in the ADVCTRL register.
Still referring to RDS group filter 914, host processor 204 may filter out a specific group type (i.e., Core discards) by setting a bit in the following data transfer mode (RDS_CONFIG) registers in transceiver core 202:

    
    
        GFILT—0—Block-B group type filter byte 0 (group type 0A-3B).
        GFILT—1—Block-B group type filter byte 1 (group type 4A-7B).
        GFILT—2—Block-B group type filter byte 2 (group type 8A-11B).
        GFILT—3—Block-B group type filter byte 3 (group type 12A-15B).
    
    


Each bit in RDS group filter 914 represents a particular group type. FIG. 11 is a conceptual block diagram illustrating an example of RDS group filter 914. When transceiver core 202 is powered on or reset, RDS group filter 914 is cleared (all bits are set back to “0”). If a bit is set (“1”) then that particular group type will not be forwarded.
Returning to FIG. 9, the next filter of filter module 906 is RDS change filter 916, which filters out an RDS group having RDS group data which has not changed. Host processor 204 can enable transceiver core 202 to pass the specified group types only if there are changes in RDS group data. RDS group data that passes through RDS group filter 914 may be applied to RDS change filter 916. RDS change filter 916 may be used to reduce the amount of repeat data for each particular group type. To enable RDS change filter 916, host processor 204 may set the RDSFILTER bit in the ADVCTRL register of transceiver core 202.
In accordance with one aspect of the disclosure, filter module 906 is capable of performing various types of filtering of RDS group data 802, so as to reduce the number of interrupts to host processor 204. As noted above, core firmware component 904 may also include group processing component 918, which will now be described in more detail.
Group processing component 918 may include RDS group type 0 data processor 922 and RDS group type 2 data processor 920. With reference to RDS group type 0 data processor 922, this processor may determine whether an RDS group has a group type 0 and whether there is a change in program service (PS) information for the RDS group, so as to assert an interrupt to host processor 204 when such a determination is positive.
Transceiver core 202 has the capability of processing RDS group type 0A and 0B data. This type of group data is typically considered to have the primary RDS features (e.g., program identification (PI), program service (PS), traffic program (TP), traffic announcement (TA), seek/scan program type (PTY) and alternative frequency (AF)) and is typically transmitted by FM broadcasters. For example, this type of group data provides FM receivers with tuning information such as the current program type (ex., “Soft Rock”), program service name (ex., “ROCK1053”) and possible alternative frequencies that carry the same program.
In this regard, FIG. 12 is a conceptual block diagram illustrating an example of RDS basic tuning and switching information for RDS group type 0A. It shows, among other data, group type code 1202, program service name and DI segment address 1204, alternative frequency 1206, and program service name segment 1208. FIG. 13, on the other hand, is a conceptual block diagram illustrating an example of RDS basic tuning and switching information for group type 0B. It shows, among other data, group type code 1302, program service name and DI segment address 1304, and program service name segment 1306.
According to one aspect of the disclosure, transceiver core 202 can assemble and validate program service character strings, and only when the string changes, or is repeated once, transceiver core 202 alerts host processor 204. Host processor 204 may only have to output the indicated string(s) on its display. To enable the RDS program service name feature, host processor 204 can set the RDSPSEN bit in the ADVCTRL register of transceiver core 202.
With further reference to group type 0 processing, the program service (PS) table event may consist of an array of eight program service name strings (8 characters in length). This PS table may be seen to handle the United States radio broadcasters' usage of program service as a text-messaging feature similar to radio text.
In this regard, FIG. 14 is a conceptual block diagram illustrating an example of a format for program service (PS) table 1400. The first byte of PS table 1400 may consist of bit flags (PS0-PS7) used to indicate which program service names in PS table 1400 are new or repeats. For example, if PS2-PS4 are set and the update bit (“U”) is set, then host processor 204 only cycles through PS2-PS4 on its display.
The next five bits in PS table 1400 are the current program type (e.g., “Classic Rock”). The update flag (“U”) indicates whether the indicated program service names are new (“0”) or repeats (“1”). The 16-bits of program identification (PI) follow.
The next four bits in PS table 1400 are flags extracted from the group 0 packet, as follows:

    
    
        TP—traffic program
        TA—traffic announcement
        MS—music/speech switch code
        DI—decoder identification control code

The remaining bytes in PS table 1400 are the 8 PS names (8 characters each).

    
    


Examples of the usage of a PS table will now be described with reference to FIGS. 15 to 17. It should be noted that the PS tables in FIGS. 15 to 17 are in a different format than that of FIG. 14, to help demonstrate its usage. FIG. 15 is a conceptual block diagram illustrating an example of generating a PS name table 1504. In this example, the broadcaster is constantly transmitting the same sequences of group 0 packets 1502 indicating the artist and song title. Transceiver core 202 re-assembles and validates each PS name string and update PS table 1504 as needed.
FIG. 16 is a conceptual diagram illustrating an example of PS name data and corresponding text displayed on a host system 200. In FIG. 16, the content of the last PS table 1602 received by host processor 204 is shown. As such, host processor 204 should read the update flag, which indicates repeat, and cycle through the PS names as indicated in the PS bit flags for PS2 through PS5. These PS names can then be displayed on host display 1604.
Enabling the foregoing validation feature as well as filtering out group 0A/0B packets from RDS group buffers 924 (see FIG. 9) can greatly reduce the amount of traffic from transceiver core 202 to host processor 204. Only a few PS table events will occur during a song or a commercial break instead of many group 0 packets.
Still referring to group type 0 processing, FIG. 17 is a sequence chart illustrating an example of processing RDS data with group type 0. More particularly, FIG. 17 provides an example of how host processor 204 can enable the RDS group type 0 data processing feature and receive PS table data from transceiver core 202.
Host system 300 may provide for dynamic program service names for group type 0 data. The RBDS standard (North American equivalent of the European RDS standard) adopted less stringent requirements for PS usage. Broadcasters in the United States use the program service name to not only present call letters (“KPBS”) and slogans (“Z-90”), but also use it to also transmit song title and artist information. Therefore, the PS may be continuously changing.
In this regard, FIGS. 18A to 18J are conceptual diagrams illustrating an example of dynamic PS name data and corresponding display text on host processor 204. In this example, an FM broadcaster uses the program service name to transmit “Soft,” “Rock,” “Kicksy,” and “96.5” repeatedly during a commercial break. When a song starts to play, the broadcaster then transmits “Faith by,” “George,” and “Michael” continuously during the song. The broadcaster constantly repeats PS strings since it does not know when receivers are tuned into the station. Such repeated transmission can lead to numerous interrupts being sent to host processor 204. In each of FIGS. 18A to 18J, element 1802 corresponds with the PS name table and element 1804 corresponds with the host display.
In FIG. 18A, which can be seen to correspond with a first event, transceiver core 202 is enabled during the broadcaster's commercial break and starts receiving RDS group type 0A segments 0-3 that create “Rock”. This string is placed in PS table 1802, the corresponding PS bit is set, and the update flag is set to new (“0”). The current program type (PTY), program identification (PI), and other fields are also filled in.
In addition, the RDSPS interrupt status bit is set and if the RDSPSINT interrupt control bit is enabled, an interrupt is generated for host processor 204. Once host processor 204 reads PS table 1802, it detects that the PS name in the table is new and refresh its display 1804 with the indicated PS string.
In FIG. 18B, which can be seen to correspond with a next event, the broadcaster transmits the same PS name again. Transceiver core 202 receives the next group 0A segments 0-3 which creates an 8-character string that matches an element already in PS table 1802. The repeated PS bit is set, and the update flag is set to repeat (“1”). An interrupt is generated for host processor 204, if enabled, and host processor 204 reads PS table 1802 and leaves its display 1804 with the repeated PS name.
In FIG. 18C, the broadcaster transmits a new PS name. Transceiver core 202 receives group 0A segments 0-3 “Kicksy”. Transceiver core 202 places the PS string in the next available slot in PS table 1802, sets the corresponding PS flag bit, and sets the update flag to new (“0”).
In FIG. 18D, the broadcaster again transmits a new PS name. Transceiver core 202 receives group 0A segments 0-3 that create the string “96.5”. Transceiver core 202 places the PS string in next available slot in PS table 1802, sets the corresponding PS flag bit, and sets the update flag to new (“0”).
In FIG. 18E, the broadcaster transmits the PS name “Soft” and transceiver core 202 updates PS table 1802. In FIG. 18F, the broadcaster is repeating the four PS names throughout the commercial break. Transceiver core 202 receives “Rock” and so it sets the corresponding PS flag bit and the update flag to repeat (“1”).
In FIG. 18G, transceiver core 202 receives “Kicksy” again and sets the PS flag bit and the update flag to repeat (“1”). Since there are now multiple program service names that are flagged as repeat, host processor 204 cycles through the PS names with a pre-defined delay (e.g., 2 seconds). If host processor 204 receives a PS table that indicates new PS names, it cancels the periodic display timer and displays the new PS name.
In FIG. 18H, transceiver core 202 receives the repeated string “96.5” and sets the corresponding PS bit and the update flag to repeat (“1”).
In FIG. 18I, transceiver core 202 receives the repeated string “Soft” and sets the corresponding PS bit and the update flag to repeat (“1”). At this point transceiver core 202 stops sending PS table events to host processor 204 since the PS names “Soft”, “Rock”, “Kicksy”, and “96.5” repeat during the commercial break (which can last a few minutes). Host processor 204 uses the last PS table 1802 received to update its display 1804.
Turning to FIG. 18J, after a couple of minutes the commercial break is over and a song starts to play. Transceiver core 202 receives RDS group type 0A segments 0-3 that create “George”. This string is placed in PS table 1802, the corresponding PS bit is set, and the update flag is set to new (“0”).
It should be noted that the RDS group type 0 data processing feature was tested with a real life broadcast. During a period of time ( ̃10 minutes), a local broadcaster transmitted 2,973 group type 0A during a Song1→Commercial Break→Song2 sequence. With the RDSPSEN feature enabled, transceiver core 202 sent 49 PS tables to host processor 204.
If host processor 204 wishes to process RDS group type 0A itself, it could configure RDS group filter 914 (see FIG. 9) to route all the group type 0A packets. In this example, host processor 204 would have received 2,973 group type 0A packets. Host processor 204 would then have to spend processor time validating and assembling the program service names. In this example, the savings in host processor “interrupts” using the RDS group type 0 data processing feature would have been 98.4%.
Still referring to group type 0 data, host system 200 may also provide for static program service names. The design intent of the program service may be to provide a label for the receiver preset which is invariant, since receivers incorporating the alternative frequency (AF) feature will switch from one frequency to another in following a selected program. In Europe, the PS name of a tuned service is inherently static. Transceiver core 202 uses the same PS table event to notify host processor 204 of a new program service name. Host processor 204 can retrieve the PS table at anytime.
FIGS. 19A to 19B are conceptual diagrams illustrating an example of static PS name data and corresponding display text on host processor 204. In this example, a European user tunes to a new channel (“CAPITAL”). In each of FIGS. 19A to 19B, element 1902 corresponds with the PS name table and element 1904 corresponds with the host display.
In FIG. 19A, which can be seen to correspond with a first event, host processor 204 tunes transceiver core 202 to a new frequency. Transceiver core 202 receives RDS group type 0A segments 0-3 that create “CAPITAL”. This string is placed in PS table 1902, the corresponding PS bit is set, and the update flag is set to new (“0”). The current program type is also filled in. Host processor 204 receives the PS table event and updates its display 1904.
In FIG. 19B, which can be seen to correspond with a next event, transceiver core 202 receives sequential segments 0-3 which creates an 8-character string that matches an element already in PS table 1902. The repeated PS bit is set and the update flag is set to repeat (“1”).
In this regard, host processor 204 leaves the repeat program service name on its display 1904 until it receives another PS table event that has the update flag set to new. This would occur if the traffic announcement (TA) field changes or if host processor 204 tunes to a different station.
Another aspect of group type 0 data relates to alternative frequency (AF) list information. Transceiver core 202 may determine whether an RDS group has a group type 0 and whether there is a change in AF list information, so that an interrupt can be asserted to host processor 204. In one example, transceiver core 202 will extract the AF list from group type 0A and only when the list changes, will transceiver core 202 provide the AF list in a host control interface (HCI) event. Host processor 204 could use this list to manually tune the FM radio to an alternative frequency. In addition, if host processor 204 receives an AF list for the currently tuned station, it can enable an AF jump search mode if the received signal strength goes below a certain threshold. To enable the RDS alternative frequency list feature, host processor 204 can set the RDSAFEN bit in the ADVCTRL register.
The following generally applies to AF list information according to one aspect of the disclosure:

    
    
        Only AF Method A (group 0A) is supported.
        Any LF/MF frequencies are not included in the AF list sent to host processor 204.
        AF codes in Enhanced Other Network (EON) group type 14A are not supported.
        The AF list event contains the currently tuned frequency, program identification (PI) code, the number of AFs in the list, and the list of AFs.
    
    


FIG. 20 is a conceptual block diagram illustrating an example of an alternative frequency (AF) list format. Host processor 204 uses the RDS_AF—0/1 data transfer (XFR) modes to read AF list 2000 from transceiver core 202.
As noted above, group processing component 918 (see FIG. 9) may also include RDS group type 2 data processor 920, which will now be described in greater detail. RDS group type 2 data processor 920 may determine whether an RDS group has a group type 2 and whether there is a change in radio text (RT) information for the RDS group, so as to assert an interrupt to the host processor when such a determination is positive. RT is typically considered to be a secondary feature of RDS, and allows radio broadcasters to transmit up to 64 characters of information to the listener such as current artist, song title, station promotions, etc.
According to one aspect of the disclosure, transceiver core 202 may extract out the RT and provide up to a 64 character string, along with the PI and PTY, to host processor 204 only when the RT string changes. Transceiver core 202 may assemble and validate the radio text character string, and when the string changes, transceiver core 202 interrupts host processor 204, if RDSRTINT is enabled. Host processor 204 may then read the radio text by using the RDS_RT—0/1/2/3/4 data transfer (XFR) modes. Host processor 204 may only need to output the string on its display. The radio text may end with a carriage return (0x0D) but some broadcasters pad the string with spaces (0x20). To enable the RDS group type 2 data processing feature, host processor 204 can set the RDSRTEN bit in the ADVCTRL register.
FIG. 21 is a conceptual block diagram illustrating an exemplary format of RDS radio text for group type 2A. It shows, among other data, group type code 2102, text segment address code 2104, and radio text segments 2106 and 2108. FIG. 22, on the other hand, is a conceptual block diagram illustrating an exemplary format of RDS radio text for group type 2B. It shows, among other data, group type code 2202, text segment address code 2204, and radio text segment 2206.
It should be noted that the RDS group type 2 data processing feature was tested with a real life broadcast. During a period of time ( ̃10 minutes), a local broadcaster transmitted 3,464 group type 2A during a Song1→Commercial Break→Song2 sequence. With the RDSRTEN advanced feature enabled, transceiver core 202 only sent three Radio Text events to host processor 204.
If RDS Block-B filter 912 (see FIG. 9) was configured to route all group type 2A, host processor 204 would have been interrupted with BFLAG 3,464 times. Host processor 204 would then have to spend processor time validating and assembling the text string. In this example, the savings in host processor “interrupts” using the RDS group type 2 data processing would have been 99.9%.
FIG. 23 is a sequence chart illustrating an example of the RDS group type 2 data processing. It shows an example of how host processor 204 would enable the RDS group type 2 data processing feature and receive radio text data.
As illustrated above, according to one aspect of the disclosure, group processing component 918 (see FIG. 9) includes RDS group type 0 data processor 922 and RDS group type 2 data processor 920 for processing these specific group types. As noted above, core firmware component 904 may also include RDS group buffers 924, which will now be described in more detail. RDS group buffers 924 may store plural RDS groups before interrupting host processor 204, so as to reduce the number of interrupts for new RDS data.
FIG. 24 is a conceptual block diagram illustrating an example of RDS group buffers. Transceiver core 202 may contain dual RDS group buffers 2402 and 2404 (corresponding to element 924 in FIG. 9) that can hold up to 21 RDS groups. An RDS group contains, for example, 4 blocks. Each block contains two information bytes and one status byte, as previously described with reference to FIG. 8.
Host processor 204 configures the buffer threshold with the DEPTH parameter of the RDS_CONFIG data transfer (XFR) mode. When transceiver core 202 reaches the buffer threshold, it can notify host processor 204 and switch to the other buffer where it begins filling with the next RDS group. The dual RDS group buffers allow host processor 204 to read from one buffer while transceiver core 202 writes to the other. It should be noted that host processor 204 reads the contents of one RDS group buffer before transceiver core 202 fills the other buffer (to the pre-defined threshold) or else it can lose the remaining data in that buffer.
Host processor 204 can also set a flush timer to prevent groups in a buffer from becoming “stale.” The flush timer can be configured by writing the FLUSHT in the RDS_CONFIG data transfer (XFR) mode.
FIG. 25 is a sequence chart illustrating an example of buffering and processing RDS group data. As can be seen in FIG. 25, host processor 204 can read the contents of the RDS group buffers 924 of FIG. 9 by communicating with transceiver core 202.
FIG. 26 is a conceptual block diagram illustrating an example of a configuration for transceiver core 202 for performing various levels of RDS data processing. As shown in FIG. 26, transceiver core 202 can be configured to perform various levels of RDS processing.
FIG. 27 is a conceptual diagram illustrating an example of data pipes between a transceiver core and a host processor for transmitting RDS data. In this regard, data pipes 2702, 2704, 2706 and 2708 are virtual data pipes which can be used to pass RDS data between transceiver core 202 and host processor 204. More particularly, for a “raw” RDS group data transfer mode, data pipe 2702 can be used for passing raw RDS group data. For an RDS program service (PS) data transfer mode, data pipe 2704 can be used for passing RDS PS data. For an RDS radio text (RT) data transfer mode, data pipe 2706 can be used for passing RDS RT data. Data pipe 2708 can be used for passing RDS alternative frequency (AF) information. The term “raw” indicates that the data is not processed within transceiver core 202. In another aspect of the disclosure, one data pipe may be used to pass RDS data of various types.
One example of host processor 204 using one or more of data pipes 2702, 2704, 2706 and 2708 can be when a user plays an MP3 song on a handset. In this example, transceiver core 202 can be used to transmit the song to a nearby car stereo. Host processor 204 can pick out, for example, the song title and artist and send text data to transceiver core 202 via RDS PS data pipe 2704 or RDS RT data pipe 2706.
In general, transceiver core 202 can convert RDS data passed to it via data pipe(s) from host processor 204 as follows:

    
    
        RDS Program service (PS) data  converted into RDS group type 0A data
        RDS radio text (RT) data  converted into RDS group type 2A data
        Raw RDS group data  not converted into RDS group type data (transmitted as is)
    
    


By passing data through the data pipes, host processor 204 does not necessarily need to handle the formatting of RDS packets. Rather, host processor 204 may only have to pass text strings to transceiver core 202. Transceiver core 202 can format the data into the appropriate RDS group type packets and send those RDS group type packets out over-the-air at an appropriate repetition rate.
FIG. 28 is a conceptual diagram illustrating an exemplary table of data pipes between a transceiver core and a host processor for transmitting RDS data. FIG. 28 depicts the data pipe type, direction, and data transfer modes associated with each of the data pipes.
In addition to converting RDS data into specific RDS group type data, transceiver core 202 can interleave RDS data of different types. FIG. 29 is a conceptual diagram illustrating an example of interleaving RDS data of different types. In this regard, host processor 204 may choose to pass RDS data through multiple data pipes at the same time. When this occurs, transceiver core 202 can interleave the RDS data of different types, in an attempt to meet a desired repetition rate, which may correspond with an RDS-standardized repetition rate.
As can be seen in FIG. 29, the interleaving of RDS data can be based on which types of RDS data are being passed by host processor 204 or which RDS data transfer modes are enabled by host processor 204. Host processor 204 can selectively enable any one or more of the RDS data transfer modes simultaneously or at different times. As an example, if host processor 204 enables the RDS PS data transfer mode and the RDS RT data transfer mode, then it may pass the RDS PS data and the RDS RT data to transceiver core 202, and transceiver core 202 may transmit two RDS PS data for every one RDS RT data. This is illustrated in the first column of FIG. 29, and the RDS PS data is represented as 0A (i.e., RDS group type 0A) after its conversion to RDS group type 0A as described above, and the RDS RT data is represented as 2A (i.e., RDS group type 2A) after its conversion to RDS group type 2A.
As another example, if host processor 204 enables the RDS RT data transfer mode and the raw RDS group data transfer mode, it may pass the RDS RT data and the raw RDS group data to transceiver core 202, and transceiver core 202 may transmit two raw RDS group data for every one RDS RT data. This is illustrated in the second column of FIG. 29, and the raw RDS group data is represented as RAW, and the RDS RT data is represented as 2A (i.e., RDS group type 2A).
As yet another example, if host processor 204 enables the RDS PS data transfer mode and the raw RDS group data transfer mode, then it may pass the RDS PS data and the raw RDS group data to transceiver core 202, and transceiver core 202 may transmit one RDS PS data for every one raw RDS group data. This is illustrated in the third column of FIG. 29, and the RDS PS data is represented as 0A (i.e., RDS group type 0A), and the raw RDS group data is represented as RAW.
As yet another example, if host processor 204 enables all of the RDS data transfer modes (e.g., the RDS PS data transfer mode, the RDS RT data transfer mode, and the raw RDS group data transfer mode), then it may pass the RDS PS data, the RDS RT data, and the raw RDS group data to transceiver core 202, and transceiver core 202 may transmit two RDS PS data and two raw RDS group data for every one RDS RT data. This is illustrated in the fourth column of FIG. 29.
Interleaving of RDS data for two or more RDS data transfer modes is not limited to the examples illustrated above. If host processor 204 enables two or more RDS data transfer modes, then transceiver core 202 may receive multiple RDS data for the RDS data transfer modes (e.g., RDS PS data for the RDS PS data transfer mode, RDS RT data for the RDS RT data transfer mode, and raw RDS group data for the raw RDS group data transfer mode), and transceiver core 202 may interleave the multiple RDS data in many other ways for transmission.
Furthermore, if RDS PS data, RDS RT data or raw RDS group data is passed separately or the RDS PS data transfer mode, the RDS RT data transfer mode or the RDS group data transfer mode is enabled separately by host processor 204, then transceiver core 202 may transmit the RDS data of that particular type separately without interleaving.
FIG. 30 is a state machine diagram illustrating exemplary events and states for transmitting RDS data. This state machine can be included within transceiver core 202. Among other things, FIG. 30 depicts transmit (TX) calibrate state 3002, TX idle state 3004, radio off state 3006, TX tuning state 3008, TX tuned state 3010, TX raw state 3012, TX radio text (RT) state 3014, TX RT raw state 3016, TX program service (PS) raw state 3018, TX PS state 3020, TX RT PS raw state 3022 and TX RT PS state 3024. In addition, transitions between these states and actions are depicted.
As noted above, host processor 204 can pass raw RDS group data to transceiver core 202, for transmission by transceiver core 202. In this regard, transceiver core 202 can include a raw RDS buffer that can hold, for example, 62 groups of raw RDS group data (information words only). Transceiver core 202 can calculate and append the 10-bit checkword. Once host processor 204 fills the raw RDS buffer with the desired RDS group data, it can command transceiver core 202 to send the raw RDS group data continuously or as “one-shot.”
FIG. 31 is a sequence chart illustrating an example of transmitting raw RDS group data on a “one-shot” basis. In this regard, transmission on a “one-shot” basis corresponds with transmitting all RDS group data at once. FIG. 31 depicts an example of host processor 204 sending up to, for example, 62 groups of raw RDS group data to transceiver core 202, and commanding transceiver core 202 to transmit all groups of the raw RDS group data at once. In “one-shot” mode, an RDSDAT interrupt can be set after every raw RDS group data is transmitted (unless masked out in INTCTRL). After the entire raw RDS group data in the raw RDS buffer is transmitted, transceiver core 202 can set the TXRDS interrupt.
FIG. 32 is a sequence chart illustrating an example of transmitting raw RDS data on a continuous basis. In this regard, transmission on a continuous basis corresponds with transmitting all of the raw RDS group data continuously. FIG. 32 depicts an example of host processor 204 sending up to 62 raw RDS group data to transceiver core 202 and commanding transceiver core 202 to transmit all of the raw RDS group data continuously. Host processor 204 can stop the transmission by issuing an RDS TX group command with the stop parameter selected.
FIGS. 33A to 33H are conceptual diagrams illustrating an example in which a host processor requests all raw RDS group data to be transmitted once (i.e., a “one-shot” basis). These figures depict an example of host processor 204 configuring the raw RDS buffer and issuing a “one-shot” command.
In FIG. 33A, which can be seen to correspond with a first event in a sequence of events, the initial state of the raw RDS buffer is shown. In particular, the raw RDS buffer can be empty with no TX activity. “H Write” of FIG. 33A points to a location in the raw RDS buffer to which host processor 204 starts to write raw RDS group data, and “TX Read” points to a location in the raw RDS buffer to which transceiver core 202 starts to retrieve raw RDS group data to be transmitted over-the-air.
In FIG. 33B, which can be seen to correspond with a next event, host processor 204 can transmit an MP3 tag. In particular, RDS groups can be written to the raw RDS buffer and stay in the raw RDS buffer until host processor 204 starts transmission. Each time host processor 204 writes to the raw RDS buffer, transceiver core 202 can return how many groups of raw RDS group data have been actually written to the raw RDS buffer. In this example, host processor 204 wishes to transmit a MP3 tag that consists of 72 groups of raw RDS group data, host processor 204 writes 8 groups with RDS_TX_GROUPS data transfer (XFR) mode, the CTRL field is set to “stop,” and 0 groups are transmitted by transceiver core 202.
In FIG. 33C, host processor 204 can write the next 8 groups of raw RDS group data, and the buffer control can still be set to “stop.” FIG. 33D depicts that host processor 204 can write 40 more groups of raw RDS group data to the raw RDS buffer.
In FIG. 33E, host processor 204 can attempt to write 8 more groups to the raw RDS buffer. In addition, CTRL can be set to “one-shot,” corresponding to host processor 204 starting transmission in a “one-shot” mode. Since there is only room for 6 more groups, transceiver core 202 can inform host processor 204 that only 6 groups have been written. At this point, host processor 204 still has 10 groups left that it wants to place in the raw RDS buffer.
In FIG. 33F, transceiver core 202 can start transmitting groups of raw RDS group data, and host processor 204 can fill the remaining groups of raw RDS group data into the raw RDS buffer. In this regard, transceiver core 202 has transmitted 4 groups. Host processor 204 can monitor the RDSDAT interrupt to determine how many groups have been transmitted, and host processor 204 can also read the RDSGROUP register. Host processor 204 can fill the raw RDS buffer by writing the next 4 groups of raw RDS group data.
FIG. 33G corresponds with host processor 204 finishing the writing of all the groups. In particular, transceiver core 202 can transmit 9 groups, and host processor 204 can write the remaining groups to the raw RDS buffer.
FIG. 33H corresponds with group transmission being complete. In this regard, no more additional groups are sent from host processor 204, and transceiver core 202 can finish processing the raw RDS buffer. Once the raw RDS buffer is empty, the state transitions to IDLE.
As noted above, host processor 204 can also request for continuous, rather than “one shot” transmission of RDS data. FIGS. 34A to 34E are conceptual diagrams illustrating an example in which host processor 204 requests for all groups of raw RDS group data to be transmitted continuously. In this regard, FIGS. 34A to 34E follow where FIGS. 33A to 33H left off, and can be viewed as a continuation thereof. FIGS. 34A to 34E illustrate an example of issuing a continuous command.
In FIG. 34A, host processor 204 can transmit a new MP3 tag. In particular, a user can select a new MP3 song/track, and host processor 204 can write the RDS information to the raw RDS buffer as described above. In this example, host processor 204 can transmit the MP3 tag as 48 groups of raw RDS group data, 48 groups can be written to the raw RDS buffer, and 0 groups are transmitted.
FIG. 34B corresponds with host processor 204 selecting continuous transmission. When host processor 204 sends the last groups, it can choose to transmit these groups continuously. Each time host processor 204 asks transceiver core 202 to transmit continuously, the current read (C Read) position can be saved and can become the new start transmission. Once the entire raw RDS group data in the raw RDS buffer has been transmitted, the process can start over again from the saved position (C Read).
In FIG. 34C, transceiver core 202 can transmit 39 groups over the FM frequency, and in FIG. 34D, transceiver core 202 can re-transmit the groups, where transmission can start over again at C Read.
In this regard, it should be noted that before any new groups of raw RDS group data are written, the raw RDS buffer can be cleared when in continuous mode. Otherwise, a pointer position may be incorrect, as shown in FIG. 34E.
FIG. 34E corresponds with host processor 204 appending more groups to the raw RDS buffer. Two groups have been transmitted from C Read when host processor 204 writes more groups to the raw RDS buffer (marked as continuous). In this example, the continuous read pointer would be set to the current read pointer.
Transmission of RDS program service (PS) data by host system 200 will now be described. In this regard, FIG. 35 is a sequence chart illustrating an example of transmitting RDS data with PS information. The transmit (TX) RDS program service name capability can provide a means for host processor 204 to send multiple program service (PS) names to transceiver core 202, to be transmitted over-the-air via, for example, RDS group type 0A packets. This can be seen as an inverse to the RDS program service names described above with reference to FIGS. 14 to 19B.
Using RDS PS data pipe 2704 of FIG. 27, host processor 204 can send to transceiver core 202 multiple PS strings without converting (or translating) them into, for example, the RDS group type 0A format. For the RDS PS data transfer mode, transceiver core 202 may include an RDS PS table that may contain an RDS program identification (PI), RDS program type (PTY) information, and an array of, for example, eight RDS program service name strings. An RDS PS table, however, is not limited to this exemplary configuration. In the RDS PS data transfer mode, transceiver core 202 may receive, from host processor 204, RDS data that includes, for example, an RDS PI, RDS PTY information and one or more RDS program service name strings. This RDS PS table can be seen to relate to the United States radio broadcasters' usage of program service as a text-messaging feature.
As can be seen in FIG. 35, host processor 204 can send a PS command to transceiver core 202. To stop the continuous RDS group type 0A transmission, host processor 204 can re-issue the RDS PS XFR Mode with the PS_Flag field set to all zeros.
Transmission of RDS radio text (RT) data by host system 200 will now be described. In this regard, FIG. 36 is a sequence chart illustrating an example of transmitting RDS data with radio text (RT) information. The transmit (TX) RDS RT capability can provide a means for host processor 204 to send a string up to, for example, 64 characters to transceiver core 202 to be transmitted over-the-air via, for example, RDS group type 2A packets. This can be seen as an inverse to the RDS radio text described above with reference to FIGS. 21 to 23. For example, FIG. 37 is a conceptual block diagram illustrating an exemplary interface format of RDS radio text for group type 2A with host processor 204.
Referring to FIG. 36, using RDS RT data pipe 2706 of FIG. 27, host processor 204 can simply send to transceiver core 202 a text string (e.g., song title) without converting it into, for example, an RDS group type 2A packet. In this regard, transceiver core 202 can be responsible for creating and continuously transmitting the RDS group type 2A packets. For the RDS radio text (RT) data transfer mode, transceiver core 202 may include an RDS RT table that may contain an RDS program identification (PI), RDS program type (PTY) information, and an array of up to 64 characters. An RDS RT table, however, is not limited to this exemplary configuration. In the RDS RT data transfer mode, transceiver core 202 may receive, from host processor 204, RDS data that includes, for example, an RDS PI, RDS PTY information and a text string. In one aspect of the disclosure, the text string includes 64 characters, and text strings can be appended if they fit within 64 characters.
FIG. 36 illustrates an example of host processor 204 sending an RT command to transceiver core 202. As can be seen in this figure, to stop the continuous RDS group type 2A transmission, host processor 204 can re-issue the RDS RT XFR Mode with the control field set to “stop.”
Referring back to FIGS. 2, 3 and 9, in accordance with one aspect of the disclosure, the following host processor controllable RDS features are provided in transceiver core 202: (i) using RDS data filter 908, host processor 204 can enable transceiver core 202 to discard uncorrectable blocks and RDS groups that consist of Block-E types, which may be used in paging systems in the United states; (ii) using RDS PI match filter 910, host processor 204 can enable transceiver core 202 to assert an interrupt whenever the program ID in block 1 and/or the bits in block 2 match a given pattern; (iii) using Block-B-filter 912, host processor 204 can enable transceiver core 202 to assert an interrupt whenever block 2 of an RDS data group matches Block-B filter parameters defined by host processor 204; (iv) using RDS group filter 914, host processor 204 can enable transceiver core 202 to only pass the specified group types; and (v) using RDS change filter 916, host processor 204 can enable transceiver core 202 to pass the specified group types only if there are changes in the group data.
The host processor controllable RDS features further include: (vi) using RDS group buffers 924, host processor 204 can configure transceiver core 202 to buffer up to 21 groups before notifying host processor 204 that there is new RDS data to be processed; (vii) using RDS group type 0 data processor 922, host processor 204 can enable transceiver core 202 to process RDS group type 0 (basic tuning and switching information) packets, where transceiver core 202 can extract out the program identification (PI) code, program type (PTY) and provide a table of program service (PS) strings, where transceiver core 202 may only send information when there are changes in the PS table (e.g., when a song changes), and where host processor 204 can also enable transceiver core 202 to extract the alternative frequency (AF) list information from RDS group type 0; and (viii) using RDS group type 2 data processor 920, host processor 204 can enable transceiver core 202 to process RDS group type 2 (radio text) packets, where transceiver core 202 can extract out the radio text (RT) and provide up to a 64 character string, along with the PI and PTY, to host processor 204 only when the RT string changes.
In addition, host processor controllable RDS features can be associated with the transmission of RDS data. In this regard, host processor 204 can interface with transceiver core 202 using one or more of several interfaces. In particular, transceiver core 202 has a separate interface for at least the following RDS data transmissions:

    
    
        (i) RDS program service (PS) data interface, which can be implemented using, for example, an RDS PS table. This table can contain RDS PS data including, for example, RDS program identification (PI), RDS program type (PTY) information and up to eight 8-byte PS strings. Transceiver core 202 can convert this RDS PS data into, for example, RDS group type 0A packet(s), which can be continuously transmitted by transceiver core 202 until new RDS PS data is received from host processor 204, or transceiver core 202 is commanded to stop by host processor 204. The format for this interface can be seen to relate to PS table 1400 of FIG. 14.
        (ii) RDS radio text (RT) data interface, which can be implemented using, for example, an RDS RT table. This table can contain RDS RT data, including, for example, RDS PI, RDS PTY information and up to a 64-byte string. Transceiver core 202 can convert the RDS RT data into, for example, RDS group type 2A packet(s), which can be continuously transmitted by transceiver core 202 until new RDS RT data is received from host processor 204, or transceiver core 202 is commanded to stop by host processor 204. The format for this interface can be seen to relate to the RDS radio text described with reference to FIG. 37.
        (iii) Raw RDS group data interface, which can be implemented using, for example, a raw RDS buffer holding up to, for example, 62 groups of raw RDS group data received from host processor 204. Transceiver core 202 can transmit all of the raw RDS group data in the raw RDS buffer continuously or as a “single-shot.” These groups of raw RDS group data received from host processor 204 can be transmitted as-is, with transceiver core 202 adding checkword information.
    
    


According to one aspect of the disclosure, a data interface may correspond with any of the RDS PS data interface described above (which relates to PS table 1400 of FIG. 14), the RDS RT data interface described above (e.g., the interface format depicted in FIG. 37) or the raw RDS group data interface described above. In another aspect, a data interface may correspond with any of data pipes 2702, 2704 or 2706 of FIG. 27.
According to one aspect of the disclosure, transceiver core 202 has numerous filtering and data processing capabilities that can help reduce the amount of RDS processing on host processor 204. For example, buffering of the RDS group data in transceiver core 202 can reduce the number of interrupts to host processor 204. Thus, host processor 204 does not have to wake-up as often to acknowledge RDS interrupts. Filtering enables host processor 204 to only receive the desired data types and only if it has changed. This typically reduces the amount of interrupts and saves code on the host processor 204 that would have been needed to filter out the “raw” RDS data. Processing of the main RDS group types (0 and 2) in transceiver core 202 is seen to offload host processor 204. Host processor 204 would only have to display the pre-processed PS and RT strings to the user. The PS table and RT string resides in the transceiver core's memory so host processor 204 could disable all interrupts and retrieve the current strings when it wishes (e.g., coming out of screen saver mode).
In addition, converting RDS data into RDS group type data by transceiver core 202 (e.g., formatting RDS PS data into RDS group type data such as RDS group type 0A data and formatting RDS RT data into RDS group type data such as RDS group type 2A data) can save host processor 204 from having to perform additional processing. Host processor 204 may only need to provide transceiver core 202 with text strings for RDS data (e.g., MP3 song title and artist). The use of data pipes for passing RDS data from host processor 204 to transceiver core 202 provides flexibility for transmission of common RDS data (e.g., groups types 0 and 2), along with raw RDS group data. Further, interleaving by transceiver core 202 to meet the desired repetition rate (e.g., the rate defined in an RDS specification) can potentially save power, memory, and processing cycles of host processor 204.
FIG. 38 is a flowchart illustrating an exemplary operation of transmitting RDS data from host system 200. In step 3802, RDS data is received by a data processor from host processor 204. In step 3804, the RDS data is converted by the data processor into RDS group type data, or the RDS data is stored by the data processor. In this regard, storing is performed if the RDS data comprises a plurality of raw RDS group data. In step 3806, the RDS data is transmitted by the data processor to one or more devices outside host system 200.
According to one aspect of the disclosure, a data processor may include one or more of the components or all of the components shown in FIG. 9. In another aspect, a data processor may include a microprocessor 322 of FIG. 3, or any other one or more of the components or all of the components shown, for example, in FIG. 3. A data processor and a host processor may be implemented on the same integrated circuit, the same printed circuit board, or the same device or component. Alternatively, a data processor and a host processor may be implemented on separate integrated circuits, separate printed circuit boards, or separate devices or components. A data processor and a host processor may be distributed over different devices or components.
In one aspect, a data processor may be configured to filter the RDS data based on one or more parameters configurable by a host processor (e.g., controlled, enabled or disabled by a host processor) so that depending on the one or more parameters, the selected set of the RDS data is a subset of the RDS data. Such subset may include selected RDS groups. In another aspect, the selected set of the RDS data is a subset of the RDS data, none of the RDS data, or the entire RDS data.
A data processor may include one or more filters (e.g., blocks 908, 910, 912, 914, and 916 in FIG. 9) for filtering the RDS data. Each or some of the filters can be selectively configurable by a host processor (e.g., controlled, enabled or disabled by a host processor). For example, each or some of the filters can be configurable by a host processor independently of one or more of the other filters. A data processor may also include one or more RDS group buffers that are selectively configurable by a host processor (e.g., controlled, enabled or disabled by a host processor).
A data processor may include one or more group processing components (e.g., blocks 920 and 922 in FIG. 9) that are selectively configurable by a host processor (e.g., controlled, enabled or disabled by a host processor). For example, one or more group processing elements can be configurable by a host processor independently of one or more of the other group processing components.
In another aspect, a data processor is configured to reduce the number of interrupts to a host processor based on one or more parameters configurable by the host processor (e.g., controlled, enabled or disabled by a host processor) so that depending on the one or more parameters, the number of interrupts are reduced or not reduced.
Each of a data processor and a host processor may be implemented using software, hardware, or a combination of both. By way of example, each of a data processor and a host processor may be implemented with one or more processors. A processor may be a general-purpose microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable device that can perform calculations or other manipulations of information. Each of a data processor and a host processor may also include one or more machine-readable media for storing software. Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code).
Machine-readable media may include storage integrated into a processor, such as might be the case with an ASIC. Machine-readable media may also include storage external to a processor, such as a random access memory (RAM), a flash memory, a read only memory (ROM), a programmable read-only memory (PROM), an erasable PROM (EPROM), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device. In addition, machine-readable media may include a transmission line or a carrier wave that encodes a data signal. Those skilled in the art will recognize how best to implement the described functionality for a data processor and a host processor. According to one aspect of the disclosure, a machine-readable medium is a computer-readable medium encoded or stored with instructions and is a computing element, which defines structural and functional interrelationships between the instructions and the rest of the system, which permit the instructions' functionality to be realized. Instructions may be executable, for example, by a host system or by a processor of a host system. Instructions can be, for example, a computer program including code.
FIG. 39 is a conceptual block diagram illustrating an example of the functionality of a host system for transmitting RDS data. Host system 200 includes a host processor 204 and a data processor 3902. Data processor 3902 includes a module 3904 for receiving RDS data from host processor 204. Data processor 3902 further includes a module 3906 for converting the RDS data into RDS group type data, or for storing the RDS data. In this regard, module 3906 is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data. In addition, data processor 3902 includes a module 3908 for transmitting the RDS data to one or more devices outside the host system.
Referring to FIGS. 3 and 39, according to one aspect of the disclosure, module 3904 for receiving RDS data may include control registers 326 and/or control interface 328. Module 3906 for converting the RDS data may include microprocessor 322 and/or RDS encoder 324. It may also include data RAM 314. Alternatively, module 3906 for storing the RDS data may include microprocessor 322 and/or data RAM 314. Module 3908 for transmitting may include antenna 208 and/or FM transmitter 306. It may also include FM modulator 316. The configuration described above is simply one example, and the modules may be implemented in many different ways.
Those of skill in the art would appreciate that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or combinations of both. For example, each of group processing component 918 and filter module 906 may be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application. Various components and blocks may be arranged differently (e.g., arranged in a different order, or partitioned in a different way) all without departing from the scope of the subject technology. For example, the specific orders of the filters in filter module 906 of FIG. 9 may be rearranged, and some or all of the filters may be partitioned in a different way.
It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. Pronouns in the masculine (e.g., his) include the feminine and neuter gender (e.g., her and its) and vice versa. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.”

## Claims

1. A host system for transmitting radio data system (RDS) data, comprising:
a host processor; and
a data processor configured to receive RDS data from the host processor, the data processor configured to convert the RDS data into RDS group type data or to store the RDS data, the data processor configured to transmit the RDS data to one or more devices outside the host system,
wherein the data processor is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data, each of the raw RDS group data comprising a plurality of blocks, each block having a block status byte, the block status byte including a block identification (ID) code and an error code, wherein the error code indicates the number of errors corrected in the block.

2. The host system of claim 1, wherein the data processor is configured to include some or all of a plurality of RDS data transfer modes, and wherein the plurality of RDS data transfer modes comprises an RDS program service (PS) data transfer mode, an RDS radio text (RT) data transfer mode, and a raw RDS group data transfer mode.

3. The host system of claim 1, wherein for an RDS program service (PS) data transfer mode, the RDS data comprises an RDS program identification (PI), RDS program type (PTY) information, and one or more RDS program service name strings.

4. The host system of claim 1, wherein for an RDS program service (PS) data transfer mode, the data processor is configured to convert the RDS data into RDS group type 0A data.

5. The host system of claim 1, wherein for an RDS radio text (RT) data transfer mode, the RDS data comprises an RDS program identification (PI), RDS program type (PTY) information, and a text sting.

6. The host system of claim 1, wherein for an RDS radio text (RT) data transfer mode, the data processor is configured to convert the RDS data into RDS group type 2A data.

7. The host system of claim 1, wherein for a raw RDS group data transfer mode, the data processor is configured to store the RDS data in a data buffer, add checkword information to the RDS data, and transmit the RDS data without further converting the RDS data into RDS group type data.

8. The host system of claim 1, wherein the data processor is configured to transmit the RDS data continuously until new RDS data is received.

9. The host system of claim 1, wherein the data processor is configured to transmit the RDS data continuously until a stop command is received.

10. The host system of claim 1, wherein the data processor is configured to transmit the RDS data once.

11. The host system of claim 2, wherein the host processor is configured to selectively enable any one or more of the plurality of RDS data transfer modes.

12. The host system of claim 2, wherein if two or more of the plurality of RDS data transfer modes are enabled, then the data processor is configured to receive a plurality of RDS data for the two or more of the plurality of RDS data transfer modes, and the data processor is configured to interleave the plurality of RDS data for transmission.

13. The host system of claim 1, further comprising: an audio component, a display module, a keypad module, and a data memory.

14. A data processor for a host system for transmitting radio data system (RDS) data, comprising:
a receive module configured to receive RDS data from a host processor of the host system;
a processing module configured to convert the RDS data into RDS group type data or to store the RDS data; and
a transmit module configured to transmit the RDS data to one or more devices outside the host system,
wherein the processing module is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data, each of the raw RDS group data comprising a plurality of blocks, each block having a block status byte, the block status byte including a block identification (ID) code and an error code, wherein the error code indicates the number of errors corrected in the block.

15. The data processor of claim 14, wherein the data processor is configured to include some or all of a plurality of RDS data transfer modes, and wherein the plurality of RDS data transfer modes comprises an RDS program service (PS) data transfer mode, an RDS radio text (RT) data transfer mode, and a raw RDS group data transfer mode.

16. The data processor of claim 14, wherein for an RDS program service (PS) data transfer mode, the RDS data comprises an RDS program identification (PI), RDS program type (PTY) information, and one or more RDS program service name strings.

17. The host system of claim 14, wherein for an RDS radio text (RT) data transfer mode, the RDS data comprises an RDS program identification (PI), RDS program type (PTY) information, and a text string.

18. A host system for transmitting radio data system (RDS) data, comprising:
a host processor; and
a data processor comprising:
means for receiving RDS data from the host processor;
means for converting the RDS data into RDS group type data or means for storing the RDS data; and
means for transmitting the RDS data to one or more devices outside the host system,

wherein the means for storing is configured to store the RDS data if the RDS data comprises a plurality of raw RDS group data, each of the raw RDS group data comprising a plurality of blocks, each block having a block status byte, the block status byte including a block identification (ID) code and an error code, wherein the error code indicates the number of errors corrected in the block.

19. The host system of claim 18, wherein the data processor is configured to include some or all of a plurality of RDS data transfer modes, and wherein the plurality of RDS data transfer modes comprises an RDS program service (PS) data transfer mode, an RDS radio text (RT) data transfer mode, and a raw RDS group data transfer mode.

20. The host system of claim 18, wherein for an RDS program service (PS) data transfer mode, the RDS data comprises an RDS program identification (PI), RDS program type (PTY) information, and one or more RDS program service name strings.

21. The host system of claim 18, wherein for an RDS radio text (RT) data transfer mode, the RDS data comprises an RDS program identification (PI), RDS program type (PTY) information, and a text sting.

22. A method of transmitting radio data system (RDS) data from a host system comprising a host processor and a data processor, the method comprising:
receiving, by the data processor, RDS data from the host processor;
converting, by the data processor, the RDS data into RDS group type data or storing, by the data processor, the RDS data; and
transmitting, by the data processor, the RDS data to one or more devices outside the host system,
wherein the step of storing is performed if the RDS data comprises a plurality of raw RDS group data, each of the raw RDS group data comprising a plurality of blocks, each block having a block status byte, the block status byte including a block identification (ID) code and an error code, wherein the error code indicates the number of errors corrected in the block.

23. The method of claim 22, wherein the data processor is configured to include some or all of a plurality of RDS data transfer modes, and wherein the plurality of RDS data transfer modes comprises an RDS program service (PS) data transfer mode, an RDS radio text (RT) data transfer mode, and a raw RDS group data transfer mode.

24. The method of claim 22, wherein for an RDS program service (PS) data transfer mode, the RDS data comprises an RDS program identification (PI), RDS program type (PTY) information, and one or more RDS program service name strings.

25. A non-transitory processor-readable storage medium having stored thereon processor-executable instructions configured to cause a processor to perform operations for transmitting radio data system (RDS) data from a host system comprising a host processor and a data processor, the operations comprising:
receiving, by the data processor, RDS data from the host processor;
converting, by the data processor, the RDS data into RDS group type data or storing, by the data processor, the RDS data; and
transmitting, by the data processor, the RDS data to one or more devices outside the host system,
wherein the step of storing is performed if the RDS data comprises a plurality of raw RDS group data, each of the raw RDS group data comprising a plurality of blocks, each block having a block status byte, the block status byte including a block identification (ID) code and an error code, wherein the error code indicates the number of errors corrected in the block.

26. The host system of claim 1, wherein the error code of the block status byte indicates whether there are uncorrectable errors in the block.

27. The data processor of claim 14, wherein the error code of the block status byte indicates whether there are uncorrectable errors in the block.

28. The host system of claim 18, wherein the error code of the block status byte indicates whether there are uncorrectable errors in the block.

29. The method of claim 22, wherein the error code of the block status byte indicates whether there are uncorrectable errors in the block.

30. The non-transitory processor-readable storage medium of claim 25, wherein the error code of the block status byte indicates whether there are uncorrectable errors in the block.