Title of Invention

A METHOD OF RECEIVING A BROADCAST SIGNAL IN A RECEIVING SYSTEM AND A RECEIVING SYSTEM FOR RECEIVING BROADCAST SIGNAL

Abstract A digital broadcasting system and a data processing method are disclosed. A receiving system ot the digital broadcasting system includes a baseband processor, an IP network stack, and a handler. The baseband processor receives a broadcast signal including mobile service data and main service data. Herein the mobile service data configures a Reed-Solomon (RS) frame, and the RS frame includes mobile service data and an internet protocol (IP) signaling channel having pro-decided IP access information included therein. The IP network stack accesses the IP signaling channel from the RS frame using the IP access information, thereby collecting signaling table information received through the IP signaling channel. And the handler identifies and parses the collected signaling table information based upon a table identifier of each signaling table received through the IP signaling channel, thereby storing the parsed result.
Full Text

Description
DIGITAL BROADCASTING SYSTEM AND METHOD OF
PROCESSING DATA IN DIGITAL BROADCASTING SYSTEM
Technical Field
[ 1 ] The present invention relates to a digital broadcasting system and a method of
processing data in a digital broadcasting system for transmitting and receiving digital
broadcast signals.
Background Art
[2] 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.
Disclosure of Invention
Technical Problem
[3] Accordingly, 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.
[4] Another object of the present invention is to provide a digital broadcasting system
and a data processing method that can receive and process mobile service data and
access information of the respective mobile service data.
Technical Solution
[5] To achieve these objects and other advantages and in accordance with the purpose of
the invention, as embodied and broadly described herein, a receiving system includes a
baseband processor, an IP network stack, and a handler. The baseband processor
receives a broadcast signal including mobile service data and main service data.
Herein, the mobile service data configures a Reed-Solomon (RS) frame, and the RS
frame includes mobile service data and an internet protocol (IP) signaling channel
having pre-decided IP access information included therein. The IP network stack
accesses the IP signaling channel from the RS frame using the IP access information,
thereby collecting signaling table information received through the IP signaling
channel. And. the handler identifies and parses the collected signaling table in-
formation based upon a table identifier of each signaling table received through the IP

signaling channel, thereby storing the parsed result.
[6] Herein, the IP access information may include a target IP address and a target UDP
port number, and the target IP address and target UDP port number of each UDP/IP
packet transmitted through the IP signaling channel may be identical to one another.
Also, the IP signaling channel may be received through at least one of a primary RS
frame and a secondary RS frame, based upon a level of importance of the cor-
responding signaling table. Moreover, the receiving system may further include a
known sequence detector, which detects a known data sequence linearly inserted in at
least one data group configuring the RS frame. Herein, the detected known data
sequence may be used for channel-equalizing the mobile service data.
[7] In another aspect of the present invention, a method for processing data in a
receiving system includes the steps of receiving a broadcast signal including mobile
service data and main service data, wherein the mobile service data configure a Reed-
Solomon (RS) frame, and wherein the RS frame includes mobile service data and an
internet protocol (IP) signaling channel having pre-decided IP access information
included therein, accessing the IP signaling channel from the RS frame using the IP
access information, thereby collecting signaling table information received through the
IP signaling channel, and identifying and parsing the collected signaling table in-
formation based upon a table identifier of each signaling table received through the IP
signaling channel, thereby storing the parsed result. Herein, the method may further
include detecting a known data sequence linearly inserted in at least one data group
configuring the RS frame.
[8] Additional advantages, objects, and features of the invention may be realized and
attained by the structure particularly pointed out in the written description as well as
the appended drawings.
Advantageous Effects
[9] The digital broadcasting system and the data processing method according to the
present invention have the following advantages. The present invention assigns an IP
signaling channel having a well-known target IP address and a well-known target UDP
port number to each ensemble. Then, the present invention transmits a signaling table
describing information required for service access through the IP signaling channel.
Therefore, after configuring the ensembles, the digital broadcast receiving system
according to the present invention opens an IP socket for an IP stream having the cor-
responding well-known target IP address and well-known target UDP port number.
[10] More specifically, the digital broadcast receiving system may access the IP signaling
channel without requesting for any separate information. Furthermore, by using a table
identifier included in a header of each signaling table, the digital broadcast receiving

system according to the present invention can find (or locate) a desired signaling table
from the corresponding IP stream.
Brief Description of the Drawings
[11] 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:
[12J FIG. 1 illustrates a block diagram showing a general structure of a digital
broadcasting receiving system according to an embodiment of the present invention;
[13] FIG. 2 illustrates an exemplary structure of a data group according to the present
invention;
[14] FIG. 3 illustrates an RS frame according to an embodiment of the present invention;
[15] FIG. 4 illustrates an example of an MH frame structure for transmitting and receiving
mobile service data according to the present invention;
[16] FIG. 5 illustrates an example of a general VSB frame structure;
[17] FIG. 6 illustrates a example of mapping positions of the first 4 slots of a sub-frame in
a spatial area with respect to a VSB frame;
[18] FIG. 7 illustrates a example of mapping positions of the first 4 slots of a sub-frame in
a chronological (or time) area with respect to a VSB frame;
[ 19] FIG. 8 illustrates an exemplary order of data groups being assigned to one of 5 sub-
frames configuring an MH frame according to the present invention;
[20] FIG. 9 illustrates an example of a single parade being assigned to an MH frame
according to the present invention;
[21] FIG. 10 illustrates an example of 3 parades being assigned to an MH frame according
to the present invention;
[22] FIG. 11 illustrates an example of the process of assigning 3 parades shown in FIG.
10 being expanded to 5 sub-frames within an MH frame;
[23] FIG. 12 illustrates a data transmission structure according to an embodiment of the
present invention, wherein signaling data are included in a data group so as to be
transmitted;
[24] FIG. 13 illustrates a hierarchical signaling structure according to an embodiment of
the present invention;
[25] FIG. 14 illustrates an exemplary FIC body format according to an embodiment of the
present invention;
[26] FIG. 15 illustrates an exemplary bit stream syntax structure with respect to an FIC
segment according to an embodiment of the present invention;
|27| FIG. 16 illustrates an exemplary bit stream syntax structure with respect to a payload

of an FIC segment according to the present invention, when an FIC type field value is
equal to '0';
[28] FIG. 17 illustrates an exemplary bit stream syntax structure of a service map table
according to the present invention;
[29] FIG. 18 illustrates an exemplary bit stream syntax structure of an MH audio
descriptor according to the present invention;
[30] FIG. 19 illustrates an exemplary bit stream syntax structure of an MH RTP payload
type descriptor according to the present invention;
[31] FIG. 20 illustrates an exemplary bit stream syntax structure of an MH current event
descriptor according to the present invention;
[32] FIG. 21 illustrates an exemplary bit stream syntax structure of an MH next event
descriptor according to the present invention;
[33] FIG. 22 illustrates an exemplary bit stream syntax structure of an MH system time
descriptor according to the present invention;
[34] FIG. 23 illustrates segmentation and encapsulation processes of a service map table
according to the present invention;
[35] FIG. 24 illustrates a flow chart for accessing a virtual channel using FIC and SMT
according to the present invention;
[36] FIG. 25 illustrates an exemplary structure of an IP signaling channel according to an
embodiment of the present invention;
[37] FIG. 26 illustrates an exemplary syntax structure of an STT section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention;
[38] FIG. 27 illustrates an exemplary syntax structure of an RRT section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention;
[39] FIG. 28 illustrates an exemplary syntax structure of a CIT section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention;
[40] FIG. 29 illustrates an exemplary syntax structure of a GAT section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention;
[41 ] FIG. 30 illustrates an exemplary syntax structure of an FET section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention; and
[42] FIG. 31 illustrates a flow chart showing an IP signaling processing method according
to the present invention.

Best Mode for Carrying Out the Invention
[43] Reference will now be made in detail to the preferred embodiments of the present
invention, examples of which are illustrated in the accompanying drawings.
[44]
[45] Definition of the terms used in the present invention
[46] In addition, although the terms used in the present invention are selected from
generally known and used terms, some of the terms mentioned in the description of the
present invention have been selected by the applicant at his or her discretion, the
detailed meanings of which are described in relevant parts of the description herein.
Furthermore, it is required that the present invention is understood, not simply by the
actual terms used but by the meaning of each term lying within.
[47] 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.
[48] 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 charac-
teristics. Therefore, the mobile service data according to the present invention are not
limited only to the MH service data.
[49] 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.

[50] 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 in-
formation 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.
[51] 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.
[52] Furthermore, the 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.
[53] 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.
[54]
[55] Receiving System
[56] FIG. 1 illustrates a block diagram showing a general structure of a receiving system
according to an embodiment of the present invention. The receiving system according
to the present invention includes a baseband processor 100, a management processor
200, and a presentation processor 300.
[57] The baseband processor 100 includes an operation controller 110, a tuner 120, a de-
modulator 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.
[58] The operation controller 110 controls the operation of each block included in the
baseband processor 100.
[59] 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 down-converted to an in-
termediate 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.
[60] The demodulator 130 performs self-gain control, carrier recovery, and timing
recovery processes on the passband digital IF signal inputted from the tuner 120,
thereby translating 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 recovery, thereby enhancing the
demodulating performance.
[61] 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 feed-back on the
decoding result from the block decoder 160, thereby enhancing the equalizing
performance.
[62] 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 de-
modulated 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 de-
modulator 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.
[63] 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.
[64] 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 (F1C)
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.
[65] 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.
[66] 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
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.
[67] 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 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.
[68] 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.
[69] 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.
[70] The TPC handler 214 receives and processes baseband information required by
modules corresponding to the MH physical adaptation processor 210. The baseband in-
formation 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.
[71] 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.
[72] Herein, the MH ensemble ID indicates an identification number of each MH
ensemble carried in the corresponding channel.
[73] 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.
[74] 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.
[75] 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.
[76] 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.
[77] Finally, the FIC version number signifies the version number of an FIC carried on
the corresponding physical channel.
[78 ] As described above, diverse TPC data are inputted to the TPC handler 214 via the
signaling decoder 190 shown in FIG. 1. Then, the received TPC data are processed by
the TPC handler 214. The received TPC data may also be used by the FIC handler 215
in order to process the FIC data.
|79| The FIC handler 215 processes the FIC data by associating the FIC data received

from the baseband processor 100 with the TPC data.
[80] The physical adaptation control signal handler 216 collects F1C 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.
[81] 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.
[82] 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.
[83] 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.
[84] 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 cor-
responding 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.
[85] The SI handler 240 receives and processes SI data having the form of IP datagrams,
which are inputted to the IP network stack 220.
[86] When the inputted data associated with SI correspond to MIME-type data, the
inputted data are outputted to the MIME-type handler 260.
[87] 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.

[88] 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 cor-
responding file includes data for other file-based services, the file is outputted to the
presentation controller 330 of the presentation processor 300.
[89] 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.
[90] 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.
[91] 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.
[92] 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.
[93] 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.
[94] The presentation controller 330 corresponds to a controller managing modules that
output data received by the receiving system to the user.
[95] 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.
[96] 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.
[97]
[98] Data Format Structure
[99] 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.
[ 100] FIG. 2 illustrates an exemplary structure of a data group according to the present
invention.
[ 101] FIG. 2 shows an example of dividing a data group according to the data structure of
the present invention into 10 MH blocks (i.e., MH block 1 (B1) to MH block 10
(B10)). In this example, each MH block has the length of 16 segments. Referring to
FIG. 2, only the RS parity data are allocated to portions of the previous 5 segments of
the MH block 1 (B1) and the next 5 segments of the MH block 10 (B10). The RS
parity data are excluded in regions A to D of the data group.
[ 102] 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 in-
terference 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 pe-
riodically 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.
[ 103] Referring to FIG. 2, MH block 4 (B4) to MH block 7 (B7) correspond to regions
without interference of the main service data. MH block 4 (B4) to MH block 7 (B7)
within the data group shown in FIG. 2 correspond to a region where no interference
from the main service data occurs. In this example, a long known data sequence is
inserted at both the beginning and end of each MH block. In the description of the
present invention, the region including MH block 4 (B4) to MH block 7 (B7) will be
referred to as "region A (=B4+B5+B6+B7)". As described above, when the data group
includes region A having a long known data sequence inserted at both the beginning
and end of each MH block, the receiving system is capable of performing equalization
by using the channel information that can be obtained from the known data. Therefore,
the strongest equalizing performance may be yielded (or obtained) from one of region
A to region D.
[ 104] In the example of the data group shown in FIG. 2, MH block 3 (B3) and MH block 8

(B8) correspond to a region having little interference from the main service data.
Herein, a long known data sequence is inserted in only one side of each MH block B3
and B8. More specifically, due to the interference from the main service data, a long
known data sequence is inserted at the end of MH block 3 (B3), and another long
known data sequence is inserted at the beginning of MH block 8 (B8). In the present
invention, the region including MH block 3 (B3) and MH block 8 (B8) will be referred
to as "region B (=B3+B8)". As described above, when the data group includes region
B having a long known data sequence inserted at only one side (beginning or end) of
each MH block, the receiving system is capable of performing equalization by using
the channel information that can be obtained from the known data. Therefore, a
stronger equalizing performance as compared to region C/D may be yielded (or
obtained).
[105] Referring to FIG. 2, MH block 2 (B2) and MH block 9 (B9) correspond to a region
having more interference from the main service data as compared to region B. A long
known data sequence cannot be inserted in any side of MH block 2 (B2) and MH block
9 (B9). Herein, the region including MH block 2 (B2) and MH block 9 (B9) will be
referred to as "region C (=B2+B9)".
[106] Finally, in the example shown in FIG. 2, MH block 1 (B1) and MH block 10 (B10)
correspond to a region having more interference from the main service data as
compared to region C. Similarly, a long known data sequence cannot be inserted in any
side of MH block 1 (B1) and MH block 10 (B10). Herein, the region including MH
block 1 (B1) and MH block 10 (B10) will be referred to as "region D (=B1+B10)".
Since region C/D is spaced further apart from the known data sequence, when the
channel environment undergoes frequent and abrupt changes, the receiving
performance of region C/D may be deteriorated.
[107] Additionally, the data group includes a signaling information area wherein signaling
information is assigned (or allocated).
[ 108] 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 1 st segment of the 4th MH block (B4) to a
portion of the 2nd segment.
[109] 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 in-
formation 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.
[110] Herein, the signaling information may be identified by two different types of

signaling channels: a transmission parameter channel (TPC) and a fast information
channel (F1C).
[111] 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).
[112] For example, when the data group includes 6 known data sequences, as shown in
FIG. 2, the signaling information area is located between the first known data sequence
and the second known data sequence. More specifically, the first known data sequence
is inserted in the last 2 segments of the 3rd MH block (B3), and the second known data
sequence in inserted in the 2nd and 3rd segments of the 4th MH block (B4).
Furthermore, the 3rd to 6th known data sequences are respectively inserted in the last 2
segments of each of the 4th, 5th, 6th, and 7th MH blocks (B4, B5, B6, and B7). The 1st
and 3rd to 6th known data sequences are spaced apart by 16 segments.
[113] FIG. 3 illustrates an RS frame according to an embodiment of the present invention.
[114] The RS frame shown in FIG. 3 corresponds to a collection of one or more data
groups. The RS frame is received for each MH frame in a condition where the
receiving system receives the FIC and processes the received FIC and where the
receiving system is switched to a time-slicing mode so that the receiving system can
receive MH ensembles including ESG entry points. Each RS frame includes IP streams
of each service or ESG, and SMT section data may exist in all RS frames.
[115] 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.
[116] 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.
[117] 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. Signaling information within the MP
payload may further include data on an IP signaling channel having well-known access
information. More specifically, at least a portion of the signaling data may be
transmitted (or delivered) through the IP signaling channel. The IP signaling channel
will be described in more detail later on with reference to FIG. 25.
[118] In the example shown in FIG. 3, the RS frame is assigned with IP datagrams (IP
datagram 1 and IP datagram 2) for two service types.
[119]
[120] Data Transmission Structure
[121] FIG. 4 illustrates a structure of a MH frame for transmitting and receiving mobile
service data according to the present invention. In the example shown in FIG. 4, one
MH frame consists of 5 sub-frames, wherein each sub-frame includes 16 slots. In this
case, the MH frame according to the present invention includes 5 sub-frames and 80
slots.
[122] 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 (1/2) 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.
[123] FIG. 5 illustrates an exemplary structure of a VSB frame, wherein one VSB frame
consists of 2 VSB fields (i.e., an odd field and an even field). Herein, each VSB field
includes a field synchronization segment and 312 data segments.
[124] The slot corresponds to a basic time unit for multiplexing the mobile service data and
the main service data. Herein, one slot may either include the mobile service data or be
configured only of the main service data.
[125] 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.
[126] Meanwhile, when the slots are assigned to a VSB frame, an off-set exists for each
assigned position.
[127] FIG. 6 illustrates a mapping example of the positions to which the first 4 slots of a
sub-frame are assigned with respect to a VSB frame in a spatial area. And, FIG. 7 il-
lustrates a mapping example of the positions to which the first 4 slots of a sub-frame
are assigned with respect to a VSB frame in a chronological (or time) area.
[128] Referring to FIG. 6 and FIG. 7. a 38th data packet (TS packet #37) of a 1 st slot (Slot
#0) is mapped to the 1st data packet of an odd VSB field. A 38th data packet (TS

packet #37) of a 2nd slot (Slot #1) is mapped to the 157th data packet of an odd VSB
field. Also, a 38th data packet (TS packet #37) of a 3rd slot (Slot #2) is mapped to the
1st data packet of an even VSB field. And, a 38th data packet (TS packet #37) of a 4th
slot (Slot #3) is mapped to the 157th data packet of an even VSB field. Similarly, the
remaining 12 slots within the corresponding sub-frame are mapped in the subsequent
VSB frames using the same method.
[129] FIG. 8 illustrates an exemplary assignment order of data groups being assigned to
one of 5 sub-frames, wherein the 5 sub-frames configure an MH frame. For example,
the method of assigning data groups may be identically applied to all MH frames or
differently applied to each MH frame. Furthermore, the method of assigning data
groups may be identically applied to all sub-frames or differently applied to each sub-
frame. At this point, when it is assumed that the data groups are assigned using the
same method in all sub-frames of the corresponding MH frame, the total number of
data groups being assigned to an MH frame is equal to a multiple of '5'.
[130] 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
sub-frame. Thus, the system can be capable of responding promptly and effectively to
any burst error that may occur within a sub-frame.
[131] 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. FIG. 8 illustrates an example of assigning 16 data
groups in one sub-frame using the above-described pattern (or rule). In other words,
each data group is serially assigned to 16 slots corresponding to the following
numbers: 0, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7, and 15. Equation 1 below shows
the above-described rule (or pattern) for assigning data groups in a sub-frame.
[132] [Math Figure 1]
[133]
[ 134] Herein, j indicates the slot number within a sub-frame. The value of j may range from

0 to 15 (i.e.,.,

). Also, variable i indicates the data group number. The value of i may range from 0 to
15 (i.e.,

)•
[135] 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.
[136] 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 A/B and
regions C/D. If the mobile service data are assigned to the latter case (i.e., one of
regions A/B 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.
[137] 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.
[138] Table 1 below shows an example of the RS frame mode.
[139] Table 1


[140] 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 A/B
are assigned and transmitted to regions A/B 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.
[141] 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.
[ 142] 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.
[ 143] FIG. 9 illustrates an example of multiple data groups of a single parade being
assigned (or allocated) to an MH frame. More specifically, FIG. 9 illustrates an
example of a plurality of data groups included in a single parade, wherein the number
of data groups included in a sub-frame is equal to '3', being allocated to an MH frame.
[144] Referring to FIG. 9. 3 data groups are sequentially assigned to a sub-frame at a cycle
period of 4 slots. Accordingly, when this process is equally performed in the 5 sub-

frames included in the corresponding MH frame, 15 data groups are assigned to a
single MH frame. Herein, the 15 data groups correspond to data groups included in a
parade. Therefore, since one sub-frame is configured of 4 VSB frame, and since 3 data
groups are included in a sub-frame, the data group of the corresponding parade is not
assigned to one of the 4 VSB frames within a sub-frame.
[145] 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)x100) 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 FIG. 9, a total of 15 data groups form
an RS frame. Accordingly, even when an error occurs in an entire data group due to a
burst noise within a channel, the percentile is merely 6.67% (=1/15x100). Therefore,
the receiving system may correct all errors by performing an erasure RS decoding
process. More specifically, when the erasure RS decoding is performed, a number of
channel errors corresponding to the number of RS parity bytes may be corrected. By
doing so, the receiving system may correct the error of at least one data group within
one parade. Thus, the minimum burst noise length correctable by a RS frame is over 1
VSB frame.
[146] Meanwhile, when data groups of a parade are assigned as shown in FIG. 9, either
main service data may be assigned between each data group, or data groups cor-
responding to different parades may be assigned between each data group. More
specifically, data groups corresponding to multiple parades may be assigned to one
MH frame.
[147] 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.
[148] 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.
[149] For example, when it is assumed that data groups corresponding to a parade are
assigned as shown in FIG. 9, data groups corresponding to the next parade may be
assigned to a sub-frame starting either from the 12th slot of a sub-frame. However, this
is merely exemplary. In another example, the data groups of the next parade may also
be sequentially assigned to a different slot within a sub-frame at a cycle period of 4

slots starting from the 3rd slot.
[ 150] FIG. 10 illustrates an example of transmitting 3 parades (Parade #0, Parade #1, and
Parade #2) to an MH frame. More specifically, FIG. 10 illustrates an example of
transmitting parades included in one of 5 sub-frames, wherein the 5 sub-frames
configure one MH frame.
[ 151] 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.
[152] 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 #1 and Slot #11)
within the sub-frame.
f 153] 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.
[154] 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.
[155] Therefore, a number of groups of one parade per sub-frame (NoG) may correspond
to any one integer from T 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'.
[156] FIG. 11 illustrates an example of expanding the assignment process of 3 parades,
shown in FIG. 10, to 5 sub-frames within an MH frame.
[157] FIG. 12 illustrates a data transmission structure according to an embodiment of the
present invention, wherein signaling data are included in a data group so as to be
transmitted.
[ 158] As described above, an MH frame is divided into 5 sub-frames. Data groups cor-
responding 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.
[ 159| The data structure shown in FIG. 12 includes 3 parades, one ESG dedicated channel
(EDC) parade (i.e.. parade with NoG=1), and 2 service parades (i.e.. parade with

NoG=4 and parade with NoG=3). Also, a predetermined portion of each data group
(i.e., 37 bytes/data group) is used for delivering (or sending) FIC information
associated with mobile service data, wherein the FIC information is separately encoded
from the RS-encoding process. The FIC region assigned to each data group consists of
one FIC segments. Herein, each segment is interleaved by MH sub-frame units,
thereby configuring an FIC body, which corresponds to a completed FIC transmission
structure. However, whenever required, each segment may be interleaved by MH
frame units and not by MH sub-frame units, thereby being completed in MH frame
units.
[160] 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.
[161] As shown in FIG. 12, the FIC segment corresponding to each data group described
service information of an MH ensemble to which the corresponding data group
belongs. When FIC segments within a sub-frame are grouped and deinterleaved, all
service information of a physical channel through which the corresponding FICs are
transmitted may be obtained. Therefore, the receiving system may be able to acquire
the channel information of the corresponding physical channel, after being processed
with physical channel tuning, during a sub-frame period.
[162] Furthermore, FIG. 12 illustrates a structure further including a separate EDC parade
apart from the service parade and wherein electronic service guide (ESG) data are
transmitted in the 1st slot of each sub-frame.
[163]
[164] Hierarchical Signaling Structure
[165] FIG. 13 illustrates a hierarchical signaling structure according to an embodiment of
the present invention. As shown in FIG. 13, the mobile broadcasting technology
according to the embodiment of the present invention adopts a signaling method using
FIC and SMT. In the description of the present invention, the signaling structure will
be referred to as a hierarchical signaling structure.
[166] Hereinafter, a detailed description on how the receiving system accesses a virtual
channel via FIC and SMT will now be given with reference to FIG. 13. Herein, the
SMT corresponds to one of multiple signaling tables being received through the IP
signaling channel of the corresponding RS frame.
[ 167] 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.

[168] 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 in-
formation required for the virtual channel service acquisition.
[169] Referring to FIG. 13, each MH ensemble (i.e., Ensemble 0, Ensemble 1,...,
Ensemble K) includes a stream information on each associated (or corresponding)
virtual channel (e.g., virtual channel 0 IP stream, virtual channel 1 IP stream, and
virtual channel 2 IP stream). For example, Ensemble 0 includes virtual channel 0 IP
stream and virtual channel 1 IP stream. And, each MH ensemble includes diverse in-
formation on the associated virtual channel (i.e., Virtual Channel 0 Table Entry,
Virtual Channel 0 Access Info, Virtual Channel 1 Table Entry, Virtual Channel 1
Access Info, Virtual Channel 2 Table Entry, Virtual Channel 2 Access Info, Virtual
Channel N Table Entry, Virtual Channel N Access Info, and so on).
[170] The FIC body payload includes information on MH ensembles (e.g., ensemble_id
field, and referred to as "ensemble location" in FIG. 13) and information on a virtual
channel associated with the corresponding MH ensemble (e.g., when such information
corresponds to a major_channel_num field and a minor_channel_num field, the in-
formation is expressed as Virtual Channel 0, Virtual Channel 1,..., Virtual Channel N
in FIG. 13).
[171] The application of the signaling structure in the receiving system will now be
described in detail.
[172] 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 cor-
responding 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.
[1731

[174] Fast Information Channel (FIC)
[175] 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.
[176] More specifically, the FIC handler 215 of FIG. 1 parses the FIC body, which
corresponds to an FIC transmission structure, and outputs the parsed result to the
physical adaptation control signal handler 216.
[177] FIG. 14 illustrates an exemplary FIC body format according to an embodiment of the
present invention. According to the embodiment of the present invention, the FIC
format consists of an FIC body header and an FIC body payload.
[178] 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.
[ 179] 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.
[180] The signaling decoder 190 included in the receiving system shown in FIG. 1 collects
each FIC segment inserted in each data group. Then, the signaling decoder 190 uses
the collected FIC segments to created a single FIC body. Thereafter, the signaling
decoder 190 performs a decoding process on the FIC body payload of the created FIC
body, so that the decoded FIC body payload corresponds to an encoded result of a
signaling encoder (not shown) included in the transmitting system. Subsequently, the
decoded FIC body payload is outputted to the FIC handler 215. The FIC handler 215
parses the FIC data included in the FIC body payload, and then outputs the parsed FIC
data to the physical adaptation control signal handler 216. The physical adaptation
control signal handler 216 uses the inputted FIC data to perform processes associated
with MH ensembles, virtual channels, SMTs, and so on.
[181] 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.
[182] 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.
[ 183] FIG. 15 illustrates an exemplary bit stream syntax structure with respect to an FIC
segment according to an embodiment of the present invention.
[184] 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
FIG. 15, the FIC segment payload corresponds to the portion starting from the 'for'
loop statement. Meanwhile, the FIC segment header may include a FIC_type field, an
error_indicator field, an FIC_seg_number field, and an FIC_last_seg_number field. A
detailed description of each field will now be given.
[ 185] The FIC_type field is a 2-bit field indicating the type of the corresponding FIC.
[186] 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.
[187] 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.
[188] 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.
[189] FIG. 16 illustrates an exemplary bit stream syntax structure with respect to a payload
of an FIC segment according to the present invention, when an FIC type field value is
equal to '0'.
[190] According to the embodiment of the present invention, the payload of the FIC
segment is divided into 3 different regions.
[191 ] 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.
[192] The current_next_indicator field is a 1-bit field. The current_next_indicator field acts
as an indicator identifying whether the corresponding FTC 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.
[ 193] 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 cor-
responding ESG, the ESG_version field enables the receiving system to notify whether
or not the corresponding ESG has been updated.
[194] Finally, the transportstream_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.
[195] A second region of the FIC segment payload corresponds to an ensemble loop
region, which includes an ensemble_id field, an SI_version field, and a num_channel
field.
[196] 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.
[ 197] 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.
[198] Finally, the num_channel field is an 8-bit field indicating the number of virtual
channel being transmitted via the corresponding ensemble.
[199] 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.
[200] 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.
[201] The channel_activity field is a 2-bit field indicating activity information of the cor-
responding virtual channel. More specifically, the channel_activity field may indicate
whether the current virtual channel is providing the current service.
[202] The CA_indicator field is a 1-bit field indicating whether or not a conditional access
(CA) is applied to the current virtual channel.
[203] 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.
[204] The major_channel_num field is an 8-bit field indicating a major channel number of
the corresponding virtual channel.
[205] Finally, the minor_channel_num field is also an 8-bit field indicating a minor
channel number of the corresponding virtual channel.

[206]
[207] Service Table Map
[208] FIG. 17 illustrates an exemplary bit stream syntax structure of a service map table
(hereinafter referred to as "SMT") according to the present invention.
[209] 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.
[210] 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.
[211] As described in FIG. 3, the SMT section may be transmitted by being included in the
MH TP within the RS frame. In this case, each of the RS frame decoders 170 and 180,
shown in FIG. 1, decodes the inputted RS frame, respectively. Then, each of the
decoded RS frames is outputted to the respective RS frame handler 211 and 212.
Thereafter, each RS frame handler 211 and 212 identifies the inputted RS frame by
row units, so as to create an MH TP, thereby outputting the created MH TP to the MH
TP handler 213.
[212] 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 parses the cor-
responding SMT section, so as to output the SI data within the parsed SMT section to
the physical adaptation control signal handler 216. However, this is limited to when the
SMT is not encapsulated to IP datagrams.
[213] Meanwhile, when the SMT is 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.
[214] The following corresponds to example of the fields that may be transmitted through
the SMT.
[215] A 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).
[216] An 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).
[217] A num_channels field is an 8-bit field, which specifies the number of virtual
channels in the corresponding SMT section.
[218] Meanwhile, the SMT according to the embodiment of the present invention provides
information on a plurality of virtual channels using the 'for' loop statement.
[219] A 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
'OxFF'.
[220] A 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
'OxFF'.
[221] A 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.
[222] A 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.
[223] Table 2


[224] A 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.
[225] A num_components field is a 5-bit field, which specifies the number of IP stream
components in the corresponding virtual channel.
[226] An 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_fP_address
field are IPv4.
[227] A source_rP_address_fIag 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.
[228| A 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.
[229] 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 in-
significant (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 T, the source_IP_address field indicates a 128-bit IPv6 address, which shows
the source of the corresponding virtual channel.
[230] 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.
[231 ] 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.
[232] Herein, an 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).

[233] Table 3 below shows an example of the RTP_payload_type.
[234] Table 3

[235] A 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 cor-
responding IP stream component. Accordingly, the receiving system (or receiver) will
ignore the virtual_channel_target_IP_address field included in the num_channels loop.
[236] 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.
[237] A 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 in-
cremented) 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.
[238] A 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.
[239] A component_level_descriptoi-() represents zero or more descriptors providing
additional information on the corresponding IP stream component.
[240] A virtual_channel_level_descriptor() represents zero or more descriptors providing

additional information for the corresponding virtual channel.
[241] An ensemble_level_descriptor() represents zero or more descriptors providing
additional information for the MH ensemble, which is described by the corresponding
SMT.
[242] FIG. 18 illustrates an exemplary bit stream syntax structure of an MH audio
descriptor according to the present invention.
[243] When at least one audio service is present as a component of the current event, the
MH_audio_descriptor() shall be used as a componerit_level_descriptor of the SMT.
The MH_audio_descriptor() may be capable of informing the system of the audio
language type and stereo mode status. If there is no audio service associated with the
current event, then it is preferable that the MH_audio_descriptor() is considered to be
insignificant (or absent) for the current event.
[244] Each field shown in the bit stream syntax of FIG. 18 will now be described in detail.
[245] A descriptor_tag field is an 8-bit unsigned integer having a TBD value, which
indicates that the corresponding descriptor is the MH_audio_descriptor().
[246] A descnptor_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().
[247] A 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.
[248] A 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.
[249] A 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.
[250] An lSO_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'.
[251] FIG. 19 illustrates an exemplary bit stream syntax structure of an MH RTP payload
type descriptor according to the present invention.

[252] 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.
[253] 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.
[254] The fields included in the MH_RTP_payload_type_descriptor() will now be
described in detail.
[255] A 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().
[256] A 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().
[257] An 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'.
[258] A MIME_type_length field specifies the length (in bytes) of a MIME_type field.
[259] 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().
[260] FIG. 20 illustrates an exemplary bit stream syntax structure of an MH current event
descriptor according to the present invention.
[261] 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.
[262] The fields included in the MH__current_event_descriptor() will now be described in
detail.
[263] A 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().
[264] A descriptor_lcngth 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_cvent_descriptor().

[265] A 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, January 6,
1980.
[266] A 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).
[267] A title_length field specifies the length (in bytes) of a title_text field. Herein, the
value '0' indicates that there are no titles existing for the corresponding event.
[268] 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].
[269] FIG. 21 illustrates an exemplary bit stream syntax structure of an MH next event
descriptor according to the present invention.
[270] 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.
[271] The fields included in the MH_next_event_descriptor() will now be described in
detail.
[272] A 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().
[273] A 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().
[274] A 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, January 6, 1980.
[275] A 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).
[276] A titlejength field specifies the length (in bytes) of a title_text field. Herein, the
value '0' indicates that there are no titles existing for the corresponding event.
[277] 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].
[278] FIG. 22 illustrates an exemplary bit stream syntax structure of an MH system time
descriptor according to the present invention.
[279] The MH_system_time_dcscriptor() 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 c or-
responding broadcast stream is located, while taking into consideration the mobile/
portable characteristics of the MH service data.
[280] The fields included in the MH_system_time_descriptor() will now be described in
detail.
[281] A 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().
[282] A descriptor_length field also corresponds to an 8-bit unsigned integer, which
indicates the length (in bytes) of the portion immediately following the descr
iptor_length field up to the end of the MH_system_time_descriptor().
[283] A 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, January 6, 1980.
[284] A 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). Ac-
cordingly, the GPS_UTC_offset field value will reflect the change.
[285] A 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, a time_zone_offset 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 field
value is subtracted from the UTC time value.
[286] 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.
[287] A daylight_savings field corresponds to a 16-bit field providing information on the
Summer Time (i.e., the Daylight Savings Time).
[288] A time_zone field corresponds to a (5x8)-bit field indicating the time zone, in which
the transmitting system (or transmitter) transmitting the corresponding broadcast
stream is located.

[289] FIG. 23 illustrates segmentation and encapsulation processes of a service map table
(SMT) according to the present invention.
[290] 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.
[291] 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.
[292] 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.
[293] FIG. 24 illustrates a flow chart for accessing a virtual channel using FIC and SMT
according to the present invention.
[294] 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 de-
modulated MH signal in sub-frame units (S504 and S505).
[295] 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 cor-
responding 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 FTC body, which is
configured by grouping the FIC segments.
[296] 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).

[297] Subsequently, the RS frame corresponding to the designated ensemble is decoded
(S509), and an IP socket is opened for SMT reception (S510).
[298] 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).
[299] 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 cor-
responding MH ensemble. Also, each SMT section is identified by an ensemble_id
included in each section.
[300] 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 cor-
responding virtual channel.
[301] 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). Ac-
cordingly, the service associated with the corresponding virtual channel is provided to
the user (S514).
[302] Meanwhile, the present invention enables signaling tables describing signaling in-
formation required for a service access using the IP signaling channel to be
transmitted.
[303] More specifically, an IP stream having a well-known IP address and a well-known
port number is assigned to an ensemble. In the description of the present invention, this
will be referred to as the IP signaling channel.
[304] The IP signaling channel transmits at least one signaling table. According to an
embodiment of the present invention, at least one signaling table, such as a service map
table (SMT), a system time table (STT), a rating region table (RRT), a guide access
table (GAT), future event table (FET), and a cell information table (CIT), is
transmitted through the IP signaling channel. Herein, the signaling tables presented in
the embodiment of the present invention are merely examples for facilitating the un-
derstanding of the present invention. Therefore, the present invention is not limited
only to the exemplary signaling tables that can be transmitted through the IP signaling
channel.

[305] The SMT provides signaling information on ensemble levels. Also, each SMT
provides IP access information for each virtual channel belonging to the corresponding
ensemble including each SMT. Furthermore, the SMT provides IP stream component
level information required for services of the corresponding virtual channel.
[306] The STT transmits information on the current data and timing information.
Meanwhile, when the digital broadcast receiving system is used in mobile conditions
and in extended regions, such as North America, the position of the receiving system
may deviate outside of the time zone. The STT may be used to notify such deviation.
[307] The RRT transmits information on region and consultation organs for program
ratings. More specifically, the RRT provides content advisory rating information.
[308] The GAT provides service guide (SG) acquisition information. And, the GAT
provides information of SG providers transmitting SGs through the corresponding MH
ensemble transmitting the GAT.
[309] The FET provides information associated with an event for a future usage. More
specifically, the FET is optional and provides information on future event transmitted
through virtual channel included in the corresponding MH ensemble transmitting the
FET.
[310] The CIT provides channel information of each cell, which corresponds to the
frequency domain of a broadcast signal. Herein, a cell refers to a scope affected (or
influenced) by a transmitter based upon a physical frequency in a multi-frequency
network (MFN) environment (or condition). More specifically, the CIT provides in-
formation on a carrier wave frequency of an adjacent cell in the current transmitter (or
transmitting system). Therefore, based upon the CIT information, a receiver (or
receiving system) can travel from one transmitter's (or exciter's) coverage area to
another.
[311] The present invention encapsulates each signaling table to a UDP header and en-
capsulates the UDP-encapsulated signaling table to an IP header. Therefore, the
processed signaling table may be transmitted through the IP signaling channel. In this
case, a number of UDP/IP packets corresponding to the number of signaling tables
transmitted through the IP signaling channel are also transmitted through the IP
signaling channel.
[312] Also, the present invention identifies (or distinguishes) each signaling table to at least
one transmission unit. Thereafter, each transmission unit is encapsulated to a UDP
header and then encapsulated to an IP header, thereby being transmitted through the IP
signaling channel.
[313] Herein, the transmission unit may correspond to a section. And, a single signaling
table may be divided into a plurality of section, wherein each section may be used as
the transmission unit.

[314] According to an embodiment of the present invention, each signaling table is divided
into at least one section. Then, each section is encapsulated to a UDP/IP header,
thereby being transmitted through the IP signaling channel. In this case, the number of
UDP/IP packets being transmitted through the IP signaling channel may vary based
upon the number of signaling tables being transmitted through the IP signaling channel
and the number of sections in each signaling table. At this point, all UDP/IP packets
transmitted through the IP signaling channel have the same number of well-known
target IP addresses and well-known target UDP port numbers. For example, when it is
assumed that the SMT, RRT, and STT are transmitted through the IP signaling
channel, the target IP address and target UDP port number of all UDP/IP packets
transmitting the SMT, RRT, and STT are identical to one another. Furthermore, the
target IP address and the target UDP port number respectively correspond to well-
known values, i.e., values pre-known by the receiving system based upon an agreement
between the receiving system and the transmitting system. Therefore, each signaling
table received through the IP signaling channel is distinguished (or identified) by a
table identifier (e.g., table_id, table_id_extension).
[315] The IP signaling channel may be assigned (or allocated) to at least one MH TP
within an RS frame corresponding to the respective ensemble. More specifically, based
upon the amount of data being transmitted through the IP signaling channel, each
signaling table may either be assigned to a single MH TP and then transmitted, or be
assigned to a plurality of MH TP and then transmitted. Additionally, the IP signaling
channel may be transmitted through at least one of a primary RS frame and a
secondary RS frame. Herein, the RS frame may be divided into a primary RS frame
and a secondary RS frame. In this case, the primary RS frame and the secondary RS
frame may be divided based upon the level of importance of the corresponding data.
[316] 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". Also, one ensemble
corresponds to one RS frame. More specifically, a primary ensemble corresponds to
the primary RS frame, and a secondary ensemble corresponds to the secondary RS
frame. Therefore, based upon the level of importance of the corresponding signaling
table, the IP signaling channel according to the embodiment of the present invention
may be assigned to the primary RS frame only, to the secondary RS frame only, or to
both primary and secondary RS frames.
[317] FIG. 25 illustrates an exemplary structure of an IP signaling channel according to an
embodiment of the present invention. Most particularly. FIG. 25 illustrates an IP
signaling channel structure in an RS frame corresponding to MH ensemble K. The IP

daylight_savings field is used for the consideration of a particular time period in the
Republic of Korea during which a daylight saving time referred to as "summer time" is
adopted. The time_zone_offset_polarity field indicates whether the time of the time
zone, in which the transmitting system is located, is faster or later than the UTC time.
The time_zone_offset field indicates a time offset of the time zone, in which the
transmitting system is located. The STT section may further include a descriptor
describing additional information associated with the STT.
[321] FIG. 27 illustrates an exemplary syntax structure of an RRT section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention. Referring to FIG. 27, an identifier identifying the RRT may be set as the
table_id field, which corresponds to the table identifier. Herein, the
section_syntax_indicator field corresponds to an indicator defining an RRT section
format. The private_indicator field indicates to which private section the RRT belongs.
The section_length field indicates the section length of the RRT. The version_number
field indicates the version number of the RRT. The section_number field indicates the
section number of the current RRT section. The last_section_number field indicates the
last section number of the RRT.
[322] The rating_region_name_length field indicates the total length of the
rating_region_name_text() field that follows. The rating_region_name_text() field
indicates, in a multiple string structure, a rating region name of a broadcast program.
The dimensions_defined field signifies the number of dimensions defined in the
current RRT section. The dimension_name_length field indicates the total length of the
dimension_name_text() field that follows. The dimension_name_text() field indicates,
in a multiple string structure, a dimension name described in a loop statement. The
graduated_scale field indicates whether or not the corresponding dimension carries a
graduated scale having a changed rating value.
[323] The values_defined field indicates the number of values defined in the corresponding
dimension. The abbrev_rating_value_length field indicates the total length of the
abbrev_rating_value_text() field that follows. The abbrev_rating_value_text() field
indicates in a multiple string structure an abbreviated name of a specific rating value.
The rating_value_length field indicates the total length of the rating_value_text() that
follows. The rating_value_text() field indicates the full name of a specific rating value
in a multiple string structure. The RRT section may further include a descriptor
describing additional information associated with the RRT.
[324] FIG. 28 illustrates an exemplary syntax structure of a CTT section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention. Referring to FIG. 28. an identifier identifying the CIT may be set as the
table_id field, which corresponds to the table identifier. Herein, the

section_syntax_indicator field corresponds to an indicator defining a CIT section
format. The private_indicator field indicates to which private section the CIT belongs.
The section_length field indicates the section length of the CIT. The version_number
field indicates the version number of the CIT. The section_number field indicates the
section number of the current CIT section. The last_section_number field indicates the
last section number of the CIT.
[325] The num_cells_in_section field corresponds to a number of cells defined in the CIT.
Herein, the number of cells defined in the CIT may be identical to the number of
transmitters (or transmitting systems). A broadcasting station may define information
on all transmitters transmitting a broadcast program in the CIT. The cell_id field
corresponds to an identifier identifying (or distinguishing) a cell according to a signal
transmitting region (or area) for each transmitter. Herein, each cell may match with the
transmitter of each broadcasting station. The num_channels_in_cell field indicates a
number of broadcast channels transmitted by each transmitter. The
num_channels_in_cell field may also correspond to a total number of virtual channels
with respect to a physical channel transmitted by each transmitter. The CIT section
may include a major_channel_number field, a minor_channel_number, a
carrier_frequency field, and a descriptor field based upon the value of each
num_channels_in_cell field.
[326] FIG. 29 illustrates an exemplary syntax structure of a GAT section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention. Referring to FIG. 29, an identifier identifying the GAT may be set as the
table_id field, which corresponds to the table identifier. Herein, the GAT of FIG. 29
assigns an 8-bit ensemble_id field and an 8-bit GAT_protocol_version field to the
position of the table_id_extension field, so that the newly assigned fields may be used
as one of the table identifiers for identifying the GAT, when the GAT is received
through the IP signaling channel. As shown in FIG. 29, the section_syntax_indicator
field corresponds to an indicator defining a GAT section format. The private_indicator
field indicates to which private section the GAT belongs. The sectionjength field
indicates the section length of the GAT.
[327] The ensemble_id field is an 8-bit 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), 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). The GAT_protocol_version field indicates
the protocol version of the corresponding GAT.
[328] The version_number field indicates the version number of the GAT. The section_nu
mber field indicates the section number of the current GAT section. The
last_section_number field indicates the last section number of the GAT. The
num_SG_provides field indicates a number of SG providers described in the current
GAT section. The SG_provider_id field indicates a unique indicator that can identify
each SG provider. The SG_provider_name_length field indicates the total length of the
SG_provider_name_text() field that follows. The SG_provider_name_text() field
indicates the name of the corresponding SG provider. The source_IP_address field
indicates a source IP address of a FLUTE session, which transmits (or delivers) an SG
entry point. The SG_entry_target_IP_address field indicates a target IP multicast
address of a FLUTE session, which transmits an SG entry point. The
SG_entry_target_UDP_port_num field indicates a designated UDP port number with
respect to a corresponding IP stream, which transmits an SG entry point. The TSI field
indicates a transport session identifier (TSI) of a FLUTE session, through which an SG
entry is transmitted.
[329] FIG. 30 illustrates an exemplary syntax structure of an FET section among multiple
signaling tables transmitted to the IP signaling channel according to the present
invention. Referring to FIG. 30, an identifier identifying the FET may be set as the
table_id field, which corresponds to the table identifier. Herein, the FET of FIG. 30
assigns an 8-bit ensemble_id field and an 8-bit FET_protocol_version field to the
position of the table_id_extension field, so that the newly assigned fields may be used
as one of the table identifiers for identifying the FET, when the FET is received
through the IP signaling channel. As shown in FIG. 30, the section_syntax_indicator
field corresponds to an indicator defining an FET section format. The private_indicator
field indicates to which private section the FET belongs. The section_length field
indicates the section length of the FET.
[330] The ensemble_id field is an 8-bit 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), 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). The FET_protocol_version field indicates
the protocol version of the corresponding FET.
[331] The version_number field indicates the version number of the FET. The
section_number field indicates the section number of the current FET section. The
last_section_number field indicates the last section number of the FET. The
num_channels field indicates a number of virtual channels described in the current
FET section. The service_id field corresponds to an identifier identifying a virtual
channel, which transmits events described in the corresponding FET section. The
num_events_in_channel field indicates a number of events on a virtual channel
described in the corresponding FET section. Herein, when the value of the
num_events_in_channel field is equal to '0', an event described in the corresponding
FET section does not exist. The MH_event_id field corresponds to an identifier that
can identify a corresponding event. The future_event_start_time field indicates the
starting time of a future event. The future_event_duration field indicates the duration
time of the future event. The title_length field indicates the total length of the
title_text() field that follows. The title_text() field indicates the title of a coreesponding
event. The FET section may further include a descriptor describing additional in-
formation associated with the FET.
[332] As described above, when not only the table_id field but also table_id_extension
field are used as table identifiers for identifying the signaling tables, each signaling
table may further include the table_id_extension field. Herein, the table_id_extension
field may be assigned with 16 bits. And, it is preferable that the table_id_extension
field is positioned after the section_length field in each signaling table. In this case, the
value of the table_id_extension field may indicate an ensemble identifier (i.e., an 8-bit
ensemble_id field) and a protocol version (i.e., an 8-bit protocol_version field) of each
signaling table, as shown in FIG. 29 and FIG. 30.
[333J Hereinafter, a process of receiving and accessing an IP signaling channel according
to the present invention will be described in detail. More specifically, in the digital
broadcast receiving system of FIG. 1, each of the RS frame decoders 170 and 180 re-
spectively decodes the inputted RS frames. Then, the decoded RS frames are outputted
to the respective RS frame handlers 211 and 212. Subsequently, each RS frame handler
211 and 212 divides the inputted RS frame in row units so as to configure an MH TP,
respectively. Thereafter, the MH TPs are outputted to the MH-TP handler 213. The
MH-TP handler 213 extracts a header from each MH TP received from the RS frame

handlers 211 and 212, respectively. Then, the MH-TP handler 213 determines the data
included in the corresponding MH TP. Accordingly, if the determined data correspond
to an IP datagram, the corresponding data are outputted to the IP network stack 220.
[334] At this point, since the IP signaling channel includes a well-known target IP address
and a well-known target UDP port number, the IP network stack 220 is already
informed of the target IP address and target UDP port number of the IP signaling
channel. Therefore, the IP network stack 220 accesses the IP signaling channel without
requesting for any separate information, thereby collecting IP datagrams that are
received through the IP signaling channel. Then, the IP network stack 220 removes IP
headers and UDP headers from the collected IP datagrams and, then, outputs the
processed IP datagrams to the SI handler 240. The SI handler 240 may use table
identifiers to distinguish (or identify) each signaling table or each signaling table
section. Also, the SI handler 240 collects sections having the same table identifier so as
to complete the corresponding signaling table. Thereafter, the SI handler 240 parses the
completed signaling table and stores the processed result to the storage unit 290.
Herein, the SI handler 240 may either perform the parsing process in signaling table
units, or perform the parsing process in signaling table section units.
[335] FIG. 31 illustrates a flow chart showing an IP signaling processing method according
to the present invention. More specifically, the IP network stack 220 opens an IP
socket in order to receive the IP signaling channel (S701). According to an
embodiment of the present invention, a plurality of signaling tables transmitted through
the IP signaling channel, the tables each carrying a target IP address and a target UDP
port number on an IP datagram, is encapsulated to IP/UDP. At this point, each UDP/IP
packet being transmitted to the IP signaling channel has the same well-known target IP
address and well-known target UDP port number. For example, when it is assumed
that the SMT, RRT, and STT are transmitted through the IP signaling channel, all
UDP/IP packets respectively transmitting the SMT, RRT, and STT have the same
target IP address and target UDP port number. Also, each of the target IP address and
target UDP port number is respectively assigned with a well-known value (i.e., a value
pre-known by the digital broadcast receiving system based upon an agreement between
the receiving system and the transmitting system).
[336] When IP socket is open in step 701, TP datagrams transmitted through the IP
signaling channel are collected (S702). At this point, since the IP signaling channel
includes a well-known target IP address and a well-known target UDP port number,
the IP network stack 220 is already informed of the target IP address and target UDP
port number of the IP signaling channel. Therefore, the IP network stack 220 accesses
the IP signaling channel without requesting for any separate information, thereby
collecting IP datagrams (i.e.. signaling table information) that are received through the

IP signaling channel. Subsequently, by identifying the collected signaling table in-
formation using each table identifier, each signaling table or each signaling table
section is recovered (S703). Thereafter, each of the recovered signaling tables or
signaling table sections is parsed. And, the parsed result is either stored in the storage
unit 290 or outputted to the block requiring the parsed result (S704).
[337] As described above, the digital broadcasting system and the data processing method
according to the present invention have the following advantages. The present
invention assigns an IP signaling channel having a well-known target IP address and a
well-known target UDP port number to each ensemble. Then, the present invention
transmits a signaling table describing information required for service access through
the IP signaling channel. Therefore, after configuring the ensembles, the digital
broadcast receiving system according to the present invention opens an IP socket for
an IP stream having the corresponding well-known target IP address and well-known
target UDP port number. More specifically, the digital broadcast receiving system may
access the IP signaling channel without requesting for any separate information.
Furthermore, by using a table identifier included in a header of each signaling table,
the digital broadcast receiving system according to the present invention can find (or
locate) a desired signaling table from the corresponding IP stream.
[338] 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.
Mode for the Invention
[339] Meanwhile, the mode for the embodiment of the present invention is described
together with the 'best Mode' description.
Industrial Applicability
[340] The embodiments of the method for transmitting and receiving signals and the
apparatus for transmitting and receiving signals according to the present invention can
be used in the fields of broadcasting and communication.

WE CLAIM :
1. A method of transmitting a broadcast signal, the method comprising:
multiplexing mobile data and main data; and
transmitting a transmission frame including the multiplexed mobile data
and main data,
wherein a parade of data groups is transmitted during slots within the
transmission frame, the slots being time periods for multiplexing of the mobile
data and the main data,
wherein each data group includes the mobile data, signaling information
and regularly spaced know data sequences,
wherein the signaling information includes fast information channel (FIC)
data having binding information between a service of the mobile data and an
ensemble, and transmission parameter channel (TPC) data having a version of
the FIC data,
wherein the FIC data is divided to a plurality of FIC segments, and each
FIC segment including an FIC segment header is transmitted in each of the
data groups,
wherein the ensemble includes the service, and a signaling table
describing the service,
wherein the service signaling table includes a guide access table (GAT)
having information about a service guide provider for a service guide data
source and access information for the service guide data source, and
wherein the ensemble is RS-CRC (cyclic redundancy check) encoded
through a Reed-Solomon (RS) frame which is 2-dimensional data frame; and a
row of a payload of the RS frame includes a transport packet of the mobile data.
2. The method of claim 1, wherein the signaling table is identified from
a different signaling table by using a table_id field and a table_id_extension field
in a table section header of the signaling table.
3. The method of claim 1, wherein the transport packet includes an
internet protocol (IP) datagram .
4. The method of claim 3, wherein the IP datagram includes the
signaling table.

5. The method of claim 4, wherein the IP datagram including the
signaling table has a well-known target IP address and well-known target UDP
port number.
6. A method of receiving a broadcast signal, the method comprising:
receiving a broadcast signal including a transmission frame, wherein a
parade of data groups is received during slots within the transmission frame, the
slots being time periods for multiplexing of mobile data and main data, and
wherein each data group includes the mobile data, signaling information
and regularly spaced know data sequences,
demodulating the broadcast signal and obtaining, from the signaling
information, fast information channel (FIC) data including binding information
between a service of the mobile data and an ensemble, and transmission
parameter channel (TPC) data having a version of the FIC data,
wherein the FIC data is divided to a plurality of FIC segments, and each
FIC segment including an FIC segment header is received in each of the data
groups,
wherein the ensemble includes the service and a signaling table
describing the service, and
wherein the service signaling table includes a guide access table (GAT)
having information about a service guide provider for a service guide data
source and access information for the service guide data source;
building a Reed-Solomon (RS) frame corresponding to the ensemble by
collecting a plurality of data portions to which the data groups are mapped,
wherein the RS frame is 2-dimensional data frame through which the
ensemble is RS-CRC (cyclic redundancy check) encoded, and a row of a
payload of the RS frame including a transport packet of the mobile data; and
decoding the built RS frame.
7. The method of claim 6, wherein the signaling table is identified from a
different signaling table by using a tablejd field and a table_id_extension field
in a table section header of the signaling table.
8. The method of claim 6, wherein the transport packet includes an
internet protocol (IP) datagram .

9. The method of claim 8, wherein the IP datagram includes the
signaling table.
10. The method of claim 9, wherein the IP datagram including the
signaling table has a well-known target IP address and well-known target UDP
port number.
11. An apparatus for transmitting a broadcast signal, the apparatus
comprising:
a multiplexer configured to multiplex mobile data and main data; and
a transmitter configured to transmit a transmission frame including the
multiplexed mobile data and main data,
wherein a parade of data groups is transmitted during slots within the
transmission frame, the slots being time periods for multiplexing of the mobile
data and the main data,
wherein each data group includes the mobile data, signaling information
and regularly spaced know data sequences,
wherein the signaling information includes fast information channel (FIC)
data having binding information between a service of the mobile data and an
ensemble, and transmission parameter channel (TPC) data having a version of
the FIC data,
wherein the FIC data is divided to a plurality of FIC segments, and each
FIC segment including an FIC segment header is transmitted in each of the
data groups,
wherein the ensemble includes the service, and a signaling table
describing the service,
wherein the service signaling table includes a guide access table (GAT)
having information about a service guide provider for a service guide data
source and access information for the service guide data source, and
wherein the ensemble is RS-CRC (cyclic redundancy check) encoded
through a Reed-Solomon (RS) frame which is 2-dimensional data frame; and a
row of a payload of the RS frame includes a transport packet of the mobile data.

12. The apparatus of claim 11, wherein the signaling table is identified
from a different signaling table by using a table_id field and a
table_id_extension field in a table section header of the signaling table.
13. The apparatus of claim 11, wherein the transport packet includes an
internet protocol (IP) datagram .
14. The apparatus of claim 13, wherein the IP datagram includes the
signaling table.
15. The apparatus of claim 14, wherein the IP datagram including the
signaling table has a well-known target IP address and well-known target UDP
port number.
16. An apparatus for receiving a broadcast signal, the apparatus
comprising:
a receiver configured to receive a broadcast signal including a
transmission frame, wherein a parade of data groups is received during slots
within the transmission frame, the slots being time periods for multiplexing of
mobile data and main data, and
wherein each data group includes the mobile data, signaling information
and regularly spaced know data sequences,
a demodulator configured to demodulate the broadcast signal and
obtaining, from the signaling information, fast information channel (FIC) data
including binding information between a service of the mobile data and an
ensemble, and transmission parameter channel (TPC) data having a version of
the FIC data,
wherein the FIC data is divided to a plurality of FIC segments, and each
FIC segment including an FIC segment header is received in each of the data
groups, and
wherein the ensemble includes the service and a signaling table
describing the service,
wherein the service signaling table includes a guide access table (GAT)
having information about a service guide provider for a service guide data
source and access information for the service guide data source; and
an RS frame decoder configured to build a Reed-Solomon (RS) frame

corresponding to the ensemble by collecting a plurality of data portions to which
the data groups are mapped, and decode the built RS frame,
wherein the RS frame is 2-dimensional data frame through which the
ensemble is RS-CRC (cyclic redundancy check) encoded, and a row of a
payload of the RS frame including a transport packet of the mobile data.
17. The apparatus of claim 16, wherein the signaling table is identified
from a different signaling table by using a table_id field and a
table_id_extension field in a table section header of the signaling table.
18. The apparatus of claim 16, wherein the transport packet includes an
internet protocol (IP) datagram .
19. The apparatus of claim 18, wherein the IP datagram includes the
signaling table.
20. The apparatus of claim 19, wherein the IP datagram including the
signaling table has a well-known target IP address and well-known target UDP
port number.


A digital broadcasting system and a data processing method are disclosed. A receiving system ot the digital broadcasting
system includes a baseband processor, an IP network stack, and a handler. The baseband processor receives a broadcast signal
including mobile service data and main service data. Herein the mobile service data configures a Reed-Solomon (RS) frame, and
the RS frame includes mobile service data and an internet protocol (IP) signaling channel having pro-decided IP access information
included therein. The IP network stack accesses the IP signaling channel from the RS frame using the IP access information, thereby
collecting signaling table information received through the IP signaling channel. And the handler identifies and parses the collected
signaling table information based upon a table identifier of each signaling table received through the IP signaling channel, thereby
storing the parsed result.

Documents:

http://ipindiaonline.gov.in/patentsearch/GrantedSearch/viewdoc.aspx?id=BrV5Vit9WNw+6NY12AKECw==&loc=wDBSZCsAt7zoiVrqcFJsRw==


Patent Number 280007
Indian Patent Application Number 742/KOLNP/2010
PG Journal Number 06/2017
Publication Date 10-Feb-2017
Grant Date 07-Feb-2017
Date of Filing 25-Feb-2010
Name of Patentee LG ELECTRONICS INC.
Applicant Address 20, YEOUIDO-DONG, YEONGDEUNGPO-GU, SEOUL 150-721, REPUBLIC OF KOREA
Inventors:
# Inventor's Name Inventor's Address
1 SONG, JAE HYUNG LG ELECTRONICS INC. IP GROUP, 16 WOOMYEON-DONG, SEOCHO-GU, SEOUL 137-724, REPUBLIC OF KOREA
2 SUH, JONG YEUL LG ELECTRONICS INC. IP GROUP, 16 WOOMYEON-DONG, SEOCHO-GU, SEOUL 137-724, REPUBLIC OF KOREA
3 KIM, JIN PIL LG ELECTRONICS INC. IP GROUP, 16 WOOMYEON-DONG, SEOCHO-GU, SEOUL 137-724, REPUBLIC OF KOREA
4 LEE, CHUL SOO LG ELECTRONICS INC. IP GROUP, 16 WOOMYEON-DONG, SEOCHO-GU, SEOUL 137-724, REPUBLIC OF KOREA
5 CHOI, IN HWAN LG ELECTRONICS INC. IP GROUP, 16 WOOMYEON-DONG, SEOCHO-GU, SEOUL 137-724, REPUBLIC OF KOREA
PCT International Classification Number H04N 7/015
PCT International Application Number PCT/KR2008/004980
PCT International Filing date 2008-08-25
PCT Conventions:
# PCT Application Number Date of Convention Priority Country
1 10-2008-0082951 2008-08-25 U.S.A.
2 60/974,084 2007-09-21 U.S.A.
3 60/977,379 2007-10-04 U.S.A.
4 61/044,504 2008-04-13 U.S.A.
5 60/957,714 2007-08-24 U.S.A.