KR101565383B1 - / digital broadcasting transmitting/receiving system and method of processing data thereof - Google Patents

Abstract

A receiving system according to an embodiment of the present invention receives a broadcast signal including mobile service data and main service data, and the mobile service data Wherein the second service data includes first service data and second service data in a format different from the first service data, wherein the second service data can constitute an RS frame, the RS frame includes second service data, A baseband processing unit including a table in which signaling information of service data is described; A table handler for parsing the table from the RS frame to extract signaling information of the second service data; And a service handler for parsing the second service data from the RS frame based on the extracted signaling information of the second service data.

Therefore, according to the present invention, one MH system can transmit and receive service data in a format different from that of an existing system.

Digital broadcasting, service map table, signaling, media flow

Description

[0001] DIGITAL BROADCASTING TRANSMITTING / RECEIVING SYSTEM AND METHOD OF PROCESSING DATA THEREOF [0002]

The present invention relates to a digital broadcasting system, and more particularly, to a digital broadcasting receiver and a control method thereof.

The digital broadcasting system may include a digital broadcasting transmitter and a digital broadcasting receiver. Also, the digital broadcast transmitter processes data such as a broadcast program in a digital manner and transmits the processed data to the digital broadcast receiver. Such digital broadcasting systems are gradually replacing analog broadcasting systems due to various advantages such as efficiency of data transmission.

However, the VSB (Vestigial Sideband) transmission system adopted as a digital broadcasting standard in North America and Korea in digital broadcasting is a single carrier system, so reception performance of a receiving system may be deteriorated in a poor channel environment. Particularly, in the case of a portable or mobile broadcast receiver, robustness against channel change and noise is further required, so that when the mobile service data is transmitted using the VSB transmission method, the reception performance is further deteriorated.

Further, in the conventional mobile digital broadcasting environment, there is no specific technique for setting a reception restriction for a specific service or releasing it. This is especially true if the service is to transmit services of a different data format or to set or release a reception restriction.

An embodiment of the present invention is to provide a digital broadcasting receiver and a control method thereof that are resistant to channel variation and noise.

Another embodiment of the present invention is to provide a data processing method capable of setting a reception restriction for a specific service in a mobile digital broadcasting environment or releasing it.

According to another aspect of the present invention, there is provided a data processing method for a receiving system, the method comprising receiving a broadcast signal including mobile service data and main service data, wherein the mobile service data includes a first service data, And the second service data may constitute an RS frame, the RS frame including a table in which second service data and signaling information of the second service data are described; Parsing the table from the RS frame to extract signaling information of the second service data; And parsing the second service data from the RS frame based on the extracted signaling information.

At this time, at least one data group constituting the RS frame includes a plurality of known data sequences, and a signaling information area is included between the first known data sequence and the second known data sequence in the known data sequence And the Signaling information region may include transmission parameter channel (TPC) signaling and fast information channel (FIC) signaling.

The RS frame includes an RS frame header and an RS frame payload, and the RS frame payload may include a transport packet configured by packetizing at least one data for the second service.

The RS frame header includes first information for identifying a type of data in a transport packet transmitted through the payload, second information for indicating presence or absence of an error in a transport packet transmitted through the payload, Third information indicating whether the stuffing byte in the RS frame is included or not and fourth information indicating a starting point of new data in the transport packet transmitted through the payload.

The first information identifies the type of data in the transport packet, and the type may be divided into data for the first service and data for the second service.

In addition, the transport packet transmitted through the RS payload may include a flow packet including data for the second service.

The flow packet includes a flow packet header and a flow packet payload. The flow packet payload includes at least one layered packet for the second service and a length information about the length of the layer packet . ≪ / RTI >

The flow packet header includes identification information for identifying a layer packet included in the flow packet, information indicating whether the flow packet is transmitted over one or more RS frames, whether the flow packet is CRC-applied And information indicating the number of layer packets included in the flow packet.

A receiving system according to an embodiment of the present invention receives a broadcast signal including mobile service data and main service data, and the mobile service data includes a first service data and a second service in a format different from the first service data Data, the second service data can constitute an RS frame, the RS frame including a table in which second service data and signaling information of the second service data are described; A table handler for parsing the table from the RS frame to extract signaling information of the second service data; And a service handler for parsing the second service data from the RS frame based on the extracted signaling information of the second service data.

At this time, at least one data group constituting the RS frame includes a plurality of known data sequences, and a signaling information area is included between the first known data sequence and the second known data sequence in the known data sequence And the signaling information region may include transmission parameter channel (TPC) signaling and fast information channel (FIC) signaling.

The baseband processor unit may further include a known data detector for detecting a known data sequence included in the data group, and the detected known data sequence may be used for demodulating and channelizing mobile service data.

In addition, the table handler extracts a table including signaling information of the second service data from the RS frame, which is composed of an RS frame header and an RS frame payload, and the RS frame payload includes at least And may include a transport packet in which one piece of data is packetized.

The table handler includes first information for identifying a type of data in a transport packet transmitted through the payload, second information for indicating presence or absence of an error of a transport packet transmitted through the payload, Extracting the RS frame header information including at least one of third information indicating whether to include stuffing bytes in a frame and fourth information indicating a starting point of new data in a transport packet transmitted through the payload And selecting the service handler from the extracted first information by identifying whether the type of data in the transferred transport packet includes first service data or second service data.

In addition, the selected service handler processes a transport packet transmitted through the RS frame payload, wherein the transport packet includes a flow packet including data for the second service, The packet header and the flow packet payload including at least one layered packet for the second service and length information about the length of the layered packet.

The service handler may include identification information capable of identifying the layer packet included in the corresponding flow packet, information indicating whether the corresponding flow packet is transmitted over one or more RS frames, whether or not the flow packet is CRC applied And information indicating the number of layer packets included in the corresponding flow packet.

According to an embodiment of the present invention, a digital broadcast receiver and a control method thereof that are resistant to channel variation and noise can be provided.

According to another embodiment of the present invention, service data in a format different from that of the existing MH system format can be transmitted and received in a mobile digital broadcasting environment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. At this time, the configuration and operation of the present invention shown in the drawings and described in the drawings are explained as at least one embodiment, and the technical idea of the present invention and its core configuration and operation are not limited thereby.

Definitions of terms used in the present invention

The terms used in the present invention are selected from general terms that are widely used in the present invention while considering the functions of the present invention. However, the terms may vary depending on the intention or custom of the artisan or the emergence of new technology. Also, in certain cases, there may be a term selected arbitrarily by the applicant, in which case the meaning thereof will be described in detail in the description of the corresponding invention. Therefore, it is to be understood that the term used in the present invention should be defined based on the meaning of the term rather than on the name of the term, and on the content of the present invention throughout the present invention.

Among the terms used in the present invention, main service data may include audio / video (A / V) data as data that can be received by a fixed receiving system. That is, the main service data may include HD (High Definition) or SD (Standard Definition) A / V data, and various data for data broadcasting may be included. The known data is previously known data by the promise of the transmitting / receiving side.

Among the terms used in the present invention, MH is the first letter of each of a mobile and a handheld, and is a concept opposite to a fixed type. The MH service data includes at least one of mobile service data and handheld service data. For convenience of explanation, the MH service data is also referred to as mobile service data in the present invention. At this time, the mobile service data may include not only MH service data but also service data indicating movement or carrying, so that the mobile service data will not be limited to the MH service data.

The mobile service data defined above may be data having information such as a program executable file, stock information, etc., or A / V data. In particular, the mobile service data may be service data for a portable or mobile terminal (or broadcast receiver), and may be A / V data having a smaller resolution and a smaller data rate than the main service data. For example, if the A / V codec used for the existing main service is an MPEG-2 codec, the A / V codec for mobile service may be MPEG-4 Advanced Video Coding (AVC), and Scalable Video Coding (SVC). In addition, any kind of data can be transmitted with the mobile service data. For example, TPEG (Transport Protocol Expert Group) data for broadcasting traffic information in real time can be transmitted as mobile service data.

The data service using the mobile service data includes a weather service, a traffic service, a securities service, a viewer participation quiz program, a real-time opinion survey, an interactive education broadcast, a game service, a story of a drama, Provide information on the program by service, media, time, or topic that provides information service for sports, history of sports, profiles and grades of players, product information, and ordering Service, and the like, and the present invention is not limited thereto.

The transmission system according to the present invention is capable of multiplexing the main service data and the mobile service data on the same physical channel without any influence on receiving the main service data in the existing receiving system.

The transmission system of the present invention performs additional coding on the mobile service data and inserts known data, that is, known data, into both the transmitting and receiving sides.

With the transmission system according to the present invention, mobile service data can be received and received in the receiving system, and stable reception of mobile service data is possible even with various distortions and noises occurring in the channel.

Receiving system

FIG. 1 is a block diagram illustrating a configuration of a reception system according to an embodiment of the present invention. Referring to FIG.

The receiving system according to the present embodiment includes a baseband processor 100, a management processor 200, and a presentation processor 300.

The baseband processor 100 includes an operation controller 110, a tuner 120, a demodulator 130, an equalizer 140, a known sequence detector A mobile handheld block decoder 160, a primary RS frame decoder 170, a secondary RS frame decoder 180, and a signaling decoder 190, . ≪ / RTI >

The operation controller 110 controls the operation of each block of the baseband processor 100.

The tuner 120 serves to receive main service data, which is a broadcast signal for a fixed broadcast receiving apparatus, and mobile service data, which is a broadcast signal for a mobile broadcast receiving apparatus, by tuning the receiving system at a specific physical channel frequency . At this time, the frequency of the tuned specific channel is down-converted to an intermediate frequency (IF) signal and output to the demodulator 130 and the known data detector 140. The passband digital IF signal output from the tuner 120 may include only main service data, only mobile service data, or both main service data and mobile service data.

The demodulator 130 performs automatic gain control, carrier recovery, and timing recovery on a digital IF signal of a passband inputted from the tuner 120, converts the signal into a baseband signal, and then outputs the baseband signal to an equalizer 140 and a known data detector 150. The demodulator 130 can improve demodulation performance by using a known data symbol sequence received from the known data detector 150 during timing recovery or carrier recovery.

The equalizer 140 compensates for the distortion on the channel included in the demodulated signal from the demodulator 130 and outputs the compensated signal to the block decoder 160. The equalizer 140 can improve equalization performance by using a known data symbol sequence input from the known data detector 150. [ Also, the equalizer 140 may feedback the decoding result of the block decoder 150 to improve the equalization performance.

The known data detector 150 detects the known data position inserted from the transmitting side from the input / output data of the demodulator 130, that is, the data before the demodulation or the demodulated data, To the demodulator 130 and the equalizer 140. The known data detector 150 detects the mobile service data that has undergone the additional coding at the transmitting end and the additional data And outputs information for enabling the block decoder 160 to distinguish the main service data to the block decoder 160.

If the data input after the channel equalization in the equalizer 140 is data in which block encoding and trellis encoding are both performed (i.e., data in the RS frame, signaling data), the block decoder 160 outputs Performs trellis decoding and block decoding, and performs only trellis decoding if the data is only Trellis-encoded (i.e., main service data) without performing block encoding.

The signaling decoder 190 decodes the signaling data input after being equalized by the equalizer 140. It is assumed that the signaling data input to the signaling decoder 190 is data in which both block encoding and trellis encoding are performed in the transmission system. Examples of such signaling data include transmission parameter channel (TPC) data and fast information channel (FIC) data. Each data item is described in detail below. The FIC data decoded by the signaling decoder 190 is output to an FIC handler 215 and the decoded TPC data is output to a TPC handler 214.

Meanwhile, according to the present invention, the transmission system uses the RS frame concept as an encoding unit. The RS frame is divided into a primary RS frame and a secondary RS frame. However, the primary RS frame and the secondary RS frame are distinguished from each other according to the importance of data.

The primary RS frame decoder 170 receives the output of the block decoder 160 as an input. In this case, the primary RS frame decoder 170 receives only Reed Solomon (RS) encoded and / or CRC (Cyclic Redundancy Check) encoded mobile service data from the block decoder 160 as an embodiment. That is, the primary RS frame decoder 170 receives only the mobile service data, not the main service data. The primary RS frame decoder 170 performs an inverse process of an RS frame encoder (not shown) of the transmission system to correct errors in the primary RS frame. That is, the primary RS frame decoder 170 collects a plurality of data groups to form a primary RS frame, and then performs error correction on a primary RS frame basis. In other words, the primary RS frame decoder 170 decodes a primary RS frame transmitted for an actual broadcast service or the like.

The secondary RS frame decoder 180 receives the output of the block decoder 160 as an input. In this case, the secondary RS frame decoder 180 receives only RS-encoded and / or CRC-encoded mobile service data. That is, the secondary RS frame decoder 180 receives only the mobile service data, not the main service data. The secondary RS frame decoder 180 performs an inverse process of the RS frame encoder (not shown) of the transmission system to correct errors in the secondary RS frame. That is, the secondary RS frame decoder 180 collects a plurality of data groups to form a three-coner RS frame, and then performs error correction on a secondary RS frame basis. In other words, the secondary RS frame decoder 180 decodes secondary RS frames transmitted for mobile audio service data, mobile video service data, guide data, and the like.

The management processor 200 according to an exemplary embodiment of the present invention includes an MH physical adaptation processor 210, an IP network stack 220, a streaming handler 230 An SI handler 240, a file handler 250, a Multipurpose Internet Mail Extensions (MIME) type handler 260, an ESG handler 270, An ESG decoder (ESG decoder) 280, and a storage unit 290.

The MH physical adaptation processor 210 includes a primary RS frame handler 211, a secondary RS frame handler 212 and an MH-TP handler 213 ), A TPC handler 214, a FIC handler 215, and a Physical Adaptation Control Signal Handler 216.

The TPC handler 214 receives and processes baseband information required by the modules corresponding to the MH physical adaptation processor 210. The baseband information is input in the form of TPC data, And processes FIC data or the like received from the baseband processor 100 using this information.

The TPC data is transmitted from the transmission system to the reception system through a predetermined area of the data group. The TPC data may include at least one of an MH-Ensemble ID, an MH-Subframe Number, a TNoG (Total Number of MH-Groups), an RS frame Continuity Counter, a N (Column Size of RS-frame) have.

The MH-Ensemble ID is an identification number for each MH ensemble transmitted on the corresponding physical channel (Identification number for each MH-Ensemble carried in this physical channel).

The MH-Subframe Number is a number indicating a subframe in the MH frame (A number that identifies the MH-Subframe number in an MH-frame, where each MH-Group is associated with this MH-Ensemble is transmitted).

The Total Number of MH-Groups (TNoG) represents the total number of data groups belonging to all the MH parades in one subframe (Total Number of MH-Groups including all MH-Groups belonging to all MH- MH-Subframe).

The RS frame continuity counter is a number indicative of a continuous indicator of an RS frame transmitted in the corresponding MH frame, and increases by 1 while employing modulo 16 for each successive RS frame (A number which serves as a continuity indicator of the RS- frames carrying this MH-Ensemble. The value will be incremented by 1 modulo 16 for each successive RS-frame).

The size of the MH-TP (Transport Packet) is determined based on the column size of the RS frame belonging to the corresponding MH ensemble. belongs to this MH-Ensemble.

The FIC Version Number indicates the version number of the FIC transmitted on the corresponding physical channel (A number, which represents the version number of the FIC carried on the physical channel).

The TPC data is input to the TPC handler 214 via the signaling decoder 190 of Figure 1 and processed by the TPC handler 214 and used by the FIC handler 215 to process the FIC data do.

The FIC handler 215 processes the FIC data received from the baseband processor 100 in association with the TPC data received from the TPC handler 214.

The physical adaptive control signal handler 216 collects the FIC data transmitted through the FIC handler 215 and the SI data received through the RS frame and uses the generated SI data to configure and access information of the IP datagram and the mobile broadcast service. And stores it in the storage unit 290.

The primary RS frame handler 211 divides the primary RS frame received from the primary RS frame decoder 170 of the baseband processor 100 into units of each row to form an MH-TP, And outputs it to the handler 213.

The secondary RS frame handler 212 divides the secondary RS frame received from the secondary RS frame decoder 180 of the baseband processor 100 into units of each row to form an MH-TP, and transmits the secondary RS frame to the MH-TP handler 213 .

The MH-TP handler 213 extracts each header of the MH-TP transmitted from the primary and secondary RS frame handlers 211 and 212 to determine data included in the corresponding MH-TP. If the determined corresponding data is SI data, the data is output to the physical adaptive control signal handler 216 (i.e., SI data that is not encapsulated in the IP datagram) 220.

The IP network stack 220 processes broadcast data transmitted in an IP datagram format. That is, the IP network stack 220 includes a UDP (User Datagram Protocol), an RTP (Real-time Transport Protocol), an RTCP (Real-time Transport Control Protocol), an Asynchronous Layered Coding / Layered Coding Transport (File Delivery over Unidirectional Transport) or the like. If the processed data is streaming data, the streaming data is output to the streaming handler 230. If the processed data is data of a file format, the data is output to the file handler 250, .

The SI handler 240 receives and processes the SI data in the form of an IP datagram input to the IP network stack 220.

The SI handler 240 outputs the SI data to the MIME type handler 260 when the input SI data is a MIME type.

The MIME type handler 260 receives and processes the SI data of the MINE type output from the SI handler 240.

The file handler 250 receives data in the form of an object according to the ALC / LCT and the FLUTE structure from the IP network stack 220. The file handler 250 collects the received data to form a file. When the file includes an electronic service guide (ESG), the file handler 250 outputs the file to the ESG handler 270. Data for other file- And outputs it to the presentation controller 330 of the presentation processor 300.

The ESG handler 270 processes the ESG data received from the file handler 250 and stores the processed ESG data in the storage unit 290 or outputs the ESG data to the ESG decoder 280 to use the ESG data in the ESG decoder 280 do.

The storage unit 290 stores SI (System Information) received from the physical adaptation control signal handler 216 and the ESG handler 270, and transmits the stored data to each block.

The ESG decoder 280 restores the ESG data and the SI data stored in the storage unit 290 or the ESG data received from the ESG handler 270 and outputs the ESG data to the presentation controller 330 Output.

The streaming handler 230 receives data from the IP network stack 220 according to the RTP and RTCP structures. The streaming handler 230 extracts an audio / video stream from the received data and outputs the extracted audio / video stream to the audio / video decoder 310 of the presentation processor 300. The audio / video decoder 311 decodes the audio stream and the video stream received from the streaming handler 230, respectively.

The display module 320 of the presentation processor 300 receives the decoded audio and video signals from the A / V decoder 310 and provides the decoded audio and video signals to a user through a speaker and / or a screen.

The presentation controller 330 is a controller responsible for modules for outputting data received by the receiving system to a user.

The channel service manager 340 interfaces with a user to enable a channel service, such as channel map management and channel service access, to be used by the user.

The Application Manager (350) is responsible for interfacing with the user to use application services other than the ESG display or other channel services.

Data format structure

Meanwhile, the data structure used in the mobile broadcasting technology according to the present embodiment includes a data group structure and an RS frame structure. This will be described in detail as follows.

2 is a diagram illustrating a structure of a data group according to an embodiment of the present invention.

In the data structure according to FIG. 2, the data group is divided into 10 MH blocks (MH blocks B1 to B10). And each MH block has a length of 16 segments as an embodiment. In FIG. 2, only the RS parity data is allocated to some of the 5 segments before the MH block B1 and the 5 segments after the MH block B10, and the data is excluded from the A region to the D region of the data group.

That is, assuming that one data group is divided into A, B, C, and D regions, each MH block may be included in any one of the A region to the D region according to the characteristics of each MH block in the data group . At this time, each MH block is included in one of the A region and the D region according to the degree of interference of the main service data.

The reason why the data group is divided into a plurality of regions is to differentiate each use. That is, a region where there is no interference of the main service data or a region where there is no interference can show robust reception performance than the region where no interference occurs. In addition, when a system for inserting known data known by the promise of a transmitting / receiving end into a data group and transmitting the data is applied, when it is desired to periodically insert consecutively long base data into mobile service data, It is possible to periodically insert a known length of known data into an area where there is no interference of data (that is, an area where main service data is not mixed). However, it is difficult to periodically insert the known data due to the interference of the main service data in the area where interference of the main service data occurs, and it is also difficult to continuously insert the known data.

MH block B4 to MH block B7 in the data group of FIG. 2 show an example in which a long known data sequence is inserted before and after each MH block as an area without interference of main service data. In the present invention, the area A (= B4 + B5 + B6 + B7) including the MH block B4 to the MH block B7 will be described. As described above, in the case of the A region having the known data sequence for each MH block, the receiving system can perform equalization using the channel information obtained from the known data. Thus, the most robust equalization performance among the A region to the D region I can get it.

The MH block B3 and the MH block B8 in the data group of FIG. 2 are areas where interference of the main service data is small and an example in which a long known data sequence is inserted into only one of the two MH blocks is shown. That is, due to the interference of the main service data, the MH block B3 inserts a long known data sequence after the corresponding MH block, and the MH block B8 inserts a long known data string only in front of the corresponding MH block. In the present invention, the MH block B3 and the MH block B8 are referred to as a B area (= B3 + B8). As described above, in the case of the B region having the known data sequence in either one of the MH blocks, the receiving system can perform equalization using the channel information obtained from the known data. Thus, the equalization performance Can be obtained.

The MH block B2 and the MH block B9 in the data group of FIG. 2 have more interference of the main service data than the B area, and can not insert a long known data sequence back and forth in both MH blocks. In the present invention, a C region (= B2 + B9) including the MH block B2 and the MH block B9 will be described.

The MH block B1 and the MH block B10 in the data group of FIG. 2 have more interference of the main service data than the C area, and similarly, it is impossible to insert a long known data sequence back and forth in both MH blocks. In the present invention, the MH block B1 and the MH block B10 will be referred to as a D area (= B1 + B10). Since the C / D region is far away from the known data sequence, the reception performance may be poor if the channel changes rapidly.

Also, the data group includes a signaling information area to which signaling information is allocated.

The present invention can use a part of the second segment from the first segment of the MH block B4 in the data group as a signaling information area.

The present invention uses 276 (= 207 + 69) bytes of the MH block B4 of each data group as a signaling information area. That is, the signaling information area is composed of 207 bytes, which is the first segment of the MH block B4, and the first 69 bytes of the second segment. The first segment of the MH block B4 corresponds to the 17th or 173rd segment of the VSB field.

The signaling information can be divided into two types of signaling channels. One is a transmission parameter channel (TPC), and the other is a fast information channel (FIC).

The TPC data may include at least one of an MH-Ensemble ID, an MH-Subframe Number, a TNoG (Total Number of MH-Groups), an RS frame Continuity Counter, a N (Column Size of RS-frame) have. The TPC information is only an example for facilitating understanding of the present invention. Addition and deletion of signaling information included in the TPC can be easily changed by those skilled in the art, so the present invention is not limited to the above embodiments. The FIC data is provided to allow a fast service acquisition at a receiver, and includes cross layer information between a physical layer and an upper layer.

For example, when the data group includes six known data strings as shown in FIG. 2, the signaling information area is located between the first known data string and the second known data string. That is, the first known data sequence is inserted into the last two segments of the MH block B3 in the data group, and the second known sequence data sequence is inserted into the second and third segments of the MH block B4. And the third to sixth known data sequences are inserted into the last two segments of the MH blocks B4, B5, B6 and B7, respectively. The first, third, and sixth to sixth known data streams are separated by 16 segments.

In addition, according to another embodiment of the present invention, MH data is transmitted to a data area for data interface for a MediaFLO service to be described later, and control data associated with the media flow service is also included in the data area together Lt; / RTI > A more detailed description thereof will be described later in this section, and a detailed description thereof will be omitted.

3 is a diagram illustrating an RS frame according to an embodiment of the present invention.

The RS frame shown in FIG. 3 is a set of one or more data groups. This RS frame is received for each MH frame with the receiving system switched to the time slicing mode so as to receive the MH ensemble including the ESG entry point after receiving the FIC and processing the FIC. One RS frame includes IP streams of each service or ESG, and SMT section data may exist in all RS frames.

The RS frame according to an exemplary embodiment of the present invention includes at least one MH TP (Transport Packet). The MH TP consists of an MH header and an MH payload.

The MH payload may include mobile service data as well as signaling data. That is, one MH payload may contain only mobile service data, only signaling data, or both service data and signaling data.

An embodiment of the present invention distinguishes data included in an MH payload by an MH header. That is, if the MH TP has a first MH header, it indicates that the MH payload contains signaling data. Also, if the MH TP has a second MH header, it indicates that the MH payload contains the signaling data and the service data. If the MH TP has a third MH header, it indicates that the MH payload contains the service data.

The RS frame of FIG. 3 shows an example in which IP datagrams (i.e., IP Datagram 1 and IP Datagram 2) for two types of services are allocated.

Data transfer structure

4 is a diagram illustrating an MH frame structure for transmitting mobile service data according to the present invention.

FIG. 4 shows an example in which one MH frame is composed of 5 subframes, and one subframe is composed of 16 slots. In this case, one MH frame includes 5 subframes, 80 slots.

One slot consists of 156 data packets (i.e., transport stream packets) at the packet level and 156 data segments at the symbol level. Or a half of the VSB field. That is, since one data packet of 207 bytes has the same amount of data as one data segment, a data packet before data interleaving can be used as a concept of a data segment. At this time, two VSB fields are gathered to form one VSB frame.

FIG. 5 shows an example of a VSB frame structure. One VSB frame is composed of two VSB fields (i.e., an odd field and an even field). Each VSB field is composed of one field sync segment and 312 data segments.

The slot is a basic time unit for multiplexing mobile service data and main service data. One slot may include mobile service data, or may consist of only main service data.

If the first 118 data packets in the slot correspond to one data group, the remaining 38 packets become the main service data packet. As another example, if there is no data group in one slot, the slot is made up of 156 main service data packets.

On the other hand, when the slots are assigned to VSB frames, they have offsets at their positions.

FIG. 6 shows a mapping example of a first 4-slot position of a subframe for one VSB frame in a spatial domain. FIG. 7 shows a mapping example of a first 4-slot position of a subframe in a time domain for one VSB frame.

6 and 7, the 38th data packet (# 37) of the first slot (Slot # 0) is mapped to the first data packet of the odd VSB field and the 38th data packet The packet # 37 is mapped to the 157th data packet of the odd VSB field. The 38th data packet (# 37) of the third slot (Slot # 2) is mapped to the first data packet of the even VSB field and the 38th data packet (# 37) of the fourth slot And is mapped to the 157th data packet of the even VSB field. Likewise, the remaining 12 slots in the subframe are mapped in the same way to the following VSB frame.

FIG. 8 shows an example of a data group allocation procedure to be assigned to one subframe among five subframes constituting an MH frame. For example, the method of allocating data groups may be the same for all MH frames or may be different for each MH frame. Also, the present invention may be applied to all subframes within one MH frame, or may be applied to each subframe differently. At this time, assuming that the allocation of the data group is applied to all the subframes in the MH frame, the number of data groups allocated to one MH frame is a multiple of 5.

And consecutively allocating a plurality of data groups as far apart as possible in a subframe according to an embodiment of the present invention. This makes it possible to strongly respond to burst errors that may occur in one subframe.

For example, assuming that three groups are allocated to one subframe, the first slot (Slot # 0), the fifth slot (Slot # 4) and the ninth slot (Slot # 8) do. FIG. 8 shows an example of allocating 16 data groups in one subframe by applying the allocation rule. In FIG. 8, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7, and 15, respectively.

Equation (1) is a mathematical expression of rules for assigning data groups to one subframe as described above.

j = (4i + O) mod 16

Where O = 0 if i < 4,

O = 2 else if i <8,

O = 1 else if i <12,

O = 3 else.

Here, j is a slot number in one subframe and may have a value between 0 and 15. The i is a group number and may have a value between 0 and 15.

In the present invention, a collection of data groups included in one MH frame is referred to as a parade. The parade transmits data of one or more specific RS frames according to the RS frame mode.

The mobile service data in one RS frame may be all allocated to the A / B / C / D area in the data group, or may be allocated to at least one area of the A / B / C / D area. In one embodiment, mobile service data in one RS frame is allotted to the A / B / C / D area or only to the A / B area and the C / D area. That is, in the latter case, the RS frame allocated to the A / B area in the data group is different from the RS frame allocated to the C / D area. According to an embodiment of the present invention, an RS frame allocated to an A / B area in a data group is referred to as a primary RS frame, and an RS frame allocated to a C / D area is referred to as a secondary RS frame frame. The primary RS frame and the secondary RS frame constitute one parade. That is, if mobile service data in one RS frame is all allocated in the A / B / C / D area in the data group, one parade transmits one RS frame. On the other hand, if the mobile service data in one RS frame is allocated to the A / B area in the data group and the mobile service data in the other RS frame is allocated to the C / D area in the corresponding data group, RS frames.

That is, the RS frame mode indicates whether one parade transmits one RS frame or two RS frames. This RS frame mode is transmitted as TPC data described above.

Table 1 below shows an example of the RS frame mode.

RS frame mode Description 00 There is only a primary RS frame for all Group Regions 01 There are two separate RS frames
-Primary RS frame for Group A and B
-Secondary RS frame for Group Region C and D 10 Reserved 11 Reserved

In Table 1, 2 bits are allocated to indicate the RS frame mode. Referring to Table 1, if the RS frame mode value is 00, it indicates that one parade transmits one RS frame. If the RS frame mode value is 01, one parade is transmitted to two RS frames, that is, a primary RS Frame and the secondary RS frame. That is, when the RS frame mode value is 01, the data of the primary RS frame for region A / B for the A / B region is allocated and transmitted to the A / B region of the data group, And the data of the secondary RS frame (region C / D) for the region is assigned to the C / D region of the corresponding data group and is transmitted.

As with the allocation of the data groups, it is also an embodiment that the parades are allocated as far apart as possible in the subframe. This makes it possible to strongly respond to burst errors that may occur in one subframe.

And the parade allocation method can be applied differently for each MH frame, and the same applies to all MH frames. Also, the present invention may be applied to all subframes within one MH frame, or may be applied to each subframe differently. The present invention may be applied to all subframes within one MH frame, and may be applied to all MH frames. That is, the MH frame structure can be changed in units of MH frames, which makes it possible to flexibly adjust the MH ensemble data rate.

9 is a diagram showing an example of assigning a single parade to one MH frame. That is, FIG. 9 shows an embodiment in which a single parade having three data groups included in one subframe is allocated to one MH frame.

Referring to FIG. 9, when three data groups are sequentially allocated in a 4-slot period in one subframe, and this process is performed on 5 subframes in the corresponding MH frame, 15 data groups are allocated to one MH frame do. Here, the 15 data groups are data groups included in one parade. Therefore, one subframe is composed of four VSB frames, but one subframe includes three data groups. Therefore, a VSB frame of one of four VSB frames in one subframe is assigned a data group of the corresponding parade It does not.

For example, one parade transmits one RS frame, performs RS encoding in the RS frame encoder (not shown) of the transmission system for the corresponding RS frame, adds 24 bytes of parity data to the corresponding RS frame In this case, the specific gravity occupied by the parity data among the lengths of the entire RS codewords is about 11.37% (= 24 / (187 + 24) x 100). On the other hand, when three data groups are included in one subframe and fifteen data groups form one RS frame in the case of assigning data groups in one parade, a burst noise generated in the channel causes a group Even in the case of an error, its proportion is 6.67% (= 1/15 x 100). Therefore, in the receiving system, all errors can be corrected by erasure RS decoding. That is, when Erasure RS decoding is performed, channel errors corresponding to the number of RS parities can be corrected. Therefore, all byte errors below the number of RS parities in one RS codeword can be corrected. In this way, the receiving system can correct errors of at least one data group in one parade. The minimum burst noise length that can be corrected by one RS frame is equal to or greater than one VSB frame (i.e., the minimum burst noise length is correctable by a VSB frame).

Meanwhile, when data groups for one parade are allocated as shown in FIG. 9, main service data may be allocated between data groups and data groups of other parades may be allocated. That is, data groups for a plurality of parades may be allocated to one MH frame.

Basically, the allocation of data groups to multiple parades is not different from that of a single parade. In other words, data groups in other parades allocated to one MH frame are also allocated in each of four slot periods.

At this time, the data group of another parade may be allocated in a circular manner from a slot to which the data group of the previous parade is not allocated.

For example, assuming that the allocation of the data group for one parade is made as shown in FIG. 9, the data group for the next parade is allocated from the 12th slot in one subframe. This is one example, and in another example, the data group of the next parade may be sequentially allocated in another slot in one subframe, for example, from the third slot to the fourth slot period.

FIG. 10 shows an example of transmitting three parades (Parade # 0, Parade # 1, Parade # 2) to one MH frame. Particularly, parade transmission of one subframe among five subframes constituting an MH frame For example.

Assuming that the first parade includes three data groups per subframe, the positions of the data groups in the subframe can be obtained by substituting 0 to 2 for the i value of Equation (1). That is, the data groups of the first parade are sequentially allocated to the first, fifth, and ninth slots (Slot # 0, Slot # 4, Slot # 8) in the subframe.

Assuming that the second parade includes two data groups per subframe, the positions of the data groups in the subframe can be obtained by substituting 3 to 4 in the i value of Equation (1). That is, the data groups of the second parade are sequentially allocated to the second and twelfth slots (Slot # 1, Slot # 11) in the subframe.

Assuming that the third parade includes two groups per subframe, the positions of the data groups in the subframe can be obtained by substituting 5 to 6 in the i value of Equation (1). That is, the data groups of the third parade are sequentially allocated to the seventh and eleventh slots (Slot # 6, Slot # 10) in the subframe.

In this way, data groups for a plurality of parades can be allocated to one MH frame, and the allocation of data groups in one subframe is performed in serial from left to right with a group space of 4 slots.

Therefore, the number of data groups within one parade (NOG) that can be allocated to one subframe can be any one of integers from 1 to 8. In this case, since one MH frame includes 5 subframes, it means that the number of data groups of one parade that can be allocated to one MH frame can be any one of multiples of 5 from 5 to 40 it means.

FIG. 11 shows an example in which the allocation process of three parades in FIG. 10 is extended to five subframes in one MH frame.

12 is a diagram illustrating a data transmission structure according to an embodiment of the present invention, in which signaling data is included in a data group and transmitted.

As described above, the MH frame is divided into five subframes, and data groups corresponding to several parades are present in each subframe. Data groups corresponding to each parade are grouped in units of MH frames Will constitute a parade. There are three parades in FIG. 12, and there is one EDG (ESG Dedicated Channel) parade (NoG = 1) and two service parades (NoG = 4, NoG = 3). In addition, a certain portion of each data group (e.g., 37 bytes / data group) is used to convey FIC information encoded separately from RS encoding for mobile service data. The FIC region allocated to each data group forms one FIC segment, and these FIC segments are interleaved on each MH subframe to form a complete FIC. However, if necessary, the FIC segments may be interleaved not only in a subframe but also in an MH frame, and may have integrity in an MH frame.

In the present embodiment, the MH ensemble concept is introduced to define a set of services. One MH ensemble has the same QoS and is coded with the same FEC code. In addition, one MH ensemble has the same unique identifier (i.e., ensemble id) and corresponds to consecutive RS frames.

As shown in FIG. 12, the FIC segment corresponding to each data group describes the service information of the MH ensemble to which the corresponding data group belongs. When the FIC segments in one subframe are collected, all the service information of the physical channel through which the corresponding FIC is transmitted can be obtained. Therefore, the receiving system can acquire the channel information of the physical channel for the sub frame period after the physical channel tuning.

In FIG. 12, Electronic Service Guide (ESG) data is transmitted at a first slot position of each subframe with a EDC parade different from a service parade.

Layered signaling structure

13 is a diagram illustrating a layered signaling structure according to an embodiment of the present invention. The mobile broadcasting technology according to the present embodiment employs a signaling method using FIC and SMT as shown in FIG. This is referred to as a layered signaling structure in the present invention.

Hereinafter, a description will be given of how the receiving system approaches the virtual channel by FIC and SMT, with reference to FIG.

The physical channel level signaling data FIC informs the physical location of each data stream for each virtual channel. In addition, the FIC provides the upper level information of each virtual channel. (The FIC defines in MH Transport (M1) identifies the physical location of each data stream for each virtual channel.

The SM ensemble level signaling data SM provides the MH ensemble level signaling information. Each SMT provides IP access information of each virtual channel belonging to the corresponding MH ensemble including each SMT. In addition, the SMT provides the IP stream component level information necessary for the service of the corresponding virtual channel (SMT). The SMT provides the IP stream component level information necessary for the service of the corresponding virtual channel. Ensemble within which the SMT is carried, and all the IP stream component level information necessary for the virtual channel service acquisition.

Each of the MH ensembles (Ensemble 0, 1, ..., K) includes stream information (for example, Virtual Channel 0 IP Stream, Virtual Channel 1 IP Stream, Virtual Channel 2 IP Stream). For example, Ensemble 0 includes Virtual Channel 0 IP Stream and Virtual Channel 1 IP Stream. Also, in each MH ensemble, various information (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, Info., Virtual Channel N Table Entry, Virtual Channel N Access Info.).

The FIC includes information on the MH ensemble (ensemble_id field, ensemble location), information on the virtual channel associated with the corresponding MH ensemble (such as a major channel num field and a minor channel num field, ., N).

Finally, the application in the receiving system is as follows.

When the user selects a channel desired to be viewed (referred to as 'channel θ' for convenience of explanation), the receiving system first parses the received FIC. Then, the receiving system acquires information (Ensemble Location) about the MH ensemble associated with the virtual channel corresponding to the channel [theta] (referred to as 'MH ensemble [theta]' for convenience of explanation). The receiving system obtains only the slots corresponding to the MH ensemble &amp;thetas; by means of the time slicing method to construct the ensemble &amp;thetas;. As described above, the ensemble? Comprises the SMT for the associated virtual channels (including channel?) And the IP stream for the virtual channels concerned. Therefore, the receiving system obtains various information (Virtual Channel? Table Entry) about the channel? And stream access information (Virtual Channel? Access Info.) About the channel? By using the SMT included in the configured MH ensemble?. The receiving system receives only the related IP stream using the stream access information for the channel [theta], and provides the user with a service for the channel [theta].

Fast Information Channel (FIC)

In addition, the receiving system according to the present invention introduces a fast information channel (FIC) to allow a user to access a currently broadcasted service more quickly.

That is, the FIC handler 215 of FIG. 1 parses the FIC and outputs the result to the physical adaptive control signal handler 216.

FIG. 14 is a diagram illustrating an embodiment of the FIC format according to the present invention. According to this embodiment, the FIC format consists of an FIC body header and an FIC body.

Meanwhile, according to the present embodiment, the data transmitted through the FIC body header and the FIC body are transmitted in FIC segment units. Each FIC segment unit is 37 bytes in size, and each FIC segment consists of a 2-byte FIC segment header and a 35-byte FIC segment payload. That is, one FIC format composed of the FIC body header and the FIC body is segmented by 35 bytes and carried in the FIC segment payload in one or more FIC segments.

In the present invention, one FIC segment is inserted into one data group and transmitted. In this case, the receiving system receives a slot corresponding to each data group by a time slicing method.

Meanwhile, the signaling decoder 190 in the receiving system of FIG. 1 collects each FIC segment inserted into each data group. And the signaling decoder 190 constructs one FIC format using each FIC segment collected. The signaling decoder 190 performs a decoding operation corresponding to the encoding of a signaling encoder (not shown) in the transmission system with respect to the FIC body of one FIC format, and one decoded FIC body is processed by the FIC handler 215 . The FIC handler 215 parses the FIC data in the FIC body and outputs the parsed FIC data to the physical adaptive control signal handler 216. The physical adaptive control signal handler 216 performs operations related to the MH ensemble, the virtual channel, the SMT, and the like using the input FIC data.

On the other hand, according to one embodiment, when one FIC format is segmented, if the last segment segmented is 35 bytes or less, the remaining FIC segment payload is allocated with a stuffing byte Can be assumed.

The byte values (FIC segment: 37 bytes, FIC segment header: 2 bytes, FIC segment payload: 35 bytes) described above are only examples, and the present invention is not limited thereto.

15 is a diagram showing an embodiment of a data structure of an FIC segment according to the present invention. Here, the FIC segment means a unit used for transmission of FIC data.

The FIC segment consists of an FIC segment header and an FIC segment payload. According to FIG. 15, the FIC segment payload can be regarded as a portion of the for loop. The FIC segment header may include an FIC_type field, an error_indicator field, an FIC_seg_number field, and an FIC_last_seg_number field. The description of each field is as follows.

The FIC_type field (2 bits) indicates the type of the corresponding FIC.

The error_indicator field (1 bit) indicates whether an error has occurred in the FIC segment during transmission, and is set to '1' when an error occurs. That is, when there is an error that can not be recovered in the process of constructing the FIC segment, this field is set to '1'. Through this field, the receiving system can recognize the presence or absence of an error in the FIC data.

The FIC_seg_number field (4 bits) indicates the number of the corresponding FIC segment when the corresponding FIC format is divided into a plurality of FIC segments.

The FIC_last_seg_number field (4 bits) indicates the last FIC segment number of the corresponding FIC format.

16 is a diagram illustrating an embodiment of a bitstream syntax structure for a payload of an FIC segment when the FIC type field value is '0' according to the present invention.

In this embodiment, the payload of the FIC segment is divided into three areas.

The first area exists only when the FIC_seg_number is '0', and may include a current_next_indicator field, an ESG_version field, and a transport_stream_id field. However, it can be assumed that the above three fields are present regardless of the FIC_seg_number depending on the embodiment.

The current_next_indicator field (1 bit) indicates whether the corresponding FIC data includes MH ensemble configuration information of the MH frame including the current FIC segment or MH ensemble configuration information of the next MH frame Indicator).

The ESG_version field (5 bits) indicates the version information of the ESG, and a version of the service guide providing channel of the corresponding ESG is provided to inform the receiving system whether the ESG is updated.

The transport_stream_id field (16 bits) indicates a unique identifier of a broadcast stream to which the FIC segment is transmitted.

The second area is an ensemble loop area, and may include an ensemble_id field, an SI_version field, and a num_channel field.

The ensemble_id field (8 bits) indicates the identifier of the MH ensemble to which the MH services described later are transmitted. This field serves to bind the MH services and the MH ensemble.

The SI_version field (4 bits) indicates the version information of the SI data of the corresponding ensemble transmitted in the RS frame.

The num_channel field (8 bits) indicates the number of virtual channels transmitted through the ensemble.

The third region may include 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 in a channel loop region.

The channel_type field (5 bits) indicates a service type of the corresponding virtual channel. For example, this field may represent 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,

The channel_activity field (2 bits) indicates the activity information of the corresponding virtual channel, so that it can know whether the corresponding virtual channel provides the current service.

The CA_indicator field (1 bit) indicates whether a conditional access (CA) is applied to the corresponding virtual channel.

The stand_alone_service_indicator field (1 bit) indicates whether the virtual channel service is a stand alone service.

The major_channel_num field (8 bits) indicates the major channel number of the corresponding virtual channel.

The minor_channel_num field (8 bits) indicates the minor channel number of the corresponding virtual channel.

Service Map Table

17 is a diagram showing an embodiment of a bitstream syntax of a service map table (hereinafter referred to as "SMT ") according to an embodiment of the present invention.

The SMT according to this embodiment is written in the MPEG-2 private section form, but the scope of the present invention is not limited thereto. The SMT according to the present embodiment includes description information of each virtual channel in one MH ensemble, and other additional information may be included in the descriptor area.

The SMT according to the present embodiment is transmitted from the transmission system to the reception system, including at least one field.

As described above in FIG. 3, the SMT section may be included in the MH TP in the RS frame and transmitted. In this case, the RS frame decoders 170 and 180 of FIG. 1 decode the input RS frame, and the decoded RS frame is output to the corresponding RS frame handlers 211 and 212. Each of the RS frame handlers 211 and 212 forms an MH TP by separating the inputted RS frame in units of rows and outputs it to the MH TP handler 213.

If it is determined that the corresponding MH TP includes the SMT section based on the header of each inputted MH TP, the MH TP handler 213 parses the included SMT section and transmits the SI data in the parsed SMT section to the physical adaptive control signal And outputs it to the handler 216. However, in this case, SMT is not encapsulated in IP datagram.

On the other hand, when the SMT is encapsulated into an IP datagram, the MH TP handler 213 determines that the corresponding MH TP includes an SMT section based on the header of each MH TP inputted, 220. Then, the IP network stack 220 performs IP and UDP processing on the SMT section and outputs the IP and UDP processing to the SI handler 240. The SI handler 240 parses the input SMT section and controls the parsed SI to be stored in the storage unit 290.

On the other hand, examples of fields that can be transmitted through the SMT are as follows.

The table_id field (8 bits) is an 8-bit field for identifying the type of the table, which indicates that the table is SMT (table_id: An 8-bit unsigned integer number indicates that the type of table section being defined in Service Map Table (SMT)).

The ensemble_id field (8 bits) is an ID value associated with the corresponding MH ensemble, and values of 0x00 to 0x3F may be assigned. The value of this field is preferably derived from the parade_id of the TPC data. If the corresponding MH ensemble is transmitted through the primary RS frame, the most significant bit (MSB) is set to '0', and the remaining 7 bits are used as the parade_id value of the corresponding MH parade. If the corresponding MH ensemble is transmitted through the secondary RS frame, the most significant bit (MSB) is set to '1' and the remaining 7 bits are used as the parade_id value of the corresponding MH parade (This 8-bit unsigned integer field in the range 0x00 to 0x3F Ensemble ID associated with this MH Ensemble.The value of this field shall be derived from the parade_id carried from the baseband processor of the MH physical layer subsystem by the parade_id of the associated MH Parade for the The least significant 7 bits, and using '0' for the most significant bit when the MH Ensemble is carried over the Primary RS frame, and using '1' for the most significant bit when the MH Ensemble is performed over the Secondary RS frame. .

The num_channels field (8 bits) indicates the number of virtual channels in the SMT section (This 8 bit field specifies the number of virtual channels in this SMT section.).

Meanwhile, the SMT according to the present embodiment provides information on a plurality of virtual channels using a for loop.

The major_channel_num field (8 bits) indicates the major channel number associated with the virtual channel, and may be assigned from 0x00 to 0xFF (this 8-bit unsigned integer field in the range 0x00 to 0xFF represents the major channel number associated with this virtual channel.).

The minor_channel_num field (8 bits) indicates the minor channel number associated with the virtual channel, and may be assigned from 0x00 to 0xFF (this 8-bit unsigned integer field in the range 0x00 to 0xFF represents the minor channel number associated with this virtual channel.).

The short_channel_name field indicates the short name of the virtual channel (the short name of the virtual channel.).

The service_id field (16 bits) indicates a value for identifying the virtual channel service (A 16-bit unsigned integer number that identifies the virtual channel service).

The service_type field (6 bits) indicates the type of service to be transmitted on the virtual channel, as defined in Table 2 below. (A 6-bit enumerated type field that will identify the type of service carried in this virtual channel as defined in Table 2).

0x00 [Reserved] 0x01 MH_digital_television - The virtual channel carries the television programming (audio, video and optional associated data) conforming to ATSC standards 0x02 MH_audio - The virtual channel carries audio programming and optional associated data conforming to ATSC standards 0x03 MH_data_only_service - The virtual channel carries a data service conforming to ATSC standards, but no video or audio component 0x04 to 0xFF [Reserved for future ATSC use]

The virtual_channel_activity field (2 bits) identifies whether the corresponding virtual channel is activated or not. If the most significant bit (MSB) of the virtual_channel_activity field is '1', it indicates that the corresponding virtual channel is active. If the MSB is '0', it indicates that the corresponding virtual channel is not active. If the least significant bit (LSB) is '1', it indicates that the corresponding virtual channel is a hidden channel. If the LSB is '0', it indicates that the corresponding virtual channel is not a hidden channel (A 2-bit enumerated (when set to 1) or inactive (when set to 0) and the least significant bit indicates whether the virtual channel is hidden (when set to 1) or not (when set to 0).

The num_components field (5 bits) indicates the number of the IP stream component on the virtual channel (This 5-bit field specifies the number of IP stream components in this virtual channel.).

When the IP_version_flag field (1 bit) is set to '1', the source_IP_address field, the virtual_channel_target_IP_address field, and the component_target_IP_address field indicate an IPv6 address, and when set to '0', a source_IP_address field, a virtual_channel_target_IP_address field, and a component_target_IP_address field indicate IPv4 addresses (A 1-bitindicator indicates that the source_IP_address, the virtual_channel_target_IP_address, and the component_target_IP_address fields indicate that the source_IP_address, the virtual_channel_target_IP_address, and the component_target_IP_address fields are IPv4 addresses.

When the source_IP_address_flag field (1 bit) is set, it indicates that the source IP address of the virtual channel exists for a specific multicast source (A 1-bit Boolean flag indicating that when a source IP address of this virtual channel is present for source specific multicast.

When the virtual_channel_target_IP_address_flag field (1 bit) is set, it indicates that the corresponding IP stream component is transmitted through an IP datagram having a target IP address different from virtual_channel_target_IP_address. Therefore, when this flag is set, the receiving system uses component_target_IP_address as the target_IP_address and ignores the virtual_channel_target_IP_address field in the num_channels loop to access the corresponding IP stream component (when the 1-bit Boolean flag indicates that when set, this IP stream The IP address of the IP address of the target is the IP address of the IP address of the virtual address of the IP address.

The source_IP_address field (32 or 128 bits) needs to be interpreted when the source_IP_address_flag is set to '1', but it need not be interpreted if the source_IP_address_flag is not set to '0'. When the source_IP_address_flag is set to '1' and the IP_version_flag field is set to '0', this field indicates a 32-bit IPv4 address indicating the source of the virtual channel. If the IP_version_flag field is set to '1', this field indicates a 32-bit IPv6 address indicating the source of the corresponding virtual channel (This field shall be present if the source_IP_address_flag is set to '1' and shall not present the source_IP_address_flag is This field specifies the 32-bit IPv4 address indicating the source of this virtual channel. If the IP_version_flag field is set to '1', this field specifies 128- bit IPv6 address indicating the source of this virtual channel.

The virtual_channel_target_IP_address field (32 or 128 bits) needs to be interpreted when the virtual_channel_target_IP_address_flag is set to '1', but not when the virtual_channel_target_IP_address_flag is set to '0'. When the virtual_channel_target_IP_address_flag is set to '1' and the IP_version_flag field is set to '0', this field indicates a 32-bit target IPv4 address for the virtual channel. When the virtual_channel_target_IP_address_flag is set to '1' and the IP_version_flag field is set to '1', this field indicates a 64-bit target IPv6 address for the virtual channel. If the corresponding virtual_channel_target_IP_address can not be interpreted, the component_target_IP_address field in the num_channels loop must be interpreted and the receiving system must use component_target_IP_address to access the IP stream component (this field shall be the virtual_channel_target_IP_address_flag is set to '1' If the IP_version_flag field is set to '0', this field specifies the 32-bit target IPv4 address for this virtual channel. field is 128-bit target IPv6 address for this virtual channel. If this virtual_channel_target_IP_address does not present, then the component_target_IP_address field in the num_channels loop will present and the receiver will utilize the component_target_IP_address to access the IP stream components.

Meanwhile, the SMT according to the present embodiment provides information on a plurality of components using a for loop.

The RTP_payload_type field (7 bits) indicates the encoding format of the component according to Table 3 below. This field shall be ignored if the IP stream component is not encapsulated by RTP. (This 7-bit field identifies the encoding format of the component according to Table 3.If the IP stream component is not encapsulated in RTP, this field shall be deprecated.).

Table 3 below shows an example of the RTP Payload Type.

RTP_payload_type Meaning 35 AVC video 36 MH audio 37-72 [Reserved for future ATSC use]

The component_target_IP_address_flag field (1 bit) indicates that when the flag is set, the corresponding IP stream component is transmitted via an IP datagram having a target IP address different from virtual_channel_target_IP_address. When this flag is set, the receiving system uses component_target_IP_address as the target IP address to access the corresponding IP stream component and ignores the virtual_channel_target_IP_address in the num_channels loop (when the A-bit Boolean flag indicates that when set, this IP stream component The IP address of the target IP address to be accessed is the IP address of the virtual IP address of the virtual IP address of the virtual IP address of the virtual IP address.

The component_target_IP_address field (32 or 128 bits) indicates that the IP_version_flag field is set to '0', this field indicates a 32-bit target IPv4 address for the corresponding IP stream component. If the IP_version_flag field is set to '1', this field indicates a 128-bit target IPv6 address for the corresponding IP stream component (When IP_version_flag field is set to '0', this field is set to 32-bit target IPv4 address for this IP stream component.When the IP_version_flag field is set to '1', this field specifies the 128-bit target IPv6 address for this IP stream component.

The port_num_count field (6 bits) indicates the number of the UDP port associated with the corresponding IP stream component. The target UDP port number value is incremented by 1, starting from the value of the target_UDP_port_num field. For the RTP stream, the target UDP port number is incremented by two, starting from the value of the target_UPD_port_num field, in order to include the RTCP stream associated with the RTP stream (this field indicates the number of UDP ports associated with this IP stream component.The values of the target UDP port numbers shall start from the target_UDP_port_num field and shall be incremented by one.For RTP streams and the target UDP port numbers shall start from the target_UPD_port_num field and shall be incremented by two to incorporate RTCP streams associated with the RTP streams.

The target_UDP_port_num field (16 bits) indicates the target UDP port number for the corresponding IP stream component. For the RTP stream, the value of target_UDP_port_num is an even number, and the next higher value represents the target UDP port number of the associated RTCP stream (A 16-bit unsigned integer field, which represents the target UDP port number for this IP stream component. , the value of target_UDP_port_num shall be even, and the next higher value shall represent the target UDP port number of the associated RTCP stream.

The component_level_descriptor () indicates a descriptor providing additional information about the corresponding IP component (Zero or more descriptors providing additional information for this IP stream component, may be included).

virtual_channel_level_descriptor () indicates a descriptor providing additional information about the virtual channel (Zero or more descriptors providing additional information for this virtual channel, may be included).

The ensemble_level_descriptor () indicates a descriptor that provides additional information on the MH ensembles described by the SMT (Zero or more descriptors providing for the MH Ensemble which SMT describes, may be included.).

18 is a diagram showing the syntax of the MH Audio Descriptor according to the embodiment of the present invention.

The MH_audio_descriptor () should be used as the component_level_descriptor in the SMT when there is one or more audio services present as a component of the current event. This teller can tell you the type of audio language and whether it is in stereo mode. If there is no audio service associated with the current event, MH_audio_descriptor () is preferably not interpreted for the current event (The MH_audio_descriptor is used as a component_level_descriptor of the SMT when there is one or more audio services present as a component of the current event.This enables, for example, announcement of audio language and stereo mode.If there is no audio service associated with the current event, then the MH_audio_descriptor will not be present for that event.

The fields shown in FIG. 18 will be described in detail as follows.

The descriptor_tag field (8 bits) indicates that the corresponding descriptor is MH_audio_descriptor () (This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_audio_descriptor.).

The descriptor_length field (8 bits) indicates the length in bytes from the end of this field to the end of the descriptor (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The channel_configuration field (8 bits) indicates the number and configuration of the audio channel. The values from 1 to 6 indicate the number and configuration of the audio channel specified in the "Default bit stream index number" on table 42 of ISO / IEC 13818-7: 2006. Table 42. ISO / IEC 13818-7: 2006.All other values are indicative of the number of audio channels as given for " default bit stream index number " and configuration of audio channels is undefined.).

The sample_rate_code field (3 bits) indicates the sample rate of the encoded audio (This is a 3-bit field which indicates the sample rate of the encoded audio. The indication may be one specific sample rate, A set of values that include the sample rate of the encoded audio as defined in Table A3.3 of ATSCA / 52B.).

The lower 5 bits of the bit_rate_code field (6 bits) indicate the nominal bit rate. If the most significant bit is '0', the corresponding bit rate is correct. If the most significant bit is '1' The rate refers to the upper bound defined in Table A3.4 of ATSC A / 53. (This is a 6-bit field. The lower 5 bits indicate a nominal bit rate.The MSB indicates whether the indicated bit rate is exact = 0) or an upper limit (MSB = 1) as defined in Table A3.4 of ATSCA / 53B.

The ISO_639_language_code field (3 bytes: 24 bits) indicates the language used for the audio stream component. If there is no language specified for the audio stream component, set each byte value to 0x00 (This 3-byte (24 bits) field, in conformance with ISO 639.2 / B [ component.In case of no language specified for this audio stream component, each byte should have the value 0x00.).

19 is a diagram showing a syntax of an MH RTP payload type descriptor according to an embodiment of the present invention.

The MH_RTP_payload_type_descriptor () indicates the type of the RTP payload, and exists only when the RTP_payload_type value in the num_components loop of the SMT has a value of 96 to 127. And this descriptor is used as a component_level_descriptor of SMT.

MH_RTP_payload_type_decryptor matches the RTP_payload_type value to the MIME type. As a result, the receiving system may collect the encoding format of the RTP-encapsulated IP stream component (The MH_RTP_payload_type_descriptor shall present and only if the value of RTP_payload_type in the num_components loop of the SMT is a dynamic value in the range of 96 -127.When present, the MH_RTP_payload_type_decryptor shall be used as a component_level_descriptor of the SMT.The MH_RTP_payload_type_de cryptor translates a dynamic RTP_payload_type value into a MIME type, so that the receiver can gather the encoding format of the IP stream component, encapsulated in RTP.).

Details of the fields included in the MH_RTP_payload_type_descriptor () are as follows.

The descriptor_tag field (8 bits) indicates that the corresponding descriptor is MH_RTP_payload_type_descriptor (). This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_RTP_payload_type_descriptor.

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor. (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The RTP_payload_type field (7 bits) indicates the encoding format of the IP stream component, and the RTP_payload_type value has a value ranging from 96 to 127 (this 7-bit field identifies the encoding format of the IP stream component, where the value of this RTP_payload_type is in the dynamic value range 96-127.).

The MIME_type_length field indicates the size of the MIME type (this field specifies the length (in bytes) of the MIME_type.).

The MIME_type field indicates a MIME type corresponding to the encoding format of the IP stream component described by this MH_RTP_payload_type_descriptor (). The MIME_type field describes the MH_RTP_payload_type_descriptor describing the encoding format of the IP stream component.

20 is a diagram showing a syntax of an MH Current Event Descriptor according to an embodiment of the present invention.

The MH_current_event_descriptor () is used as a virtual_channel_level_descriptor in the SMT. This descriptor provides basic information (e.g., current event start time, duration time, title) about the current event transmitted on the virtual channel (The MH_current_event_descriptor, when present, when used as a virtual_channel_level_descriptor of the SMT .The MH_current_event_descriptor provides the basic information on the current event carried through this virtual channel (current event start time, duration and title).

Details of each field included in the MH_current_event_descriptor are as follows.

The descriptor_tag field (8 bits) is a field indicating that this descriptor is MH_current_event_descriptor (). (This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_current_event_descriptor.)

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor. (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The current_event_start_time field (32 bits) indicates the start time of this event (A 32-bit unsigned integer representing the start time of the current event as the number of GPS seconds since 00:00:00 UTC, January 6, 1980).

The current_event_duration field (24 bits) indicates the duration of this event. (A 24-bit field contains the duration of the current event in hours, minutes, seconds.Format: 6 digits, 4-bit BCD = 24 bits.)

The title_length field indicates the size of the title_text. (This field specifies the length (in bytes) of the title_text.Value 0 means that no title exists for this event.).

The title_text field indicates the title of the corresponding event. (The event title in the format of a multiple string structure as defined in ATSC A / 65C [x].).

21 is a diagram showing a syntax of an MH Next Event Descriptor according to an embodiment of the present invention.

The MH_next_event_descriptor () is used as a virtual_channel_level_descriptor of the SMT. The MH_next_event_descriptor () provides basic information (for example, a future event start time, a duration, a title) on a future event transmitted through the corresponding virtual channel (The optional MH_next_event_descriptor, may present as a virtual_channel_level_descriptor of the SMT.The The MHnext event descriptor provides the basic information on the next event, which is the next event start time, duration and title.

Details of each field included in the MH_next_event_descriptor are as follows.

The descriptor_tag field (8 bits) indicates that this descriptor is MH_next_event_descriptor (). This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_next_event_descriptor.

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor. (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The next_event_start_time field (32 bits) represents the start time of the future event (A 32-bit unsigned integer representing the start time of the next event as the number of GPS seconds since 00:00:00 UTC, January 6, 1980).

The next_event_duration field (24 bits) indicates the duration of the future event (A 24-bit field containing the duration of the next event in hours, minutes, seconds. Format: 6 digits, 4-bit BCD = 24 bits).

The title_length field indicates the size of the title_text. (This field specifies the length (in bytes) of the title_text.Value 0 means that no title exists for this event.).

The title_text field indicates the title of the corresponding event. (The event title in the format of a multiple string structure as defined in ATSC A / 65C [x].).

22 is a diagram showing a syntax of an MH System Time Descriptor according to an embodiment of the present invention.

The MH_system_time_descriptor () is used as the ensemble_level_descriptor of the SMT. The MH_system_time_descriptor () provides current time and date information. In addition, the MH_system_time_descriptor provides time zone information for a transmission system that transmits a received broadcast stream in consideration of a mobile environment (The MH_system_time_descriptor, when present, used as an ensemble_level_descriptor of the SMT.The MH system time descriptor provides the current date and time of day information. In addition, taking the mobile / portable characteristic of MH, the MH system time descriptor provides the time zone information for where the transmitter of the broadcast stream is located.

Details of each field included in the MH_system_time_descriptor () are as follows.

The descriptor_tag field (8 bits) indicates that this descriptor is MH_system_time_descriptor () (This 8-bit unsigned integer shall have the value TBD, identifying this descriptor as MH_system_time_descriptor.).

The descriptor_length field (8 bits) indicates the size from this field to the last field in this descriptor (This 8-bit unsigned integer specifies the length (in bytes) immediately following this field.

The system_time field (32 bits) represents the current time on the GPS (A 32-bit unsigned integer representing the current system time as the number of GPS seconds since 00:00:00 UTC, January 6th, 1980.).

The GPS_UTC_offset field (8 bits) indicates the current offset between GPS and UTC. To convert the GPS time to UTC time, subtract GPS_UTC_offset from GPS (An 8-bit unsigned integer that defines the current offset in whole seconds between GPS and UTC time standards.To convert GPS time to UTC, 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 may be added (or subtracted), and the GPS_UTC_offset will reflect the change.

The time_zone_offset_polarity field (1 bit) indicates whether the time for the time zone of the broadcast station position precedes or follows UTC. If this field is '0', it means that the time in the current time zone is ahead of UTC, so the value of time_zone_offset is added to UTC. On the other hand, if this field is '1', it means that the time in the current time zone is behind UTC, so that the time_zone_offset value is added in UTC (an one-bit indicator that indicates whether or not the time zone is the broadcast This field indicates that the current time zone is the UTC (ie, the time_zone_offset is added to UTC) and when set to '1', this field indicates that the station is located or lags UTC.When set to '0' that is the current time zone lags UTC.

The time_zone_offset field (31 bits) represents the time offset value for the broadcast station position as compared to UTC (representing the time offset of the time zone in GPS seconds, where the broadcast station is located, compared to UTC .).

The daylight_savings field (16-bit) provides information about daylight saving time (Daylight Savings Time control bytes.Refer to Annex A of ATSC-A / 65C with amd. # 1 [x], for the use of these two bytes.) .

The time_zone field (5x8 bits) represents the time zone for the transmission system transmitting the received broadcast stream.

23 is a diagram for explaining the segmentation and encapsulation of the SMT according to the present invention.

According to the present invention, the SMT is encapsulated in UDP with the target IP address and the target UDP port number on the IP datagram. That is, the SMT is segmented into a predetermined number of sections, then encapsulated into a UDP header, and then encapsulated into an IP header.

In addition, the SMT section provides signaling information for all virtual channels included in the MH ensemble containing the corresponding SMT section. And the SMT section describing the MH ensemble includes at least one in each RS frame belonging to the corresponding MH ensemble. And each SMT section is distinguished by the ensemble_id included in each section. In the embodiment of the present invention, the receiving system recognizes the target IP address and the target UDP port number so that the receiving system can parse the target IP address and the target UDP port number without requesting additional information.

24 is a flow diagram illustrating accessing a virtual channel using FIC and SMT in accordance with an embodiment of the present invention.

That is, one physical channel is tuned (S501), and if there is an MH signal in the tuned physical channel (S502), the MH signal is demodulated (S503). Then, the FIC segments are collected in units of subframes from the demodulated MH signal (S504, S505).

In the present invention, one FIC segment is inserted into one data group and transmitted. That is, the FIC segment corresponding to each data group describes the service information of the MH ensemble to which the corresponding data group belongs. When the FIC segments are deinterleaved by collecting in units of subframes, all the service information of the physical channel through which the corresponding FIC segment is transmitted can be obtained. Therefore, the receiving system can acquire the channel information of the corresponding physical channel during the sub frame period after the physical channel tuning. When the FIC segments are collected by the steps S504 and S505, the broadcast stream to which the corresponding FIC segment is transmitted is identified (S506). The broadcast stream can be identified, for example, by parsing the transport_stream_id field of the FIC body configured by collecting the FIC segments.

In addition, an ensemble identifier, a major channel number, a minor channel number, and channel type information are extracted from the FIC body (S507). Then, only the slots corresponding to the ensemble desired to be received are acquired by the time slicing method using the extracted ensemble information to configure an ensemble (S508).

Then, the RS frame corresponding to the desired ensemble is decoded (S509), and an IP socket is opened to receive the SMT (S510).

The SMT is encapsulated in UDP with a target IP address and a target UDP port number on an IP datagram as an example. That is, the SMT is segmented into a predetermined number of sections, then encapsulated into a UDP header, and then encapsulated into an IP header. In the embodiment of the present invention, the receiving system knows the target IP address and the target UDP port number so that the receiving system parses the SMT section and the descriptors of each SMT section without requesting additional information (S511).

The SMT section provides signaling information for all the virtual channels included in the MH ensemble including the corresponding SMT section. And the SMT section describing the MH ensemble includes at least one in each RS frame belonging to the corresponding MH ensemble. And each SMT section is distinguished by the ensemble_id included in each section.

Also, each SMT provides IP access information of each virtual channel belonging to the corresponding MH ensemble including each SMT. Also, the SMT provides IP stream component level information necessary for the service of the corresponding virtual channel.

Accordingly, an IP stream component belonging to a virtual channel desired to be received is accessed using the information parsed from the SMT (S513), and a service for the virtual channel is provided to the user (S514).

Hereinafter, transmission and reception of service data in a format different from that of existing MH format data in the MH system will be described in another embodiment of the present invention. In this case, the service of the different format includes a MediaFLO service for implementing a subscription base mobile broadcast service through a single physical channel. Hereinafter, Flow will be described as an example. It should be noted, however, that the present invention is not limited thereto.

In order to transmit / receive data for the media flow service in the MH system, the data for the media flow service must be changed to a format for transmission / reception in the MH system. To this end, interfaces between layers on existing MH systems and layers for media flow services must be interfaced with each other.

Hereinafter, a protocol stack for transmitting and receiving data for media flow service in the MH system will be described.

25 shows a protocol stack of an MH system according to an embodiment of the present invention.

25, an interface is defined between an MH Transport Layer (MH Transport Layer) and a media adaptation layer of a media flow to transmit and receive the media flow service data in the MH system, (Signaling Data).

One embodiment of the protocol stack in the MH system shown in FIG. 25 is that data for a media flow service as a whole is transmitted in synchronization with the media flow service, such as a sync layer, a file delivery layer, Layer (IP Adaptation Layer) and transmitted through the MH transport layer and the MH physical layer. Here, the protocol stack also handles the signaling, that is, the MH Signaling Layer, in connection with the interface in the MH system of the media flow service data.

The protocol stack shown in FIG. 25 includes a media codec layer for transmitting data for a media flow service, a non-real time files layer, and an IPv4 / IPv6 layer A Sync Layer, a File Delivery Layer, and an IP Adaptation Layer for interfacing data for a media flow service downloaded from the respective layers to an MH system, ).

In the above, the media codec layer is a layer for service for real-time applications, the non-real time files layer is a layer for service for file-based applications, and the IPv4 / These are the layers for the service. At this time, a more detailed description of each layer related to the Media Flow service will be referred to, for example, TIA-1130 (Media Adaptation Layer), and will be omitted here for the sake of convenience. In connection with the media flow service, a non-real time files layer and a file delivery layer, an IPv4 / IPv6 layer and an IP adaptation layer (IP) layer Adaptation Layer) can be defined and transmitted in the existing MH format.

In the protocol stack, the FIC layer and the MH-signaling layer are layers for signaling in the MH system. In addition, the MH transport layer and the MH physical layer are layers for packetizing and transmitting data for the media flow service interfaced.

A more detailed description of the interface and signaling associated with the protocol stack of the MH system will be described later in that section.

26 illustrates a conceptual block diagram of an MH receiver in accordance with another embodiment of the present invention.

26, an MH receiver according to another embodiment of the present invention includes a flow packet handler 2619, an RS frame handler 2620, a physical parameter handler 2621, A FIC handler 2622, a non-IP MH-Signaling Decoder 2625, an IP-based MH-Signaling Decoder 2626, A Sync Layer Handler 2632, a File Delivery Layer Handler 2633, an IP Adaptation Layer Handler 2634, an MH-Signaling (DB) 2627, a channel manager 2629, and a service manager 2630.

Hereinafter, a process and configuration for receiving and processing data for a media flow service transmitted in accordance with the protocol stack shown in FIG. 25 in the MH system will be mainly described, and the configuration of the MH receiver The description of the common parts with those of the above-described embodiments is used herein. 26, the dotted line indicates the flow of control data, and the solid line indicates the flow of actual data. Here, the control data refers to a representation collectively referred to as various additional information used for processing data for the media flow service. In addition, each layer described below refers to the layer on the protocol stack of Fig. 25 described above.

The RS-frame handler 2620 processes the RS-frame, which is the output of the MH physical layer. Here, the signaling information related to the media flow service in the processed RS frame is transmitted to the non-IP MH signaling buffer 2623, and the flow packet associated with the media flow service is transmitted to the flow packet handler 2619.

The flow packet handler 2619 receives the flow packet from the RS-frame handler 2620, extracts information about the type in the header of the received flow packet, and outputs the information to the sink layer handler 2632, which will be described later, The file delivery layer handler 2633, and the IP adaptation layer handler 2634, as shown in FIG. The flow packet handler 2619 transmits the received flow packet to be processed by the selected handler.

The physical parameter handler 2621 handles the processing of a physical layer parameter required at a management layer or higher.

The FIC handler 2622 processes the FIC data. In order to process the FIC data, parameters of a physical layer are required. Parameters of the physical layer are decoded by the signaling decoder 2616 in the physical parameter handler 2621 And obtained from the transmitted TPC data.

The non-IP MH-signaling decoder 2625 receives the MH-Signaling information transmitted via the FIC handler 2622 and the non-IP MH-Signaling transmitted in the RS- Information is received and processed.

The IP-based MH-signaling decoder 2626 processes the MH-signaling information transmitted via the FIC handler 2622 and the IP-based MH-signaling information transmitted in the RS-frame do.

The sink layer handler 2632 receives and processes a flow packet including data transmitted from a sync layer of the flow packets constituting the RS-frame from the flow packet handler 2619.

The file delivery layer handler 2633 receives and processes a flow packet including data delivered from a file delivery layer of the flow packets constituting the RS-frame from the flow packet handler 2619.

The IP adaptation layer handler 2634 receives and processes a flow packet including data transmitted from an IP adaptation layer among the flow packets constituting the RS-frame from the flow packet handler 2619.

The MH-signaling database 2627 serves as a database for storing and using signaling data received in the form of non-IP or IP.

The channel manager 2629 manages a user input such as a channel setting with an MH user interface.

The service manager 2630 manages user inputs such as an EPG display and a service setting through an MPG by an MH user interface.

The control data may be transmitted, for example, in a service map table or an electronic service guide (ESG), which will be described later. However, the control data may be transmitted by other methods. In addition, the MH receiver according to another embodiment of the present invention may obtain information required for the control data configuration from other transmitted data. In this regard, the control data may be stored in, for example, the MH-signaling database 2627, stored in a separate storage space, or may be received and used in real time depending on the characteristics of the control data. For example, when the MH receiver uses the media flow service according to a user's request, the MH receiver may store the control data related to the service in the MH-signaling database 2627, a separate secure storage space, And can transmit it to the flow packet handler 2619 or the RS-frame handler 2620. Accordingly, the flow packet handler 2619 and the RS-frame handler 2620 can process the media flow service data using the extracted control data.

Next, the structure of an RS frame and data packet multiplexing according to another embodiment of the present invention will be described. FIG. 27 illustrates a structure of an RS frame including a multiplexed data packet according to another embodiment of the present invention. Referring to FIG.

27 shows an example of a format of an RS frame for transmitting data corresponding to an MH ensemble (MH Ensemble) per MH frame as an output of an MH Physical Layer Subsystem can see.

One RS frame may transmit a plurality of MH services. Data constituting one MH service can be continuously transmitted in one area within an RS frame. Also, one MH service may be composed of a plurality of flow packets.

Here, the RS frame is configured in the form of a two dimensional byte array of 187 x N bytes. Therefore, in the MH transport layer, each row of the RS frame forms an MH transport packet (MHTP).

28 shows a structure of an MH transport packet (MHTP) according to an embodiment of the present invention.

28, one MH transport packet MH TP includes an MH transport packet header (MH TP Header) (2 bytes) and an MH transport packet payload (MH TP MH TP Payload) (N-2 bytes ).

The MH transport packet header (MHTP Header) includes, for example, a Type Indicator field, an Error Indicator field, a Stuff Indicator field, and a Pointer field. Hereinafter, the respective fields will be described.

First, the Type Indicator field (3 bits) indicates the type of data carried in the payload portion of the corresponding MH transport packet. At this time, the field value and its meaning can be defined, for example, as shown in Table 4 below.

Type Indicator Meaning 000 MH Signaling Data 001 IP Datagram 010 Sync Layer Data 011 File Delivery Layer Data 100 IP Adaptation Layer Data 101-111 Reserved

If the value of the Type Indicator field is '000', it means that the data type loaded in the payload of the corresponding MH transport packet is MH signaling data. If the value of the Type Indicator field is '001' , The data type carried in the payload of the corresponding MH transport packet is an IP datagram. If the value of the Type Indicator field is '010', the data type carried in the payload of the corresponding MH transport packet is the sink If the value of the Type Indicator field is '011', it means that the data type loaded in the payload of the corresponding MH transport packet is the file delivery layer data, and if the value of the Type Indicator field is '100' , It means that the data type carried in the payload of the corresponding MH transport packet is the IP adaptation layer data. Here, if the value of the Type Indicator field is '101-111', it is reserved for future use.

Also, the type of the service transmitted and received in the MH system can be distinguished from the value of the Type Indicator field. For example, when the value of the Type Indicator field is '010' to '100', the receiver can know that the data for the media flow service is transmitted through the corresponding MH transport packet from the field value. If the field value is '000', that is, the MH signaling data or '001', that is, in the case of an IP datagram, the MH transport packet includes the MH transport packet in the existing MH format, .

The Error Indicator field (1 bit) is an indicator for indicating whether an error exists in the corresponding MH transport packet. At this time, for example, if the value of the Error Indicator field is '0', it indicates that an error is not found, and '1' is an indication that an error is found.

The Stuff Indicator field (1 bit) is an indicator indicating the presence or absence of stuffing bytes in the corresponding MH transport packet. If the value of the Stuff Indicator field is '0', for example, it indicates that there is no stuffing byte. If the value of the Stuff Indicator field is '1', it indicates that the beginning of the packet payload is a stuffing field. Or &lt; / RTI &gt; Here, the stuffing byte indicates the K bytes of stuffing that are present in one MH transport packet if necessary, and the stuffing field including the K bytes may be the beginning of the packet payload. If the length of the stuffing field is 1 byte, the value of the first byte of the stuffing field will be set to '0xFF'. If the length of the stuffing field is 2 bytes, the value of the first byte of the stuffing field may be set to '0xFE', and the value of the second byte may be '0xFF'. Also, if the length of the stuffing field is 2 bytes or more, the value of the first two bytes of the field may indicate the number of bytes in the stuffing byte field.

The Pointer field (11 bits) indicates the start point of a new packet in the payload of the corresponding MH transport packet. Here, the starting point of the new packet may indicate the starting point of the flow packet header, for example.

However, the values of the respective fields in the above-described MH transport packet header are illustrated for convenience of description and are not limited thereto.

Next, the one MH transport packet MH TP includes a stuffing portion (K bytes) and a payload portion (N-2-K bytes) in addition to the MH transport packet header portion described above. At this time, the sum of the stuffing portion and the payload portion may be referred to as a payload.

The RS frame structure in which a plurality of data packets for the media flow service shown in FIG. 27 are multiplexed will be described. In the RS frame, data packets divided into A to K are multiplexed.

In the RS frame structure, a column named 'RS frame header' on the left side describes a type of data packet included in the RS frame payload part of the corresponding row. For example, in the case of the RS frame shown in FIG. 27, the RS frame header portion of the first row is denoted by A, which includes the signaling data packet A 'in the payload portion of the first row . If the RS frame header of a specific line of the RS frame is represented by B to D in the same manner as described above, it can be seen that the RS frame payload of the corresponding line includes the data packet indicated by B to D.

FIG. 27 shows an example of multiplexing data for four services (Data for Service 1-4). That is, the service 1 describes a sync layer packet, the service 2 a file delivery layer packet, the service 3 an IP adaptation layer packet, and the service 4 a service including the layer packet. In addition, each service packet can be distinguished from another through a different flow packet.

Next, packetization and transmission of data related to the sync layer with respect to the media flow service will be described. FIG. 29 illustrates a packetization process in a sync layer according to an embodiment of the present invention.

The sync layer serves as an interface between a media codec layer and an MH transport layer for data transmission for real-time applications in the MH system as described above . At this time, the real-time application includes, for example, video, audio, timed text, and the like.

FIG. 29 illustrates a process of packetizing a media frame downloaded from a media codec layer in a sync layer. Referring to FIG.

The sink layer downloads media frames of varying length from the media codec layer. A sync header is attached to each of the downloaded media frames to form a sync layer packet. At this time, if necessary, a packet formed by attaching a header to a sync layer adaptation frame (SLAF) may be inserted between the sync layer packets configured as described above.

Here, the sync header includes information indicating a media type (MT), general media header (MCH), media specific header (MSH), and sync layer And adaptation type information (SLAT: Sync Layer Adaptation Type). For example, in the case of a header attached in the process of packetizing a media frame, information (MT) indicating a media type, information (MCH) about a general media header, and media specific header information (MSH) are included in FIG. do. In the case of a header for packetization of a sync layer adaptation frame SLAF, information MT indicating a media type and sync layer adaptation type information SLAT are included.

30 illustrates a process of packetizing sync layer packets at the MH transport layer according to an embodiment of the present invention.

30 illustrates a process of interfacing data for real-time applications in a sink layer via a media codec layer and packets in a transport format format suitable for an MH system in an MH transport layer according to the present invention. In this case, the process of interfacing to the above-mentioned process is described with reference to FIG. 29. Hereinafter, a process of packetizing packets for transmission in the MH transport layer after the interface will be described.

Referring to FIG. 30, the MH transport layer packetizes at least one flow packet (N-2 bytes) into one MH transport packet (N bytes) by attaching an MH transport packet header (2 bytes). Here, the flow packet is again divided into a flow packet header and a flow packet payload. 31, the flow packet payload (N-2-5 bytes) has a variable length. In the above-mentioned sink layer of Fig. 29, the packetized sync layer packet is divided And a plurality of sync layer packets corresponding to the length may be configured as one flow packet payload. In addition, the flow packet payload may include a length field (16 bits) regarding the length of each sync layer packet included in the corresponding flow packet payload.

For example, the type indicator field may be '000' in the header of the first MH transport packet among the above-configured MH transport packets. When the flow packet divided in the above is N-2 bytes or less, a stuffing byte can be added. Here, the pointer field of the MH transport packet header can indicate the start point of the flow packet header.

As will be described later, the flow packet is divided into a flow packet header and a flow packet payload. The flow packet payload includes a sink layer packet packetized in a sync layer, that is, a sync packet composed of a sync packet header and a media frame And length information for the length.

Referring to FIG. 30, one MH transport packet (MHTP) includes at least one flow packet, and one flow packet may include a plurality of sync layer data packets.

Here, if the length of each sync layer data packet is not known on the receiving side, the length value can not be processed even if it is received, and information on the length of each packetized sync layer data packet .

FIG. 31 illustrates a format of a flow packet according to an embodiment of the present invention. As described above, a flow packet is divided into a flow packet header and a flow packet payload.

The flow packet header will be described below. The Flow Packet header includes a Flow_ID (entifier) field (20 bits) for identifying a flow packet to which the flow packet belongs, a CHECKSUM_ACTIVE field (1 bit) for indicating whether a CRC (Cyclic Redundancy Check) A NUM_SYNC_PKTS field (1 bit) indicating the number of sync layer packets to be transmitted through the corresponding flow packet payload, an FD_FLOW_TYPE field (1 bit) indicating the type of the corresponding flow packet, FASB_ALLOWED field (1 bit) indicating whether or not an encryption is applied to the flow packet payload, and a STREAM_ENCRYPTION_ACTIVE field (16 bits) indicating whether or not an encryption is applied to the flow packet payload. Here, with respect to the FASB_ALLOWED field, if the corresponding flow packet is a Real Time Application Flow Packet, the field value may be set to 'FALSE'.

In the above description, it is obvious that the values of the respective fields are arbitrarily set by the applicant and can be expressed using different values from the above.

The above-mentioned flow packet is packetized into the MH transport packet (MH TP) in the MH transport layer and transmitted through the MH physical layer.

Accordingly, the RS frame handler 2620 of the receiver shown in FIG. 26 searches the MH transport packet header configured as described above, parses the MH transport packet whose type indicator in the header is '001' To the flow packet handler 2619, and the flow packet handler 2619 extracts the corresponding sink layer packets and transmits them to the sink layer handler 2632.

Following packetization of the above-described Sync Layer Packets, packetization process of File Delivery Layer Packets will be described. FIG. 32A shows a configuration in which an FDP (File Delivery Protocol) and an FDCP (File Delivery Control Protocol) data packet are packetized at the MH transport layer according to an embodiment of the present invention.

The File Delivery Layer provides a non-real time files layer and an MH transport layer for data transmission for a non-real time application. ) As an interface.

Here, the file delivery layer can transfer FDDP packets for FDP packets and File Delivery Control to different MHP transport layers, respectively. At this time, each of the FDP and FDCP packets is packetized into an MH transport packet (MH TP), and each configuration is the same as in FIG. 32A (FDP packet and FDCP packet).

Here, the process or method of packetizing in the MH transport layer of the FDP and FDCP packets is similar to that described above with respect to the sync layer packet in FIGS. 29 to 31, And the detailed description thereof will be omitted here. Therefore, referring to FIG. 32B, similar to the above-described sync layer, field values of a flow header will be applied. In addition, a flow packet payload having a variable length includes a length and an FDP packet or a length and an FDCP packet.

Lastly, the packetization process of the IP adaptation layer packet will be described following the packet related to the sync layer and the file delivery layer. 33 illustrates packetization of an IP datagram packet at the MH transport layer according to an embodiment of the present invention.

The IP adaptation layer is an interface between an IPv4 / IPv6 layer and an MH transport layer for data transmission for an IP datacast application. Interface.

The IP adaptation layer can transport IP datagrams into different flow packets with the MH transport layer. Here, the IP datagram is packetized into an MH transport packet (MH TP). FIG. 33 shows a configuration of the packetized IP datagram.

The method of packetizing the IP datagram in the MH transport layer also uses a sync layer packet (Sync Layer Packet) in common with the above description, and a detailed description thereof will be omitted. Each value constituting the header of Fig. 34 will also be defined as an appropriate value according to the IP datagram. The flow packet payload also includes an IP datagram and length information about the IP datagram.

Next, a service map table (SMT-MH: Service Map Table-MH) according to another embodiment of the present invention will be described with respect to signaling information on data for the media flow service. 35 illustrates a bitstream syntax of a service map table according to another embodiment of the present invention.

The MH transport packet MH TP set to "Type Indicator = '000'" among the MH transport packets MH TP transmitted through the RS frame configured as shown in FIG. 27 is normally located at the beginning of the RS frame The MH transport packet located at the beginning of the RS frame is transmitted with a service map table including signaling data describing the data structure of the corresponding RS frame.

The service map table transmits information on the flow packets belonging to the MH services transmitted through the corresponding RS frame to the receiver. Here, the service map table may be processed in the "Non-IP MH Signaling Decoder 2625 ", for example, of the MH receiver structure of FIG. 26 described above.

In addition, the service map table transmits information on the start and end of the MH transport packets belonging to the MH services transmitted through the corresponding RS frame, so that even if there is no ID value corresponding to the corresponding MH services in the receiver, Frame handler) 2620 to extract desired MH service data.

Another embodiment related to the service map table in FIG. 35 is prepared according to the MPEG-2 short form, but it is not necessary to follow the short form. However, the description of the overlapping portions in the service map table of FIG. 17, which is one embodiment of the present invention, will be omitted and will be mainly described in connection with the present embodiment.

Referring to FIG. 35, the first_MH_TP_num field indicates a first MH transport packet among a plurality of MH transport packets including a flow packet, and the last_MH_TP_num field indicates a last MH transport packet.

Hereinafter, a process of extracting and processing data transmitted to an MH transport layer (MHTP layer) to provide broadcast or service in an MH receiver will be described. 36 to 38 illustrate an embodiment of a data processing process according to the present invention.

When the MH receiver is powered on, it decodes the received broadcast or service RS frame for service (S3601).

Then, a service map table (SMT-MH) including signaling information of data for a media flow service is extracted from the decoded RS frame (S3602).

Here, among the configurations of the MH receiver shown in FIG. 26, for example, the RS frame handler 2620 can perform steps 3601 to 3602 described above.

If the service map table including the signaling information is extracted in step S3602, the first_MH_TP_num and last_MH_TP_num fields are parsed from the extracted service map table section (S3503).

Here, in the configuration of the MH receiver shown in FIG. 26, for example, the non-IP MH signaling decoder 2625 can perform the above step S3603.

In steps S3602 and S3603, the base station extracts the MH transport packets from the RS frame based on the extracted service map table and information on the parsed first_MH_TP_num and last_MH_TP_num fields (S3604).

The header of the extracted MH transport packet is parsed (S3605).

Here, in the configuration of the MH receiver shown in FIG. 26, for example, the RS frame handler 2620 can perform the above steps S3604 to S3605.

In step S3605, a Type Indicator in the header of the parsed MH transport packet is extracted. The flow packet header is extracted and parsed based on the extracted type indicator (S3606). For example, if the extracted Type Indicator value is '010', it indicates a flow packet including a sync layer packet. If the extracted Type Indicator value is '011', a flow including FDP and FDCP packets Packet, and if the extracted Type Indicator value is '100', indicates a flow packet including IP datagram packets.

In the example shown in FIG. 36, the value of the Type Indicator is '010', that is, a flow packet including a sync layer packet will be described as an example.

Extracts the length information of each of the sync layer packets included in the corresponding flow packet payload from the flow packet header parsed in step S3606, and extracts each of the sync layer packets according to the extracted length information (S3607).

Here, among the configuration of the MH receiver in FIG. 26, for example, the flow packet handler 2619 may perform steps 3606 to 3607. FIG.

The sync layer action is performed using the sync layer packets extracted in step S3607 (S3608).

Here, the sink layer handler 2632 may perform the above step 3608 in the configuration of the MH receiver in FIG. 26, for example.

By performing the above-described process, a sync layer packet for the media flow service included in the MH transport packet can be processed and provided to the user according to the protocol stack of the MH system.

Next, a case in which the extracted Type Indicator value indicates '011', that is, a flow packet including FDP and FDCP packets, will be described with reference to FIG. In Fig. 37, the description of Fig. 36 described above is equally applied before step 3706. In step 3706, description will be made below.

Accordingly, if FDP and FDCP packets other than the sync layer packets are included in the corresponding flow packet according to the value of the extracted Type Indicator, the header of the corresponding flow packet including the FDP and FDCP packets is extracted and parsed (S3706) .

Extracts length information about each FDP and FDCP packets included in the corresponding flow packet payload from the flow packet header parsed in step S3706, and extracts each FDP and FDCP packets according to the extracted length information (S3707) .

Here, among the configuration of the MH receiver shown in FIG. 26, for example, the flow packet handler 2619 may perform steps 3706 to 3707.

The file delivery layer action is performed using the FDP and FDCP packets extracted in step S3707 (S3708).

Here, in the MH receiver configuration shown in FIG. 26, for example, the file delivery layer handler 2633 can perform the above step 3708.

According to the above-described process, the FDP and the FDCP layer packet for the media flow service included in the MH transport packet can be processed and provided to the user according to the protocol stack of the MH system.

Finally, a case in which the value of the extracted Type Indicator indicates '100', that is, a flow packet including IP datagrams, will be described with reference to FIG. 38, the description of FIG. 36 described above is used equally. In the following, description will be made from step 3806.

If the flow packet indicated by the value of the extracted Type Indicator includes IP datagrams that are not the sync layer packet or the FDP and FDCP packets, the header of the flow packet including the IP datagrams is extracted and parsed (S3806).

Extracts the length information about each IP datagram included in the corresponding flow packet payload from the flow packet header parsed in step S3806, and extracts each IP datagram using the extracted length information (S3807).

The IP adaptation layer action is performed using the IP datagrams extracted in step 3807 (S3808).

By performing the above-described process, the IP datagram for the media flow service included in the MH transport packet can be processed and provided to the user according to the protocol stack of the MH system.

38, the MH receiver configuration block for performing each step is the same as the configuration block described in Fig.

According to the present invention, a protocol stack capable of transmitting and receiving service data in a format other than the existing MH format can be defined.

As a result, according to the present invention, a variety of broadcasting services can be provided through the MH system, and various services can be provided to the user, thereby widening the selection range.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the equivalents of the claims, as well as the claims.

1 is a block diagram showing a configuration of a receiving system according to an embodiment of the present invention;

2 is a diagram showing an embodiment of a structure of a data group according to the present invention.

3 is a diagram illustrating an RS frame according to an embodiment of the present invention.

4 is a diagram showing an example of an MH frame structure for transmission of mobile service data according to the present invention.

5 is a diagram showing an example of a VSB frame structure

6 shows a mapping example of the first four slot positions of a subframe for one VSB frame in a spatial domain

7 shows a mapping example of the first 4-slot position of a subframe for one VSB frame in the time domain

8 shows an example of a data group allocation procedure to be assigned to one subframe among five subframes constituting an MH frame

9 is a diagram showing an example of assigning a single parade to one MH frame

10 shows an example of transmitting three parades (Parade # 0, Parade # 1, Parade # 2) to one MH frame

FIG. 11 shows an example in which the allocation process of the three parades in FIG. 10 is extended to five subframes in one MH frame

12 is a diagram illustrating a data transmission structure according to an embodiment of the present invention, in which signaling data is included in a data group and transmitted

13 is a diagram illustrating a layered signaling structure according to an embodiment of the present invention.

Figure 14 illustrates an embodiment of an FIC format according to the present invention;

15 is a diagram showing an embodiment of a data structure of an FIC segment according to the present invention;

16 is a diagram showing an embodiment of a bitstream syntax structure for a payload of an FIC segment when the FIC type field value is '0' according to the present invention.

17 is a diagram showing an embodiment of a bitstream syntax of a service map table according to an embodiment of the present invention;

18 is a diagram showing the syntax of the MH Audio Descriptor according to the embodiment of the present invention

19 is a diagram showing a syntax of an MH RTP payload type descriptor according to an embodiment of the present invention.

20 is a diagram showing a syntax of an MH Current Event Descriptor according to an embodiment of the present invention;

21 is a diagram showing the syntax of the MH Next Event Descriptor according to the embodiment of the present invention

22 is a diagram showing a syntax of an MH System Time Descriptor according to an embodiment of the present invention;

23 is a view for explaining the segmentation and encapsulation of the SMT according to the present invention;

FIG. 24 is a flow diagram illustrating accessing a virtual channel using FIC and SMT in accordance with an embodiment of the present invention.

25 shows a protocol stack of an MH system according to an embodiment of the present invention

26 is a conceptual block diagram of an MH receiver according to another embodiment of the present invention

27 illustrates a structure of an RS frame including a multiplexed data packet according to another embodiment of the present invention

28 shows a structure of an MH transport packet (MHTP) according to an embodiment of the present invention

29 illustrates a process of packetizing in the sink layer according to an embodiment of the present invention

30 shows a process of packetizing sync layer packets at the MH transport layer according to an embodiment of the present invention

31 is a diagram showing an embodiment of the flow packet format of FIG. 30

32A is a diagram showing a configuration in which an FDP (File Delivery Protocol) and an FDCP (File Delivery Control Protocol) data packet are packetized at the MH transport layer according to an embodiment of the present invention
FIG. 32B shows an embodiment of the flow packet format of FIG. 31A

33 illustrates packetization of an IP datagram packet at the MH transport layer according to an embodiment of the present invention
FIG. 34 shows an embodiment of the flow packet format of FIG. 33

35 shows a bitstream syntax of a service map table according to another embodiment of the present invention

36 to 38 illustrate an embodiment of a data processing process according to the present invention

Description of the Related Art

100: MH Baseband Processor

200: MH Management Processor

300: MH Presentation Processor

Claims (20)

Encoding broadcast service data for a broadcast service; And And transmitting a broadcast signal including the encoded broadcast service data, Wherein the broadcast signal includes signaling data and a signaling table, Wherein the signaling data includes information for quick acquisition of the broadcast service and a transmission parameter, the transmission parameter includes encoding information of the broadcast service data, Wherein the signaling table includes service identification information for identifying the broadcast service, access information for accessing the broadcast service, and information for indicating whether the broadcast service is active. Processing method. The method according to claim 1, The broadcast service data is based on IP (Internet Protocol) Wherein the access information includes information indicating whether an IP address of the broadcast service is included in the signaling table. 3. The method of claim 2, Wherein the access information further includes information indicating whether an IP address of a component included in the broadcast service is included in the signaling table. 3. The method of claim 2, Wherein the access information further includes information indicating a number of UDP (User Datagram Protocol) ports related to a component included in the broadcasting service. 3. The method of claim 2, Wherein the access information further includes a UDP port number of a component included in the broadcast service. The method according to claim 1, Wherein the signaling table further includes information indicating a number of components included in the broadcast service. delete The method according to claim 1, Wherein the signaling table further comprises information indicating whether the broadcast service is in a hidden state. The method according to claim 1, Wherein the signaling table further includes information indicating a type of the broadcast service. The method according to claim 1, Wherein the transmission parameter further includes information indicating whether information for quick acquisition of the broadcast service is changed. An encoder for encoding broadcast service data for a broadcast service; And And a transmitter for transmitting a broadcast signal including the encoded broadcast service data, Wherein the broadcast signal includes signaling data and a signaling table, Wherein the signaling data includes information for quick acquisition of the broadcast service and a transmission parameter, the transmission parameter includes encoding information of the broadcast service data, Wherein the signaling table includes service identification information for identifying the broadcast service, access information for accessing the broadcast service, and information indicating whether the broadcast service is in an active state. 12. The method of claim 11, Wherein the broadcast service data is IP-based, Wherein the access information includes information indicating whether an IP address of the broadcast service is included in the signaling table. 13. The method of claim 12, Wherein the access information further includes information indicating whether an IP address of a component included in the broadcasting service is included in the signaling table. 13. The method of claim 12, Wherein the access information further includes information indicating a number of UDP ports associated with a component included in the broadcast service. 13. The method of claim 12, Wherein the access information further includes a UDP port number of a component included in the broadcast service. 12. The method of claim 11, Wherein the signaling table further comprises information indicating a number of components included in the broadcast service. delete 12. The method of claim 11, Wherein the signaling table further includes information indicating whether the broadcast service is in a hidden state. 12. The method of claim 11, Wherein the signaling table further comprises information indicating a type of the broadcast service. 12. The method of claim 11, Wherein the transmission parameter further includes information indicating whether information for quick acquisition of the broadcast service is changed.

Images