Method and apparatus for transmitting broadcast, method and apparatus for receiving broadcast.

METHOD OF TRANSMISSION OF A MOBILE DIFFUSION SERVICE AND APPLIANCE

FOR TRANSMISSION OF A MOBILE BROADCASTING SERVICE

TECHNICAL AREA

[0001] The present invention relates to a method and apparatus for transmitting a broadcast, and relates to a method and apparatus for receiving a broadcast, and relates more particularly to a method and apparatus for broadcast transmission to provide a mobile broadcast service.

DISCLOSURE OF THE INVENTION

[0002] The Advanced Television System Committee (ATSC) is a group that sets standards for digital television broadcasting (DTV) in the United States of America among standards for broadcast digital television broadcasting ( Terrestrial DTV). A main point of the standards defined by the ATSC refers to the compression and transmission of audio / video (AV). That is, a video signal is compressed according to the MPEG2 standard, the sound and the voice signals are compressed according to the AC-3 standard, and these signals are transmitted using the vestigial side band technique (“Vestigial Side Band - VSB). VSB, which consists of terrestrial DTV reception patterns, is advantageous in the fact that it increases the use of frequency bands, thus maximizing the DTV viewing range, but it is disadvantageous in that it is hardly applicable in mobile TV as a radio signal is difficult to be received on the move.

[0003] However, to the extent that a need for broadcast services, such as DMB broadcast services

Petition 870190118091, of 11/14/2019, p. 5/167

2/160 terrestrial and DMB satellite broadcasting service, which uses a mobile communication device, has been increasing and the requirements for broadcasting services have increased and have diversified, several broadcasting techniques have been introduced to meet such demands from users.

DESCRIPTION OF THE DRAWINGS

[0004] FIGS. 1A and 1B illustrate an MCAST data protocol stack according to a configuration of the present invention.

[0005] FIG. 2 illustrates an MCAST data protocol stack according to another embodiment of the present invention.

[0006] FIG. 3 schematically illustrates the structure of an MCAST A-VSB transmission system according to a configuration of the present invention.

[0007] FIG. 4 schematically illustrates the structure of an MCAST A-VSB transmission system according to another embodiment of the present invention.

[0008] FIG. 5 schematically illustrates a BCAST OMA service layer according to a configuration of the present invention.

[0009] FIG. 6 schematically illustrates a terminal network protocol interface according to a configuration of the present invention.

[00010] FIGS. 7A through 7D illustrate a high speed service access method supported by an ATSC-MCAST system according to a configuration of the present invention.

[00011] FIGS. 8A and 8B illustrate a high-speed service access method supported by the ATSC-MCAST system according to another embodiment of the present invention.

Petition 870190118091, of 11/14/2019, p. 6/167

3/160

[00012] FIGS. 9A and 9B illustrate a high-speed service access method supported by the ATSC-MCAST system according to another embodiment of the present invention.

[00013] FIGS. 10A through 10C illustrate service configuration information according to a configuration of the present invention.

[00014] FIG. 11 illustrates the structure of an information_version_indicator_ information field () illustrated in FIG. 10A according to a configuration of the present invention.

<td> [00015]</td><td>FIG.</td><td> 12</td><td>illustrates the</td><td>structure</td><td>in</td><td>One field</td><td>in</td>

<td colspan="2">group_information</td><td>'_in_</td><td>_frames().</td><td></td><td></td><td></td><td></td>

<td> [00016]</td><td>FIG.</td><td> 13</td><td>illustrates the</td><td>structure</td><td>in</td><td>One field</td><td>in</td>

turbo_channel_information () illustrated in FIG. 10A according to a configuration of the present invention.

[00017] FIG. 14 illustrates the structure of an additional_service_information field () illustrated in FIG. 10A according to a configuration of the present invention.

[00018] FIG. 15 illustrates the structure of a description_channel__turbo_channel field () according to a configuration of the present invention.

[00019] FIG. 16A illustrates the structure of a turbo_channel_configuration field () illustrated in FIG. 10B according to a configuration of the present invention.

<td>[00020] A</td><td>FIG. 16B</td><td>illustrates</td><td>The</td><td>structure</td><td>in</td><td>One field</td><td>in</td>

<td>configuration_</td><td>de_canal_</td><td>turbo ()</td><td>in</td><td>wake up</td><td colspan="3">with another</td>

<td>configuration</td><td colspan="3">of the present invention.</td><td></td><td></td><td></td><td></td>

<td>[00021] A</td><td>FIG. 17</td><td>illustrates</td><td>The</td><td>structure</td><td>in</td><td>One field</td><td>in</td>

<td colspan="2">enlace_de_descritor ()</td><td>illustrated</td><td>at</td><td>FIG. 16A</td><td>in</td><td>a deal with</td><td>an</td>

<td>configuration</td><td colspan="3">of the present invention.</td><td></td><td></td><td></td><td></td>

<td>[00022] A</td><td>FIG. 18</td><td>illustrates</td><td>The</td><td>structure</td><td>in</td><td>One field</td><td>in</td>

Petition 870190118091, of 11/14/2019, p. 7/167

4/160 'updating-of-group-of-frames' when the value of a 'tag' field ('tag') illustrated in FIG. 17 is set to be '0'.

[00023] FIG. 19A illustrates the structure of a 'Update_of_Duration_of_Fatmento_de_Quadro' field when the

<td>value of</td><td>field of</td><td>'marker' illustrated in FIG. 17 is</td><td>defined</td>

<td>to be</td><td>'1 of</td><td>according to a configuration of</td><td>gift</td>

<td>invention.</td><td></td><td></td><td></td>

<td> [00024]</td><td>FIG.</td><td>19B illustrates the structure of the</td><td>field of</td>

'Update_of_Duration_of_Fatmento_de_Quadro' when the value of the 'marker' field illustrated in FIG. 17 is defined to be '1', according to another embodiment of the present invention.

[00025] FIG. 20A illustrates the structure of an 'update_of_SRS_position' field when the value of the 'marker' field illustrated in FIG. 17 is defined to be '2', according to a configuration of the present invention.

[00026] FIG. 20B illustrates the structure of the 'update_of_SRS_position' field when the value of the 'marker' field illustrated in FIG. 17 is defined to be '2', according to another embodiment of the present invention.

[00027] FIG. 21A illustrates the structure of a 'turbo_channel_update' field when the value of the 'marker' field illustrated in FIG. 17 is defined to be '3', according to a configuration of the present invention.

[00028] FIG. 21B illustrates the structure of a 'turbo_channel_update' field when the value of the 'marker' field illustrated in FIG. 17 is defined to be '3', according to another embodiment of the present invention.

[00029] FIG. 22A illustrates the structure of a field of

Petition 870190118091, of 11/14/2019, p. 8/167

5/160

<td>'Package_BD'</td><td>in</td><td>a deal with</td><td>a configuration</td><td>gives</td><td>gift</td>

<td>invention.</td><td></td><td></td><td></td><td></td><td></td>

<td>[00030] A</td><td>FIG</td><td>. 22B illustrates</td><td>the structure of</td><td>one</td><td>field of</td>

<td>'Package_BD'</td><td>in</td><td>according to a</td><td>other configuration</td><td>gives</td><td>gift</td>

<td>invention.</td><td></td><td></td><td></td><td></td><td></td>

<td>[00031] A</td><td>FIG</td><td>23 illustrates the</td><td>structure of a</td><td colspan="2">descriptor</td>

broadcasting (“Broadcast Descriptor” - BD) according to a configuration of the present invention.

[00032] FIG. 24A illustrates the structure of a 'Channel_information_ update ()' field when the value of a

<td>'marker' field illustrated in FIG.</td><td>23 is</td><td> '1',</td><td>in</td><td>wake up</td><td>with</td>

<td>a configuration of the present invention.</td><td></td><td></td><td></td><td></td><td></td>

<td colspan="2">[00033] FIG. 24B illustrates the structure</td><td>in</td><td>one</td><td>field</td><td>in</td>

<td>'update_of_Channel_information ()'</td><td>in</td><td colspan="2">wake up</td><td>with</td><td>an</td>

<td>configuration of the present invention.</td><td></td><td></td><td></td><td></td><td></td>

<td colspan="2">[00034] FIG. 24C illustrates the structure</td><td>in</td><td>one</td><td>field</td><td>in</td>

<td>'update_of_Channel_information ()'</td><td colspan="2">according</td><td>with</td><td colspan="2">another</td>

configuration of the present invention.

[00035] FIG. 25A illustrates an Internet protocol (IP) mapping descriptor when the value of the 'marker' field illustrated in FIG. 23 is '1', according to a configuration of the present invention.

[00036] FIG. 25B illustrates the IP mapping descriptor according to another embodiment of the present invention.

<td>[00037] FIG. 26</td><td>illustrates the structure</td><td>in</td><td>one</td><td>field</td><td>in</td>

<td>'channel_description_of_</td><td>_IP ”illustrated in FIG.</td><td>2 5A</td><td>in</td><td>wake up</td><td>with</td>

<td colspan="2">a configuration of the present invention.</td><td></td><td></td><td></td><td></td>

<td>[00038] FIG. 27A</td><td>illustrates the structure</td><td>in</td><td>one</td><td>field</td><td>in</td>

<td>'address_table_of_</td><td>IP 'when the value</td><td>in</td><td>one</td><td>field</td><td>in</td>

<td>illustrated 'marker'</td><td>in FIG. 26 is' ​​1'de</td><td colspan="2">wake up</td><td>with</td><td>an</td>

Petition 870190118091, of 11/14/2019, p. 9/167

6/160 configuration of the present invention.

[00039]

FIG. 27B illustrates the structure of the IP address table field when the value of the marker field 'illustrated in FIG. 26 is

1 'according to another embodiment of the present invention.

[00040]

FIG. 28 illustrates the structure of a MAC address table field when the value of the 'marker' field illustrated in FIG. 26 is '2' according to a configuration of the present invention.

[00041] FIG. 29 illustrates the structure of a 'text_description_table' field when the value of the 'marker' field illustrated in FIG. 26 is '3' according to a configuration of the present invention.

[00042] FIG. 30A illustrates a multiplexing structure

MCAST according to a configuration of the present invention.

[00043] FIG. 30B illustrates a multiplexing structure

MCAST according to another embodiment of the present invention.

[00044] FIG. 31A illustrates an MCAST frame structure and an LMT according to a configuration of the present invention.

<td> [00045]</td><td>THE</td><td>FIG.</td><td>31B</td><td>illustrates</td><td>a frame structure</td><td>MCAST and</td>

<td>an LMT</td><td>in</td><td colspan="2">wake up</td><td>with one</td><td>another configuration of</td><td>gift</td>

<td>invention.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> [00046]</td><td>THE</td><td>FIG.</td><td> 32</td><td>illustrates</td><td>a verification method</td><td>of a</td>

<td>change</td><td colspan="2">on a</td><td>sub</td><td>-channel</td><td colspan="2">using data from</td>

virtual map identification ("Virtual Map Identification" VMI) according to a configuration of the present invention.

[00047] FIG. 33 is a flow diagram illustrating a method of acquiring a service using VMI according to a configuration of the present invention.

Petition 870190118091, of 11/14/2019, p. 10/167

7/160

[00048] FIG. 34A illustrates the structure of a Location Map Table (LMT) according to a configuration of the present invention.

[00049] FIG. 34B illustrates in detail the structure of the LMT of FIG. 34A according to a configuration of the present invention.

[00050] FIGS. 35A and 35B illustrate the structures of the LMT according to configurations of the present invention.

[00051] FIG. 36 illustrates the structure of a 'LMT_information' field illustrated in FIG. 35 according to a configuration of the present invention.

[00052] FIGS. 37A and 37B illustrate the structures of the LMT and the 'information_of_LMT' field according to another embodiment of the present invention.

[00053] FIG. 38 illustrates the structure of the LMT according to another embodiment of the present invention.

[00054] FIG. 39 illustrates the structures of an MCAST frame and a linkage information table ("Linkage Information Table" - LIT) according to a configuration of the present invention.

[00055] FIG. 40 illustrates a structure of an LIT according to a configuration of the present invention.

[00056] FIGS. 41A and 41B illustrate the structure of an LIT according to another embodiment of the present invention.

[00057] FIG. 42A is a flow diagram illustrating a method of providing a service using an LMT and an LIT according to a configuration of the present invention.

[00058] FIG. 42B is a flow diagram illustrating a method of providing a service using an LMT and an LIT according to another embodiment of the present invention.

Petition 870190118091, of 11/14/2019, p. 11/167

8/160

[00059] FIG. 43 illustrates the structure of object transmission information according to a configuration of the present invention.

<td>[00060] FIG. 44 illustrates the structure</td><td>in</td><td>one</td><td>field</td><td>in</td>

<td>'directory_information' illustrated in FIG.</td><td> 43</td><td>in</td><td>wake up</td><td>with</td>

<td>a configuration of the present invention.</td><td></td><td></td><td></td><td></td>

<td>[00061] FIG. 45 illustrates the structure</td><td>in</td><td>one</td><td>field</td><td>in</td>

'time_table' illustrated in FIG. 43 according to a configuration of the present invention.

<td>[00062] A</td><td>FIG. 46</td><td>illustrates</td><td>The</td><td colspan="2">structure</td><td>on one</td><td>field</td><td>in</td>

<td>'descriptor_</td><td>de_name</td><td>_content'</td><td colspan="2">When</td><td>the ditch</td><td>r of one</td><td>field</td><td>in</td>

<td>'highlighter'</td><td>illustrated</td><td>in FIG.</td><td> 43</td><td>is</td><td>'1 of</td><td>wake up</td><td>with</td><td>an</td>

<td colspan="4">configuration of the present invention.</td><td></td><td></td><td></td><td></td><td></td>

<td>[00063] A</td><td>FIG. 47</td><td>illustrates</td><td>The</td><td colspan="2">structure</td><td>on one</td><td>field</td><td>in</td>

<td>'description_</td><td>de_type_of_</td><td colspan="2">_mime 'when</td><td>O</td><td>value</td><td>on one</td><td>field</td><td>in</td>

<td>'highlighter'</td><td>illustrated</td><td>in FIG.</td><td> 43</td><td>is</td><td>'2' from</td><td>wake up</td><td>with</td><td>an</td>

configuration of the present invention.

[00064] FIG. 48 illustrates the relationship between an encapsulation package and a transport package in an MCAST system according to a configuration of the present invention.

[00065] FIGS. 49A and 49B illustrate the structure of an encapsulation package for signaling according to a configuration of the present invention.

[00066] FIGS. 50A and 50B illustrate the structure of an encapsulation package for real-time data according to a configuration of the present invention.

[00067] FIG. 51 illustrates the syntax of an encapsulation package for real-time data according to a configuration of the present invention.

[00068] FIGS. 52A and 52B illustrate the syntax of a package of

Petition 870190118091, of 11/14/2019, p. 12/167

9/160 encapsulation for IP data according to a configuration of the present invention.

[00069] FIG. 53 illustrates the syntax of an encapsulation packet for IP data according to another embodiment of the present invention.

[00070] FIGS. 54A and 54B illustrate the structure of a package for object data according to a configuration of the present invention.

[00071] FIGS. 55A and 55B illustrate the structure of a package for object data according to another embodiment of the present invention.

[00072] FIG. 56 illustrates a method of transmitting object data according to a configuration of the present invention.

[00073] FIG. 57 illustrates the application of error correction by application layer anticipation (“Application Layer Forward Error Correction” - AL-FEC) according to a configuration of the present invention.

[00074] FIG. 58 illustrates header structures of a transport package and a transport package according to configurations of the present invention.

[00075] FIG. 59 illustrates the syntax of a transport package according to a configuration of the present invention.

[00076] FIGS. 60A and 60B illustrate the structures of a transport package, a base header, and an additional field according to another embodiment of the present invention.

[00077] FIGS. 61A and 61B illustrate the structure of a 'fill_field' field when the value of a 'marker' field illustrated in FIG. 60 is '0', according to a

Petition 870190118091, of 11/14/2019, p. 13/167

10/160 configuration of the present invention.

[00078] FIG. 62 illustrates the structure of a 'field_of_LMT' field when the value of the 'marker' field illustrated in FIG. 60 is '1', according to a configuration of the present invention.

[00079] FIG. 63 illustrates the structure of a 'compaction_field_parameter' field when the value of the 'marker' field illustrated in FIG. 60 is '2', according to a configuration of the present invention.

[00080] FIGS. 64A and 64B illustrate the structure of a signaling package according to a configuration of the present invention.

[00081] FIG. 65 illustrates a BCAST OMA service provision process in an MCAST transmission system according to a configuration of the present invention.

[00082] FIG. 66 illustrates a method of providing a service using MCAST that supports OMA-BCAST according to a configuration of the present invention.

[00083] FIG. 67 illustrates four layers for protection of a service and content according to a configuration of the present invention.

[00084] FIG. 68 illustrates a power management mechanism according to a configuration of the present invention.

[00085] FIG. 69 illustrates parameters related to MCAST frame slicing according to a configuration of the present invention.

[00086] FIG. 70 illustrates energy saving related parameters according to a configuration of the present invention.

[00087] FIG. 71 is an illustrative graph of a method for

Petition 870190118091, of 11/14/2019, p. 14/167

11/160 allocation to each service of a previously determined bandwidth for burst mode transmission according to a configuration of the present invention.

[00088] FIG. 72 is an illustrative graph of service rotation for burst mode transmission according to a configuration of the present invention.

<td> [00089]</td><td>THE</td><td>FIG. 73 is</td><td>one</td><td>illustrative graphic of</td><td>a matrix</td>

<td>generator</td><td>in</td><td>a deal with</td><td>an</td><td>configuration of this</td><td>invention.</td>

<td> [00090]</td><td>THE</td><td>FIG. 74 is</td><td>one</td><td colspan="2">illustrative flow diagram of a</td>

<td>method</td><td>in</td><td colspan="2">determination</td><td>degree (vi) according</td><td>with one</td>

configuration of the present invention.

[00091] FIG. 75 is a flow diagram illustrating a connection of message nodes to a code node according to a configuration of the present invention.

[00092] FIG. 76 is a flow diagram illustrating in detail the operation S7520 illustrated in FIG. 75 according to a configuration of the present invention.

[00093] FIG. 77 is a block diagram of an MCAST broadcast receiver according to a configuration of the present invention.

[00094] FIG. 78 is a flow diagram illustrating a method of receiving a broadcast according to a configuration of the present invention.

[00095] FIG. 79 is a schematic illustration of an A-VSB MCAST receiving system according to a configuration of the present invention.

[00096] FIG. 80 is a block diagram of a diffusion receiving apparatus capable of indicating an error packet according to a configuration of the present invention.

[00097] FIG. 81 is an illustrative flow diagram of a

Petition 870190118091, of 11/14/2019, p. 15/167

12/160 method of receiving a broadcast indicating an error packet according to a configuration of the present invention.

[00098] FIGS. 82A and 82B illustrate the structure of a prepackage according to configurations of the present invention.

[00099] FIG. 83 is a flow diagram illustrating a method of processing DCI by a diffusion receiving apparatus according to a configuration of the present invention.

[000100] FIG. 84A illustrates a method of updating CBT in adaptive time slicing according to a configuration of the present invention.

[000101] FIG. 84B illustrate an update method using DB in adaptive time slicing according to a configuration of the present invention.

[000102] FIG. 85 is a block diagram of a broadcast service transmission apparatus according to a configuration of the present invention.

[000103] FIG. 86 is a block diagram of a broadcast service receiving apparatus according to a configuration of the present invention.

[000104] FIG. 87 is a flow diagram illustrating a method of transmitting a broadcast service according to a configuration of the present invention.

[000105] FIG. 88 is a flow diagram illustrating a method of receiving a broadcast service for mobile communication according to a configuration of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

TECHNICAL PROBLEM

[000106] The present invention provides a method and apparatus for transporting broadcast services with the capacity for fast and efficient provision of a broadcast service.

Petition 870190118091, of 11/14/2019, p. 16/167

High quality standard 13/160 in a mobile communications system,

<td>and a month diffusion.</td><td>whole and a device for reception</td><td>in</td><td>services</td><td>in</td>

<td> [000107]</td><td>TECHNICAL SOLUTION The present invention provides</td><td>one</td><td>method</td><td>in</td>

transport of a broadcast service for mobile communications, in which the method comprises the generation of an encapsulation package including configuration information adaptable to the application data to be transmitted and the application data; generation of transport packages having data related to the encapsulation package by dividing the encapsulation package into packages of previously determined dimensions, in which the transport packages include information regarding the structures of the transport packages; and generating service configuration information including defined information about a channel containing transport packages, and including service configuration information in a service information channel at a predetermined location out of at least one transport channel in a transport string or chain.

ADVANTAGE EFFECTS

[000108] According to the present invention, due to the fact that service configuration information is present in a previously determined region of a transport frame, a broadcast service reception apparatus can access a transport channel using configuration information without processing channel information signaling. In this way, it is possible to reduce the waiting time for an

Petition 870190118091, of 11/14/2019, p. 17/167

14/160 broadcast services for reception of a broadcast service, which is caused until each of the broadcast services is accessed after the detection of the signaling information channel in the transport frame and interpretation of the signaling information channel.

[000109] Furthermore, according to the present invention, the structures of an encapsulation package and a transport package are determined adaptively with respect to the type of application data provided, thus allowing an efficient use of a data region and allowing to increase the data transmission speed.

[000110] In addition, according to the present invention, decoder configuration information is carried along with a broadcast service that provides real-time media data, so that a receiving side can update the specifications of a decoder suitable for the media format provided using decoder configuration information.

PREFERENTIAL MODE

[000111] In accordance with an aspect of the present invention, an apparatus is provided for carrying a broadcast service for mobile communications, wherein the apparatus includes an encapsulation packet generating unit that generates an encapsulation packet including configuration information adaptable for application data to be transmitted and application data; a transport packet generating unit that generates transport packets containing data related to the encapsulation package by dividing the encapsulation package into packages of previously determined dimensions, in which the

Petition 870190118091, of 11/14/2019, p. 18/167

15/160 transport packages comprise information regarding the structures of transport packages; and a service configuration information generation unit that generates service configuration information including defined information about a channel containing transport packages, and including service configuration information in a service information channel at a location previously determined from at least one transport channel in a transport sequence or chain.

[000112] In accordance with an aspect of the present invention, a method is provided for receiving a broadcast service for mobile communications, wherein the method includes determining a previously determined transport channel using extracted service configuration information a service information channel; extracting a transport package from the determined transport channel; extracting information regarding the transport package from the extracted transport package; obtaining a combination of encapsulation packages in which each of them has at least one transport package by extracting the information relating to the transport package; and obtaining a combination of application data having at least one encapsulation package using information relating to the encapsulation packages, which are extracted from the combination of the encapsulation packages.

[000113] In accordance with an aspect of the present invention, an apparatus for receiving broadcast service for mobile communications is provided, wherein the apparatus includes a transport channel determining unit which determines a transmission channel.

Petition 870190118091, of 11/14/2019, p. 19/167

16/160 transport previously determined using service configuration information extracted from a service information channel; a transport package extraction unit which extracts a transport package from the determined transport channel; a transport package information extraction unit that extracts transport package information from the extracted transport package; an encapsulation packet combining unit that obtains a combination of encapsulation packets, each of which has at least one transport packet, using the information relating to the transport packets; and an application data combining unit that obtains a combination of application data having at least one encapsulation package using information relating to the encapsulation packages, which are extracted from the combination of the encapsulation packages.

[000114] In accordance with an aspect of the present invention, a method of transporting a sequence of data or chain is provided, wherein the method includes the insertion of a second transport sequence, which is necessary for a mobile terminal to receive data of diffusion, in a first transport sequence, and the transport of the first transport sequence in which the second transport sequence was inserted.

[000115] The second transport sequence can be inserted at a location previously determined in the first transport sequence.

[000116] The method may additionally include the generation of signaling information including at least one of the information regarding the location of the second transport sequence, and information necessary for processing the signal.

Petition 870190118091, of 11/14/2019, p. 20/167

17/160 second transport sequence, in which during the transport of the first transport sequence, the signaling information is additionally transported.

[000117] In accordance with an aspect of the present invention, a method of receiving a sequence of data is provided, wherein the method includes obtaining a second transport sequence by receiving a first transport sequence in which it is inserted the second transport sequence; and processing the second transport sequence.

[000118] The second transport sequence can be inserted at a location previously determined in the first transport sequence.

<td colspan="2">[000119] During obtaining</td><td>gives</td><td>Monday</td><td>sequence</td><td>in</td>

<td>transport,</td><td colspan="2">can be additionally</td><td>obtained</td><td>information</td><td>in</td>

<td>signaling</td><td>including at least</td><td>an</td><td colspan="2">referring information</td><td>The</td>

<td>location</td><td>of the second string</td><td>in</td><td colspan="3">transport and information</td>

<td>needed</td><td>for processing</td><td>gives</td><td>Monday</td><td>sequence</td><td>in</td>

<td>transport,</td><td>and processing</td><td>gives</td><td>Monday</td><td>sequence</td><td>in</td>

<td>transport</td><td colspan="2">may include processing</td><td colspan="2">of the second string</td><td>in</td>

<td>transport</td><td>based on information</td><td>s of</td><td colspan="2">signaling.</td><td></td>

<td colspan="2">INVENTION MODE</td><td></td><td></td><td></td><td></td>

<td colspan="4">[000120] For the sake of convenience of</td><td>explanation,</td><td>at</td>

abbreviations and terms used in this specification will be defined as follows:

. application layer: streaming [in-stream configuration] of audio / video (A / V), and Internet Protocol (IP) services and services not performed in real time (NonReal-Time - NRT). ATSC-M / H terminal: a terminal device that

Petition 870190118091, of 11/14/2019, p. 21/167

18/160 accesses an ATSC-M / H service. ATSC-M / H service: an ATSC service for mobile and hand-held terminals. ATSC-M / H system: a combination of a head-end service and equipment system that makes ATSC-M / H services available through broadcast and optionally through an interaction channel. cluster: a group formed by any number of sectors in which a Turbo fragment is placed. primary service: a first priority service viewed by a user when activated. This is an optional broadcast provider service.

. interlinking layer [link layer]: coding

FEC, partitioning and mapping between a turbo sequence and clusters. Linkage Information Table (LIT): a table of interconnection information between service components that is arranged everywhere in an MCAST service package. Location Map Table ”

- LMT): - a table of location information that is arranged everywhere in an MCAST service package.

. MCAST package: a transport package defined in an MCAST package. MCAST service package: a group of MCAST packages decoded after the Turbo packages are extracted from a service package. MCAST string: a string of MCAST packets. MCAST transport layer: a layer of

Petition 870190118091, of 11/14/2019, p. 22/167

19/160 transport defined in ATSC-MCAST. MPEG data: a TS sequence with no synchronization byte. MPEG data packet: a TS sequence packet with no synchronization byte. service pack: a group of 624 TS MPEG data packets. sector: an 8-byte space reserved in AF or a TS or an MPEG data packet. SIC: a type of turbo sequence, consisting of a signaling information channel containing information for processing all turbo sub channel sequences: a physical space for streaming

A / V, Internet protocol (IP) and NRT data. sub channel data: a physical space for sub channel components.

. transport layer: a transport layer defined in ATSC-MCAST. turbo channel: a transport strings. The channels can be different ones. turbo string: TS. VSB frame: 626 physical space that stores levels of turbo protection from others.

turbo-coded segments consisting of 2 data field synchronization segments and 624 segments (data + FEC). A-VSB: an advanced VSB System. AF: adaptation field in a TS package with definition A / 53. ATSC: Advanced Television Systems Committee

[Commission for Advanced Television Systems]

Petition 870190118091, of 11/14/2019, p. 23/167

20/160. BD: diffusion descriptor. BCAST: Enabler of OMA mobile broadcast services. IRD: integrated receiver and decoder. DC: decoder configuration. DCI: decoder configuration information. DFS: data field synchronization. DVB: digital video broadcast. ES: elementary sequence. EC channel: elementary component channel. FEC: early error correction. F / L: first / last. IMT: IP mapping table. IPEP: IP encapsulation package. LMT: location map table. LIT: interconnection information table. MAC: media access layer. MCAST: mobile broadcast. OEP: object encapsulation package. OMA: open mobile alliance. PCR: program clock reference. PSI: program-specific information. PSIP: program specification information protocol. REP: encapsulation package in real time. SD-VFG: division of service into a group of variable staff. SEP: signal encapsulation package. SG: service guide. SIC: signaling information channel

Petition 870190118091, of 11/14/2019, p. 24/167

21/160. SRC: supplementary reference string. TS: transport string

[000121] Hereinafter exemplary configurations of the present invention will be described in more detail with reference to the attached drawings.

[000122] An MCAST transmission system according to the present invention is capable of providing several types of services together or providing only a specific type of service, such as an Internet protocol (IP) service. FIG. 1 illustrates a case in which several types of services are provided together. FIG. 2 illustrates a case in which only a specific type of service is provided.

[000123] FIGS. 1A and 1B illustrate an MCAST data protocol stack according to a configuration of the present invention. Referring to FIGS. 1A and 1B, different types of content are transmitted in such a way that different types of services are provided through an MCAST transmission system. Examples of services supported by the MCAST transmission system, for example, a real-time service, an IP service and an object download service will now be described. However, the types of services that can be supported by the MCAST transmission system are not limited to the services described.

[000124] In a real-time service, data is received in real time, and is intended to be consumed as soon as it is received. Real-time data types include video, audio, and ancillary information designed to be displayed alongside audio / video (A / V).

[000125] An IP service is a broad term that indicates all types of services including services that use data

Petition 870190118091, of 11/14/2019, p. 25/167

22/160 based on IP protocol, such as casting IP data. In an IP service, IP-based data received in real time is expected to be consumed as soon as the data is received or in the near future. Otherwise, the IP service can be extended to a service in which the IP-based data is downloaded as an object and is stored on a storage device for later use.

[000126] An object download service is characterized by the fact that multimedia data or general object data is received at any point in time, and is displayed or stored in response to a control signal.

[000127] The data characteristics supported by the MCAST system for the provision of a service will now be described.

[000128] MCAST supports H.264 / AVC video encoding and decoding on an IRD. In order to make possible full compliance with specifications and upward compatibility with future improved versions, the IRD must be able to disregard data structures that are currently reserved for those that correspond to functions not implemented by the IRD.

[000129] Regarding profile and level, MCAST supports encoding and decoding as follows:

. encoding: An H.264 / AVC bit stream must comply with the restrictions described in ITU-T Recommendation H.264 (H.264 recommended by ITU-T) / ISO / IEC 14496-10 for Level 1.3 Baseline Profile with constraint_set1_flag (constraint_set1_flag) equal to '1'.

. decoding: Similarly, an IRD that supports

H.264 / AVC should be able to decode and render images

Petition 870190118091, of 11/14/2019, p. 26/167

23/160 using the 1.3 Baseline Profile with constraint_seti_flag (constraint_seti_flag) equal to '1'.

[000130] In the case of a sample aspect ratio, a quadrangular sample aspect ratio (1: 1) will be used for coding, and each IRD must support decoding and rendering of images with a quadrangular sample aspect ratio (1 : 1) for decoding.

[000131] With respect to random access point, it is recommended that sets of image parameters and sequences be sent together with a random access point at least once every two seconds.

[000132] With regard to audio, ATSC-MCAST supports the MPEG-4 AAC profile, the MPEG-4 HE AAC profile and the MPEG HE AAC v2 profile. To allow full compliance with ISO / IEC14496-3 [5] and upward compatibility ”with future improved versions, the IRD should be able to ignore data structures that are currently reserved” or that correspond to functions not implemented by the IRD.

[000133] With respect to an audio mode, the audio will be encoded in mono, parametric stereo or 2-channel stereo according to the functionality defined in level 2 of HE AAC v2 profile or it will be encoded in a multichannel according to functionality defined in HE AAC v2 profile level 4 as specified in ISO-IEC 14496-3 including amendments 1 and 2 [5]. In addition, the IRD must be able to decode mono, parametric stereo or 2-channel stereo from the functionality defined in level 2 of HE AAC v2 profile as specified in ISO-IEC 14496-3 including amendments 1 and 2 [5].

Petition 870190118091, of 11/14/2019, p. 27/167

24/160

[000134] Regarding bit rates, during encoding, the maximum audio bit rate should not exceed 192 kbits / s for a stereo pair and the maximum encoded audio bit rate must not exceed 320 kbits / s for audio multiple channels. During decoding, the IRD must support the HE AAC v2 profile and a selected level subject to a maximum of 192 kbit / s for a stereo pair.

[000135] In addition, with respect to matrix downmixing, the IRD must support matrix downstream mixing as defined in the MPEG-4 standard.

[000136] However, MCAST is not limited to the encoding method described above. Sequences encoded according to another encoding method, for example, MPEG-2 Video / BSAC can also be transmitted by direct / indirect expression of the encoding method.

[000137] FIG. 2 illustrates an MCAST data protocol stack according to another embodiment of the present invention. In detail, FIG. 2 illustrates a case where only one IP service is provided through MCAST.

[000138] A packet layer segments signaling information and the IP datagram for MCAST packets and adds a transmission header to them. The signaling information channel (SIC) contains signaling information for each turbo channel.

[000139] In mobile services, a quick purchase of services is an important requirement. MCAST reduces the steps for tuning, demultiplexing and decoding services, and thus provides for the quick acquisition of services.

[000140] In addition, MCAST supports the concept of a primary service. The primary service is a first-rate service

Petition 870190118091, of 11/14/2019, p. 28/167

25/160 priority for a user to watch continuously. In a general case of access and service in a turbo sequence, the SIC must be purchased and decoded first for turbo processing. The SIC contains physical decoding information and some simple descriptions of all turbo services. In the case of the primary service, quick access is possible due to the fact that the access information is defined in the Data Field Sync ”(DFS). A quick access method will be described below with reference to FIGS. 7 through 9.

[000141] The primary service and the SIC must be in a continuous transmission mode and the SIC must exist in each frame. In streaming mode, frames are transmitted continuously. In a burst mode, a plurality of frames are transmitted at a point in time at a specific point in time (see FIG. 68 for details). The SIC is indispensable. However, the primary service is optional and depends on a service provider.

[000142] FIG. 3 schematically illustrates the structure of an A-VSB MCAST transmission system according to a configuration of the present invention. Referring to FIG. 3, MCAST supports several types of services. An MCAST architecture is composed of four layers: an application layer, a transport layer, a data interconnection layer, and a physical layer. These layers are indicated from left to right in FIG. 3.

[000143] The transport layer provides the fragmentation and application-specific information of the application data, and encapsulates elementary units with a syntax

Petition 870190118091, of 11/14/2019, p. 29/167

26/160 previously defined. The application strings are encapsulated by specific type and are multiplexed in fixed length packages, which are referred to as a 'MCAST turbo string'. The packages subsequently form turbo channels.

[000144] The interconnection layer receives turbo channels and applies specific forward error correction (“Forward Error Correction” FEC), for example, a code rate, etc., to each of the turbo channels. The signaling information present in a SIC is important, and therefore the most powerful FEC correction is applied to it in such a way that a signaled application can be received even at a lower level of signal-to-noise ratio (SNR). then, the turbo channels to which FEC is applied are transmitted together with the Normal TS packets to an A-VSB MAC layer.

[000145] A layer A-VSB MAC inserts or adds a robust package containing additional data that a mobile terminal can receive for a Normal TS. For example, a robust package can be inserted into a region of null MPEG TS TS packets or it can be included in a region of private data TS TSEGEG 2. The A-VSB MAC layer opens adaptation fields (“Adaptation Fields” - AF) in Normal TS packages if necessary. In this case, the SIC that transmits signaling information for processing the robust package is defined, and the SIC can be easily obtained due to the fact that it is present in a previously determined location or by using an indicator (“flag”) that indicates SIC location. As described above, the AVSB MAC layer specifies a method or information regarding the insertion or addition of the robust package to a normal TS. For

Petition 870190118091, of 11/14/2019, p. 30/167

27/160 obtaining a general gain and a result (improvement) of efficiency in relation to a system, which an 8-VSB system does not originally have, with simultaneous maintenance of compatibility, the robust data is mapped to a deterministic frame structure , are signaled and transmitted to a physical layer 8-VSB. In addition, an exciter device operates deterministically on the physical layer under control of the MAC layer, and inserts signaling information into DFS.

[000146] MCAST provides a real-time service, an IP service and an object service as application services. At least one of these services is multiplexed to an MCAST sequence by turbo channels. In particular, MCAST is capable of providing a primary service to obtain an initial high-speed service.

[000147] For the provision of various services, the MCAST transmission provides at least one of four types of data: real-time audio, real-time video, IP, and object signaling. For example, to improve the service quality of applications, it is possible to apply application layer FEC correction (AL-FEC) to object strings or IP strings when large amounts of files are transmitted. The AL-FEC correction will be described later with reference to FIG. 57.

[000148] FIG. 4 schematically illustrates the structure of an A-VSB MCAST transmission system according to another embodiment of the present invention. Referring to FIG. 4, MCAST supports only one IP service. The A-VSB MCAST transmission system is identical to that illustrated in FIG. 3 with the exception of the fact that only IP services are

Petition 870190118091, of 11/14/2019, p. 31/167

28/160 multiplexed in an MCAST sequence for each of the turbo channels.

[000149] FIG. 5 schematically illustrates the structure of an OMA BCAST service layer according to a configuration of the present invention. In FIG. 5, one terminal corresponds to an 'ATSC-M / H terminal' in terms of functions, and the other elements correspond to an 'ATSC-M / H system'.

• BCAST-5 is a broadcast services layer interface to an upper part of a management layer. A lower part of this interface consists of Internet Protocol (IP), which in turn is subsequently interfaced with an upper part of the X-3 / X-4 interface.

• BCAST-6 is the interactive services layer interface for the top of the management layer.

• BCAST-7 represents an interface that supports signaling for managing subscribers and content / services transactions.

• BCAST-8 represents service-oriented interactivity.

• The X-3 and X-4 interfaces are considered identical in this specification. They represent a carrier layer and carry data associated with the BCAST-5 interface. For an inferior part this interface specifies the carrier A-VSB. For an upper part this interface specifies MCAST transport supporting BCAST5 provision.

• The X-5 and X-6 interfaces are considered identical

Petition 870190118091, of 11/14/2019, p. 32/167

29/160 in this specification. They represent an optional interactivity between network / carrier for transporting data associated with BCAST-6, BCAST-7 and BCAST-8 interfaces.

[000150] The interfaces BCAST-1, BCAST-2, BCAST-3, BCAST-4, BDS-1, BDS-2, X-1 and X-2 are not relevant to the present report described and will not be described here.

[000151] FIG. 6 schematically illustrates the terminal-network protocol interface structure according to a configuration of the present invention. In FIG. 6, an ATSC-M / H terminal-network interface will be described in more detail using the concepts of a BCAST interface and an MCAST structure. FIG. 6 illustrates a proposed ATSC-M / H protocol stack not only for an interactive broadcast mode but also for a broadcast-only mode. The stack is divided into two main parts. One of the main parts is an ATSC-M / H service layer consisting of methods applicable to all ATSCM / H receivers and optional interactivity methods. Below the ATSC-M / H Services Layer are carrier layers, one of which illustrates the ATSC-M / H carrier layer and the other illustrates an optional interactive carrier.

[000152] An MCAST signaling method will now be described. An important requirement for mobile broadcasting is access to high-speed services. ATSCMCAST provides two representative ways for accessing high-speed services: a primary service, and splitting ES signaling information for a real-time media service. A high-speed service access method supported by the ATSC-MCAST system will be described later

Petition 870190118091, of 11/14/2019, p. 33/167

30/160 with reference to FIG. 7.

[000153] In addition, the ATSC-MCAST system can provide a SIC. The SIC can contain essential information, for example for processing a turbo channel. The SIC can contain essential information essential for a user to view a broadcast. For example, the SIC may contain physical decoding information or a brief description of all turbo services which is optional. The SIC must be processed first to process other turbo channels. The SIC will be described later with reference to FIG. 10.

[000154] A primary service and the SIC are present in a continuous transmission mode, and the SIC can be present in all frames. Although the SIC is an indispensable element, a service provider can determine whether to provide the primary service.

[000155] FIG. 7 illustrates a high-speed service access method supported by an ATSC-MCAST system according to a configuration of the present invention. Referring to FIG. 7, a primary service is provided according to the high speed service access method. The primary service is a high priority for a user to receive a broadcast service.

[000156] Specifically, FIG. 7A illustrates a process for receiving a service in an MCAST system according to a configuration of the present invention.

[000157] A broadcast receiving device verifies the location of an ISC by interpreting a DFC. The broadcast receiver then accesses the pump based on the verified location of the pump, as indicated by the arrow (1). The SIC contains information regarding the number of

Petition 870190118091, of 11/14/2019, p. 34/167

31/160 turbo channels that make up a frame, and information regarding the structure of each of the turbo channels (turbo channel decoding information, metadata, etc.).

[000158] The broadcast reception device accesses a desired turbo channel using the information contained in the SIC, as indicated by the arrow (2), and obtains data from an application layer by processing a turbo sequence received through the turbo channel desired, as indicated by the arrow (3).

[000159] As described above, to allow a user to receive a broadcast service, a previously determined waiting time is necessary due to the fact that the above processes have to be performed after power is supplied to the broadcast receiving device and the broadcast signal has been received. To solve a problem in which a broadcast service is not provided until the SIC channel is fully interpreted, a service is supported that can be provided as a standard prior to the time when the broadcast receiving device operates and receives the SIC. Such a service is referred to as a 'primary service'. The primary service is provided by a broadcast service provider and is intended to be viewable by a user first.

[000160] FIG. 7B illustrates a process of providing a primary service by an MCAST system according to a configuration of the present invention. In FIG. 7B, the access information for accessing a primary service is present in a previously determined location on a transport board.

[000161] In the case of the ATSC transport frame according to

Petition 870190118091, of 11/14/2019, p. 35/167

32/160 ATSC standards, access information for access to a primary service can be defined in DFS. In this way, the broadcast receiver can directly access a turbo sequence for the DFS primary service without searching for and processing a SIC, as indicated by the arrow (1).

[000162] FIG. 7C illustrates a method of transmitting a turbo sequence to a primary service according to a configuration of the present invention.

[000163] A turbo sequence for a primary service is formed in the same way as other turbo sequences are formed, and can be transmitted while being mapped to a transport frame in a similar way to that of another turbo sequence. However, a turbo sequence for a primary service can be transmitted through a residual data region of a transport frame. In general, the size of a residual data region of a transport frame is smaller than that of a channel for a primary service, and therefore, a turbo sequence from the primary service is divided according to the size of the residual data region of the transport service. transport frame and is transmitted through a plurality of transport frames.

[000164] The signaling information that will be described later can be transmitted in a similar way. That is, signaling information can be transmitted alternatively through a separate channel, such as a SIC, or through a residual data region of a transport frame. A method will now be described to allow a user to obtain signaling information while viewing a primary service, with respect to a case where signaling information is transmitted via a

Petition 870190118091, of 11/14/2019, p. 36/167

33/160 separate channel and a case where signaling information is transmitted through a residual data region of a transport frame.

[000165] FIG. 7D is a flow diagram illustrating a method of obtaining signaling information in an MCAST system according to a configuration of the present invention.

[000166] In operation S710, a broadcast signal is searched for at the moment when power is supplied to a broadcast receiver.

[000167] In operation S720, the broadcast receiver processes a turbo sequence for a primary service. The turbo sequence for a primary service can be transmitted on an additional turbo channel, or it can be divided into several parts and transmitted in a residual data region of a transport frame.

[000168] In the S730 operation, the broadcast receiving device provides the primary service using the processing result in the S720 operation. Simultaneously with the S730 operation, the S740 operation is performed to obtain signaling information. Information indicating whether signaling information or turbo sequence for a primary service is / is transmitted (s) via a separate channel or a residual data region of a transport frame can be stored in a previously determined region of a transport board, and signaling information and the turbo sequence for a primary service are obtained using this information. In the case of an ATSC system, this information can be stored in DFS.

[000169] If signaling information is transmitted via a separate SIC, the S742 operation is performed for

Petition 870190118091, of 11/14/2019, p. 37/167

34/160 obtaining signaling information by processing the SIC. If the signaling information is divided into several parts and transmitted through a residual data region of a transport frame, operation S744 is performed to obtain the signaling information from the residual data region of the transport frame.

[000170] In operation S750, it is determined whether the signaling information is updated. If the signaling information is up to date, the S740 operation is performed again to obtain the updated signaling information. If the signaling information is not up-to-date, the S760 operation is performed using the signaling information, thus channel switching is performed.

[000171] FIG. 8 illustrates the high-speed access method supported by an ATSC-MCAST system according to another embodiment of the present invention. Referring to FIG. 8, signaling information is divided for high speed service access.

[000172] In the case of an enriched media service provided in real time, information such as PSI (PAT, PMT, CAT, or NIT) must be gained first for decoding multimedia data in a broadcast receiver. The user can watch a video after receiving all PSI. Even though the receiver has acquired a decoding frame, it is necessary for the user to wait until the receiver receives specific decoder information from the PSI.

[000173] ATSC-MCAST has proposed the transport of a specific multimedia decoder information descriptor to be included in each elementary sequence ("Elementary Stream"

Petition 870190118091, of 11/14/2019, p. 38/167

35/160

ES) of multimedia. This means that the decoder configuration information and multimedia data are transported at the same time. Therefore, it is not necessary for the receiver to wait to obtain the PSI.

[000174] More specifically, FIG. 8A is a diagram comparing the service access time in ATSC-MCAST according to the present invention, with that of a conventional diffusion system.

[000175] For example, a PAT and PMT transmission period is assumed to be 0.5 seconds and an I-frame transmission period is delta seconds. In the worst case, there will be a delay of 0.5 + 0.5 + delta seconds for viewing the first video as it is necessary to obtain the entire PAT, PMT, and I-frame. However, the ATSC-MCAST system requires only delta seconds to obtain a first I-frame to be presented at the receiver. In this way, the ATSC-MCAST system can quickly process the I-frame after receiving it. Decoder specific information will be described with reference to FIG. 8B.

[000176] FIG. 8B illustrates decoder configuration information (DCI) ???

<td>according to a</td><td>configuration</td><td>gift</td><td>invention.</td><td>At</td><td>DCI</td>

<td>are included in a</td><td>field 'field_of_</td><td>DCI '.</td><td></td><td></td><td></td>

<td>[000177] The field</td><td>'field_of_DCI'</td><td>illustrated</td><td>in FIG.</td><td>8B</td><td>is</td>

<td colspan="2">related to media in time</td><td>real in</td><td colspan="2">a layer</td><td>in</td>

encapsulation of MCAST. A 'decoder-specific information' field included in the 'DCI_field' field contains information specific to a media decoder. The field 'field_of_DCI' can exist only in an encapsulation package for real-time media.

Petition 870190118091, of 11/14/2019, p. 39/167

36/160

[000178] A 'Content Type' field represents a content type in the sequence. Examples of the type of content defined according to the value of this field are as described below:

[Table 1]

<td>Value</td><td>Content Type Description</td>

<td> 0</td><td>reserved</td>

<td> 1</td><td>H.264 / AVC</td>

<td> 2</td><td>HE AAC</td>

<td> 3 - 255</td><td>TBD</td>

[000179] A 'Max Decoding Buffer Size' field indicates the extent in bytes of a decoding buffer memory. The definition of a buffer memory depends on the type of a string.

[000180] A 'DSI extension' field indicates the extension of a 'decoder-specific information' field, as will be described, in bytes.

[000181] The 'Decoder Specific Information' field contains decoder specific information. The 'Decoder Specific Information' field depends on the type of string and represents the decoder specifications.

[000182] FIG. 9 illustrates a high-speed access method supported by an ATSC-MCAST system according to another embodiment of the present invention.

[000183] In FIG. 9, it is assumed that the broadcast of IP data or an IP service is provided through MCAST. In general, a service guide (“Service Guide” - SG) needs to be provided simultaneously with the diffusion of IP data or with the IP service to provide the diffusion of IP data or the IP service.

Petition 870190118091, of 11/14/2019, p. 40/167

37/160

IP. The broadcast receiver in general must first obtain the SG to obtain the broadcast of IP data or the IP service. From now on in this specification, an SG defined in OMA-BCAST is used as an example of SG but is not limited to it. Any type of SG that provides information regarding the diffusion of IP data or an IP service or access information for access to the diffusion of IP data or the IP service may be used.

[000184] A user must first obtain the SG in order to receive a service to receive a service via IP data broadcast, and thus, a broadcast reception device must remain in standby mode until the SG is received, regardless of whether the user wants to obtain the SG or not. To solve this problem, the information needed to receive broadcast data from IP or the IP service is transmitted in such a way that the service can be provided in the first place without reception from the SC. In this way, access to high-speed services is made possible in terms of the dissemination of IP data or IP service.

[000185] More specifically, FIG. 9A illustrates the structure of transport data used to access high speed services in IP data broadcast according to a configuration of the present invention.

[000186] A SIC contains IP information for receiving an SG, such as the SG's IP address. It is possible to use a fixed address already known by a broadcast receiving device as the SG's IP address, or to indicate that the SG is included in the IP information. For example, it is possible to express the transmission of the SG indirectly in

Petition 870190118091, of 11/14/2019, p. 41/167

38/160 IP information using a marker (flag) that indicates IP information corresponding to the SG.

[000187] In addition, the SIC may contain additional information for the provision of a service to a user before the broadcast receiving apparatus obtains a part or all of the SG. In the present specification, for the sake of convenience of explanation, a service that can be provided to a user before the SG is partially or fully obtained will be referred to as a 'representative service'. The additional information may contain information for the alternative provision of the dissemination of IP data corresponding to the representative service or the IP service, or information indicating the location of the information. In addition, the additional information may contain an IP address related to the representative service. In a location indicated by the IP address, there is a sequence for the provision of the representative service or information necessary for the provision of the representative service. An example of this information is unidirectional flute session information, a Session Description Protocol (SDP), or sequence processing information.

[000188] In an MCAST system, there may (m) be one or a plurality of representative services. If a plurality of representative services are provided, information regarding the representative services is provided to the broadcast receiving apparatus so that a user can select one of them. When a user selects one of a plurality of representative services, the selected representative service is provided up to the

Petition 870190118091, of 11/14/2019, p. 42/167

39/160 broadcast reception complete obtaining the SG. After the SG has been fully obtained, the user can again select a desired service based on the SG.

[000189] Alternatively, only a representative service may be provided, or a selected representative service may be provided without the selection being made by a user even if a plurality of representative services are provided.

[000190] Within a turbo channel, an IP string for the provision of a representative service and IP strings for the provision of a broadcast service in general are transmitted.

[000191] FIG. 9B is a flow diagram illustrating a high-speed service access method for broadcasting IP data according to a configuration of the present invention.

[000192] In operation S910, an IMT mapping table is obtained. IMT represents mapping information between a

<td>IP adress</td><td>and a turbo</td><td>channel,</td><td>and can be</td><td>transmitted</td><td>through</td>

<td>of a channel</td><td>SIC.</td><td></td><td></td><td></td><td></td>

<td>[000193] On</td><td>operation</td><td>S920, is</td><td>determined</td><td>if a sis</td><td>theme of</td>

<td>transport</td><td>performs</td><td>or not</td><td>provision</td><td>on one</td><td>service</td>

representative. If a representative service is not provided, the S932 operation is performed to obtain a SG. In this case, it is impossible to provide the user with a broadcast service until a previously determined part or the entire SG has been obtained. If a representative service is provided, operation S934 is performed to provide the representative service to the user. That is, the representative service is provided through parsing of a

Petition 870190118091, of 11/14/2019, p. 43/167

40/160 sequence providing the same through the use of information regarding the representative service, which are included in the SIC (or DFS) and an IMT. At the same time, the S936 operation is performed to obtain the SG in the background.

[000194] After the SG is fully obtained, the S940 operation is performed to determine whether the user's input data has been received or not. If the user input data has not been received, the S952 operation is performed to repeatedly reproduce the representative service or enter standby mode until the user input data is received. If the user input data has been received, the S954 operation is performed to process and reproduce an IP string corresponding to a channel selected by the user.

[000195] FIG. 10A illustrates service configuration information according to a configuration of the present invention.

[000196] The SIC channel contains signaling information, such as information relating to turbo channel information. In particular, the SIC has service configuration information that contains turbo channel position information for each of the turbo channels in an A-VSB frame, time slicing information, and information for processing each turbo channel. The SIC can be a type of turbo channel, and it can be present in a previously determined location in an A-VSB board.

[000197] The structure of the service configuration information will now be described with reference to FIG. 10A.

[000198] A field 'marker_of_information_of_turbo_channel' indicates whether there is turbo channel information. In the current

Petition 870190118091, of 11/14/2019, p. 44/167

41/160 configuration, the 'channel_turbo_information' field contains turbo channel information which is described in more detail later with reference to FIG. 13.

[000199] A field 'additional_service_information_ marker' indicates whether description information exists for a turbo service. In the current configuration, the 'additional_service_information' field contains additional description information for all turbo channels. Additional service information will be described in more detail below with reference to FIG. 14.

[000200] A 'filler_mark' field indicates whether a fill area exists.

[000201] A field 'information_of_indicator_of_version ()' indicates the version of the service configuration information and when this information should be updated. In the current configuration, the version of the 'ServiceConfiguration Information ()' field is indicated and when this field should be updated. The field 'information_of_version_indicator ()' will be described in more detail later with reference to FIG. 11.

[000202] A field of 'information_of_group_of_frames ()' indicates the number of a current frame and the total number of frames within a group of frames. The field 'information_of_group_of_frames ()' will be described in more detail below with reference to FIG. 12.

[000203] A 'byte' field indicates padding bytes and is used by an encoder. The field is used to fill an unassigned region having an OxFF value.

[000204] A 'CRC' field contains a CRC value.

Petition 870190118091, of 11/14/2019, p. 45/167

42/160

[000205] FIG. 10B illustrates service configuration information according to another configuration of the present invention.

<td> [000206]</td><td>a</td><td>field</td><td>in</td><td>'number</td><td colspan="3">_de_quadro_atual '</td><td>indicates a</td><td>number</td>

<td>of picture</td><td colspan="2">current.</td><td>O</td><td>number</td><td>in</td><td>frame</td><td colspan="2">is incremented</td><td>by 1</td>

<td>inside of</td><td>one</td><td>group</td><td>in</td><td>frames</td><td> .</td><td></td><td></td><td></td><td></td>

<td> [000207]</td><td>a</td><td>field</td><td>in</td><td>'number_</td><td colspan="3">_total_de_frames'</td><td>indicates the</td><td>number</td>

total frames in the frame group.

[000208] In the current configuration, the service configuration information may include information regarding the TCC or a broadcast descriptor (BD) according to the current frame number. That is, if the current frame number is an even number, the information regarding the TCC is included and if the current frame number is an odd number, information regarding the BD descriptor is included.

[000209] A field 'next_development_details_of_decision_data' indicates the total number of frames prior to updating the version of the turbo channel configuration information. In the current configuration, the 'channel_configuration_field' contains the turbo channel configuration information.

[000210] A 'TCC_version' field consists of 3 bits and indicates the version number of the TCC fields. The version number must be increased by 1 module 8 whenever there is a change in one of the fields related to TCC.

[000211] A 'channel_turbo_number' field indicates the total number of turbo channels ported by A-VSB. The number of spread out SRS channels is also specified in this field.

[000212] A 'channel_configuration_field' includes turbo channel configuration information. The 'channel_turbo_configuration' field will be described further

Petition 870190118091, of 11/14/2019, p. 46/167

43/160 in detail below with reference to FIG. 16.

[000213] A 'DB_package ()' field contains a broadcast descriptor. The 'DB_package ()' field will be described in more detail below with reference to FIG. 22.

[000214] FIG. 10C illustrates service configuration information according to another configuration of the present invention. The service configuration information illustrated in FIG. 10C are identical to those illustrated in FIG. 10B with the exception of an 'awakening mode' field.

[000215] The wake-up mode field 'indicates the TCC parsing mode of the next TCC in the' next_deviation_details_of_development_of_TCC 'field. For example, if the value of this field is set to '1', the next TCC may be subject to parsing.

[000216] FIG. 11 illustrates the structure of the 'version_indicator_information_information ()' field illustrated in FIG. 10A according to a configuration of the present invention.

[000217] In mobile broadcast, service configuration information is very crucial. A 'version_indicator_information_information ()' field that will be described later includes information for updating service configuration information. In this way, a field of 'Service configuration information ()' indicates the exact location and version of a frame that must be changed.

[000218] A 'frame_count' field indicates the total number of frames transmitted prior to changing the service configuration information. After a shipping frame is received, the service configuration information will change.

[000219] A 'version' field indicates the version of the information

Petition 870190118091, of 11/14/2019, p. 47/167

44/160 service configuration. Whenever the service configuration information is changed, the version value is incremented by 1.

[000220] FIG. 12 illustrates the structure of the 'information_of_group_of_frames ()' field illustrated in FIG. 10A according to a configuration of the present invention.

[000221] A group of frames is a group of frames created by slicing MCAST frames, and occurs periodically starting with the same number of frames. In a transmission system, a technique for including transmission data relating to a service in at least one frame and frame transmission in burst mode is referred to as a frame slicing technique. When the frame slicing technique is used, there are frames that do not contain data related to a target service and a terminal can enter an idle mode without receiving a signal in a section where such a frame is transmitted, thereby saving consumption of energy. A burst section indicates a group of frames containing data related to the target service and can be expressed using the frame number that will be described later.

[000222] A 'current_frame_number' field indicates the number of a current frame in a frame group. The frame number can be increased by 1 within a group of frames.

[000223] A field of 'total_number_of_frames' indicates the total number of frames in the frame group.

[000224] FIG. 13 illustrates the structure of the 'channel_turbo_information ()' field illustrated in FIG. 10A according to a configuration of the present invention.

[000225] A 'channel_turbo_information ()' field indicates

Petition 870190118091, of 11/14/2019, p. 48/167

45/160 turbo channel information and contains essential information for a plurality of turbo channels. Physical decoding information, information indicating whether MCAST frame slicing exists, and the total number of turbo channels are important factors. In particular, when MCAST frame slicing is supported, the 'channel_turbo_information ()' field indicates the current frame number and the total number of frame blocks to be received for a selected turbo channel.

[000226] A 'version' field consists of three bits and indicates the version of the turbo channel information. In the current configuration, the version can be increased by 1 whenever there is a change in the 'channel_turbo_information ()' field. When the version is changed, the turbo channel information will be carried forward.

[000227] A 'Turbo_svc' field indicates the total number of turbo channels in an A-VSB system according to a configuration of the present invention.

[000228] A field 'id_de_turbo_svc' indicates the identifier of a current turbo channel.

[000229] An 'Is_Enhanced' field indicates whether the data is base data or extended data. For example, when a 'scalable' video codec is used, an elementary sequence and an extended sequence can be contained in a separate turbo channel or data subchannel. If the elementary sequence and the extended sequence are contained in the separate turbo channel, it will be possible to distinguish between the elementary sequence and the extended sequence using the field 'Is_Approved'.

[000230] A field 'marker_of_Fatmento_de_Quadro_MCAST'

Petition 870190118091, of 11/14/2019, p. 49/167

46/160 specifies whether a current turbo sequence is transmitted in burst mode.

[000231] A field 'marker_of_FEC_AL_MCAST' specifies whether a current turbo sequence consists of the application layer of FEC support (AL-FEC).

[000232] A field 'posiQdo_de_inicio_de_turbo' indicates a starting position of a turbo channel.

[000233] A field of 'bits_of_fragmentos_de_turbo' indicates the index of turbo channel extension.

[000234] A 'Turbo_configuration_index' field indicates a number. If the number is n, this means that each number (nth) packet includes a fragment of turbo channel.

[000235] A field of 'encoding_ rates' indicates the index of a turbo channel encoding rate.

[000236] A 'starting_frame_number' field indicates an initial frame number of a current turbo service when MAST frame slicing exists.

[000237] A field of 'number_of_block_frames' specifies the total number of a current turbo channel.

[000238] FIG. 14 illustrates the structure of the 'additional_services_information' field ()^, illustrated in FIG. 10A according to a configuration of the present invention.

[000239] A SIC channel provides a structure for transporting additional information. In the current configuration, the 'additional_services_information' field^, contains additional information. The 'additional_Services_information' field^, it can be provided using a plurality of blocks and indicates the current and final indexes of segmented blocks.

[000240] A 'current_index' field indicates the index of a

Petition 870190118091, of 11/14/2019, p. 50/167

47/160 current index within the total number of description blocks.

[000241] A 'final_index' field indicates the index of a last block within the total number of description blocks.

[000242] An 'extension' field indicates the extent of additional service information.

[000243] A 'user_data' field indicates the syntax of the user's private data which should follow &lt;marker&gt;&lt;extension&gt; &lt;data&gt;. The marker values ​​can be defined in Table 2.

Table 2]

<td>Label</td><td>Identifier</td>

<td> 0</td><td>Reserved</td>

<td> 1</td><td>Turbo channel information descriptor</td>

<td> 2 - 255</td><td>TBD</td>

[000244] If the marker value is '1', the 'user_data' field contains a turbo channel information descriptor which will be described later with reference to FIG. 15.

[000245] FIG. 15 illustrates the structure of a 'channel_turbo_information_ description ()' field according to a configuration of the present invention. The structure of the 'channel_turbo_information_description_description' field () is similar to that of the 'channel_turbo_information' field illustrated in FIG. 13.

[000246] A 'channel_turbo_configuration ()' field contains indispensable configuration information for turbo channels. The 'channel_turbo_configuration ()' field can contain important information, such as physical decoding information, information indicating whether there is frame slicing, and information regarding the total number of turbo channels, similar to the 'channel_tourbo_channel' field illustrated in FIG. 13.

Petition 870190118091, of 11/14/2019, p. 51/167

48/160

[000247] A 'bits_selectors' field indicates whether frame slicing, a scattered SRS channel, a turbo channel, or a 'link_de_descritor_de_turbo_canal' field is present. Table 3 below illustrates the definition of the 'bits_selectors' field according to their value. In Table 3, 'x' can be '0' or '1'.

[Table 3]

<td>Value of selector bits</td><td>description</td>

<td>0B1xx</td><td>frame slicing</td>

<td>0Bx1x</td><td>spread SRS channel position</td>

<td>0Bx0x</td><td>turbo channel position</td>

<td>0Bxx1</td><td>link channel turbo descriptor</td>

[000248] A 'channel_turbo_id' field indicates the identifier of the turbo channel. When a specific turbo channel descriptor is included, this field is used to identify the turbo channel. However, if this field has a previously determined value, for example, 0x1f, in that case the descriptor will be applied to all turbo channels. For example, when a field containing information pertaining to a group of frames is updated and the value of the 'channel_turbo_id' field is 0x1f, information relating to the group of frames will be applied to the 'channel_turbo_channel' field for all channels.

[000249] An 'initial_frame_number' field indicates the number of an initial frame of a service provided in burst mode. The initial frame is a first frame to be received to allow the purchase of the service.

[000250] A 'table_count' field indicates the total number of frames to be received to obtain the service in

Petition 870190118091, of 11/14/2019, p. 52/167

49/160 burst mode.

[000251] A 'reserved' field is a field reserved for future use. The value of the 'reserved' field is set to '1'. In the present specification, the function of the 'reserved' field is identical and therefore will not be described hereinafter.

[000252] A 'turbo_group_size' field indicates the grouping size of SRS strings spread across a plurality of sectors.

[000253] An 'is_perfected' field indicates whether the current turbo channel contains improved data. If the value of this field is set to '1', this could mean that the current turbo channel contains improved data. In this case, the base channels and the enhanced channels must share the same turbo channel ID. The receiver can receive both channels and provide them as one channel. For example, if a 'scalable' video codec is used, the video quality provided when both channels are received is higher than when a single channel is received.

[000254] An 'adaptive time_label_of_time_ marker' field indicates whether a current turbo channel supports adaptive time slicing. If the value of this field is set to '1', this could mean that the current turbo channel supports adaptive time slicing. A physical configuration is changed according to this field.

[000255] A field 'encoding rates' indicates the index of a turbo channel encoding rate.

[000256] A 'full package_ marker' field indicates whether a first sector of a turbo sequence is transmitted via a null packet or a specified PID packet. If the value of this field is set to '1', in this case the first sector

Petition 870190118091, of 11/14/2019, p. 53/167

50/160 is transported via a null packet or a specified PID packet without the AF header field. Similarly, if the value of this field is set to '0', the first sector is transported through the AF field.

[000257] A field of 'sector_of_start_of_turbo' indicates the physical position of the start of the turbo sequence.

[000258] A 'turbo_group_size' field indicates the grouping size of the turbo string in a plurality of sectors.

[000259] A 'link_de_descritor_de_turbo_canal ()' field provides additional optional information related to the turbo channel. This field will be described in more detail below with reference to FIG. 17.

[000260] FIG. 16B illustrates the structure of the 'channel_configuration_field ()' field illustrated in FIG. 10B according to another embodiment of the present invention.

[000261] The structure of the 'channel_turbo_configuration ()' field illustrated in FIG. 16B is identical to the 'channel_configuration_channel ()' field illustrated in FIG. 16A with the exception of the 'perfected_protection_mode' field.

[000262] An 'enhanced_protection_mode' field indicates whether an enhanced protection mode will be supported. There is a case where an error will be easily corrected according to the type of data transmitted or a communication environment. In this case, error correction can be easily accomplished by reducing the payload extension in a packet and increasing the RS byte. If the value of this field is set to '1', the payload extension of a transport packet will be 168 bytes and the RS byte will be 40 bytes. However, if the value

Petition 870190118091, of 11/14/2019, p. 54/167

51/160

<td colspan="2">of this field</td><td>is set to '0'</td><td> ,</td><td>the extension</td><td>in</td><td>charge</td><td>useful</td>

<td>will be</td><td> 188</td><td>bytes and the RS byte will have</td><td> 20</td><td>bytes.</td><td></td><td></td><td></td>

<td> [000263]</td><td>THE</td><td>FIG. 17 illustrates the</td><td></td><td>structure</td><td>of</td><td>field</td><td>in</td>

<td>'link</td><td colspan="2">dedescritor () 'illustrated</td><td>at</td><td>FIG. 16A</td><td>in</td><td>wake up</td><td>with</td>

a configuration of the present invention.

[000264] A 'link_de_descritor ()' field allows signaling of additional information referring to each of the turbo channels. A change in information, such as numbers of groups of frames, a length of time slicing in relation to the turbo channels, and the locations of the turbo channels, will be signaled by the field 'enlace_de_descritor ()'.

[000265] A 'next_indicator' field is a 1-bit field that indicates the presence of the subsequent 'information_of_descriptor' field. If the value of this field is set to '1', the 'information_of_descriptor' field will be found below. If the value of this field is set to '0', no 'description_descriptor' fields will be present in the 'description_link_ ()' field.

[000266] A 'bookmark' (tag) field indicates the identifier of the 'description_information' field as defined in Table 4 below.

[Table 4]

<td>Highlighter (tag)</td><td>description</td>

<td> 0</td><td>Update Frame Group</td>

<td> 1</td><td>Frame Slicing Duration Update</td>

<td> 2</td><td>SRS position update</td>

<td> 3</td><td>Turbo Channel Position Update</td>

<td> 4 - 127</td><td>reserved for future use</td>

[000267] An 'extension' field indicates the total extension in

Petition 870190118091, of 11/14/2019, p. 55/167

52/160 bytes of the 'descriptor_information' field.

[000268] A 'descriptor_information' field can be defined differently according to the value of the 'marker' field. The 'descriptor_information' field defined in the

<td>Table 4</td><td colspan="2">will be described more</td><td>in detail</td><td colspan="2">forward</td><td>with</td>

<td>reference</td><td>to FIGS. 18</td><td>up to 21.</td><td></td><td></td><td></td><td></td>

<td>[000269] A</td><td>FIG. 18</td><td>illustrates the</td><td>structure of</td><td>one</td><td>field</td><td>in</td>

<td colspan="2">'update_group_</td><td>de_frames'</td><td>when the value</td><td>of</td><td>field</td><td>in</td>

<td>'highlighter'</td><td>illustrated</td><td>in FIG. 17</td><td>is defined</td><td colspan="2">like '0'</td><td>in</td>

according to a configuration of the present invention.

[000270] The updating of groups of frames can be used to change a period of time slicing. That is, the 'update — of_group — of_frames' field can be used to update the total number of frame groups. The field 'update_of_group_of_frames' can be flagged at least 6 seconds before the update. The information contained in this field will be applied to the settings of all turbo channels. When this field is received, a field of 'selector bits' can be set to '0x001' indicating update of groups of frames and a field of 'channel_id_turbo' can have a previously determined value, for example, '0x1f', which is determined to update groups of frames to the entire turbo channel.

[000271] A 'next_update_data lag' indicates the total number of frames remaining prior to the application of the number of new GOF's (Groups Of Frames ”). This field has a relative value based on the 'next_update_date_direction_ from_TCC' field mentioned above. In this way, the value of this field is changed when a TCC update occurs. That is, the value of this field is not changed

Petition 870190118091, of 11/14/2019, p. 56/167

53/160 on a frame-by-frame basis and changed whenever a TCC version change occurs, thereby reducing the number of times the TCC channel is updated.

[000272] A 'novo_GOF' field indicates the total number of new GOF's.

[000273] FIG. 19A illustrates the structure of a 'Update_of_Duration_of_Fatamento_de_Quadro' field when the 'marker' field shown in FIG. 17 is defined as '1' according to a configuration of the present invention.

[000274] A 'Frame_Form_Duration_Update_Update' field is used when the number of frames that make up the frame slicing is changed in a current turbo channel. Equation (1) below can be used to calculate the duration of a pause when frame slicing is applied. In this case, the update is performed in units of the number of frames constituting a number of frames.

(núier3_cte_qjadro_inicial + prfxima_atualização_de_ICC) * 48.4ms + cfe 'jitter type ... (1)

[000275] In Equation (1), 'jitter time' means an establishment time required for a physical layer and '48, 4 ms' means a cycle in which a VSB frame is transmitted. However, the present invention is not limited to the VSB framework. If a transmission period is determined by another transport frame and another group of frames.

[000276] A 'new_number_initial_frame' field indicates the number of a new initial frame for frame slicing within a GOF.

[000277] A 'new_frame_count' field indicates a new final frame number for slicing frames within GOF.

[000278] FIG. 19B illustrates the structure of the

Petition 870190118091, of 11/14/2019, p. 57/167

54/160 'Update_of_Duration_of_Fatamento_de_Quadro' when the value of the 'marker' field illustrated in FIG. 17 is defined as '1' according to another embodiment of the present invention.

[000279] Equation (2) indicates a time required to acquire a first frame for slicing a frame in a 'description_description_field', whose syntax is as illustrated in FIG. 19B:

(oetasagmcfepóxiim.ahalizar cteTCC + rMãsagmdpróia atalizaã * 48.4m + tenpocte 'jitter ... (2)

[000280] The 'descriptor_information' fields illustrated in FIG. 19B are identical to those illustrated in FIG. 19A with the exception of a 'next_update_data lag' field.

[000281] The 'next_update_delivery_device' field indicates the location of a frame to which new frame slicing information should be applied, based on a 'next_development_development_of_development_of_TCC' field.

[000282] FIG. 20A illustrates the structure of an 'update_of_SRS_position' field when the value of the 'marker' field illustrated in FIG. 17 is defined as '2' according to a configuration of the present invention.

[000283] A field 'update_of_SRS_position' is used when the location of a spread SRS changes. A point in time when the new location information is to be applied can be calculated to be relatively based on the start of a GOF.

[000284] A field of 'initial_frame_data' indicates the number of an initial frame to which the new SRS position should be applied within a new GOF.

[000285] A 'turbo_group_size' field indicates the size of a new turbo grouping in a plurality of

Petition 870190118091, of 11/14/2019, p. 58/167

55/160 sectors.

[000286] FIG. 20B illustrates the structure of the 'update_of_SRS_position' field when the value of the 'marker' field illustrated in FIG. 17 is defined as '2' according to another embodiment of the present invention.

[000287] The field 'updating_of_SRS_position' is identical to the one illustrated in FIG. 20A with the exception of a 'next_update_data lag' field.

[000288] The 'next_update_data lag' field indicates a next update position in which the following values ​​are applied.

[000289] A point in time in which the new location information should be applied can be expressed by adding the values ​​of a 'next_deviation_of_direction_of_direction_of_direction_of_delivery_direction' field. Otherwise, the value of the 'next_update_delivery_data' field can be used as a relative value of the 'next_detail_detailed_details_date'.

[000290] FIG. 21A illustrates the structure of a 'turbo_channel_update' field when the value of the 'marker' field illustrated in FIG. 17 is defined as '3' according to a configuration of the present invention.

[000291] The 'update_turbo_channel' field is used when the location of a turbo channel is updated. This field should be applied after the receipt of a 'next_deviation_date_of_TCC_deviation' indicating that a new GOF has been received.

[000292] A field of 'initial_frame_deviation' indicates the number of an initial frame within a new GOF. Starting

Petition 870190118091, of 11/14/2019, p. 59/167

56/160 of this table a new field of 'turbo_group_size' can be applied.

[000293] An 'is_perfected' field indicates whether a current turbo channel contains enhanced data. If the value of this field is set to '1', it could mean that the current turbo channel contains improved data. In this case, the basic and improved channels can constitute the same turbo channel ID as described above.

[000294] A field 'encoding_ rates' indicates an index of a turbo channel encoding rate.

[000295] A 'full package_ marker' field indicates whether a first sector in a turbo sequence is transmitted via a null packet or a specific PID packet without using an AF header field. If the value of this field is set to '1', in this case the first sector of the turbo sequence can be carried by a null packet or a specified PID packet without using the AF header field. If the value of this field is set to '0', then the first sector can be transported by the AF header field.

[000296] A field of 'sector_of_start_of_turbo' indicates a physical starting position of the turbo sequence.

[000297] A 'turbo_group_size' field indicates the

<td>size of</td><td>grouping</td><td>from turbo</td><td colspan="2">string in</td><td>an</td><td colspan="2">plurality</td>

<td>sectors.</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000298] A</td><td>FIG. 21B</td><td>illustrates</td><td>The</td><td>structure</td><td>of</td><td>field</td><td>in</td>

<td>'update</td><td colspan="3">_de_turbo_canal 'when</td><td>the value</td><td>of</td><td>field</td><td>in</td>

'marker' illustrated in FIG. 17 is defined as '3' according to another embodiment of the present invention.

[000299] The 'update_turbo_channel' field illustrated in

Petition 870190118091, of 11/14/2019, p. 60/167

57/160

FIG. 21B is identical to that illustrated in FIG. 21A, with the exception of a 'next_update_data lag' field, a 'adaptive time slot marker' and a 'perfected_protection_mode' field.

[000300] The 'next_update_data lag' field indicates an update position in which the subsequent values ​​are applied. A point in time in which the new position information is applied can be expressed by adding the values ​​of a field of 'next_devision_of_update_of_development_of_direction_of_direction_ofdate'. Otherwise, the value of the 'next_update_delivery_data' field may be used as a relative value of the 'next_detail_detail_development_date'.

[000301] The 'adaptive time slot marker' indicates whether a current turbo channel supports adaptive time slicing. If the value of this field is set to '1', it can be understood that the current turbo channel supports adaptive time slicing. The physical configuration of the 'channel_turbo_update' field is changed due to this field.

[000302] The 'perfected_protection_mode' field indicates whether the current turbo channel supports an enhanced protection mode. If the value of this field is set to '1', it can be understood that the current turbo channel supports the enhanced protection mode.

[000303] For example, if the value of this field is set to '1', the payload extension in a transport packet can be 168 bytes and the RS byte extension can be 40 bytes for improved protection provision. However,

Petition 870190118091, of 11/14/2019, p. 61/167

58/160 if the value of this field is set to '0', the payload extension may be 188 bytes and the RS byte extension may be 20 bytes.

[000304] FIG. 22A illustrates the structure of a 'Package_BD' field according to a configuration of the present invention.

[000305] The 'Package_BD' field will be used to transport additional information regarding turbo strings, such as an IP mapping table and turbo channel update information. This field will be applied to all turbo channels and can be transported within several fragments.

[000306] A field 'first_last^, consists of two bits and specifies whether a packet is a first or a last packet, as defined in Table 5.

Table 5]

<td>Value</td><td>description</td>

<td> 00</td><td>Intermediate package of a series</td>

<td> 01</td><td>Last package in a series</td>

<td> 10</td><td>First package in a series</td>

<td> 11</td><td>The only package</td>

[000307] A 'filler_mark' field indicates whether padding bytes exist.

[000308] A 'DB_version' field consists of three bits and indicates the version number of a broadcast descriptor ("Broadcast Descriptor" - BD). The version number will be incremented by 1 module 8 whenever the database is updated.

[000309] A 'fill_extension' field specifies the number of fill bytes in a 'package_BD' field.

[000310] A 'fill_byte' field has one or more 8-bit values ​​defined to be '0xFF' capable of being

Petition 870190118091, of 11/14/2019, p. 62/167

59/160 insertion by an encoder. This field is discarded by a decoder.

[000311] A 'Fragment_of_BD' field contains fragmented BD's. That is, a database is divided into a plurality of fragments and is provided through the field 'Fragment_of_BD'. A BD will be explained in more detail

<td>forward</td><td colspan="2">with reference</td><td>to FIG.</td><td> 23.</td><td></td><td></td><td></td>

<td> [000312]</td><td>FIG.</td><td>22B</td><td colspan="2">illustrates the</td><td colspan="2">structure of a field</td><td>in</td>

<td>'Package_</td><td>de_BD 'de</td><td colspan="3">a deal with</td><td>an</td><td>other configuration</td><td>gives</td>

<td>gift</td><td>invention.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> [000313]</td><td>The field</td><td>in</td><td>'Package</td><td>in</td><td>BD '</td><td>illustrated in FIG. 22B</td><td>is</td>

<td>identical</td><td colspan="3">to that illustrated in</td><td>FIG.</td><td>22A</td><td colspan="2">except for one field</td>

of 'system_time_ marker' and a 'system_time' field.

[000314] The 'system_time_ marker' field indicates whether the system time information is present. In this specification, a 'system_time' field contains the system time information. If the value of this field is set to '1', this means that the 'system_time' field is present.

[000315] The 'system_time' field indicates the system time. System time can be expressed on the basis of absolute time, such as UTC, which is identical with no place relation but can be expressed on the basis of time affected by a transmission system. System time can be used to correct time at a terminal. For this purpose, the difference value (time lag) according to a place can be used. System time can be used to equalize the time on one side of service provision with that on the

Petition 870190118091, of 11/14/2019, p. 63/167

60/160 service or to correct these times. For example, information such as an electronic service guide ("Electronic Service Guide" - ESG) may contain time information, for example the start or end times of each service. In this case, a broadcast reception device can start or end a service, which is intended to be provided to a user, exactly according to the established schedule, using system time information.

[000316] FIG. 23 illustrates the structure of a broadcast descriptor ("Broadcast Descriptor" - BD) according to a configuration of the present invention.

[000317] The database is fragmented into several database fragments and is mapped to the field 'DB_package'.

[000318] A field of 'number_of_DB' indicates the total number of fields of 'information_of_Diffusion_Descriptor' as will be

<td>described</td><td colspan="5">further up.</td>

<td> [000319]</td><td>a</td><td>field</td><td>in</td><td>'marker' indicates the type</td><td>of data</td>

<td>contained</td><td>at the</td><td>field</td><td>in</td><td>'information_of_Descriptor_of_</td><td>Diffusion'.</td>

<td>Examples</td><td>in</td><td>kind of</td><td colspan="3">data according to the value of this field</td>

are as follows:

[Table 6]

<td>Highlighter</td><td>description</td>

<td> 0</td><td>forbidden</td>

<td> 1</td><td>updating channel information</td>

<td> 2</td><td>IP mapping descriptor</td>

<td> 3 - 127</td><td>Reserved</td>

[000320] An 'extension' field indicates the extension of the 'Diffusion_Descriptor_information' field.

[000321] The type of data in the field

Petition 870190118091, of 11/14/2019, p. 64/167

61/160 'information-from-Descriptor-from-Diffusion' is determined according to Table 6. The structure of the 'information_discrimination_discriber' field according to data type will be described later with reference to FIGS. 24 and 25.

[000322] FIG. 24A illustrates the structure of a 'channel_information_update' field () 'when the' marker 'field illustrated in FIG. 23 has a value of 1 according to a configuration of the present invention.

[000323] The 'update_of_information_of_channel ()' field is used to update turbo channel information. This field indicates the time when new turbo channel information should be applied. Turbo channel configuration and version information can be included in this field.

[000324] A 'counter_of_ update_of_frame' field indicates a relative frame number based on the reference frame number to which a new TCC should be applied. [000325] The 'new_TCC_version' field indicates the version of the TCC information. This field must be identical to a 'TCC_version' field present in an SIC when an update is performed.

[000326] A 'channel_turbo_channel' field indicates the number of the following fields of configuration_of_turbo_channel ().

[000327] The structure of a 'new_turbo_channel_configuration ()' field can be identical to that of the 'above-mentioned_turbo_channel ()' field.

[000328] FIG. 24B illustrates the structure of the 'update_of_information_of_channel' field () 'when the' marker 'field illustrated in FIG. 23 has a value of 1 according to another embodiment of the present invention.

Petition 870190118091, of 11/14/2019, p. 65/167

62/160

[000329] The 'update_of_channel_information ()' field illustrated in FIG. 24B is identical to that illustrated in FIG. 24A with the exception of a 'next_update_data lag' field.

[000330] The field of 'next_update_data lag' indicates a table to which the new TCC can be applied. This field has a relative value based on a 'next_data_delivery_direction_date_date' field.

[000331] FIG. 24C illustrates the structure of the 'update_of_channel_information ()' field according to another configuration of the present invention.

[000332] The 'update_of_channel_information ()' field illustrated in FIG. 24C is identical to that illustrated in FIG. 24B with the exception of a 'frame_update_count_count' field and a 'new_TCC_version_count' field.

[000333] The field 'contador_de_atualização_de_fradro' indicates a table to which the new TCC should be applied.

[000334] The 'nova_versão_de_TCC' field indicates the version information of the TCC. The version value can be identical to the version of the TCC in a SIC.

[000335] FIG. 25A illustrates an IP mapping descriptor when the value of the 'marker' field illustrated in FIG. 23 is defined as '1' according to a configuration of the present invention.

[000336] The IP mapping descriptor provides mapping information between an IP string and a turbo channel. At least one of the turbo channel information, an IP address, a MAC address and a simple description of an IP can be included in the IP mapping descriptor. In the current configuration, an IP mapping table (“IP Mapping Table” - IMT) indicates an IP mapping descriptor.

Petition 870190118091, of 11/14/2019, p. 66/167

63/160

[000337] A 'version — extended' field indicates whether the IMT has been updated. If the value of this field is set to '0', it can be understood that the IMT has not been updated even if a 'DB_version_number' field is updated.

[000338] A 'number_of_IP' field indicates the total number of IP strings.

[000339] A 'reference_channel_ marker' field indicates whether a current channel is a reference channel. If the value of this field is set to '1', it can be understood that the current channel is the reference channel. An example of the reference channel may consist of an aggregated ESG channel. ESG information constitutes a large amount of information, and therefore, in general, ESG information may not be fully included in a channel. In this case, a broadcast receiver can collect all ESG information only through the reference channel. In this way, a smaller amount of ESG information can be transmitted through an individual channel than through the reference channel, thus being allocated a greater bandwidth for content.

[000340] A 'channel_turbo_id' field indicates the identifier of a current turbo channel.

[000341] A field of 'number_MT_Index_number' indicates the locations of the IP strings in a turbo channel. The IP strings are mapped to a data subchannel on the turbo channel.

[000342] A field of 'IP_channel_number_discriptor' indicates the number of 'IP_channel_description_descriptors' that are next.

[000343] A 'IP_channel_description' field contains

Petition 870190118091, of 11/14/2019, p. 67/167

64/160 additional IP channel information. This field will be described in detail below with reference to FIG. 26.

[000344] FIG. 25B illustrates an IP mapping descriptor according to another embodiment of the present invention.

[000345] The IMT illustrated in FIG. 25B is identical to that illustrated in FIG. 25A with the exception of a 'channel_number' field and a 'VMI' field.

[000346] The 'channel_number' field indicates the total number of turbo channels or data subchannels.

[000347] The 'VMI' (“Virtual Map ID”) field indicates the identifier of a data subchannel in a turbo channel.

[000348] FIG. 26 illustrates the structure of the 'IP_channel_description_field' illustrated in FIG. 25A according to a configuration of the present invention.

[000349] The 'IP_channel_description_' field is used to transmit additional information related to an IP channel as described above.

[000350] A 'marker' field is used to identify data included in the 'IP_channel_table' field. The data types according to the values ​​in this field are as follows:

[Table 7]

<td>Highlighter</td><td>description</td>

<td> 0</td><td>forbidden</td>

<td> 1</td><td>table of IP addresses</td>

<td> 2</td><td>MAC address table</td>

<td> 3</td><td>text description table</td>

<td> 4 - 255</td><td>Reserved</td>

[000351] An 'extension' field indicates the extension of the

Petition 870190118091, of 11/14/2019, p. 68/167

65/160 'description-of-Channel-of-IP' in bytes.

[000352] An 'IP_channels_table ()' field indicates IP channel information, such as an IP address and a port. This field will be described in detail below with reference to FIGS. 27 to 29.

<td>000353] A</td><td>FIG. 27A</td><td>illustrates the</td><td colspan="2">structure of a</td><td>field</td><td>in</td>

<td>table of_</td><td>address_of_</td><td>IP 'when</td><td>the value</td><td>of</td><td>field</td><td>in</td>

<td>highlighter'</td><td colspan="2">illustrated in FIG. 26</td><td>is '1' from</td><td>wake up</td><td>with</td><td>an</td>

configuration of the present invention.

[000354] An 'IP_version' field indicates an IP version 4 or 6 but the present invention is not limited in that way. That is, another version may be reserved.

[000355] The IPv4_address and the IPv6 address are described in more detail in RFC 791 and RFC 2460. In addition, the port_number is described in more detail in RFC 793 for TCP and in RFC 768 for UDP.

[000356] FIG. 27B illustrates the structure of a 'IP_address_table' field when the value of the 'marker' field illustrated in FIG. 26 is '1' according to another embodiment of the present invention.

[000357] The 'IP_address_table' field illustrated in FIG. 27B is identical to that illustrated in FIG. 27A with the exception of a 'port_number_user_user' field.

[000358] The 'port_user_user_port_number' field indicates whether port numbers exist. In the current configuration, the existence or not of a 'port_number' field is indicated in a 'IP_address_table' field.

[000359] FIG. 28 illustrates the structure of a 'MAC_address_table' field when the value of the

Petition 870190118091, of 11/14/2019, p. 69/167

66/160 'marker' illustrated in FIG. 26 and '2' according to a configuration of the present invention.

[000360] The MAC_address is 1042.

[000361] FIG. 29 illustrates 'text_description_table_' 'marker' illustrated in FIG.

The structure of a field is described in detail in RFC when the field value is '3' according to a configuration of the present invention.

[000362] A 'text_description_text_text' field provides text description for an IP channel.

[000363] A 'language_code_ISO_ISO_639' field indicates that the information in the following text is identified by the ISO 639-3 language code. In the current configuration, a 'description' field contains the text information.

[000364] The 'description' field provides a text description of the IP channel. The text description is encoded in IOS 8859-1 characters.

[000365] A multiplexing structure of the MCAST system will now be described.

[000366] A transport frame contains a plurality of

<td>turbo channels and</td><td>each</td><td>one of the</td><td>turbo</td><td>channels</td><td>contains a</td><td>plurality</td>

<td>sub-channels.</td><td>Beyond</td><td>of this,</td><td>each</td><td>one of the</td><td>sub-channels</td><td>can contain</td>

<td>sub-channels of</td><td>Dice</td><td>. Dice</td><td>From</td><td>same</td><td>types are</td><td>transmitted</td>

<td>through the</td><td colspan="2">sub-channels.</td><td>The</td><td colspan="3">data subchannels can</td>

constitute services themselves or components of services.

[000367] Several types of data can be multiplexed and transmitted or only a specific type of data can be transmitted through MCAST. As examples of the first case, signaling data, real-time media data,

Petition 870190118091, of 11/14/2019, p. 70/167

67/160

IP and object data can be multiplexed and transmitted. As examples of the latter case, only signaling data and IP data can be transmitted. In the latter case, the data subchannels can be characterized by differences in the type of IP compression.

[000368] Signaling data is transmitted via a 168 or 188 (or 187) byte MCAST transport packet. The length of the transport package is variable. An LMT specifies the locations and numbers of all data subchannels. In addition, the LMT can specify the location of data mapped to the data subchannels or the locations of IP strings in a turbo channel.

[000369] The following LMT may be present in a transport package on a turbo data channel or may be periodically or not periodically present in a package at a specific location. For example, the LMT may be present in a first signaling data subchannel or in an MCAST packet header. In addition, the LMT can be present in each of the frames but cannot be transmitted when the locations of service components are fixed in frames.

[000370] An LIT contains service configuration information, and a number and identifier for each of the data subchannels.

[000371] A conventional broadcasting system seeks a desired program through PID filtering, whereas an MCAST system can directly provide a user with a desired service by detecting the exact location of the data that constitute each service on a frame-by-frame basis through an LMT and / or an LIT without conducting

Petition 870190118091, of 11/14/2019, p. 71/167

68/160 filtration.

[000372] FIG. 30A illustrates an MCAST multiplexing structure according to a configuration of the present invention.

[000373] In detail, FIG. 30A illustrates a case in which signaling data, real-time data, IP data and object data are multiplexed. A frame is divided into a service access region for accessing a service, for example, an LMT or an LIT, and a data region for data transmission. A MCAST transport frame according to a configuration of the present invention can be transmitted while being inserted into a transport frame of another broadcast system, can be transmitted separately, or can be transmitted while being mapped on a one-to-one basis. for a transport frame of another diffusion system. In the current configuration, an MCAST transport frame is transmitted via an ATSC transport frame.

[000374] As described above, the MCAST transport frame is divided into subchannels according to data types. Subchannels are channels subdivided by physical division of turbo channels transmitting a sequence of data according to the type of data. In FIG. 30A, the subchannels are subdivided into a subchannel for a real-time data type, a subchannel for an IP data type, and a subchannel for an object data type.

[000375] Sub-channels can be divided into independent data sub-channels. A data subchannel includes more than one transport package. A data subchannel consists of a set of 188-byte (or 168-byte) MCAST transport packets within an ATSC frame. The package extension can be variable.

Petition 870190118091, of 11/14/2019, p. 72/167

69/160

[000376] FIG. 30B illustrates an MCAST multiplexing structure according to another embodiment of the present invention.

[000377] In detail, FIG. 30B illustrates a case where only signaling data and IP data are multiplexed. LMT information can be transmitted while being included in a SIC or an IP data type subchannel.

[000378] FIG. 31A illustrates an MCAST frame structure and an LMT according to a configuration of the present invention.

[000379] FIG. 31A illustrates in more detail the subchannel illustrated in FIG. 30A. Referring to FIG. 31A, the MCAST transport frame consists of a signaling subchannel, a real time media subchannel, an IP subchannel and an object subchannel. That is, at least one of three types of data, such as real-time media data, IP data, and object data, is transmitted via the MCAST transport frame.

[000380] Each of the sub-channels includes a data sub-channel.

[000381] The real-time media subchannel transmits media data in real time, such as an A / V sequence. In the current configuration, the real-time media subchannel consists of a data subchannel 1 (R-1) and a data subchannel 2 (R-2). The IP subchannel transmits IP data, and includes a data subchannel (IP-1) in the current configuration. The object subchannel transmits object data that is used in real time or is used after being received and stored in a broadcast service reception apparatus. In the current configuration, the object subchannel includes a data subchannel 1 (O-1), a data subchannel 2 (O-2), a data subchannel 3 (O-3) and a data subchannel 4 (O-4).

Petition 870190118091, of 11/14/2019, p. 73/167

70/160

[000382] A service consists of more than one service component. Thus, all service components of a service must be received in order for the service to be provided. A data subchannel is a pathway through which only one service component is transmitted. Thus, in order to obtain access to a service, it is necessary to know the locations of all data subchannels that respectively transmit components of the service.

[000383] Service access information, such as an LMT or an LIT, for access to service components that constitute a service, is included in a header part of a transport package. The transport package can include at least one of a 'header' field, a 'LMT' field, a 'LIT' field, and a payload.

[000384] An LMT field provides the structure of the data sub-channel and physical location information, which will be described later with reference to FIG. 34.

[000385] FIG. 31B illustrates an MCAST framework structure and

<td>an LMT</td><td colspan="2">according to a</td><td>another</td><td>configuration</td><td colspan="3">of this</td>

<td>invention.</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> [000386]</td><td>Making</td><td>reference</td><td>to FIG.</td><td>31B, only</td><td>Dice</td><td>in</td><td>IP</td>

<td colspan="2">are transmitted</td><td>through</td><td>on one</td><td>picture of</td><td>MCAST</td><td>and</td><td>at</td>

VMI information is included to identify a data subchannel.

[000387] It is very important to detect the location of a data subchannel in an MCAST frame, and this information is included in an LMT as described above. The location of the data subchannel is detected using a lag in the frame. However, when there is a change in the data subchannel, for example,

Petition 870190118091, of 11/14/2019, p. 74/167

71/160 when a data subchannel is added or canceled, it is necessary to recognize this change. If data subchannels can be identified by identifying

<td colspan="2">virtual mapping</td><td>("Virtual</td><td>Map Identification</td><td colspan="2">- VMI), will be</td>

<td>possible</td><td>check</td><td colspan="2">easily a change in</td><td>sub-channels</td><td>in</td>

<td>Dice. THE</td><td>VMI will be</td><td>described</td><td>in detail with</td><td>reference</td><td>The</td>

<td>FIG. 32.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000388]</td><td>FIG. 32</td><td>illustrates</td><td>a verification method</td><td colspan="2">fication of a</td>

<td>change</td><td colspan="2">in a subchannel</td><td>data through</td><td>use</td><td>in</td>

virtual map identification (“Virtual Map Identification - VMI) according to a configuration of the present invention.

[000389] The VMI according to a configuration of the present invention is included in signaling information such as an LMT, an LIT, or an IMT. The VMI is an identifier that identifies data subchannels. It is possible to determine whether a data subchannel has changed using the VMI.

[000390] Referring to FIG. 32, in a previous table, the data subchannels that constitute a service 1 are audio 1, video 1 and image 1. Values ​​1, 3, and 5 are respectively assigned to these data subchannels as VMI values. .

[000391] In a subsequent frame, the data subchannel corresponding to image 1 is canceled. If the location of a data subchannel is identified with only a lag in a frame, it is unreasonable to use a lag as an identifier as the lags of data subchanges are different on a frame basis. However, if VMI's are respectively assigned to data subchannels

Petition 870190118091, of 11/14/2019, p. 75/167

72/160 as unique identifiers, it will be possible to accurately recognize a data subchannel in which a change occurs.

[000392] FIG. 33 is a flow diagram illustrating a method of acquiring a service using VMI according to a configuration of the present invention.

[000393] In operation S3310, an LMT and / or an LIT is obtained.

[000394] In operation S3320, the VMI of a data subchannel that transmits a service component that constitutes a requested service is verified.

[000395] In operation S3330, an IMT is obtained.

[000396] In operation S3340, a VMI is checked on a current turbo channel.

[000397] In operation S3350, data is obtained by accessing a desired data subchannel.

[000398] FIG. 34A illustrates the structure of an LMT according to a configuration of the present invention.

[000399] An LMT according to a configuration of the present invention includes a 'bitmap type' field, a 'version number' field and at least one 'data subchannel number' field.

[000400] The 'bitmap type' field indicates the type of data included in an MCAST transport frame transmitted at predetermined time intervals. The object data, real-time media data and IP data are supposed to be transmitted through the MCAST transport frame.

[000401] The 'bitmap type' field consists of three bits, each of which can indicate whether a data type is present. For example, a first bit is supposed to indicate whether there is real-time media data present in the

Petition 870190118091, of 11/14/2019, p. 76/167

73/160 frame, a second bit indicates whether there are IP data present in the frame, a third bit indicates whether there are object data present in the frame, and there is data corresponding to a case in which the bit value is '1'. Thus, if the value of the 'bitmap type' field is '111', this means that all data types are present and its value of the 'bitmap type' field is '011', this means that IP data and object data are present.

[000402] The 'version number' field indicates the version of the LMT.

[000403] The 'data subchannel number' field indicates the total number of data subchannels for each type of data. The value of this field corresponds to the total number of 'channel pointer' fields indicating the physical address of a data subchannel.

[000404] Referring to FIG. 34A, insofar as there are I 'channel pointer' fields that correspond to real-time media data, there are I data subchannels that transmit media data in real time.

[000405] Each of the 'channel pointer' fields indicates the physical location of a data subchannel. Index numbers can be sequentially assigned to the 'channel pointer' fields. The numbers that are assigned sequentially to the 'channel pointers' fields in the LMT are referred to as 'LMT index numbers'. LMT index numbers may not be included in the 'channel pointer' fields but are instead assigned sequentially to the 'channel pointer' fields when a broadcast receiver interprets a 'LMT' field. The LMT index numbers are assigned for reference to the sub-channel channel pointers that constitute respective services in the LIT.

Petition 870190118091, of 11/14/2019, p. 77/167

74/160

[000406] FIG. 34B illustrates in detail the structure of the LMT according to FIG. 34A.

[000407] If the value of the 'bitmap type' field is assumed to be '011', the value of the 'data subchannel number' field for IP data is '2' and the value of the 'data subchannel number' field is '3', the 'channel pointer' fields 1 and 2 indicate the locations of data subchannels for IP data and the 'channel pointer' fields 3 up to 5 indicate the locations of data subchannels for IP data. If LMT index numbers are sequentially assigned to these 'channel pointer' fields, LMT index numbers 1 through 5 are respectively assigned to 'channel pointer' fields 1 through 5.

[000408] FIGS. 35A and 35B illustrate the structures of an LMT according to configurations of the present invention.

[000409] A 'marker' field indicates whether LMT information will be included. In the current configuration, the LMT information is in fact included in an 'LMT_information' field.

[000410] The 'extension' field consists of eight bits and indicates the extension of a 'information_of_LMT' field.

[000411] The field 'information_of_LMT' specifies the locations of data subchannels in a subchannel and signaling data (“Signaling Data” - SD) in a signaling subchannel. The 'information_of_LMT' field will be described with reference to FIG. 36C.

[000412] FIG. 36 illustrates the structure of the 'LMT_information' field illustrated in FIG. 35 according to a configuration of the present invention.

[000413] A field of 'coverage_of_LMT' indicates the number of the following LMT's that are identical to a current LMT. Per

Petition 870190118091, of 11/14/2019, p. 78/167

75/160 example, if the value of a 'version_number' field that will be described later is' 1 'and the value of the' MLM_range 'field is' 001', this means that an LMT whose version is' is present 1'. Similarly, if a subsequent LMT is not identical to the current LMT, the value of this field will be set to '0'.

[000414] A 'version_number' field consists of four bits and indicates the version of the LMT. The version number will be incremented by 1 module 16 whenever one of the fields related to LMT is changed.

[000415] A field 'delimitation_of_LMT' indicates the location of packages covered by a current LMT. The value of the 'LMT_ delimitation' field is not limited if it can represent the packages covered by the current LMT. For example, the value of this field can indicate the lags or the total number of packages covered by a current LMT.

[000416] A field of 'SD_final_deviation' is an 8-bit field indicating the position of the end of a signaling subchannel. If there is no signaling data contained in the

<td>subchannel</td><td>signaling, the</td><td>value</td><td>this</td><td>field</td><td>should</td><td>to be</td>

<td>defined</td><td>like '0'.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000417]</td><td>A 'number_ field</td><td>_de_IP '</td><td>indicates</td><td colspan="2">the number of</td><td>sub-</td>

<td>channels of</td><td>IP data.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000418]</td><td colspan="2">A 'lag_f_ field</td><td>inal_de_</td><td>IP 'is</td><td colspan="2">a field of</td>

bits indicating the end positions of IP data subchannels contained in an IP subchannel. If there is no IP data contained in a first IP data subchannel, the value of this field must be set to '0'.

[000419] FIGS. 37A and 37B illustrate the structure of an LMT and an 'information_of_LMT' field according to another

Petition 870190118091, of 11/14/2019, p. 79/167

76/160 configuration of the present invention.

[000420] Referring to FIG. 37A, the LMT indicates the end lag information for data subchannels. The data subchannels transmit four types of

<td>Dice:</td><td colspan="2">signaling data,</td><td>Dice</td><td>in</td><td>media in time</td><td>real,</td>

<td>Dice</td><td>IP and data</td><td>from obje</td><td>to, and</td><td>at</td><td>locations of</td><td>sub-</td>

<td>channels</td><td>of data from</td><td>wake up</td><td>with</td><td>type</td><td>are expressed</td><td>with</td>

final lags.

[000421] A start value for each of the data subchannels is always '1' and the numbers are assigned individually to the data subchannels according to the data subtypes. However, if there is no first data subchannel, the value of a 'next_sticker ()' field is set to '0'.

[000422] If there is temporarily no valid data packet in one or more parcels, the lag of a corresponding data subchannel will be the same as that of a previous packet. The lag of the first data subchannel is set to '0'.

[000423] Each of the fields is defined with reference to FIG. 37B.

[000424] A 'SPEP_mark' field indicates whether or not there is a signal encapsulation packet (“Signal Encapsulation Packet” - SEP).

[000425] A 'SPEP_final_difference' field is an 8-bit field indicating the position of the end of a SEP data subchannel when the value of the 'SPEP_mark' field is '1'.

[000426] A first 'next_indicator' field indicates whether there is an additional 'present_final_depth_data lag' present. If the value of this field is '0', this means that there is no longer a field of

Petition 870190118091, of 11/14/2019, p. 80/167

77/160 'real_tempo_defasagem_de_fasagem_de_fasagem_de_final_de_tempo_real'.

[000427] The 'real-time_final_deviation' field is a 7-bit field that indicates the position of the end of the real-time data subchannel that transmits media data in real time. If a current MCAST plot has no data in real time, the value of this field must be set to '0' or this field may not exist.

[000428] A second field of 'next_indicator' indicates whether there is an additional field of 'IP_final lag'. If the value of this field is '0', a current field of 'IP_final_deviation' will be the last one and if the value of this field is '1', another 'IP_deviation_deviation' field will be present.

[000429] An 'IP_final_deviation' field is a seven-bit field that indicates the end position of an IP data subchannel that transmits IP data. If no IP data subchannel is present in the current MCAST plot, the value of this field must be set to '0' or this field may not exist.

[000430] A third field of 'next_indicator' indicates whether there is an additional field of 'lag_of_final_of_object' in addition. If the value of this field is '0', a current field of 'object_final_deviation' will be the last one and if the value of this field is '1', there will be a subsequent field of 'object_final_deviation'.

[000431] An 'object_final_deviation' field is a seven-bit field that indicates the position of the end of an object data subchannel that transmits object data. If there is no

Petition 870190118091, of 11/14/2019, p. 81/167

78/160 no object data subchannel in the current MCAST plot, the value of this field must be set to '0' or this field may not exist.

[000432] FIG. 38 illustrates the structure of an LMT according to another embodiment of the present invention.

[000433] A field of 'coverage_of_LMT' indicates the number of

Subsequent LMT's that are identical to a current LMT. If a subsequent LMT is not identical to the current LMT, the value of this field will be set to '0'.

[000434] A 'version_number' field is a two-bit field that indicates the version of the LMT. The version number will be incremented by 1 module 4 whenever one of the fields related to LMT is changed.

[000435] A field of 'bits_selectors (SEP, inverted, IP)' indicates the type of an existing data subchannel. In FIG. 38, due to the fact that only IP data is assumed to be transmitted through an MCAST frame, a second bit is a reserved bit. If a first bit is '1', this means that there is a SEP data subchannel and if a third bit

<td>is '1',</td><td colspan="2">this means that there is a subchannel</td><td>in</td><td>Dice</td><td>in</td>

<td>IP.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000436]</td><td>A 'extension_of_MT' field</td><td colspan="3">indicates the extent of</td><td>one</td>

<td>field of</td><td>LMT.</td><td></td><td></td><td></td><td></td>

<td> [000437]</td><td>A 'delimitation__ field</td><td>LMT 'indicates</td><td>O</td><td>number</td><td>in</td>

package lags covered by a current LMT.

[000438] A 'SEP number' field is an eight-bit field that indicates the total number of SEP data subchannels.

[000439] A 'VMI' field indicates the identifiers of data subchannels, with singularity in a turbo channel.

[000440] A 'number_of_IP' field indicates the number of sub

Petition 870190118091, of 11/14/2019, p. 82/167

79/160 channels of IP data.

[000441] An 'IP_final_deviation' field is an eight-bit field that indicates the position of the end of an IP data subchannel. Both the 'end_of_SEP_deviation' field and the 'end_of_event_deviation' field are calculated by counting packets based on a packet containing the LMT. In another configuration of the present invention, a lag can be calculated in bytes.

[000442] FIG. 39 illustrates the structures of an MCAST frame and an LIT according to a configuration of the present invention.

[000443] An LIT can be located in a signaling subchannel that is positioned first in a turbo channel containing data within an ATSC frame. Each service consists of one or more service components and the LIT indicates a list of the service components. That is, the LIT will specify the service composition information. The position of a data subchannel is detected from the LMT referred to above.

[000444] The LIT is closely related to the LMT and may be present in each of the tables.

[000445] FIG. 40 illustrates the structure of an LIT according to

<td>with one</td><td colspan="2">configuration</td><td>present invention.</td><td></td><td></td><td></td>

<td> [000446]</td><td>One field</td><td>in</td><td>'service_number'</td><td>indicates</td><td>the number</td><td>in</td>

<td>services</td><td>included</td><td>in</td><td colspan="2">a MCAST framework of</td><td>a deal with</td><td>The</td>

<td>gift</td><td>invention.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000447]</td><td>One field</td><td>in</td><td>'version_number'</td><td>indicates</td><td>the version</td><td>gives</td>

LIT.

[000448] Each of the service fields consists of a 'service identifier' field and at least one 'number

Petition 870190118091, of 11/14/2019, p. 83/167

80/160 LMT index '. The 'LMT index number' is assigned to a 'channel pointer' field as described above with reference to FIG. 34B. In this way, a broadcast receiver is capable of detecting the physical address of a data subchannel for a desired service in a transport frame by interpreting the LIT.

[000449] FIGS. 41A and 41B illustrate the structure of an LIT according to another embodiment of the present invention.

[000450] When a plurality of data sub-channels form a service, the LIT specifies the structure of the service. The locations of the data subchannels can be determined by the lag information of the data subchannels included in the LMT. That is, each component can be identified using an accumulator counter for each of the data sub-channels.

[000451] A 'service_number' field is a 6-bit field that indicates the number of services available in a current frame.

[000452] A 'version_number' field is a 10-bit field that indicates the version number of LIT-related fields. The version number will be incremented by 1 whenever one of the LIT related fields is changed.

[000453] A 'service_ID' field is an 8-bit field that identifies a service on a turbo channel.

[000454] A 'next_indicator' field is a 1-bit field that indicates whether additional fields of 'next_indicator' and 'number_of_MT_Index' are present. If the value of this field is '1', this means that the fields 'next_indicator' and 'number_of_MT_Index' are present, and if the value of this field is '0', the

Petition 870190118091, of 11/14/2019, p. 84/167

81/160 'indicator — Next' and 'LMT_Index_number' fields^,they no longer exist.

[000455] A field of 'type_information' indicates the type of a data subchannel indicated by the field of 'number_of_MT_Index^,, which is defined according to the value of this field as follows:

[Table 8]

<td>Value</td><td>description</td>

<td> 00</td><td>reserved</td>

<td> 01</td><td>real-time data</td>

<td> 10</td><td>IP data</td>

<td> 11</td><td>object data</td>

[000456] A field of 'number_of_MT_ index^, is a 7-bit field that indicates a set index for each LMT. The value of this field is increased individually according to the 'type_information' field^,. That is, referring to FIG. 40, the LMT index number is increased sequentially regardless of the type of the data subchannel. However, with reference to FIG. 41, the LMT index number is individually increased according to the type of the data subchannel.

[000457] For example, it is assumed that two channel pointers corresponding to an IP data subchannel and three channel pointers corresponding to an object data subchannel are present in an MCAST frame. In this case, referring to FIG. 40, the index numbers 1 through 5 are assigned sequentially to the channel pointers, and therefore, the LMT index numbers 3 through 5 are respectively assigned to the channel pointers corresponding to the object data subchannel. However, referring to FIG. 41,

Petition 870190118091, of 11/14/2019, p. 85/167

82/160 the LMT index numbers are individually increased according to the type of the data subchannel, and thus, the LMT index numbers from 1 to 3 are respectively assigned to the channel pointers corresponding to the subchannel of object data.

[000458] FIG. 42A is a flow diagram illustrating a method of providing a service using an LMT and an LIT according to a configuration of the present invention.

[000459] Referring to FIG. 42A, an LMT field is transmitted at regular intervals and is located in a previously determined area of ​​an MCAST frame. In operation S4201, when a transport frame is being received, a broadcast service reception apparatus acquires and interprets a signaling package including service access information, which is located in a previously determined area of ​​the transport frame.

[000460] In operation S4203, the broadcast service receiving apparatus determines whether or not there is an LMT field in the signaling package. If it is determined in operation S4203 that there is no LMT field in the signaling packet, it will be determined whether a previous LMT field has been stored in the broadcast service receiving apparatus in operation S4205. If it is determined in operation S4205 that there is a previous LMT field in the broadcast service receiving apparatus, the method proceeds to operation S4211.

[000461] If it is determined in operation S4203 that an LMT field exists in the signaling package, the broadcast service receiving apparatus determines whether the version of the LMT field has been updated using the version information

Petition 870190118091, of 11/14/2019, p. 86/167

83/160 included in the LMT field, in operation S4207. If it is determined in operation S4207 that the version of the LMT field has been updated, the LMT field is interpreted in operation S4209. By interpreting the LMT field in operation S4209, information is obtained on the locations of the data subchannels.

[000462] In operation S4211, the broadcast service receiving device determines whether there is an LIT field in the signaling package. If it is determined in operation S4211 that there is no LIT field, it will be determined whether there is a previous LIT field in the broadcast service receiving apparatus, in operation S4213. If it is determined in operation S4213 that there is a previous LIT field, the method proceeds to operation S4219.

[000463] If it is determined in operation S4211 that exists in the LIT field in the signaling package, the version of the LIT field in operation S4215 will be determined. By interpreting the LIT field in operation S4217, interconnection information related to each of the services is obtained, that is, service configuration information.

[000464] In operation S4219, services are obtained from the results of the interpretations of the LMT field and the LIT field, and are then processed.

<td> [000465]</td><td>FIG. 42B is a diagí</td><td>love</td><td>illustrative flow of</td><td>one</td>

<td>method of</td><td colspan="2">provision of a service</td><td>through the use of</td><td>an</td>

<td colspan="2">LMT and an LIT according to the present invention.</td><td>with</td><td>another configuration</td><td>gives</td>

<td> [000466]</td><td>Referring to the</td><td colspan="2">FIG. 42B, an LMT contains</td><td>one</td>

<td>field of</td><td>'MST_range',</td><td>and</td><td>therefore, the location</td><td>in</td>

<td>an LMT</td><td>subsequent can be</td><td colspan="2">detected even if not</td><td>for</td>

Petition 870190118091, of 11/14/2019, p. 87/167

84/160 it is possible to receive a package containing the LMT, due to an error, or if LMT's are not periodically inserted. In this way, the location of the LMT and an LMT field insertion cycle in a transport field are variable. The operations in FIG. 42B indicated by reference numbers identical to those of FIG. 42A are identical to those of FIG. 42A, and therefore detailed descriptions thereof will be omitted here.

[000467] Referring to FIG. 42B, in operation S4220, an LMT is extracted from an MCAST frame according to LMT pointer information extracted from a previous LMT. The LMT pointer information points to the location of a subsequent LMT. In this way, even when the LMT ceases to be inserted in a previously determined area of ​​the transport frame, it is possible to easily extract the LMT from the transport frame.

[000468] In operation S4203, it is determined whether or not an LMT field exists at a location indicated by the LMT pointer information. If it is determined in operation 4203 that an LMT field exists, the method proceeds to operation S4207. If it is determined in operation 4203 that there is no LMT field, the method proceeds to operation S4230. The absence of an LMT field at the location indicated by the LMT pointer information implies a case in which the LMT field is omitted and in which case an error is generated in the LMT field.

[000469] In operation S4230, it is determined whether the previous LMT field is valid, based on information regarding the total number of LMT's with the same version, which are included in the previous LMT field. The fact that the previous LMT field is valid means that it can be used

Petition 870190118091, of 11/14/2019, p. 88/167

85/160 continuously. If it is determined in operation S730 that the previous LMT field is valid, the method proceeds to operation S4211.

[000470] The structure of transport information according to data types will now be described.

[000471] First, in the case of services rich in real time, it will be necessary to obtain and decode PSI information from MPEG-2 and ATSC to decode elementary multimedia streams in a broadcast system. Then, it is necessary for a decoder to wait to receive a frame that should be the first to be decoded. Subsequently, a user can view video. In MCAST, important decoding information is encoded in an information descriptor included in each of the elementary multimedia strings.

[000472] In this case, the decoder configuration information (DCI) and multimedia data can be transmitted simultaneously for high speed access, as described above. That is, the INNs are inserted into an I-frame and are then transmitted. INNs have been described above with reference to FIG. 4.

[000473] FIG. 43 illustrates the object transmission information structure according to a configuration of the present invention.

[000474] Referring to FIG. 43, an 'object_delivery_information' field contains signaling information for transmitting an object. The 'object_delivery_information' field includes the object's expiration end date, parameters for AL-FEC, and a

Petition 870190118091, of 11/14/2019, p. 89/167

86/160 additional descriptor. Directory components are objects or other directories.

[000475] A field of 'object_of_delivery_information' can be transmitted via a signaling encapsulation packet (“Signaling Encapsulation Packet” - SEP).

[000476] A field of 'bookmark_of_directory_information' indicates whether a directory exists.

[000477] The object information can be expressed in a tree with a directory. If the value of the 'directory_information_ marker' field is '1', it can be understood that there is a directory.

[000478] An 'object_number' field indicates the total number of objects transmitted through the 'object_delivery_information' field.

[000479] A 'directory_number' field indicates the total number of directory information. In the current configuration, a 'directory_information' field contains directory information.

[000480] The 'directory_information' field contains directory information, which will be described in more detail below with reference to FIG. 44.

[000481] An 'object_id' field indicates the object identifier.

[000482] A field of 'expiration_ marker_of_valid_value' indicates whether the object has an expiration time.

[000483] A field of 'number_of_MT_Index' indicates the numbers of indexes of data subchannels categorized according to data type.

[000484] An 'object_extension_id_id' field is used

Petition 870190118091, of 11/14/2019, p. 90/167

87/160 as an additional identifier for a plurality of objects when the objects are transmitted in the same data subchannel.

[000485] An 'AL-FEC mode' field indicates an ALFEC mode. Examples of the AL-FEC mode according to the value of this field are described below:

[Table 9]

<td>value</td><td>Mode</td>

<td> 0</td><td>MCAST AL FEC</td>

<td> 1-15</td><td>reserved</td>

[000486] A 'total_extension' field indicates the object's extension in bytes.

[000487] A 'time_table' field contains time information allowing objects not to be used after their expiration dates. This field will be described in detail below with reference to FIG. 45.

<td>[000488] One</td><td>'mode_ field</td><td colspan="2">de_coding 'indicates a</td><td>mode</td><td>in</td>

<td>coding</td><td>used by</td><td>AL-FEC. Examples</td><td>of</td><td>mode</td><td>in</td>

<td>coding</td><td>according</td><td>the value of this</td><td>field</td><td>are</td><td>the</td>

following:

Table 10]

<td>Value</td><td>Description (n, k)</td>

<td> 0</td><td> (2880,2304)</td>

<td> 1</td><td> (1920, 1536)</td>

<td> 2</td><td> (960,768)</td>

<td> 3 - 15</td><td>Reserved</td>

[000489] A 'fill_extension' field indicates the fill extent in a last object source block.

Petition 870190118091, of 11/14/2019, p. 91/167

88/160

[000490] A 'number of_descriptors' field indicates the number of subsequent 'descriptor' fields.

[000491] A 'marker' field indicates object data types. In the current configuration, this field indicates the type of data included in the 'descriptor' field. Examples of data types according to the value of this field are as follows:

Table 11]

<td>Value</td><td>description</td>

<td> 0</td><td>forbidden</td>

<td> 1</td><td>content name description</td>

<td> 2</td><td>mime type description</td>

<td> 3 - 15</td><td>Reserved</td>

[000492] An 'extension' field indicates the extension in bytes of the 'descriptor' fields.

[000493] A 'descriptor' field indicates descriptors according to the value of the 'marker' field. The 'descriptor' field according to the 'marker' field value will be described in more detail below with reference to FIGS. 46 and 47.

[000494] FIG. 44 illustrates the structure of the 'directory_information' field illustrated in FIG. 43 according to a configuration of the present invention.

[000495] A 'directory_number' field indicates the number of directories.

[000496] A 'directory_id' field indicates the identifier of the directory.

[000497] A field of 'extension_of_directory_name' indicates the extension in bytes of the name of the directory.

[000498] A 'directory_name' field indicates the name of the directory encoded in ISO 8859-1 characters.

[000499] A 'number_of_components' field indicates the number

Petition 870190118091, of 11/14/2019, p. 92/167

89/160 of components included in each of the directories.

[000500] A field of 'directory_id, object_id' indicates the identifiers of objects or other directories.

[000501] FIG. 45 illustrates the structure of a 'time_table' field illustrated in FIG. 43 according to a configuration of the present invention.

[000502] A 'years' field indicates a year. It is possible to express the amount of time that has elapsed from a specific point in time. For example, if the year 1970 is a reference year and the value of this field is '0', this means the year 1970.

[000503] A 'months' field indicates a month from January to December.

[000504] A 'days' field indicates a date.

[000505] A 'hours' field indicates an hour between one and twenty-four hours.

<td>[000506] One</td><td>field of</td><td>'minutes</td><td>'indicates</td><td>one</td><td>minute of</td><td>in between</td><td>one</td>

<td>up to sixty</td><td>minutes.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000507] A</td><td>FIG. 46</td><td>illustrates</td><td colspan="3">the structure of a</td><td>field</td><td>in</td>

<td>'descriptor</td><td>_name of_</td><td>content'</td><td>When</td><td>O</td><td>value of</td><td>field</td><td>in</td>

<td colspan="2">illustrated 'marker'</td><td>in FIG.</td><td>43 for</td><td> '1'</td><td>according</td><td>with</td><td>an</td>

configuration of the present invention.

[000508] A field of 'content_name_extension' indicates the extension of the content name in bytes.

[000509] A content name field 'indicates the name of the content encoded in ISO 8859-1 characters.

[000510] FIG. 47 illustrates the structure of a 'mime_type_description_field' when the value of the 'marker' field illustrated in FIG. 43 is '2' according to a configuration of the present invention.

Petition 870190118091, of 11/14/2019, p. 93/167

90/160

[000511] A 'mime_type_extension' field indicates the length of the mime type in bytes. (mime stands for "Multipurpose Internet Mail Extensions ???" [000512] A 'mime_type' field indicates the type of mime.

This field is defined for strings that encode any type of media registered with the IANA. For more detailed information, see RFC 2045, RFC 2046, and http://www.iana.org/assignments/media-typs.

[000513] FIG. 48 illustrates the relationship between an encapsulation package and a transport package in an MCAST system according to a configuration of the present invention.

[000514] In the MCAST system, a transport layer is divided into an encapsulation layer and a packet forming layer. The encapsulation layer is responsible for fragmenting the application data and the transport layer divides the encapsulation package into MCAST transport packages.

[000515] More specifically, the encapsulation layer encapsulates all types of application data to be adapted for an A-VSB transmission method. That is, an encapsulation package having an adaptive structure for

<td>Dice</td><td>in</td><td>application is</td><td colspan="2">created for</td><td colspan="3">be suitable for the format</td><td>From</td>

<td>Dice</td><td>in</td><td>application.</td><td>The data</td><td>in</td><td>application</td><td>include</td><td>Dice</td><td>in</td>

<td>media</td><td>in</td><td>real time,</td><td>data from</td><td>IP,</td><td>data from</td><td>object and</td><td>Dice</td><td>in</td>

signaling. The encapsulation package has a specific structure according to the type of application.

[000516] The package forming layer divides an encapsulation package generated from an encapsulation layer into at least one transport package. The package size of

Petition 870190118091, of 11/14/2019, p. 94/167

91/160

<td>transportation can be</td><td>determined</td><td>so</td><td>variable,</td><td>per</td>

<td colspan="2">example, 168 or 188 bytes. [000517] The payload of the package of</td><td>MCAST can</td><td colspan="2">be transmitted</td>

<td>concatenated.</td><td>This is a</td><td>part or the</td><td>totality</td><td>in</td>

<td>two or more packages</td><td colspan="2">encapsulation can be</td><td>included in</td><td>one</td>

<td>MCAST package. In</td><td>a deal with</td><td>the present</td><td>invention,</td><td>are</td>

<td>a field is used</td><td>from 'first</td><td>_last 'and</td><td>One field</td><td>in</td>

<td>'pointer_field'</td><td colspan="2">for indication of this</td><td>situation</td><td>with</td>

simultaneous bit saving.

[000518] The field 'first-last' and the field 'field_of_post' present in a header region of a transport package, as will be described later, can be defined as follows:

[Table 12]

<td rowspan="2">first_last field</td><td rowspan="2">Field of Pointer</td><td colspan="2">description</td>

<td>First Package Encapsulation</td><td>Second Pack of Encapsulation</td>

<td> 00</td><td> 1</td><td rowspan="2">starts at the previous TP and ends at this TP</td><td>starts at this TP and does not end at this package</td>

<td> 01</td><td> 1</td><td>starts at this TP and ends at this package</td>

<td> 10</td><td> 1</td><td rowspan="2">starts and ends in this TP</td><td>starts at this TP and does not end at this package</td>

<td> 11</td><td> 1</td><td>starts at this TP and ends at this package</td>

[000519] The 'pointer_field' field indicates whether an MCAST transport packet includes two or more encapsulation packets. If the value of this field is '1', this means that two or more encapsulation packages are present in the MCAST transport package. In the current

Petition 870190118091, of 11/14/2019, p. 95/167

92/160 configuration, the value of this field is '1', and therefore two or more encapsulation packages are contained in the MCAST transport package.

[000520] The field 'first_last' indicates whether the start and end of the encapsulation packages are included in the MCAST transport package. For the sake of convenience of explanation, a preceding package and a subsequent package will be referred to respectively as a first encapsulation package and a second encapsulation package between two or more continuous encapsulation packages. If two or more encapsulation packages are included in the MCAST transport package, the end of the first encapsulation package and the beginning of the second encapsulation package are included in the MCAST transport package.

[000521] A first bit of the 'first_last' field indicates whether the start of the first encapsulation packet is included in the MCAST transport packet, and a second bit of that field indicates whether the end of the second encapsulation packet is included in the MCAST transport package. For example, if the value of this field is '10', both the beginning and the end of the first encapsulation package are included in the MCAST transport package and only the beginning of the second encapsulation package is included in the transport package. MCAST.

[000522] FIGS. 49 to 55 illustrate examples of an encapsulation package according to a configuration of the present invention.

[000523] FIGS. 49A and 49B illustrate the structure of an encapsulation package for signaling according to a configuration of the present invention.

Petition 870190118091, of 11/14/2019, p. 96/167

93/160

[000524] The package illustrated in FIG. 49A includes a 4-byte header and a payload. The payload can include an application description or metadata, such as an ESG and an Electronic Program Guide -

<td>EPG). Beyond</td><td>of this,</td><td>the payload includes</td><td>Dice</td><td colspan="2">optional,</td><td>such</td>

<td>as a</td><td>table</td><td>information</td><td colspan="2">mapping</td><td>in</td><td>IP and</td>

<td>information</td><td>of goal</td><td>-data of an object.</td><td></td><td></td><td></td><td></td>

<td colspan="2">[000525] One field</td><td>from 'first_last'</td><td>it is a</td><td>field</td><td>of 2</td><td>bits</td>

which specifies whether an encapsulation packet is a first packet or a last packet. This field can be defined according to its value, as shown in Table 5.

[000526] A 'compression_mark' field is a 1-bit field that specifies whether the payload data is compressed or not. If the value of this field is '1', this means that the payload data is compressed.

[000527] A 'signal_type' field indicates the type of the payload data. The type of payload data according to the value of this field can be as illustrated in Table 13 or Table 14.

Table 13]

<td>Value</td><td>description</td>

<td> 0</td><td>forbidden</td>

<td> 1</td><td>[TBD]</td>

<td> 2</td><td>Object Provisioning Information</td>

<td> 3 - 31</td><td>Reserved</td>

Table 14]

<td>Value</td><td>description</td>

<td> 0</td><td>forbidden</td>

Petition 870190118091, of 11/14/2019, p. 97/167

94/160

<td> 1</td><td>IP mapping table</td>

<td> 2 - 31</td><td>Reserved</td>

[000528] A 'SequenceNumber' field is an 8-bit field that indicates a value that is incremented within the same data type as an encapsulation packet. The value of this field returns to '0' if a maximum value is reached. The 'sequence_number' field is used for an object fragmentation identifier during a retransmission.

[000529] A 'version_number' field is a 4-bit field indicating the version number of a Signaling Encapsulation Packet - SEP. The version number is incremented by 1 whenever the encapsulation payload version is changed.

[000530] A 'package_extension' field indicates the extension in bytes of the payload in the package.

[000531] A 'data_bytes' field is an 8-bit field. The type of data transmitted via the payload depends on the value of the 'signal_type' field.

[000532] FIGS. 50A and 50B illustrate the structure of an encapsulation package for real-time data according to a configuration of the present invention.

[000533] The package illustrated in FIG. 50 is an encapsulation package for real-time data type, and includes a header, an additional field, and a payload.

[000534] A 'first_ultimate' field is a 2-bit field that specifies whether an encapsulation packet is a first

<td>package or one</td><td colspan="2">last package. This one</td><td>field</td><td>Can be</td><td>defined</td><td>in</td>

<td>according to</td><td>your</td><td>value as</td><td>if</td><td>finds</td><td>illustrated</td><td>at</td>

<td>Table 5.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000535] One</td><td>field</td><td>of 'Tipo_de_RT</td><td>it is a</td><td>field of</td><td>6 bits</td><td>what</td>

Petition 870190118091, of 11/14/2019, p. 98/167

95/160 indicates the type of data transmitted through the payload. An example of a data type according to the value of this field can be as follows:

[Table 15]

<td>Value</td><td>description</td>

<td> 0</td><td>Audio</td>

<td> 1</td><td>Video</td>

<td> 3 - 63</td><td>Reserved</td>

[000536] A 'DCI_label' field indicates whether there is decoder configuration information (DCI) in the header of the encapsulation package. In the current configuration, the 'DCI_field' field contains DCI.

[000537] A 'DC_version' field indicates the DCI version. The value of this field is closely related to that of the DC field and must be defined in order to be equal to the value of the same (or of the DCI_field) of a transport package.

[000538] An 'addition_mark' field indicates whether additional information is present in the encapsulation package header. In the current configuration, the 'additional_field' field includes additional information.

[000539] A 'DCI_extension' field indicates the extension in bytes of the 'DCI_field' field in the packet header.

[000540] The 'DCI_field' field includes DCI. The 'DCI_field' field (or a 'decoder_configuration_information' field^,) was described above with reference to FIG. 4.

[000541] A 'package_extension' field indicates the length in bytes of a package's payload after the 'package_extension' field.

Petition 870190118091, of 11/14/2019, p. 99/167

96/160

[000542] A 'PTS_mark' field indicates whether there is PTS information present in the encapsulation packet header. In the current configuration, a 'PTS' field contains PTS information.

[000543] A 'DTS_mark' field indicates whether DTS information is present in the encapsulation packet header. In the current configuration, a 'DTS' field contains DTS information.

[000544] A 'filler_mark' field indicates whether there are padding bytes present in the encapsulation packet header.

[000545] A 'signal_crossing_control' field [scrambling control] contains a mode of crossing signals [scrambling] of the payload of the encapsulation package.

[000546] The 'PTS' field is a 33-bit field that indicates a presentation time stamp (“Presentation Time Stamp” PTS) as defined in ISO / IEC 13818-1.

[000547] The 'DTS' field is a 33-bit field that indicates a Decoding Time Stamp (DTS) as defined in ISO / IEC 13818-1.

[000548] A 'fill_extension' field indicates the extent in bytes of filler data in the package. In the current configuration, a 'fill_byte' field contains fill data.

[000549] The 'fill_byte_field' has an 8-bit value equal to '0xFF' and can be inserted by an encoder. This field is discarded by a decoder.

[000550] A 'data byte_field' consists of eight bits.

[000551] FIG. 51 illustrates the syntax of an encapsulation package for real-time data according to another

Petition 870190118091, of 11/14/2019, p. 100/167

97/160 configuration of the present invention. The fields in the encapsulation package illustrated in FIG. 51 are identical to those in FIG. 50.

[000552] FIGS. 52A and 52B illustrate the syntax of an encapsulation packet for IP data according to a configuration

<td>of this</td><td>invention.</td><td></td><td></td><td></td><td></td>

<td>[000553] O</td><td>illustrated package</td><td>at</td><td>FIG. 52</td><td>is</td><td>used for</td>

<td>streaming</td><td>of a datagram of</td><td>IP.</td><td colspan="2">The datagram</td><td>IP can be</td>

<td>divided in</td><td>a plurality</td><td>in</td><td>packages</td><td>in</td><td>encapsulation and</td>

subsequently transmitted. There is a need to represent whether a current package is a last package, and can be used in this case in the 'last_last' field which will be described later. Alternatively, if the value of the 'first_last' field is set to '0x01' or '0x03, a current IP encapsulation packet can be determined to be a last packet.

[000554] If a target encapsulation packet is a first packet, a header field contains information indicating whether this encapsulation packet is the first or the last packet, information indicating whether there is additional information, information regarding the included IP data format in a payload region, and information regarding the extent of the encapsulation package.

[000555] If the target package is not a first package, the header field includes information indicating whether this package is the first or the last package, sequence number information, and information regarding the extension of the package .

[000556] An additional header field contains information indicating whether subsequent additional information exists,

Petition 870190118091, of 11/14/2019, p. 101/167

98/160 information regarding the type of additional information, information regarding the extent of additional information, and additional information.

[000557] A 'first_last' field is a 2-bit field that indicates whether a current packet is a first packet or a last packet. This field can be defined according to its value, as shown in Table 5.

[000558] An 'addition_mark' field is a 1 bit field that indicates whether additional information is present. In the current configuration, an 'additional_data' field contains additional information. If the value of this field is '1', it can be understood that the 'additional_data' field exists.

[000559] An 'IP_type' field is a 5-bit field that indicates the type of data transmitted via an IP payload. For example, this field can be used to distinguish between IPv4 and IPv6.

[000560] A 'sequence_number' field consists of four bits and is incremented by 1 within the same type of encapsulation packet data. The value of this field returns to '0' if it reaches a maximum value. This field is used as an IP fragmentation identifier during a retransmission.

[000561] An 'encapsulation_package_extension' field consists of 12 bits and indicates the extent of the payload in bytes.

[000562] A 'continuity_ marker' field consists of a bit and indicates whether '{marker, extension_additional_data}' fields will subsequently occur. If the value of this field is '0', it can be understood that a current field is a last field containing additional information.

Petition 870190118091, of 11/14/2019, p. 102/167

99/160

[000563] A 'marker' field is a 7-bit field that indicates the type of an 'additional_data' field. This field acts as a container that can contain different types of information that will be additionally necessary for transmitting IP data. The type of information that will be additionally required is not limited.

[000564] An 'extension' field indicates the extension in bytes of the 'additional_data' field.

[000565] The extension of the 'additional_data' field can be

<td>determined</td><td colspan="2">so</td><td colspan="2">variable. The</td><td>'Dice_</td><td colspan="3">additional 'include</td>

<td>information</td><td colspan="2">according</td><td>with the field</td><td>in</td><td colspan="2">'highlighter'</td><td> .</td><td></td>

<td>[000566] One</td><td>field</td><td>in</td><td colspan="2">'useful load'</td><td>can</td><td>to be</td><td>determined</td><td>in</td>

<td colspan="2">variable shape and</td><td colspan="2">includes data</td><td>in</td><td colspan="2">packages</td><td colspan="2">IP as</td>

<td>defined in</td><td>field</td><td>in</td><td>'IP_type'</td><td> .</td><td></td><td></td><td></td><td></td>

<td>[000567] A</td><td>FIG.</td><td> 53</td><td>illustrates the</td><td colspan="2">syntax</td><td>in</td><td>a package</td><td>in</td>

encapsulation for real time data according to another embodiment of the present invention.

[000568] The package illustrated in FIG. 53 is identical to that of FIG. 52 except that a header is changed.

[000569] FIGS. 54A and 54B illustrate the structure of a package for object data according to a configuration of the present invention.

[000570] The package illustrated in FIG. 54A is an encapsulation package for object data type transmission. The packet includes a plurality of transport packets through which object data types are transmitted. The package is divided into a header, additional information, and a payload. An additional header field contains additional information regarding the payload.

[000571] The object data is transported through a

Petition 870190118091, of 11/14/2019, p. 103/167

100/160 object data subchannel according to two methods which will be described in more detail below with reference to FIG. 56.

[000572] If an encapsulation packet is a first packet, a header field contains information indicating whether this packet is a first or a last packet, information indicating whether there is additional information, information identifying the object data that is provided through a payload field, information regarding the type of object data, and information regarding the extension of the package.

[000573] If an encapsulation packet is not a first packet, the header field contains information indicating whether this packet is a first packet or a last packet, information indicating whether there is additional information, sequence number information, and information regarding the package extension.

[000574] The additional header field contains information indicating whether or not subsequent additional information is present, information regarding the type of additional information, information regarding the extent of additional information, and additional information.

[000575] A 'first_last' field indicates whether a current packet is a first or a last encapsulation packet. This field can be defined according to its value, as shown in Table 5.

[000576] In the 'addition_mark' field it indicates whether additional information is present in the header of the encapsulation package. In the current configuration, an 'additional_field' field contains additional information.

Petition 870190118091, of 11/14/2019, p. 104/167

101/160

[000577] An 'object_id' field is used to identify all objects provided through the same data subchannel.

[000578] An 'object_type' field specifies the type of object data, for example, jpeg (compressed or not), text (compressed or not), or mp3.

[000579] A 'sequence_number' field indicates fragmentation information.

[000580] A 'package_extension' field indicates the extent of subsequent data.

[000581] A 'continuity_ marker' field specifies whether an 'additional_field' will be found next. If the value of this marker is set to '1', this means that the 'additional_field' field will be next, and if the value of this field is set to '0', this means that a current 'additional_field' field is the last.

[000582] A 'bookmark' field indicates the type of object decoder specific information. This field shows a subdivision of the type of object data specified in the 'object_type' field. For example, if the 'object_type' field indicates text (compressed), the data type can be subdivided according to a compression method. In this case, the data type can be expressed as 'text with GZIP compression' through the 'bookmark' field.

[000583] An 'extension' field expresses the extension in bytes of the 'additional_field_data' field.

[000584] An 'additional_field_data' field contains the specific object decoder information.

[000585] A 'payload' field contains the object data.

[000586] FIGS. 55A and 55B illustrate the structure of a package

Petition 870190118091, of 11/14/2019, p. 105/167

102/160 for object data according to another embodiment of the present invention.

[000587] A 'first_last' field is a 2-bit field that indicates whether a packet is a first or a last encapsulation packet. The definition of this field according to its value is shown in Table 5.

[000588] A 'object_delivery_mode' field indicates a source block mode. If the value of this field is '0', a source block number may not be used, and if the value of this field is 3, the field is inverted for the future.

[000589] An 'object_extension_id_id' field is used as an additional identifier for a plurality of objects when the objects are transmitted within the same data subchannel.

[000590] A 'source_block_block_number_8' field consists of 8 bits and indicates the number of a source block number. The value of this field represents the number of a source block to which a current OEP belongs.

[000591] A 'source_block_number_number_16' field consists of bits and indicates the number of a source block. The value of this field represents the number of a source block to which a current OEP belongs.

[000592] A 'version' field indicates the version number of the object data. The version number is increased by 1 whenever the object data is changed. A change to an object means that the object is updated. For example, when a name is added to a mapping file, an object consisting of the mapping file is changed.

[000593] A 'fragment_number' indicates fragmentation information for a field source block or an object

Petition 870190118091, of 11/14/2019, p. 106/167

103/160 when the source block or object extension exceeds a maximum packet extension.

[000594] A 'package_extension' field indicates the package extension in bytes.

[000595] FIG. 56 illustrates a method of transmitting object data according to a configuration of the present invention.

[000596] One or more pieces of object data are provided at once through a data subchannel. A case in which a piece of object data is provided through a data subchannel is referred to as a simple object mode, and a case in which a plurality of pieces of object data is provided through a subchannel data is referred to as a multiple object mode.

[000597] In multiple object mode, it is necessary to assign identifiers to a series of object data in the data subchannel respectively. Alternatively, a plurality of object data portions transmitted through the same data subchannel can be identified using object ID. Otherwise, when a packet contains an 'additional_field' field for transmitting additional information such as information from object data characteristics, a series of objects in the same data subchannel can be identified by inserting a ' object_extension_id 'in a' additional_field 'field.

[000598] FIG. 57 illustrates the application of AL-FEC according to a configuration of the present invention.

[000599] An OEP packet contains a header and a payload and consists of a plurality of transport packets. An SEP provides information on the use of AL-FEC and specific parameters. A method of configuring an AL-FEC layer and

Petition 870190118091, of 11/14/2019, p. 107/167

104/160 objects will now be described with reference to FIG. 57.

[000600] When MCAST AL-FEC is applied, objects are fragmented into a plurality of source blocks. Each of the source blocks consists of packages having a previously determined extension. The length and package numbers are determined by an MCAST ALFEC encoding mode. After MCAST AL-FEC encoding is performed, a redundant package is added. Error correction can be performed within the range of the redundant package.

[000601] An MCAST transport package will now be described here.

[000602] FIG. 58A and 58B illustrate a transport package and a transport package header structure according to configurations of the present invention.

[000603] Referring to FIG. 58A, a transport package according to a configuration of the present invention includes a base header field, a PCR information field, a pointer field, a padding field, an LMT field, an LIT field, and a payload field.

[000604] The base header field contains information indicating whether a transport packet is a first or last encapsulation packet, information indicating whether a PCR reference is present, information indicating whether DCI information is present in a field of encapsulation packet header, information indicating whether

<td>exists</td><td>an</td><td>region</td><td>in</td><td>fill,</td><td>information</td><td>indicating</td><td>if</td>

<td>exists</td><td>an</td><td>table</td><td>LMT</td><td>, and information</td><td>indicating</td><td>if there is</td><td>an</td>

<td>table</td><td>LIT.</td><td>These</td><td colspan="5">fields will be described in more detail</td>

<td>forward</td><td>with</td><td colspan="2">reference</td><td>to FIG. 59.</td><td></td><td></td><td></td>

<td> [000605</td><td>] A</td><td>FIG.</td><td>58B</td><td colspan="2">illustrates the structure of</td><td>One field</td><td>in</td>

Petition 870190118091, of 11/14/2019, p. 108/167

105/160 filling a transport package according to a configuration of the present invention.

[000606] The transport package filling field according to a configuration of the present invention can include filling extension information and filling bytes.

[000607] An LMT field and an LIT field in the transport package are as described above with reference to FIGS. 34 to 41.

[000608] FIGS. 58C and 58D illustrate a transport package and a transport package header structure according to another embodiment of the present invention.

[000609] The package illustrated in FIGS. 58C and 58D can be used when only one type of data is transmitted, for example, when only IP data is transmitted via a MAST system.

[000610] FIG. 59A illustrates the syntax of a transport package according to a configuration of the present invention.

[000611] A 'first_last' field indicates whether a transport packet is a first or a last encapsulation packet. The definition of this field according to its value is as shown in Table 5.

[000612] In the 'DC_label' field, indicates whether there is DCI information present in the header of an encapsulation package. In the current configuration, a 'decoder_configuration_information' field includes DCI.

[000613] A 'pointer_mark' field indicates whether there is a 'pointer_field' field in the header of a transport package.

Petition 870190118091, of 11/14/2019, p. 109/167

106/160

[000614] In the 'filler_mark' field it indicates whether there is a 'fill' field in the transport package header.

[000615] A field of 'marker_MT_' indicates whether there is a field of 'field_of_LMT' in the header of the transport package.

[000616] A field of 'marker_IT_IT' indicates whether there is a field of 'field_of_LIT' in the header of the transport package.

[000617] A 'PCR_mark' field indicates whether or not the transport package includes a 'PCR_field' field. If the value of this field is '1', it can be understood that the transport package includes the field 'field_of_PCR'.

[000618] A 'pointer_field' indicates the start position of a second payload when two encapsulation packages are present in a transport package.

[000619] A 'fill_extension' field indicates a fill size in bytes within a packet.

[000620] A 'fill_byte' field has an 8-bit value that is equal to '0xFF' which is inserted by an encoder. The 'fill-byte_field' is discarded by a decoder.

[000621] The fields from a 'bitmap_type' field to a 'object_channel_ pointer' field have the same structure as the LMT illustrated in FIG. 34, and therefore will only be briefly described.

[000622] The 'bitmap_type' field indicates the type of data provided via a transport packet. Each bit in this field has a specific meaning. A first bit of this field means that there is a real-time data channel, a second bit of this field means that there is an IP data channel, and a third bit of this field means that

Petition 870190118091, of 11/14/2019, p. 110/167

107/160 there is an object data channel.

[000623] The 'version_number' field indicates the version number of an LMT. The version number is increased by 1 module 16 whenever the LMT data is changed.

[000624] A 'realtime_channel_channel_number' field indicates the number of data subchannels in a real-time media type channel.

[000625] A 'IP_channel_number' field indicates the number of data subchannels in an IP type channel.

[000626] An 'object_channel_number' field indicates the number of data subchannels in an object type channel.

[000627] A 'real-time_channel_ pointer' field indicates the location of a real-time data type data subchannel in a data channel.

[000628] A 'IP_channel_ pointer' field indicates the location of an IP data type data subchannel in the data channel.

[000629] A 'object_channel_ pointer' field indicates the location of an object data type data subchannel in the data channel.

[000630] The fields from a field of 'service_number' to a field of 'number_MT_Index_number' are identical to the LIT

<td>illustrated</td><td>at</td><td>FIG.</td><td> 40</td><td colspan="2">and will therefore be described here only</td>

<td colspan="2">briefly.</td><td></td><td></td><td></td><td></td>

<td> [000631]</td><td>a</td><td>field</td><td>in</td><td>'service_number' indicates the</td><td>number of</td>

<td>services</td><td>what</td><td>can</td><td>to be</td><td>used within a channel</td><td>of data.</td>

<td> [000632]</td><td>a</td><td>field</td><td>in</td><td>'version_number' indicates the</td><td>number of</td>

<td>version of</td><td>one</td><td>field</td><td>in</td><td colspan="2">LIT. The version number is increased by 1</td>

<td colspan="2">whenever the</td><td>Dice</td><td>in</td><td>signaling are changed.</td><td></td>

[000633] A 'service_ID' field identifies a service in

Petition 870190118091, of 11/14/2019, p. 111/167

108/160 a turbo channel. The ID has a specific value in the turbo channel.

[000634] A 'next_indicator' field indicates the presence of a subsequent 'next_indicator' field and a subsequent 'MT_Index_number' field. For example, when the value of this field is '0', this means that there are no more fields for 'next_indicator' or 'number_of_MT_Index'.

[000635] The field 'number_MT_Index_Number' indicates the location of a data subchannel in an LMT.

[000636] An 'index_number' field indicates the sequence number of an elementary channel associated with a service.

[000637] A 'program_reference_base_reference_field^,/^,program_reference_reference_program_relationship 'includes a 42-bit PCR reference divided into two parts and subsequently coded. The first part is a 33-bit field whose value is a base obtained from the same equation defined in 2-1 on page 14 in MPEG-2 specification 13818-1. The second part is a 9-bit field whose value is obtained from the same equation that is defined in 22 on page 14 in the MPEG-2 specification 13818-1.

<td> [000638]</td><td>At the</td><td>field of</td><td>'byte_de_dados' consists</td><td>in 8 bits</td><td>and</td>

<td colspan="2">includes data</td><td>of package</td><td>encapsulation.</td><td></td><td></td>

<td> [000639]</td><td>THE</td><td>FIG. 59B</td><td>illustrates the structure of</td><td>a package</td><td>in</td>

<td colspan="3">shipping according</td><td colspan="3">with another configuration of this</td>

<td>invention.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000640]</td><td>The</td><td>fields in</td><td colspan="3">transport package illustrated in FIG.</td>

<td>59B are</td><td colspan="2">identical to</td><td>transport package</td><td>illustrated</td><td>at</td>

<td>FIG. 59A.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000641]</td><td>THE</td><td>FIG. 59C</td><td>illustrates the structure of</td><td>a package</td><td>in</td>

transport according to another configuration of this

Petition 870190118091, of 11/14/2019, p. 112/167

109/160 invention.

[000642] The structure of the transport package illustrated in FIG. 59C is identical to the transport package of FIG. 19A with the exception of an 'error_label' field.

[000643] The 'error_label' field indicates whether or not there is an error in a current package. If the value of this field is '1', there is an error in this packet when the packet is deformed from the packet form.

[000644] FIG. 59D illustrates the structure of a transport package according to another configuration of the present

<td colspan="6">invention.</td>

<td> [000645]</td><td>The</td><td>fields</td><td>at the</td><td>shipping package</td><td>illustrated in FIG.</td>

<td>59D are</td><td colspan="2">identical</td><td>to</td><td colspan="2">of the transport package illustrated in</td>

<td>FIG. 59A</td><td> .</td><td></td><td></td><td></td><td></td>

<td> [000646]</td><td>At</td><td>FIGS.</td><td>60A</td><td>and 60B illustrate the</td><td>structures of a</td>

<td>package</td><td>in</td><td colspan="2">transport,</td><td>a header</td><td>base and a field</td>

according to another embodiment of the present invention.

[000647] The transport package illustrated in FIG. 60A includes a plurality of header fields and a payload field. Each of the header fields includes base header information, information indicating whether or not a pointer exists, LMT information, additional information, and a payload. An IP datagram and signaling packets are provided through the payload field.

[000648] In detail, FIG. 60A illustrates the syntax of a transport package according to another embodiment of the present invention.

[000649] A 'first_last' field is a 2-bit field that specifies whether a packet is a first or a last packet

Petition 870190118091, of 11/14/2019, p. 113/167

110/160 encapsulation, as defined in Table 5.

[000650] In the 'indicator-of-package-de-signaling' field, it indicates whether the payload data is signaling data. If the value of this field is '1', it can be understood that the data

<td>provided through</td><td>in</td><td>One field</td><td>in</td><td>'charge</td><td>useful'</td><td>are</td><td>data from</td>

<td>signaling.</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000651] In the field</td><td>in</td><td colspan="2">'indicator_of_</td><td>mistake'</td><td>indicates</td><td>if</td><td>a package</td>

<td>includes an error.</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000652] One field</td><td>in</td><td>'highlighter_</td><td>add</td><td>ional '</td><td colspan="2">it's a field</td><td>1 bit</td>

which indicates whether additional information exists. In the current configuration, an 'additional_field' field contains additional information. If the value of this field is '1', it can be understood that the 'additional_field' field exists.

[000653] A 'compression_mark' field indicates whether an IP datagram is compressed. If the value of this field is '1', this means that an IP datagram provided through the 'payload' field is compressed.

[000654] A 'pointer_label' field indicates whether there is another IP datagram or signaling data. If the value of this field is '1', it can be understood that there is another IP datagram or signaling.

[000655] A 'continuity_mark' field is a 1-bit field that indicates whether there is a '&lt;mark&gt; &lt;extension&gt; &lt;additional field data&gt;' field. That is, if the field of '&lt;marker&gt; &lt;extension&gt; &lt;additional field data&gt;' is referred to as the 'Additional field' field, it can be understood that the 'Additional field' exists when the value of the 'continuity_mark' field 'is' 1' and that the 'Additional Field' field does not exist when the 'continuity marker' field value is' 0 '.

Petition 870190118091, of 11/14/2019, p. 114/167

111/160

[000656] In the 'bookmark' field, define the data type of additional information, as follows:

[Table 16]

<td>Value</td><td>description</td>

<td> 0</td><td>fill-in field</td>

<td> 1</td><td>LMT field</td>

<td> 2</td><td>compression parameter field</td>

<td> 3 - 127</td><td>Reserved</td>

[000657] An 'extension' field indicates the extent of additional information. In the current configuration, an 'additional_field' field contains additional information, and therefore the 'extension' field indicates the extension of the 'additional_field' field.

<td>[000658] O</td><td>field</td><td>of 'field</td><td>_additional'</td><td>contains the</td><td colspan="2">information</td>

<td>additional.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000659] O</td><td>field</td><td>from 'campo_</td><td>de_postteiro '</td><td>it's a field</td><td>'of 8:</td><td>bits</td>

<td>that indicates</td><td>an</td><td>lag</td><td>since</td><td>beginning of</td><td>package</td><td>in</td>

<td>transport</td><td>until the</td><td>first</td><td>byte of</td><td>one second</td><td>package</td><td>in</td>

<td>encapsulation</td><td>at the</td><td>pack of</td><td>transport</td><td>when the</td><td>package</td><td>in</td>

transport includes two or more encapsulation packages.

[000660] A 'data byte_field' contains an IP datagram or signaling data. The data can be fragmented.

[000661] FIGS. 61A and 61B illustrate the structure of a 'fill_field' field when the value of the 'marker' field illustrated in FIG. 60 is '0' according to a configuration of the present invention.

[000662] The 'marker' field indicates that there will be a field below.

[000663] An 'extension' field is an 8-bit field that indicates the length of the padding field. At present

Petition 870190118091, of 11/14/2019, p. 115/167

112/160 configuration, a 'fill_byte' field contains data

<td colspan="2">filling,</td><td>and</td><td>therefore,</td><td>the field of '</td><td>extension 'indicates</td><td>The</td>

<td>extension of</td><td>field</td><td>in</td><td>'byte_de_</td><td>fill'</td><td> .</td><td></td>

<td>[000664] O</td><td>field</td><td>in</td><td>'byte_de_</td><td>fill'</td><td>has a value of</td><td> 8</td>

<td>bits which is</td><td colspan="2">equal</td><td>the '0xFF'</td><td>and can be</td><td>inserted by</td><td>one</td>

<td>encoder.</td><td>This one</td><td colspan="3">field is discarded by a</td><td>decoder.</td><td></td>

<td>[000665] A</td><td>FIG.</td><td> 62</td><td>illustrates</td><td>the structure</td><td>of a field</td><td>in</td>

'field_of_LMT' when the value of the 'marker' field illustrated in FIG. 60 is '1' according to a configuration of the present invention.

[000666] A 'marker' field indicates that LMT information will follow. In the current configuration, an 'LMT_information' field contains LMT information.

<td>[000667] One</td><td>field of</td><td>'extension' is</td><td>a field of</td><td>8 bits that</td>

<td>indicates the</td><td>extension</td><td>in bytes</td><td>on one</td><td>field of</td>

<td>'information_</td><td>de_LMT '.</td><td></td><td></td><td></td>

[000668] The field 'information_of_LMT' contains position information of all IP data within an IP data subchannel and position information of all signaling data within a signaling data subchannel. This field has been described above with reference to FIGS. 34 to 39.

[000669] FIG. 63 illustrates the structure of a 'compaction_field_parameter' field when the value of the 'marker' field illustrated in FIG. 60 is '2' according to a configuration of the present invention.

[000670] A 'marker' field indicates whether information related to compaction parameters will be found next. In the current configuration, a 'compression_parameter' field contains information regarding compression parameters.

Petition 870190118091, of 11/14/2019, p. 116/167

113/160

[000671] An 'extension' field is an 8-bit field that specifies the extension in bytes of a 'compression_type' field and the 'compression_parameter' field.

[000672] The 'compression_type' field indicates the type of compression. Additional information regarding the type of compaction will be carried by an 'additional_field' field. An example of the type of compaction according to the value of the 'type_of_compaction' field is illustrated below:

Table 17]

<td>'compression parameter'</td><td>description</td>

<td> 0</td><td>No compression</td>

<td> 1</td><td>ROHC</td>

<td> 2 - 255</td><td>Reserved</td>

[000673] The 'compaction_parameter' field contains parameters related to the compression of the payload data. The parameters vary according to the type of compaction.

[000674] FIGS. 64A and 64B illustrate the structure of a signaling package according to a configuration of the present invention.

[000675] Signaling data is transported via a payload from an MCAST transport package. Signaling data contains additional information regarding an IP datagram. The IMT information carried through a signaling packet includes information on the association between IP strings and IP data subchannels.

[000676] A 'signal_type' field indicates the type of data provided by the payload, as follows:

[Table 18]

Petition 870190118091, of 11/14/2019, p. 117/167

114/160

<td>Value</td><td>description</td>

<td> 0</td><td>forbidden</td>

<td> 1</td><td>IP mapping table</td>

<td> 2 - 31</td><td>Reserved</td>

[000 677] A 'version_number' field is a 3-bit field that indicates the version number of a signaling package. The version number is incremented by 1 whenever the signaling data transmitted via the payload is changed.

[000678] A 'payload_extension' field is a 16-bit field that indicates the extent of the following signaling data.

[000679] A 'data_byte' field contains signaling data according to a 'signal_type' field.

[000680] A method of supporting OMA-BCAST through MCAST will now be described, and the relationship between OMA-BCAST and MCAST according to a configuration of the present invention.

[000681] An ATSC-M / H terminal supports not only IPv6 but also IPv4 for general encapsulation and network packet transmission. An ATSC-M / H system can also use both IPv6 and IPv4. The Internet protocol allows a carrier layer and a management layer to be distinguished in an abstract and logical way from each other. The IP datagrams are encapsulated in an MCAST transport packet. For MCAST transmission, mapping information between an IP datagram and a turbo channel is required, and such an IP address mapping signaling can be performed through the IMT mapping table mentioned above.

[000682] An association between an OMA BCAST service and MCAST will now be described. The most important factors of this

Petition 870190118091, of 11/14/2019, p. 118/167

115/160 association are signaling, the discovery of a service guide entry point, and the discovery of broadcast sessions. For this purpose, it is necessary that the IP strings and transport channels are associated with each other and signaled. To access an OMA BCAST service, it is first necessary to ensure a point of entry for service announcement information. Service announcement information can be provided through more than one turbo channel. In MCAST, the location information of a turbo channel at the service's entry point is transmitted using an IMT transmitted through a SIC. In addition, an IMT containing location information of IP strings included in turbo channels can be present in a predetermined location of each of the turbo channels. For the sake of convenience of explanation, the mapping information transmitted through a SIC is referred to as 'i-MT' and the mapping information on a turbo channel transmitting data is referred to as 'IMT'.

[000683] For the provision of an OMA-BCAST service guide, a service guide announcement channel and a service guide supply channel are included in turbo channels. In particular, one of the turbo channels can provide a large amount of information pertaining to service fragments for a service guide on all turbo channels, such as an aggregated ESG. In addition, this channel can provide a service advertisement channel. The aggregated ESG channel provides location information for IP strings included in other turbo channels, thereby allowing access to the other turbo channels to obtain a specific IP sequence.

Petition 870190118091, of 11/14/2019, p. 119/167

116/160

[000684] FIG. 65 illustrates a process and provision of an OMA BCAST service by an MCAST transmission system according to a configuration of the present invention.

[000685] Referring to FIG. 65, an SIC includes an i-IMT containing a list of all service entry points. Service entry points describe a specific service guide or aggregate service guide channel. I-IMT contains location information for IP strings on turbo channels.

[000686] A diffusion receiving device obtains the i-IMT from the SCI. I-IMT includes location information for a channel including the specific service guide or aggregate service guide channel. The broadcast reception apparatus accesses a turbo channel containing a desired service from among the turbo channels, based on the location information included in i-IMT.

[000687] In each of the turbo channels there is a signal data subchannel transmitting signaling data, and an IMT can be present in the signaling data subchannel. The IMT may have location information for at least one of a service guide ad channel included in a corresponding broadcast channel, a service guide delivery channel, and IP data strings. The broadcast receiver receives a service guide based on the location information included in the IMT. The broadcast receiver can access a specific service based on the information contained in the service guide. A method for allowing a user to receive a service will be described in more detail below with reference to FIG. 66.

Petition 870190118091, of 11/14/2019, p. 120/167

117/160

[000688] FIG. 66 illustrates a method of providing a service using MCAST with OMA-BCAST support according to a configuration of the present invention.

[000689] First, to support OMA BCAST, it is necessary that a service guide announcement channel ("Service Guide" SG) and a SG supply channel are provided through more than one channel. The broadcast receiving apparatus must subsequently access the SG announcement channel and the SG delivery channel. The SG supply channel transmits fragments of a service guide, and the service guide provides metadata relating to broadcast services, for example, configuration of broadcast services. The SG ad channel provides information for processing the SG delivery channel.

[000690] The broadcast receiving device first accesses a SIC to check a turbo channel through which the SG announcement channel is provided. An i-IMT contains the IP address of the SG ad channel, or location information of the SG ad channel, or a channel including IP data strings. For example, i-IMT may contain mapping information between the IP address of the SG ad channel and the number of a turbo channel.

[000691] The broadcast receiving device can receive information regarding the channel included in i-IMT so that a user can select a specific channel or so that an ad channel can be randomly selected as a standard without user intervention. If the user selects the specific channel, the selected channel is accessed using the IP address of the selected channel and the information included in i-IMT. In this way, it is possible to provide

Petition 870190118091, of 11/14/2019, p. 121/167

118/160 in addition to the user a service guide or a service. [000692] In a turbo channel, a signal data sub-channel transmitting signal data is present. in a signaling data subchannel, an IMT is present containing location information of strings provided through a current turbo channel. For example, mapping information can be included between the IP addresses of IP data strings provided through a current turbo channel and a data subchannel.

[000693] The broadcast receiver may obtain the location information of the SG announcement channel from the IMT. A data subchannel including the SG ad channel is accessed using the IP address of the SG ad channel obtained from i-IMT and IMT. The broadcast receiving apparatus obtains the location information of the SG supply channel by processing the SG advertisement channel. For example, the IP address of the SG delivery channel can be obtained by processing the SG advertising channel. Insofar as mapping information between IP addresses and data subchannels are present in the IMT previously obtained, the broadcast receiving device accesses the SG supply channel using the IP address of the supply channel SG and IMT, and obtain a service guide for the SG supply channel.

[000694] The service guide consists of metadata relating to a broadcast service intended to be provided, such as an ESG and an EPG, as described above. The broadcast receiver may provide the service guide to a user so that the user can select a desired broadcast service, or

Petition 870190118091, of 11/14/2019, p. 122/167

119/160 can provide a broadcast service designated as standard. If the user selects a desired broadcast service, the selected broadcast service is provided using the service guide. For example, the service guide may include the IP addresses of IP strings that provide services. As the previously obtained IMT includes the mapping information between IP addresses and data subchannels, a sequence of IP data is obtained using the IP addresses of the IP strings that provide broadcast services, that are obtained from the service guide, and from IMT. The broadcast reception device provides the selected broadcast service using the obtained IP string.

[000695] A layer of OMA BCAST services will now be briefly described.

[000696] A service guide allows services and content to be described, which are created by service / content providers either through a broadcast channel or through an interactive channel or which are provided by subscription or purchase. In addition, the service guide describes a method of accessing services. in terms of a user terminal, the service guide is an access point for discovering services or content that can currently be used or are intended to be used. In addition, the service guide provides a data entry point for a random directional service.

The service guide has the following functions.

[000697] First, the service guide data model creates a service, a schedule, a content, provision of data related to acquisition, access, and interactive data

Petition 870190118091, of 11/14/2019, p. 123/167

120/160 in a service guide fragment form.

[000698] Second, the discovery of the service guide allows to discover an entry point of an initial link and the service guide.

[000699] Third, the provision of the service guide is carried out not only through an optional interactive channel but also through a broadcast channel.

[000700] Finally, the update, management, and completeness of the service guide ensure that the service guide is up to date and sufficiently complete to be provided for viewing by a user.

[000701] An ATSC-M / H Terminal must support the mandatory parts of an OMA BCAST Service Guide for Service Guide functionality. In addition, the parties associated with interactive methods, supply and use of the Service Guide must be interpreted as optional in this specification, even when specified as mandatory. A transmission path and a transmission according to data format will be described below.

[000702] First, an A / V sequence transmission in real time through diffusion will be described.

[000703] For real-time provision of audio-visual broadcasting services to ATSC-M / H, RTP / UDP should be used as the transport protocol. The different audio and video formats are encapsulated for RTP using specific RTP payload formats, each of which is defined for a specific codec. Sequence delivery aspects are enhanced with the optional use of receipt reports.

Petition 870190118091, of 11/14/2019, p. 124/167

121/160

[000704] The ATSC-M / H Terminal shall support the mandatory parts of OMA BCAST File Distribution and Data Sequences for the provision of audio-visual sequences in real time. In addition, the terminal may support the associated delivery procedures for OMA BCAST File Distribution and Data Strings.

[000705] The transmission of a requested A / V sequence through a bidirectional channel will be described below.

[000706] The RTP / UTP transport protocol is also used to provide audio-visual sequences through the interactive channel for on-demand services. As interactive mode is optional, the ATSC-M / H Terminal can support the OMA BCAST String Distribution interactive parts as specified in the specification.

[000707] Next, a non-real time transmission of content through a broadcast channel will be described.

[000708] For this purpose, to perform the provision of content in non-real time through a broadcast channel, FLUTE / UDP is used as the transport protocol. The robustness of file delivery can be increased in two ways - by applying application layer FEC or by applying post-delivery procedures (error correction) that operate through an optional return channel.

[000709] The ATSC-M / H Terminal shall support the mandatory parts of OMA BCAST Files and Data Sequences Distribution, specification for providing non-real time content. In addition, the terminal may support the associated delivery procedures for OMA BCAST File Distribution and Data Strings.

[000710] A transmission of content will be described below

Petition 870190118091, of 11/14/2019, p. 125/167

122/160 in non-real time through an interactive channel.

[000711] Insofar as the interactive mode is optional, the ATSC-M / H Terminal can support the interactive parts of OMA BCAST File Distribution as specified in the specification. It should be noted that in this case only the mandatory parts of the specification will be supported.

[000712] Finally, the ATSC-M / H terminal supports auxiliary data, advertising, and notifications as defined in the specifications.

[000713] Protection of a content service through OMA BCAST will now be described.

[000714] FIG. 67 schematically illustrates the four-layer structure for protecting a service and content according to a configuration of the present invention.

[000715] For service protection, two key management systems (Key Management Systems ”KMS's) are supported.

[000716] One of the two KMS's is a terminal-based KMS (DRM profile) that consists of key management performed by a terminal. The other KMS is a KMS based on a smart card (smartcard profile ”) performed by (U) SIM or (R) UIM / CSIM.

[000717] An ATSC-M / H terminal can support both KMS's together but cannot support only one of them.

[000718] If the ATSC-M / H terminal supports terminal-based KMS, the terminal will support the mandatory parts of the DRM profile defined in the specifications.

[000719] If the ATSC-M / H terminal supports smart card-based KMS, the terminal will support the mandatory parts of the smart card profile defined in

Petition 870190118091, of 11/14/2019, p. 126/167

123/160 specifications.

[000720] Both of the two KMS's mentioned above provide a high level of security for protecting services on mobile devices, and can be applied simultaneously.

[000721] The four layers will now be described with reference to FIG. 59.

[000722] A traffic layer uses IPsec, SRTP or ISMACryp as a traffic cryptogram.

[000723] IPsec is an encapsulating security payload (ESP) and uses AES-128-cbc with explicit IV as an encryption algorithm in each IP packet. Authentication is optional and uses HMAC-SHA-196.

[000724] SRTP uses AES-128-CTR as an encryption algorithm. Authentication is optional and uses HMAN-SHA-180.

[000725] ISMACryp 1.1 with OMA BCAST specifies extensions for codec agnosticism.

[000726] AES-BYTE-CTR is used as an encryption algorithm. Authentication is optional and uses HMAC-SHA1.

[000727] A key management layer, a rights management layer and a record layer for DRM profile using Microsoft PlayReady are specified in the specifications.

[000728] A key management layer, a rights management layer and a registration layer for DRM profile using OMA DRM 2.0 are specified in the specifications.

[000729] A key management layer, a rights management layer and a profile registration layer

Petition 870190118091, of 11/14/2019, p. 127/167

124/160 smart card are specified in the specifications.

[000730] A terminal that supports interactivity can support any or both of the DRM and smart card profiles. For the DRM profile, provision of long-term key messages (“LTKM's”) will be supported through an interactive channel and provision of LTKM through a broadcast channel may be supported.

[000731] A terminal that does not support interactivity can support the DRM profile. The provision of LTKM through a broadcast channel will be supported.

[000732] An ATSC-M / H Terminal can support content protection. If the ATSC-M / H terminal supports content protection, it must support either or both, Microsoft PlayReady and OMA DRM v2.0.

[000733] ​​An MCAST system according to a configuration of the present invention allows an optional support for an interactive channel. Support for interactive features is optional for the ATSC-M / H Terminal. However, if the ATSC-M / H terminal supports interactive features, the terminal must support the OMA BCAST 1.0 specification for address interactivity. For these specifications, mandatory parts are supported.

[000734] Hereinafter, representation layer aspects of ATSC-M / H will be described in accordance with a configuration of the present invention.

[000735] Regarding the video codec, an ATSC-M / H Terminal must support the H.264 / AVC video codec. Additionally, the

ATSC-M / H terminal must support at least one of the following five capacities:

• decoding bit strings with

Petition 870190118091, of 11/14/2019, p. 128/167

125/160 compliance for H.264 / AVC Level 1b of the baseline profile with a 'constraint_label1_restrict' field with a value of '1';

• decoding of bit streams with H.264 / AVC Level 1.2 compliance from the baseline profile with a 'constraint_label1_restrict' field with a value of '1';

• decoding of bit streams with H.264 / AVC Level 2 compliance from the baseline profile with a field of 'marker_de_definir1_restrição' with a value equal to '1';

• decoding of sequences of bits with H.264 / AVC Level 3 compliance of the baseline profile with a field of 'marker_de_definir1_restrição' with a value equal to '1'; and • decoding of strings with H.264 / AVC Level 4 compliance from the baseline profile with a 'constraint_label1_restrict' field with a value of '1';

[000736] The ATSC-M / H Terminal can optionally support more than one of these capacities, and a capacity to support decoding of higher levels and profiles than those required by this capacity.

[000737] Regarding the frame rate, the ATSC-M / H terminal will decode each of the permissible frame rates according to the H.264 / AVC profile and level associated with the implemented capacity. Frame rates can include variable frame rates. Decoders will not be required to decode bit strings when the maximum distance between two images exceeds 0.7 seconds.

Petition 870190118091, of 11/14/2019, p. 129/167

126/160

[000738] Regarding the aspect ratio, the ATSC-M / H terminal will decode each of the allowable aspect ratios according to the H.264 / AVC profile and level associated with the implemented capacity.

[000739] Regarding the luminance resolution, the ATSC-M / H terminal will decode each of the permissible luminance resolutions according to the H.264 / AVC profile and level associated with the implemented capacity.

[000740] Regarding chromacity, the ATSC-M / H terminal will decode each permissible value of primary_color, transfer_characteristics, and matrix_coefficients.

[000741] Regarding the chrominance format, the ATSC-M / H terminal will decode each permissible value of field_of_type_of_type_of_location_of_city_of_family_of_family_of_of_family_of_family_of_family.

[000742] Regarding the audio codec, the ATSC-M / H Terminal must support any or both HE AAC v2 and AMR-WB + (Extended AMR-WB) codecs.

[000743] HH AAC v2 will be described first. The ATSC-M / H terminal must support mono / parametric coding or a 2-channel sterile function as defined in Profile Level 2 of HE AAC v2. ATSC-M / H can optionally support multi-channel audio decoding defined in Profile Level 4 of HE AAC v2.

[000744] Regarding profiles, the ATSC-M / H terminal must support the HE AAC v2 Profile. The ATSC-M / H terminal can optionally support decoding the HE AAC Profile.

[000745] Regarding the bit rate, the ATSC-M / H terminal should decode any bit rate allowed by the HE AAC Profile v2 and Level selected.

Petition 870190118091, of 11/14/2019, p. 130/167

127/160

[000746] Regarding the sampling frequency, the ATSC-M / H terminal must decode each audio sampling rate allowed by the HE AAC Profile v2 and Level selected.

[000747] With respect to dynamic range control, the terminal

ATSC-M / H shall support the AAC MPEG-4 dynamic range control tool.

[000748] With respect to downmixing, the ATSC-M / H terminal must support matrix downmixing as defined in MPEG-4.

The AMR-WB codec will now be described.

[000749] Regarding an audio mode, the ATSC-M / H terminal must perform decoding in mono and stereo with the functionality defined in AMR-WB +.

[000750] Regarding the sampling frequency, the ATSC-M / H terminal should be able to encode each of the audio sampling rates allowed by the AMR-WB + for mono and stereo.

[000751] With regard to subtitling, the ATSC-M / H system shall provide closed captions and text synchronized with images (using the 3GPP Timed Text format). The ATSC-M / H Terminal must support the 3GPP Timed Text format for subtitles and texts synchronized with images (closed captions).

[000752] FIG. 68 illustrates a power management mechanism according to a configuration of the present invention.

[000753] In general, the devices critical in terms of energy consumption are a display panel, such as a MCD, and a radio frequency (RF) module. In this section, an energy saving mechanism based on RF module control will be described.

Petition 870190118091, of 11/14/2019, p. 131/167

128/160

[000754] In a generic diffusion system, the RF module must be activated and must monitor all input frames to find a desired frame. In ATSC-MCAST, all turbo services are grouped and mapped to a set of sequence of frames and information related to frames, for example, positions and frame number, are provided through a SIC. Based on the information provided, a broadcast receiving apparatus can distinguish between an idle period and a work period.

[000755] FIG. 68 illustrates examples of MCAST frame slicing, and frame numbers that are used to identify a service. For example, if a user selects program # 1, the RF module can work to receive frames # 1 through # 4 from the groups of RF frames. That is, a transport layer instructs a physical layer to receive frames # 1 through # 4. The number of groups of RF frames and the duration of frame slicing may vary and information regarding a change in them is transmitted through the SIC.

[000756] A fixed number of MCAST packages are burst type units. The number of MCAST packets varies depending on the function of a turbo coding mode. MCAST packet numbers can be changed for each burst.

[000757] FIG. 69 is an illustrative graph of parameters related to MCAST frame slicing according to a configuration of the present invention.

[000758] A method of data transmission according to a burst transmission method will now be described.

[000759] FIG. 69 illustrates parameters used for time slicing. The definition of the parameters is

Petition 870190118091, of 11/14/2019, p. 132/167

129/160 follow:

[Table 19]

<td>Parameter</td><td>description</td>

<td>Bp</td><td>Gust Period (chart)</td>

<td>Bd</td><td>Gust Duration (chart)</td>

<td>Ot</td><td>Idle Time (frame)</td>

<td>Bs</td><td>Burst Size (Block)</td>

<td>Bb</td><td>Gust Bandwidth (Block / Frame)</td>

<td>Cb</td><td>Constant Bandwidth (Block / Frame)</td>

[000760] The relationship between parameters Bd, Bb, Bp and Cb is expressed as 'BdxBb = BpxCb'.

[000761] FIG. 70 is an illustrative graph of energy saving parameters according to a configuration of the present invention.

[000762] There are 3 stages required for assigning multiple burst services to a turbo channel. First, it is necessary to calculate a previously determined bandwidth for each of the services using Equation (3)

<td>Next. N</td><td>Equation (3),</td><td>'Tc'</td><td>indicates a rate</td><td>turbo</td>

<td>coding,</td><td>e.g. 1/2,</td><td> 1/3,</td><td>or 1/4.</td><td></td>

<td></td><td>Cbn = Rate</td><td>Dice</td><td>(kbit / s)</td><td></td>

<td></td><td>32 x 8 x</td><td>78x</td><td>188 x Tc</td><td></td>

<td></td><td>24.2 (ms)</td><td></td><td> 208 ...</td><td> (3)</td>

<td>[000763] In</td><td>second place,</td><td>each</td><td>one of the services is</td><td>assigned</td>

for the previously determined bandwidth.

[000764] FIG. 71 is an illustrative graph of a method for assigning each service to a previously determined bandwidth for burst mode transmission according to a configuration of the present invention.

Petition 870190118091, of 11/14/2019, p. 133/167

130/160

[000765] A total bandwidth is calculated by:

CbToT = Cbl + Cb2 + ..... + CbN. ... (4)

[000766] Thirdly, services # 1 to # 3 must be rotated 90 degrees clockwise or counterclockwise.

[000767] FIG. 72 is an illustrative graph of service rotation for burst mode transmission according to a configuration of the present invention.

[000768] AL-FEC will now be described according to a configuration of the present invention.

[000769] Regarding coding, the MCAST AL-FEC is a concatenated code of two linear block codes. Internal and external codes are defined as generating matrices or equivalent graphics. For example, an internal and external code has a message code (ui, u₂). Each of u₂ I₂represents a sequence of bits having an extension L that is greater than '1'. Similarly, the code word in the code is expressed as (v₂, v₂, v₂, v₄, v₂, v₂), and ví {1 = 1, ... 6} is a sequence of bits with an extension L.

[000770] If a matrix G illustrated in Equation (5) is given, the message word (u₂, u₂) is encoded in a code word (v₂, v₂, v₃, v₄, v₅, v₆) by v₂= Ui, v₂= u₂(+) u₂, v₄= u₂, v₅= ui, ev₆= u₂. The (+) operator above indicates an XOR-like bit string (exclusive-OR - exclusive-OR).

4 s ΰ

0 ] 01 “

II 0 l]₂ ¢5)

[000771] To the extent that the length of the code word is three times greater than the length of the message word, a

Petition 870190118091, of 11/14/2019, p. 134/167

131/160 code rate is 1/3. The generating matrix can be conventionally expressed by a graph.

[000772] FIG. 73 is an illustrative graph of a generator matrix according to a configuration of the present invention. The graph of FIG. 73 represents matrix G illustrated in Equation (5). The graph description is equivalent to that of the generating matrix. Each column in the graph corresponds to a codeword node (v_i, i = 1, ..., 6), while each line represents a message code (u₂, u₂). The value at x^The line and y^The column of matrix G means the line between u_x ev_y on the graph. The degree of a node (u or v) represents the number of lines connected to the node and is marked as a degree (u or v). For example, grade (u1) is 4 and grade (v₃) is 2. The generating matrix is ​​an important element that must be properly constructed.

[000773] The construction of a generating matrix will now be described.

[000774] It is assumed that the number of message nodes is k and the number of code nodes is n. A code fee is k / n. A message word is represented by (u1, u₂, ....., u_k) and a code word is represented by (v1, v₂, ....., v_n). First, a graph is constructed, and a generating matrix is ​​obtained by transforming a graph. A graph is obtained in two steps. The first step is to determine the degree of codeword nodes (grade (vi)). The second step is to connect message nodes and codeword nodes.

[000775] In detail, in the first step, k message nodes are given in ALC codeword nodes, and the degree of codeword nodes (grade (vi)) is determined as follows.

1. Determine d · - · of a construction parameter Δ.

Petition 870190118091, of 11/14/2019, p. 135/167

132/160

Δ is an integral value from 1 to 16. d_Max is specified by the value of the construction parameter Δ. For example, if Δ is '8', d_Max will be '61'.

[Table 20] .4 1 Z 3 4 5 6 7 8 9 10 11 1¾ ί; μ qg

U aiT ses “zãi ws 1 ir si 74 oi 52 44 ϊί ãõ 27 2ã m^-

2. Determine a set of integral values, {N [i] | i = 1,2,. . ., d_Max} this way:

- If an external code is assigned, N [1] = n and N [i] = 0 (í ^—2 , ....., dw_Thex)

- If an internal code is assigned,

2-Δ ^ -ΙΟΟ

Ml) = »&lt;U (100 + 2-á) _„ ^1W &amp; .. + 1 100 + 2 A

-1 í-ff-Dj '

ΛΙ2) = »- Λ · []] - £ λΈτ]

<td></td><td>in</td><td>that [x] indicates</td><td>the biggest</td><td>number</td><td>interpositive</td><td>what</td><td>is</td>

<td colspan="2">less than or</td><td>equal to x.</td><td></td><td></td><td></td><td></td><td></td>

<td></td><td> 3 .</td><td>Determine the</td><td>degrees</td><td>decade</td><td colspan="2">word knot</td><td>in</td>

<td>i code</td><td>) degree</td><td>2 (v₂,), degree (v₂)</td><td> , . . .,</td><td>degree (v_n) )</td><td>i agree</td><td>with</td><td>O</td>

<td>diagram</td><td>in</td><td>illustrated flow</td><td>in FIG.</td><td> 63 .</td><td></td><td></td><td></td>

<td> [000776]</td><td>THE</td><td colspan="2">FIG. 74 is a diagram</td><td>flow</td><td>illustrative</td><td>in</td><td>one</td>

<td>method</td><td>in</td><td>determination</td><td>degree</td><td>(vi) of</td><td colspan="3">according to a</td>

configuration of the present invention.

[000777] In operation 7410, integer variables (kl, k2.... Km) are initialized to '0', that is, kl = k2 = ... = km = 0, where m indicates a number greater integer such that N [m] is not zero. The other integer variable j is defined as '1'.

a = min min —2j_

[000778] In operation S7420, an index a, such as', is determined. When there is a plurality of minimum values,

Petition 870190118091, of 11/14/2019, p. 136/167

133/160 a set of indices {ab ..., c} is determined.

[000779] In operation S7430, the degree of Vj is a and j is increased by 1. In addition, the degree of Vj is bej is increased by 1. This procedure is repeated until all indexes are used.

[000780] In operation S7440, only variables (k_The, k_B, ..., k_ç) specified in the set of indexes {a, b, ..., c} are increased by 1.

[000781] In operation S7450, it is checked whether all degrees (degree (vj) j = 1, ..., n) have been determined. If they have not all been determined, the S7420 operation is repeated.

[000782] In the second step, k message nodes are given in codeword nodes, the degrees of codeword nodes are grade (vi), and the message nodes connected to a codeword node are checked in accordance with according to the flow diagram of FIG. 64.

[000783] FIG. 75 is a flow diagram illustrating a connection of message nodes to a code node according to a configuration of the present invention.

[000784] In operation S7510, an index variable j of a codeword node vj is initialized to be '1'.

[000785] In operation S7520, a set of message node indexes {a, b, ..., c} is obtained which should be associated with the

<td>knot</td><td colspan="2">word of</td><td>code</td><td>Vj.</td><td>O</td><td>number of</td><td colspan="2">elements</td>

<td>(| {a, b, ..</td><td>.,ç}</td><td colspan="2">|) in this set</td><td colspan="2">should</td><td>be equal to</td><td>degree of</td><td>Vj,</td>

<td>degree (Vj).</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> [000786]</td><td>At</td><td>operation</td><td>S7530,</td><td>are</td><td colspan="2">identified</td><td>the knots</td><td>in</td>

<td>message</td><td>what</td><td>should be</td><td>connected</td><td>to</td><td>at the</td><td colspan="2">code word</td><td>vj</td>

<td>with {u_The,</td><td>B, .</td><td>.., uc}.</td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> [000787]</td><td>At</td><td>operation</td><td>S7540,</td><td>the</td><td colspan="2">procedures</td><td>above</td><td>are</td>

<td>repeated</td><td colspan="2">for all</td><td>give us</td><td colspan="2">word</td><td>of code.</td><td></td><td></td>

Petition 870190118091, of 11/14/2019, p. 137/167

134/160

[000788] FIG. 76 is a flow diagram illustrating in detail the S7520 operation of FIG. 75 according to a configuration of the present invention.

[000789] In operation S7610, the message node index sets U and S are initialized to {1, ..., k} and {} respectively. The U and S sets are ordered sets and the order is defined as follows. Ox data^O aeoy element^O element b in the U or S set, if x &lt;y, then a &lt;b and vice versa. This initialization is performed only once before invoking this procedure.

[000790] In operation S7620, after obtaining a pseudo-random value x in {1, ..., | U |}, the message node index that must be returned is obtained by x^O element in set U where | U | means the number of all elements in set U. Subsequently, this element moves from set U to set S. In this way, all previously selected message node index values ​​are included in set S while the other values ​​do not. selected remain in the U set.

[000791] In operation S7630, it is determined whether set U is an empty set. If set U is an empty set, operation S7630 is performed to respectively initialize sets S and U to {1, ..., k} and {}.

[000792] In FIG. 76 an operation to obtain a message node index number x is specified in {0, ..., | U |}. This operation is performed using the Mersenne Twister (MT) algorithm, which is a pseudo-random number generation algorithm developed by Makoto Matsumoto and Takuji Nishimura in 1996/1997 and improved in 2002. The inventors' standard C code is freely available for

Petition 870190118091, of 11/14/2019, p. 138/167

135/160 any purpose, including for commercial use.

[000793] Prior to any procedure call, the Mersenne Twister (MT) algorithm is initialized by an unsigned 32-bit integer seed. To obtain a message node index number x at {0, ..., | U |], an unsigned 32-bit integer is then generated, a minimum integer, and in such a way that | U | &lt;= 2^and, the most significant bits are obtained, and the previous procedure is discarded and is repeated again if the number is

<td>bigger then</td><td>or equal to</td><td>| U |.</td><td>If</td><td>O</td><td>number</td><td>for</td><td>smaller</td><td>what</td><td>| m</td><td>, O</td>

<td>number x</td><td>index</td><td>at the</td><td>in</td><td colspan="2">message</td><td>it's the</td><td>number</td><td> + 1</td><td>what</td><td>if</td>

<td colspan="2">find at {0, ..., | d |}</td><td> .</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td> [000794]</td><td colspan="3">It will now be described</td><td>one</td><td>method</td><td>in</td><td colspan="2">construction</td><td>in</td><td>an</td>

generating matrix.

[000795] Each column corresponds to a codeword node (ν ±, i = 1, ..., n) in a graph where each line represents a message node (u_i, i = 1, ..., k). When U_x it's on av_y in the graph, the element at x^The line and on i^The column in the generating matrix will be '1'. If they are not connected, the element will be zero.

Pre-built AL-FEC codes will now be described.

[000796] To define an MCAST AL-FEC code, two matrices are defined. One is for the internal code and the other is for the external code. Given an MCAST AL-FEC code (n, k), the internal code will be a code (n, k + d_k) and the external code will be a code (k + d_k, k). k + ô_k is the number of code nodes converted to the external code and message nodes to the internal codes.

[000797] To define degree (vj) in the internal code, it is necessary to provide a construction parameter Δ.

Petition 870190118091, of 11/14/2019, p. 139/167

136/160

[000798] To define the connection between _ui and Vj in the internal and external codes, it is necessary to provide a random seed for the Mersenne Twister procedure. This seed will be used for both the internal code and the external code.

[000799] Thus, the three parameters ô_k, Δ and seed are sufficient to define an MCAST AL-FEC code. For 3 different MCAST AL-FEC codes (n, k), these parameters are listed as follows

[Table 21]

<td>(n, k)</td><td>(O_k, Δ, seed)</td>

<td> (2880,2304)</td><td> (10, 6, 14)</td>

<td> (1920, 1536)</td><td> (3,8,6)</td>

<td> (960,768)</td><td> (1,8,8)</td>

[000800] FIG. 77 is a block diagram of an MCAST broadcast receiver according to a configuration of the present invention.

[000801] Referring to FIG. 77, the broadcast receiving apparatus includes a signaling information extractor 7701, a data acquisition unit 7702, and a data processing unit 7703.

[000802] The signaling information extractor 7701 obtains signaling information necessary for processing a transport channel. Signaling information can be provided through a transport channel such as an SIC. Signaling information can include at least one of the configuration information for an ATSC M / H string, error correction information for the transport channel, transport channel configuration information that is required for processing

Petition 870190118091, of 11/14/2019, p. 140/167

137/160 of the transport channel.

[000803] Signaling information can be included continuously or discontinuously in the normal ATSC sequence and can then be transmitted. The signaling information is included in a predetermined location of a frame or location information of the signaling information is included in the previously determined location of the frame in such a way that the 7701 signaling information extractor can recognize the location of the signaling information. In addition, the location of the signaling information can be indicated by including a specific bit sequence inside or outside a channel that transmits the signaling information.

[000804] Signaling information is important information as it contains information necessary for processing other transport channels, and therefore may contain additional code for error correction. Signaling information can be transmitted in-band or out-of-band or can be transmitted via a specific location in a transport sequence.

[000805] The data acquisition unit 7702 obtains packets transmitted through the transport channel. The term 'transport channel' used in this specification has a broader definition than that used in a broadcast system in general. That is, the term 'transport channel' according to the present invention includes a sequence provided during inclusion in another transport sequence. For example, it is possible to transmit a normal ATSC sequence (MPEG-2 TS) by including an MPEG-2 TS sequence or another type of

Petition 870190118091, of 11/14/2019, p. 141/167

138/160 transport still through an additional indication in the normal ATSC sequence. In the current configuration, the broadcast receiver receives data by processing a transport sequence included in a normal sequence. The data can be obtained according to a previously determined method or by using the signaling information referred to above transmitted through a specific channel such as a SIC. A transport sequence according to the present invention, which is intended to be received by a mobile terminal, is inserted into another transport sequence, or information indicating this insertion is transmitted via a SIC. For example, a transport string is included in an MPEG-2 TS null packet region or in an MPEG-2 TS private data field.

[000806] If a transport string according to the present invention, which is intended to be received by a mobile terminal, is inserted into (or added to) another transport string, it will also be necessary to include display information or a header for processing the inserted or added string. For example, a combination of information regarding the start and end positions of the added string, information regarding the length of the added string, information indicating whether the added string exists, and other information necessary for processing the added string can be entered.

[000807] Although this is not illustrated in the drawings, the data acquisition unit 7702 can include a metadata output unit and a transport channel access unit.

Petition 870190118091, of 11/14/2019, p. 142/167

139/160

[000808] The metadata output unit produces as output metadata referring to a provided broadcast service. Meta-data provides information regarding the broadcast service provided, such as an ESG, EPG, or OMA BCAST service guide. Metadata can include information necessary for processing a transport package. For example, SDP data for processing IP strings can also be included in the metadata. That is, several information related to the service can be considered as constituting metadata. From this point on, the present invention will be described with reference to an OMA BCAST service guide as an example of metadata. A service guide must be obtained through sequential access to a service guide ad channel and a service guide supply channel for the provision of a service under OMA BCAST. A transport channel that broadcasts a service guide ad channel can be specified on an i-IMT or SIC as described above. In this way, the metadata output unit obtains metadata for a service, which is provided through the transport channel, from i-IMT and then outputs the data.

[000809] If the MCAST transmission system supports high-speed access such as the primary service mentioned above, it will be possible to provide a primary service simultaneously with obtaining metadata.

[000810] The transport channel access unit accesses a transport channel that provides a broadcast service selected by a user. Alternatively, a transport channel can be automatically selected by the broadcast receiving device or by a service provider.

Petition 870190118091, of 11/14/2019, p. 143/167

140/160 diffusion.

[000811] If the transport channel is selected, the data transmitted through the transport channel will be obtained. The data transmitted through the transport channel can be constructed in units of packets, units of strings of bytes, or units of strings of bits. An error protection code can be added to the data to correct any errors in them. In this case, the error is corrected using the error protection code. As described above, data transmitted through the transport channel can be presented at a specific location or a location known to a SIC, and the transport channel access unit can process all of this information. However, according to another configuration of the present invention, the processing of this information can be performed by the data collection unit 7703.

[000812] The data processing unit 7703 processes data obtained. Data can be processed in units of packets, units of strings of bytes, or units of strings of bits. Each header contains the configuration information for a package, and the original data is restored based on the configuration information.

[000813] In particular, the MCAST transmission system according to the current configuration fragments application data for encapsulation packages and segments encapsulation packages into transport packages. In this case, the data processing unit 7703 restores the encapsulation packets using the transport packet header information and restores the application data

Petition 870190118091, of 11/14/2019, p. 144/167

141/160 originals using the header information of the encapsulation packages.

[000814] According to another configuration of the present invention, data can be processed in sequences of packets. In this case, the configuration information regarding the package strings, for example, the LMT above, is obtained, and then the data is obtained by processing the packages included in the package sequences.

[000815] The obtained data are produced as output through an output device (not shown) after being decoded or without having been decoded. The output device processes and outputs data in Access Units (AU's) to provide a broadcast service to a user. The AU indicates a minimum unit that can be divided and processed by an output device or a decoding device. For example, in the case of video, I, P, and B frame packages may consist of AU units, in the case of an MPEG-2 transport package, a PES or section data may consist of AU units.

[000816] Although this is not illustrated in the drawings, the broadcast receiving apparatus may additionally include a channel setting module, an RF receiver, a baseband processor, and a built-in sequence information receiver. The channel setting mode establishes a frequency for a channel and the RF receiving device receives a signal corresponding to the established frequency. The baseband processor processes the received signal, and transforms it into a sequence of bits in order to process the signal at a later stage. The built-in sequence information receiver receives

Petition 870190118091, of 11/14/2019, p. 145/167

142/160 information regarding an embedded string. The information regarding an embedded string can consist of any information necessary for processing the embedded string, including information that specifies whether an embedded string is present or not, the type of the embedded string, or a method of processing the embedded string, for example. example, outer interleaving, RS parity information, time interleaving.

[000817] If a first transport sequence includes a second transport sequence in the same format or in a different format, the embedded sequence described with reference to FIG. 77 is used to indicate the inclusion of the second transport sequence. In this way, the information for processing the embedded sequence is transmitted in bandwidth or out-of-band, or a previously determined value or condition is used, so that the broadcast receiving device can recognize them.

[000818] FIG. 78 is a flow diagram illustrating a method of receiving a broadcast according to a configuration of the present invention.

[000819] In operation S7810, a frequency of one channel is established.

[000820] In operation S7820, a signal corresponding to the established frequency is received.

[000821] In operation S7830, information regarding an embedded sequence is received.

[000822] In operation S7840, signaling information containing information for processing one or more transport channels is obtained. In this specification,

Petition 870190118091, of 11/14/2019, p. 146/167

143/160 signaling information can be transmitted via an SIC.

[000823] In operation S7850, the information of a transport channel is provided to a user to obtain the user's selection.

[000824] In operation S7860, a transport channel providing a service is selected, based on user intervention. Alternatively, a previously determined transport channel can be selected as the default.

[000825] In operation S7870, data is received through one or more transport channels.

<td>[000826] On</td><td>operation</td><td>S7880, the</td><td>Dice</td><td>received</td><td>are</td>

<td>processed.</td><td></td><td></td><td></td><td></td><td></td>

<td>[000827] On</td><td>operation</td><td>S7890, the</td><td>Dice</td><td>processed</td><td>are</td>

<td colspan="2">produced as output.</td><td></td><td></td><td></td><td></td>

<td>[000828] One</td><td>frame</td><td>carriage</td><td>in</td><td>a deal with</td><td>an</td>

configuration of the present invention can be transmitted through a transport frame used in an ATSC transport system or separately. If a transport frame containing a transport sequence used in another transport system is transmitted, some of the operations illustrated in FIG. 78 may be omitted according to another embodiment of the present invention.

[000829] FIG. 79 schematically illustrates an A-VSB MCAST receiving system according to a configuration of the present invention.

[000830] A broadcast signal received through a tuner is provided to a user through a physical layer, a data interconnection layer, a transport layer and an application layer. Tier operations

Petition 870190118091, of 11/14/2019, p. 147/167

144/160 illustrated in FIG. 79 are opposite to those of the layers in an MCAST transmission system.

[000831] The physical layer obtains an MCAST transport frame from the received broadcast signal. The MCAST transport frame can be inserted into a transport frame in another transport system and be subsequently transmitted. In this way, the physical layer must obtain an MCAST transport frame. If the MCAST transport sequence is inserted into an ATSC transport frame and is subsequently transmitted, the MCAST transport sequence is obtained by detecting a 'Deterministic Frame Sync' field (DFS), where the MCAST transport sequence is divided into N packets. The MCAST transport frame has a deterministic structure, and therefore, the N packets can be included in the MCAST transport frame regardless of the presence of an error.

[000832] The data interconnection layer corrects errors in

<td>Dice</td><td colspan="2">transmitted through</td><td>in</td><td>a turbo</td><td colspan="2">channel and in a</td>

<td colspan="2">plurality</td><td>of parcels</td><td>in</td><td>information</td><td>in</td><td>signaling</td>

<td colspan="3">transmitted through a</td><td>SIC.</td><td colspan="3">A transmission side can</td>

<td>to apply</td><td>FEC</td><td>specific (one</td><td>rate</td><td>of code,</td><td>etc.)</td><td>every turbo</td>

<td>channel.</td><td>In</td><td>particular, can</td><td>to be</td><td>applied</td><td>an</td><td>FEC correction</td>

<td>robust</td><td>at</td><td>information</td><td colspan="2">signage on</td><td>SIC.</td><td>The layer of</td>

data interconnection in the broadcast receiving apparatus can perform error correction using additional code such as an FEC.

[000833] The transport layer in the broadcast receiving apparatus includes a packetization layer and an encapsulation layer. The layer of

Petition 870190118091, of 11/14/2019, p. 148/167

145/160 package forming creates an encapsulation package by processing a multiplexed transport package, and the encapsulation layer restores the original application data and application-specific information by processing the encapsulation package. Application data can include real-time media data, IP data, object data and signaling data.

[000834] A transport frame used in the MCAST transmission system has a deterministic structure. That is, integral packages are present in a shipping box. When a transport frame has a deterministic structure, it is effective because it is possible to remove a 'sync' field or a 'CC' field from the packages. However, in a system that multiplexes and transmits data in installment units in accordance with the present invention, multiplexing using a parcel requires that all packages that make up the parcel be received. If an error occurs in any of the packages, the error packages must also be received in order for the parcel to be constituted. Otherwise, an end lag value of a data subchannel and the location of the data in the parcel itself are changed, thereby preventing all packets from being fully received. For example, information such as an LMT, which indicates the location of a transport channel, indicates the location of the data using a lag value in a frame, and thus, the physical layer must transmit even an error packet. to a higher layer.

[000835] Thus, when an error occurs in a specific package, it is necessary to indicate that the error occurred

Petition 870190118091, of 11/14/2019, p. 149/167

146/160 is indicated on this package or that a device for demultiplexing packages is informed of this fact. The occurrence of an error can be reported as follows: [000836] First, the occurrence of an error is indicated by an 'error_indicator' field in the header of a package.

This method is used in the case of an MPEG-2 TS sequence. However, the package efficiency is degraded due to the fact that it is necessary to add a new field to the header of a package.

[000837] Second, a hardware signal marker is used to indicate that an error occurs in a current package. When an 'error_indicator' field is not used, the occurrence of an error is indicated by additional signaling. However, there is a drop in performance (overhead) as it is necessary to synchronize the signaling information with the package.

[000838] Third, an additional field that is not specified in the standards is generated for each package, and the 'error_indicator' field is included in the additional field.

However, this is a nuisance as it is necessary for a terminal to individually enter information representative of the occurrence of an error.

[000839] To solve these problems, the occurrence of an error is implicitly indicated using a combination of fields illustrating a discrepancy according to the structure of the package header. The occurrence of an error can be indicated by building the header of an error packet so that it does not exist in a packet itself. That is, the header of the error packet is constructed using a combination of fields that cannot exist

Petition 870190118091, of 11/14/2019, p. 150/167

147/160 actually in the packet header. Because such a header structure cannot exist, a packet demultiplexing unit determines that a packet with such a header structure will be an error packet.

[000840] The following is a configuration of the header of an error packet according to the definition in MCAST.

First_last 0x00 DC marker 0x01

[000841] These fields mean that an encapsulation packet is not a first packet and includes decoder configuration information.

[000842] Decoder configuration information is always included in a location where a first package from an encapsulation package is present, and therefore cannot exist in an MCAST package. In this way, a terminal determines that a packet that has this header structure is a packet with an error.

[000843] FIG. 80 is a block diagram of a diffusion receiving apparatus capable of indicating an error packet according to a configuration of the present invention. Referring to FIG. 80, the diffusion receiving apparatus includes an RF module 8001, a baseband processing unit 8002, a DFS detection unit 8003, a pre-header insertion unit 8004, a demultiplexing unit 8005, and an 8006 renderer.

[000844] The RF module 8001 receives an analog broadcast signal, and the baseband processing unit 8002 generates a bit sequence according to the ATSC and AVSB standards. The DFS 8003 detection unit divides the bit sequence into N packets by means of DFS detection.

Petition 870190118091, of 11/14/2019, p. 151/167

148/160

[000845] The pre-header insertion unit 8004 inserts a pre-header in each of the packages. The pre-header can include an identifier representing the type of the package, error information indicating whether or not there is an error present in the package, and a 'CC' field to check whether there is continuity according to the type of package. Using the 'CC' field, it will be possible to determine where a lost packet is.

[000846] The structure of the pre-header according to a configuration of the present invention will be described below with reference to FIG. 82.

[000847] The demultiplexing unit 8005 demultiplexes a transport package. In this case, the identifier representing the type of the package, which is included in the pre-header, can be used.

[000848] Renderer 8006 processes data and outputs the processing result.

[000849] FIG. 81 is a flow diagram illustrating a method of receiving a broadcast indicating an error packet according to a configuration of the present invention.

[000850] In operation S8110, a sequence of bits is received from a baseband processor.

[000851] In operation S8120, the sequence of bits is divided into N packets using DFS. The value of N can vary according to a transmission mode.

[000852] In the S8130 operation, error correction is performed. An error correction method corresponds to an error protection method, which was used on one transmission side. For example, RS decoding or external decoding can be performed.

Petition 870190118091, of 11/14/2019, p. 152/167

149/160

[000853] In operation S8140, the types of packages are identified. For example, it is determined whether a transport packet is alternatively a signal packet containing signaling data or a data packet in general.

[000854] In operation S8150 an identifier is added to each of the packages according to the type of the package. For example, '0x30' is added as an identifier to the signaling package containing signaling information, and '0x47' is added as an identifier to an MCAST transport package in general.

[000855] In operation S8160 it is determined if there is an error present in each of the packages, and when an error is present, information indicating this fact is added to the package containing the error.

[000856] In operation S8170 it is determined whether all of the above operations were performed for all packages. If not, the above operations are repeated.

[000857] In operation S8180, packets are processed by a demultiplexer in a transport layer.

[000858] The operations S8110 to S8170 above are performed by the baseband processor or below the transport layer.

[000859] FIGS. 82A and 82B illustrate the structure of a pre-header according to configurations of the present invention.

[000860] The pre-header can include a synchronization byte and a CC verification field.

[000861] The synchronization byte is a byte that contains identifying information that identifies the type of packet. For example, '0x38' can indicate a signal packet and '0x47' can indicate a data packet in general.

Petition 870190118091, of 11/14/2019, p. 153/167

150/160

[0008 62] The CC field is a 1-byte field and may contain an error marker indicating whether an error is present in a packet. When an error is present, a bit from the DC field can be used to indicate the error.

[000863] For example, '0,1,2,3,4, ...., 254,255,0,1,2,3, ..

indicates that no error is present and '0,1,2,3,4, ...., 126,127,0,1,2,3, ...' indicates that an error is present.

[000864] FIG. 83 is a flow diagram illustrating a method of processing DCI by a diffusion receiving apparatus according to a configuration of the present invention.

[000865] In operation S8310, an MCAST transport package is received.

[000866] In operation S8320, a RAP marker is received.

[000867] If the RAP marker is activated, an encapsulation package is built in operation S8330.

[000868] In operation S8340, the DCI marker is checked.

[000869] In operation S8350, parsing of a DCI field is performed.

[000870] In operation S8360, a decoder is established in order to correspond to the DCI field.

[000871] FIG. 84A illustrates a method of updating CBT in adaptive time slicing according to a configuration of the present invention.

[000872] Referring to FIG. 84A, a group of GOF frames consists of five frames, and numbers 0 through 5 are assigned respectively to frames belonging to each of the GOF's.

[000873] A 'next_development_detail_detail_delay' field can be

Petition 870190118091, of 11/14/2019, p. 154/167

151/160

<td>transmitted</td><td>Through a</td><td>field</td><td>in</td><td colspan="3">'information</td><td>in</td>

<td>configuration</td><td>of service 'in one</td><td>SIC,</td><td colspan="2">and indicates</td><td>one</td><td>frame</td><td>whose</td>

<td>CBT should</td><td>be updated.</td><td>This</td><td>is,</td><td>if</td><td>O</td><td>field</td><td>in</td>

<td>'lag_</td><td colspan="2">_de_próxima_atualização_de_</td><td>CBT '</td><td colspan="2">have</td><td colspan="2">a value of</td>

4, this means that the TCC is updated after four frames. [000874] A 'next_update_delivery_deviation' field varies according to the type of channel, and a point in time when the TCC is updated in each of the channels can be calculated using the 'next_devent_development_of_development_of_TCC' field and the ' next_date_delivery '. In the current configuration, a point in time when the TCC is updated in a turbo channel is calculated so as to be

[000875] First, a point in time will be described when the TCC is updated on an A channel.

[000876] When a frame having a value of 1 and belonging to a first GOF is received, the diffusion receiving apparatus obtains the values ​​of the 'delay_of_proxy_update_of_the_update' field. In the current configuration, the value of the 'next_development_details_deviation' field is '4' and the value of the 'next_devent_development_deviation' field is '0'. In this way, the “Turbo Channel Configuration” information (TCC) information is updated at a point in time indicated by the sum of the values ​​of the 'defaults_of_update_of_update_of_the_updates' field, that is, after four

Petition 870190118091, of 11/14/2019, p. 155/167

152/160 frames. In this way, the modified TCC is applied from a table having a value of 5 and belonging to the first GOF.

[000877] Similarly, in a channel B, the altered TCC is applied from a frame having a value of 2 and belonging to a second GOF, and in a channel C, the altered TCC is applied from a frame having a value of 5 and belonging to the second GOF.

[000878] FIG. 84B illustrates an update method using DB in adaptive time slicing according to a configuration of the present invention. In detail, FIG. 84B illustrates a method of updating an IMT and channel information using information contained in a BD broadcast descriptor. Similar to FIG. 84A, a GOF consists of five frames and numbers 0 through 5 are respectively assigned to frames belonging to each frame.

[000879] If it is assumed that a frame has a value of 1 and belongs to a first GOF, a diffusion apparatus obtains the

<td>value</td><td>in</td><td>one</td><td>field</td><td>in</td>

<td>'lag_of_</td><td>_next_</td><td>_update_of_</td><td>BD '. At</td><td>current</td>

<td>configuration,</td><td>O</td><td>value</td><td>from Camp</td><td>in</td>

<td>'lag_of_</td><td>_next_</td><td>_update_of_</td><td>BD 'is' 4'.</td><td></td>

<td>[000880] In addition</td><td>of this,</td><td>the values</td><td>of a field</td><td>in</td>

'frame_update_count' (or 'channel_information_information') include in a 'channel_information_descriptor' field and an 'extended version' field included in the 'IMT' field. In the current configuration, the 'next_data_delivery_display_delay_data' field has a value of 4 and the 'extended version' field has a value of 0. Thus, the IMT

Petition 870190118091, of 11/14/2019, p. 156/167

153/160 is updated at a point in time indicated by the sum of the values ​​of the field 'outdated_pr0xima_atualizaQdo_de_de_de' and the field of 'extended version', that is, after four frames. In this way, the updated IMT is applied from a table having a value of 5 and belonging to the first GOF.

[000881] In addition, the turbo channel information is updated at a point in time indicated by the sum of the values ​​of the 'next_degree_delivery_delivery_delivery_device' field, that is, after seven frames. In this way, the updated channel information is applied from a frame with a value of 2 and belonging to a second GOF. The fact that the turbo channel information is updated refers not only to a case in which the turbo channel information is changed, but also to a case in which some turbo channels are added or canceled.

[000882] When the descriptor BD consists of a plurality of frames, the value of the 'table_ update_count' counter is greater than '0'.

[000883] FIG. 85 is a block diagram of an 8500 apparatus for transporting a broadcast service according to a configuration of the present invention.

[000884] Referring to FIG. 85, the 8500 apparatus includes an 8510 encapsulation packet generating unit, an

<td>unity</td><td>in</td><td>generation of packages</td><td>in</td><td>transport 8520, and</td><td>an</td>

<td>unity</td><td>in</td><td>information generation</td><td>in</td><td colspan="2">service configuration</td>

<td> 8530.</td><td></td><td></td><td></td><td></td><td></td>

<td> [000885]</td><td>THE</td><td>generation unit</td><td colspan="2">encapsulation packages</td><td> 8510</td>

receives application data, generates an encapsulation package that includes configuration information adaptive to the type of

Petition 870190118091, of 11/14/2019, p. 157/167

154/160 application data to be transported and application data, and outputs the encapsulation package for the transport package generation unit 8520.

[000886] In a configuration of the present invention, the application data is of a type between signaling data, real-time media data, IP data, and object data. Depending on the type of application data, information about the encapsulation package is established differently.

[000887] In particular, an encapsulation package including real-time media data according to a configuration of the present invention includes, in a header area, decoder configuration information (DCI) which determines the specifications of a target decoder.

[000888] The 8520 transport packet generating unit receives the encapsulation packet from the 8510 encapsulation packet generating unit, divides the encapsulation packet into at least one transport packet of predetermined size that includes data from the encapsulation packet and information about the transport package itself, and outputs the transport package to the 8530 service configuration information generation unit.

[000889] According to a configuration of the present invention, the transport package generation unit 8520 generates a transport package that includes a basic header area, a pointer area, a padding area, a map table area location (LMT), an association or interconnection information table area (LIT), and a payload area.

Petition 870190118091, of 11/14/2019, p. 158/167

155/160

[000890] The 8530 service configuration information generation unit receives the transport package from the 8520 transport package generation unit, generates service configuration information that includes information established about a channel including the transport package, and outputs service configuration information to a SIC (not shown) at a location previously determined from at least one transport channel in a transport sequence.

[000891] In accordance with a configuration of the present invention, the 8530 service configuration information generation unit includes a service configuration information determination unit for determining service configuration information that includes information about a turbo channel and information of group of frames.

[000892] FIG. 86 is a block diagram of an 8600 apparatus for receiving a broadcast service according to a configuration of the present invention. Referring to FIG. 86, apparatus 8600 includes a transport channel determination unit 8610, a transport pack extraction unit 8620, a transport pack information extraction unit 8630, an encapsulation pack combination unit 8640, and a 8650 application data combining unit.

[000893] Transport channel determination unit 8610 determines a previously determined transport channel using service configuration information extracted from a service information channel at a previously determined location in a received frame, and

Petition 870190118091, of 11/14/2019, p. 159/167

156/160 outputs information about the transport channel determined for the transport package extraction unit 8620.

[000894] According to a configuration of the present invention, information about a turbo channel and frame group information is extracted from the service configuration information.

[000895] The transport packet extraction unit 8620 extracts a transport packet from the transport channel determined by the transport channel determination unit 8610, and outputs the transport packet to the packet information extraction unit. transport 8630.

[000896] The transport package information extraction unit 8630 extracts transport package information from the transport package extracted by the transport package extraction unit 8620, and outputs transport package information to the combination unit as output encapsulation packets.

[000897] The encapsulation packet combining unit 8640 obtains a combination of encapsulation packets including at least one transport packet using the extracted transport packet information, and produces that combination as output to the data generation unit of application 290.

[000898] In a configuration of the present invention, basic configuration information, an LMT, an LIT, and a program clock reference ("Program Clock Reference" - PCR) are extracted from the transport package.

[000899] The 8650 application data combining unit

Petition 870190118091, of 11/14/2019, p. 160/167

157/160 receives the encapsulation packet combination from the 8640 encapsulation packet combining unit, extracts encapsulation packet information from the encapsulation packets, and generates application data including at least one encapsulation packet using the packet information. extracted encapsulation.

[000900] FIG. 87 is a flow diagram of a method of transporting a broadcast service according to a configuration of the present invention.

[000901] In operation 8710, an encapsulation package is generated including configuration information adaptive to the type of application data to be transported and the application data.

[000902] In operation 8720, transport packages are obtained including data related to the encapsulation package, by dividing the encapsulation package into packages of previously determined sizes. Transport packages include information about the structures of transport packages.

[000903] In operation 8730, service configuration information including information established on a channel including transport packages is generated and included in

<td>a SIC in</td><td>an</td><td colspan="3">location previously</td><td>determined</td><td colspan="2">from between</td>

<td>at least</td><td>one</td><td>channel</td><td>in</td><td>transport</td><td colspan="2">in a sequence</td><td>in</td>

<td>transport.</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000904] A</td><td>FIG</td><td>88 is</td><td>one</td><td>diagram of</td><td>flow one</td><td>method</td><td>in</td>

<td>reception of</td><td>one</td><td>service</td><td>in</td><td>diffusion to</td><td>communications</td><td>furniture</td><td>in</td>

according to a configuration of the present invention.

[000905] In operation 8810, a previously determined transport channel is determined using service configuration information extracted from a SIC.

Petition 870190118091, of 11/14/2019, p. 161/167

158/160

[000906] In operation 8820, a transport package is extracted from the determined transport channel.

[000907] In operation 8830, information about the transport package is extracted from the transport package.

[000908] In operation 8840, a combination of encapsulation packages having individually at least one transport package are generated using the information about the transport package.

[000909] In operation 8850, a combination of application data including at least one of the encapsulation packages

<td>are generated</td><td colspan="3">upon use</td><td colspan="2">of information</td><td>on</td><td>the</td>

<td>packages of</td><td>encapsulation</td><td colspan="2">that are</td><td>extracted</td><td>From</td><td>packages</td><td>in</td>

<td>encapsulation.</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>[000910] The</td><td>settings</td><td>above</td><td>gives</td><td colspan="3">present invention can</td><td>to be</td>

<td>configured</td><td>in the form</td><td>in</td><td colspan="2">programs of</td><td colspan="2">computer</td><td>and</td>

<td>implemented</td><td colspan="2">on computers</td><td colspan="2">digital from</td><td>use</td><td>general</td><td>what</td>

run programs using readable recording media on a computer. Examples of computer-readable recording media include magnetic storage media (for example, ROM, floppy disks, hard drives, etc.), optical recording media (for example, CDROM's, or DVD's), and storage media such as carrier waves (for example, transmissions through the

Internet).

[000911] The data fields, package structures, API's and each block of the flow diagram illustrations described to explain the above-mentioned configurations of the present invention, can be implemented by computer program instructions. These computer program instructions may be provided by a computer processor for use

Petition 870190118091, of 11/14/2019, p. 162/167

159/160 general, a specific-use computer, or other programmable data-processing device for producing a machine, such that instructions, which are executed through the computer's processor or other programmable data-processing device, create means for implementations of the functions specified in the flow diagram block or blocks. These computer program instructions can also be stored in a computer-readable or computer-readable memory that can instruct a computer or other programmable data processing device to function in a specific way, such that instructions stored in memory usable on a computer or readable by a computer produce a manufacturing article including instruction means that implement the functions specified in the flow diagram block or blocks. Computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operating steps to be performed on the computer or other programmable device to produce a computer-implemented process in such a way that the instructions that are executed on the computer or other programmable device provide steps for implementing the functions specified in the block or blocks in the diagram flow.

[000912] Each block of the flow diagram illustrations may represent a module, segment, or code portion, which includes one or more executable instructions for implementing the specified logic function (s). It should also be noted that in some alternative implementations, the functions marked in the blocks can occur

Petition 870190118091, of 11/14/2019, p. 163/167

160/160 out of order. For example, two blocks illustrated successively can actually be executed substantially concurrently or the blocks can sometimes be executed in reverse order, depending on the functionality involved.

[000913] In addition, the data and package fields illustrated in this specification can be replaced by other data and package fields that perform the same functions.