TECHNICAL FIELD
[0001] The present disclosure relates to a broadcast transmitting device, a broadcast receiving
device, a method for operating the broadcast transmitting device, and a method for
operating the broadcast receiving device.
BACKGROUND ART
[0002] As the Internet is widely used, media services for providing content using an Internet
Protocol as a main transmission network are actively provided. With this trend, MPEG-Dynamic
Adaptive Streaming over HTTP (DASH) that is a standard technology for adaptively transmitting
media content according to a network environment and MEPG Media Transport (MMT) that
is a transmission standard for efficiently transmitting media content via an IP network
have been developed.
[0003] However, most media content is still transmitted via typical digital broadcasting
networks based on satellites, cables, terrestrial networks, or the like. Therefore,
many users use satellite, cable or terrestrial broadcast receiving devices. Therefore,
it is necessary to develop a broadcast transmitting device, a broadcast receiving
device, a method for operating the broadcast transmitting device, and a method for
operating the broadcast receiving device for enabling such satellite, cable or terrestrial
broadcast receiving devices to access media content transmitted via an IP network.
[0004] In particular, a broadcast transmitting device, a broadcast receiving device, a method
for operating the broadcast transmitting device, and a method for operating the broadcast
receiving device which are compatible with technical standards such as MPEG-DASH and
MMT are required.
DISCLOSURE OF THE INVENTION TECHNICAL PROBLEM
[0005] Embodiments provide a broadcast transmitting device, a broadcast receiving device,
a method for operating the broadcast transmitting device, and a method for operating
the broadcast receiving device for receiving, via a broadcasting network other than
an IP network, media content presentation information including information on media
content transmitted via the IP network.
[0006] Embodiments also provide a broadcast transmitting device, a broadcast receiving device,
a method for operating the broadcast transmitting device, and a method for operating
the broadcast receiving device for synchronizing media content transmitted via an
IP network with media content transmitted via a broadcasting network other than the
IP network.
[0007] Embodiments also provide a broadcast transmitting device, a broadcast receiving device,
a method for operating the broadcast transmitting device, and a method for operating
the broadcast receiving device for providing information on media content transmitted
via a broadcasting network other than an IP network using media content presentation
information including information on media content transmitted via the IP network.
TECHNICAL SOLUTION
[0008] In one embodiment, a method for operating a broadcast receiving device includes:
receiving a first broadcast stream including broadcast content via a broadcasting
network other than an IP network; receiving media content presentation information
for media content transmitted via the IP network on the basis of the first broadcast
stream; receiving the media content; and presenting the media content on the basis
of the media content presentation information.
[0009] The first broadcast stream may include a broadcast information signaling table including
information on the broadcast content, wherein the broadcast information signaling
table may include a first element indicating a transmission method of the media content
presentation information and a second element indicating transmission information
corresponding to the transmission method, wherein the receiving the media content
presentation information may include receiving the media content presentation information
on the basis of the first element and the second element.
[0010] The broadcast information signaling table may be one of a program map table (PMT),
a service map table (SMT), and a terrestrial virtual channel table (TVCT).
[0011] The first element may indicate that the media content presentation information is
transmitted on a second broadcast stream different from the first broadcast stream,
wherein the second element may include an identifier of the second broadcast stream.
[0012] The first element may indicate that the media content presentation information is
transmitted by a session-based transport protocol, wherein the second element may
include an identifier of a session of the session-based transport protocol.
[0013] The first element may indicate that the media content presentation information is
added to an information table in the first broadcast stream so as to be transmitted,
wherein the second element may include an identifier of a packet including the information
table.
[0014] The first element may indicate that the media content presentation information is
added to an Internet protocol (IP) datagram in the first broadcast stream so as to
be transmitted, wherein the second element may include an identifier of a data transmission
channel of a physical layer for transmitting the IP datagram and a port number and
an IP address of the IP datagram.
[0015] The method may include extracting, from the broadcast stream, synchronization information
for synchronizing the broadcast content with the media content, wherein the presenting
the media content may include synchronizing the media content with the broadcast content
on the basis of the synchronization information.
[0016] The synchronization information may include a first element indicating an own presentation
time of the media content and a second element indicating an identifier of a presentation
interval of the media content.
[0017] The synchronization information may include a third element indicating a remaining
time from a broadcast stream reference time of the packet including the synchronization
information to a start time of the presentation interval of the media content to be
synchronized.
[0018] The synchronization information may include a fourth element indicating whether the
media content presentation information is required to be updated prior to synchronization,
wherein the synchronizing the media content with the broadcast content may include
updating the presentation information on the basis of a value of the fourth element.
[0019] The synchronization information may be added to a header of a packet including a
video or an audio included in the broadcast content.
[0020] In another embodiment, a broadcast receiving device includes: a broadcast receiving
unit configured to receive a first broadcast stream including broadcast content via
a broadcasting network other than an IP network; an IP transmitting/receiving unit
configured to receive media content transmitted via the IP network; and a control
unit configured to receive media content presentation information for the media content
on the basis of the first broadcast stream, and present the media content on the basis
of the media content presentation information.
[0021] In further another embodiment, a method for operating a broadcast transmitting device
includes: inserting broadcast content into a broadcast stream; inserting, into the
broadcast stream, media content presentation information for media content transmitted
via an IP network; and transmitting the broadcast stream via a broadcasting network
other than an Internet protocol (IP) network.
ADVANTAGEOUS EFFECTS
[0022] One embodiment provides a broadcast transmitting device, a broadcast receiving device,
a method for operating the broadcast transmitting device, and a method for operating
the broadcast receiving device for receiving media content presentation information
including information on media content transmitted via an IP network.
[0023] Another embodiment provides a broadcast transmitting device, a broadcast receiving
device, a method for operating the broadcast transmitting device, and a method for
operating the broadcast receiving device for synchronizing media content transmitted
via an IP network with media content transmitted via a broadcasting network other
than the IP network.
[0024] Another embodiment provides a broadcast transmitting device, a broadcast receiving
device, a method for operating the broadcast transmitting device, and a method for
operating the broadcast receiving device for providing information on media content
transmitted via a broadcasting network other than an IP network using media content
presentation information including information on media content transmitted via the
IP network.
BRIEF DESCRIPTION OF THE DRAWINGS
[0025]
Fig. 1 is a block diagram illustrating a media content transmitting/receiving system
according to an embodiment.
Fig. 2 is a diagram illustrating a system for transmitting/receiving media content
via an IP network according to an embodiment.
Fig. 3 illustrates a structure of a media presentation description (MPD) according
to an embodiment.
Fig. 4 illustrates an XML syntax of the MPD according to an embodiment.
Fig. 5 illustrates an XML syntax of a period element of the MPD according to an embodiment.
Fig. 6 is a flowchart illustrating an operation of receiving, by a broadcast receiving
device, media content via an IP network according to an embodiment.
Fig. 7 illustrates a bitstream syntax for the case where the MPD is transmitted in
a format of an MPD information table.
Fig. 8 is a flowchart illustrating an operation of extracting, by the broadcast receiving
device, the MPD on the basis of an information table including the MPD according to
an embodiment.
Fig. 9 illustrates an MPD link table including an MPD link according to an embodiment.
Fig. 10 is a flowchart illustrating an operation of receiving, by the broadcast receiving
device, the MPD on the basis of a media content presentation information table including
a media content presentation information link according to an embodiment.
Fig. 11 illustrates that the MPD or the MPD information table is added to an IP datagram
so as to be transmitted according to an embodiment.
Fig. 12 illustrates a syntax of the IP datagram for the case where the MPD or the
MPD information table is added to the IP datagram so as to be transmitted according
to an embodiment.
Fig. 13 illustrates a syntax of an MPD payload included in the IP datagram for the
case where the MPD or the MPD information table is added to the IP datagram so as
to be transmitted according to an embodiment.
Fig. 14 is a flowchart illustrating an operation of extracting, by the broadcast receiving
device, the media content presentation information or the media content presentation
information table on the basis of the IP datagram including the media content presentation
information or the media content presentation information table according to an embodiment.
Fig. 15 illustrates a syntax of an MPD descriptor for transmitting the MPD according
to an embodiment.
Fig. 16 illustrates a syntax of MPD bootstrap_data in the case where the MPD descriptor
directly includes the MPD.
Fig. 17 illustrates a syntax of MPD bootstrap_data in the case where the MPD descriptor
includes a link to the MPD.
Fig. 18 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes an identifier of a data packet including the MPD.
Fig. 19 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes an identifier of an additional broadcast stream including the
MPD.
Fig. 20 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes information on an IP datagram including the MPD.
Fig. 21 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes information on a session of a session-based transport protocol
for transmitting the MPD.
Fig. 22 is a flowchart illustrating an operation of receiving, by the broadcast receiving
device, the media content presentation information in the case where a method of transmitting
the media content presentation information is added to a broadcast information signaling
information table so as to be transmitted.
Fig. 23 is a flowchart illustrating an operation of presenting, by the broadcast receiving
device, media content on the basis of whether transmission of a broadcast stream is
stable in the case where broadcast content is transmitted via not only a broadcasting
network but also an IP network.
Fig. 24 illustrates a syntax of a broadcast stream packet including synchronization
information of media content transmitted via an IP network according to an MPEG-DASH
standard.
Fig. 25 illustrates a syntax of the synchronization information added to a header
of a packet including broadcast content such as a video or an audio according to an
embodiment.
Fig. 26 illustrates the syntax of the synchronization information added to the header
of a packet including broadcast content such as a video or an audio according to another
embodiment.
Fig. 27 is a flowchart illustrating an operation of synchronizing, by the broadcast
receiving device, broadcast content with media content according to an embodiment.
Fig. 28 illustrates a format of information for identifying broadcast content included
in the media content presentation information in the case where the broadcast content
is transmitted according to an ATSC standard.
Fig. 29 illustrates an example of the MPD of MPEG-DASH including information for identifying
broadcast content transmitted according to the ATSC standard.
Fig. 30 is a flowchart illustrating an operation of receiving, by the broadcast receiving
device, broadcast content on the basis of the media content presentation information.
Fig. 31 is a block diagram illustrating that the broadcast receiving device receives
the MPD of MPEG-DASH via a broadcasting network for transmitting a broadcast stream
according to an MPEG-2 TS standard.
Fig. 32 is a block diagram illustrating that the broadcast receiving device synchronizes
broadcast content of a broadcast stream transmitted according to the MPEG-2 TS standard
with media content transmitted via an IP network.
MODE FOR CARRYING OUT THE INVENTION
[0026] Embodiments of the present disclosure are described below in detail with reference
to the accompanying drawings so that the embodiments are easily carried out by those
skilled in the art. However, the embodiments of the present disclosure may be implemented
in various different forms and are not limited to the examples described herein. Some
parts of the embodiments, which are not related to the description, are not illustrated
in the drawings in order to clearly describe the embodiments of the present disclosure.
Like reference numerals refer to like elements throughout the description.
[0027] When it is mentioned that a certain part "includes" or "comprises" certain elements,
the part may further include other elements, unless otherwise specified.
[0028] Fig. 1 is a block diagram illustrating a media content transmitting/receiving system
according to an embodiment.
[0029] The media content transmitting/receiving system includes a broadcaster 10, a content
provider 30, a content server 50, and a broadcast receiving device 100.
[0030] The content provider 30 provides media content to the broadcaster and the content
server 50.
[0031] The broadcaster 10 transmits a broadcast stream including media content using at
least one of a satellite, terrestrial or cable broadcasting network.
[0032] The content server 50 transmits media content on the basis of a request of the broadcast
receiving device.
[0033] The broadcast receiving device 100 includes a control unit 110, an IP transmitting/receiving
unit 130, a broadcast receiving unit 150, and a decoder 170. The broadcast receiving
device 100 controls operation of the IP transmitting/receiving unit 130, the broadcast
receiving unit 150, and the decoder 170 via the control unit 110. The broadcast receiving
device 100 receives a broadcast stream including media content via the broadcast receiving
unit 150. Here, the broadcast stream may be transmitted using at least one of a satellite,
terrestrial or cable broadcasting network. Therefore, the broadcast receiving unit
150 may include at least one of a satellite tuner, a terrestrial tuner, or a cable
tuner to receive the broadcast stream. The broadcast receiving device 100 requests
media content from the content server 50 via the IP transmitting/receiving unit 130.
The broadcast receiving device 100 receives the media content from the content server
50 via the IP transmitting/receiving unit 130. The broadcast receiving device 100
decodes the media content via the decoder 170.
[0034] Media content transmission/reception via an IP network according to an embodiment
will be described with reference to Figs. 2 to 6.
[0035] Fig. 2 is a diagram illustrating a system for transmitting/receiving media content
via an IP network according to an embodiment.
[0036] The media content transmission/reception via an IP network according to an embodiment
is divided into transmission/reception of a transmission packet including actual media
content and transmission/reception of media content presentation information. The
broadcast receiving device 100 receives the media content presentation information,
and receives the transmission packet including media content. The media content presentation
information represents information required for presenting the media content. The
media content presentation information includes at least one of spatial information
or temporal information required for presenting the media content. The broadcast receiving
device 100 presents the media content on the basis of the media content presentation
information.
[0037] In a specific embodiment, media content may be transmitted/received via an IP network
according to an MPEG Media Transport (MMT) standard. The content server 50 transmits
a presentation information (PI) document including the media content presentation
information. Furthermore, the content server 50 transmits an MMT protocol (MMTP) packet
including media content on the basis of a request of the broadcast receiving device
100. The broadcast receiving device 100 receives the PI document. The broadcast receiving
device 100 receives a transmission packet including media content. The broadcast receiving
device 100 extracts the media content from the transmission packet including the media
content. The broadcast receiving device 100 presents the media content on the basis
of the PI document.
[0038] In another specific embodiment, as illustrated in Fig. 2, media content may be transmitted/received
via an IP network according to an MPEG-Dynamic Adaptive Streaming over HTTP (DASH)
standard. In Fig. 2, the content server 50 transmits a media presentation description
(MPD) including the media content presentation information. However, depending on
a specific embodiment, the MPD may be transmitted by another external server instead
of the content server 50. Furthermore, the content server 50 transmits a segment including
media content on the basis of a request of the broadcast receiving device 100. The
broadcast receiving device 100 receives the MPD. The broadcast receiving device 100
requests media content from the content server 50 on the basis of the MPD. The broadcast
receiving device 100 receives a transmission packet including media content on the
basis of a request. The broadcast receiving device 100 presents the media content
on the basis of the MPD. To this end, the broadcast receiving device 100 may include
a DASH client in the control unit 110. The DASH client may include an MPD parser for
parsing the MPD, a segment parser for parsing the segment, an HTTP client for transmitting
an HTTP request message and receiving an HTTP response message via the IP transmitting/receiving
unit 130, and a media engine for presenting media. The MPD will be described in detail
with reference to Figs. 3 to 5.
[0039] Fig. 3 illustrates a structure of the MPD according to an embodiment. Fig. 4 illustrates
a syntax of the MPD according to an embodiment. Fig. 5 illustrates an XML syntax of
a period element of the MPD according to an embodiment.
[0040] The MPD may include a period element, an adaptation set element, and a representation
element.
[0041] The period element includes information on a period. The MPD may include information
on a plurality of periods. The period represents a continuous time interval of media
content presentation.
[0042] The adaptation set element includes information on an adaptation set. The MPD may
include information on a plurality of adaptation sets. The adaptation set is a set
of media components including one or more interconvertible media content components.
The adaptation set may include one or more representations. The adaptation sets may
respectively include audios of different languages or subtitles of different languages.
[0043] The representation element includes information on a representation. The MPD may
include information on a plurality of representations. The representation is a structured
set of one or more media components. There may exist a plurality of representations
differently encoded for the same media content component. In the case where bitstream
switching is allowed, the broadcast receiving device 100 may switch a received representation
to another representation on the basis of information updated during presentation
of media content. In particular, the broadcast receiving device 100 may switch a received
representation to another representation according to conditions of a bandwidth. The
representation is divided into a plurality of segments.
[0044] The segment is a unit of media content data. The representation may be transmitted
as the segment or a part of the segment according to a request of the media content
receiver 30 using the HTTP GET or HTTP partial GET method defined in the HTTP 1.1
(RFC 2616) protocol.
[0045] Furthermore, the segment may include a plurality of sub-segments. The sub-segment
may represent a smallest unit able to be indexed at a segment level. The segment may
include an initialization segment, a media segment, an index segment, and a bitstream
switching segment.
[0046] Fig. 6 is a flowchart illustrating an operation of receiving, by a broadcast receiving
device, media content via an IP network according to an embodiment.
[0047] The broadcast receiving device 100 receives the media content presentation information
via the IP transmitting/receiving unit 130 (S101). In a specific embodiment, the media
content presentation information may be the MPD according to the MPEG-DASH standard.
Here, the broadcast receiving device 100 may receive the MPD via the IP transmitting/receiving
unit 130. In another specific embodiment, the media content presentation information
may be the PI document according to the MMT standard. Here, the broadcast receiving
device 100 may receive the PI document via the IP transmitting/receiving unit 130.
[0048] The broadcast receiving device 100 receives media content via the IP transmitting/receiving
unit 130 on the basis of the media content presentation information (S103).
[0049] The broadcast receiving device 100 presents the media content via the control unit
110 (S105). In detail, the broadcast receiving device 100 may present the media content
on the basis of the media content presentation information via the control unit 110.
[0050] As described above, the broadcast receiving device 100 that receives a broadcast
stream via a satellite, cable or terrestrial broadcasting network is required to receive
the media content presentation information in order to receive media content via an
IP network. In particular, the media content presentation information is required
to be transmitted or received via a broadcast stream in order to efficiently interwork
with content transmitted via a broadcasting network. This is because a content provider
or a broadcaster may integrally manage content information provided via a broadcasting
network and information on media content transmitted via an IP network in the case
where the media content presentation information is transmitted via a broadcast stream.
Furthermore, this is because the broadcast receiving device 100 may quickly determine
whether the media content presentation information is updated without an additional
information request message in the case where the media content presentation information
is transmitted via a broadcast stream since the broadcast receiving device 100 continually
receives a broadcast stream.
[0051] Described below with reference to Figs. 7 to 21 is a method of transmitting/receiving
the media content presentation information using a broadcast stream transmitted via
a broadcasting network instead of an IP network.
[0052] A content provider or a broadcaster may add the media content presentation information
to a media content presentation information table to transmit the media content presentation
information. This operation of adding the media content presentation information to
the media content presentation information table to transmit the media content presentation
information is described below with reference to Figs. 7 and 8.
[0053] In the case where the media content presentation information is added to the media
content presentation information table so as to be transmitted, the broadcast receiving
device 100 may receive the media content presentation information on the basis of
the media content presentation information table. In detail, the broadcast receiving
device 100 may extract the media content presentation information from the media content
presentation information table to receive the media content presentation information.
[0054] Here, the media content presentation information table may include an id element
for identifying the media content presentation information table among various information
tables.
[0055] Furthermore, the media content presentation information table may include an id_extension
element. The id_extension element may indicate an identifier for identifying a media
content presentation information table instance. Here, an id_extension field may include
a protocol_version field indicating a protocol version of the media content presentation
information table. The id_extension field may also include a sequence_number field
for identifying each of a plurality of media content presentation information tables
including different pieces of media content presentation information. The id_extension
element may indicate a service identifier for identifying a broadcasting service associated
with the media content presentation information table. Here, the id_extension element
may indicate any one of a program number, a service id, and a source id.
[0056] Furthermore, the media content presentation information table may include a version
element indicating a version of the media content presentation information table.
Here, the broadcast receiving device 100 may determine whether the media content presentation
information table is updated on the basis of the version element. In detail, the broadcast
receiving device 100 may determine that the media content presentation information
table has been updated, upon receiving the media content presentation information
table having a version element value different from that of a previously received
media content presentation information table. Here, the broadcast receiving device
100 may extract the media content presentation information from the media content
presentation information table. Furthermore, the broadcast receiving device 100 may
determine that the media content presentation information table has not been updated,
upon receiving the media content presentation information table having the same version
element value as that of a previously received media content presentation information
table. In this case, the broadcast receiving device 100 does not extract the media
content presentation information from the media content presentation information table.
In a specific embodiment, the version element may have the same value as that of the
version element included in the media content presentation information.
[0057] Furthermore, the media content presentation information table may include a media
content presentation information id element indicating an identifier for identifying
the media content presentation information.
[0058] Here, the media content presentation information table may include a media content
presentation information id_length element indicating a length of the identifier for
identifying the media content presentation information.
[0059] Furthermore, the media content presentation information table may include a coding
element indicating an encoding method of the media content presentation information.
Here, the coding element that indicates the encoding method may indicate that the
media content presentation information table includes the media content presentation
information without particularly compressing the media content presentation information.
Furthermore, the coding element that indicates the encoding method may indicate that
the media content presentation information table includes the media content presentation
information compressed by a specific algorithm. Here, the specific algorithm may be
a gzip algorithm.
[0060] Furthermore, the media content presentation information table may include a byte_length
element indicating a length of the media content presentation information.
[0061] Furthermore, the media content presentation information table may include a byte()
element that is the media content presentation information itself.
[0062] Here, the media content presentation information table may have an XML, HTML5 or
bitstream format.
[0063] Fig. 7 illustrates a bitstream syntax for the case where the MPD is transmitted in
a format of an MPD information table according to an embodiment.
[0064] Fig. 7 illustrates the case where the media content presentation information table
has a bitstream format, and the media content presentation information is included
in the MPD. Therefore, with respect to Fig. 7, the media content presentation information
table is referred to as an MPD information table.
[0065] The MPD information table includes a table_id field, a section_syntax_indicator field,
a private_indicator field, a private_section_length field, a table_id_extension field,
an MPD_data_version field, a section_number field, a last_section_number field, an
MPD_id_length field, an MPD_id_bytes field, an MPD_coding field, an MPD_byte_length
field, and an MPD_byte field.
[0066] In the example of Fig. 7, the table_id field indicates an identifier of the MPD information
table. Here, the table_id field may be 0xFA that is one of reserved id values defined
in ATSC A/65.
[0067] The section_syntax_indicator field indicates whether the MPD information table is
a long-type private section table of an MPEG-2 TS standard. Since the MPD information
table is not a long-type table, the section_syntax_indicator field has a value of
0.
[0068] The private_indicator field indicates whether a current table corresponds to a private
section. Since the MPD information table corresponds to the private section, the private_indicator
field has a value of 1.
[0069] The private_section_length field indicates a length of a section following the private_section_length
field.
[0070] The table_id_extension field indicates an identifier for identifying a broadcasting
service associated with the MPD transmitted via the MPD information table. Here, the
table_id_extension field may indicate any one of a program number, a service id, and
a source id. In another embodiment, the table_id_extension field may indicate an identifier
for identifying the MPD. In detail, the table_id_extension field may include a protocol_version
field indicating a protocol version of the MPD information table. Furthermore, the
table_id_extension field may include a sequence_number field for identifying each
of a plurality of MPD information tables including different MPDs.
[0071] The MPD_data_version field indicates a version of the MPD information table. Here,
the broadcast receiving device 100 may determine whether the MPD information table
is updated on the basis of the MPD_data_version field. The MPD_data_version field
may have the same value as that of the version element included in the MPD.
[0072] The section_number field indicates a number of a current section.
[0073] The last_section_number field indicates a number of a last section. In the case where
the MPD information table has a large size, the MPD information table may be divided
into a plurality of sections so as to be transmitted. Here, the broadcast receiving
device 100 determines whether all sections required for the MPD information table
are received on the basis of the section_number field and the last_section_number
field.
[0074] The MPD_id_bytes field indicates an identifier for identifying the MPD.
[0075] The MPD_id_length field indicates a length of the identifier for identifying the
MPD.
[0076] The MPD_coding field indicates an encoding method for the MPD. Here, the MPD_coding
field that indicates the encoding method may indicate that the MPD information table
includes the media content presentation information without particularly compressing
the media content presentation information. Furthermore, the MPD_coding field may
indicate that the MPD information table includes the MPD compressed by a specific
algorithm. Here, the specific algorithm may be a gzip algorithm. In a specific embodiment,
a value of the MPD_coding field may be defined as shown in Table 1.
[Table 1]
Value |
Designation |
0×00 |
Plain text |
0×01 |
Compressed by gzip |
0×02-0×03 |
Reserved for future use |
[0077] In the example of Table 1, in the case where the MPD_coding field has a value of
0x00, the MPD_coding field indicates that the MPD information table includes the media
content presentation information without particularly compressing the media content
presentation information. In the case where the MPD_coding field has a value of 0x01,
the MPD_coding field indicates that the MPD information table includes the MPD compressed
by a gzip algorithm.
[0078] The MPD_byte_length field indicates a length of the MPD.
[0079] The MPD_byte() field includes actual data of the MPD included in the MPD information
table.
[0080] Fig. 8 is a flowchart illustrating an operation of extracting, by a broadcast receiving
device, the MPD on the basis of an information table including the MPD according to
an embodiment.
[0081] The broadcast receiving device 100 receives a broadcast stream via the broadcast
receiving unit 150 (S301).
[0082] The broadcast receiving device 100 extracts the media content presentation information
table from the broadcast stream via the control unit 110 (S303). In a specific embodiment,
the broadcast receiving device 100 may extract the media content presentation information
table from the broadcast stream on the basis of the id element via the control unit
110. In detail, the broadcast receiving device 100 may extract the media content presentation
information table from the broadcast stream on the basis of information in which the
id element is combined with the id_extension element via the control unit 110. For
example, the broadcast receiving device 100 may identify the media content presentation
information table using a value of the id element via the control unit 110 so as to
extract the media content presentation information table from the broadcast stream.
Here, the broadcast receiving device 100 may identify the media content presentation
information table using a value obtained by combining the value of the id element
and the value of the id_extension element via the control unit 110 so as to extract
the media content presentation information table from the broadcast stream.
[0083] The broadcast receiving device 100 extracts the media content presentation information
on the basis of the media content presentation information table via the control unit
110 (S305). Here, in the case where the media content presentation information is
compressed, the broadcast receiving device 100 may decompress the media content presentation
information via the control unit 110 so as to extract the media content presentation
information.
[0084] The broadcast receiving device 100 receives media content via the IP transmitting/receiving
unit 130 on the basis of the media content presentation information (S307).
[0085] The broadcast receiving device 100 presents the media content via the control unit
110 (S309). In detail, the broadcast receiving device 100 may present the media content
on the basis of the media content presentation information via the control unit 110.
[0086] A content provider or a broadcaster may add the media content presentation information
to an IP datagram to transmit the media content presentation information via a broadcasting
network instead of an IP network. Here, the content provider or the broadcaster may
add the media content presentation information table including the media content presentation
information to the IP datagram to transmit the media content presentation information
table. This operation of adding the media content presentation information to the
IP datagram to transmit the media content presentation information is described below
with reference to Figs. 9 to 12.
[0087] In the case where the media content presentation information is added to the IP datagram
so as to be transmitted, the broadcast receiving device 100 may receive the media
content presentation information on the basis of a media IP datagram. In a specific
embodiment, the broadcast receiving device 100 may extract the media content presentation
information from the IP datagram to receive the media content presentation information.
In another specific embodiment, the broadcast receiving device 100 may extract the
media content presentation information table from the IP datagram to receive the media
content presentation information.
[0088] Here, the media content presentation information may be added to a UDP payload. The
UDP payload may include a payload_type field and a payload field. The payload_type
field indicates a data type of the media content presentation information included
in the payload field. Here, a value of the payload_type field may indicate that the
media content presentation information included in the payload field is a file itself.
In a specific embodiment, in the case where the media content presentation information
is included in the MPD, the value of the payload_type field may indicate that the
payload field includes the MPD as it is. In another specific embodiment, in the case
where the media content presentation information is included in the PI document, the
value of the payload_type field may indicate that the payload field includes the PI
document as it is. Furthermore, the value of the payload_type field may indicate that
the media content presentation information is included in a specific syntax format.
Furthermore, the value of the payload_type field may indicate that the media content
presentation information is included in the form of the above-mentioned media content
presentation information table.
[0089] The payload field may include the media content presentation information.
[0090] The content provider or the broadcaster may add a media content presentation information
link to the media content presentation information table to transmit the media content
presentation information link. Here, the media content presentation information link
may provide a link to the media content presentation information so that the media
content presentation information is received. Here, the media content presentation
information link may have a format of a uniform resource locator (URL). This operation
of adding the media content presentation information link to the media content presentation
information table to transmit the media content presentation information link is described
below with reference to Figs. 9 and 10.
[0091] In the case where the media content presentation information link is added to the
media content presentation information table so as to be transmitted, the broadcast
receiving device 100 may receive the media content presentation information on the
basis of the media content presentation information table. In detail, the broadcast
receiving device 100 may extract the media content presentation information link from
the media content presentation information table. Here, the broadcast receiving device
100 may receive the media content presentation information from the media content
presentation information link.
[0092] Here, the media content presentation information table may include an id element
for identifying the media content presentation information table among various information
tables.
[0093] Furthermore, the media content presentation information table may include an id_extension
element. The id_extension element may indicate an identifier for identifying a media
content presentation information table instance. Here, an id_extension field may include
a protocol_version field indicating a protocol version of the media content presentation
information table. The id_extension field may also include a sequence_number field
for identifying each of a plurality of media content presentation information tables
including different pieces of media content presentation information. The id_extension
element may indicate a service identifier for identifying a broadcasting service associated
with the media content presentation information table. Here, the id_extension element
may indicate any one of a program number, a service id, and a source id.
[0094] Furthermore, the media content presentation information table may include a version
element indicating a version of the media content presentation information table.
Here, the broadcast receiving device 100 may determine whether the media content presentation
information table is updated on the basis of the version element. In detail, the broadcast
receiving device 100 may determine that the media content presentation information
table has been updated, upon receiving the media content presentation information
table having a version element value different from that of a previously received
media content presentation information table. Here, the broadcast receiving device
100 may extract the media content presentation information from the media content
presentation information table. Furthermore, the broadcast receiving device 100 may
determine that the media content presentation information table has not been updated,
upon receiving the media content presentation information table having the same version
element value as that of a previously received media content presentation information
table. In this case, the broadcast receiving device 100 does not extract the media
content presentation information from the media content presentation information table.
In a specific embodiment, the version element may have the same value as that of the
version element included in the media content presentation information.
[0095] Furthermore, the media content presentation information table may include a media
content presentation information id element indicating an identifier for identifying
the media content presentation information.
[0096] Here, the media content presentation information table may include a media content
presentation information id_length element indicating a length of the identifier for
identifying the media content presentation information.
[0097] Furthermore, the media content presentation information table may include a byte_length
element indicating a length of the media content presentation information link.
[0098] Furthermore, the media content presentation information table may include a byte()
element that is the media content presentation information link itself. Here, the
media content presentation information link may have a URL format.
[0099] Here, the media content presentation information table may have an XML, HTML5 or
bitstream format.
[0100] Fig. 9 illustrates an MPD link table including an MPD link according to an embodiment.
[0101] Fig. 9 illustrates the case where the media content presentation information table
has a bitstream format, and the media content presentation information is included
in the MPD. Therefore, with respect to Fig. 9, the media content presentation information
table is referred to as an MPD information table. The media content presentation information
link has a URL format. Therefore, the media content presentation information link
is referred to as an MPD_URL.
[0102] The MPD information table includes a table_id field, a section_syntax_indicator field,
a private_indicator field, a private_section_length field, a table_id_extension field,
an MPD_data_version field, a section_number field, a last_section_number field, an
MPD_id_length field, an MPD_id_byte field, an MPD_URL_length field, and an MPD_URL_bytes
field.
[0103] In the example of Fig. 9, the table_id field indicates an identifier of the MPD information
table. Here, the table_id field may be 0xFA that is one of reserved id values defined
in ATSC A/65.
[0104] The section_syntax_indicator field indicates whether the MPD information table is
a long-type private section table of the MPEG-2 TS standard. Since the MPD information
table is not a long-type table, the section_syntax_indicator field has a value of
0.
[0105] The private_indicator field indicates whether a current table corresponds to a private
section. Since the MPD information table corresponds to the private section, the private_indicator
field has a value of 1.
[0106] The private_section_length field indicates a length of a section following the private_section_length
field.
[0107] The table_id_extension field indicates an identifier for identifying a broadcasting
service associated with the MPD transmitted via the MPD information table. Here, the
table_id_extension field may indicate any one of a program number, a service id, and
a source id. In another embodiment, the table_id_extension field may indicate an identifier
for identifying the MPD. In detail, the table_id_extension field may include a protocol_version
field indicating a protocol version of the MPD information table. Furthermore, the
table_id_extension field may include a sequence_number field for identifying each
of a plurality of MPD information tables including different MPDs.
[0108] The MPD_data_version field indicates a version of the MPD information table. Here,
the broadcast receiving device 100 may determine whether the MPD information table
is updated on the basis of the MPD_data_version field. The MPD_data_version field
may have the same value as that of the version element included in the MPD.
[0109] The section_number field indicates a number of a current section.
[0110] The last_section_number field indicates a number of a last section. In the case where
the MPD information table has a large size, the MPD information table may be divided
into a plurality of sections so as to be transmitted. Here, the broadcast receiving
device 100 determines whether all sections required for the MPD information table
are received on the basis of the section_number field and the last_section_number
field.
[0111] The MPD_id_bytes field indicates an identifier for identifying the MPD.
[0112] The MPD_id_length field indicates a length of the identifier for identifying the
MPD.
[0113] The MPD_URL_length field indicates a length of the MPD_URL.
[0114] The MPD_URL_bytes() field indicates the MPD_URL itself.
[0115] Fig. 10 is a flowchart illustrating an operation of receiving, by a broadcast receiving
device, the MPD on the basis of the media content presentation information table including
the media content presentation information link according to an embodiment.
[0116] The broadcast receiving device 100 receives a broadcast stream via the broadcast
receiving unit 150 (S401).
[0117] The broadcast receiving device 100 extracts the media content presentation information
table including the media content presentation information link from the broadcast
stream via the control unit 110 (S403). In a specific embodiment, the broadcast receiving
device 100 may extract the media content presentation information table from the broadcast
stream on the basis of the id element via the control unit 110. In detail, the broadcast
receiving device 100 may extract the media content presentation information table
from the broadcast stream on the basis of information in which the id element is combined
with the id_extension element via the control unit 110. For example, the broadcast
receiving device 100 may identify the media content presentation information table
using a value of the id element via the control unit 110 so as to extract the media
content presentation information table from the broadcast stream. Here, the broadcast
receiving device 100 may identify the media content presentation information table
using a value obtained by combining the value of the id element and the value of the
id_extension element via the control unit 110 so as to extract the media content presentation
information table from the broadcast stream.
[0118] The broadcast receiving device 100 extracts the media content presentation information
link on the basis of the media content presentation information table via the control
unit 110 (S405). Here, the media content presentation information link may have a
URL format.
[0119] The broadcast receiving device 100 receives the media content presentation information
on the basis of the media content presentation information link via the IP transmitting/receiving
unit 130 (S407).
[0120] The broadcast receiving device 100 receives media content via the IP transmitting/receiving
unit 130 on the basis of the media content presentation information (S409).
[0121] The broadcast receiving device 100 presents the media content via the control unit
110 (S411). In detail, the broadcast receiving device 100 may present the media content
on the basis of the media content presentation information via the control unit 110.
[0122] Figs. 11 to 13 illustrate the case where the media content presentation information
is included in the MPD. Fig. 11 illustrates that the MPD or the MPD information table
is added to an IP datagram so as to be transmitted according to an embodiment.
[0123] As exemplified by the data structure of Fig. 11, the IP datagram includes a UDP datagram
in an IP payload in the examples of Figs. 11 to 13. The UDP datagram includes the
MPD or the MPD information table in a UDP payload. A syntax of the IP datagram will
be described in detail with reference to Fig. 12.
[0124] Fig. 12 illustrates the syntax of the IP datagram for the case where the MPD or the
MPD information table is added to the IP datagram so as to be transmitted according
to an embodiment.
[0125] The UDP payload includes an MPD_payload_type field and a payload field. The MPD_payload_type
field indicates a data type of the MPD included in the MPD_payload field. A value
of the MPD_payload_type field may indicate that the MPD_payload field includes the
MPD itself. Furthermore, the value of the MPD_payload_type field may indicate that
the MPD_payload field includes the MPD in a specific syntax format. In detail, the
value of the MPD_payload_type field may be defined as shown in Table 2 below.
[Table 2]
Value |
Designation |
0×00 |
Not specified |
0×01 |
Syntax |
0×02 |
MPD file as it is |
0×03 |
MPD section |
0×03 |
Reserved for future use |
[0126] In the example of Table 2, in the case where the value of the MPD_payload_type field
is 0x01, the MPD_payload_type field indicates that the MPD_payload field includes
the MPD in a specific syntax format. In the case where the value of the MPD_payload_type
field is 0x02, the MPD_payload_type field indicates that the MPD_payload field includes
the MPD as it is. In the case where the value of the MPD_payload_type field is 0x03,
the MPD_payload_type field indicates that the MPD_payload field includes the MPD in
the form of the above-mentioned MPD information table.
[0127] The MPD_payload field includes the MPD.
[0128] Fig. 13 illustrates a syntax of an MPD payload included in the IP datagram for the
case where the MPD or the MPD information table is added to the IP datagram so as
to be transmitted according to an embodiment.
[0129] An MPD_coding field indicates an encoding method for the MPD or the MPD information
table. Here, the MPD_coding field that indicates the encoding method may indicate
that the MPD payload includes the MPD or the MPD information table without particularly
compressing the MPD or the MPD information table. Furthermore, the MPD_coding field
may indicate that the MPD payload includes the MPD or the MPD information table compressed
by a specific algorithm. Here, the specific algorithm may be a gzip algorithm. In
a specific embodiment, a value of the MPD_coding field may be defined as shown in
Table 3.
[Table 3]
Value |
Designation |
0×00 |
Plain text |
0×01 |
Compressed by gzip |
0×02-0×03 |
Reserved for future use |
[0130] In the example of Table 3, in the case where the MPD_coding field has a value of
0x00, the MPD_coding field indicates that the MPD payload includes the MPD or the
MPD information table without particularly compressing the MPD or the MPD information
table. In the case where the MPD_coding field has a value of 0x01, the MPD_coding
field indicates that the MPD payload includes the MPD or the MPD information table
compressed by a gzip algorithm.
[0131] An MPD_byte_length field indicates a length of the MPD or the MPD information table.
[0132] Fig. 14 is a flowchart illustrating an operation of extracting, by a broadcast receiving
device, the media content presentation information or the media content presentation
information table on the basis of the IP datagram including the media content presentation
information or the media content presentation information table according to an embodiment.
[0133] The broadcast receiving device 100 receives a broadcast stream via the broadcast
receiving unit 150 (S501).
[0134] The broadcast receiving device 100 extracts the IP datagram from the broadcast stream
via the control unit 110 (S503).
[0135] The broadcast receiving device 100 extracts the UDP datagram from the IP datagram
via the control unit 110 (S505). In detail, the broadcast receiving device 100 extracts
the UDP datagram from a payload of the IP datagram.
[0136] The broadcast receiving device 100 extracts the media content presentation information
on the basis of the UDP datagram via the control unit 110 (S507). In detail, the broadcast
receiving device 100 extracts the media content presentation information or the media
content presentation information table from the payload of the UDP datagram. In a
specific embodiment, in the case where the media content presentation information
or the media content presentation information table is compressed, the broadcast receiving
device 100 may decompress the media content presentation information or the media
content presentation information table via the control unit 110 so as to extract the
media content presentation information or the media content presentation information
table. Here, the broadcast receiving device 100 may decompress the media content presentation
information or the media content presentation information table on the basis of a
coding field included in the UDP datagram. Here, the broadcast receiving device 100
may extract the media content presentation information from the media content presentation
information table via the control unit 110.
[0137] The broadcast receiving device 100 receives media content via the IP transmitting/receiving
unit 130 on the basis of the media content presentation information (S507).
[0138] The broadcast receiving device 100 presents the media content via the control unit
110 (S509). In detail, the broadcast receiving device 100 may present the media content
on the basis of the media content presentation information via the control unit 110.
[0139] A content provider or a broadcaster may add a method of transmitting the media content
presentation information to a broadcast information signaling table to transmit the
method of transmitting the media content presentation information. This operation
of adding the method of transmitting the media content presentation information to
the broadcast information signaling table to transmit the method of transmitting the
media content presentation information is described below with reference to Figs.
15 to 23. Here, the broadcast information signaling table may have an XML, HTML5 or
bitstream format.
[0140] In a specific embodiment, the content provider or the broadcaster may add a descriptor
including the method of transmitting the media content presentation information to
the broadcast information signaling table to transmit the descriptor.
[0141] Here, the broadcast information signaling information table may be one of a program
specific information (PSI) table defined in an ISO/IEC 13818-1 standard, a system
information (SI) table defined in an ETSI EN 300 468 standard, and a program and system
information protocol (PSIP) table defined in an ATSC standard. In particular, the
signaling information table may be an information table for signaling information
on broadcast content. Here, the information on broadcast content may be one of information
on a broadcasting service, information on an elementary stream, and information on
an event. In detail, the information table may be one of a terrestrial virtual channel
table (TVCT) and an event information table (EIT) among tables defined in A/65 that
is one of ATSC standards, a service map table (SMT) among tables defined in A/153,
a service description table (SDT) and an EIT defined in an ETSI EN 300 468 standard,
and a program map table (PMT) defined in an ISO/IEC 13818-1 standard.
[0142] The descriptor may include a tag element for identifying the descriptor.
[0143] Furthermore, the descriptor may include a length element indicating a length of the
descriptor.
[0144] The descriptor may include a simulcast_flag indicating that broadcast content specified
by the descriptor is simultaneously transmitted via not only a broadcasting network
but also an IP network. Here, the broadcast content may be one of an elementary stream
specified by the descriptor, a service specified by the descriptor, and an event specified
by the descriptor. In the case where the simulcast_flag has a value of 1 and transmission
of a broadcast stream via the broadcasting network is unstable, the broadcast receiving
device 100 may receive the broadcast content specified by the descriptor via the IP
network. In detail, in the case where the simulcast_flag has a value of 1 and a strength
of a signal of the broadcast stream transmitted via the broadcasting network is lower
than a certain reference level or presentation interruption of the broadcast content
occurs, the broadcast receiving device 100 may receive the broadcast content specified
by the descriptor via the IP network. Here, the broadcast receiving device 100 may
notify a user that the broadcast content specified by the descriptor is able to be
received. Furthermore, the broadcast receiving device 100 may receive the broadcast
content specified by the descriptor on the basis of an input from the user. In detail,
the broadcast receiving device 100 may receive the broadcast content specified by
the descriptor via the IP network, upon receiving an input from the user.
[0145] Furthermore, the descriptor may include a version element indicating a version of
the media content presentation information.
[0146] Moreover, the descriptor may include a transport_mode element indicating a specific
method of transmitting the media content presentation information or the media content
presentation information table. Here, a value of the transport_mode element may indicate
that the descriptor directly includes the media content presentation information or
the media content presentation information table. Furthermore, the value of the transport_mode
element may indicate that the media content presentation information or the media
content presentation information table may be downloaded via a link address included
in the descriptor. The value of the transport_mode element may indicate that an information
table included in a packet that is different from a packet that includes the descriptor
includes the media content presentation information. The value of the transport_mode
element may indicate that an additional broadcast stream includes the media content
presentation information. The value of the transport_mode element may indicate that
an IP datagram includes the media content presentation information or the media content
presentation information table. The value of the transport_mode element may indicate
that the media content presentation information or the media content presentation
information table is transmitted using a session-based transport protocol. Here, the
session-based transport protocol may be File Delivery over Unidirectional Transport
(FLUTE). The session-based transport protocol may be Asynchronous Layered Coding (ALC)/Layered
Coding Transport (LCT).
[0147] The descriptor may include a bootstrap_data element including specific transmission
information corresponding to a method of transmitting the media content presentation
information or the media content presentation information table. Here, in the case
where the descriptor directly includes the media content presentation information,
the bootstrap_data element may include the media content presentation information
itself. In this case, the broadcast receiving device 100 may extract the media content
presentation information from the descriptor.
[0148] In the case where the media content presentation information or the media content
presentation information table is able to be received via a link included in the descriptor,
the bootstrap_data element may include a link for downloading the media content presentation
information or the media content presentation information table. In a specific embodiment,
the broadcast receiving device 100 may access the link to download the media content
presentation information or the media content presentation information table. Here,
the link may be provided in plurality. Furthermore, there may be a priority order
for the plurality of links. In this case, the broadcast receiving device 100 may attempt
to download the media content presentation information or the media content presentation
information table in descending order of priorities of the links. Here, the links
may have a URL format.
[0149] In the case where an information table included in a packet that is different from
a packet that includes the descriptor includes the media content presentation information
or the media content presentation information link for providing a link to the media
content presentation information, the bootstrap_data element may include an identifier
of a packet that includes the media content presentation information or the media
content presentation information link. Here, a table ID of the information table may
be predetermined. However, in the case where the table ID of the information table
is not predetermined, the bootstrap_data element may include the table ID of the information
table. Here, the information table may be the above-mentioned media content presentation
information table.
[0150] In the case where an additional broadcast stream includes the media content presentation
information or the media content presentation information link, the bootstrap_data
element may include an identifier of a packet and an identifier of the broadcast stream
including the media content presentation information or the media content presentation
information link. Here, in the case where the broadcast stream complies with the MPEG-2
TS standard, the identifier of the broadcast stream may be a TS ID and the packet
identifier may be a PID. In detail, the information table included in the packet may
include the media content presentation information or the media content presentation
information link. Here, the table ID of the information table may be predetermined.
However, in the case where the table ID of the information table is not predetermined,
the bootstrap_data element may include the table ID of the information table. Here,
the information table including the media content presentation information may be
the above-mentioned media content presentation information table.
[0151] In the case where an IP datagram includes the media content presentation information
or the media content presentation information table, the bootstrap_data element may
include an identifier of a data transmission channel of a physical layer for downloading
the IP datagram including the media content presentation information, an IP address,
a port number, a flag indicating whether a source IP address is included, the source
IP address, and a version of an IP address format.
[0152] In the case where the media content presentation information or the media content
presentation information table is transmitted via a session-based transport protocol
session, the bootstrap_data element may include an identifier of a data transmission
channel of a physical layer for downloading the media content presentation information
or the media content presentation information table, an identifier of a session, an
IP address of the session, a port number of the session, a flag indicating whether
a source IP address of the session is included, the source IP address of the session,
and a version of an IP address format. As described above, the session-based transport
protocol may be FLUTE. The session-based transport protocol may be ALC/LCT. In the
case where the session-based transport protocol is FLUTE, the identifier of the session
may be TSI that is a FLUTE session identifier.
[0153] In the examples of Figs. 15 to 21, the MPD includes the media content presentation
information. Therefore, with respect to the examples of Figs. 15 to 21, a descriptor
including a method of transmitting the media content presentation information or the
media content presentation information table is referred to as an MPD descriptor.
Here, the MPD descriptor is included in a bitstream-type broadcast information signaling
information table.
[0154] Fig. 15 illustrates a syntax of the MPD descriptor for transmitting the MPD according
to an embodiment.
[0155] The MPD descriptor includes a descriptor_tag field, a descriptor_length field, an
MPD_version field, a simulcast_flag field, an MPD_transport mode field, and an MPD_bootstrap_data
field.
[0156] The descriptor_tag field indicates an identifier of the MPD descriptor.
[0157] The descriptor_length field indicates a length of the MPD descriptor.
[0158] The MPD_version field indicates a version of the MPD.
[0159] The simulcast_flag field indicates that broadcast content specified by the MPD descriptor
is simultaneously transmitted via not only a broadcasting network but also an IP network.
Here, the broadcast content may be one of an elementary stream specified by the MPD
descriptor, a service specified by the MPD descriptor, and an event specified by the
MPD descriptor. In the case where the simulcast_flag has a value of 1 and transmission
of a broadcast stream via the broadcasting network is unstable, the broadcast receiving
device 100 may receive the broadcast content specified by the descriptor via the IP
network. In detail, in the case where the simulcast_flag has a value of 1 and a strength
of a signal of the broadcast stream transmitted via the broadcasting network is lower
than a certain reference level or presentation interruption of the broadcast content
occurs, the broadcast receiving device 100 may receive the broadcast content specified
by the descriptor via the IP network. Here, the broadcast receiving device 100 may
notify the user that the broadcast content specified by the MPD descriptor is able
to be received. Furthermore, the broadcast receiving device 100 may receive the broadcast
content specified by the MPD descriptor on the basis of an input from the user. In
detail, the broadcast receiving device 100 may receive the broadcast content specified
by the MPD descriptor via the IP network, upon receiving an input from the user.
[0160] The MPD_transport mode field indicates a specific method of transmitting the MPD,
the MPD information table (MPD_Section) or the MPD link table (MPD_URL_Section). Here,
a value of the MPD_transport mode field may indicate that the MPD descriptor directly
includes the MPD. Furthermore, the value of the MPD_transport mode field may indicate
that the MPD, the MPD information table, or the MPD link table is able to be downloaded
via a link address included in the MPD descriptor. The value of the MPD_transport
mode field may indicate that an information table included in a packet that is different
from a packet that includes the MPD descriptor includes the MPD or the MPD_URL. Here,
the MPD_URL indicates a URL for downloading the MPD. Here, the information table may
be the above-mentioned MPD information table. The information table may be the above-mentioned
MPD link information table. The value of the MPD_transport mode field may indicate
that an additional broadcast stream includes the MPD or the MPD_URL. Here, the information
table may be the above-mentioned MPD information table. The information table may
be the above-mentioned MPD link information table. Furthermore, the value of the MPD_transport
mode field may indicate that an IP datagram includes the MPD, the MPD information
table, or the MPD link table. Furthermore, the value of the MPD_transport mode field
may indicate that the MPD, the MPD information table, or the MPD link table is transmitted
via a session-based transport protocol session such as FLUTE or ALC/LCT. In detail,
the MPD_transport mode field may be assigned values as shown in Table 4 below.
[Table 4]
Value |
Designation |
0×00 |
The MPD is delivered in MPD data bytes() |
0×01 |
The location of MPD, MPD_Section or MPD_URL_Section is identified in the URL carried
in the MPD URL |
0×02 |
The MPD or MPD_URL is delivered by section as separate tables (e.g., MPEG-2 private
section) in same broadcast network |
0×03 |
The MPD or MPD_URL is delivered by section as separate tables (e.g., MPEG-2 private
section) in different broadcast network |
0×04 |
The MPD, MPD_Section or MPD_URL_Section is delivered in IP datagrams |
0×05 |
The MPD, MPD_Section or MPD_URL is delivered in sessions (e.g., FLUTE, ALC/LCT, etc.) |
0×06-0×07 |
Reserved for future use |
[0161] In the example of Table 4, in the case where the value of the MPD_transport mode
field is 0x00, the MPD_transport mode field indicates that the MPD descriptor directly
includes the MPD. In the case where the value of the MPD_transport mode field is 0x01,
the MPD_transport mode field indicates that the MPD, the MPD information table, or
the MPD link table is able to be downloaded via a link address included in the MPD
descriptor. In the case where the value of the MPD_transport mode field is 0x02, the
MPD_transport mode field indicates that an information table included in a packet
that is different from a packet that includes the MPD descriptor includes the MPD
or the MPD_URL. In the case where the value of the MPD_transport mode field is 0x03,
the MPD_transport mode field indicates that an additional broadcast stream includes
the MPD. In the case where the value of the MPD_transport mode field is 0x04, the
MPD_transport mode field indicates that an IP datagram includes the MPD, the MPD information
table or the MPD link table. In the case where the value of the MPD_transport mode
field is 0x05, the MPD_transport mode field indicates that the MPD, the MPD information
table or the MPD link table is transmitted via a transport protocol session. Here,
the transport protocol may be FLUTE. Alternatively, the transport protocol may be
ALC/LCT.
[0162] The MPD_bootstrap_data field includes specific transmission information according
to a method of transmitting the MPD or the MPD information table. This configuration
will be described in detail with reference to Figs. 14 to 19.
[0163] Fig. 16 illustrates a syntax of MPD bootstrap_data in the case where the MPD descriptor
directly includes the MPD.
[0164] In the case where the MPD descriptor directly includes the media content presentation
information, the bootstrap_data includes an MPD_data_length field and an MPD_data_byte
field. The MPD_data_length field indicates a size of MPD data. The MPD_data_byte field
indicates actual data of the MPD. In this case, the broadcast receiving device 100
may extract the MPD from the MPD descriptor.
[0165] Fig. 17 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes a link address indicating a storage place of the MPD, the MPD
information table or the MPD link table.
[0166] In the case where the MPD is downloadable via the link address included in the MPD
descriptor, the bootstrap_data includes an MPD_URL_length field and an MPD_URL field.
The MPD_URL_length field indicates a length of a URL. The MPD_URL field indicates
a URL for downloading the MPD, the MPD information table or the MPD link table.
[0167] Fig. 18 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes an identifier of a data packet including the MPD.
[0168] In the case where an information table included in a packet that is different from
a packet that includes the MPD descriptor includes the MPD and the MPD_URL, the bootstrap_data
includes an MPD_pid field. Here, the information table may be the MPD information
table as described above. Alternatively, the information table may be the MPD link
information table as described above. The MPD_pid field indicates an identifier of
a packet including the MPD. Here, in the case where a broadcast stream complies with
the MPEG-2 TS standard, the packet identifier may be a PID. The broadcast receiving
device 100 may extract the MPD on the basis of the MPD_pid field. The broadcast receiving
device 100 may identify a packet including the MPD or the MPD_URL using a value of
the MPD_pid field, and may extract the MPD or the MPD_URL from the packet including
the MPD or the MPD_URL. Here, the table ID of the information table may be predetermined.
However, in the case where the table ID of the information table is not predetermined,
the bootstrap_data may include a table_id field indicating the table ID of the information
table.
[0169] Fig. 19 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes an identifier of an additional broadcast stream including the
MPD.
[0170] In the case where the additional broadcast stream includes the MPD or the MPD_URL,
the bootstrap_data includes a transport_stream_id field and an MPD_pid field. The
transport_stream_id field indicates an identifier of a broadcast stream including
the MPD. The MPD_pid field indicates an identifier of a packet including the MPD or
the MPD_URL. Here, in the case where the broadcast stream complies with the MPEG-2
TS standard, the identifier of the broadcast stream may be a TS ID and the packet
identifier may be a PID. The broadcast receiving device 100 may extract the MPD or
the MPD_URL on the basis of the transport_stream_id field and the MPD_pid field. The
broadcast receiving device 100 may identify the broadcast stream including the MPD
or the MPD_URL using the transport_stream_id field, and may identify the packet including
the MPD using the MPD_pid field. Thereafter, the broadcast receiving device 100 may
extract the MPD or the MPD_URL from the packet including the MPD or the MPD_URL. In
a specific embodiment, the packet including the MPD may include the MPD information
table. In another specific embodiment, the packet including the MPD_URL may include
the MPD link information table. Here, the table ID of the information table may be
predetermined. However, in the case where the table ID of the information table is
not predetermined, the bootstrap_data may include a table_id field indicating the
table ID of the information table.
[0171] Fig. 20 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes information on an IP datagram including the MPD, the MPD information
table or the MPD link information table.
[0172] In the case where the MPD descriptor includes information on an IP datagram including
the MPD, the MPD information table or the MPD link information table, the bootstrap_data
includes an IP_version_flag field, a source_IP_address_flag field, a source_IP_address
field, a destination_IP_address field, a destination_port_number field, and a dataPipe_id
field. The dataPipe_id field indicates an identifier of a data transmission channel
of a physical layer. In detail, the broadcast receiving device 100 may obtain a specific
IP datagram via a corresponding transmission channel. The IP_version_flag field indicates
a version of an IP address format. The source_IP_address_flag field indicates whether
a source IP address of the IP datagram including the MPD, the MPD information table
or the MPD link information table is included. The destination_IP_address field indicates
an IP address for downloading the IP datagram including the MPD, the MPD information
table or the MPD link information table. The destination_port_number field indicates
a port number for downloading the IP datagram including the MPD, the MPD information
table or the MPD link information table. The broadcast receiving device 100 may extract
the MPD, the MPD information table or the MPD link information table on the basis
of the dataPipe_id field, the destination_IP_address field, and the destination_port_number
field. The broadcast receiving device 100 may identify the data channel of the physical
layer that transmits the IP datagram on the basis of the dataPipe_id field, and may
extract the IP datagram including the MPD, the MPD information table or the MPD link
information table on the basis of the destination_IP_address field and the destination_port_number
field. Thereafter, the broadcast receiving device 100 may extract the MPD, the MPD
information table or the MPD link information table from the IP datagram including
the MPD, the MPD information table or the MPD link information table.
[0173] Fig. 21 illustrates the syntax of the MPD bootstrap_data in the case where the MPD
descriptor includes information on a session-based transport protocol session such
as FLUTE or ALC/LCT for transmitting the MPD.
[0174] In the case where the media content presentation information is transmitted via a
session-based transport protocol session such as FLUTE or ACL/LCT, the bootstrap_data
includes an IP_version_flag field, a source_IP_address_flag field, a source_IP_address
field, a destination_IP_address field, a destination_port_number field, a dataPipe_id
field, and a flute_tsi field. The IP_version_flag field indicates a version of an
IP address format. The source_IP_address_flag field indicates whether a source IP
address of a FLUTE session for transmitting the MPD is included. The destination_IP_address
field indicates an IP address of the FLUTE session for transmitting the MPD. The destination_port_number
field indicates a port number of the FLUTE session for transmitting the MPD. The dataPipe_id
field indicates an identifier of a data transmission channel of a physical layer.
The flute_tsi field indicates an identifier of the FLUTE session for transmitting
the MPD. The broadcast receiving device 100 may extract the MPD, the MPD information
table or the MPD link information table using the dataPipe_id field, the destination_IP_address
field, and the destination_port_number field, and the flute_tsi field. In detail,
the broadcast receiving device 100 may identify the data transmission channel of the
physical channel according to a value of the dataPipe_id field, and may extract the
MPD, the MPD information table or the MPD link information table using the flute_tsi
field, the destination_IP_address field, and the destination_port_number field.
[0175] Fig. 22 is a flowchart illustrating an operation of receiving, by a broadcast receiving
device, the media content presentation information in the case where a method of transmitting
the media content presentation information is added to the broadcast information signaling
information table so as to be transmitted.
[0176] The broadcast receiving device 100 receives a broadcast stream via the broadcast
receiving unit 150 (S701).
[0177] The broadcast receiving device 100 extracts, via the control unit, an information
table including a descriptor including the method of transmitting the media content
presentation information (S703). As described above, the information table may be
one of a program specific information (PSI) table defined in the ISO/IEC 13818-1 standard,
a system information (SI) table defined in the ETSI EN 300 468 standard, and a program
and system information protocol (PSIP) table defined in the ATSC standard. In particular,
the information table may be an information table for signaling information on broadcast
content. The information on broadcast content may be information on a broadcasting
service, information on an elementary stream, or information on an event. In detail,
the information table may be one of a terrestrial virtual channel table (TVCT) and
an event information table (EIT) among tables defined in A/65 that is one of ATSC
standards, a service map table (SMT) among tables defined in A/153, a service description
table (SDT) and an EIT defined in the ETSI EN 300 468 standard, and a program map
table (PMT) defined in the ISO/IEC 13818-1 standard.
[0178] The broadcast receiving device 100 extracts, via the control unit 110, the descriptor
including the method of transmitting the media content presentation information from
the information table (S705).
[0179] The broadcast receiving device 100 extracts, via the control unit 110, the method
of transmitting the media content presentation information from the information table
(S707). The descriptor may include a transport_mode element indicating a specific
method of transmitting the media content presentation information or the media content
presentation information table. The descriptor may include a bootstrap_data element
including specific transmission information according to the method of transmitting
the media content presentation information or the media content presentation information
table. Here, the broadcast receiving device 100 may identify the method of transmitting
the media content presentation information or the media content presentation information
table on the basis of the transport_mode element, and may extract transmission information
of the media content presentation information or the media content presentation information
table on the basis of the bootstrap_data element. Here, as described above, the method
of transmitting the media content presentation information may correspond to one of
the case where the descriptor directly includes the media content presentation information,
the case where the descriptor directly includes the media content presentation information
table, the case where the media content presentation information or the media content
presentation information table is downloadable via a link included in the descriptor,
the case where a packet that is different from a packet that includes the descriptor
includes the media content presentation information or the media content presentation
information link, the case where an additional broadcast stream includes the media
content presentation information or the media content presentation information link,
the case where the bootstrap_data element includes an identifier of a broadcast stream
including the media content presentation information and a packet identifier, the
case where an IP datagram includes the media content presentation information or the
media content presentation information table, and the case where the media content
presentation information is transmitted via a session-based transport protocol.
[0180] The broadcast receiving device 100 obtains, via the control unit 110, the media content
presentation information on the basis of the method of transmitting the media content
presentation information or the media content presentation information table (S709).
Here, the broadcast receiving device 100 may obtain the media content presentation
information table via the control unit 110. The broadcast receiving device 100 may
extract the media content presentation information from the media content presentation
information table via the control unit 110.
[0181] The broadcast receiving device 100 receives media content via the IP transmitting/receiving
unit 130 on the basis of the media content presentation information (S711).
[0182] The broadcast receiving device 100 presents the media content via the control unit
110 (S713). In detail, the broadcast receiving device 100 may present the media content
on the basis of the media content presentation information via the control unit 110.
Here, in the case where broadcast content is transmitted via not only a broadcasting
network but also an IP network, the media content may be presented on the basis of
whether transmission of a broadcast stream is stable. This configuration will be described
with reference to Fig. 23.
[0183] Fig. 23 is a flowchart illustrating an operation of presenting, by a broadcast receiving
device, media content on the basis of whether transmission of a broadcast stream is
stable in the case where broadcast content is transmitted via not only a broadcasting
network but also an IP network.
[0184] The broadcast receiving device 100 determines, via the control unit 110, whether
broadcast content specified by a descriptor is transmitted via not only a broadcasting
network but also an IP network (S901). In detail, the broadcast receiving device 100
may determine, via the control unit 110, whether a value of the simulcast_flag element
included in the descriptor is 1.
[0185] In the case where the broadcast content specified by the descriptor is transmitted
via the IP network, the broadcast receiving device 100 determines, via the control
unit 110, whether transmission of a broadcast stream is stable (S903). In detail,
the broadcast receiving device 100 may determine, via the control unit 110, whether
a strength of a signal of the broadcast stream transmitted via the broadcasting network
is lower than a certain reference level. In another specific embodiment, the broadcast
receiving device 100 may determine, via the control unit 110, whether presentation
interruption of the broadcast content occurs.
[0186] If the transmission of the broadcast stream is unstable, the broadcast receiving
device 100 receives the media content via the IP transmitting/receiving unit 130 on
the basis of the media content presentation information (S905).
[0187] The broadcast receiving device 100 presents the media content via the control unit
110 (S907). In detail, the broadcast receiving device 100 may present the media content
on the basis of the media content presentation information via the control unit 110.
[0188] In general, a time of presenting broadcast content on a screen is determined according
to a program clock reference such as 90 KHz. However, a time of presenting, on a screen,
media content transmitted via an IP network is determined according to a timescale
assigned at the moment of generating the content. Therefore, the broadcast receiving
device 100 capable of presenting both broadcast content and media content is required
to synchronize the screen presentation time of the broadcast content with that of
the media content transmitted via the IP network. In particular, in the case of presenting
media content transmitted via the IP network which is the same as broadcast content
transmitted via the broadcasting network after presenting the broadcast content as
described above with reference to Fig. 21, the broadcast receiving device 100 is required
to synchronize presentation times. Furthermore, the broadcast receiving device 100
is required to synchronize presentation times so that various additional services
received via a broadcast stream is provided in synchronization with media content.
[0189] Described below with reference to Figs. 24 to 27 is a method of synchronizing screen
presentation times between broadcast content and media content transmitted via an
IP network.
[0190] A content provider or a broadcaster may add information for synchronizing media content
to an additional synchronization information packet of a broadcast stream to transmit
the information for synchronizing media content. This operation of adding the information
for synchronizing media content to the additional synchronization information packet
of the broadcast stream to transmit the information for synchronizing media content
is described below with reference to Fig. 24.
[0191] The synchronization information packet may include a force_update element indicating
whether the media content presentation information is required to be updated prior
to presentation time synchronization.
[0192] Furthermore, the synchronization information packet may include a switch_timer indicating
a remaining time from a broadcast stream reference time of the synchronization information
packet to a start time of a presentation interval of media content to be synchronized.
Here, the broadcast stream reference time is set so that a plurality of elementary
streams included in a broadcast stream are synchronized with one timeline. Here, the
synchronization information packet may include the broadcast stream reference time
of the synchronization information packet. In the case where the broadcast stream
complies with the MPEG-2 TS standard, the broadcast stream reference time of the synchronization
information packet may be a PTS. In the case where a value of the switch_timer element
is 0, the switch_timer element may indicate that the presentation interval of the
media content to be synchronized is active and the media content is required to be
synchronized immediately. In the case where the value of the switch_timer element
is not 0, the switch_timer element may indicate that the presentation interval of
the media content to be synchronized is not active.
[0193] Furthermore, the synchronization information packet may include a presentation_time
element indicating an own presentation time of the media content to be synchronized
with broadcast content. Here, a synchronized presentation time of broadcast content
received before a new synchronization information packet is received may be obtained
using a value of the presentation_time element. This operation is performed using
the following equation.

[0194] In the equation, MPT denotes the synchronized presentation time of broadcast content
received before a new synchronization information packet is received, PT0 denotes
the broadcast stream reference time of the synchronization information packet, PT
denotes the broadcast stream reference time of the broadcast content received before
the new synchronization information packet is received, RC denotes the reference clock
of a broadcast stream, presentation_time denotes the own presentation time of media
content which is a value of the presentation_time element, TimeOffset denotes a media
content presentation start time of a presentation interval of the media content to
be synchronized by the synchronization information packet, and timescale denotes a
timescale of the own presentation time of the media content.
[0195] Furthermore, the packet including the information for synchronizing media content
may include a period_id element indicating an identifier of the presentation interval
of the media content to be synchronized. In a specific embodiment, in the case where
media content is transmitted according to the MPEG-DASH standard, the period_id element
may include an ID of a period element of the MPD and a URL of the MPD.
[0196] In the case where a broadcast stream is transmitted according to the MPEG-2 TS standard,
the synchronization information packet may be transmitted as a packet elementary stream
(PES) packet. Here, the synchronization information packet may be a private stream
having a stream id value of 0xBD. Furthermore, the synchronization information packet
having a data_alignment_indicator value of 1 may match a start of a payload of a PES
packet.
[0197] Fig. 24 illustrates a syntax of a broadcast stream packet including synchronization
information of media content transmitted via an IP network according to the MPEG-DASH
standard.
[0198] In the example of Fig. 24, media content is transmitted according to the MPEG-DASH
standard. Therefore, the synchronization information packet is referred to as a DASHTime
packet.
[0199] The DASHTime packet includes a DASHTimePacket_identifier field, an mpd_force_update
field, a period_switch_timer field, a presentation_time field, and a period_id field.
[0200] The DASHTimePacket_identifier field indicates an identifier for identifying the DASHTime
packet.
[0201] The mpd_force_update field indicates that the MPD is required to be updated with
respect to the synchronization information packet prior to presentation time synchronization.
[0202] The period_switch_timer field indicates a remaining time from the broadcast stream
reference time of the DASHTime packet to a start time of the period element of the
MPD to be synchronized. In the case where a value of the switch_timer field is 0,
the switch_timer field may indicate that a period identified by the period_id field
is currently active and media content is required to be synchronized immediately.
In the case where the value of the switch_timer field is not 0, the switch_timer field
may indicate that the period identified by the period_id field is not currently active.
[0203] The presentation_time field indicates an own presentation time of media content transmitted
via an IP network which is to be synchronized with broadcast content. Here, a synchronized
presentation time of broadcast content received before a new DASHTime packet is received
may be obtained using a value of the presentation_time field. This operation is performed
using the following equation.

[0204] In the equation, MPT denotes the synchronized presentation time of broadcast content
received before a new DASHTime packet is received, PT0 denotes the broadcast stream
reference time of the synchronization information packet, PT denotes the broadcast
stream reference time of the broadcast content received before the new DASHTime packet
is received, RC denotes the reference clock of a broadcast stream, presentation_time
denotes the own presentation time of media content which is a value of the presentation_time
field, TimeOffset denotes a media content presentation start time of a presentation
interval of the media content to be synchronized by the DASHTime packet, and SegmentBase.timescale
denotes a value of the timescale element of the MPD.
[0205] The period_id field enables identification of the period element of the MPD, and
includes an ID of the period element of the MPD and a URL of the MPD. The broadcast
receiving device 100 may identify media content to be synchronized and the period
element that is a presentation interval of the media content, using the period_id
field.
[0206] In the case where synchronization information is transmitted via an additional synchronization
information packet as described above with reference to Fig. 24, the broadcast receiving
device 100 is required to receive an additional packet to synchronize media content
with broadcast content. In general, to overcome this limitation, a header of a packet
including broadcast content such as a video or an audio includes a broadcast content
reference time for synchronization between elementary streams. For example, the header
of a packet of a broadcast stream according to the MPEG-2 TS standard includes a PTS.
Therefore, if the synchronization information is added to the header of a packet including
broadcast content such as a video or an audio so as to be transmitted, the broadcast
receiving device 100 may efficiently synchronize media content with broadcast content.
This configuration will be described in detail with reference to Figs. 25 and 26.
[0207] The header of a packet including broadcast content such as a video or an audio may
include a presentation_time element indicating an own presentation time of media content
to be synchronized with the broadcast content. Furthermore, the header may include
a period_id element indicating an identifier of a presentation interval of media content
to be synchronized. The header may also include an id element indicating that information
for synchronization between media content and broadcast content is included.
[0208] Fig. 25 illustrates a syntax of the synchronization information added to the header
of a packet including broadcast content such as a video or an audio according to an
embodiment.
[0209] Fig. 26 illustrates the syntax of the synchronization information added to the header
of a packet including broadcast content such as a video or an audio according to another
embodiment.
[0210] In the examples of Figs. 25 and 26, the header of a packet including broadcast content
such as a video or an audio includes information for synchronization with media content
transmitted according to the MPEG-DASH standard. Here, the information for synchronization
is referred to as DASHTime_private_data. The DASHTime_private_data includes a presentation_time
field and a period_id field. The presentation_time field indicates an own presentation
time of media content synchronized with broadcast content. The period_id field enables
identification of the period element of the MPD, and includes an ID of the period
element of the MPD and a URL of the MPD. In the example of Fig. 26, the DASHTime_private_data
further includes an ID element indicating that the DASHTime_private_data includes
information for synchronization between media content and broadcast content.
[0211] Fig. 27 is a flowchart illustrating an operation of synchronizing, by a broadcast
receiving device, broadcast content with media content according to an embodiment.
[0212] The broadcast receiving device 100 receives a broadcast stream via the broadcast
receiving unit 150 (S1101).
[0213] The broadcast receiving device 100 extracts, via the control unit 110, synchronization
information for synchronizing broadcast content with media content transmitted via
an IP network (S1103). In a specific embodiment, the broadcast receiving device 100
may extract, via the control unit 110, the synchronization information from a synchronization
information packet. In another specific embodiment, the broadcast receiving device
100 may extract, via the control unit 110, the synchronization information from the
header of a packet including broadcast content such as a video or an audio.
[0214] The broadcast receiving device 100 receives media content via the IP transmitting/receiving
unit 130 (S1105).
[0215] The broadcast receiving device 100 synchronizes, via the control unit 110, the media
content with the broadcast content.
[0216] In the case where the broadcast receiving device 100 receives not only broadcast
content but also media content via an IP network, the broadcast receiving device 100
may be required to access the broadcast content on the basis of presentation information
of the media content so as to improve efficiency of interworking between the broadcast
content and the media content.
[0217] Described below with reference to Figs. 28 to 30 is a method of adding information
on broadcast content to the media content presentation information to transmit the
information on broadcast content.
[0218] The media content presentation information may include information for identifying
broadcast content so that the broadcast receiving device 100 may access the broadcast
content on the basis of the media content presentation information. In detail, the
media content presentation information may include an identifier for identifying a
broadcast stream including the broadcast content. For example, in the case where the
broadcast content is transmitted according to the MPEG-2 TS standard, the media content
presentation information may include a TSID. Furthermore, the media content presentation
information may include an identifier for identifying a broadcasting service including
the broadcast content. For example, in the case where the broadcast content is transmitted
according to the MPEG-2 TS standard, the media content presentation information may
include a program number. In the case where the broadcast content is transmitted according
to the ATSC standard, the media content presentation information may include a source
id and a channel number of a virtual channel. In the case where the broadcast content
is transmitted according to a DVB standard, the media content presentation information
may include a service id. Furthermore, the media content presentation information
may include an identifier for identifying a packet including the broadcast content.
For example, in the case where the broadcast content is transmitted according to the
MPEG-2 TS standard, the media content presentation information may include a PID.
[0219] In a specific embodiment, the media content presentation information may include
an identifier obtained by combining the identifier for identifying a broadcast stream
including broadcast content, the identifier for identifying a broadcast service including
broadcast content, and the identifier for identifying a packet including broadcast
content.
[0220] Fig. 28 illustrates a format of information for identifying broadcast content included
in the media content presentation information in the case where the broadcast content
is transmitted according to the ATSC standard.
[0221] Fig. 29 illustrates an example of the MPD of MPEG-DASH including information for
identifying broadcast content transmitted according to the ATSC standard.
[0222] In the examples of Figs. 28 and 29, the information for identifying broadcast content
may be a combination of a TSID for identifying a transport stream, an SSID for identifying
a source of an elementary stream, and a PID for identifying a packet.
[0223] The information for identifying broadcast content may be a combination of a TSID
for identifying a transport stream, a PNUM for identifying a program stream, and a
PID for identifying a packet.
[0224] The information for identifying broadcast content may be a combination of a TSID
for identifying a transport stream, a CHNUM for identifying a virtual stream, and
a PID for identifying a packet. Here, the CHUM for identifying a virtual channel may
have a format in which a major channel number and a minor channel number are connected
to each other by "-".
[0225] Fig. 30 is a flowchart illustrating an operation of receiving, by a broadcast receiving
device, broadcast content on the basis of the media content presentation information.
[0226] The broadcast receiving device 100 receives the media content presentation information
via the IP transmitting/receiving unit 130 (S1303).
[0227] The broadcast receiving device 100 extracts, via the control unit 110, information
for identifying broadcast content (S1303).
[0228] The broadcast receiving device 100 receives, via the broadcast receiving unit 150
and the control unit 110, the broadcast content on the basis of the information for
identifying the broadcast content (S1305). In detail, the broadcast receiving device
100 receives a broadcast stream via the broadcast receiving unit 150. Here, the broadcast
receiving device 100 may receive the broadcast stream on the basis of a broadcast
stream identifier included in the information for identifying the broadcast content.
The broadcast receiving device 100 extracts, from the broadcast stream, the broadcast
content on the basis of the information for identifying the broadcast content. Here,
the broadcast receiving device 100 may extract, from the broadcast stream, the broadcast
content on the basis of a broadcast service identifier included in the information
for identifying the broadcast content.
[0229] Described below with reference to Figs. 31 and 32 is a method of receiving, by a
broadcast receiving device, the media content presentation information via a broadcasting
network in relation to the above-mentioned examples. Furthermore, an operation of
synchronizing, by the broadcast receiving device, broadcast content with media content
will be described in detail.
[0230] Fig. 31 is a block diagram illustrating that the broadcast receiving device receives
the MPD of MPEG-DASH via a broadcasting network for transmitting a broadcast stream
according to the MPEG-2 TS standard.
[0231] According to the embodiment of Fig. 31, the control unit 110 of the broadcast receiving
device 100 includes a PSI parser, a TS filter, a TS/PES depacketizer, and a decoder.
[0232] The TS filter extracts, from a broadcast stream, a packet having a specific PID.
[0233] The PSI parser parses a PSI table such as a program association table (PAT) or a
program map table (PMT) to extract signaling information. In a specific example, the
PSI parser may extract an MPD_descriptor included in the PMT.
[0234] The TS/PES depacketizer extracts payload data from a TS/PES packet. In a specific
embodiment, in the case where the MPD is transmitted as an additional information
table in a broadcast stream, the TS/PES depacketizer may extract the MPD from the
additional information table on the basis of the MPD_descriptor. In detail, the TS/PES
depacketizer may extract the MPD from an information table included in a packet corresponding
to a PID included in the MPD_descriptor. Furthermore, the TS/PES depacketizer extracts
a video elementary stream and an audio elementary stream from the TS/PES packet.
[0235] The decoder decodes a video or an audio.
[0236] Fig. 32 is a block diagram illustrating that the broadcast receiving device synchronizes
broadcast content of a broadcast stream transmitted according to the MPEG-2 TS standard
with media content transmitted via an IP network.
[0237] According to the embodiment of Fig. 32, the control unit 110 of the broadcast receiving
device 100 includes a TS/PES depacketizer and a decoder.
[0238] The TS/PES depacketizer extracts payload data from a TS/PES packet. In a specific
example, in the case where the MPD is transmitted as an additional information table
in a broadcast stream, the MPD may be extracted from the additional information table
on the basis of the MPD_descriptor. In detail, the MPD may be extracted from an information
table included in a packet corresponding to a PID included in the MPD_descriptor.
Furthermore, the TS/PES depacketizer extracts, from the TS/PES packet, synchronization
information for synchronizing media content with broadcast content. Here, the synchronization
information may include a presentation time of media content, an identifier for identifying
a period element of the MPD, and an MPD URL. Furthermore, the TS/PES depacketizer
extracts a video elementary stream and an audio elementary stream from the TS/PES
packet.
[0239] The IP transmitting/receiving unit 130 receives media content from a CDN server on
the basis of the MPD.
[0240] The decoder synchronizes the received media content on the basis of the synchronization
information and decodes the media content.
[0241] The above-mentioned features, structures or effects are included in at least one
embodiment, but are not necessarily limited to only one embodiment. Furthermore, the
features, structures or effects of each embodiment may be combined or modified by
those skilled in the art so as to be implemented for other embodiments. Therefore,
such combination or modification should be construed as falling within the scope of
the present disclosure.
[0242] Although embodiments have been described with reference to a number of illustrative
embodiments thereof, it should be understood that numerous other modifications and
embodiments can be devised by those skilled in the art that will fall within the spirit
and scope of the principles of this disclosure. More particularly, various variations
and modifications are possible in the component parts and/or arrangements of the subject
combination arrangement within the scope of the disclosure, the drawings and the appended
claims. In addition to variations and modifications in the component parts and/or
arrangements, alternative uses will also be apparent to those skilled in the art.