Patent Grant
RE47183
1. Field of the Invention
The present invention relates to a digital broadcasting system, and more particularly, to a digital broadcasting system and a data processing method.
2. Discussion of the Related Art
The Vestigial Sideband (VSB) transmission mode, which is adopted as the standard for digital broadcasting in North America and the Republic of Korea, is a system using a single carrier method. Therefore, the receiving performance of the digital broadcast receiving system may be deteriorated in a poor channel environment. Particularly, since resistance to changes in channels and noise is more highly required when using portable and/or mobile broadcast receivers, the receiving performance may be even more deteriorated when transmitting mobile service data by the VSB transmission mode.
An object of the present invention is to provide a digital broadcasting system and a data processing method that are highly resistant to channel changes and noise. An object of the present invention is to provide a digital broadcasting system and a method of processing data in a digital broadcasting system that can enhance the receiving performance of a receiving system (or receiver) by having a transmitting system (or transmitter) perform additional encoding on mobile service data. Another object of the present invention is to provide a digital broadcasting system and a method of processing data in the digital broadcasting system that can also enhance the receiving performance of a digital broadcast receiving system by inserting known data already known in accordance with a pre-agreement between the receiving system and the transmitting system in a predetermined region within a data region.
Another object of the present invention is to provide a digital broadcasting system and a data processing method which can quickly access services of mobile service data when the mobile service data is multiplexed with main service data and the multiplexed resultant data is transmitted.
The present invention provides a data processing method. The data processing method includes receiving a broadcast signal in which main service data and mobile service data are multiplexed, acquiring transmission-parameter-channel signaling information including transmission parameter information of the mobile service data, and fast-information-channel signaling information, acquiring binding information describing a relationship between at least one ensemble transferring the mobile service data and a first virtual channel contained in any of the at least one ensemble by decoding fast-information-channel signaling information, acquiring ensemble identification information transferring the first virtual channel using the binding information, and receiving at least one mobile service data group transferring an ensemble according to the ensemble identification information, parsing service table information contained in the ensemble and decoding content data contained in the first virtual channel using the parsed service table information, and displaying the decoded content data.
Also, the present invention provides the processing method performing a first error correction encoding process on fast-information-channel signaling information including binding information, in which the binding information describes a relationship between a first virtual channel in any of at least one ensemble transferring mobile service data and the ensemble transferring the first virtual channel, performing a second error correction encoding process on mobile service data to be transferred to the ensemble and service table information describing channel information of the ensemble and multiplexing the encoded fast-information-channel signaling information and the mobile service data, multiplexing the multiplexed mobile service data and main service data, and modulating the resultant multiplexed data.
The present invention provides a digital broadcasting system. The digital broadcasting system includes a baseband processor configured to acquire transmission-parameter-channel signaling information including transmission parameter information of mobile service data and fast-information-channel signaling information from a broadcast signal, and receive a mobile service data group which transmits an ensemble according to fast-information-channel signaling information including binding information describing a relationship between a first virtual channel of the mobile service data and the ensemble transferring the first virtual channel, a management processor configured to acquire the binding information by decoding the fast-information-channel signaling information, and parsing service table information of the ensemble received according to the binding information and a presentation processor configured to decode mobile service data of the first virtual channel according to the service table information, and displaying content data contained in the decoded mobile service data.
The fast-information-channel signaling information may be divided into a plurality of segments according to the mobile service data group. The fast-information-channel signaling information may include channel type information indicating a type of a service transferred to the virtual channel. The fast-information-channel signaling information may include a major-channel number and a minor-channel number of the virtual channel, which is contained in each ensemble according to the ensemble identification information. The fast-information-channel signaling information includes transport stream identification information of a broadcast signal.
The transmission-parameter-channel signaling information may include version information of the fast-information-channel signaling information.
The baseband processor may receive a time-discontinuous mobile service data group, and receive the ensemble including the first virtual channel by using the fast-information-channel signaling information.
The presentation processor may include an application manager providing data broadcasting using the data broadcasting content, and a display module outputting the data broadcasting provided by the application manager.
The data group is contained in data groups in the broadcast signal, where the data groups are time-discontinuously received.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. In the drawings;
Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. At this time, it is to be understood that the following detailed description of the present invention illustrated in the drawings and described with reference to the drawings are exemplary and explanatory and technical spirits of the present invention and main features and operation of the present invention will not be limited by the following detailed description.
Definition of Terms Used in the Present Invention
Although general terms, which are widely used considering functions in the present invention, have been selected in the present invention, they may be changed depending on intention of those skilled in the art, practices, or new technology. Also, in specific case, the applicant may optionally select the terms. In this case, the meaning of the terms will be described in detail in the description part of the invention. Therefore, it is to be understood that the terms should be defined based upon their meaning not their simple title and the whole description of the present invention.
Among the terms used in the description of the present invention, main service data correspond to data that can be received by a fixed receiving system and may include audio/video (A/V) data. More specifically, the main service data may include A/V data of high definition (HD) or standard definition (SD) levels and may also include diverse data types required for data broadcasting. Also, the known data correspond to data pre-known in accordance with a pre-arranged agreement between the receiving system and the transmitting system.
Additionally, among the terms used in the present invention, “MH” corresponds to the initials of “mobile” and “handheld” and represents the opposite concept of a fixed-type system. Furthermore, the MH service data may include at least one of mobile service data and handheld service data, and will also be referred to as “mobile service data” for simplicity. Herein, the mobile service data not only correspond to MH service data but may also include any type of service data with mobile or portable characteristics. Therefore, the mobile service data according to the present invention are not limited only to the MH service data.
The above-described mobile service data may correspond to data having information, such as program execution files, stock information, and so on, and may also correspond to A/V data. Most particularly, the mobile service data may correspond to A/V data having lower resolution and lower data rate as compared to the main service data. For example, if an A/V codec that is used for a conventional main service corresponds to a MPEG-2 codec, a MPEG-4 advanced video coding (AVC) or scalable video coding (SVC) having better image compression efficiency may be used as the A/V codec for the mobile service. Furthermore, any type of data may be transmitted as the mobile service data. For example, transport protocol expert group (TPEG) data for broadcasting real-time transportation information may be transmitted as the main service data.
Also, a data service using the mobile service data may include weather forecast services, traffic information services, stock information services, viewer participation quiz programs, real-time polls and surveys, interactive education broadcast programs, gaming services, services providing information on synopsis, character, background music, and filming sites of soap operas or series, services providing information on past match scores and player profiles and achievements, and services providing information on product information and programs classified by service, medium, time, and theme enabling purchase orders to be processed. Herein, the present invention is not limited only to the services mentioned above.
In the present invention, the transmitting system provides backward compatibility in the main service data so as to be received by the conventional receiving system. Herein, the main service data and the mobile service data are multiplexed to the same physical channel and then transmitted.
Furthermore, the digital broadcast transmitting system according to the present invention performs additional encoding on the mobile service data and inserts the data already known by the receiving system and transmitting system (e.g., known data), thereby transmitting the processed data.
Therefore, when using the transmitting system according to the present invention, the receiving system may receive the mobile service data during a mobile state and may also receive the mobile service data with stability despite various distortion and noise occurring within the channel.
Receiving System
The baseband processor 100 includes an operation controller 110, a tuner 120, a demodulator 130, an equalizer 140, a known sequence detector (or known data detector) 150, a block decoder (or mobile handheld block decoder) 160, a primary Reed-Solomon (RS) frame decoder 170, a secondary RS frame decoder 180, and a signaling decoder 190. The operation controller 110 controls the operation of each block included in the baseband processor 100.
By tuning the receiving system to a specific physical channel frequency, the tuner 120 enables the receiving system to receive main service data, which correspond to broadcast signals for fixed-type broadcast receiving systems, and mobile service data, which correspond to broadcast signals for mobile broadcast receiving systems. At this point, the tuned frequency of the specific physical channel is downconverted to an intermediate frequency (IF) signal, thereby being outputted to the demodulator 130 and the known sequence detector 140. The passband digital IF signal being outputted from the tuner 120 may only include main service data, or only include mobile service data, or include both main service data and mobile service data.
The demodulator 130 performs self-gain control, carrier wave recovery, and timing recovery processes on the passband digital IF signal inputted from the tuner 120, thereby modifying the IF signal to a baseband signal. Then, the demodulator 130 outputs the baseband signal to the equalizer 140 and the known sequence detector 150. The demodulator 130 uses the known data symbol sequence inputted from the known sequence detector 150 during the timing and/or carrier wave recovery, thereby enhancing the demodulating performance.
The equalizer 140 compensates channel-associated distortion included in the signal demodulated by the demodulator 130. Then, the equalizer 140 outputs the distortion-compensated signal to the block decoder 160. By using a known data symbol sequence inputted from the known sequence detector 150, the equalizer 140 may enhance the equalizing performance. Furthermore, the equalizer 140 may receive feedback on the decoding result from the block decoder 160, thereby enhancing the equalizing performance.
The known sequence detector 150 detects known data place (or position) inserted by the transmitting system from the input/output data (i.e., data prior to being demodulated or data being processed with partial demodulation). Then, the known sequence detector 150 outputs the detected known data position information and known data sequence generated from the detected position information to the demodulator 130 and the equalizer 140. Additionally, in order to allow the block decoder 160 to identify the mobile service data that have been processed with additional encoding by the transmitting system and the main service data that have not been processed with any additional encoding, the known sequence detector 150 outputs such corresponding information to the block decoder 160.
If the data channel-equalized by the equalizer 140 and inputted to the block decoder 160 correspond to data processed with both block-encoding and trellis-encoding by the transmitting system (i.e., data within the RS frame, signaling data), the block decoder 160 may perform trellis-decoding and block-decoding as inverse processes of the transmitting system. On the other hand, if the data channel-equalized by the equalizer 140 and inputted to the block decoder 160 correspond to data processed only with trellis-encoding and not block-encoding by the transmitting system (i.e., main service data), the block decoder 160 may perform only trellis-decoding.
The signaling decoder 190 decoded signaling data that have been channel-equalized and inputted from the equalizer 140. It is assumed that the signaling data inputted to the signaling decoder 190 correspond to data processed with both block-encoding and trellis-encoding by the transmitting system. Examples of such signaling data may include transmission parameter channel (TPC) data and fast information channel (FIC) data. Each type of data will be described in more detail in a later process. The FIC data decoded by the signaling decoder 190 are outputted to the FIC handler 215. And, the TPC data decoded by the signaling decoder 190 are outputted to the TPC handler 214.
Meanwhile, according to the present invention, the transmitting system uses RS frames by encoding units. Herein, the RS frame may be divided into a primary RS frame and a secondary RS frame. However, according to the embodiment of the present invention, the primary RS frame and the secondary RS frame will be divided based upon the level of importance of the corresponding data.
The primary RS frame decoder 170 receives the data outputted from the block decoder 160. At this point, according to the embodiment of the present invention, the primary RS frame decoder 170 receives only the mobile service data that have been Reed-Solomon (RS)-encoded and/or cyclic redundancy check (CRC)-encoded from the block decoder 160.
Herein, the primary RS frame decoder 170 receives only the mobile service data and not the main service data. The primary RS frame decoder 170 performs inverse processes of an RS frame encoder (not shown) included in the digital broadcast transmitting system, thereby correcting errors existing within the primary RS frame. More specifically, the primary RS frame decoder 170 forms a primary RS frame by grouping a plurality of data groups and, then, correct errors in primary RS frame units. In other words, the primary RS frame decoder 170 decodes primary RS frames, which are being transmitted for actual broadcast services.
Additionally, the secondary RS frame decoder 180 receives the data outputted from the block decoder 160. At this point, according to the embodiment of the present invention, the secondary RS frame decoder 180 receives only the mobile service data that have been RS-encoded and/or CRC-encoded from the block decoder 160. Herein, the secondary RS frame decoder 180 receives only the mobile service data and not the main service data. The secondary RS frame decoder 180 performs inverse processes of an RS frame encoder (not shown) included in the digital broadcast transmitting system, thereby correcting errors existing within the secondary RS frame. More specifically, the secondary RS frame decoder 180 forms a secondary RS frame by grouping a plurality of data groups and, then, correct errors in secondary RS frame units. In other words, the secondary RS frame decoder 180 decodes secondary RS frames, which are being transmitted for mobile audio service data, mobile video service data, guide data, and so on.
Meanwhile, the management processor 200 according to an embodiment of the present invention includes an MH physical adaptation processor 210, an IP network stack 220, a streaming handler 230, a system information (SI) handler 240, a file handler 250, a multi-purpose internet main extensions (MIME) type handler 260, and an electronic service guide (ESG) handler 270, and an ESG decoder 280, and a storage unit 290.
The MH physical adaptation processor 210 includes a primary RS frame handler 211, a secondary RS frame handler 212, an MH transport packet (TP) handler 213, a TPC handler 214, an FIC handler 215, and a physical adaptation control signal handler 216.
The TPC handler 214 receives and processes baseband information required by modules corresponding to the MH physical adaptation processor 210. The baseband information is inputted in the form of TPC data. Herein, the TPC handler 214 uses this information to process the FIC data, which have been sent from the baseband processor 100.
The TPC data are transmitted from the transmitting system to the receiving system via a predetermined region of a data group. The TPC data may include at least one of an MH ensemble ID, an MH sub-frame number, a total number of MH groups (TNoG), an RS frame continuity counter, a column size of RS frame (N), and an FIC version number.
Herein, the MH ensemble ID indicates an identification number of each MH ensemble carried in the corresponding channel. The MH sub-frame number signifies a number identifying the MH sub-frame number in an MH frame, wherein each MH group associated with the corresponding MH ensemble is transmitted. The TNoG represents the total number of MH groups including all of the MH groups belonging to all MH parades included in an MH sub-frame.
The RS frame continuity counter indicates a number that serves as a continuity counter of the RS frames carrying the corresponding MH ensemble. Herein, the value of the RS frame continuity counter shall be incremented by 1 modulo 16 for each successive RS frame.
N represents the column size of an RS frame belonging to the corresponding MH ensemble. Herein, the value of N determines the size of each MH TP.
Finally, the FIC version number signifies the version number of an FIC body carried on the corresponding physical channel.
As described above, diverse TPC data are inputted to the TPC handler 214 via the signaling decoder 190 shown in
The FIC handler 215 processes the FIC data by associating the FIC data received from the baseband processor 100 with the TPC data.
The physical adaptation control signal handler 216 collects FIC data received through the FIC handler 215 and SI data received through RS frames. Then, the physical adaptation control signal handler 216 uses the collected FIC data and SI data to configure and process IP datagrams and access information of mobile broadcast services. Thereafter, the physical adaptation control signal handler 216 stores the processed IP datagrams and access information to the storage unit 290.
The primary RS frame handler 211 identifies primary RS frames received from the primary RS frame decoder 170 of the baseband processor 100 for each row unit, so as to configure an MH TP. Thereafter, the primary RS frame handler 211 outputs the configured MH TP to the MH TP handler 213.
The secondary RS frame handler 212 identifies secondary RS frames received from the secondary RS frame decoder 180 of the baseband processor 100 for each row unit, so as to configure an MH TP. Thereafter, the secondary RS frame handler 212 outputs the configured MH TP to the MH TP handler 213.
The MH transport packet (TP) handler 213 extracts a header from each MH TP received from the primary RS frame handler 211 and the secondary RS frame handler 212, thereby determining the data included in the corresponding MH TP. Then, when the determined data correspond to SI data (i.e., SI data that are not encapsulated to IP datagrams), the corresponding data are outputted to the physical adaptation control signal handler 216. Alternatively, when the determined data correspond to an IP datagram, the corresponding data are outputted to the IP network stack 220.
The IP network stack 220 processes broadcast data that are being transmitted in the form of IP datagrams. More specifically, the IP network stack 220 processes data that are inputted via user datagram protocol (UDP), real-time transport protocol (RTP), real-time transport control protocol (RTCP), asynchronous layered coding/layered coding transport (ALC/LCT), file delivery over unidirectional transport (FLUTE), and so on. Herein, when the processed data correspond to streaming data, the corresponding data are outputted to the streaming handler 230. And, when the processed data correspond to data in a file format, the corresponding data are outputted to the file handler 250. Finally, when the processed data correspond to SI-associated data, the corresponding data are outputted to the SI handler 240.
The SI handler 240 receives and processes SI data having the form of IP datagrams, which are inputted to the IP network stack 220. When the inputted data associated with SI correspond to MIME-type data, the inputted data are outputted to the MIME-type handler 260. The MIME-type handler 260 receives the MIME-type SI data outputted from the SI handler 240 and processes the received MIME-type SI data.
The file handler 250 receives data from the IP network stack 220 in an object format in accordance with the ALC/LCT and FLUTE structures. The file handler 250 groups the received data to create a file format. Herein, when the corresponding file includes ESG, the file is outputted to the ESG handler 270. On the other hand, when the corresponding file includes data for other file-based services, the file is outputted to the presentation controller 330 of the presentation processor 300.
The ESG handler 270 processes the ESG data received from the file handler 250 and stores the processed ESG data to the storage unit 290. Alternatively, the ESG handler 270 may output the processed ESG data to the ESG decoder 280, thereby allowing the ESG data to be used by the ESG decoder 280.
The storage unit 290 stores the system information (SI) received from the physical adaptation control signal handler 210 and the ESG handler 270 therein. Thereafter, the storage unit 290 transmits the stored SI data to each block.
The ESG decoder 280 either recovers the ESG data and SI data stored in the storage unit 290 or recovers the ESG data transmitted from the ESG handler 270. Then, the ESG decoder 280 outputs the recovered data to the presentation controller 330 in a format that can be outputted to the user.
The streaming handler 230 receives data from the IP network stack 220, wherein the format of the received data are in accordance with RTP and/or RTCP structures. The streaming handler 230 extracts audio/video streams from the received data, which are then outputted to the audio/video (A/V) decoder 310 of the presentation processor 300. The audio/video decoder 310 then decodes each of the audio stream and video stream received from the streaming handler 230.
The display module 320 of the presentation processor 300 receives audio and video signals respectively decoded by the A/V decoder 310. Then, the display module 320 provides the received audio and video signals to the user through a speaker and/or a screen.
The presentation controller 330 corresponds to a controller managing modules that output data received by the receiving system to the user.
The channel service manager 340 manages an interface with the user, which enables the user to use channel-based broadcast services, such as channel map management, channel service connection, and so on.
The application manager 350 manages an interface with a user using ESG display or other application services that do not correspond to channel-based services.
Meanwhile, the streaming handler 230 may include a buffer temporarily storing audio/video data. The digital broadcasting reception system periodically sets reference time information to a system time clock, and then the stored audio/video data can be transferred to A/V decoder 310 at a constant bitrate. Accordingly, the audio/video data can be processed at a bitrate and audio/video service can be provided.
Data Format Structure
Meanwhile, the data structure used in the mobile broadcasting technology according to the embodiment of the present invention may include a data group structure and an RS frame structure, which will now be described in detail.
More specifically, when it is assumed that one data group is divided into regions A, B, C, and D, each MH block may be included in any one of region A to region D depending upon the characteristic of each MH block within the data group.
Herein, the data group is divided into a plurality of regions to be used for different purposes. More specifically, a region of the main service data having no interference or a very low interference level may be considered to have a more resistant (or stronger) receiving performance as compared to regions having higher interference levels. Additionally, when using a system inserting and transmitting known data in the data group, wherein the known data are known based upon an agreement between the transmitting system and the receiving system, and when consecutively long known data are to be periodically inserted in the mobile service data, the known data having a predetermined length may be periodically inserted in the region having no interference from the main service data (i.e., a region wherein the main service data are not mixed). However, due to interference from the main service data, it is difficult to periodically insert known data and also to insert consecutively long known data to a region having interference from the main service data.
Referring to
In the example of the data group shown in
Referring to
Finally, in the example shown in
Additionally, the data group includes a signaling information area wherein signaling information is assigned (or allocated).
In the present invention, the signaling information area may start from the 1st segment of the 4th MH block (B4) to a portion of the 2nd segment.
According to an embodiment of the present invention, the signaling information area for inserting signaling information may start from the 1st segment of the 4th MH block (B4) to a portion of the 2nd segment. More specifically, 276(=207+69) bytes of the 4th MH block (B4) in each data group are assigned as the signaling information area. In other words, the signaling information area consists of 207 bytes of the 1st segment and the first 69 bytes of the 2nd segment of the 4th MH block (B4). The 1st segment of the 4th MH block (B4) corresponds to the 17th or 173rd segment of a VSB field.
Herein, the signaling information may be identified by two different types of signaling channels: a transmission parameter channel (TPC) and a fast information channel (FIC).
Herein, the TPC data may include at least one of an MH ensemble ID, an MH sub-frame number, a total number of MH groups (TNoG), an RS frame continuity counter, a column size of RS frame (N), and an FIC version number. However, the TPC data (or information) presented herein are merely exemplary. And, since the adding or deleting of signaling information included in the TPC data may be easily adjusted and modified by one skilled in the art, the present invention will, therefore, not be limited to the examples set forth herein. Furthermore, the FIC is provided to enable a fast service acquisition of data receivers, and the FIC includes cross layer information between the physical layer and the upper layer(s). For example, when the data group includes 6 known data sequences, as shown in
The RS frame shown in
The RS frame according to the embodiment of the present invention consists of at least one MH transport packet (TP). Herein, the MH TP includes an MH header and an MH payload.
The MH payload may include mobile service data as well as signaling data. More specifically, an MH payload may include only mobile service data, or may include only signaling data, or may include both mobile service data and signaling data.
According to the embodiment of the present invention, the MH header may identify (or distinguish) the data types included in the MH payload. More specifically, when the MH TP includes a first MH header, this indicates that the MH payload includes only the signaling data. Also, when the MH TP includes a second MH header, this indicates that the MH payload includes both the signaling data and the mobile service data. Finally, when MH TP includes a third MH header, this indicates that the MH payload includes only the mobile service data.
In the example shown in
The IP datagram in the MH-TP in the RS frame may include reference time information (for example, network time stamp (NTP)), the detailed description for the reference time information will be disclosed by being referred to
Data Transmission Structure
In the example shown in
Also, in a packet level, one slot is configured of 156 data packets (i.e., transport stream packets), and in a symbol level, one slot is configured of 156 data segments. Herein, the size of one slot corresponds to one half (½) of a VSB field. More specifically, since one 207-byte data packet has the same amount of data as a data segment, a data packet prior to being interleaved may also be used as a data segment. At this point, two VSB fields are grouped to form a VSB frame.
If the first 118 data packets within the slot correspond to a data group, the remaining 38 data packets become the main service data packets. In another example, when no data group exists in a slot, the corresponding slot is configured of 156 main service data packets.
Meanwhile, when the slots are assigned to a VSB frame, an off-set exists for each assigned position.
Referring to
According to the embodiment of the present invention, a plurality of consecutive data groups is assigned to be spaced as far apart from one another as possible within the MH frame. Thus, the system can be capable of responding promptly and effectively to any burst error that may occur within a sub-frame.
For example, when it is assumed that 3 data groups are assigned to a sub-frame, the data groups are assigned to a 1st slot (Slot #0), a 5th slot (Slot #4), and a 9th slot (Slot #8) in the sub-frame, respectively.
j=(4i+0)mod 16 [Equation 1]
0=0 if i<4,
0=2 else if i<8,
Herein,
0=1 else if i<12,
0=3 else.
Herein, j indicates the slot number within a sub-frame. The value of j may range from 0 to 15 (i.e., 0≤j≤15). Also, variable i indicates the data group number. The value of i may range from 0 to 15 (i.e., 0≤i≤15).
In the present invention, a collection of data groups included in a MH frame will be referred to as a “parade”. Based upon the RS frame mode, the parade transmits data of at least one specific RS frame.
The mobile service data within one RS frame may be assigned either to all of regions A/B/C/D within the corresponding data group, or to at least one of regions A/B/C/D. In the embodiment of the present invention, the mobile service data within one RS frame may be assigned either to all of regions A/B/C/D, or to at least one of regions NB and regions C/D. If the mobile service data are assigned to the latter case (i.e., one of regions NB and regions C/D), the RS frame being assigned to regions A/B and the RS frame being assigned to regions C/D within the corresponding data group are different from one another.
According to the embodiment of the present invention, the RS frame being assigned to regions A/B within the corresponding data group will be referred to as a “primary RS frame”, and the RS frame being assigned to regions C/D within the corresponding data group will be referred to as a “secondary RS frame”, for simplicity. Also, the primary RS frame and the secondary RS frame form (or configure) one parade. More specifically, when the mobile service data within one RS frame are assigned either to all of regions A/B/C/D within the corresponding data group, one parade transmits one RS frame. Conversely, when the mobile service data within one RS frame are assigned either to at least one of regions A/B and regions C/D, one parade may transmit up to 2 RS frames. More specifically, the RS frame mode indicates whether a parade transmits one RS frame, or whether the parade transmits two RS frames. Such RS frame mode is transmitted as the above-described TPC data. Table 1 below shows an example of the RS frame mode.
Table 1 illustrates an example of allocating 2 bits in order to indicate the RS frame mode. For example, referring to Table 1, when the RS frame mode value is equal to ‘00’, this indicates that one parade transmits one RS frame. And, when the RS frame mode value is equal to ‘01’, this indicates that one parade transmits two RS frames, i.e., the primary RS frame and the secondary RS frame.
More specifically, when the RS frame mode value is equal to ‘01’, data of the primary RS frame for regions NB are assigned and transmitted to regions NB of the corresponding data group. Similarly, data of the secondary RS frame for regions C/D are assigned and transmitted to regions C/D of the corresponding data group.
As described in the assignment of data groups, the parades are also assigned to be spaced as far apart from one another as possible within the sub-frame. Thus, the system can be capable of responding promptly and effectively to any burst error that may occur within a sub-frame. Furthermore, the method of assigning parades may be identically applied to all MH frames or differently applied to each MH frame.
According to the embodiment of the present invention, the parades may be assigned differently for each MH frame and identically for all sub-frames within an MH frame. More specifically, the MH frame structure may vary by MH frame units. Thus, an ensemble rate may be adjusted on a more frequent and flexible basis.
Referring to
For example, when it is assumed that one parade transmits one RS frame, and that a RS frame encoder (not shown) included in the transmitting system performs RS-encoding on the corresponding RS frame, thereby adding 24 bytes of parity data to the corresponding RS frame and transmitting the processed RS frame, the parity data occupy approximately 11.37% (=24/(187+24)×100) of the total code word length. Meanwhile, when one sub-frame includes 3 data groups, and when the data groups included in the parade are assigned, as shown in
Meanwhile, when data groups of a parade are assigned as shown in
Basically, the method of assigning data groups corresponding to multiple parades is very similar to the method of assigning data groups corresponding to a single parade. In other words, data groups included in other parades that are to be assigned to an MH frame are also respectively assigned according to a cycle period of 4 slots.
At this point, data groups of a different parade may be sequentially assigned to the respective slots in a circular method. Herein, the data groups are assigned to slots starting from the ones to which data groups of the previous parade have not yet been assigned.
For example, when it is assumed that data groups corresponding to a parade are assigned as shown in
When the 1st parade (Parade #0) includes 3 data groups for each sub-frame, the positions of each data groups within the sub-frames may be obtained by substituting values ‘0’ to ‘2’ for i in Equation 1. More specifically, the data groups of the 1st parade (Parade #0) are sequentially assigned to the 1st, 5th, and 9th slots (Slot #0, Slot #4, and Slot #8) within the sub-frame.
Also, when the 2nd parade includes 2 data groups for each sub-frame, the positions of each data groups within the sub-frames may be obtained by substituting values ‘3’ and ‘4’ for i in Equation 1. More specifically, the data groups of the 2nd parade (Parade #1) are sequentially assigned to the 2nd and 12th slots (Slot #3 and Slot #11) within the sub-frame.
Finally, when the 3rd parade includes 2 data groups for each sub-frame, the positions of each data groups within the sub-frames may be obtained by substituting values ‘5’ and ‘6’ for i in Equation 1. More specifically, the data groups of the 3rd parade (Parade #2) are sequentially assigned to the 7th and 11th slots (Slot #6 and Slot #10) within the sub-frame.
As described above, data groups of multiple parades may be assigned to a single MH frame, and, in each sub-frame, the data groups are serially allocated to a group space having 4 slots from left to right.
Therefore, a number of groups of one parade per sub-frame (NoG) may correspond to any one integer from ‘1’ to ‘8’. Herein, since one MH frame includes 5 sub-frames, the total number of data groups within a parade that can be allocated to an MH frame may correspond to any one multiple of ‘5’ ranging from ‘5’ to ‘40’.
As described above, an MH frame is divided into 5 sub-frames. Data groups corresponding to a plurality of parades co-exist in each sub-frame. Herein, the data groups corresponding to each parade are grouped by MH frame units, thereby configuring a single parade. The data structure shown in
Meanwhile, the concept of an MH ensemble is applied in the embodiment of the present invention, thereby defining a collection (or group) of services. Each MH ensemble carries the same QoS and is coded with the same FEC code. Also, each MH ensemble has the same unique identifier (i.e., ensemble ID) and corresponds to consecutive RS frames.
As shown in
Furthermore,
If the digital broadcasting reception system recognizes a frame start point or a frame end point of the MH frame (or the MH subframe), then the digital broadcasting reception system can set the reference time information to the system time clock at the frame start point or the frame end point. The reference time information can be the network time protocol (NTP) timestamp. The detailed description for the reference time information will be disclosed by being referred to
Hierarchical Signaling Structure
Hereinafter, a detailed description on how the receiving system accesses a virtual channel via FIC and SMT will now be given with reference to
The FIC body defined in an MH transport (M1) identifies the physical location of each the data stream for each virtual channel and provides very high level descriptions of each virtual channel.
Being MH ensemble level signaling information, the service map table (SMT) provides MH ensemble level signaling information. The SMT provides the IP access information of each virtual channel belonging to the respective MH ensemble within which the SMT is carried. The SMT also provides all IP stream component level information required for the virtual channel service acquisition.
Referring to
The FIC body payload includes information on MH ensembles (e.g., ensemble_id field, and referred to as “ensemble location” in
The application of the signaling structure in the receiving system will now be described in detail.
When a user selects a channel he or she wishes to view (hereinafter, the user-selected channel will be referred to as “channel θ” for simplicity), the receiving system first parses the received FIC. Then, the receiving system acquires information on an MH ensemble (i.e., ensemble location), which is associated with the virtual channel corresponding to channel θ (hereinafter, the corresponding MH ensemble will be referred to as “MH ensemble θ” for simplicity). By acquiring slots only corresponding to the MH ensemble θ using the time-slicing method, the receiving system configures ensemble θ. The ensemble θ configured as described above, includes an SMT on the associated virtual channels (including channel θ) and IP streams on the corresponding virtual channels. Therefore, the receiving system uses the SMT included in the MH ensemble θ in order to acquire various information on channel θ (e.g., Virtual Channel θ Table Entry) and stream access information on channel θ (e.g., Virtual Channel θ Access Info). The receiving system uses the stream access information on channel θ to receive only the associated IP streams, thereby providing channel θ services to the user.
Fast Information Channel (FIC)
The digital broadcast receiving system according to the present invention adopts the fast information channel (FIC) for a faster access to a service that is currently being broadcasted.
More specifically, the FIC handler 215 of
Meanwhile, according to the embodiment of the present invention, data are transmitted through the FIC body header and the FIC body payload in FIC segment units. Each FIC segment has the size of 37 bytes, and each FIC segment consists of a 2-byte FIC segment header and a 35-byte FIC segment payload. More specifically, an FIC body configured of an FIC body header and an FIC body payload is segmented in units of 35 data bytes, which are then carried in at least one FIC segment within the FIC segment payload, so as to be transmitted.
In the description of the present invention, an example of inserting one FIC segment in one data group, which is then transmitted, will be given. In this case, the receiving system receives a slot corresponding to each data group by using a time-slicing method.
The signaling decoder 190 included in the receiving system shown in
According to an embodiment of the present invention, when an FIC body is segmented, and when the size of the last segmented portion is smaller than 35 data bytes, it is assumed that the lacking number of data bytes in the FIC segment payload is completed with by adding the same number of stuffing bytes therein, so that the size of the last FIC segment can be equal to 35 data bytes.
However, it is apparent that the above-described data byte values (i.e., 37 bytes for the FIC segment, 2 bytes for the FIC segment header, and 35 bytes for the FIC segment payload) are merely exemplary, and will, therefore, not limit the scope of the present invention.
Herein, the FIC segment signifies a unit used for transmitting the FIC data. The FIC segment consists of an FIC segment header and an FIC segment payload. Referring to
The FIC_type field is a 2-bit field indicating the type of the corresponding FIC.
The error_indicator field is a 1-bit field, which indicates whether or not an error has occurred within the FIC segment during data transmission. If an error has occurred, the value of the error_indicator field is set to ‘1’. More specifically, when an error that has failed to be recovered still remains during the configuration process of the FIC segment, the error_indicator field value is set to ‘1’. The error_indicator field enables the receiving system to recognize the presence of an error within the FIC data.
The FIC_seg_number field is a 4-bit field. Herein, when a single FIC body is divided into a plurality of FIC segments and transmitted, the FIC_seg_number field indicates the number of the corresponding FIC segment.
Finally, the FIC_last_seg_number field is also a 4-bit field. The FIC_last_seg_number field indicates the number of the last FIC segment within the corresponding FIC body.
According to the embodiment of the present invention, the payload of the FIC segment is divided into 3 different regions. A first region of the FIC segment payload exists only when the FIC_seg_number field value is equal to ‘0’. Herein, the first region may include a current_next_indicator field, an ESG_version field, and a transport_stream_id field. However, depending upon the embodiment of the present invention, it may be assumed that each of the 3 fields exists regardless of the FIC_seg_number field.
The current_next_indicator field is a 1-bit field. The current_next_indicator field acts as an indicator identifying whether the corresponding FIC data carry MH ensemble configuration information of an MH frame including the current FIC segment, or whether the corresponding FIC data carry MH ensemble configuration information of a next MH frame.
The ESG_version field is a 5-bit field indicating ESG version information. Herein, by providing version information on the service guide providing channel of the corresponding ESG, the ESG_version field enables the receiving system to notify whether or not the corresponding ESG has been updated.
Finally, the transport_stream_id field is a 16-bit field acting as a unique identifier of a broadcast stream through which the corresponding FIC segment is being transmitted.
A second region of the FIC segment payload corresponds to an ensemble loop region, which includes an ensemble_id field, a SI_version field, and a num_channel field.
More specifically, the ensemble_id field is an 8-bit field indicating identifiers of an MH ensemble through which MH services are transmitted. The MH services will be described in more detail in a later process. Herein, the ensemble_id field binds the MH services and the MH ensemble.
The SI_version field is a 4-bit field indicating version information of SI data included in the corresponding ensemble, which is being transmitted within the RS frame.
Finally, the num_channel field is an 8-bit field indicating the number of virtual channel being transmitted via the corresponding ensemble.
A third region of the FIC segment payload a channel loop region, which includes a channel_type field, a channel_activity field, a CA_indicator field, a stand_alone_service_indicator field, a major_channel_num field, and a minor_channel_num field.
The channel_type field is a 5-bit field indicating a service type of the corresponding virtual channel. For example, the channel_type field may indicates an audio/video channel, an audio/video and data channel, an audio-only channel, a data-only channel, a file download channel, an ESG delivery channel, a notification channel, and so on.
The channel_activity field is a 2-bit field indicating activity information of the corresponding virtual channel. More specifically, the channel_activity field may indicate whether the current virtual channel is providing the current service.
The CA_indicator field is a 1-bit field indicating whether or not a conditional access (CA) is applied to the current virtual channel.
The stand_alone_service_indicator field is also a 1-bit field, which indicates whether the service of the corresponding virtual channel corresponds to a stand alone service.
The major_channel_num field is an 8-bit field indicating a major channel number of the corresponding virtual channel.
Finally, the minor_channel_num field is also an 8-bit field indicating a minor channel number of the corresponding virtual channel.
Service Table Map
According to the embodiment of the present invention, the SMT is configured in an MPEG-2 private section format. However, this will not limit the scope and spirit of the present invention. The SMT according to the embodiment of the present invention includes description information for each virtual channel within a single MH ensemble. And, additional information may further be included in each descriptor area.
Herein, the SMT according to the embodiment of the present invention includes at least one field and is transmitted from the transmitting system to the receiving system.
As described in
Meanwhile, when the SMT is not encapsulated to IP datagrams, and when it is determined that the corresponding MH TP includes an SMT section based upon the header in each of the inputted MH TP, the MH TP handler 213 outputs the SMT section to the IP network stack 220. Accordingly, the IP network stack 220 performs IP and UDP processes on the inputted SMT section and, then, outputs the processed SMT section to the SI handler 240. The SI handler 240 parses the inputted SMT section and controls the system so that the parsed SI data can be stored in the storage unit 290.
The following corresponds to example of the fields that may be transmitted through the SMT.
The table_id field corresponds to an 8-bit unsigned integer number, which indicates the type of table section. The table_id field allows the corresponding table to be defined as the service map table (SMT).
The ensemble_id field is an 8-bit unsigned integer field, which corresponds to an ID value associated to the corresponding MH ensemble. Herein, the ensemble_id field may be assigned with a value ranging from range ‘0x00’ to ‘0x3F’. It is preferable that the value of the ensemble_id field is derived from the parade_id of the TPC data, which is carried from the baseband processor of MH physical layer subsystem. When the corresponding MH ensemble is transmitted through (or carried over) the primary RS frame, a value of ‘0’ may be used for the most significant bit (MSB), and the remaining 7 bits are used as the parade_id value of the associated MH parade (i.e., for the least significant 7 bits). Alternatively, when the corresponding MH ensemble is transmitted through (or carried over) the secondary RS frame, a value of ‘1’ may be used for the most significant bit (MSB).
The num_channels field is an 8-bit field, which specifies the number of virtual channels in the corresponding SMT section.
Meanwhile, the SMT according to the embodiment of the present invention provides information on a plurality of virtual channels using the ‘for’ loop statement.
The major_channel_num field corresponds to an 8-bit field, which represents the major channel number associated with the corresponding virtual channel. Herein, the major_channel_num field may be assigned with a value ranging from ‘0x00’ to ‘0xFF’.
The minor_channel_num field corresponds to an 8-bit field, which represents the minor channel number associated with the corresponding virtual channel. Herein, the minor_channel_num field may be assigned with a value ranging from ‘0x00’ to ‘0xFF’.
The short_channel_name field indicates the short name of the virtual channel.
The service_id field is a 16-bit unsigned integer number (or value), which identifies the virtual channel service.
The service_type field is a 6-bit enumerated type field, which designates the type of service carried in the corresponding virtual channel as defined in Table 2 below.
The virtual_channel_activity field is a 2-bit enumerated field identifying the activity status of the corresponding virtual channel. When the most significant bit (MSB) of the virtual_channel_activity field is ‘1’, the virtual channel is active, and when the most significant bit (MSB) of the virtual_channel_activity field is ‘0’, the virtual channel is inactive. Also, when the least significant bit (LSB) of the virtual_channel_activity field is ‘1’, the virtual channel is hidden (when set to 1), and when the least significant bit (LSB) of the virtual_channel_activity field is ‘0’, the virtual channel is not hidden.
The num_components field is a 5-bit field, which specifies the number of IP stream components in the corresponding virtual channel.
The IP_version_flag field corresponds to a 1-bit indicator. More specifically, when the value of the IP_version_flag field is set to ‘1’, this indicates that a source_IP_address field, a virtual_channel_target_IP_address field, and a component_target_IP_address field are IPv6 addresses. Alternatively, when the value of the IP_version_flag field is set to ‘0’, this indicates that the source_IP_address field, the virtual_channel_target_IP_address field, and the component_target_IP_address field are IPv4.
The source_IP_address_flag field is a 1-bit Boolean flag, which indicates, when set, that a source IP address of the corresponding virtual channel exist for a specific multicast source.
The virtual_channel_target_IP_address_flag field is a 1-bit Boolean flag, which indicates, when set, that the corresponding IP stream component is delivered through IP datagrams with target IP addresses different from the virtual_channel_target_IP_address. Therefore, when the flag is set, the receiving system (or receiver) uses the component_target_IP_address as the target_IP_address in order to access the corresponding IP stream component. Accordingly, the receiving system (or receiver) may ignore the virtual_channel_target_IP_address field included in the num_channels loop.
The source_IP_address field corresponds to a 32-bit or 128-bit field. Herein, the source_IP_address field will be significant (or present), when the value of the source_IP_address_flag field is set to ‘1’. However, when the value of the source_IP_address_flag field is set to ‘0’, the source_IP_address field will become insignificant (or absent). More specifically, when the source_IP_address_flag field value is set to ‘1’, and when the IP_version_flag field value is set to ‘0’, the source_IP_address field indicates a 32-bit IPv4 address, which shows the source of the corresponding virtual channel. Alternatively, when the IP_version_flag field value is set to ‘1’, the source_IP_address field indicates a 128-bit IPv6 address, which shows the source of the corresponding virtual channel.
The virtual_channel_target_IP_address field also corresponds to a 32-bit or 128-bit field. Herein, the virtual_channel_target_IP_address field will be significant (or present), when the value of the virtual_channel_target_IP_address_flag field is set to ‘1’. However, when the value of the virtual_channel_target_IP_address_flag field is set to ‘0’, the virtual_channel_target_IP_address field will become insignificant (or absent). More specifically, when the virtual_channel_target_IP_address_flag field value is set to ‘1’, and when the IP_version_flag field value is set to ‘0’, the virtual_channel_target_IP_address field indicates a 32-bit target IPv4 address associated to the corresponding virtual channel. Alternatively, when the virtual_channel_target_IP_address_flag field value is set to ‘1’, and when the IP_version_flag field value is set to ‘1’, the virtual_channel_target_IP_address field indicates a 64-bit target IPv6 address associated to the corresponding virtual channel. If the virtual_channel_target_IP_address field is insignificant (or absent), the component_target_IP_address field within the num_channels loop should become significant (or present).
And, in order to enable the receiving system to access the IP stream component, the component_target_IP_address field should be used.
Meanwhile, the SMT according to the embodiment of the present invention uses a ‘for’ loop statement in order to provide information on a plurality of components.
Herein, the RTP_payload_type field, which is assigned with 7 bits, identifies the encoding format of the component based upon Table 3 shown below. When the IP stream component is not encapsulated to RTP, the RTP_payload_type field shall be ignored (or deprecated).
Table 3 below shows an example of an RTP payload type.
The component_target_IP_address_flag field is a 1-bit Boolean flag, which indicates, when set, that the corresponding IP stream component is delivered through IP datagrams with target IP addresses different from the virtual_channel_target_IP_address. Furthermore, when the component_target_IP_address_flag is set, the receiving system (or receiver) uses the component_target_IP_address field as the target IP address for accessing the corresponding IP stream component. Accordingly, the receiving system (or receiver) will ignore the virtual_channel_target_IP_address field included in the num_channels loop.
The component_target_IP_address field corresponds to a 32-bit or 128-bit field. Herein, when the value of the IP_version_flag field is set to ‘0’, the component_target_IP_address field indicates a 32-bit target IPv4 address associated to the corresponding IP stream component. And, when the value of the IP_version_flag field is set to ‘1’, the component_target_IP_address field indicates a 128-bit target IPv6 address associated to the corresponding IP stream component.
The port_num_count field is a 6-bit field, which indicates the number of UDP ports associated with the corresponding IP stream component. A target UDP port number value starts from the target_UDP_port_num field value and increases (or is incremented) by 1. For the RTP stream, the target UDP port number should start from the target_UDP_port_num field value and shall increase (or be incremented) by 2. This is to incorporate RTCP streams associated with the RTP streams.
The target_UDP_port_num field is a 16-bit unsigned integer field, which represents the target UDP port number for the corresponding IP stream component. When used for RTP streams, the value of the target_UDP_port_num field shall correspond to an even number. And, the next higher value shall represent the target UDP port number of the associated RTCP stream.
The component_level_descriptor( ) represents zero or more descriptors providing additional information on the corresponding IP stream component.
The virtual_channel_level_descriptor( ) represents zero or more descriptors providing additional information for the corresponding virtual channel.
The ensemble_level_descriptor( ) represents zero or more descriptors providing additional information for the MH ensemble, which is described by the corresponding SMT.
The descriptor_tag field is an 8-bit unsigned integer having a TBD value, which indicates that the corresponding descriptor is the MH_audio_descriptor( ) The descriptor_length field is also an 8-bit unsigned integer, which indicates the length (in bytes) of the portion immediately following the descriptor_length field up to the end of the MH_audio_descriptor( ) The channel_configuration field corresponds to an 8-bit field indicating the number and configuration of audio channels. The values ranging from ‘1’ to ‘6’ respectively indicate the number and configuration of audio channels as given for “Default bit stream index number” in Table 42 of ISO/IEC 13818-7:2006. All other values indicate that the number and configuration of audio channels are undefined.
The sample_rate_code field is a 3-bit field, which indicates the sample rate of the encoded audio data. Herein, the indication may correspond to one specific sample rate, or may correspond to a set of values that include the sample rate of the encoded audio data as defined in Table A3.3 of ATSC A/52B. The bit_rate_code field corresponds to a 6-bit field. Herein, among the 6 bits, the lower 5 bits indicate a nominal bit rate. More specifically, when the most significant bit (MSB) is ‘0’, the corresponding bit rate is exact. On the other hand, when the most significant bit (MSB) is ‘0’, the bit rate corresponds to an upper limit as defined in Table A3.4 of ATSC A/53B. The ISO_639 language_code field is a 24-bit (i.e., 3-byte) field indicating the language used for the audio stream component, in conformance with ISO 639.2/B [x]. When a specific language is not present in the corresponding audio stream component, the value of each byte will be set to ‘0x00’.
The MH_RTP_payload_type_descriptor( ) specifies the RTP payload type. Yet, the MH_RTP_payload_type_descriptor( ) exists only when the dynamic value of the RTP_payload_type field within the num_components loop of the SMT is in the range of ‘96’ to ‘127’. The MH_RTP_payload_type_descriptor( ) is used as a component_level_descriptor of the SMT.
The MH_RTP_payload_type_descriptor translates (or matches) a dynamic RTP_payload_type field value into (or with) a MIME type. Accordingly, the receiving system (or receiver) may collect (or gather) the encoding format of the IP stream component, which is encapsulated in RTP.
The fields included in the MH_RTP_payload_type_descriptor( ) will now be described in detail.
The descriptor_tag field corresponds to an 8-bit unsigned integer having the value TBD, which identifies the current descriptor as the MH_RTP_payload_type_descriptor( )
The descriptor_length field also corresponds to an 8-bit unsigned integer, which indicates the length (in bytes) of the portion immediately following the descriptor_length field up to the end of the MH_RTP_payload_type_descriptor( )
The RTP_payload_type field corresponds to a 7-bit field, which identifies the encoding format of the IP stream component. Herein, the dynamic value of the RTP_payload_type field is in the range of ‘96’ to ‘127’.
The MIME_type_length field specifies the length (in bytes) of the MIME_type field.
The MIME_type field indicates the MIME type corresponding to the encoding format of the IP stream component, which is described by the MH_RTP_payload_type_descriptor( )
The MH_current_event_descriptor( ) shall be used as the virtual_channel_level_descriptor( ) within the SMT. Herein, the MH_current_event_descriptor( ) provides basic information on the current event (e.g., the start time, duration, and title of the current event, etc.), which is transmitted via the respective virtual channel.
The fields included in the MH_current_event_descriptor( ) will now be described in detail.
The descriptor_tag field corresponds to an 8-bit unsigned integer having the value TBD, which identifies the current descriptor as the MH_current_event_descriptor( )
The descriptor_length field also corresponds to an 8-bit unsigned integer, which indicates the length (in bytes) of the portion immediately following the descriptor_length field up to the end of the MH_current_event_descriptor( )
The current_event_start_time field corresponds to a 32-bit unsigned integer quantity. The current_event_start_time field represents the start time of the current event and, more specifically, as the number of GPS seconds since 00:00:00 UTC, Jan. 6, 1980.
The current_event_duration field corresponds to a 24-bit field. Herein, the current_event_duration field indicates the duration of the current event in hours, minutes, and seconds (wherein the format is in 6 digits, 4-bit BCD=24 bits).
The title_length field specifies the length (in bytes) of the title_text field. Herein, the value ‘0’ indicates that there are no titles existing for the corresponding event.
The title_text field indicates the title of the corresponding event in event title in the format of a multiple string structure as defined in ATSC A/65C [x].
The optional MH_next_event_descriptor( ) shall be used as the virtual_channel_level_descriptor( ) within the SMT. Herein, the MH_next_event_descriptor( ) provides basic information on the next event (e.g., the start time, duration, and title of the next event, etc.), which is transmitted via the respective virtual channel. The fields included in the MH_next_event_descriptor( ) will now be described in detail.
The descriptor_tag field corresponds to an 8-bit unsigned integer having the value TBD, which identifies the current descriptor as the MH_next_event_descriptor( )
The descriptor_length field also corresponds to an 8-bit unsigned integer, which indicates the length (in bytes) of the portion immediately following the descriptor_length field up to the end of the MH_next_event_descriptor( )
The next_event_start_time field corresponds to a 32-bit unsigned integer quantity. The next_event_start_time field represents the start time of the next event and, more specifically, as the number of GPS seconds since 00:00:00 UTC, Jan. 6, 1980.
The next_event_duration field corresponds to a 24-bit field. Herein, the next_event_duration field indicates the duration of the next event in hours, minutes, and seconds (wherein the format is in 6 digits, 4-bit BCD=24 bits).
The title_length field specifies the length (in bytes) of the title_text field. Herein, the value ‘0’ indicates that there are no titles existing for the corresponding event.
The title_text field indicates the title of the corresponding event in event title in the format of a multiple string structure as defined in ATSC A/65C [x].
The MH_system_time_descriptor( ) shall be used as the ensemble_level_descriptor( ) within the SMT. Herein, the MH_system_time_descriptor( ) provides information on current time and date.
The MH_system_time_descriptor( ) also provides information on the time zone in which the transmitting system (or transmitter) transmitting the corresponding broadcast stream is located, while taking into consideration the mobile/portable characteristics of the MH service data. The fields included in the MH_system_time_descriptor( ) will now be described in detail.
The descriptor_tag field corresponds to an 8-bit unsigned integer having the value TBD, which identifies the current descriptor as the MH_system_time_descriptor( )
The descriptor_length field also corresponds to an 8-bit unsigned integer, which indicates the length (in bytes) of the portion immediately following the descriptor_length field up to the end of the MH_system_time_descriptor( )
The system_time field corresponds to a 32-bit unsigned integer quantity.
The system_time field represents the current system time and, more specifically, as the number of GPS seconds since 00:00:00 UTC, Jan. 6, 1980.
The GPS_UTC_offset field corresponds to an 8-bit unsigned integer, which defines the current offset in whole seconds between GPS and UTC time standards. In order to convert GPS time to UTC time, the GPS_UTC_offset is subtracted from GPS time. Whenever the International Bureau of Weights and Measures decides that the current offset is too far in error, an additional leap second may be added (or subtracted). Accordingly, the GPS_UTC_offset field value will reflect the change.
The time_zone_offset_polarity field is a 1-bit field, which indicates whether the time of the time zone, in which the broadcast station is located, exceeds (or leads or is faster) or falls behind (or lags or is slower) than the UTC time. When the value of the time_zone_offset_polarity field is equal to ‘0’, this indicates that the time on the current time zone exceeds the UTC time. Therefore, the time_zone_offset_polarity field value is added to the UTC time value. Conversely, when the value of the time_zone_offset_polarity field is equal to ‘1’, this indicates that the time on the current time zone falls behind the UTC time. Therefore, the time_zone_offset_polarity field value is subtracted from the UTC time value.
The time_zone_offset field is a 31-bit unsigned integer quantity. More specifically, the time_zone_offset field represents, in GPS seconds, the time offset of the time zone in which the broadcast station is located, when compared to the UTC time.
The daylight_savings field corresponds to a 16-bit field providing information on the Summer Time (i.e., the Daylight Savings Time). The time_zone field corresponds to a (5×8)-bit field indicating the time zone, in which the transmitting system (or transmitter) transmitting the corresponding broadcast stream is located.
According to the present invention, the SMT is encapsulated to UDP, while including a target IP address and a target UDP port number within the IP datagram.
More specifically, the SMT is first segmented into a predetermined number of sections, then encapsulated to a UDP header, and finally encapsulated to an IP header. In addition, the SMT section provides signaling information on all virtual channel included in the MH ensemble including the corresponding SMT section. At least one SMT section describing the MH ensemble is included in each RS frame included in the corresponding MH ensemble. Finally, each SMT section is identified by an ensemble_id included in each section. According to the embodiment of the present invention, by informing the receiving system of the target IP address and target UDP port number, the corresponding data (i.e., target IP address and target UDP port number) may be parsed without having the receiving system to request for other additional information.
More specifically, a physical channel is tuned (S501). And, when it is determined that an MH signal exists in the tuned physical channel (S502), the corresponding MH signal is demodulated (S503). Additionally, FIC segments are grouped from the demodulated MH signal in sub-frame units (S504 and S505).
According to the embodiment of the present invention, an FIC segment is inserted in a data group, so as to be transmitted. More specifically, the FIC segment corresponding to each data group described service information on the MH ensemble to which the corresponding data group belongs. When the FIC segments are grouped in sub-frame units and, then, deinterleaved, all service information on the physical channel through which the corresponding FIC segment is transmitted may be acquired. Therefore, after the tuning process, the receiving system may acquire channel information on the corresponding physical channel during a sub-frame period. Once the FIC segments are grouped, in S504 and S505, a broadcast stream through which the corresponding FIC segment is being transmitted is identified (S506). For example, the broadcast stream may be identified by parsing the transport_stream_id field of the FIC body, which is configured by grouping the FIC segments.
Furthermore, an ensemble identifier, a major channel number, a minor channel number, channel type information, and so on, are extracted from the FIC body (S507). And, by using the extracted ensemble information, only the slots corresponding to the designated ensemble are acquired by using the time-slicing method, so as to configure an ensemble (S508).
Subsequently, the RS frame corresponding to the designated ensemble is decoded (S509), and an IP socket is opened for SMT reception (S510).
According to the example given in the embodiment of the present invention, the SMT is encapsulated to UDP, while including a target IP address and a target UDP port number within the IP datagram. More specifically, the SMT is first segmented into a predetermined number of sections, then encapsulated to a UDP header, and finally encapsulated to an IP header. According to the embodiment of the present invention, by informing the receiving system of the target IP address and target UDP port number, the receiving system parses the SMT sections and the descriptors of each SMT section without requesting for other additional information (S511).
The SMT section provides signaling information on all virtual channel included in the MH ensemble including the corresponding SMT section. At least one SMT section describing the MH ensemble is included in each RS frame included in the corresponding MH ensemble. Also, each SMT section is identified by an ensemble_id included in each section.
Furthermore each SMT provides IP access information on each virtual channel subordinate to the corresponding MH ensemble including each SMT. Finally, the SMT provides IP stream component level information required for the servicing of the corresponding virtual channel.
Therefore, by using the information parsed from the SMT, the IP stream component belonging to the virtual channel requested for reception may be accessed (S513). Accordingly, the service associated with the corresponding virtual channel is provided to the user (S514).
A receiver can acquire service configuration- and location-information from a specific data position of a transmission signal, such that it can quickly and effectively acquire desired services using the acquired information. As one example of this acquired information, the FIC data have been disclosed in the above embodiment. Other embodiments of the FIC data will hereinafter be described in detail.
A FIC_Segment_Number field of 3 bits indicates a serial number of FIC segments.
A FIC_Last_Segment_Number field of 3 bits indicates a number of the last FIC segment among FIC segments.
A FIC_Update_Notifier field of 4 bits indicates an update timing of FIC data. For example, if the FIC_update_Notifier field is set to ‘0000’, this means that FIC is not immediately updated but is updated after the lapse of an MH signal frame including the FIC data having the same value as that of a corresponding field.
An ESG_version field of 4 bits indicates a version of service guide information which is exclusively transmitted through an ensemble.
Information contained in the second-type FIC segment includes at least one of a FIC_Ensemble_Header field and a FIC_Ensemble_Payload field.
The FIC_Ensemble_Header field includes an Ensemble_id field, an RS_Frame_Continuity_Counter field, a Signaling_version field, and a NumChannels field.
The Ensemble_id field of 8 bits indicates an ensemble indicator (ID). The RS_Frame_Continuity_Counter field of 4 bits indicates whether the RS frame transmitting the ensemble is continued or discontinued. The Signaling_version field of 4 bits indicates a version of signaling information of the ensemble applied to the RS frame. For example, the service transmitted through an ensemble may be described by the service map table (SMT), such that version information of this SMT may be established in this field. In addition, provided that the ensemble can be described by other signaling information transmitted on the basis of a section, version information of this signaling information may also be established in the field. For the convenience of description and better understanding of the present invention, if specific information, which is transmitted in the form of a section used as a specific transmission unit of the ensemble, describes mobile service data contained in the ensemble, this specific information is referred to as service table information.
A NumChannels field of 8 bits indicates the number of virtual channels contained in each ensemble.
A FIC_Ensemble_Payload field may include a Channel_type field, a CA_indicator field, a Primary_Service_Indicator field, a major_channel_num field, and a minor_channel_num field.
The Channel_type of 6 bits indicates a type of a service transferred through a corresponding virtual channel. Examples of this field value will hereinafter be described in detail.
The CA_indicator field of one bit represents conditional access information indicating whether a corresponding virtual channel is an access-restricted channel. For example, if the CA_indicator field is set to 1, an access to a corresponding virtual channel may be restricted.
The Primary_Service_Indicator field of one bit indicates whether a corresponding virtual channel is a primary service.
The major_channel_num field of 8 bits indicates a major number of a corresponding virtual channel, and a minor_channel_num field of 8 bits indicates a minor number of the corresponding virtual channel.
In the FIC_ensemble_payload, various fields from the Channel_type field to the minor_channel_num field from among the above-mentioned fields may be repeated according to the number of channels.
The FIC_type field of 2 bits indicates a type of the FIC segment.
The NumChannels field of 6 bits indicates the number of virtual channels transferred through an ensemble transmitting a corresponding FIC.
The FIC_Section_Number field of 8 bits indicates a number of a corresponding segment when FIC body data is divided into a plurality of segments.
The FIC_Last_Section_Number field indicates the number of the last FIC segment contained in corresponding FIC body data.
The FIC segment payload (FIC_Segment_Payload) may include a FIC_channel_header field and a FIC_channel_payload field. The FIC_channel_header field includes an ESG_requirement_flag field, a num_streams field, an IP_address_flag field, and a Target_IP_address field.
The ESG_requirement_flag field of one bit indicates whether service guide information is needed for a user to view a corresponding virtual channel. For example, if this ESG_requirement_flag field is set to 1, this field indicates whether service guide information is needed for the user to view a virtual channel. Namely, the ESG_requirement_flag field indicates that the virtual channel can be selected through service guide information.
The num_streams field of 6 bits indicates the number of video data, audio data, and data streams transferred through a corresponding virtual channel.
The IP_address_flag field of one bit can represent an IP address for providing a corresponding virtual channel by an IP version 4 (IPv4) or IP version 6 (IPv6). An address of the IP version 4 (IPv4) may be composed of 32 bits, and an address of IP version 6 (IPv6) may be composed of 48 bits. The Target_IP_address field indicates an IP address capable of receiving a corresponding virtual channel.
The FIC_channel_payload field may include a stream_type field, a target_port_number field, and an ISO_639_language_code field.
The stream_type of 8 bits indicates a type of a stream transferred through a corresponding virtual channel. The Target_port_number field of 8 bits indicates the number of a transport port capable of acquiring a corresponding stream. If a stream is an audio stream, the ISO_639_language_code field denoted by 8*3 bits indicates a language of this audio.
A general type of the MH transport packet (TP) includes a type indicator field of 3 bits, an error indicator field of one bit, a stuffing-byte field of one bit, a pointer field of 11 bits, and a payload field.
This payload field may include various format data, for example, general mobile service data, service table information transmitted in the form of a section used as a specific transmission unit, or IP datagram, etc.
The type indicator field of 3 bits indicates a type of the MH transport packet (TP). This MH TP type may be changed according to categories of data entering the payload field.
The error indicator field of one bit indicates the presence or absence of any error in the MH TP. The stuffing-byte field of one bit indicates the presence or absence of a stuffing byte in the payload.
The example shown in
A table_id field of 8 bits indicates an indicator of a table.
A section_number field of 8 bits indicates the number of a section used as an SMT transmission unit.
A last_section_number field of 8 bits indicates the last section number acquired when the SMT is transmitted after being divided into sections.
The following fields may be contained in each virtual channel (num_channels_in_ensemble) of a corresponding ensemble.
An ESG_requirement_flag field of one bit indicates whether service guide information is needed to acquire a virtual channel service.
A num_streams field of 6 bits indicates the number of audio/video/data streams of a corresponding virtual channel.
An IP_version_flag field of one bit indicates whether an IP address of a virtual channel is an IPv4 or an IPv6. In association with the case of IPv4 or IPv6, an IP address (target_IP_address) transferring a virtual channel is transmitted according to a corresponding IP address format.
In association with each stream (num_streams) contained in the virtual channel, the stream_type field of 8 bits indicates the type of a corresponding stream. The stream_type field will hereinafter be described in detail.
A target_port_number field of 8 bits indicates a number of a port corresponding to each stream.
An ISO_639 language_code field composed of 8*3 bits indicates audio language information when a corresponding stream is an audio stream.
As can be seen from
Relationship Between FIC Data and Other Data
As shown in the above-mentioned description, mobile service data and main service data are multiplexed in the MH broadcasting signal and the multiplexed data in the MH broadcasting signal is transmitted. In order to transmit mobile service data, transmission-parameter-channel signaling information is established in TPC data, and fast-information—channel signaling information is established in FIC data. TPC data and FIC data are multiplexed and randomized, ¼ Parallel Concatenated Convolutional Code (PCCC) is error-correction-encoded, such that the PCCC-encoded data is transmitted to a data group. Otherwise, mobile service data contained in the ensemble is SCCC (Serial Concatenated Convolutional Code)-outer-encoded, such that the SCCC-encoded data is transmitted to a data group. Mobile service data includes content data constructing a service and service table information describing this service. This service table information includes channel information of the ensemble indicating at least one virtual channel group, and includes service description information based on channel information.
For the convenience of description, if several data segments pass through different modulation processes in a transmission unit or different demodulation processes in a reception unit although the data segments located in the same signal frame (or the same data group), it is represented that the data segments are transferred to different data channels because these data segments are signaling-processed via different paths. For example, it can be represented that the TPC data and FIC data are transmitted to a data channel other than a data channel in which the content data and the service table information are transmitted. Because error correction coding/decoding processes to which the TPC data and FIC are applied are different from those applied to the content data and the service table information contained in the ensemble.
Under the above-mentioned assumption, a method for receiving the MH broadcasting signal will hereinafter be described. A digital broadcasting system according to the present invention receives a broadcasting signal in which mobile service data and main service data are multiplexed. The system acquires version information of FIC data from TPC data received in a first data channel among mobile service data and acquires binding information of an ensemble and a virtual channel contained in the ensemble from the FIC data. Therefore, it can be recognized which one of ensembles transmits a service of a user-selected virtual channel.
Thus, the system can receive the ensemble transferring the corresponding virtual channel according to a parade format. The system can acquire data groups contained in a series of slots from the parade received in a receiver. If the data groups are collected during only one MH frame, the system can acquire the RS frame equipped with this ensemble. Therefore, the system decodes the RS frame, and parses the service table information contained in the decoded RS frame. The system can acquire a service of the virtual channel from the parsed service table information using information describing the user-selected virtual channel.
The FIC data transferred to a first data channel may indicate binding information an ensemble and the virtual channel associated with the ensemble, in which the ensemble is transferred to a second data channel. Using the binding information, the system can parse the service table information contained in a specific ensemble, such that the service can be quickly displayed.
Referring to
The system acquires binding information of a virtual channel and ensembles at step S806, and searches for an ensemble including a desired virtual channel at step S807. As a result, the system searches for service table information (SMT) in the searched ensemble, and parses the searched SMT at step S808.
If there is needed the service guide information for acquiring a service from a corresponding virtual channel at step S809, the system checks ESG version information from FIC data at step S810.
If the checked ESG version information is new version information at step S811, the system selects the ensemble providing service guide information at step S812, acquires the service guide information, and parses the acquired service guide information at step S813.
The system determines whether the selected virtual channel is a valid channel at step S814 after performing the step S813 or S811. If the selected virtual channel is not determined to be the valid channel, the system displays a specific status in which a broadcasting signal cannot be displayed at step S815.
If the selected virtual channel is determined to be the valid channel at step S814, the system establishes either an IP address for acquiring the stream of a corresponding virtual channel or the number of ports at step S816. The system can display a channel number on the screen according to receiver operations at step S817.
If a corresponding service is displayed at step S818 and a physical channel is changed to another at step S819, the system returns to the step S802. If the ensemble is changed to another at step S820, the system performs the step S807.
If the virtual channel of the ensemble is changed to another at step S821, the system performs the step S809. If a version of FIC data is changed to another, the system acquires specific information contained in FIC body data from the signal frame, and then performs the step S805. If section-formatted signaling information having the same section format as that of service table information is updated at step S823, the system performs the step S808.
Therefore, by means of the FIC data, the system can quickly identify the ensemble transferring a selected service, and can acquire a desired service from the identified ensemble without acquiring the desired service from all ensembles.
As apparent from the above description, the digital broadcasting system and the data processing method according to the present invention have strong resistance to any errors encountered when mobile service data is transmitted over a channel, and can be easily compatible with the conventional receiver. The digital broadcasting system according to the present invention can normally receive mobile service data without any errors over a poor channel which has lots of ghosts and noises. The digital broadcasting system according to the present invention inserts known data at a specific location of a data zone, and performs signal transmission, thereby increasing the reception (Rx) performance under a high-variation channel environment. Specifically, the digital broadcasting system according to the present invention can be more effectively used for mobile phones or mobile receivers, channel conditions of which are excessively changed and have weak resistances to noise.
If the digital broadcasting system according to the present invention multiplexes mobile service data along with main service data, and transmits the multiplexed result, it can quickly access a service which is provided as mobile service data.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the inventions. Thus, it is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2008-0083068 | Aug 2008 | KR | national |
This application is a reissue application of U.S. Pat. No. 8,391,404, issued on Mar. 5, 2013 from U.S. patent application Ser. No. 13/420,471, filed on Mar. 14, 2012, which is a continuation of U.S. patent application Ser. No. 13/178,453, filed on Jul. 7, 2011, now U.S. Pat. No. 8,165,244, which is a continuation of U.S. patent application Ser. No. 12/198,089, filed on Aug. 25, 2008, now U.S. Pat. No. 8,005,167, which claims the benefit of earlier filing date and right of priority to Korean Patent Application No. 10-2008-0083068, filed on Aug. 25, 2008, and also claims the benefit of U.S. Provisional Application Ser. Nos. 61/076,686, filed on Jun. 29, 2008, 61/044,504, filed on Apr. 13, 2008, 60/977,379, filed on Oct. 4, 2007, 60/974,084, filed on Sep. 21, 2007, 60/969,166, filed on Aug. 31, 2007, and 60/957,714, filed on Aug. 24, 2007, the contents of which are all incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5208816 | Seshardi et al. | May 1993 | A |
| 5258987 | Wei | Nov 1993 | A |
| 5301167 | Proakis et al. | Apr 1994 | A |
| 5502506 | Choi | Mar 1996 | A |
| 5508752 | Kim et al. | Apr 1996 | A |
| 5619269 | Lee et al. | Apr 1997 | A |
| 5619386 | Voorman et al. | Apr 1997 | A |
| 5634138 | Ananthan et al. | May 1997 | A |
| 5649284 | Yoshinobu | Jul 1997 | A |
| 5691993 | Fredrickson | Nov 1997 | A |
| 5740205 | Baum et al. | Apr 1998 | A |
| 5754651 | Blatter et al. | May 1998 | A |
| 5757416 | Birch et al. | May 1998 | A |
| 5797093 | Houde | Aug 1998 | A |
| 5805076 | Ito et al. | Sep 1998 | A |
| 5867503 | Ohsuga et al. | Feb 1999 | A |
| 5903324 | Lyons et al. | May 1999 | A |
| 5936949 | Pasternak et al. | Aug 1999 | A |
| 5956373 | Goldston et al. | Sep 1999 | A |
| 5978424 | Turner | Nov 1999 | A |
| 6021421 | Retter et al. | Feb 2000 | A |
| 6049651 | Oshima | Apr 2000 | A |
| 6061826 | Thirumoorthy et al. | May 2000 | A |
| 6067457 | Erickson et al. | May 2000 | A |
| 6091440 | Kokkinen | Jul 2000 | A |
| 6124898 | Patel et al. | Sep 2000 | A |
| 6212659 | Zehavi | Apr 2001 | B1 |
| 6219386 | Amrany et al. | Apr 2001 | B1 |
| 6233295 | Wang | May 2001 | B1 |
| 6243469 | Kataoka et al. | Jun 2001 | B1 |
| 6263466 | Hinedi et al. | Jul 2001 | B1 |
| 6266813 | Ihara | Jul 2001 | B1 |
| 6285681 | Kolze et al. | Sep 2001 | B1 |
| 6289485 | Shiomoto | Sep 2001 | B1 |
| 6308066 | Ranta et al. | Oct 2001 | B1 |
| 6314366 | Farmakis et al. | Nov 2001 | B1 |
| 6334187 | Kadono | Dec 2001 | B1 |
| 6339618 | Puri et al. | Jan 2002 | B1 |
| 6370391 | Lietsalmi et al. | Apr 2002 | B1 |
| 6373534 | Yasuki et al. | Apr 2002 | B1 |
| 6396423 | Laumen | May 2002 | B1 |
| 6411253 | Cox et al. | Jun 2002 | B1 |
| 6459741 | Grabb et al. | Oct 2002 | B1 |
| 6490007 | Bouillet et al. | Dec 2002 | B1 |
| 6498936 | Raith | Dec 2002 | B1 |
| 6512759 | Hashimoto et al. | Jan 2003 | B1 |
| 6515713 | Nam | Feb 2003 | B1 |
| 6553538 | Zehavi | Apr 2003 | B2 |
| 6573947 | Oh | Jun 2003 | B1 |
| 6628667 | Murai et al. | Sep 2003 | B1 |
| 6651250 | Takai | Nov 2003 | B1 |
| 6665343 | Jahanghir et al. | Dec 2003 | B1 |
| 6671002 | Konishi et al. | Dec 2003 | B1 |
| 6680952 | Berg et al. | Jan 2004 | B1 |
| 6686880 | Marko et al. | Feb 2004 | B1 |
| 6731700 | Yakhnich et al. | May 2004 | B1 |
| 6734920 | Ghosh et al. | May 2004 | B2 |
| 6744474 | Markman | Jun 2004 | B2 |
| 6760077 | Choi et al. | Jul 2004 | B2 |
| 6768517 | Limberg et al. | Jul 2004 | B2 |
| 6775334 | Liu et al. | Aug 2004 | B1 |
| 6775800 | Edmonston et al. | Aug 2004 | B2 |
| 6785513 | Sivaprakasam | Aug 2004 | B1 |
| 6803970 | Limberg et al. | Oct 2004 | B1 |
| 6810084 | Jun et al. | Oct 2004 | B1 |
| 6816204 | Limberg | Nov 2004 | B2 |
| 6917655 | Fimoff et al. | Jul 2005 | B2 |
| 6924753 | Bretl et al. | Aug 2005 | B2 |
| 6927708 | Fimoff | Aug 2005 | B2 |
| 6931198 | Hamada et al. | Aug 2005 | B1 |
| 6944242 | Yakhnich et al. | Sep 2005 | B2 |
| 6947487 | Choi et al. | Sep 2005 | B2 |
| 6952595 | Ikedo et al. | Oct 2005 | B2 |
| 6956619 | Choi et al. | Oct 2005 | B2 |
| 6973137 | Birru et al. | Dec 2005 | B2 |
| 6975689 | McDonald et al. | Dec 2005 | B1 |
| 6977914 | Paila et al. | Dec 2005 | B2 |
| 6980603 | Choi et al. | Dec 2005 | B2 |
| 6985537 | Milbar | Jan 2006 | B1 |
| 6993021 | Chuah et al. | Jan 2006 | B1 |
| 6993062 | Kong et al. | Jan 2006 | B1 |
| 6996133 | Bretl et al. | Feb 2006 | B2 |
| 7010038 | Choi et al. | Mar 2006 | B2 |
| 7016327 | Grilli et al. | Mar 2006 | B2 |
| 7016446 | Spalink | Mar 2006 | B1 |
| 7020481 | Kivijarvi | Mar 2006 | B2 |
| 7027103 | Choi et al. | Apr 2006 | B2 |
| 7030935 | Choi et al. | Apr 2006 | B2 |
| 7038732 | Limberg et al. | May 2006 | B1 |
| 7042949 | Omura et al. | May 2006 | B1 |
| 7085324 | Choi et al. | Aug 2006 | B2 |
| 7092447 | Choi et al. | Aug 2006 | B2 |
| 7092455 | Choi et al. | Aug 2006 | B2 |
| 7102692 | Carlsgaard et al. | Sep 2006 | B1 |
| 7110449 | Heo et al. | Sep 2006 | B2 |
| 7111221 | Birru et al. | Sep 2006 | B2 |
| 7130313 | Pekonen | Oct 2006 | B2 |
| 7148932 | Choi et al. | Dec 2006 | B2 |
| 7151575 | Landry et al. | Dec 2006 | B1 |
| 7194047 | Strolle et al. | Mar 2007 | B2 |
| 7206352 | Birru et al. | Apr 2007 | B2 |
| 7209459 | Kangas | Apr 2007 | B2 |
| 7221358 | Sasaki | May 2007 | B2 |
| 7221680 | Vijayan et al. | May 2007 | B2 |
| 7343487 | Lindqvist et al. | Mar 2008 | B2 |
| 7359357 | Rhee et al. | Apr 2008 | B2 |
| 7376074 | Jung et al. | May 2008 | B2 |
| 7430251 | Choi et al. | Sep 2008 | B2 |
| 7440516 | Kim et al. | Oct 2008 | B2 |
| 7450613 | Choi et al. | Nov 2008 | B2 |
| 7454683 | Vesma et al. | Nov 2008 | B2 |
| 7460606 | Choi et al. | Dec 2008 | B2 |
| 7486640 | Borsos et al. | Feb 2009 | B2 |
| 7584495 | Hannuksela et al. | Sep 2009 | B2 |
| 7590187 | Jeong et al. | Sep 2009 | B2 |
| 7711045 | Park et al. | May 2010 | B2 |
| 7792103 | Kim et al. | Sep 2010 | B2 |
| 7933232 | Lee et al. | Apr 2011 | B2 |
| 8165244 | Lee et al. | Apr 2012 | B2 |
| 8490147 | Lee et al. | Jul 2013 | B2 |
| 20010011213 | Hindie et al. | Aug 2001 | A1 |
| 20010034867 | Jaffe et al. | Oct 2001 | A1 |
| 20010038744 | Yamada et al. | Nov 2001 | A1 |
| 20020080992 | Decker et al. | Jun 2002 | A1 |
| 20020085632 | Choi et al. | Jul 2002 | A1 |
| 20020089078 | Suzuki et al. | Jul 2002 | A1 |
| 20020126222 | Choi et al. | Sep 2002 | A1 |
| 20020136197 | Owen et al. | Sep 2002 | A1 |
| 20020136276 | Franceschini et al. | Sep 2002 | A1 |
| 20020138806 | Scalise et al. | Sep 2002 | A1 |
| 20020150246 | Ogino | Oct 2002 | A1 |
| 20020154709 | Choi et al. | Oct 2002 | A1 |
| 20020157099 | Schrader et al. | Oct 2002 | A1 |
| 20020159520 | Choi et al. | Oct 2002 | A1 |
| 20020172154 | Uchida et al. | Nov 2002 | A1 |
| 20020186790 | Choi et al. | Dec 2002 | A1 |
| 20020187767 | Meehan | Dec 2002 | A1 |
| 20020191716 | Xia et al. | Dec 2002 | A1 |
| 20020194570 | Birru et al. | Dec 2002 | A1 |
| 20030046431 | Belleguie | Mar 2003 | A1 |
| 20030066082 | Kliger et al. | Apr 2003 | A1 |
| 20030067899 | Chen et al. | Apr 2003 | A9 |
| 20030093798 | Rogerson | May 2003 | A1 |
| 20030099303 | Birru et al. | May 2003 | A1 |
| 20030103446 | Negishi et al. | Jun 2003 | A1 |
| 20030115540 | Bae et al. | Jun 2003 | A1 |
| 20030121045 | Cho | Jun 2003 | A1 |
| 20030125033 | Rindsberg et al. | Jul 2003 | A1 |
| 20030152107 | Pekonen | Aug 2003 | A1 |
| 20030193618 | Patel et al. | Oct 2003 | A1 |
| 20030206053 | Xia et al. | Nov 2003 | A1 |
| 20030223519 | Jeong et al. | Dec 2003 | A1 |
| 20030234890 | Bae et al. | Dec 2003 | A1 |
| 20040022307 | Dale et al. | Feb 2004 | A1 |
| 20040028076 | Strolle et al. | Feb 2004 | A1 |
| 20040034491 | Kim | Feb 2004 | A1 |
| 20040061645 | Seo et al. | Apr 2004 | A1 |
| 20040081199 | Lopez et al. | Apr 2004 | A1 |
| 20040090997 | Choi et al. | May 2004 | A1 |
| 20040101046 | Yang et al. | May 2004 | A1 |
| 20040105507 | Chang et al. | Jun 2004 | A1 |
| 20040110522 | Howard et al. | Jun 2004 | A1 |
| 20040123332 | Hanson | Jun 2004 | A1 |
| 20040125235 | Kim et al. | Jul 2004 | A1 |
| 20040148642 | Park et al. | Jul 2004 | A1 |
| 20040156460 | Kim et al. | Aug 2004 | A1 |
| 20040237024 | Limberg | Nov 2004 | A1 |
| 20040260985 | Krieger | Dec 2004 | A1 |
| 20050013380 | Kim et al. | Jan 2005 | A1 |
| 20050024543 | Ramaswamy et al. | Feb 2005 | A1 |
| 20050049923 | Tanaka et al. | Mar 2005 | A1 |
| 20050054345 | Lee | Mar 2005 | A1 |
| 20050060760 | Jaffe et al. | Mar 2005 | A1 |
| 20050090235 | Vermola et al. | Apr 2005 | A1 |
| 20050097428 | Chang et al. | May 2005 | A1 |
| 20050111586 | Kang et al. | May 2005 | A1 |
| 20050129132 | Choi et al. | Jun 2005 | A1 |
| 20050157758 | Yoo | Jul 2005 | A1 |
| 20050162886 | Jeong et al. | Jul 2005 | A1 |
| 20050166244 | Moon | Jul 2005 | A1 |
| 20050168641 | Seo | Aug 2005 | A1 |
| 20050175080 | Bouillett | Aug 2005 | A1 |
| 20050249300 | Jeong et al. | Nov 2005 | A1 |
| 20050249301 | Jeong et al. | Nov 2005 | A1 |
| 20050259813 | Wasilewski et al. | Nov 2005 | A1 |
| 20050262419 | Becker et al. | Nov 2005 | A1 |
| 20050271158 | Birru | Dec 2005 | A1 |
| 20050289586 | Park et al. | Dec 2005 | A1 |
| 20050289592 | Vermola | Dec 2005 | A1 |
| 20060007953 | Vesma et al. | Jan 2006 | A1 |
| 20060015914 | Lee | Jan 2006 | A1 |
| 20060018269 | Agrawal et al. | Jan 2006 | A1 |
| 20060029159 | Oh et al. | Feb 2006 | A1 |
| 20060031905 | Kwon | Feb 2006 | A1 |
| 20060039460 | Fimoff et al. | Feb 2006 | A1 |
| 20060039503 | Choi et al. | Feb 2006 | A1 |
| 20060052052 | Jung et al. | Mar 2006 | A1 |
| 20060072623 | Park | Apr 2006 | A1 |
| 20060078072 | Cheon et al. | Apr 2006 | A1 |
| 20060104391 | Choi et al. | May 2006 | A1 |
| 20060126633 | Park | Jun 2006 | A1 |
| 20060126668 | Kwon et al. | Jun 2006 | A1 |
| 20060126757 | Choi et al. | Jun 2006 | A1 |
| 20060130099 | Rooyen | Jun 2006 | A1 |
| 20060133429 | Seo et al. | Jun 2006 | A1 |
| 20060140301 | Choi et al. | Jun 2006 | A1 |
| 20060146797 | Lebizay | Jul 2006 | A1 |
| 20060146955 | Choi et al. | Jul 2006 | A1 |
| 20060159183 | Gaddam et al. | Jul 2006 | A1 |
| 20060184965 | Lee et al. | Aug 2006 | A1 |
| 20060194536 | Kim et al. | Aug 2006 | A1 |
| 20060223461 | Laroia et al. | Oct 2006 | A1 |
| 20060245488 | Puputti et al. | Nov 2006 | A1 |
| 20060245505 | Limberg | Nov 2006 | A1 |
| 20060245516 | Simon | Nov 2006 | A1 |
| 20060246836 | Simon | Nov 2006 | A1 |
| 20060248563 | Lee et al. | Nov 2006 | A1 |
| 20060253890 | Park et al. | Nov 2006 | A9 |
| 20060262227 | Jeong | Nov 2006 | A1 |
| 20060262744 | Xu et al. | Nov 2006 | A1 |
| 20060262863 | Park et al. | Nov 2006 | A1 |
| 20060263863 | Park et al. | Nov 2006 | A1 |
| 20060268671 | Coon | Nov 2006 | A1 |
| 20060268673 | Roh et al. | Nov 2006 | A1 |
| 20060271991 | Bae et al. | Nov 2006 | A1 |
| 20060285608 | Kim et al. | Dec 2006 | A1 |
| 20070003217 | Jang | Jan 2007 | A1 |
| 20070014379 | Park et al. | Jan 2007 | A1 |
| 20070041399 | Wendling et al. | Feb 2007 | A1 |
| 20070071110 | Choi et al. | Mar 2007 | A1 |
| 20070079223 | Mondin et al. | Apr 2007 | A1 |
| 20070092043 | Yu et al. | Apr 2007 | A1 |
| 20070101352 | Rabina et al. | May 2007 | A1 |
| 20070121681 | Kang et al. | May 2007 | A1 |
| 20070121748 | Park et al. | May 2007 | A1 |
| 20070127598 | Kang et al. | Jun 2007 | A1 |
| 20070130495 | Yoon et al. | Jun 2007 | A1 |
| 20070136643 | Kang et al. | Jun 2007 | A1 |
| 20070140368 | Kim et al. | Jun 2007 | A1 |
| 20070168844 | Jeong et al. | Jul 2007 | A1 |
| 20070172003 | Kim et al. | Jul 2007 | A1 |
| 20070195889 | Hong et al. | Aug 2007 | A1 |
| 20070201544 | Zhu et al. | Aug 2007 | A1 |
| 20070206590 | Baek et al. | Sep 2007 | A1 |
| 20070230460 | Jeong et al. | Oct 2007 | A1 |
| 20070230607 | Yu et al. | Oct 2007 | A1 |
| 20070237184 | Park et al. | Oct 2007 | A1 |
| 20070242701 | Lee et al. | Oct 2007 | A1 |
| 20070253502 | Park et al. | Nov 2007 | A1 |
| 20070258487 | Puputti | Nov 2007 | A1 |
| 20070268979 | Chang et al. | Nov 2007 | A1 |
| 20070281613 | Lee et al. | Dec 2007 | A1 |
| 20070283412 | Lie et al. | Dec 2007 | A1 |
| 20070297544 | Choi et al. | Dec 2007 | A1 |
| 20080002765 | Song et al. | Jan 2008 | A1 |
| 20080005767 | Seo | Jan 2008 | A1 |
| 20080008155 | Yoon et al. | Jan 2008 | A1 |
| 20080083000 | Orrell et al. | Apr 2008 | A1 |
| 20080095096 | Cho et al. | Apr 2008 | A1 |
| 20080170162 | Kim et al. | Jul 2008 | A1 |
| 20080225799 | Lee et al. | Sep 2008 | A1 |
| 20080239161 | Kim et al. | Oct 2008 | A1 |
| 20080240065 | Choi et al. | Oct 2008 | A1 |
| 20080240293 | Kim et al. | Oct 2008 | A1 |
| 20080240297 | Kim et al. | Oct 2008 | A1 |
| 20080246881 | Kim et al. | Oct 2008 | A1 |
| 20080267307 | Chang et al. | Oct 2008 | A1 |
| 20080273589 | Kim et al. | Nov 2008 | A1 |
| 20090013356 | Doerr et al. | Jan 2009 | A1 |
| 20090028079 | Song et al. | Jan 2009 | A1 |
| 20090028081 | Song et al. | Jan 2009 | A1 |
| 20090028230 | Leitner | Jan 2009 | A1 |
| 20090028272 | Song et al. | Jan 2009 | A1 |
| 20090052587 | Song et al. | Feb 2009 | A1 |
| 20090055864 | Yoo et al. | Feb 2009 | A1 |
| 20090059086 | Lee et al. | Mar 2009 | A1 |
| 20090067336 | Cho et al. | Mar 2009 | A1 |
| 20090077588 | Sugai | Mar 2009 | A1 |
| 20090080405 | Lee et al. | Mar 2009 | A1 |
| 20090080574 | Choi et al. | Mar 2009 | A1 |
| 20090129504 | Lee et al. | May 2009 | A1 |
| 20090175218 | Song et al. | Jul 2009 | A1 |
| 20090235141 | Shelby et al. | Sep 2009 | A1 |
| 20090252253 | Choi et al. | Oct 2009 | A1 |
| 20090260041 | McGinn et al. | Oct 2009 | A1 |
| 20090265751 | Limberg | Oct 2009 | A1 |
| 20100100793 | Limberg | Apr 2010 | A1 |
| 20100254494 | Song et al. | Oct 2010 | A1 |
| 20110261902 | Lee et al. | Oct 2011 | A1 |
| 20120177149 | Lee et al. | Jul 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1463126 | Dec 2003 | CN |
| 1496107 | May 2004 | CN |
| 1678068 | Oct 2005 | CN |
| 1736119 | Feb 2006 | CN |
| 1738436 | Feb 2006 | CN |
| 1829270 | Sep 2006 | CN |
| 1946190 | Apr 2007 | CN |
| 101018105 | Aug 2007 | CN |
| 101018223 | Aug 2007 | CN |
| 101022435 | Aug 2007 | CN |
| 0996291 | Apr 2000 | EP |
| 1014711 | Jun 2000 | EP |
| 1085750 | Mar 2001 | EP |
| 1566905 | Aug 2005 | EP |
| 1628420 | Feb 2006 | EP |
| 1768396 | Mar 2007 | EP |
| 9-284664 | Oct 1997 | JP |
| 11069253 | Mar 1999 | JP |
| 2000224136 | Aug 2000 | JP |
| 2001054031 | Feb 2001 | JP |
| 2001274769 | Oct 2001 | JP |
| 2002218339 | Aug 2002 | JP |
| 2003032640 | Jan 2003 | JP |
| 2003134117 | May 2003 | JP |
| 2003209525 | Jul 2003 | JP |
| 2003284037 | Oct 2003 | JP |
| 2004129126 | Apr 2004 | JP |
| 2006148543 | Jun 2006 | JP |
| 2007096403 | Apr 2007 | JP |
| 10-1998-0023115 | Jul 1998 | KR |
| 1020000040481 | Jul 2000 | KR |
| 20030026236 | Mar 2003 | KR |
| 1020030030175 | Apr 2003 | KR |
| 1020030037138 | May 2003 | KR |
| 1020030062138 | Jul 2003 | KR |
| 10-2004-0013153 | Feb 2004 | KR |
| 1020040032282 | Apr 2004 | KR |
| 1020040032283 | Apr 2004 | KR |
| 1020050036552 | Apr 2005 | KR |
| 1020050041489 | May 2005 | KR |
| 10-2005-0062867 | Jun 2005 | KR |
| 10-2005-0062867 | Jun 2005 | KR |
| 1020050065898 | Jun 2005 | KR |
| 1020050072988 | Jul 2005 | KR |
| 10-2005-0093921 | Sep 2005 | KR |
| 1020050112879 | Dec 2005 | KR |
| 1020050117314 | Dec 2005 | KR |
| 10-2006-0016582 | Feb 2006 | KR |
| 10-2006-0017695 | Feb 2006 | KR |
| 1020060009737 | Feb 2006 | KR |
| 1020060012510 | Feb 2006 | KR |
| 1020060039728 | May 2006 | KR |
| 1020060053061 | May 2006 | KR |
| 1020060055959 | May 2006 | KR |
| 10-2006-0065435 | Jun 2006 | KR |
| 1020060063867 | Jun 2006 | KR |
| 1020060065435 | Jun 2006 | KR |
| 1020060068449 | Jun 2006 | KR |
| 1020060068989 | Jun 2006 | KR |
| 1020060070665 | Jun 2006 | KR |
| 1020060072573 | Jun 2006 | KR |
| 10-2006-0095235 | Aug 2006 | KR |
| 1020060095126 | Aug 2006 | KR |
| 1020060102160 | Sep 2006 | KR |
| 1020060117484 | Nov 2006 | KR |
| 1020060133011 | Dec 2006 | KR |
| 1020070007995 | Jan 2007 | KR |
| 1020070013168 | Jan 2007 | KR |
| 1020070015810 | Feb 2007 | KR |
| 10-2007-0034215 | Mar 2007 | KR |
| 100710248 | Apr 2007 | KR |
| 1020070068015 | Jun 2007 | KR |
| 1020070068960 | Jul 2007 | KR |
| 1020070075549 | Jul 2007 | KR |
| 10-2007-0079328 | Aug 2007 | KR |
| 0044145 | Jul 2000 | WO |
| 0045552 | Aug 2000 | WO |
| 0105157 | Jan 2001 | WO |
| 01005157 | Jan 2001 | WO |
| 03017254 | Feb 2003 | WO |
| 03049449 | Jun 2003 | WO |
| 2004057873 | Jul 2004 | WO |
| 2004066652 | Aug 2004 | WO |
| 2005032034 | Apr 2005 | WO |
| 2005043403 | May 2005 | WO |
| 2005069624 | Jul 2005 | WO |
| 2005101655 | Oct 2005 | WO |
| 2005109878 | Nov 2005 | WO |
| 2006003531 | Jan 2006 | WO |
| 2006003531 | Jan 2006 | WO |
| 2007030590 | Mar 2007 | WO |
| 2007046676 | Apr 2007 | WO |
| 2007089108 | Aug 2007 | WO |
| 2008105587 | Sep 2008 | WO |
| 2009038402 | Mar 2009 | WO |
| 2009038405 | Mar 2009 | WO |
| Entry |
|---|
| Kim, Sung-Hoon, et al.; “Enhanced-x VSB System Development for Improving ATSC Terrestrial DTV Transmission Standard”; IEEE Transactions on Broadcasting, vol. 52, No. 2, Jun. 2006. |
| ATSC Standards: “A/53: ATSC Digital Television Standard, Parts 1-6”, Advanced Television Systems Committee, Inc, Washington, D.C., USA. vol. A/53, Jan. 3, 2007, pp. 1-136, XP008115585, Retrieved from the Internet: URL:http″//www.atsc.org/standards/a53/a_53-Part-1-62007.pdf *the whole document*. |
| ESTI EN 300 744: “Digital Video Broadcasting( DVB); Framing structure, channel coding and modulation for digital terrestrial television (DVB-T)”, V1.2.1 (Jul. 1999), XP-002231749. |
| ESTI EN 300 468: “Digital Video Broadcasting(DVB); Specification for Service Information (SI) in DVB systems”, V1.3.1 (Feb. 1998). |
| Search Report of European Patent Office in Appl'n. No. 08778394.0, dated Oct. 18, 2013. |
| Notice of Allowance of Korean Patent Office in Appl'n. No. 10-2008-0060491, dated Mar. 20, 2014. |
| Notice of Allowance of Korean Patent Office in Appl'n. No. 10-2008-0083068, dated Jun. 24, 2014. |
| Notice of Allowance of Korean Patent Office in Appl'n. No. 10-2014-0107109, dated Sep. 23, 2014. |
| Office Action of India Patent Office in Appl'n. No. 149/KOLNP/2010, dated Nov. 19, 2014. |
| Notice of Allowance of the U.S. Patent Office in U.S. Appl. No. 12/962,500, dated May 19, 2014. |
| Office Action of the U.S. Patent Office in U.S. Appl. No. 14/463,371, dated Nov. 14, 2014. |
| Office Action of the U.S. Patent Office in U.S. Appl. No. 14/152,742, dated Feb. 10, 2016. |
| U.S. Appl. No. 13/420,471, filed Mar. 14, 2012 (U.S. Pat. No. 8,391,404). |
| U.S. Appl. No. 13/178,453, filed Jul. 7, 2011 (U.S. Pat. No. 8,165,244). |
| U.S. Appl. No. 12/198,089, filed Aug. 25, 2008 (U.S. Pat. No. 8,005,167). |
| Chernock, Rich; “PSIP Generation and ATSC Stream Monitoring”; Triveni Digital, Oct. 8, 2004. |
| Advanced Television Systems Commitee; “Recommended practice: Guide to the Use of the ATSC Digital Television Standard, Including Corrigendum No. 1”; Doc A/54A; Dec. 4, 2003. |
| ISO/IEC: “Information Technology—Generic Coding of Moving Pictures and Associated Audio Information Systems”; ISO/IEC 13818-1: International Standard; Second Edition; Dec. 1, 2000. |
| Federal Information Processing Standards Publication 197; Announcing the Advanced Encryption Standard (AES); Nov. 26, 2001. |
| Graell, A. et al., “Analysis and Design of Rate Compatible Serial Concatenated Convolutional Codes”; Proceedings of the 2005 International Symposium on Information Theory; pp. 607-611; Sep. 4, 2005. |
| Advanced Television Systems Committee; “ATSC Recommended Practice: E-VSB Implementation Guidelines” ; Doc A/112, Apr. 18, 2006. |
| Yao, J., “IP Datacasting and Channel Error Handling With DVB-H”;Proceedings of the 2005 Emerging Information Technology Conference; XP-010856441; Aug. 15, 2005. |
| Touzni, A, et al. “Enhanced 8-VSB Transmission for North-American HDTV Terrestrial Broadcast”; Proceedings of the 2003 IEEE International Conference on Acoustics, Speech and Signal Processing; vol. 2; pp. 437-440. XP010640975; Apr. 6, 2003. |
| Gaddam, V. R., et al., “A Newly Proposed ATSC DTV System for Transmitting a Robust Bit-Stream Along With the Standard Bit-Stream”, IEEE Transactions on Consumer Electronics, XP001201224; vol. 49; Issue 4; Nov. 2003. |
| Gupta, N., “The Eureka 147 Digital Audio Broadcasting System Adapted to the U.S.,” Massachusetts Institute of Technology (MIT), May 1996, Retrieved online on Jan. 13, 2010 at http://dspace.mit.edu/bitstream/handle/1721.1/38795/35332950.pdf?sequence=1. |
| Fairhurst, G. et al.; “Extensions Formats for Unidirectional Lightweight Encapsulation (ULE) and the Generic Stream Encapsulation (GSE)”; Internet Engineering Task Force; Aug. 2007. |
| European Telecommunications Standards Institute (ETSI); “Digital Video Broadcasting (DVB); Support for Use of Scrambling and Conditional Access (CA) Within Digital Broadcasting Systems”; ETR 289; Oct. 1996. |
| European Telecommunications Standards Institute (ETSI); “Digital Audio Broadcasting (DAB); Internet Protocol (IP) Datagram Tunnelling”; ETSI ES 201 735; v1.1.1; (Sep. 2000). |
| European Telecommunications Standards Institute (ETSI); “Digital Audio Broadcasting (DAB); Conditional Access”; ETSI TS 102 367; v1.1.1 (Jan. 2005). |
| Chari, M et al.; “FLO Physical Layer: An Overview”; IEEE transactions on Broadcasting; vol. 53, Issue 1, part 2; pp. 145-160; Feb. 26, 2007. |
| European Telecommunications Standards Institute (ETSI); “Digital Video Broadcasting (DVB); IP Datacast Over DVB-H; Program Specific Information (PSI)/Service Information (SI)”; ETSI TS 102 470 v1.1.1; (Apr. 2006). |
| European Telecommuniaction Standards Institute (ETSI); Digital Audio Broadcasting (DAB); Distribution Interfaces; Ensemble Transport Interface (ETI); ETSI ETS 300 799; Sep. 1997. |
| Fimoff, M., et al.; “E-VSB Map Signaling”, IEEE Transactions on Consumer Electronics; vol. 49; Issue 3; pp. 515-518; Aug. 2003. |
| Advanced Television Systems Committee; “ATSC Standard: Digital Television Standard (A/53), Revision D, Including Amendment No. 1”, DocA/53D; Jul. 19, 2005. |
| Uehara, M., et al.; “Transmission Scheme for the Terrestrial ISDB System”; IEEE Transactions on Consumer Electronics; vol. 45; Issue 1; Feb. 1999. |
| ETSI “Digital Video Broadcasting (DVB); DVB-H Implementation Guidelines” ETSI TR 102 377 v1.2.1, Nov. 2005. |
| ATSC Standard “Program and System Information Protocol for Terrestrial Broadcast and Cable (Revision B)” A/65B, Mar. 18, 2003. |
| Advanced Television Systems Committee (ATSC); “Candidate Standard: ATSC-M/H Standard, Part 1—Mobile/Handheld Digital Television System (A/153, Part 1:2009)”; Doc. No. S4-130r12; Dec. 31, 2008. |
| Advanced Television Systems Committee (ATSC); “Candidate Standard: ATSC-M/H Standard, Part 2—Mobile/Handheld Digital Television System (A/153, Part 1:2009)”; Doc. No. S4-131r11; Dec. 31, 2008. |
| Advanced Television Systems Committee (ATSC); “Candidate Standard: ATSC-M/H Standard, Part 3—Mobile/Handheld Digital Television System (A/153, Part 1:2009)”; Doc. No. S4-132r11; Dec. 31, 2008. |
| Korean Broadcasting System (KBS); “Technology Trend in DTV RF Transmission”; KBS Broadcast Technical Research; 2007; pp. 73-92. |
| DVB Document A092 Rev. 2 (Draft v. 1.3.1), DVB-H Implementation Guidelines, May 2007, all pages, (www.dvb-h.org). |
| ETSI TS 102 470 V1.1.1, Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Program Specific Information (PSI)/Service Information (SI), Apr. 2006, all pages. |
| OMA-TS-BCAST_SERVICES-V1_0-20070529-C, Mobile Broadcast Services Candidate Version 1.0, May 29, 2007, all pages. |
| ETSI EN 300 401 V1.4.1, Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to Mobile, Portable and Fixed Receivers; Jun. 2006. |
| Number | Date | Country | |
|---|---|---|---|
| 61076686 | Jun 2008 | US | |
| 61044504 | Apr 2008 | US | |
| 60977379 | Oct 2007 | US | |
| 60974084 | Sep 2007 | US | |
| 60969166 | Aug 2007 | US | |
| 60957714 | Aug 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13178453 | Jul 2011 | US |
| Child | 13420471 | US | |
| Parent | 12198089 | Aug 2008 | US |
| Child | 13178453 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13420471 | Mar 2012 | US |
| Child | 14638900 | US |
