# Patent

## Title
Broadcast service transmitting method, broadcast service receiving method and broadcast service receiving apparatus

## Abstract

A method of receiving a broadcast service is provided. The method includes receiving uncompressed audio or video content, obtaining information regarding a channel of the uncompressed audio or video content on the basis of a part of the uncompressed audio or video content, and obtaining content and trigger information for the broadcast service by using the obtained information.

## Background
This application is a 35 USC §371 National Stage entry of International Application No. PCT/KR2011/009564 filed Dec. 13, 2011, and claims priority of U.S. provisional Application No. 61/427,200 filed Dec. 26, 2010 and 61/525,836 filed Aug. 21, 2011, which are hereby incorporated by reference in its entirety.


TECHNICAL FIELD
The present disclosure relates to a broadcast service transmitting method, broadcasting service receiving method and broadcast service receiving apparatus.
BACKGROUND ART
A digital television (DTV) is now presented to offer various services in addition to a television (TV)'s original function such as playing video and audio. For example, broadcasting information such as Electronic Program Guide (EPG) may be provided to a user, and also, broadcasting services from at least two channels may be simultaneously provided to a user. Especially, since a receiving system of the receiving system includes a large capacity of a storage device, and is connected to a data communication channel and the internet through which two-way communication is available, more services become accessible through broadcast signals. Additionally, since services offered through broadcast signals become more diversified, needs for utilizing the diversified services accurately is increased.
DISCLOSURE OF THE INVENTION
Technical Problem
Embodiments provide a broadcasting service receiving method and a receiving apparatus using the same, which efficiently provide an enhanced service according to a broadcast receiving environment of the receiving apparatus.
Technical Solution
In one embodiment, a method of receiving a broadcast service, the method includes: receiving uncompressed audio or video content; obtaining information regarding a channel of the un-compressed audio or video content on the basis of a part of the un-compressed audio or video content; and obtaining content and trigger information for the broadcast service by using the obtained information.
In another embodiment, a receiving apparatus includes: a receiving unit receiving un-compressed audio or video content; and a service management unit obtaining information regarding a channel of the un-compressed audio or video content on the basis of a part of the un-compressed audio or video content and obtaining content and trigger information for the broadcast service by using the obtained information, wherein the information regarding the channel comprises address information of a server that is connected to obtain at least one of channel identification information, timestamp information, and the content and trigger information.
Advantageous Effects
According to an embodiment, broadcasting service using a content downloaded through a non-real time service can be linked with a real-time broadcasting service so as to provide the accurate timing.
According to another embodiment, a receiver receiving uncompressed main audio-visual (AV) content can obtain content and trigger information for a broadcasting service by using automatic content recognition (ACR) mechanism, and accordingly can provide a broadcasting company led service regardless of a broadcast receiving environment of the receiver.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a conceptual diagram illustrating how RT 10 service and NRT service are provided.
FIG. 2 is a view illustrating a structure of NRT service according to an embodiment.
FIG. 3 is a view illustrating a protocol stack for NRT service according to an embodiment.
FIG. 4 is view illustrating one example of the protocol stack for mobile NRT service.
FIG. 5 is a view illustrating a bit stream section of a TVCT table section (VCT) according to an embodiment.
FIGS. 6 and 7 are views illustrating how to define a value of a service type field according to an embodiment.
FIG. 8 is view of data service table section) for identifying an application of NRT service and bit stream syntax of data service table bytes in a DST section.
FIG. 9 is a view illustrating a method of receiving and providing NRT service in a receiving system by using ATSC A or 90 standard for transmitting data broadcasting stream and ATSC A or 92 standard for transmitting IP multicast stream.
FIG. 10 is a view illustrating a method of 30 receiving an NRT service by using a DSM-CC addressable section data according to another embodiment.
FIG. 11 is a view illustrating a method of signaling a DSM-CC addressable section data by using VCT according to another embodiment.
FIGS. 12 and 13 are views illustrating a bit stream syntax of NST according to an embodiment.
FIG. 14 is a view illustrating a bit stream syntax of NRT_component_descriptor (MH_component_descriptor) according to an embodiment.
FIG. 15 is a view illustrating a bit stream syntax of NRT component descriptor including NRT_component_data according to an embodiment.
FIG. 16 is a view illustrating a bit stream syntax of NRT-IT section for signaling NRT application according to an embodiment.
FIG. 17 is a view illustrating a syntax structure of bit stream for NRT section (NRT_content_table_section) according to an embodiment.
FIG. 18 is a view illustrating a bit stream syntax structure of an SMT session providing signaling information on NRT service data according to an embodiment.
FIG. 19 is a view illustrating an FDT schema for mapping a file and content_id according to an embodiment.
FIG. 20 is a view illustrating an FDT schema for mapping a file and content_id according to another embodiment.
FIG. 21 is a flowchart illustrating an operation of a receiver according to an embodiment.
FIGS. 22 and 23 are views illustrating a receiving system receiving, storing, and playing an NRT content for NRT service according to another embodiment.
FIG. 24 is a flowchart illustrating a method of a receiver to receive and provide NRT service according to an embodiment.
FIG. 25 is a view illustrating a bit stream syntax of a trigger according to an embodiment.
FIG. 26 is a view illustrating a PES structure according to a synchronized data stream method including a trigger according to an embodiment.
FIG. 27 is a view illustrating a synchronized data packet structure of PES payload for transmitting trigger as bit stream syntax according to an embodiment.
FIG. 28 is a view illustrating a content type descriptor structure in tap( ) on DST according to an embodiment
FIG. 29 is a view illustrating a syntax of PMT and service identifier descriptor according to an embodiment.
FIG. 30 is a view illustrating a trigger stream descriptor according to an embodiment.
FIG. 31 is a view of AIT according to an embodiment.
FIG. 32 is a view of STT according to an embodiment.
FIG. 33 is a block diagram illustrating a transmitter for transmitting TDO and a trigger according to an embodiment.
FIG. 34 is a block diagram illustrating a receiver 300 for receiving TDO and a trigger according to an embodiment.
FIG. 35 is a flowchart illustrating a trigger transmitting method according to an embodiment.
FIG. 36 is a flowchart illustrating an operation of a receiver 300 according to an embodiment.
FIG. 37 is a flowchart illustrating a trigger receiving method by using a trigger table according to an embodiment.
FIG. 38 is a flowchart illustrating an operation of a receiver when trigger signaling information and trigger are transmitted using DST according to an embodiment.
FIG. 39 is a flowchart illustrating an operation of a receiver when a trigger is transmitted using a trigger stream descriptor according to an embodiment.
FIG. 40 is a flowchart illustrating an operation of a receiver when a trigger is transmitted using a stream type according to an embodiment.
FIG. 41 is a flowchart illustrating an operation of a receiver when a trigger is transmitted using AIT according to an embodiment.
FIG. 42 is a flowchart illustrating an operation of a receiver when a trigger is transmitted using STT according to an embodiment.
FIG. 43 is a view illustrating a bit stream syntax of a trigger formed according to another embodiment.
FIG. 44 is a view illustrating an embodiment of a method of setting deleting time information.
FIG. 45 is a flowchart illustrating a TDO deleting method according to an embodiment.
FIG. 46 is a block diagram illustrating the network topology according to the embodiment.
FIG. 47 is a block diagram illustrating a watermark based network topology according to an embodiment.
FIG. 48 is a ladder diagram illustrating a data flow in a watermark based network topology according to an embodiment.
FIG. 49 is a view illustrating a watermark based content recognition timing according to an embodiment.
FIG. 50 is a block diagram illustrating a fingerprint based network topology according to an embodiment.
FIG. 51 is a ladder diagram illustrating a data flow in a fingerprint based network topology according to an embodiment.
FIG. 52 is a view illustrating an XML schema diagram of ACR-Resulttype containing a query result according to an embodiment.
FIG. 53 is a block diagram illustrating a watermark and fingerprint based network topology according to an embodiment.
FIG. 54 is a ladder diagram illustrating a data flow in a watermark and fingerprint based network topology according to an embodiment.
FIG. 55 is a block diagram illustrating a configuration of a receiving apparatus according to another embodiment.



MODE FOR CARRYING OUT THE INVENTION
Preferred embodiments of the present invention will be described below in more detail with reference to the accompanying drawings. The configurations and operations of the present invention shown in and described with the accompanying drawings are explained as at least one example, and the technical idea of the present invention and its core configurations and operations are not limited thereby.
The terms used in the present invention are selected as currently used general terms if possible in the consideration of functions of the present invention but could vary according to intentions or conventions of those in the art or the advent of new technology. In certain cases, there are terms that are selected by an applicant arbitrarily, and in such a case, their meanings will be described in more detail in the specification. Accordingly, the terms used in the present invention should be defined on the basis of the meanings of the terms and contents over the present invention not the simple names of the terms.
Moreover, among the terms in the present invention, a real time (RT) service literally means a service in real time. That is, the service is time-restricted. In contrast, a non-real time (NRT) service is a service in NRT other than the RT service. That is, the NRT service is not restricted by time. Furthermore, data for NRT service is called NRT service data.
A broadcast receiver according to the present invention may receive NRT service through a medium such as a terrestrial wave, a cable, and the internet.
The NRT service may be stored in a storage medium of the broadcast receiver, and then may be displayed on a display device according to a predetermined time or at the user's request. The NRT service is received in a file format, and is stored in a storage medium according an embodiment. The storage medium may be an HDD embedded in the broadcast receiver according to an embodiment. As another example, the storage medium may be a Universal Serial Bus (USB) memory or an external HDD, which is connected to the broadcast receiving system.
Signaling information is necessary to receive files constituting the NRT service, store them in a storage medium, and provide a service to a user. The present invention may designate the above signaling information as NRT service signaling information or NRT service signaling data.
The NRT service includes Fixed NRT service and Mobile NRT service according to a method of obtaining IP datagram including NRT service signaling data. Especially, the Fixed NRT service is provided to a fixed broadcast receiver, and the Mobile NRT service is provided to a mobile broadcast receiver.
TDO Content: 10FPDTV423
FIG. 1 is a conceptual diagram illustrating how RT service and NRT service are provided.
A broadcasting station transmits the RT service according to a traditional way, that is, like current terrestrial broadcasting (or mobile broadcasting). At this point, the broadcasting station transmits the RT service, and then, by using a remaining bandwidth during the transmission or an exclusive bandwidth, may provide the NRT service. That is, the RT service and NRT service are transmitted through the same or different channel. Accordingly, in order for a broadcast receiver to separate the RT service and the NRT service and store the separated NRT service in order to provide it to a user if necessary, service signaling information (or NRT service signaling data) is required. The NRT service signaling information (or NRT service signaling data) will be described in more detail later.
For example, a broadcasting station transmits broadcasting service data in real time and transmits news clip, weather information, advertisements, and Push VOD in non-real time. Additionally, the NRT service may be specific scenes, detail information of a specific program, and preview in real-time broadcasting stream in addition to news clip, weather information, advertisements, and Push VOD.
A typical broadcast receiver (i.e., a legacy device) may receive and process the RT service but may not receive and process the NRT service. That is, the typical broadcast receiver (i.e., a legacy device) is not influenced, in principle, by an NRT stream in a channel broadcasting RT service. That is, even when receiving NRT service, the typical broadcast receiver cannot process the received NRT service because it does not include a unit for processing it properly.
On the contrary, the broadcast receiver (i.e., an NRT device) of the present invention receives NRT service combined with RT service and properly processes the NRT service, so that it provides more various functions to a viewer than a typical broadcast receiver.
FIG. 2 is a view illustrating a structure of NRT service according to an embodiment.
The NRT service includes at least one content item (or content or NRT content) as shown in FIG. 2, and the content item includes at least one file according to an embodiment. A file and object have the same meaning in the present invention.
The content item is a minimum unit playable independently. For example, news is provided in NRT. If the news includes business news, political news, and lift news, it may be NRT service, and each may be designated as a content item. Moreover, each of the business news, political news, and life news may include at least one file.
At this point, the NRT service may be transmitted in an MPEG-2 transport stream (TS) packet format through the same broadcasting channel as the RT service or an exclusive broadcasting channel. In this case, in order to identify the NRT service, a unique PID may be allocated to the TS packet of the NRT service data and then transmitted. According to an embodiment of the present invention, IP based NRT service data is packetized into an MPEG-2 TS packet and then transmitted.
At this point, NRT service signaling data necessary for receiving the NRT service data is transmitted through an NRT service signaling channel. The NRT service signaling channel is transmitted through a specific IP stream on an IP layer, and at this point, this specific IP stream may be packetized into an MPEG-2 TS packet and then transmitted. The NRT service signaling data transmitted through the NRT service signaling channel may include at least one of a Service Map Table (SMT), an NRT Service Table (NST), an NRT Content Table (NCT), an NRT Information Table (NRT-IT), and a Text Fragment Table (TFT). The NST or SMT provides access information on at least one NRT service operating on an IP layer, or the content items or files constituting the NRT service. The NRT-IT or NCT provides access information on the content items or files constituting the NRT service.
Additionally, NRT service signaling data including SMT (or NST) and NRT-IT (or NCT) may be included in a PSIP table on MPEG-2 TS or may be transmitted through an NRT service signaling channel on an IP layer in a virtual channel. Moreover, a plurality of NRT service data may be provided through one virtual channel.
The NRT-IT includes information describing a content downloadable to be stored in a receiving device. Information provided to the NRT-IT may include a content title (for example, the name of a downloadable program), available time for downloading content, content recommendation, availability of caption service, content identification, and other metadata.
Additionally, the TFT provides detailed description on a content item or service. The TFT may include a data structure supporting multi languages and, as a result, may represent detailed descriptions (e.g., each string corresponds to one language) in different languages. The text fragment table may be included in private sections having a table_id value (TBD) and may be identified by TFT_id. A TFT section may be included IP packets in a service signaling channel, and a multicast IP address (224.0.23.60) and a port (4937) may be allocated to the service signaling channel by IANA.
First, a receiver may identify whether a corresponding service is the NRT service with reference to a service_category field in the SMT, for example. Additionally, the receiver may uniquely identify the NRT service from the SMT through an NRT_service_id field.
Additionally, the NRT service may include a plurality of content items. The receiver may identify an NRT content item through a content_id field in the NCT or NRT-IT. In addition, the NRT content item and NRT service may be connected to each other by matching the NRT_channel_id field of the NCT to the NRT_service_id field.
Moreover, the NRT service may be transmitted through a FLUTE session and the receiver may extract FDT information from the FLUTE session. Then, content_id in the extracted FDT information is mapped into content_id of NCT or OMA-BCAST SG in order to confirm and receive the NRT service content that a user selects. If the mapping method is described briefly, for example, the receiver identifies each file constituting the NRT content item through the TOI and Content-Location fields in the FDT in the FLUTE session. Each TOI or the Content-Location and content item maps the content_ID of the FDT into the content_id field of the NCT or the content_id field of the OMA BCAST SG, so as to confirm and receive the NRT service content.
FIG. 3 is a view illustrating a protocol stack for NRT service according to an embodiment.
For Fixed NRT service, the NRT service of a file format is IP-packetized in an IP layer, and then, is transmitted in an MPEG-2 TS format through a specific channel.
Through an MPEG-2 based Program Specific Information (PSI) or Program and System Information Protocol (PSIP) table, for example, a VCT, it is determined whether there is NRT service in a virtual channel and identification information of NRT service is signaled.
According to an embodiment, the NRT service signaling channel, which transmits NRT service signaling data signaling the access information of the IP based NRT service, is IP packetized into a specific IP stream in the IP layer, and then, is transmitted in an MPEG-2 TS format.
That is, a broadcasting station packetizes the NRT content item or files according to a file transfer protocol method as shown in FIG. 3, and then, packetizes the packetized NRT content item or files in an Asynchronous Layered Coding (ALC) or Layered Coding Transport (LCT) method. Then, the packetized ALC or LCT data are packetized according to a UDP method. Then, the packetized UDP data is packetized according to the IP method again, and then, becomes IP data. Here, the IP data may include a File Description Table (FDT) having information on a File Delivery over Unidirectional Transport (FLUTE) session. The packetized IP data may be designated as IP datagram for convenience of description in the present invention.
Additionally, the IP datagram of NRT service is encapsulated in an addressable section structure and is packetized again in an MPET-2 TS format. That is, one addressable section structure has a section header and CRC checksum, which are added to one IP datagram. The format of the addressable section structure is matched to a Digital Storage Media Command and Control (DSM-CC) section format for private data transmission in terms of a structure. Accordingly, the addressable section may be designated as a DSM-CC addressable section.
Moreover, NRT service signaling data including at least one of SMT (or NST) and NRT-IT (or NCT) necessary for receiving NRT content or files may be transmitted through an NRT service signaling channel on an IP layer. Accordingly, the NRT service signaling data may be packetized according to an IP method in order to transmit it through the NRT service signaling channel on an IP layer. The NRT service signaling channel is encapsulated in the IP datagram having a well-known IP address and is multi-casted according to an embodiment.
Additionally, the NRT service signaling data may be included in Program Specific Information (PSI) or Program and System Information Protocol (PSIP) table section data and then transmitted. Moreover, the PSI table may include a Program Map Table (PMT) and a Program Association Table (PAT). The PSIP table may include a Virtual Channel Table (VCT), a Terrestrial Virtual Channel Table (TVCT), a Cable Virtual Channel Table (CVCT), a System Time Table (STT), a Rating Region Table (RRT), an Extended Text Table (ETT), a Direct Channel Change Table (DCCT), a Direct Channel Change Selection Code Table (DCCSCT), an Event Information Table (EIT), and a Master Guide Table (MGT).
Furthermore, as data for digital rights management and encryption of broadcasting service to protect the NRT service from illegal distribution and reproduction, BroadCast Services Enabler Suite Digital Rights Management (BCAST DRM) suggested by Open Mobile Alliance (OMA) may be used.
Moreover, the above mentioned Program Specific Information (PSI), Program and System Information Protocol (PSIP) table section data, DSM-CC addressable section data, and OMA BCAST DRM data are divided by a 184 byte unit, and then, a 4 byte MPEG header is added to each 184 bytes in order to obtain a 188 byte MPEG-2 TS packet. At this point, a value allocated to the PID of the MPEG header is a unique value identifying a TS packet for transmitting the NRT service and NRT service signaling channel.
MPEG-2 TS packets may be modulated in a predetermined transmission method in a physical layer, for example, an 8-VSB transmission method, and then, may be transmitted to a receiving system.
Moreover, FIG. 4 is a view illustrating a protocol stack for NRT service according to another embodiment.
FIG. 4 is view illustrating one example of the protocol stack for mobile NRT service. As shown in FIG. 4, an adaption layer is included between an IP layer and a physical layer. As a result, without using an MPEG-2 TS format, the IP datagram of mobile service data and IP datagram of signaling information may be transmitted.
That is, a broadcasting station packetizes the NRT content or files according to a file transfer protocol method as shown in FIG. 4, and then, packetizes them according to an Asynchronous Layered Coding (ALC) or Layered Coding Transport (LCT) method. Then, the packetized ALC or LCT data are packetized according to a UDP method. Then, the packetized ALC or LCT or UDP data is packetized again according to the IP method and becomes ALC or LCT or UDP or IP data. The packetized ALC or LCT or UDP or IP data may be designated as IP datagram for convenience of description in the present invention. At this point, OMA BCAST SG information undergoes the same process as the NRT content or file to constitute IP datagram.
Additionally, when NRT service signaling information (for example, SMT) necessary for receiving the NRT content or files is transmitted through a service signaling channel, the service signaling channel is packetized according to a User Datagram protocol (UDP) method, and the packetized UDP data is packetized again according to the IP method to become UDP or IP data. The UDP or IP data may be designated as IP datagram for convenience of description in the present invention. At the time, the service signaling channel is encapsulated in the IP datagram including Well-known IP destination address and well-known destination UDP port number, and is multi-casted according to an embodiment.
In addition, in relation to OMA BCAST DRM for service protection, a UDP header and an IP header are sequentially added to constitute one IP datagram.
The IP datagram of the NRT service, NRT service signaling channel, and mobile service data are collected in an adaption layer to generate a RS frame. The RS frame may include IP datagram of OMA BCAST SG.
The length (i.e., the number of rows) of a column in the RS frame is set by 187 bytes, and the length (i.e., the number of columns) of a row is N bytes (N may vary according to signaling information such as a transmission parameter (or TPC data).
The RS frame is modulated in a predetermined transmission method in a mobile physical layer (for example, VSB transmission method) and then is transmitted to a receiving system.
Moreover, whether the NRT service is transmitted is signaled through a PSI or PSIP table. As one example, whether the NRT service is transmitted is signaled to the VCT or TVCT.
FIG. 5 is a view illustrating a bit stream section of a TVCT table section (VCT) according to an embodiment.
Referring to FIG. 5, the TVCT table section has a table form of an MPEG-2 private section as one example, but is not limited thereto.
When the VCT and PID of the audio or video are parsed and then transmitted through the TVCT, the packet identification (PID) information may be obtained.
Accordingly, the TVCT table section includes a header, a body, and a trailer. A header part ranges from a table_id field to a protocol_version field. A transport_stream_id field is a 16 bit field and represents an MPEG-2 TS ID in a program association table (PAT) defined by a PID value of 0 for multiplexing. In a body part, a num_channels_in_section field is an 8 bit field and represents the number of virtual channels in a VCT section. Lastly, a trailer part includes a CRC_32 field.
First, the header part will be described as follows.
A table_id field (8 bits) is set with 0xC8 and identifies that a corresponding table section is a table section constituting TVCT.
A section_syntax_indicator field (1 bit) is set with 1 and represents that the section follows a general section syntax.
A private_indicator field (1 bit) is set with 1.
A section_length field (12 bits) describes that the number of bits remaining in the section to the last of the section from immediately after the section_length field. The value of the section_length field may not be greater than 1021.
A table_id_extension field (16 bits) may be set with 0x000.
A version_number field (5 bits) may have 0 and means the version number of VCT.
A current_next_indicator field (1 bit) represents that a corresponding table section is applicable currently if set with 1.
A section_number field (8 bits) indicates the number of corresponding table section among TVCT sections. In a first section of TVCT, section_number should be set with 0x00.
A last_section_number field (8 bits) means the table section of the last and highest number among TVCT sections.
A protocol_version field (8 bits) is a function that allows a table type delivering parameters having a different structure than one defined in a current protocol. Today, only one valid value of protocol_version is 0. The protocol_version having other than 0 may be used for the future version of the standard in order to recognize another table having a different structure.
Next, the body part will be described.
A num_channels_in_section field (8 bits) designates the numbers of virtual channels in the VCT section. The numbers are restricted by a table section length.
A short_name field (16 bits) represents the name of the virtual channel using 16 bit code value from 1 to 7 sequentially.
A major_channel_number field (10 bits) represents a major channel number related to a virtual channel defined by repetition in a “for” loop. Each virtual channel should relate to a major channel number and a minor channel number. The major channel number together with the minor channel number serve as a reference number of a virtual channel of a user.
A minor_channel_number field (10 bits) represent minor or sub channel numbers ranging from ‘0’ to ‘999’. This field together with major_channel_number serves as the second of the number or a channel number of second part representing the right portion. The minor_channel_number is set with 0 if service_type is an analog television. When the service_type is an ATSC_digital_television or an ATSC_audio_only, it uses a minor number ranging from 1 to 99. A value of the minor_channel_number does not overlap that of the major_channel_number in a TVCT.
A modulation_mode field (8 bits) represents a modulation mode for carrier related to a virtual channel.
A carrier_frequnecy field (32 bits) has a recommendation value of 0. Although the field is used to identify a carrier frequency, it is not recommended.
A channel_TSID field (16 bits) is an unsigned integer field representing an MPEG-2 TS ID related to a TS containing an MPEG-2 program, which is reference by a virtual channel in a range from ‘0x0000’ to ‘0xFFFF’.
A program_number field (16 bits) identifies an unsigned integer number related to a virtual channel defined in an MPEG-2 program association table (PAT) and a TS program map table (PMT). A virtual channel corresponding to analog service includes program_number of ‘0xFFFF’.
An ETM_location field (2 bits) describes the existence and location of an extended text message (ETM).
An access_controlled field (1 bit) indicates an access to events related to a virtual channel is controlled once it is set. If the flag is set with 0, an event access is not restricted.
A hidden field (1 bit) indicates that a user by a direct entry of a virtual channel number cannot access a virtual channel once it is set. A hidden virtual channel is omitted when a user surfs a channel, and is shown when the user accesses undefined or direct channel entry. A typical application of a hidden channel is a test signal and NVOD service. The hidden channel and its events may be shown on an EPG display according to a state of a hide_guide bit.
A hidden_guide field allows a virtual channel and its events to be displayed on an EPG display once it is set with 0 for a hidden channel. The bit is not related to a channel having no hidden bit set and thus non-hidden channels and their events are always displayed on an EPG display regardless of a state of a hide_guide bit. A typical application of a hidden channel, in which a hidden_guide bit set is set with 1, is a test signal and service easily obtainable through an application level pointer.
A service_type field (6 bits) represents a type of service transmitted from a virtual channel. FIGS. 6 and 7 are views illustrating how to define a value of a service_type field according to an embodiment. According to an embodiment, a service_type value (i.e., ‘0x04’) shown in FIG. 6 means that service_type is ATSC_data_only_service and NRT service is transmitted through a virtual channel. According to another embodiment, a service_type value (i.e., ‘0x08’) shown in FIG. 7 means that service_type is ATSC_nrt_service and a virtual channel provides NRT service satisfying the ATSC standard.
A source_id field (16 bits) represents the source of a program related to a virtual channel.
A descriptors_length field represents the total length (byte unit) of a descriptor for the following virtual channel.
A descriptor( ) field includes at least zero descriptor.
An additional_descriptors_length field represents a total length (byte unit) of the following VCT descriptor.
Lastly, in relation to the trailer part, a CRC_32 field is a 32 bit field and includes a cyclic redundancy check (CRC) value, which ensures zero output from registers of a decoder defined in an MPEG-2 system after processing an entire STT section.
FIG. 8 is view of data_service_table_section) for identifying an application of NRT service and bit stream syntax of data_service_table_bytes in a DST section. A broadcasting station NRT service data or NRT service signaling data, satisfying ASTC standard, may be transmitted through the DST table section of FIG. 8.
Hereinafter, semantic of fields including a data_service_table_section structure is as follows.
A table_id field (8 bits) as a field for type identification of a corresponding table section is a table section in which a corresponding table section constitutes DST through this field. For example, a receiver identifies that a corresponding table section is a table section constituting DST if a value of the field is 0XCF.
A section_syntax_indicator field (1 bit) is an indicator defining a section format of DST, and the section format may be short-form syntax (0) of MPEG, for example.
A private_indicator field (1 bit) represents whether the format of a corresponding section follows a private section format and may be set with 1.
A private_section_length field (12 bits) represents a remaining table section length after a corresponding field. Additionally, a value of this field does not exceed ‘0xFFD’.
A table_id_extension field (16 bits) is dependent on a table, and may be a logical part of a table_id field providing a range of the remaining fields.
A version_number field (5 bits) represents the version number of DST.
A current_next_indicator field (1 bit) indicates whether a transmitted DST table section is applicable currently. If the field value is 0, it means that there is no table yet and the next table is valid.
A section_number field (8 bits) represents a section number in sections in which a corresponding table section constitutes a DST table. section_number of the first section in DST is set with ‘0x00’. The section_number is increased by one as the section of DST is increased.
A last_section_number field (8 bits) represents the last section number constituting a DST table, i.e., the highest section_number.
data_service_table_bytes represents a data block constituting DST, and its detailed structure will be described below.
A CRC_32 field is a 32 bit field and includes a cyclic redundancy check (CRC) value, which ensures zero output from registers of a decoder defined in an MPEG-2 system after processing an entire DST section.
Hereinafter, semantic of fields including a data_service_table_bytes structure is as follows.
An sdf_protocol_version field (8 bits) describes the version of a Service Description Framework protocol.
An application_count_in_section field (8 bits) represents the number of applications listed in a DST section.
A compatibility_descriptor( ) field represents that a corresponding structure includes a DSM-CC compatible descriptor. Its purpose is to signal compatible requirements of an application in a receiving platform in order to use a corresponding data service after determining its ability.
An app_id_byte_length field (16 bits) describes the number of bytes used for identifying an application.
An app_id_description field (16 bits) describes the format and semantic of the following application identification bytes. For example, a value of an app_id_description may be defined as Table 1.










TABLE 1







Value
Application Identifier Format









0x0000
DASE Application



0x0000-0x7FFF
ATSC Reserved



0x8000-0xFFFF
User Private










An app_id_byte field (8 bits) represents a byte of an application identifier.
A tap_count field (8 bits) describes the number of Tap( ) structures used for corresponding application.
A protocol_encapsulation field (8 bits) describes a protocol encapsulation type used for transmitting a specific data element referenced by a Tap( ) field. A value of the protocol_encapsulation field is defined as Table 2.










TABLE 2







Value
Encapsulated Protocol









0x00
Not in a MPEG-2 Transport Stream



0x01
Asynchronous non-flow controlled scenario




of the DSM-CC Download protocol




encapsulated in DSM-CC sections



0x02
Non-streaming Synchronized Download




protocol encapsulated in DSM-CC sections



0x03
Asynchronous multiprotocol datagrams in




Addressable Sections using LLC or SNAP




header



0x04
Asynchronous IP datagrams in Addressable




Sections



0x05
Synchronized streaming data encapsulated




in PES



0x06
Synchronous streaming data encapsulated




in PES



0x07
Synchronized streaming multiprotocol




datagrams in PES using LLC or SNAP header



0x08
Synchronous streaming multiprotocol




datagrams in PES using LLC or SNAP header



0x09
Synchronized streaming IP datagrams in




PES



0x0A
Synchronous streaming IP datagrams in PES



0x0B
Proprietary Data Piping



0x0C
SCTE DVS 051 asynchronous protocol [19]



0x0D
Asynchronous carousel scenario of the




DSM-CC Download protocol encapsulated in




DSM-CC sections



0x0E
Reserved for harmonization with another




standard body



0x0F-0x07F
ATSC reserved



0x80-0xFF
User defined










An action_type field (7 bits) represents attribute of data referenced by a Tap( ).
A resource_location field (1 bit) describes a position of an association_tag field matching to an association_tag value listed in the next Tap structure. When a corresponding field is set with 0, association_tag exists in PMT of a current MPEG-2 program. Like this, when the corresponding field is set with 1, a matching association_tag exits in DSM-CC Resource Descriptor in a Network Resources Table of a corresponding data service.
A Tap( ) field may include information on searching a data element of an application state in a communication channel of a lower layer. An association_tag field in a Tap( ) field may include correspondence information between data elements of an application state. A value of an association_tag field in one Tap structure corresponds to a value of an association_tag field of one association tag descriptor in a current PMT. For example, a Tap( ) field may have a specific structure including fields of Table 3.











TABLE 3







Syntax
No. of bits
Format









Tap( ){





tap_id
16
uimsbf



use
16
uimsbf



association_tag
16
uimsbf



selector( )



}










A tap_id field (16 bits) is used by an application to identify data elements. A value of tap_id has a range defined by values of app_id_byte fields related to Tap( ) in DST. A tap_id value is selected by a data service provider. Additionally, the tap_id value may be used for application to deal with a data element.
A Use field (16 bits) is used to specify a communication channel referenced by association_tag.
An association_tag field (16 bits) uniquely identifies one of a DSM-CC resource descriptor listed in a Network Resource Table or data elementary stream listed in PMT. A value of a corresponding field may be identical to an association_tag value of association_tag_descriptor.
A Selector( ) field describes a specific data element available in a communication channel or data elementary stream referenced by the association_tag field. Additionally, the selector structure may indicate a protocol required for a corresponding data element.
A tap_info_length field (16 bits) describes the number of bytes of descriptors in the next of a corresponding field.
A descriptor( ) field may include descriptor information according to a corresponding descriptor format.
An app_info_length field (8 bits) describes the number of bytes of the next descriptors of a corresponding field.
A descriptor( ) field may include descriptor information according to a corresponding descriptor format.
An app_data_length field (16 bits) describes the length of a byte unit of app_data_byte fields.
An app_data_byte (8 bits) field represents input parameters related to application and other private data fields in 1 byte.
A service_info_length field (8 bits) describes the number of byte units of the next descriptor.
A descriptor( ) field may include descriptor information according to a corresponding descriptor format.
A service_private_data_length field (16 bits) describes the length of a byte unit in private fields.
A service_private_data_byte field (8 bits) represents a private field in 1 byte.
FIG. 9 is a view illustrating a method of receiving and providing NRT service in a receiving system by using ATSC A or 90 standard for transmitting data broadcasting stream and ATSC A or 92 standard for transmitting IP multicast stream.
That is, information on stream constituting each virtual channel is signaled to service location descriptor of VCT or ES_loop of PMT. For example, as shown in FIG. 7 or 8, if VCT service type is 0x02 (i.e., digital A or V or Data), 0x04 (i.e., Data only), or 0x08 (i.e., NRT Only service), NRT service stream may be transmitted to the virtual channel. At this point, if 0x95 (i.e., DST transmission) is allocated to a stream_type field value in a service location descriptor (or ES loop of PMT), it means that broadcast is transmitted. If the stream_type field value has no value or is not 0x95, only typical A or V is transmitted. That is, if the stream_type field value in service location descriptor has 0x95, an Elementary_PID field value at this point is a PID value of a Data Service Table (DST). Accordingly, DST may be received through the Elementary_PID.
Through the DST, types of application and detailed information on data broadcasting stream transmitted through the channel may be obtained. The DST is used to identify NRT application (i.e., NRT service).
That is, the App_id_descrption field of DST defines the format and interpretation of the following application identification bytes. According to an embodiment, ‘0x0003’ is allocated to the App_id_descrption field to identify NRT application. The above numerical value is just one example, and does not restrict the range of the rights of the present invention.
If the App_id_descrption field value is ‘0x0003’, the next following Application_id_byte value becomes a Service ID value of the NRT application. A service ID for the NRT application may have a URI value uniquely identifying a corresponding service around the world.
After the NRT application is identified, PID of an MPEG-2 TS packet divided from the IP datagram of an NRT service signaling channel is searched through Tap information. Then, IP datagram transmitting a NRT service signaling channel may be obtained from MPEG-2 TS packets having PID obtained through the tap information, and NRT service signaling data may be obtained from the obtained IP datagram. At this point, the IP access information of the NRT service signaling channel may be well-known IP access information, i.e., well-known IP address and well-known UDP port number.
That is, if the Protocol_encapsulation field value in the DST is 0x04, asynchronous IP stream is transmitted, and if the Selector_type field value is 0x0102, a device_id value indicating destination address may be delivered through selector_bytes. multiprotocol_encaplsulation_descriptor is used to accurately interpret the selector_bytes value and the number of valid bytes in the device_id value is signaled. As a result, through the Tap information, an IP Multicast address (or address range) of the NRT service signaling channel, transmitted to the corresponding PID, is obtained.
Accordingly, a receiver accesses the Multicast address (or address range) to receive IP stream, i.e., IP packet, and then, extracts NRT service signaling data from the received IP packet.
Then, the receiver receives NRT service data, i.e., NRT content item or files to store them in a storage medium or display them on a display device, on the basis of the extracted NRT service signaling data.
According to another embodiment, a Stream Type field value of DST may have new 0x96 instead of 0x95 to signal NRT service. This is because NRT service, i.e., new application, may malfunction when a typical receiver determines whether there is data broadcasting stream only on the basis of whether there is stream having a stream type of 0x95. In this case, with designating a stream newly, a typical receiver may disregard it to guarantee backwards compatibility.
FIGS. 10 and 11 are views illustrating a method of receiving NRT service by using DSM-CC addressable section data according to another embodiment.
A data transmission method using DST is a standard for transmitting all kinds of IP datagram through digital broadcasting stream, and may be inefficient for the NRT service. Accordingly, FIGS. 10 and 11 illustrate a method of receiving the NRT service by signaling the PID of a specific stream including IP address information and section data of the IP datagram with respect to the NRT service through the data of the DSM-CC addressable section.
As shown in FIG. 10, the receiver may obtain information that NRT service stream is transmitted through the virtual channel when a service type of VCT (or TVCT) is 0x08 (i.e., NRT Only service). That is, the receiver may obtain information on whether there is NRT service according to service_type information by mapping the PID of a virtual channel into a channel number.
At this point, if 0x0D is allocated to a stream_type field value in service location descriptor of VCT (or ES loop of PMT), it means that DSM-CC stream is transmitted. An Elementary_PID field value at this point may be the PID value of a DSM-CC addressable section. Accordingly, the receiver receives a DSM-CC addressable section including NRT service data through Elementary_PID.
That is, the receiver may obtain the PID of the DSM-CC addressable section through VCT or PMT. Here, the receiver may obtain an NRT_IP_address_list_descriptor_A( ) field including an IP address of an NRT service signaling channel or an IP address of the FLUTE session for transmitting NRT service data, which corresponds to the PID obtained from PMT of the corresponding stream.
Moreover, the receiver may receive DSM-CC addressable section data from IP multicast stream or IP subnet on the basis of the IP address obtained from an NRT_IP_address_list_descriptor_A( ) field. The receiver may obtain a corresponding IP datagram including a specific NRT service (for example, A, B, or C) data by searching a DSM-CC addressable section having PID corresponding to the obtained elementary_PID from the received DSM-CC addressable section data.
FIG. 11 is a view illustrating a method of signaling a DSM-CC addressable section data by using VCT according to another embodiment.
As mentioned above, the receiver may obtain information that NRT service stream may be transmitted when a service_type in VCT is 0X02, 0X04 of 0X08. Also, the receiver may obtain elementary_PID having a stream type of 0X0D from the service_location_descriptor( ) field to receive the DSM-CC stream. Here, the receiver may obtain an NRT_IP_address_list_descriptor_B( ) field including an IP address of an NRT service signaling channel or an IP address of the FLUTE session for transmitting NRT service data, which corresponds to the obtained elementary_PID.
Moreover, the receiver may receive DSM-CC addressable section data from IP multicast stream or IP subnet on the basis of the IP address obtained from an NRT_IP_address_list_descriptor_B( ) field. The receiver may obtain the IP datagram including specific NRT service (for example, A, B, or C) that it wants to receive from the received DSM-CC addressable section data by parsing the DSM-CC dddressable section having PID corresponding to the obtained elementary_PID.
The processes for extracting NRT service signaling data and NRT service data are described as follows. Here, 0x08 is allocated to the service_type field value in VCT, and indicates that at least one NRT service is transmitted to a corresponding virtual channel.
That is, when the receiver is turned on and a channel is selected by default or a user through a tuner, the PSI or PSIP section handler obtains VCT and PMT from a broadcast signal received through the selected channel. Also, the PSI or PSIP section handler parses the obtained VCT to confirm whether there is NRT service. This is confirmed by checking the service_type field value in a virtual loop of the VCT. For example, when the service type field value is not 0x08, the corresponding virtual channel does not transmit NRT service. At this point, since the virtual channel transmits existing service (i.e., legacy ATSC service), the receiver operates properly according to information in the virtual channel.
Additionally, in relation to a demultiplexing unit, if a service_type field value is 0x08 according to a control of a service manager, a corresponding virtual channel transmits NRT service. In this case, PID of DST is extracted by parsing a service location descriptor in a virtual channel loop of the VCT. Moreover, DST is received by using the extracted PID.
Moreover, the receiver confirms whether a corresponding service provided through a channel selected from the received DST is NRT service.
The NRT service is confirmed by an App_id_descrption field value.
According to an embodiment, ‘0x0003’ is allocated to the App_id_descrption field to identify NRT application. The above numerical value is just one example, and does not restrict the range of the rights of the present invention.
If the App_id_descrption field value in the DST is ‘0x0003’, the next following Application_id_byte value becomes a Service ID value of the NRT application (i.e., NRT service). Therefore, the service manager or PSI or PSIP section handler extracts Tap( ) to PID of an MEGP-2 TS packet separated from the IP datagram of the NRT service signaling channel after identifying the NRT application (i.e., NRT service). Then, stream PID including association_tag of the extracted Tap is extracted from PMT.
Also, the addressable section handler may recover the DSM-CC addressable section by removing decapsulation, i.e., an MPEG-2 header, after receiving MPEG-2 TS packets corresponding to the extracted stream PID.
Then, the receiver recovers the IP datagram transmitting an NRT service signaling channel by removing a section header and CRC checksum from the DSM-CC addressable section and obtains NRT service signaling data from the recovered IP datagram. Here, access information on the IP datagram transmitting the NRT service signaling channel is a well-known destination IP address and a well-known destination UDP port number.
That is, if the Protocol_encapsulation field value in the DST is 0x04, asynchronous IP stream is transmitted, and if the Selector_type field value is 0x0102, a device_id value indicating a destination address may be delivered through selector_bytes. multiprotocol_encaplsulation_descriptor is used to accurately interpret the selector_bytes value and the number of valid bytes in the device_id value is signaled. As a result, through the Tap information, an IP Multicast address (or address range) of the NRT service signaling channel, transmitted to the corresponding PID, is obtained.
Accordingly, a receiver accesses the Multicast address (or address range) to receive IP stream, i.e., IP packet, and then, extracts NRT service signaling data from the received IP packet.
The receiver receives NRT service data, i.e., NRT content item or files to store them in a storage medium or display them on a display device, on the basis of the extracted NRT service signaling data.
Moreover, the NRT service may be provided Dynamic Content Delivery (DCD) service according to an embodiment. The DCD service is service for transmitting content to a receiver periodically or at the user request, and the content is selected from a server according to receiver information. The DCD service supports a point-to-point method and a broadcast method in a communication means for content delivery, and the above NRT service is transmitted through an OMA BCAST method and one of the broadcast methods of the DCD service.
NRT service data may be transmitted through the DCD service of the OMA BCAST method. In this case, the receiver may obtain the DCD channel information to receive NRT service and may receive the NRT service through a corresponding DCD channel on the basis of the DCD channel information.
Moreover, the DCD channel information may be included in the NST and transmitted. For example, the receiver receives NST, and obtains DCD channel information through DCD bootstrap.
Additionally, the NST may include DCD channel metadata, received through a DCD administrative channel, for signaling of the DCD channel information. Accordingly, the receiver may obtain information on a channel for receiving NRT service and metadata through NST.
Accordingly, when NST including DCD channel information is transmitted, the receiver accesses the DCD channel through NST without transmission of the NRT service signal data, and then receives the NRT service.
Like this, if NST includes metadata of a channel for receiving NRT service, there are several advantages.
First, without receiving the NRT service signaling data on the basis of the service type of a virtual channel, service access speed may be increased by receiving channel metadata that directly receives NRT service from NST.
Additionally, update signaling for a channel change item may be performed in real time in a broadcast environment.
Moreover, access information in OMA BCAST SG may be obtained by referring to NST. For example, the receiver receives DCD channel meta data on the basis of the DCD channel information in NST, and obtains access information to receive NRT service on the basis of the NRT service signaling data and DCD channel metadata obtained from NST.
Lastly, NST including a list of NRT service related to another virtual channel may be transmitted. Accordingly, list information of the NRT service may be transmitted through a specific NRT service signaling channel on an IP layer not on a PSI or PSIP layer. Accordingly, in this case, backwards compatibility to PSI or PSIP may be reserved.
In addition, as mentioned above, the DCD channel information including the DCD channel metadata may be included in the access information of SG in OMA BCAST, and the access information corresponds to the NRT service information in NST. In more detail, the receiver may obtain NRT service information in NST from an access fragment of OMA BCAST SG. Accordingly, the receiver may obtain information on receiving NRT service by receiving NST corresponding to the obtained NRT service information.
Moreover, the NRT service transmitted through the DCD channel may be divided by a service category allocated. For example, the service category of the NRT service transmitted through the DCD channel may be identified by 0X0F.
FIGS. 12 and 13 are views illustrating a bit stream syntax of NST according to an embodiment.
Here, the corresponding syntax is created in an MPEG-2 private section format to help understanding, but the format of the corresponding data may vary. For example, the corresponding data may be expressed in a Session Description Protocol (SDP) format and signaled through a Session Announcement Protocol (SAP) according to another method.
NST describes service information and IP access information in a virtual channel for transmitting NST, and provides NRT broadcast stream information of a corresponding service by using an identifier of the NRT broadcast stream, i.e., NRT_service_id, in each service. Furthermore, the NST describes description information of each fixed NRT service in one virtual channel, and a descriptor area may include other additional information.
A table_id field (8 bits) as a field for type identification of a corresponding table section is a table section in which a corresponding table section constitutes NST through this field.
A section_syntax_indicator field (1 bit) is an indicator defining a section format of NST, and the section format may be short-form syntax (0) of MPEG, for example.
A private_indicator field (1 bit) represents whether the format of a corresponding section follows a private section format and may be set with 1.
A section_length field (12 bits) represents a remaining table section length after a corresponding field. Additionally, a value of this field does not exceed ‘0xFFD’.
A table_id_extension field (16 bits) is dependent on a table, and may be a logical part of a table_id field providing a range of the remaining fields. Here, a table_id_extension field includes an NST_protocol_version field.
The NST_protocol_version field (8 bits) shows a protocol version for notifying that NST transmits parameters having a different structure than other defined in a current protocol. Currently, this field value is 0. If the field value is designated with other than 0 later, it is for a table having a different structure.
A version_number field (5 bits) represents the version number of NST.
A current_next_indicator field (1 bit) indicates whether a transmitted NST table section is applicable currently. If the field value is 0, it means that there is no table yet and the next table is valid.
A section_number field (8 bits) represents a section number in sections in which a corresponding table section constitutes a NST table.
section_number of the first section of an NRT Service Table (NST) is set with ‘0x00’. The section_number is increased by one each time a section of the NST is increased.
A last_section_number field (8 bits) represents the last section number constituting a NST table, i.e., the highest section_number. (Highest section_number)
A carrier_frequnecy field (32 bits) notifies a transmission frequency corresponding to a channel.
A channel_TSID field (16 bits) means a unique channel identifier of broadcast stream in which a corresponding NST section is currently transmitted.
A program_number field (16 bits) represents the number of a program related to a virtual channel.
A source_id field (16 bits) represents the source of a program related to a virtual channel.
A num_NRT_services field (8 bits) represents the number of NRT services in an NST section.
Additionally, NST provides information on a plurality of fixed NRT services by using a ‘for’ loop. Hereinafter, the same field information may be provided to each fixed NRT service.
An NRT_service_status field (2 bits) identifies a state of a corresponding mobile service. Here, MSB indicates whether a corresponding mobile service is active (1) or inactive (0), and whether the corresponding mobile service is hidden (1) or not (0). Here, if the mobile service is NRT service, a state of the corresponding NRT service is identified. Hidden service is mainly used for exclusive application and a typical receiver disregards it.
A SP_indicator field (1 bit) is a field representing service protection if the service protection applied to at least one of components necessary for providing meaningful presentation of a corresponding mobile service is set.
A CP_indicator field (1 bit) represents whether content protection of a corresponding NRT service is set. If the CP_indicator field value is 1, it means that the content protection is applied to at least one of components required to provide a meaningful presentation of a corresponding NRT service.
An NRT_service_id field (16 bits) is an indicator that uniquely identifies a corresponding NRT service in a range of a corresponding NRT broadcast. The NRT_service_id is not changed during the corresponding service. Here, if the service is terminated, in order to evade confusion, NRT_service_id for the service may not be used for another service until an appropriate time elapses.
A Short_NRT_service_name field (8*8 bits) displays a short name of the NRT service. If there is no short name of the NRT service, the field may be filled with a null value (for example, 0x00).
An NRT_service_category field (6 bits) identifies a type of service in the corresponding NRT service.
A num_components field (5 bits) displays the number of IP stream components in the NRT service.
If an IP_version_flag field (1 bit) is set with 0, it indicates that a source_IP_address field, an NRT_service_destination_IP_address field, and a component_destination_IP_address field are IPv4 addresses. If set with 1, a source_IP_address field, an NRT_service_destination_IP_address field, and a component_destination_IP_address field are IPv6 addresses.
A source_IP_address_flag field (1 bit) indicates when a flag is set that there is a source IP address value for corresponding NRT service to indicate source specific multicast.
An NRT_service_destination_IP_address_flag field (1 bit) indicates when a flag is set with 1 that there is an NRT_service_destination_IP_address field for providing a default IP address for components of a corresponding NRT service.
In relation to a source_IP_address field (128 bits), there is a corresponding field if source_IP_address_flag is set with 1, but there is no corresponding field if set with 0. If there is a corresponding field, the corresponding field includes a source IP address of all IP datagram transmitting components of the corresponding NRT service. A restricted use of a 128 bit long address of a corresponding field is for future use of IPv6, which is not currently used though. Source_IP_address becomes a source IP address of the same server transmitting all channels of a FLUTE session.
In relation to an NRT_service_destination_IP_address field (128 bits), if source_IP_address_flag is set with 1, there is a source_IP_address field, but if source_IP_address_flag is set with 0, there is no corresponding source_IP_address field. If there is no corresponding source_IP_address field, a component_destination_IP_address field exists for each component in a num_components loop. A restricted use of a 128 bit long address of a corresponding source_IP_address field is for future use of IPv6, which is not currently used though. NRT_service_destination_IP_Address is signaled if there is a destination IP address of a session level of the FLUTE session.
Additionally, NST provides information on a plurality of components by using a ‘for’ loop. An essential_component_indicator field (1 bit) indicates when a value of a corresponding value is set with 1 that a corresponding component is a necessary component for NRT service. If not, the corresponding component is a selected component.
A port_num_count field (6 bits) indicates numbers of UDP ports related to a corresponding UDP or IP stream component. Values of the destination UDP port numbers are increased by one, starting from a component_destination_UDP_port_num field value.
A component_destination_IP_address_flag field (1 bit) is a flag representing that there is a component_destination_IP_address field for corresponding component if set with 1.
In relation to component_destination_IP_address field (128 bits), if component_destination TP address_flag is set with 1, there is corresponding field, but if component_destination_IP_address_flag is set with 0, there is no corresponding field. If there is a corresponding field, the corresponding field includes a source IP address of all IP datagram transmitting components of the corresponding NRT service. A restricted use of a 128 bit long address of a corresponding field is for future use of IPv6, which is not currently used though.
A component_destination_UDP_port_num field (16 bits) represents a destination UDP port number for corresponding UDP or IP stream component.
A num_component_level_descriptors field (4 bits) provides the number of descriptors providing additional information on corresponding IP stream component.
A component_level_descriptors field identifies at least one descriptor providing additional information on a corresponding IP stream component.
A num_NRT_service_level_descriptors field (4 bits) represents the number of NRT service level descriptors for corresponding service.
NRT_service_level_descriptor( ) identifies no or at least one descriptor providing additional information on corresponding NRT service. Here, a specific service type for NRT service may be provided. The specific service type includes a portal service providing web content, push VOD, and A or V download.
A num_virtual_channel_level_descriptors field (4 bits) describes the number of virtual channel level descriptors for a corresponding virtual channel.
virtual_channel_level_descriptor( ) represents a descriptor providing additional information on a virtual channel that a corresponding NST describes.
Moreover, NRT service is transmitted through FLUTE, and access information on the NST table is connected to FLUTE session information as follows.
Source_IP_address is a source IP address of the same server transmitting all channels of the FLUTE session.
NRT_service_destination_IP_Address is signaled if there is a destination IP address of a session level of the FLUTE session.
A component may be mapped into a channel in the FLUTE session, and an additional destination IP address (which is different from an IP address signaled by session) is signaled through component_destination_IP_address at each channel.
Additionally, a destination port number is signaled through component_destination_UDP_port_num and the number of destination ports starting from component_destination_UDP_port_num may be additionally designated through port_num_count.
A plurality of channels may be configured for one destination IP address by designating a port in plurality. Here, one component designates a plurality of channels. However, it is desired to identify a channel through a destination IP address in general. Here, one channel is typically mapped into one component.
Content items or files for NRT service are transmitted through FLUTE, and corresponding FLUTE session information is signaled using access information on the NST table.
FIG. 14 is a view illustrating a bit stream syntax of NRT_component_descriptor (MH_component_descriptor) according to an embodiment.
NRT_component_descriptor( ) is shown in a component descriptor loop in each component of each NRT service in NST. Then, all parameters in a corresponding descriptor correspond to parameters used for components of NRT service.
Hereinafter, each field information transmitted through the NRT_component_descriptor of FIG. 14 will be described as follows.
A component_type field (7 bits) identifies an encoding format of a component. The identification value may be one of values allocated for payload_type of a RTP or AVP stream. Additionally, the identification value may be a dynamic value ranging from 96 to 127. Values of the field for components constituting media transmitted through RTP are identical to those in payload_type in an RTP header of IP stream transmitting a corresponding component.
An adding value of a component_type field in a range of 43 to 71 will be defined in the future version of the standard. When NRT service stream is transmitted based on FLUTE, in order to additionally signal parameters (described below) necessary for FLUTE session, 38 (which is component_type defined for a FLUTE component in ATSC) may be used, or 43 (i.e., an unallocated value) may be defined as component_type for new NRT transmission, and used.
A num_STKM_streams field (8 bits) identifies numbers of STKM streams related to a corresponding component.
A STKM_stream_id field (8 bits) identifies STKM stream having keys in order to decrypt the obtained corresponding protected component. Here, the STKM_stream_id field in the component descriptor for the STKM stream is referred.
An NRT_component_data (component_type) field provides at least one of encoding parameters necessary for expressing a corresponding component and other parameters. Here, a structure of an NRT_component_data element is determined by a value of a component_type field.
A File Delivery Table (FDT) of FLUTE sessions is used for delivering item lists of all content items, and provides sizes, data types, and other information of items related to obtain the items.
Accordingly, the present invention obtains information for accessing the FLUTE session transmitting a corresponding content by using NST, in order to receive a selected content from SG obtained by using NRT-IT. Moreover, the present invention maps information in a file transmitted through a corresponding FLUTE session into information on a content item of NRT-IT. In this case, identification of service including the selected content item is resolved through NRT_service_id of the NST.
NRT service is transmitted through FLUTE, and access information on the NST table is connected to FLUTE session information as follows.
Source_IP_address is a source_IP_address of the same server transmitting all channels of the FLUTE session.
NRT_service_destination_IP_Address is signaled if there is a destination IP address of a session level of the FLUTE session.
A component may be mapped into a channel in the FLUTE session, and an additional destination TP address (which is different from an IP address signaled by session) is signaled through component_destination_IP_address at each channel. Additionally, a destination port number is signaled through component_destination_UDP_port_num and the number of destination ports starting from component_destination_UDP_port_num may be additionally designated through port_num_count.
A plurality of channels may be provided to one destination IP address by designating a plurality of ports, and in such a case, one component designates a plurality of channels. However, it is recommended that a channel be distinguished through a destination IP address, and in such a case, one channel is mapped into one component.
component_attribute_byte may be used to signal an additional attribute of a component constituting a session. Additional parameters necessary for signaling a FLUTE session may be signaled through this.
In this regard, parameters for signaling the FLUTE session are required, and include definitely necessary required parameters and optional necessary parameters related to a corresponding FLUTE session. Firstly, the definitely necessary parameters include parameters such as a source IP address, the number of channels in the session, the destination IP address and port number for each channel in the session, the Transport Session Identifier (TSI) of the session, and the start time and end time of the session. The optional necessary parameters related to a corresponding FLUTE session include parameters such as FEC Object Transmission Information, some information that tells receiver in the first place, that the session contains files that are of interest and bandwidth specification.
The number of channels in the session may be explicitly provided, or may be obtained by adding up the number of streams constituting the session. Through the NST and component_descriptor, parameters such as start time and end time of the session, source IP address, destination IP address and port number for each channel in the session, Transport Session Identifier (TSI) of the session, and number of channels in the session may be signaled.
FIG. 15 is a view illustrating a bit stream syntax of NRT component descriptor including NRT_component_data according to an embodiment.
One NRT service may be included in multiple FLUTE sessions. Each session may be signaled using at least one NRT component descriptors depending on IP addresses and ports used for the session.
Hereinafter, each field of NRT_component_data will be described as follows.
A TSI field (16 bits) represents TSI of a FLUTE session.
A session_start_time field indicates a start time of the FLUTE session. If all values of the corresponding fields are 0, it means that a session started already.
A session_end_time field indicates an end time of the FLUTE session. If all values of the corresponding fields are 0, it means that a session continues infinitely.
A tias_bandwidth_indicator field (1 bit) indicates flags including Transport Independent Application Specific (TIAS) bandwidth information. If it indicates that the TIAS bandwidth field exists, a corresponding bit is set with 1, and if it indicates that the TIAS bandwidth field does not exist, the corresponding bit is set with 0.
In relation to an as_bandwidth_indicator field (1 bit), flags include Application Specific (AS) bandwidth information. If it indicates that the AS bandwidth field exists, a corresponding bit is set with 1, and if it indicates that the AS bandwidth field does not exist, the corresponding bit is set with 0.
An FEC_OTI_indicator field (1 bit) represents whether FEC object transmission information (OTI) is provided.
A tias_bandwidth field represents a TIAS maximum bandwidth.
An as_bandwidth field has an AS maximum bandwidth value.
An FEC_encoding_id field represents FEC encoding ID used in the corresponding FLUTE session.
An FEC_instance_id field represents FEC instance ID used in the corresponding FLUTE session.
Provided is a method of providing all Information necessary for receiving the FLUTE session by signaling the same parameters as above through FLUTE component data bytes, and of receiving files by obtaining information on all the files delivered through the FLUTE session that uses FDT received through the session.
This FLUTE component descriptor may be delivered through a Component_level_descriptor loop of NST. If the FLUTE channel is in plurality, since TSI and session_start_time, session_end_Time, i.e., parameters of a session level, should be signaled once, a FLUTE component descriptor may be transmitted only in one of components in several channels through a Component_level_descriptor loop.
FIG. 16 is a view illustrating a bit stream syntax of NRT-IT section for signaling NRT application according to an embodiment.
Information provided from NRT-IT includes a title of content (for example, a name of downloadable program), download available time and information, content advisories, caption service availability, content identification, and other metadata. One item of content may include at least one file. For example, an audio or video clip may be played in a JPEG thumbnail image used for displaying a screen.
An instance of NRT-IT may include data corresponding to an arbitrarily predetermined period, or may describe a NRT content starting at a predetermined time and ends at the indefinite future. Each NRT-IT represents a start time and a duration period that may be indefinite. Each NRT-IT instance may be divided into 256 sections. Each section includes information on a plurality of content items. Information of a specific content item cannot be divided and stored in at least two sections.
The downloadable content item, which is more extended than a period that at least one NRT-IT instance takes, is the first of NRT-IT. The content item description is stored in NRT_information_table_section ( ) in an availability order. Accordingly, when a value of last_section_number is greater than 0 (it means that NRT-IT is transmitted to a plurality of sections), all content item description in a specific section not the first section may have the same as or higher availability than the content item description of the next section.
Each NRT-IT identifies an NRT service related to a specific value of a valid service_id in a specific virtual channel during the period.
A table_id field (8 bits) is set with 0xTBD to identify a table section that a corresponding table section constitutes NRT-IT.
A service_id field (16 bits) describes a service_id field related to NRT service showing a content item that the section describes.
An NRT_IT_version_number field (5 bits) is defined as a set in at least one NRT_content_table_section( ) having a common value with respect to service_id, current_next_indicator, protocol_version, and time_span_start fields. It identifies a version number of an NRT-IT instance. The version number is increased by 1 modulo 32 when a field of NRT-IT instance is changed.
A current_next_indicator field (1 bit) represents that a corresponding table section is applicable currently if set with 1.
A protocol_version field (8 bits) is set with 0. A function of protocol_version allows a table type having parameters in the future, which has a different structure than those defined in the current protocol. Currently, only one valid value of protocol_version is 0. A value other than 0 in protocol_version is used for the future version of standard to recognize other tables having different structures.
A time_span_start field (32 bits) represents a start time of an instance period represented in GPS sec from 00:00:00 UTC, Jan. 6, 1980. A time of day of time_span_start is set to 00 min of the time. A value 0 of time_span_start represents a period of an NRT-IT instance starting from a negative past. A value of time_span is identical at each section of multi-sectioned NRT-IT instance. Values of time_spdn_start dnd time_span_length are set not to overlap another NRT-IT instance of an IP subnet at a specified period.
A time_span_length field (11 bits) identifies a number of min starting at the time recognized at time_span_start that the instance covers. Once it is set, a value of time_span_length does not change in a value of time_span_start. If a value of time_span_length is 0, an NRT-IT instance covers an entire time starting from time_span_start at the indefinite future. When a value of time_span_start is 0, there is no meaning in time_span_length.
A value of time_span_start is identical at each section of multi-sectioned NRT-IT instance. Values of time_span_start and time_span_length are set not to overlap another NRT-IT instance of an IP subnet at a specified period.
A num_items_in_section field (8 bits) represents the number of content items described in an NRT-IT section.
A content_linkage field (16 bits) represents an identification number within a range from 0x0001 to 0xFFFF. 0x0000 is not used. content_linkage is a linkage function for two: this links at least one file of FLUTE FDT related to NRT service with metadata of NRT-IT and forms TF_id (identifier for Text Fragment in Text FragmentTable). A value of a content_linkage field corresponds to a value of an FDTCotent-Linkage element or a value of a File-Content-Linkage element in FLUTE FDT of each file related to a content item. A priority rule is applied when each content linkage value including a corresponding content linkage element in FLUTE FDT is matched.
A TF_available flag (Boolean flag) is set with 1 when Text Fragment exists in a Text Fragment Table of a service signaling channel. If Text Fragment is not included in a service signaling channel for the content item, a value of the TF_available field is set with 0.
If a low_lantency flag (Boolean flag) is set with 1, as a user waits, content is valid in a current digital transmission of sufficiently low delay time that collection attempts. If set with 0, a collection delay time becomes longer and a user interface suggests a post view to a user.
A playback_length_in_seconds (20 bits) is an integer representing a playing time of a content in sec. A content including texts and or or still images has a value of 0. In relation to a content including audio or audio or video content, playback_length_in_seconds represents a playing time of audio or audio or video content.
If a content_length_included flag (Boolean flag) is set with 1, a content_length field exists in the repetition in a ‘for’ loop. If set with 0, it indicates that the content_length field does not exist in the repetition in a ‘for’ loop.
If a playback_delay_included flag (Boolean flag) is set with 1, it indicates that a playback_delay field exists in the repetition in a ‘for’ loop. If set with 0, it indicates that the playback_delay field does not exist in the repetition in a ‘for’ loop.
If an expiration_included flag (Boolean flag) is set with 1, an expiration field exits in the repetition in a ‘for’ loop. If set with 0, it indicates that the expiration field does not exist in the repetition in a ‘for’ loop.
A duration (12 bits) field represents an expected cycle time of carousel including a referenced content item in a range of 1 to 2880 in min. A receiver uses a duration parameter determining a time taking for the referenced content capture.
playback_delay (20 bits) is represented with a number of the next sec of the first byte before playing a related content while incoming stream is buffered. A value of 0 represents playing starts immediately. When playback_delay is not set, a receiver collects a complete file or a file before playing.
An expiration field (32 bits) represents expiration time expressed in GPS sec from 00:00:00 UTC, Jan. 6, 1980. After expiration, the content is deleted from the memory. If it is not expired, the receiver uses a method that a company for managing a memory resource selects.
A content_name_length_field (8 bits) represents the length (byte unit) of content_name_text.
A content_name_text( ) field represents a content item title in a system having a plurality of string structures.
A content_descriptors_length field (12 bits) represents an entire length (byte unit) of content_descriptor providing additional information on a content level.
content_descriptor is a descriptor that is additionally applied to each content item.
descriptor_length (10 bits) represents an entire length (byte unit) of a descriptor.
A descriptor is generally applied to all content items described in the current NRT-IT section.
FIG. 17 is a view illustrating a syntax structure of bit stream for NRT section (NRT_content_table_section) according to an embodiment. Detailed description of each field in the NCT section is as follows.
In FIG. 17, a table_id field (8 bits) as the identifier of a table includes an identifier identifying NCT.
A section_syntax_indicator field (1 bit) is an indicator defining a section format of NCT.
A private_indicator field (1 bit) represents whether NCT follows a private section.
A section_length field (12 bits) represents the section length of NST.
An NRT_channel_id field (16 bits) represents a value uniquely identifying NRT service including content described in NCT.
A version_number field (5 bits) represents the version number of NCT.
A current_next_indicator field (1 bit) represents whether information in a corresponding NCT section is applicable currently or in the future.
A section_number field (8 bits) represents the section number of a current NCT section.
A last_section_number field (8 bits) represents the last section number of NCT.
A protocol_version field (8 bits) indicates a protocol version for allowing NCT, which transmits parameters having different structures then those defined in a current protocol. (An 8-bit unsigned integer field whose function is to allow, in the future, this NRT Content Table to carry parameters that may be structured differently than those defined in the current protocol. At present, the value for the protocol_version shall be zero. Non-zero values of protocol_version may be used by a future version of this standard to indicate structurally different tables.)
A num_contents_in_section field (8 bits) indicates the number of contents in the NCT. At this point, the number of contents represents the number of contents transmitted through a virtual channel that source_id specifies.
Later, a ‘for’ loop (or a content loop) is performed as many as the number of contents corresponding to the num_contents_in_section field value, to provide the detailed information of a corresponding content by each content.
A content_version field (32 bits) indicates the version number for content (or a file) having a specific content_id value. That is, let's assume that if content_id of a content that a receiver receives previously is 0x0010, the same content, i.e., its content_id value is 0x0010 is transmitted. At this point, if the content_version field value is different, the previously stored content is updated or replaced by receiving the newly announced content through the NCT. In this embodiment, the content_version field value means a series number representing a release version but may actually represent published (released) time directly. At this point, if the content_version field is difficult to represent publish time, a new field may be used to represent the published (released) time.
A content_id field (16 bits) indicates an identifier uniquely identifying the content (or file).
A content_available_start_time field (32 bits) and a content_available_end_time field (32 bits) represent a start time and end time of a FLUTE session transmitting the content.
An ETM_location field (2 bits) describes the existence and location of an extended text message (ETM).
A content_length_in_seconds field (30 bits) represents an actual play time of a corresponding content in sec unit when the content (or file) is an A or V file.
A content_size field (48 bits) represents the size of the content (or file) in byte unit.
A content_delivery_bit_rate field (32 bits) represents a bit rate at which the content (or file) is transmitted, and means a target bit rate. That is, when a service provider or broadcasting station transmits a corresponding content, the content_delivery_bit_rate field displays how wide a bandwidth is to be allocated. Accordingly, if a receiver uses content_size and content_delivery_bit_rate, the minimum time for receiving a corresponding content (or file) is obtained. That is, the time for receiving content is estimated and provided to a user. Also, the minimum receiving time is obtained by calculating (conent_size*8) or (content_delivery_bit_rate) and its unit is in sec.
A content_title length field (8 bits) represents the length of content_title_text( ) in byte unit. If this field is used, the receiver knows how many bytes need to be read to obtain content_title_text ( ) information.
A content_title_text( ) field represents a content title in the format of a multiple string structure.
That is, the receiver uses the NCT to obtain configuration information on NRT content or file, and provides a guide for the NRT or file on the basis of the obtained configuration information on NRT content or file. Moreover, the receiver obtains access information of FLUTE session, which transmits the content or file selected by the guide, from NST, and receives the selected content by using the obtained FLUTE session access information.
Moreover, the present invention may include container information, encoding information, and decoding parameters of media objects, necessary for rendering of the content or files constituting NRT service, in the NCT, and then transmit it. Accordingly, a receiving system extracts the container information, the encoding information, and the decoding parameters of media objects by each content, necessary for rendering of the corresponding content or files, and uses them in rendering.
FIG. 18 is a view illustrating a bit stream syntax structure of an SMT session providing signaling information on NRT service data according to an embodiment.
Here, the corresponding syntax is created in an MPEG-2 private section format to help understanding, but the format of the corresponding data may vary.
The SMT describes signaling information (or signaling information of NRT service) and IP access information of a mobile service in Ensemble in which SMT is transmitted. The SMT uses Transport_Stream_ID, i.e., an identifier of broadcast stream including each service, and provides broadcasting stream information of a corresponding service. Furthermore, SMT includes description information of each mobile service (or NRT service) in one Ensemble, and includes other additional information in a descriptor area.
As mentioned above, the SMT session may be included as the IP stream format in the RS frame, and then, transmitted. In this case, RS frame decoders of a receiver describe later decode inputted RS frames, and outputs the decoded RS frames as a corresponding RS frame handler. Moreover, each RS frame handler divides the inputted RS frame by a row unit to constitute M or H TP, and outputs it as an M or H TP handler.
In addition, examples of fields transmitted through SMT are as follows.
A table_id field (8 bits) is a field indicating a table type, and through this, it is confirmed that this table section is a table section in SMT. (table_id: An 8-bit unsigned integer number that indicates the type of table section being defined in Service Map Table (SMT)).
A section_syntax_indicator field (1 bit) is an indicator defining a session format of SMT, and its session format may be a short-form syntax (‘0’) of MPEG (section_syntax_indicator: This 1-bit field shall be set to ‘0’ to always indicate that this table is derived from the “short” form of the MPEG-2 private section table).
A private_indicator field (1 bit) indicates whether SMT follows a private section (private_indicator: This 1-bit field shall be set to ‘1’).
A section_length field (12 bits) represents the remaining session length of SMT after a corresponding field (section_length: A 12-bit field. It specifies the number of remaining bytes this table section immediately following this field. The value in this field shall not exceed 4093 (0xFFD)).
A table_id_extension field (16 bits) is dependent on a table, and may be a logical part of a table_id field providing a range of the remaining fields (table_id_extension: This is a 16-bit field and is table-dependent. It shall be considered to be logically part of the table_id field providing the scope for the remaining fields).
Here, a table_id_extension field includes an SMT_protocol_version field.
The SMT_protocol_version field (8 bits) shows a protocol version that allows SMT transmitting parameters having a different structure than those defined in a current protocol (SMT_protocol_version: An 8-bit unsigned integer field whose function is to allow, in the future, this SMT to carry parameters that may be structured differently than those defined in the current protocol. At present, the value for the SMT_protocol_version shall be zero. Non-zero values of SMT_protocol_version may be used by a future version of this standard to indicate structurally different tables).
An ensemble_id field (8 bits) includes values of ‘0x00’ to ‘0x3F’, as an ID value related to corresponding Ensemble (ensemble_id: This 8-bit unsigned integer field in the range 0x00 to 0x3F shall be the Ensemble ID associated with this Ensemble. The value of this field shall be derived from the parade_id carried from the baseband processor of physical layer subsystem, by using the parade_id of the associated Parade for the least significant 7 bits, and using ‘0’ for the most significant bit when the Ensemble is carried over the Primary RS frame, and using ‘1’ for the most significant bit when the Ensemble is carried over the Secondary RS frame).
A version_number field (5 bits) represents the version number of SMT. A current_next_indicator field (1 bit) indicates whether a transmitted SMT table session is applicable currently (current_next_indicator: A one-bit indicator, which when set to ‘1’ shall indicate that the Service Map Table sent is currently applicable. When the bit is set to ‘0’, it shall indicate that the table sent is not yet applicable and will be the next table to become valid. This standard imposes no requirement that “next” tables (those with current_next_indicator set to ‘0’) must be sent. An update to the currently applicable table shall be signaled by incrementing the version_number field).
A section_number field (8 bits) represents a current SMT session number (section_number: This 8-bit field shall give the section number of this NRT Service Signaling table section. The section_number of the first section in an NRT Service Signaling table shall be 0x00. The section_number shall be incremented by 1 with each additional section in the NRT Service Signaling table).
A last_section_number field (8 bits) represents the last session number constituting an SMT table.
(last_section_number: This 8-bit field shall give the number of the last section (i.e., the section with the highest section_number) of the Service Signaling table of which this section is a part).
A num_services field (8 bits) indicates the number of services in an SMT session. (num_services: This 8 bit field specifies the number of services in this SMT section.). At least one mobile service, at least one NRT service, or mobile and NRT services may be received through Ensemble having the SMT. If only NRT services are transmitted through the Ensemble having SMT, it may indicate the number of NRT services in the SMT.
Later, a ‘for’ loop (or a service loop) is performed as many times as the number of services corresponding to the num_service field value, to provide signaling information on a plurality of services. That is, signaling information of a corresponding service is displayed by each service in the SMT session. Here, the service may be mobile or NRT service. At this point, the following field information may be provided to each service.
A service_id field (16 bits) represents a value uniquely identifying a corresponding service (A 16-bit unsigned integer number that shall uniquely identify this service within the scope of this SMT section.). The service_id of a service shall not change throughout the life of the service.
To avoid confusion, it is recommended that if a service is terminated, then the service_id for the service should not be used for another service until after a suitable interval of time has elapsed. Here, if the service is NRT service, the service_id may identify the NRT service.
A Multi_ensemble_service field (2 bits) identifies whether a corresponding service is transmitted through at least one Ensemble.
Additionally, the corresponding field identifies whether service is rendered as a portion of the service transmitted through a corresponding Ensemble. That is, if the service is NRT service, the filed identifies whether NRT service is transmitted through at least one Ensemble (multi_ensemble_service: A two-bit enumerated field that shall identify whether the Service is carried across more than one Ensemble. Also, this field shall identify whether or not the Service can be rendered only with the portion of Service carried through this Ensemble.).
A service_status field (2 bits) identifies a state of a corresponding service. Here, MSB indicates whether a corresponding service is active (1) or inactive (0), and LSB indicates whether a corresponding service is hidden (1) or not (0). Here, when the service is NRT service, MSB of the service_status field indicates whether a corresponding NRT service is active (1) or inactive (0), and LSB indicates whether a corresponding NRT service is hidden (1) or not (0).
A SP_indicator field (1 bit) represents whether service protection of a corresponding service is set. If a SP_indicator field value is 1, service protection is applied to components required for providing meaningful presentation of a corresponding service.
A short_service_name_length field (3 bits) represents the length of a short service name in a short_service_name field in byte unit.
A short_service_name field represents a short name of a corresponding service (short_service_name: The short name of the Service, each character of which shall be encoded per UTF-8 [29]. When there is an odd number of bytes in the short name, the second byte of the last of the byte pair per the pair count indicated by the short_service_name_length field shall contain 0x00). For example, if the service is mobile service, a short name of the mobile service is displayed, and if it is NRT service, a short name of the NRT service is displayed.
A service category field (6 bits) identifies a type category of a corresponding service. If a value of a corresponding field is set with a value indicating “informative only”, it is dealt as an informative description for the category of the service. And, a receiver is required to test a component_level_descriptors( ) field of SMT in order to identify an actual category of the received service. The service_category field has an NTP time based component for services having video and or or audio component.
Especially, in regards to the present invention, if a service_category field value has ‘0x0E’, a corresponding service indicates NRT service. In this case, it is indicated that signaling information of service currently described in an SMT session is signaling information of NRT service.
A num_components field (5 bits) indicates the number of IP stream components in this service.
IP_version_flag field (1 bit), when set to ‘0’, shall indicate that source_IP_address, service_destination_IP_address, and component_destination_IP_address fields are IPv4 addresses. The value of ‘1’ for this field is reserved for possible future indication that source_IP_address, service_destination_IP_address, and component_destination_IP_address fields are for IPv6. Use of IPv6 addressing is not currently defined.
A source_IP_address_flag field (1 bit) shall indicate, when set, that a source IP address value for this Service is present to indicate a source specific multicast.
When a service_destination_IP_address_flag field (1 bit) is set, it indicates that a corresponding IP stream component is transmitted through IP datagram having a different target IP address than service_destination_IP_address.
Accordingly, if the flat is set, a receiving system uses component_destination_IP_address as destination_IP_address, and disregards a service_destination_IP_address field in a num_channels loop (service_destination_IP_address_flag: A 1-bit Boolean flag that indicates, when set to ‘1’, that a service_destination_IP_address value is present, to serve as the default IP address for the components of this Service).
In relation to the source_IP_address field (32 or 128 bits), if source_IP_address_flag is set with 1, interpretation is required, but if not set with 0, no interpretation is required.
When the source_IP_address_flag field is set with ‘1’ and the IP_version_flag field is set with ‘0’, this field indicates a 32 but IPv4 address representing a source of a corresponding circuit channel. If the IP_version_flag field is set with ‘1’, this field indicates a 32 bit IPv6 address representing a source of a corresponding virtual channel (source_IP_address: This field shall be present if the source_IP_address_flag is set to ‘1’ and shall not be present if the source_IP_address_flag is set to ‘0’. If present, this field shall contain the source_IP_address of all the IP datagram carrying the components of this Service. The conditional use of the 128 bit-long address version of this field is to facilitate possible use of IPv6 in the future, although use of IPv6 is not currently defined).
If the service is NRT service, the Source_IP_address field becomes a source_IP_address of the same server transmitting all channels of the FLUTE session.
In relation to the service_destination_IP_address field (32 or 128 bits), if service_destination_IP_dddress_flay is set with 1, interpretation is required, but if set with 0, no interpretation is required. When the service_destination_IP_address_flag field is set with ‘1’ and the IP_version_flag field is set with ‘0’, this field indicates a 32 bit destination IPv4 address for a corresponding virtual channel.
When the service_destination_IP_address_flag field is set with ‘1’ and the IP_version_flag field is set with ‘1’, this field indicates a 64 bit destination IPv6 address for a corresponding virtual channel. If the corresponding service_destination_IP_address cannot be interpreted, a component_destination_IP_address field in a num_components loop needs to be interpreted, and a receiving system uses component_destination_IP_address to access an IP stream component (service_destination_IP_address: This field shall be present if the service_destination_IP_address_flag is set to ‘1’ and shall not be present if the service_destination_IP_address_flag is set to ‘0’. If this service_destination_IP_address is not present, then the component_destination_IP_address field shall be present for each component in the num_components loop. The conditional use of the 128 bit-long address version of this field is to facilitate possible use of IPv6 in the future, although use of IPv6 is not currently defined). If the service is NRT service, the service_destination_IP_Address field is signaled with a destination IP address of a session level of the FLUTE session.
Additionally, SMT provides information on a plurality of components by using a ‘for’ loop.
Later, a ‘for’ loop (or a component loop) is performed as many times as the number of components corresponding to the num_components field value, to provide access information on a plurality of components. That is, access information on each component in a corresponding service is provided. At this point, the following field information on each component may be provided. Here, one component corresponds to one FLUTE session according to an embodiment.
An essential_component_indicator field (1 bit), when set to ‘1’, shall indicate that this component is an essential component for the service. Otherwise, this field indicates that this component is an optional component).
A component_destination_IP_address_flag field (1 bit) shall indicate, when set to ‘1’, that the component_destination_IP_address is present for this component.
A port_num_count field (6 bits) shall indicate the number of destination UDP ports associated with this UDP or IP stream component. The values of the destination UDP port numbers shall start from the component_destination_UDP_port_num field and shall be incremented by one, except in the case of RTP streams, when the destination UDP port numbers shall start from the component_destination_UPD_port_num field and shall be incremented by two, to allow for the RTCP streams associated with the RTP streams.
A component_destination_UDP_port_num (16 bits) represents the destination UDP port number for this UDP or IP stream component. For RTP streams, the value of component_estination_UDP_port_num shall be even, and the next higher value shall represent the destination UDP port number of the associated RTCP stream).
A component_destination_IP_address field (32 or 128 bits) shall be present if the component_destination_IP_address_flag is set to ‘1’ and shall not be present if the component_destination_IP_address_flag is set to ‘0’. When this field is present, the destination address of the IP datagram carrying this component of the M or H Service shall match the address in this field. When this field is not present, the destination address of the IP datagram carrying this component shall match the address in the M or H_service_destination_IP_address field. The conditional use of the 128 bit-long address version of this field is to facilitate possible use of IPv6 in the future, although use of IPv6 is not currently defined.
A num_component_level_descriptors field (4 bits) indicates the number of descriptors providing additional information on a component level.
component_level_descriptor( ) fields are included in the component loop as many as a number corresponding to the num_component_level_descriptors field value, so that additional information on the component is provided.
A num_service_level_descriptors field (4 bits) indicates the number of descriptors providing additional information on a corresponding service level.
service_level_descriptor( ) fields are included in the service loop as many as a number corresponding to the num_service_level_descriptors field value, so that additional information on the service is provided. If the service is mobile service, additional information on the mobile service is provided, and if it is NRT service, additional information on the NRT service is provided.
A num_ensemble_level_descriptors field (4 bits) indicates the number of descriptors providing additional information on an ensemble level.
ensemble_level_descriptor( ) fields are included in the ensemble loop as many as a number corresponding to the num_ensemble_level_descriptors field value, so that additional information on the ensemble is provided.
Moreover, component_descriptor( ) as component_level_descriptors( ) may be provided to SMT of FIG. 18.
The component_descriptor( ) is used as one of component_level_descriptors( ) of SMT, and describes additional signaling information of a corresponding component.
Accordingly, in relation to mobile NRT service, signaling information necessary for receiving a corresponding FLUTE session may be provided using the component descriptor of FIG. 14.
For example, if a component_type field value of the component descriptor of FIG. 14 is 38, a component_data (component_type) field provides data for FLUTE file delivery as shown in FIG. 15. Since each field description of FIGS. 14 and 15 is made above, overlapping descriptions will be omitted.
FIG. 19 is a view illustrating an FDT schema for mapping a file and content_id according to an embodiment. FIG. 20 is a view illustrating an FDT schema for mapping a file and content_id according to another embodiment. They represent an FDT instant level entry file designating method. NRT content includes a plurality of files. However, since each file has no mark, it is difficult to search a file related to NRT content. Accordingly, as shown in FIGS. 19 and 20, content_id is inserted into FDT in each file.
Hereinafter, an FDT instance level means, if a common attribute of all files declared in FDT needs to be defined, a level including a definition portion for the common attribute. An FDT file level may mean a level including definition for an individual attribute of each file.
A receiver identifies whether a service transmitted through a corresponding channel is an SMT based NRT service. Additionally, the receiver identifies a content item and file of the corresponding NRT service.
As mentioned above, although the receiver may identify a file and content item in the NRT service, it does not have information on files of the content item and thus cannot match them. Accordingly, the receiver may not process the NRT service.
Accordingly, the present invention provides a method of identifying whether a content item is related. That is, a corresponding method shows what kinds of files are included in a content item. In this case, the receiver may properly process the received NRT service. Accordingly, the corresponding method may be designated on the basis of FDT information in FLUTE session transmitting NRT service. For example, each file constituting a content item is identified on the basis of a content-location and TOI field designated in the FLUTE session. content_id in FDT is matched to a content identifier (content_id) of NCT or a content identifier of content fragment in OMB BCAST SG.
Referring to FIGS. 19 and 20, a portion indicated with 1 declares a content identifier in an FDT-Instance level, and this declared content identifier is assigned to all files declared in a corresponding FDT-Instance. Of course, this information may be overridden by assigning a new content identifier in a file level. Or, if a specific file belongs to another content item not a content item defined in the FDT-Instance level, this may be notified through assigning a file level content_id described below. This embodiment expresses content_id in 16 bits.
In relation to a portion indicated with 2, when a file in the FDT Instance is included different content items with content_id declaration in a file level, this method signals which file, all files of a content item and content, belongs to which entry.
A portion 3 is a method of notifying whether a corresponding file for each file is an entry file. That is, a file corresponding to a root file, which is played first among several files constituting a content item or is necessarily executed first to access a content item is called an entry file, and represents a method of notifying this information. An entry attribute may be omitted, and its default value is false. When it is omitted, it means that a corresponding file is not an entry file. “Entry” is a head of a file that needs to be processed to execute the file. For example, “index.html” may be an “entry”. Accordingly, an entry file may be set with ‘true” and other files are set with “false”. Through the entry file, transmitting the same file repeatedly may be effectively controlled. Once a file is downloaded, the entry file indicates a file of content for another reference, so that there is no need to download it in another or an additional instance.
A specific file functions as an entry in a specific group as a group related to a file level signals whether entry is possible, but its corresponding role may fail in another group. When a content identifier is assigned in an FDT-instance level, a method of notifying an entry file may be considered as the following two methods.
1) A method of additionally assigning a file level content identifier to a file corresponding to an entry file and setting its entry attribute with true: in this case, a content identifier is duplicated in an FDT-Instance level and a file level, but has the most flexible structure. That is, although one of the File-level and FDT-instance level may designate content_id, if another content_id is designated together in the File-level and FDT-instance, the content_id of the File level has priority to that of the FDT-instance level.
2) like another embodiment of the FDT schema of FIG. 20, files functioning as an entry file may be directly referenced in content identifier definition in the FDT-instance level. For this, according to the embodiment of FIG. 20, FDT-Content-ID-Type is additionally defined for an FDT-instance level content identifier, and as shown in the portion 2, extends to include a content location of an entry file. In the case of the portion 2, an entry level is defined with its content_id. For example, each content_id shows which entry file exists.
In this method, content-location is duplicated so signaling may be problematic, but entry file configuration information may be immediately obtained by each content item.
FIG. 21 is a flowchart illustrating an operation of a receiver according to an embodiment.
Referring to FIG. 21, according to an embodiment, a receiver receives NRT service signaling data through an NRT service signaling channel, displays NRT guide information on the basis of the received NRT service signaling data, and receives NRT service data for the selected NRT content, in order to provide NRT service.
First, once the receiver is turned on, a user selects a channel in operation S1000. Then, a physical transmission channel is turned according to the selected channel.
Then, VCT and PMT are obtained from a broadcast signal received through the tuned physical transmission channel in operation S1010. Then, it is confirmed in operation S1020 whether there is NRT service by parsing the obtained TVCT (VCT). This is confirmed by checking the service_type field value in a virtual loop of the VCT. For example, if a service_type field has 0x08, there is NRT service. Moreover, if not 0x08, since a corresponding virtual channel does not transmit the NRT service, a proper operation such as general A or V service may be performed according to information in the virtual channel in operation S1111.
Moreover, if it is determined that there is NRT service, since a corresponding virtual channel transmits NRT service, PID(PID=PID_NST) matching to a specific PID(PID_NST) of stream including a well known IP address for NRT service signaling channel address is obtained in operation S1030.
Moreover, the receiver receives a Transport Packet (TP) having the same PID as the obtained PID value (PID_NST) in operation S1040.
Then, the receiver extracts NRT service signaling data including a NRT service table (NST) from the received TP, or extracts an IP address for the NRT service signaling channel access from the received TP, in order to receive NRT service signaling data transmitted in another format through an IP layer in operation S1050.
Then, the receiver obtains channel information on NRT service data transmission by each NRT service from NST in operation S1060.
Then, the receiver obtains an NRT content table (NCT) including an NRT_channel_id field value identical to a value of Channel_id, an identifier of the obtained channel information, from the NRT service signaling data in operation S1070.
Then, the receiver obtains content information on NRT content constituting each NRT service from each field of the obtained NCT in operation S1080. For example, the content information may include at least one of content_delivery_bit_rate, content_available_start_time, content_available_end_time and content_title_text( ) fields according to an embodiment of the NCT.
Then, the receiver displays NRT guide information by using content information in operation S1090. A user may select NRT content to use or be received, from the displayed NRT guide information.
Then, the receiver obtains NRT service access information having the selected NRT content from NST in operation S1100. The NRT service access information may include channel information or IP address information for receiving NRT service data, for example.
Moreover, the receiver receives a corresponding NRT content in operation S1110 by using the obtained NRT service access information after accessing a channel or server for transmitting NRT service, and performs a proper operation according to the NRT content.
FIGS. 22 and 23 are views illustrating a receiving system receiving, storing, and playing an NRT content for NRT service according to another embodiment.
The receiver of FIG. 23 may include an operation controlling unit 100, a baseband processing unit 110, a service demultiplexer 120, a stream component handler 130, a media handler 140, a file handler 150, a service manager 160, a PVR manager 170, a first storage unit 180, an SG handler 190, an EPG manager 191, an NRT service manager 192, an application manager 194, a middleware engine 193, a presentation manager 195, and a User Interface (UI) manager 196.
The baseband processing unit 110 may include a tuner 111 and a demodulator. The service demultiplexer 120 may include an MPEG-2 TP handler 121, a PSI or PSIP handler 122, an MPEG-2 TP demultiplexer 123, a descrambler 124, and a second storage unit 125.
The stream component handler 130 may include a Packetized Elementary Stream (PES) demodulator 131, an Elementary Stream (ES) demodulator 132, a PCR handler 133, a STC handler 134, a DSM-CC addressable section handler 135, an IP datagram handler 136, a descrambler 137, a UDP handler 138, a service signaling section handler 138-1, and a Conditional Access System (CAS) 139.
The media handler 140 may include an A or V demodulator 141. The file handler 150 may include an ALC or LCT stream handler 151, a file reconstruction buffer 152, an XML parser 153, an FDT handler 154, a decompressor 155, a third storage unit 156, and a file decoder 157.
In FIG. 23, the tuner 111 tunes a broadcast signal of a desired channel among broadcast signals received through a terrestrial wave according to a control of the service manager 160, and then down-converts the tuned broadcast signal into an Intermediate Frequency (IF) signal to output it to the demodulator 112. The tuner 111 may receive real-time stream and non-real-time stream. The non-real-time stream is called an NRT stream in the present invention.
The demodulator 112 performs automatic gain control, carrier recovery, and timing recovery on a digital IF signal of a pass band inputted from the tuner 111, converts the digital IF signal into a baseband signal, and performs channel equalization. For example, when the broadcast signal is a VSB modulation signal, a VSB demodulation process is performed for automatic gain control, carrier recovery, and timing recovery.
The demodulated and channel-equalized data in the demodulator 112 is outputted to the MPEG-2 TP handler 121 in an MPEG-2 Transport Stream (TS) packet format.
The MPEG-2 TP handler 121 includes an MPEG-2 TP buffer and an MPEG-2 TP parser, and analyzes a TS header after temporarily storing an output of the demodulator 112. Then, if an output of the demodulator 112 is an A or V TS packet for real Lime or an NRT TS packet, ii is outputted to the demultiplexer 123, and if it is a TS packet for PSI or PSIP table, it is outputted to the PSI or PSIP handler 122.
The PSI or PSIP handler 122 includes a PSI or PSIP section buffer and a PSI or PSIP parser, and after temporarily storing a TS packet outputted from the MPEG-2 TP handler 121, restores and parses a corresponding table from PSI or PSIP section data in a payload of the TS packet, with reference to a table identifier. At this point, it is determined whether one table includes one section or a plurality of sections through a table_id field, a section_number field, and a last_section_number field in a corresponding section. Also, sections having the same table identifier are collected to complete a corresponding table. For example, sections having a table identifier allocated to VCT are collected to complete VCT. Moreover, the parsed information of each table is collected by the service manager 160 to be stored in the first storage unit 180. Table information such as VCT, PAT, PMT, and DST are stored in the first storage unit through the above processes. The service manager 160 stores the table information in the first storage unit 180 in a service map and guide data format.
The demultiplexer 123, if the inputted TS packet is an A or V TS packet in real time, divides the TS packet into an audio TS packet and a video TS packet, and then outputs them into the PES decoder 131. If the inputted TS packet is an NRT TS packet, it is outputted to the DSM-CC handler 135. Additionally, the demultiplexer 123, if the TS packet includes a Program Clock Reference (PCR), outputs it to the PCR handler 133, and if it includes Conditional Access (CA) information, outputs it to the CAS 139. An NRT TS packet includes a TS packet having NRT service data and a TS packet having NRT service signaling channel. A unique PID for identifying the NRT service is allocated to a TS packet of the NRT service data, and PID of a TS packet including the NRT service signaling channel is extracted using DST and PMT.
The demultiplexer 123, if a payload of the inputted TS packet is scrambled, outputs it to the descrambler 124, and then, the descrambler 124 receives information (control words used for scramble) necessary for descramble from the CAS 139, and performs descramble on the TS packet.
The demultiplexer 123 stores an A or V packet in real time, inputted at the one request of temporary recording, scheduled recording, and time shift, in the second storage unit 125. The second storage unit 125 is a mass storage medium and may include HDD, for example. The second storage unit 125 performs downloading (i.e., storing) and updating (i.e., playing) according to a control of the PVR manager 170.
The demultiplexer 123 separates an audio TS packet and a video TS packet from the A or V TS packet updated from the second storage unit and then outputs them to the PES decoder 131 at the playing request.
The demultiplexer 123 is controlled by the service manager 160 and or or the PVR manager 170 to perform the above processes.
That is, if a service_type field value in VCT indicates that NRT service is transmitted, the service manger 160 extracts identification information of each NRT service from NRT_service_descriptor( ) received from a virtual channel loop of the VCT and stores it, and then extracts DST PID from a service location descriptor (or an ES loop of PMT) of the VCT to receive DST.
Then, NRT service is identified from the received DST, and PID of an MPEG-2 TS packet including the NRT service signaling channel is extracted to receive the identified NRT service by using DST and PMT. The extracted PID is outputted to the demultiplexer 123. The demultiplexer 123 outputs MPEG-2 TS packets corresponding to PID, outputted from the service manager 160, to the addressable section handler 135.
The PCR is a time reference value used for time synchronization of audio ES and video ES in the A or V decoder 141. The PCR handler 133 restores PCR in the payload of the inputted TS packet and outputs it to the STC handler 134. The STC handler 134 restores System Time Clock (STC), i.e., a reference clock of a system, from the PCR, and outputs it to the A or V decoder 141.
The PES decoder 131 includes a PES buffer and a PES handler, and after temporarily storing an audio TS packet and a video TS packet, removes a TS header from the TS packet to restore audio PES and video PES. The restored audio PES and video PES are outputted to the ES decoder 132. The ES decoder 132 includes an ES buffer and an ES handler, and removes each PES header from audio PES and video PES to restore audio ES and video ES, i.e., pure data. The restored audio ES and video ES are outputted to the A or V decoder 141.
The A or V decoder 141 decodes the audio ES and video ES through each decoding algorithm to restore a previous state of compression, and then outputs it to the presentation manager 195. At this point, time synchronization is performed when audio ES and video ES are decoded according to the STC. As one example, an audio decoding algorithm includes at least one an AC-3 decoding algorithm, an MPEG 2 audio decoding algorithm, an MPEG 4 audio decoding algorithm, an AAC decoding algorithm, an AAC+ decoding algorithm, an HE AAC decoding algorithm, an AAC SBR decoding algorithm, an MPEG surround decoding algorithm, and a BSAC decoding algorithm. A video decoding algorithm includes at least one of an MPEG 2 video decoding algorithm, an MPEG 4 video decoding algorithm, an H.264 decoding algorithm, an SVC decoding algorithm, and a VC-1 decoding algorithm.
The CAS 139 includes a CA stream buffer and a CA stream handler, and after temporarily storing a TS packet outputted from the MPEG-2 TP handler or service protection data restored and outputted from a UDP datagram handler 138, restores information (for example, control words used for scramble) necessary for descramble from the stored TS packet or service protection data. That is, Entitlement Management Message (EMM) and Entitlement Control Message (ECM) in the payload of the TS packet are extracted and information necessary for descramble is obtained by analyzing the extracted EMM and ECM. The ECM may include a control word (CW) used in scramble. At this point, the control word may be encrypted using an encryption key. The EMM may include an encryption key and qualification information of corresponding data. Information necessary for descramble obtained from the CAS 339 is outputted to the descrambler 124 and 137.
The DSM-CC section handler 135 includes a DSM-CC section buffer and a DSM-CC section parser, and after temporarily storing a TS packet outputted from the demultiplexer 123, restores an addressable section in the payload of the TS packet. After restoring IP datagram by removing a header and CRC checksum of the addressable section, the restored IP datagram is outputted to the IP datagram handler 136.
The IP datagram handler 136 includes an IP datagram buffer and an IP datagram parser. After buffering IP datagram delivered from the DSM-CC section handler 135, the IP datagram handler 136 extracts and analyzes a header of the buffered IP datagram to restore UDP datagram from the payload of the IP datagram, and then, outputs it to the UDP datagram handler 138.
At this point, if the IP datagram is scrambled, the scrambled UDP datagram is descrambled in the descrambler 137 and then is outputted to the UDP datagram handler 138. As one example, the descrambler 137 receives information (e.g., a control word used for scramble) necessary for descramble from the CAS 138 and performs descramble on the UDP datagram to output it to the UDP datagram handler 138.
The UDP datagram handler 138 includes an UDP datagram buffer and a UDP datagram parser. After buffering IP datagram delivered from the IP datagram handler 136 or the descrambler 137, the UDP datagram handler 138 extracts and analyzes a header of the buffered UDP datagram to restore the data included in the payload of the UDP datagram. At this point, if the restored data is service protection data, it is outputted to the CAS 139; if the restored data is NRT service signaling data, it is outputted to the service signaling section handler 138-1; and if the restored data is NRT service data, it is outputted to the ALC or LCT stream handler 151.
That is, access information on the IP datagram transmitting the NRT service signaling channel is a well-known destination IP address and a well-known destination UDP port number.
Accordingly, the IP datagram handler 136 and the UDP datagram handler 138 include a well-known destination IP multicast address and a well-known destination UDP port number, and extracts an IP multicast stream transmitting an NRT service signaling channel, i.e., NRT service signaling data, to output it to the service signaling section handler 138-1.
Moreover, the service signaling section handler 138-1 includes a service signaling section buffer and a service signaling section parser, and restores and parses NST from the NRT service signaling data to output it to the service manager 160. When the NST is parsed, access information of the FLUTE session that transmits content or files constituting NRT service and signaling information necessary for rendering the NRT service may be extracted. For example, information necessary for rendering content or files of the NRT service, transmitted from the NST to each FLUTE session, may be extracted. Information necessary for rendering the content or files of the NRT service may include container information, encoding information, or decoding parameters of a media object.
The parsed information from the NST is collected by the service manager 160, and then, stored in the first storage unit 180. The service manager 160 stores the extracted information from the NST in the first storage unit 180 in a service map and guide data format. As another example, the NRT service manager 182 may serve as the service manager 160. That is, the parsed information from the NST is collected by the NRT service manager 192, and then, stored in the first storage unit 180.
The ALC or LCT stream hander 151 includes an ALC or LCT stream buffer and an ALC or LCT stream parser, and after buffering data having an ALC or LCT structure outputted from the UDP datagram handler 138, analyzes a header and header extension of an ALC or LCT session from the buffer data. On the basis of the analysis result of the header and header extension of the ALC or LCT session, if data transmitted to the ALC or LCT session has an XML structure, it is outputted to the XML parser 153. If the data has a file structure, after being temporarily stored in the file reconstruction buffer 152, it is outputted to the file decoder 157 or stored in the third storage unit 156. The ALC or LCT stream handler 151 is controlled by the NRT service manager 192 if data transmitted to the ALC or LCT session is data for NRT service. At this point, if data transmitted to the ALC or LCT session is compressed, after decompressed in the decompressor 155, it is outputted to at least one of the XML parser 153, the file decoder 157, and the third storage unit 156.
The XML parser 153 analyzes XML data transmitted through the ALC or LCT session, and if the analyzed data is for a file based service, it is outputted to the FDT handler 154. If the analyzed data is for service guide, it is outputted to the SG handler 190.
The FDT handler 154 analyzes and processes a file description table of the FLUTE protocol through an ALC or LCT session. The FDT handler 154 is controlled by the NRT service manager 192 if the received file is for NRT service.
The SG handler 190 collects and analyzes data for service guide transmitted in the XML structure and then output it to the EPG manager 191.
The file decoder 157 decodes a file outputted from the file reconstruction buffer 152, a file outputted from the decompressor 155, or a file uploaded from the third storage unit 156 through a predetermined algorithm, thereby outputting it to the middleware engine 193 or the A or V decoder 141.
The middleware engine 193 interprets and executes data having a file structure, i.e., application. Moreover, the application may be outputted to a screen or speaker through the presentation manager 195. The middleware engine 193 is a JAVA based middleware engine according to an embodiment.
The EPG manager 191 receives service guide data from the SG handler 190 according to a user input, and then, converts the received service guide data into a display format to output it to the presentation manager 195. The application manager 194 performs general managements on processing application data received in the format such as a file.
The service manager 160 collects and analyzes PSI or PSIP table data or NRT service signaling data transmitted to an NRT service signaling channel to create a service map, and then stores it in the first storage unit 125. Additionally, the service manager 160 controls access information on NRT service that a user wants, and also controls the tuner 111, the demodulator 112, and the IP datagram handler 136.
The operation controller 100 controls at least one of the service manager 160, the PVR manger 170, the EPG manager 191, the NRT service manager 192, the application manager 194, and the presentation manager 195 according to a user command, and thus, performs a function that a user wants.
The NRT service manager 192 performs general management on NRT service transmitted in a content or file format through the FLUTE session on an IP layer.
The UI manager 196 delivers a user input to the operation controller 100 through UI.
The presentation manager 195 provides to a user through at least one of a speaker and a screen at least one of audio or video data outputted from the A or V decoder 141, file data outputted from the middleware engine 193, and service guide data outputted from the EPG manager 191.
Moreover, one of the service signaling section handler 138-1, the service manager 160, and the NRT service manager 192 obtains content constituting the NRT service or IP access information on the FLUTE session transmitting a file, from a FLUTE session loop of NST (or an a component loop of NST). Additionally, the one obtains FLUTE level access information from component_descriptor( ) received in the component loop of the NST.
Then, the ALC or LCT stream handler and the file decoder 157 access the FLUTE file delivery session by using the obtained FLUTE level access information to collect files in the session. Once the files are collected, they constitute one NRT service. This NRT service may be stored in the third storage unit 156, or outputted to the middleware engine 193 or the A or V decoder 141 to be displayed on a display device.
The third storage unit 158, i.e., a storage medium storing a file such as NRT service data, may be shared with the second storage unit 125, or may be separately used.
FIG. 24 is a flowchart illustrating a method of a receiver to receive and provide NRT service according to an embodiment.
The receiver may obtain NRT service signaling information through an NRT service signaling channel or by receiving IP datagram in the case of mobile NRT service, and obtains SMT from the NRT service signaling information in operation S2010.
Then, the receiver obtains NRT service information from SMT in operation S2020. The NRT service information may be obtained by parsing NRT_service_info_descriptor in a service level descriptor loop. The obtained NRT service information may include requirement information on an application type for each NRT service or other NRT services.
Later, the receiver outputs NRT service guide on the basis of the obtained NRT service information in operation S2030. The NRT service guide may include application and service category information on each service. Additionally, detailed information may be further displayed on the basis of each field of NRT service info descriptor. The detailed information may include capacity information on corresponding NRT service according to a storage_requirement field or audio or video codec information on corresponding NRT service according to an audio_codec_type or video_codec_type field. A user may select NRT service to receive and use it on the basis of the information in the service guide.
Then, the receiver obtains identifier (content_id) for content items constituting the selected NRT service from NCT in operation S2040. The receiver obtains NRT_service_id corresponding to the selected NRT service from SMT, obtains NCT having the same NRT_channel_id value as the obtained NRT_service_id, and obtains an identifier (content_id) for content items constituting a corresponding NRT service through the obtained NCT.
Then, the receiver accesses the FLUTE session to receive a file constituting the corresponding content item by using the obtained content item identifier (content_id) in operation S2050. Since each file constituting the content item is matched to TOI or a content location field of FDT in the FLUTE session, the receiver receives a file of a corresponding content item by using the FLUTE session in operation S2060. The receiving of the file may include receiving a corresponding file or object when a Content-ID attribute field for a corresponding file is identical to the obtained content_id after reading FDT in a corresponding FLUTE session.
Additionally, the receiver parses FDT instances in a corresponding FLUTE session to obtain a list of files corresponding to the content item. Moreover, the receiver obtains entry information including a list of files serving as an entry among lists of files.
Lastly, the receiver provides NRT service to a user on the basis of the receiver content item and the list of files corresponding thereto or entry information in operation S2080.
The content downloaded through the NRT service may be used at the timing that a user wants, being separated from real-time broadcasting.
Additionally, after transmitting NRT service in advance and storing it in a receiver, a broadcasting station may designate a content item of the corresponding NRT service, which is executed at the timing of when a specific real-time broadcasting is transmitted or the NRT service is displayed. According to an embodiment of the present invention, the NRT service may include content, which is downloaded in advance linking with real-time broadcasting and executed at the specific timing. Additionally, according to an embodiment of the present invention, the NRT service may include content, which is prepared in advance to execute specific NRT service at the specific timing. An NRT service content triggered at the specific timing linked with real-time broadcasting to execute a specific action for a specific NRT service is called a Triggered Declarative Object (TDO). Accordingly, an NRT service application is classified as a non-real time declarative object (NDO) or a triggered declarative object (TDO) according to whether it is executed at the specific timing.
According to an embodiment of the present invention, a broadcasting station may transmit trigger information on trigging the TDO. The trigger information may include information on performing a specific action for a specific TDO at the specific timing.
Additionally, the trigger information may include trigger signaling data (trigger signaling information) for signaling a trigger, and trigger data constituting a trigger. Additionally, data stream transmitting trigger data may be designated as trigger stream. Also, the trigger data may mean itself.
Such a trigger may include at least one of a trigger identifier for identifying a trigger, a TDO identifier for identifying NRT service for trigger, and action information and trigger time on TDO.
The trigger identifier may be an identifier uniquely identifying a trigger. For example, a broadcasting station may include at least one trigger in broadcasting program information of a predetermined time provided through EIT. In this case, the receiver may perform an action on the trigger target TDO at the timing designated for each trigger on the basis of at least one trigger. At this point, the receiver may identify each trigger by using a trigger identifier.
A TDO identifier may be an identifier for identifying an NRT service content, i.e., a target of trigger. Accordingly, the TDO identifier may include at least one of a trigger NRT service identifier (NRT_service_id), content linkage (content_linkage), and URI or URL of an NRT content item entry. Moreover, the TDO identifier may include a target identifier (target_service_id) for identifying a trigger target TDO described later.
Additionally, TDO action information may include information on action for TDO of a trigger target. The action information may be at least one of execution, termination, and extension commands of the target TDO. Additionally, the action information may include commands for generating a specific function or event in the target TDO. For example, if the action information includes the execution command of the target TDO, a trigger may request the activation of the target TDO to the receiver. Additionally, if the action information includes the extension command of the target TDO, a trigger may notify the receiver that the target TDO would extend. Additionally, if the action information includes the termination command of the target TDO, a trigger may notify the receiver that the target TDO would terminate. Thus, the broadcasting station may control a TDO operation in the receiver according to a real-time content through trigger.
Moreover, a trigger time may mean a time designated for performing (trigging) an action designated for the target TDO. Additionally, the trigger time may be synchronized with video stream in a specific virtual channel in order to link NRT service with real-time broadcasting. Accordingly, the broadcasting station may designate a trigger time with reference to PCR that video stream refers. Accordingly, the receiver may trigger TDO at the timing that the broadcasting station designates with reference to PCR that video stream refers. Moreover, the broadcasting station may signal a trigger with a trigger identifier in a header of video stream in order to transmit accurate trigger time.
Additionally, the trigger time may be designated with UTC time. In the case of UTC time, the trigger time is not a relative time but an absolute time.
The trigger time may be accurate trigger timing or may include an approximate start time. Moreover, the receiver may prepare an action for target TDO in advance before accurate trigger timing by receiving approximate time. For example, the receiver may prepare TDO execution in advance so that TDO operates smoothly at the trigger time.
FIG. 25 is a view illustrating a bit stream syntax of a trigger according to an embodiment.
Here, trigger or trigger data is in a trigger table form, and a corresponding syntax is in an MPEG-2 private section form to help understanding. However, the format of corresponding data may vary. For example, the corresponding data may be expressed in a Session Description Protocol (SDP) format and signaled through a Session Announcement Protocol (SAP) according to another method.
A table_id field is set with 0XTBD arbitrarily, and identifies that a corresponding table section is a table section constituting a trigger.
A section_syntax_indicator field is set with 1 and indicates that the section follows a general section syntax.
A private_indicator field is set with 1.
A section_length field describes that the number of bits remaining in the section to the last of the section from immediately after the section_length field.
A source_id field represents the source of a program related to a virtual channel.
A TTT_version_number field represents version information of a trigger. Additionally, the version information of a trigger represents the version of a trigger protocol. The trigger version information may be used for determining where there is change in a trigger structure or a trigger itself. For example, the receiver determines that there is no trigger change if the trigger version information is identical. Additionally, the receiver determines that there a trigger change if the trigger version information is different. For example, the trigger version information may include a plurality of version numbers, and the receiver may determine whether there is a trigger change on the basis of some of the plurality of version numbers.
A current_next_indicator field represents that a corresponding table section is applicable currently if set with 1.
A section_number field indicates a number of a corresponding table section.
A last_section_number field means a table section of the last and highest number among sections.
A num_triggers_in_section field means the number of triggers in a corresponding table section. The number of triggers in one session may be one or in plurality. Additionally, the next ‘for’ loop is performed as many times as the number of triggers.
A trigger_id field represents an identifier uniquely identifying a trigger.
A trigger_time field represents a time for which a trigger is performed. Moreover, this field may not be included in the session, and in this case, the trigger time may be a time designated from broadcasting stream as mentioned above.
A trigger_action field represents action information of a trigger performed at the trigger time. A trigger action may include at least one of a preparation command for target TDO, a target TDO execution command, a target TDO extension command, and a target TDO termination command. The trigger action may further include a command generating a specific command or event.
A trigger_description_length field represents the length of trigger_description_text.
A trigger_description_text field represents description for a corresponding trigger in a text format.
A service_id_ref field represents an identifier identifying a target TDO of a trigger. Accordingly, for example, a service_id_ref field may indicate an NRT_service_id field of SMT or NST to identify NRT service of a trigger target TDO.
A content_linkage field represents an identifier identifying a target TDO content item of a trigger. For example, a content_linkage field may indicate a content_linkage field of NRT-IT or NCT to identify a target TDO content item of a trigger. Additionally, a service_id_ref field and a content_linkage field may be included in a class for indicating one target TDO.
A num_trigger_descriptors field represents the number of trigger descriptors.
A trigger_descriptor( ) field represents a descriptor including information on a trigger.
When a trigger is in a table format of the MPEG-2 private section, a broadcasting station may transmit one trigger according to a virtual channel.
A first method of a broadcasting station to transmit a trigger may include transmitting 0X1FF stream including the trigger table, i.e., PSIP basic PID. The first method may distinguish the trigger table from other tables by allocating table_id of the trigger table.
Moreover, a second method of transmitting a trigger includes allocating PID corresponding to a trigger table to a Master Guide Table (MGT) and transmitting a corresponding PID stream having the trigger table. The second method processes all tables in a corresponding PID stream by using the trigger table.
Moreover, according to an embodiment, at least one of trigger and trigger signaling information is transmitted through an MPEG-2 Packetized Elementary Stream (PES) in order to designate the accurate timing synchronized with video and audio as a trigger time.
Here, the video and audio synchronization of MPEG-2 PES will be described as follows. A receiver decoder operates in synchronization with a time stamp of a transmitter encoder. The encoder has a main oscillator, called a System Time Clock (STC), and a counter. The STC is included in a specific program and a main clock of program for video and audio encoders.
Moreover, if a video frame or an audio block occurs in an encoder input, STC is sampled. A sampling value and a constant value as much as delay of the encoder and decoder buffers are added to generate display time information, i.e., Presentation Time Stamp (PTS) and then are inserted into the first portion of a picture or audio block. When frame reordering occurs, Decode Time Stamp (DTS) representing a time at which data needs to be decoded in a decoder is inserted. Except for the frame reordering of the B picture, DTS and PTS are same. DTS is additionally required in the case of the frame reordering. When DTS is used, there is PTS always. They may be inserted at an interval of less than about 700 msec. Additionally, it is defined in ATSC that PTS and DTS are inserted at the starting portion of each picture.
Moreover, an output of an encoder buffer includes a time stamp such as Program Clock Reference (PCR) in a transport packet level. Moreover, a PCT time stamp occurs at an interval of less than 100 msec, and is used for synchronizing STC of a decoder and STC of an encoder.
Moreover, video stream and audio stream may have each PTS or DTS corresponding to a common STC, for synchronization of audio stream and the decoder. Accordingly, PTS and DTS indicate when audio stream and video stream are played at each decoding unit, and are used to synchronize audio and video.
For example, a decoder of receiver outputs a PES packet in the received TS stream as a video PES depacketizer, and outputs a PCR value inserted in a TS packet header to a PCR counter. The PCR counter counts 100 of the PCR value and outputs it to a comparison unit. Moreover, the video PES depacketizer outputs a header of a PES packet to a DTS or PTS extractor, buffers Elementary Stream, i.e., image data to be displayed, in an Elementary Stream Buffer&Decoder. The DTS or PTS extraction unit extracts DTS and PTS values from the PES packet header and outputs them to the comparison unit. The comparison unit, if the PCR value inputted from the PCR counter becomes a DTS value or the PCR value of 100 becomes a PTS value, outputs each signal for that to a decoding or display control unit. The decoding or display control unit receives a signal that the PCR value becomes the DTS value from the comparison unit, and decodes the image data buffered in the elementary stream buffer & decoder to store them in a decoded stream memory. Additionally, the decoding or display control unit displays the decoded image data stored in the decoded stream memory through a display unit when receiving the signal that the PCR value becomes the PTS value from the comparison unit
Accordingly, MPEG-2 PES includes PTS and DTS in its header, which synchronize data transmitted during data transmission with one elementary stream (ES) or presentation time between a plurality of ES. This is called a synchronized data stream method.
That is, according to an embodiment, a broadcasting station includes trigger data or trigger stream in the payload of PES and designates trigger time as a PTS value of the PES packet header by using the above synchronized data stream method. In this case, the receiver may trigger a target TDO at the accurate timing according to the PCR value that PTS of PES including a trigger refers. Accordingly, a broadcasting station may synchronize a trigger at the accurate timing of audio and video presentation that the broadcasting station is to trigger by using the PTS of the PES packet header designated as a trigger time and the PTS of the audio and video PES packet header.
Moreover, in relation to the header of the PES stream packet including a trigger, a stream_type value may be 0x06 to indicate a synchronized data stream method, stream_id may indicate a identifier of a predetermined stream, and PES_packet_length may indicate the length of PES stream including the payload of PES stream.
FIG. 26 is a view illustrating a PES structure according to a synchronized data stream method including a trigger according to an embodiment.
As shown in FIG. 26, PES of the synchronized data stream method may include a PES header and PES payload. The PES payload may include a synchronized data packet structure. As mentioned above, the trigger including a trigger table or another type of data may be included in the PES payload of FIG. 26 and then transmitted. Additionally, a broadcasting station may packetize the trigger in an IP datagram format, and may include and transmit the packetized trigger in an IP data area.
FIG. 27 is a view illustrating a synchronized data packet structure of PES payload for transmitting trigger as bit stream syntax according to an embodiment.
As shown in FIGS. 26 and 27, the trigger may be included in the synchronized data packet structure and then transmitted. Detailed description of each field in the structure is as follows.
A data_identifier field is an identifier identifying a type of data included in a PES data packet. This may be set with 0X22 according to a type.
A sub_stream_id field is an identifier (user private) settable by a user.
A PTS_extention_flag field indicates whether there is a PTS_extention field. If this field value is 1, the PTS_extension field may be in the PES_data_packet field. Additionally, this field may be 0 when there is no PTS_extension field.
An output_data_rate_flag field may be set with 0.
A syncnronized_data_packet_header_length field represents the length of an optical field in the PES packet header. This field may be included If the PTS_extention_flag field is 1, and represents the length including synchroziced_data_privete_data_byte(s).
A PTS_extension field extends PTS delivered from the header of a corresponding PES packet. This field may include 9 bit Program Clock Reference (PCR) extension information. Additionally, a receiver may extend the PTS resolution of synchronized data from 11.1 μs (90 kHz), i.e., the MPEG-2 standard, to 37 ns (27 MHz).
A synchronized_data_private_data_byte field represents a payload byte of a synchronized PES packet. If the protocol_encapsulation of DST represents one of synchronized datagram, IP datagram not including LLC or SNAP, and multiprotocol including LLS or SNAP, the synchronized_data_byte field may include one unique datagram. Accordingly, when LLC or SNAP is used, an 8 byte LLC or SNAP header may be shown in only the first 8 byte synchronized_data_byte of the PES packet.
Accordingly, if a broadcasting station includes a trigger in a synchronized data stream (stream_type) of PES and transmits it, a receiver may extract trigger stream from the payload of PES. Additionally, the receiver may perform an action on a target TDO by using the PTS value of the PES header as a trigger time. Accordingly, TDO may be trigged at the accurate timing of a frame unit by synchronizing a trigger on the basis of PTS, i.e., a reference time for presentation synchronization of video and audio. Additionally, when a trigger time is designated with PTS, video and audio synchronization may be easily obtained.
Moreover, trigger signaling information on obtaining trigger stream is transmitted according to an embodiment. A receiver receives trigger signaling information and obtains trigger stream in the synchronized data stream of PES on the basis of the received trigger signaling information.
A method of transmitting trigger signaling information to obtain trigger stream transmitted using synchronized data streaming may vary. One of the following methods is used to transmit trigger signaling information: 1. a transmission method through DST; 2. a transmission method through a service id descriptor; 3. a transmission method through a trigger stream descriptor; and 4. a transmission method by defining a stream type of trigger stream.
According to an embodiment, trigger signaling information may be transmitted through DST for NRT service. DST is a table session for transmitting data service. Since its description and description for its data_service_bytes( ) are identical to those of FIG. 8, overlapping description will be omitted.
The DST may include signaling data for receiving each Elementary Stream (ES) constituting data service. Accordingly, trigger signaling data for receiving trigger stream may be included in DST.
Moreover, each data service may include at least one application, and each application may in an application identification structure including an application identifier such as app_id. Moreover, each application may include at least one data element constituting a corresponding application or data stream.
Accordingly, in order to transmit trigger stream through data service, a broadcasting station includes one trigger stream in a specific virtual channel and transmits it. Moreover, the broadcasting station may include one trigger stream in each application and transmit it. Accordingly, embodiments for transmitting trigger signaling information will be described according to two methods.
When one trigger stream is included a virtual channel, a data service for transmitting trigger stream is called a trigger service. In this case, a broadcasting station may allocate a fixed service identifier (service ID) to a trigger service.
Accordingly, a receiver may identify that one trigger stream is transmitted to a virtual channel when the service identifier has 0X01 as a fixed value.
Here, the broadcasting station may include trigger signaling information in an application identification structure in DST and transmit it.
For example, the broadcasting station adds 0x0001 as an App_id_description field value of DST to set a value that means interactive application for linking NT service such as TDO with a real-time broadcast Additionally, app_id_byte_length may use 3 bytes (0x0003) and app_id_byte may be allocated with 0x01 to indicate that corresponding data service includes trigger stream signaling information.
Accordingly, the receiver receives DST through the above method, and may identify tap( ) including trigger signaling information when app_id_byte_length is 0x0003, app_id_description is 0x0001, and app_id_byte is 0x01. The receiver extracts trigger signaling information including an association_tag value from the identified tap( ) structure, and association_tag_descriptor receives stream having the same PID as the extracted association_tag from data elementary stream (ES) listed in PMT extracted from broadcasting stream in order to receive trigger stream.
As mentioned above, NRT service is signaled through SMR or NST, and may be uniquely identified through 16 bit service identifier (sevice_id). Additionally, content items constituting NRT service may be identified through conent_lengate or a content identifier in NCT or NRT-IT. Accordingly, trigger service may be transmitted like NRT service by extending app_id_byte through DST. For example, app_id_byte may include data combining a service identifier (service id) field of trigger service and a content_linkage field. Accordingly, the first 16 bits of app_id_byte correspond to a service id field in SMT or NST, and the later 32 bits correspond to a content linkage field in NCT or NRT-IT.
As above, the broadcasting station may include trigger signaling information in tap( ) and transmits it through an application identification structure of DST when one stream is included in each channel.
Moreover, according to an embodiment, trigger signaling information may be transmitted through a protocol_encapsulation field of DST. For example, if app_id_byte_length in DST is set with 0x0000, app id is not allocated. If protocol_encapsulation has 0x0F, it indicates that trigger signaling information is included in a corresponding tap( ) structure. Accordingly, a receiver may receive trigger signaling information from the corresponding tap( ) structure if app_id_byte_length is 0x0000 and protocol_encapsulation is 0x0F. Through this, a PID value on PMT indicating trigger stream is obtained and trigger stream is received as mentioned above.
Moreover, according to another embodiment, trigger signaling information may be transmitted through a content type descriptor field of DST.
As shown in FIG. 28, a content type descriptor structure in tap( ) on DST according to an embodiment is as follows.
A descriptorTag may have 0x72 to represent contentTypeDescriptor.
A descriptorLength field represents the total length of a descriptor in a byte unit.
A contentTypeByte field represents a MIME media type value of data referenced by tap connected to the descriptor. The MIME media type is defined in 5 of RFC2045 section [8].
Accordingly, a content type descriptor may be added to a tap( ) structure including trigger signaling information according to an embodiment. Accordingly, a receiver may receive trigger signaling information from the corresponding tap( ) structure if app_id_byte_length is 0x0000 and content type descriptor of the tap( ) structure corresponds to the predetermined content. Through this, a PID value on PMT indicating trigger stream is obtained and trigger stream is received as mentioned above. The MIME media type may be designated with a specific type to identify that there is trigger service signaling information through a content type descriptor.
As mentioned above, one NRT service may be a trigger service for transmitting trigger stream and may transmit respectively different stream to content items in the trigger service. In this case, each application may include one trigger stream.
Accordingly, an embodiment may include trigger stream in each content item of NRT service and may transmit it. In this case, the above-mentioned application identification structure may be used. For example, if app_id_byte_length is 0x0003, it indicates that trigger stream is transmitted through one NRT service by using one service identifier. If app_id_byte_length is 0x0007, it indicates that trigger stream is transmitted by each content item by using a service identifier and content linkage. If defined as above, each trigger stream may be transmitted in correspondence to each NRT service or content item. Since the next stage of a method of transmitting and receiving trigger stream is identical to that of transmitting one trigger stream for each virtual channel, overlapping description will be omitted.
FIG. 29 is a view illustrating a syntax of PMT and service identifier descriptor according to an embodiment.
As shown in FIG. 29, a Program Map Table (PMT) represents information of a program broadcasted in each channel. A Program AssociationTable (PAT), in which ‘packet ID’ is defined as ‘0x00’ and transmitted, may receive PMT by parsing ‘packet ID’ of PMT.
Moreover, a service identifier descriptor may be included in a descriptor loop for each ES of PMT. Then, it may include list information of services in each program element.
A structure of the service identifier descriptor will be described as follows.
A descriptor_tag field indicates that the descriptor is service_id_descriptor( ) and may have 0xC2.
A descriptor_length field represents a byte unit length from this field to the termination of the descriptor.
A service_count field indicates the number of services in a program element having the descriptor.
A service_id field indicates a service identifier in a program element having the descriptor.
According to an embodiment, trigger stream may be transmitted through a well-known IP address. Moreover, in order to signal a trigger, a broadcasting station may include a specific service identifier (service id, for example, 0x01) corresponding trigger stream in a service identifier descriptor and may transmit it. That is, trigger signaling information on receiving trigger stream may be transmitted through a service identifier descriptor. Accordingly, if a service identifier of service_id_descriptor in an ES descriptor loop in an ES loop of PMT is 0x01, the receiver determines that elementray_PID in the ES loop is PID indicating trigger stream and receives the trigger stream through the PID.
FIG. 30 is a view illustrating a trigger stream descriptor according to an embodiment. According to an embodiment, a trigger may be signaled using a trigger stream descriptor. Like the above service identifier descriptor, the trigger stream descriptor may be included in an ES descriptor loop in an ES loop of PMT. Accordingly, if there is trigger stream, a trigger stream descriptor may exist in an ES descriptor loop. If identifying a trigger stream descriptor, a receiver may receive trigger stream by obtaining PID of the trigger stream from elementary_PID in a corresponding ES loop.
Like this, a trigger stream descriptor for transmitting trigger signaling information may include at least one of a service identifier (target service id) of TDO, a trigger target in trigger stream, and an IP address list transmitting trigger stream. The trigger stream descriptor of FIG. 30 is provided according to an embodiment and its structure will be described as follows.
A descriptor_tag field indicates a trigger_stream_descriptor if set with a predetermined value.
A descriptor_length field represents a byte unit length from this field to the termination of the descriptor.
A target_service_count field represents the number of target NRT service (TOD) of at least one trigger in trigger stream.
A target_service_id field represents a service identifier (service_id) of target NRT service (TOD) of at least one trigger in trigger stream. A receiver may identify a service identifier (service_id) before receiving trigger stream by using the target_service_id field.
A target_content_item_count field represents the number of target NRT service content items of at least one trigger in trigger stream.
A target_content_linkage field represents a target NRT service content item linkage (content_linkage) of at least one trigger in trigger stream.
Moreover, a trigger stream descriptor is provided according to an embodiment, and thus, it is apparent that it may include additional information or have another configuration. For example, when one trigger stream is transmitted for each channel, a content item field may be omitted. Additionally, at least one of a trigger stream identification information field and a profile information field may be added to identify trigger stream.
A broadcasting station may transmit list information of trigger target NRT service such as TDO by using the trigger stream descriptor. Additionally, the broadcasting station may transmit trigger signaling information by using the target_service_id and target_content_linkage fields if there is another trigger according to a content item. Additionally, a trigger stream descriptor may further include a list of IP address information or port numbers transmitting trigger stream.
According to an embodiment, a broadcasting station designates a stream type and transmits trigger signaling information. A receiver extracts trigger signaling information by using a stream type from PMT and receives trigger stream through the trigger signaling information. For example, 0x96, one of stream types set preliminarily at the present, may be designated as trigger stream. In this case, a typical receiver has no information that a stream type is 0x96 and thus may not process trigger stream and disregard it. Accordingly, backwards compatibility for sub model receiver is guaranteed.
According to an embodiment, a trigger may be included in an Application information Table (AIT) for transmitting application information in data broadcasting such as Multimedia Home Platform (MHP) or Advanced Common application platform (ACAP), and may be transmitted. FIG. 31 is a view of AIT according to an embodiment.
Moreover, according to another embodiment a trigger may be included in a descriptor of STT to refer to a System Time Table (STT) as a trigger time, and then transmitted. FIG. 32 is a view of STT according to an embodiment.
FIG. 33 is a block diagram illustrating a transmitter for transmitting TDO and a trigger according to an embodiment.
Referring to FIG. 33, the transmitter 200 includes an NRT service transmitting unit 210, a trigger transmitting unit 220, a multiplexing unit 230, and a demodulation unit 240. The NRT service transmitting unit 210 includes an NRT service (TDO) generating unit 211 and an NRT service signaling data generating unit 212. The trigger transmitting unit 220 includes a trigger generating unit 221 and a trigger signaling data generating unit 222.
The NRT service (TDO) generating unit 211 receives data for NRT service generation from a service provider to generate the NRT service, packetizes the generated NRT service into IP datagram, and then packetized the packetized IP datagram into a transmission packet (TP). The packetized NRT service data is transmitted to the multiplexing unit 230.
The NRT service generating unit 211 transmits metadata including channel information about NRT service in transmission and service_id, to the NRT service signaling data generating unit 212. Additionally, if the generated NRT service is TDO, the NRT service generating unit 211 extracts trigger information including a trigger time for triggering TDO, identification information, and trigger action information of a target TDO, and then transmits it to the trigger generating unit 221.
The NRT service signaling data generating unit 212 generates NRT service signaling data for receiving NRT service by using the NRT service metadata, and packetizes the generated NRT service signaling data to the transmission packet (TP) to transmit it to the multiplexing unit 230.
Additionally, the trigger generating unit 221 generates trigger data by using trigger information of the TDO received from the NRT service (TDO) generating unit. The generated trigger data is packetized into a transmission packet to transmit it to the multiplexing unit 230. Moreover, the trigger generating unit 221 transmits metadata for receiving a trigger such as the packet identifier (PID) of the transmitted trigger data to the trigger signaling data generating unit 222.
The trigger signaling data generating unit 22 generates trigger signaling data on the basis of the received metadata, and packetizes the trigger signal in data into a transmission packet to transmit it to the multiplexing unit 230.
The multiplexing unit 230 multiplexes the received transmission packets by each channel, and then transmits the multiplexed signal to the modulation unit 240.
The modulation unit 240 modulates the multiplexed signal and transmits it to the external. The modulation method may vary, and the present invention is not limited thereto.
FIG. 34 is a block diagram illustrating a receiver for receiving TDO and a trigger according to an embodiment.
Referring to FIG. 34, the receiver 300 includes a demodulation unit 310, a demultiplexing unit 320, a trigger processing unit 330, an NRT service processing unit 340, and a service manager 350. The trigger processing unit 330 includes a trigger receiving unit 331 and a trigger signaling data receiving unit 332. The NRT service processing unit 340 includes an NRT service (TDO) receiving unit 341 and an NRT service signaling data receiving unit 342.
The demodulation unit 310 receives a modulated signal from the transmitter 200, and demodulates the received signal according to a predetermined demodulation method to transmit it to the demultiplexing unit 320.
The demultiplexing unit 320 demultiplexes the demodulated signal to restore an original transmission packet for each channel to transmit them to each receiving unit of the trigger processing unit 330 or the NRT service processing unit 340.
The NRT service signaling data receiving unit 342 receives and restores the packetized NRT service signaling data from the multiplexing unit 320 to extract information on NRT service, and then transmits it to the NRT service (TDO) receiving unit 341. The NRT service (TDO) receiving unit 341 receives transmission packets of NRT service from the multiplexing unit 320 by using information on receiving NRT service, and restores it as service data to transmit it to the service manager 350.
Moreover, the NRT service signaling data receiving unit 332 receives and restores the packetized trigger signaling data from the multiplexing unit 320, extract information on receiving a trigger, and then, transmits it to the trigger receiving unit 331. The trigger receiving unit 331 receives transmission packets including a trigger from the multiplexing unit 32 by using information on receiving a trigger, and restores trigger data to transmit it to the service manager 350.
The service manager 350 receives at least one of trigger data or NRT service (TDO) data from the trigger processing unit 330 or the NRT processing unit 340. Moreover, the service manager 350 performs and applies a trigger action on a trigger target TDO at the trigger timing, so that a trigger action on TDO is performed.
FIG. 35 is a flowchart illustrating a trigger transmitting method according to an embodiment.
Referring to FIG. 35, the NRT service generating unit 211 generates NRT service data by receiving NRT service data from external or on the basis of data received from the NRT service provider in operation S100. Moreover, the NRT service generating unit 211 packets the generated data into a transmission packet. Additionally, the NRT service generating unit 211 transmits information on receiving transmission packets including NRT service to the NRT service signaling data generating unit 212.
Then, the NRT service signaling data generating unit 212 generates the above described NRT service signaling data and packetizes it into a transmission packet in operation S110.
Moreover, the NRT service generating unit 211 determines whether the generated NRT service is a trigger declarative object, i.e., TDO in operation S120.
Additionally, if the generated NRT service is TDO, the NRT service generating unit 211 transmits trigger information including a trigger time for triggering TDO, trigger action, target TDO identification information, to the trigger generating unit 221, and the trigger generating unit 211 generates trigger data by using the received triggered information in operation S130. The generated trigger data is packetized into a transmission packet and transmitted to the multiplexing unit. For example, a target service identifier for target TDO and trigger action information applied to a target service may be inserted into a packetized stream, i.e., the payload of PES, and then transmitted. Additionally, trigger time information is designated into a PTS or DTS format, inserted into the payload or header of PES, and then is transmitted. When the synchronized data streaming method is used, PTS of trigger stream and PTS of video and audio stream are synchronized to set the accurate play timing.
Moreover, the trigger signaling data generating unit 222 generates trigger signaling data for identifying and receiving a trigger transmitted from the trigger generating unit 221 and packetized the generated trigger signaling data into a transmission packet to transmit it to the multiplexing unit in operation S140. Here, the trigger signaling data may include a trigger stream descriptor or a service identifier descriptor, inserted in a program map table, and may include a packet identifier of trigger stream corresponding to each descriptor. Additionally, trigger signaling data may include a packet identifier of trigger stream in a TAP structure of DST.
Later, the multiplexing unit 230 multiplexes at least one of transmission-packetized NRT service data, NRT service signaling data, trigger data, and trigger signaling data by each transmission channel and then transmits it to the modulation unit 240.
Moreover, the modulation unit 240 performs modulation to transmit the multiplexed signal and transmits it to external receiver or a broadcasting network in operation S160.
FIG. 36 is a flowchart illustrating an operation of a receiver 300 according to an embodiment.
First, when the receiver 300 is turned on, a channel is selected by a user or a predetermined channel is selected in operation S200. The demodulation unit 310 demodulates the received signal from the selected channel, and the demultiplexing unit 320 demultiplexes the demodulated signal by each transmission channel. Also, the NRT service receiving unit 341 and the NRT service signaling data receiving unit 342 receive NRT service data and transmit it to the service manager 350 as described above.
Then, the trigger signaling data receiving unit 332 or the NRT service signaling data receiving unit 342 confirms whether trigger reception is possible in operation s220. The trigger reception confirmation may use one of the above-mentioned methods. That is, the trigger signaling data receiving unit 332 or the NRT service signaling data receiving unit 342 uses one of a method of confirming PID corresponding to a trigger in MGT or PSIP based PID, a method of using a tap structure of DST, a method of using a service identifier descriptor or a trigger stream descriptor, a method of using a trigger stream type, and a method of using AIT or STT, in order to confirm whether trigger reception is possible.
Moreover, when it is confirmed that trigger reception is possible, the trigger signaling data receiving unit 332 receives a transmission packet including trigger signaling data to restore the trigger signaling data, and then transmits it to the trigger receiving unit 331 in operation S230.
Later, the trigger receiving unit 331 extracts trigger data from the received transmission packet by using the trigger signaling data, and transmits it to the service manager 350 in operation S240. For example, the trigger receiving unit 331 may receive trigger stream by using a packet identifier corresponding to the trigger stream descriptor. Additionally, the trigger receiving unit 331 extracts trigger information from trigger stream and transmits it to the service manager 350. Additionally, if the received trigger stream is PES, PTS in the header of PES is extracted as a trigger time, and a target service identifier and trigger action in the payload of PES are extracted, in order to transmit them to the service manager 350.j 
Moreover, the service manager 350 performs a trigger action on a target TDO at the trigger timing, so that a trigger action on TDO is performed in operation S250. Especially, if the PTS of PES is a trigger time, the PTS of trigger stream is synchronized with the PTS in the header of audio and video stream, to satisfy the accurate play timing.
FIG. 37 is a flowchart illustrating a trigger receiving method by using a trigger table according to an embodiment.
The demodulation unit 310 receives and demodulates a broadcast signal for selected channel. Moreover, the trigger signaling data receiving unit 332 receives a PSIP table through the demultiplexing unit 320 and determines whether there is a trigger table in the received table to identify a trigger service in operation S310. The trigger signaling data receiving unit 332 searches PID allocated to a trigger table from an MGT or PSIP based table, or searches a table corresponding to Table_id allocated to a trigger table to identify a trigger service.
If the trigger service is not identified, the receiver 300 provides general broadcasting services.
Moreover, if the trigger service is identified, the trigger receiving unit 331 receives the searched trigger table and parses it in operations S320 and S330.
Then, the service manger 350 receives trigger information including trigger time, trigger action, and target TDO identification information parsed in the trigger table, and performs a corresponding trigger action on a corresponding TDO at the corresponding trigger timing in operation S340.
FIG. 38 is a flowchart illustrating an operation of a receiver 300 when trigger signaling information and trigger are transmitted using DST according to an embodiment.
When a physical transmission channel is selected in operation S3000 and a channel selected by a tuner is tuned, the receiver 300 obtains VCT and PMT from a broadcast signal received through the tuned physical transmission channel by using the demodulation unit 310 and the demultiplexing unit 320 in operation S3010. Then, the PSI or PSIP section handler or the trigger signaling data receiving unit 332 or the NRT service signaling data receiving unit 342 parses the obtained VCT and PMT to confirm whether there is NRT service.
For example, when the service_type field value of VCT is not 0x04 or 0x08, since the corresponding virtual channel does not transmit NRT only service, the receiver 300 operates properly according to information in the virtual channel. However, even though the service_type field value does not mean NRT only service, the corresponding virtual channel may include NRT service. This case is called adjunct NRT service included in the corresponding virtual channel, and the receiver 300 may perform the same process as the case of receiving NRT service.
Then, the NRT service signaling data receiving unit 342 or the trigger signaling data receiving unit 332 determines that NRT service is received through a corresponding virtual channel if a service_type field value is 0x04 or 0x08. In this case, if a stream_type field value in a service location descriptor of VCT (or an ES loop of PMT) is 0x95 (i.e., DST transmission), DST is received using an Elementary_PID field value in operation S3020. This may be performed in the demultiplexing unit 320 according to a control of the service manager 350.
Also, the trigger signaling data receiving unit 342 identifies a trigger service from the received DST in operation S3040. A method of identifying a trigger service uses one of a method of identifying a specific value allocated to app_id_description and app_id_byte by using an application identification structure, a method of identifying a specific value allocated to a protocol_encapsulation field, and a method of identifying tap including a content type descriptor.
If the trigger service is not identified from the received DST, since trigger data transmits general NRT service through a corresponding virtual channel, the receiver 300 operates properly according to NRT service in the corresponding virtual channel in operation S3030.
Moreover, when the trigger service is identified from DST, the trigger signaling data receiving unit 332 extracts tap from DST including trigger signaling information (PID of trigger stream) in operation S3060.
Then, the trigger signaling data receiving unit 332 extracts stream PID from PMT including association_tag of the extracted Tap in operation S3070.
The trigger receiving unit 331 receives MPEG-2 TS packets corresponding to the extracted stream PID, and removes decapsulation, i.e., TS header, to restore PES stream including trigger stream. The stream_type of a PES packet including trigger stream may be 0x06 representing synchronized data stream. The trigger receiving unit 331 parses at least one of PTS of a PES packet header from the restored PES stream, a target TDO identifier in trigger stream, a trigger identifier, or trigger action information in operation S3070.
Then, the service manager 350 performs an action on the target TDO at the trigger timing by using the PTS of the PES packet header including a trigger as the trigger timing in operation S3080. Here, the target TDO may be NRT service indicated by the parsed target TDO identifier. Additionally, the action may be one of preparation, execution, extension, and termination commands provided from the parsed trigger action information.
FIG. 39 is a flowchart illustrating an operation of a receiver 300 when a trigger is transmitted using a trigger stream descriptor according to an embodiment.
When a physical transmission channel is selected in operation S3000 and a channel selected by a tuner is tuned, the receiver 300 obtains VCT and PMT from a broadcast signal received through the tuned physical transmission channel by using the demodulation unit 310 and the demultiplexing unit 320 in operation S4000. The broadcast signal includes VCT and PMT, and the trigger signaling data receiving unit 332 or the PSI or PSIP section handler parses the obtained VCT and PMT.
Also, the trigger signaling data receiving unit 332 confirms whether a trigger is transmitted from the VCT and PMT to a corresponding virtual channel. For this, the trigger signaling data receiving unit 332 determines whether there is the Trigger_stream_descriptor in the ES descriptor loop corresponding to a corresponding virtual channel in operation S4020. Whether there is Trigger_stream_descriptor is determined by using whether a stream_type value is 0x06 (synchronized data streaming) and a descriptor_tag field of a corresponding descriptor is identical to a value set to correspond to a trigger stream descriptor after searching descriptors in an ES descriptor loop.
If it is determined that Trigger_stream_descriptor is not identified from PMT and thus there is no Trigger_stream_descriptor, since a corresponding virtual channel does no transmit a trigger, the receiver 300 operates properly according to broadcast service in the corresponding virtual channel in operation S4025.
Then, if there is Trigger_stream_descriptor, the trigger signaling data receiving unit 332 extracts Elementary_PID in the corresponding ES loop of PMT in operation S4030. The extracted stream PID may be a PID value of stream including trigger stream.
Then, the trigger receiving unit 331 receives MPEG-2 TS packets corresponding to the extracted stream PID, and performs decapsulation (i.e., removes a TS header) to restore PES stream including trigger stream. The stream_type of a PES packet including trigger stream may be 0x06 representing synchronized data stream. The trigger receiving unit 331 parses at least one of PTS of a PES packet header from the restored PES stream, a target TDO identifier in trigger stream, a trigger identifier, or trigger action information in operation S4040.
Then, the service manager 350 performs an action on the target TDO at the trigger timing by using the PTS of the PES packet header including a trigger as the trigger timing in operation S4050. Here, the target TDO may be NRT service indicated by the parsed target TDO identifier. Additionally, the action may be one of preparation, execution, extension, and termination commands provided from the parsed trigger action information.
FIG. 40 is a flowchart illustrating an operation of a receiver when a trigger is transmitted using a stream type according to an embodiment.
When a physical transmission channel is selected and a channel selected by a tuner is tuned, the receiver 300 obtains VCT and PMT from a broadcast signal received through the tuned physical transmission channel by using the demodulation unit 310 and the demultiplexing unit 320. The broadcast signal includes VCT and PMT, and the trigger signaling data receiving unit 332 or the PSI or PSIP section handler parses the obtained VCT and PMT in operation S400.
Also, the trigger signaling data receiving unit 332 confirms whether a trigger is transmitted from the VCT and PMT to a corresponding virtual channel. For this, the trigger signaling data receiving unit 332 determines whether there is 0x96, i.e., the specific stream type in the ES descriptor loop corresponding to a corresponding virtual channel in operation S410.
If it is determined that 0x96 is not identified from stream type and thus there is no stream type, since a corresponding virtual channel does no transmit a trigger, the receiver 300 operates properly according to broadcast service in the corresponding virtual channel in operation S415.
Then, if the stream type is 0x96, the trigger signaling data receiving unit 332 extracts Elementary_PID in the corresponding ES loop of PMT in operation S420. The extracted stream PID may be a PID value of stream including trigger stream.
Then, the trigger receiving unit 331 receives MPEG-2 TS packets corresponding to the extracted stream PID, and performs decapsulation (i.e., removes a TS header) to restore PES stream including trigger stream. The trigger receiving unit 331 parses at least one of PTS of a PES packet header from the restored PES stream, a target TDO identifier in trigger stream, a trigger identifier, or trigger action information in operation S430.
Then, the service manager 350 performs an action on the target TDO at the trigger timing by using the PTS of the PES packet header including a trigger as the trigger timing in operation S440. Here, the target TDO may be NRT service indicated by the parsed target TDO identifier. Additionally, the action may be one of preparation, execution, extension, and termination commands provided from the parsed trigger action information.
FIG. 41 is a flowchart illustrating an operation of a receiver when a trigger is transmitted using AIT according to an embodiment.
The trigger signaling data receiving unit 332 receives AIT by using the demodulation unit 310 and the demultiplexing unit 320 in operation S500.
Also, the trigger signaling data receiving unit 332 confirms whether a trigger is transmitted from AIT. For this, the trigger signaling data receiving unit 332 confirms whether there is a trigger descriptor in AIT in operation S510.
If it is determined that there is no trigger descriptor, since a corresponding application does not include a trigger, the receiver 300 operates properly according to corresponding application service in operation 5515.
Also, if there is a trigger descriptor, the trigger receiving unit 332 extracts trigger data from the trigger descriptor and parses the extracted trigger data to transmit it to the service manager 350 in operation S530.
Then, the service manager 350 performs an action on the target TDO at the trigger timing by using the parsed trigger data in operation S540. Here, the target TDO may be NRT service indicated by the parsed target TDO identifier. Additionally, the action may be one of preparation, execution, extension, and termination commands provided from the parsed trigger action information.
FIG. 42 is a flowchart illustrating an operation of a receiver when a trigger is transmitted using STT according to an embodiment.
The trigger signaling data receiving unit 332 receives STT by using the demodulation unit 310 and the demultiplexing unit 320 in operation S600.
Also, the trigger signaling data receiving unit 332 confirms whether a trigger is transmitted from STT. For this, the trigger signaling data receiving unit 332 confirms whether there is a trigger descriptor in STT in operation S610.
If it is determined that there is no trigger descriptor, since a corresponding STT does not include a trigger, the receiver 300 operates properly according to a broadcast signal in operation S615.
Also, if there is a trigger descriptor, the trigger receiving unit 332 extracts trigger data from the trigger descriptor and parses the extracted trigger data to transmit it to the service manager 350 in operation S630.
Then, the service manager 350 performs an action on the target TDO at the trigger timing by using the parsed trigger data in operation S540. Here, the target TDO may be NRT service indicated by the parsed target TDO identifier. Additionally, the action may be any one of preparation, execution, extension, and termination commands provided from the parsed trigger action information.
TDO-Auto Deleting Content:10FPDTV423US
As describe above, a receiver 300 according to an embodiment may automatically delete the TDO received from a transmitter 200 and stored according to deleting information.
For example, a specific TDO such as a popularity vote TDO at the end of the year award program, a TDO for donation at a special charity event program, a best player vote TDO at a sport matching game, or a TDO at a specific movie program may be downloaded from the transmitter 200 and stored in the receiver 300.
Alternatively, a TDO at a documentary program broadcasted a plurality of times may be downloaded from the transmitter 200 and stored in the receiver 300 so as to be executed as many as broadcasted.
In the above described case, after the corresponding TDO is executed once or a plurality of times, the TDO stored in the receiver 300 may be no longer used. Accordingly, the TDO may be automatically deleted inside the receiver 300 without user's selection after executed a predetermined number of times.
Moreover, during execution of a TDO, since a corresponding channel is selected by a user, it is difficult to confirm whether the TDO is executed a predetermined number of times.
Therefore, according to an embodiment, the above described deleting information of the TDO may be set in a time unit.
In addition, for a TDO to be executed during a specific period such as a TDO used during a world cup season, a TDO used in a festival period of a specific city, a TDO used on national holidays, holidays, or election days, or a TDO used during vacation, the deleting information for the TDO may set to be automatically deleted in a day unit in the receiver 300 after a specific period.
FIG. 43 is a view illustrating a bit stream syntax of a trigger formed according to another embodiment, wherein the above described deleting information is added to the bit stream syntax of the trigger described in relation to FIG. 25.
Referring to FIG. 43, for the TDO terminated after being executed a predetermined number of times (or after a specific time or day), trigger data may include the deleting information, and the deleting information may include an Auto Deleting Type field and an Auto Deleting info field.
The Auto Deleting Type field indicates a scheme for deleting a corresponding TDO, and may have, for example, a value corresponding to any one of a ‘Normal’ type, a “Run Hour type’, and a ‘Run Day’ type.
For example, the Auto Deleting Type field includes 2 bits, and a value thereof may be designated as ‘00’ for the ‘Normal’ type, ‘01’ for the ‘Run Hour’ type, and ‘10’ for the ‘Run day’ type.
Also, in a case where a value of the Auto Deleting Type field is designated as ‘11’, the field may indicate TBD.
More specifically, in case of the ‘Normal’ type, the TDO stored in the receiver 300 may be deleted according to a criterion of the receiver 300 or a TDO action, not according to an automatic deleting method according to an embodiment.
For example, when a memory of the receiver 300 where NRT content such as the TDO is stored becomes a full state, the oldest content or content executed the longest time ago from among contents stored in the memory of the receiver 300 may be deleted, and replaced with a newly downloaded content.
Alternately, in a full state of the memory, information about content to be newly downloaded is provided to a user of the receiver 300. When the user allows the corresponding content to be downloaded, information about the contents stored in the memory of the receiver 300 is classified into each category to be provided. Then the user may request for deleting contents (or some of them) corresponding to a specific category.
Moreover, the above described categories may be divided for each broadcasting company's content, or each kind of content, or may be arranged for capacity or for a date to be provided to the user.
The ‘Run Hour’ type allows the corresponding TDO to be automatically deleted in the receiver 300 after a preset time has passed, and the ‘Run Date’ type allows the corresponding TDO to be automatically deleted in the receiver 300 after the preset number of days has passed.
The deleting time information for indicating a time when the TDO is to be automatically deleted according to the ‘Run Hour’ type or the ‘Run Date’ type may be included in the Auto Deleting info field.
For example, the Auto Deleting info field includes 14 bits, wherein the ‘Run Hour’ type may include deleting time information for an hour, and the ‘Run Date’ type may include deleting time information for a day.
That is, for the ‘Run Hour’ type, when a value of the Auto Deleting info field indicates ‘2’, the corresponding TDO may be automatically deleted in the receiver 300 after two hours have passed from a time when the corresponding TDO is downloaded.
Moreover, for the ‘Run Date’ type, when a value of the Auto Deleting info field indicates ‘2’, the corresponding TDO may be automatically deleted in the receiver 300 after two days have passed from a time when the corresponding TDO is downloaded.
As described above, in relation to FIG. 43, it is exemplarily described that the deleting information for automatically deleting the TDO stored in the receiver 300 is included in trigger data and transferred from the transmitter 200, but not limited thereto.
For example, the above described deleting information may be included in a TDO or metadata (for example, one or more tables from among NRT service signaling tables described in relation to FIGS. 1 to 21) for the TDO, transmitted from the transmitter 200.
However, when content of the deleting information included in the TDO transmitted from the transmitter 200 changes, the deleting information about the changed content may be transferred to the receiver 300 by using the trigger data as described in relation to FIG. 43.
For example, when a TDO is desired to be deleted after the transmitter 200 has deleting information set to be the ‘Normal’ type included in the TDO and transmits the TDO, deleting information having an automatic deleting time designated according to the ‘Run Hour’ type or the ‘Run Date’ type may be included in trigger data and then transmitted to the receiver 300.
On the contrary, an described above, deleting time information (for example, an Auto Deleting info field value) included in the deleting information may be set or changed according to a relationship with a download time of NRT content.
FIG. 44 is a view illustrating an embodiment of a method of setting deleting time information.
Referring to FIG. 44. when a transmission time of NRT (T1), which is NRT content (for example, a TDO), is in ‘N’ time to ‘N+2’ time, the deleting time information may be set to be different values according to a corresponding period.
For example, when the deleting time information is set for the NRT(T1) to be automatically deleted after M hours from ‘N’ time, which is a first download time, the deleting time information included in trigger data (or NRT(T1)) transmitted from the transmitter 200 after ‘N+1’ time may be changed to ‘M−l’.
Also, the deleting time information included in trigger data (or NRT(T1)) transmitted from the transmitter 200 after ‘N+2’ time may be changed to ‘M−2’.
Moreover, when NRT content such as the TDO is retransmitted during a time period beyond 24 hours, day unit information included in the deleting time information may be identically set or changed to the hour unit information.
FIG. 45 is a flow chart illustrating a TDO deleting method according to an embodiment. In the illustrated TDO deleting method, the same descriptions as those in relation to FIGS. 43 and 44 are omitted.
Referring to FIG. 45, the receiver 300 receives the TDO and trigger data and stored them (operation S4100), and confirm that the deleting information exists in the received TDO or trigger data (operation S4110).
The deleting information may have the same configuration as described in relation to FIG. 43, and be included in the TDO or the trigger data to be transmitted from the transmitter 200.
Thereafter, the deleting information is extracted from the received data (operation S4120) and updated (operation S4130).
For example, the receiver 300 may extract the deleting information from a TTT table or the TDO itself received from the transmitter 200, and update the deleting time information for the stored TDO according the consecutively extracted deleting information.
In this case, the updated deleting time information may be stored in the receiver 300 together with identification information (for example, a TDO ID) for the corresponding TDO in a non-volatile memory, since the storage is to be maintained even when power of the receiver 300 becomes off.
Thereafter, the receiver 300 determines whether a current time obtained by a system timer is the same as the deleting time information, and confirms that it is time to delete the stored TDO (operation S4140).
When it is not time to delete the TDO, the receiver 300 continuously confirms that it is time to delete, while repeating operations S4110 to S4130 for the trigger data transmitted form the transmitter 200.
Moreover, when the deleting information is included in the TDO, the deleting information may be updated only once.
When it is time to delete, the receiver 300 searches for TDO to be deleted by using identification information stored together with corresponding deleting time and deletes it (operation S4150). Meta data (for example, including trigger data for the TDO) related to the TDO may also be deleted together with the TDO from the receiver 300.
TDO+ACR Content: 10FPDTV41OUS
Content such as the TDO transferred from the transmitter 200 to the receiver 300 through an NRT service by using the method described in relation to FIGS. 1 to 24, may be transferred to the receiver 300 through another interface using the internet.
In addition, trigger information transferred from the transmitter 200 to the receiver 300 through a broadcast stream as described in relation to FIGS. 25 to 32, may be transferred to the receiver 300 through another interface using the internet.
The receiver 300 according to an embodiment may obtain information necessary for receiving content such as a TDO or trigger information through another interface such as the internet by using automatic content recognition (ACR) mechanism.
For example, when the receiver 300 receives a broadcast stream only including uncompressed AV data through a cable or from a satellite set-top box, the receiver 300 may not know information about the received content, and NRT content such as the TDO or the trigger information transmitted from the transmitter 200 together with the broadcast stream may not be transferred to the receiver 300.
In the above described case, in order to receive the enhanced service as described in relation to FIGS. 1 to 42, the receiver 300 may obtain information about currently received channels and information about content forming the enhanced service by using the ACR mechanism.
Thereafter, the receiver 300 may receive content through the internet by using the obtained channel and content information, and play the received content.
For example, the content information may include connection information for receiving corresponding content or metadata related thereto, and the connection information may be an address (URL) of a server which provides the content or the metadata.
Moreover, the metadata may include signaling information about the enhanced service provided by using corresponding content.
Accordingly, the receiver 300 may connect to the server by using the URL included in the content information to receive signaling information for the enhanced service, and receive the content by using the received signaling information.
According to an embodiment, the received content may be needed to provide the enhanced service linked to the corresponding channel, and may be, for example, the TDO described in relation to FIGS. 1 to 45.
Moreover, the trigger information as described in FIGS. 1 to 45 may be necessary for playing the content such as the TDO, and the trigger information may also be received to the receiver 300 through the internet by using the channel information and content information obtained by the ACR mechanism.
Hereafter, a method of receiving content and trigger information for an enhanced service by using ACR mechanism by the receiver 300 will be described in relation to FIGS. 46 to 55.
Hereinafter, an video display device including a playing module for a video output or an audio output is exemplarily described as an embodiment, but it is not limited thereto, and various types of display apparatuses capable of providing the enhanced service may be applied to the receiver 300.
Also, hereinafter, as content forming the enhanced service, the TDO described in relation to FIGS. 1 to 45 is exemplified, but the embodiment is applicable to various contents other than the TDO.
FIG. 46 is a block diagram illustrating the network topology according to the embodiment.
As shown in FIG. 46, the network topology includes a content providing server 710, a content recognizing service providing server 720, a multi channel video distributing server 730, an enhanced service information providing server 740, a plurality of enhanced service providing servers 750, a broadcast receiving device 760, a network 770, and an video display device 800.
The content providing server 710 may correspond to a broadcasting station and broadcasts a broadcast signal including main audio-visual contents. The broadcast signal may further include an enhanced service. The enhanced service may or may not relate to main audio-visual contents. The enhanced service may have formats such as service information, metadata, additional data, compiled execution files, web applications, Hypertext Markup Language (HTML) documents, XML documents, Cascading Style Sheet (CSS) documents, audio files, video files, ATSC 2.0 contents, and addresses such as Uniform Resource Locator (URT.). There may be at least one content providing server.
According to an embodiment, the enhanced services may be achieved by receiving contents such as a TDO to store them and playing at a specific time according to trigger information.
In this case, ATSC 2.0 content included in the enhanced service may be the TDO, and the enhanced service may include service information, metadata, or the trigger information as enhanced data.
Moreover, the content recognizing service providing server 720 provides a content recognizing service that allows the video display device 800 to recognize content on the basis of main audio-visual content. The content recognizing service providing server 720 may or may not edit the main audio-visual content. There may be at least one content recognizing service providing server.
The content recognizing service providing server 720 may be a watermark server that edits the main audio-visual content to insert a visible watermark, which may look a logo, into the main audio-visual content. This watermark server may insert the logo of a content provider at the upper-left or upper-right of each frame in the main audio-visual content as a watermark.
Additionally, the content recognizing service providing server 720 may be a watermark server that edits the main audio-visual content to insert content information into the main audio-visual content as an invisible watermark.
Additionally, the content recognizing service providing server 720 may be a fingerprint server that extracts feature information from some frames or audio samples of the main audio-visual content and stores it. This feature information is called signature.
According to an embodiment, the content recognizing service providing server 720 may transfer an address (URL) of an enhanced service information providing server which provides enhanced service related information together with information about a currently viewed channel to the video display device 800.
The multi channel video distributing server 730 receives and multiplexes broadcast signals from a plurality of broadcasting stations and provides the multiplexed broadcast signals to the broadcast receiving device 760. Especially, the multi channel video distributing server 730 performs demodulation and channel decoding on the received broadcast signals to extract main audio-visual content and enhanced service, and then, performs channel encoding on the extracted main audio-visual content and enhanced service to generate a multiplexed signal for distribution.
At this point, since the multi channel video distributing server 730 may exclude the extracted enhanced service or may add another enhanced service, a broadcasting station may not provide services led by it. There may be at least one multi channel video distributing server.
The broadcast receiving device 760 may tune a channel selected by a user and receives a signal of the tuned channel, and then, performs demodulation and channel decoding on the received signal to extract a main audio-visual content. The broadcasting device 760 decodes the extracted main audio-visual content through H.264 or Moving Picture Experts Group-4 advanced video coding (MPEG-4 AVC), Dolby AC-3 or Moving Picture Experts Group-2 Advanced Audio Coding (MPEG-2 AAC) algorithm to generate an uncompressed main audio-visual (AV) content. The broadcast receiving device 760 provides the generated uncompressed main AV content to the video display device 800 through its external input port.
The enhanced service information providing server 740 provides enhanced service information on at least one available enhanced service relating to a main AV content in response to a request of an video display device 800. There may be at least one enhanced service providing server. The enhanced service information providing server 740 may provide enhanced service information on the enhanced service having the highest priority among a plurality of available enhanced services.
According to an embodiment, enhanced service information provided by the enhanced service information providing server 740 may include an address (URL) of the enhanced service providing server 750 providing content such as a TDO, or a address of the enhanced service providing server 750 providing trigger information.
In addition, the enhanced service providing server 750 provides at least one available enhanced service relating to a main AV content in response to a request of an video display device. There may be at least one enhanced service providing server.
According to an embodiment, the enhanced service providing server 750 provides content such as the TDO or the trigger information, and the content such as the TDO or the trigger information may be provided through the single enhanced service providing server 750 or two or more enhanced service providing servers 750.
The video display device 800 may be a television, a notebook computer, a hand phone, and a smart phone, each including a display unit. The video display device 800 may receive an uncompressed main AV content from the broadcast receiving device 760 or a broadcast signal including an encoded main AV content from the contents providing server 710 or the multi channel video distributing server 730.
The video display device 800 may receive a content recognizing service from the content recognizing service providing server 20 through the network 770, an address of at least one available enhanced service relating to a main AV content from the enhanced service information providing server 740 through the network 770, and at least one available enhanced service relating to a main AV content from the enhanced service providing server 750.
At least two of the content providing server 710, the content recognizing service providing server 720, the multi channel video distributing server 730, the enhanced service information providing server 740, and the plurality of enhanced service providing servers 750 may be combined in a form of one server and may be operated by one provider.
FIG. 47 is a block diagram illustrating a watermark based network topology according to an embodiment.
As shown in FIG. 47, the watermark based network topology may further include a watermark server 721.
As shown in FIG. 47, the watermark server 721 edits a main AV content to insert content information into it. The multi channel video distributing server 730 may receive and distribute a broadcast signal including the modified main AV content. Especially, a watermark server may use a digital watermarking technique described below.
A digital watermark is a process for inserting information, which may be almost undeletable, into a digital signal. For example, the digital signal may be audio, picture, or video. If the digital signal is copied, the inserted information is included in the copy. One digital signal may carry several different watermarks simultaneously.
In visible watermarking, the inserted information may be identifiable in a picture or video. Typically, the inserted information may be a text or logo identifying a media owner. If a television broadcasting station adds its logo in a corner of a video, this is an identifiable watermark.
In invisible watermarking, although information as digital data is added to audio, picture, or video, a user may be aware of a predetermined amount of information but may not recognize it. A secret message may be delivered through the invisible watermarking.
One application of the watermarking is a copyright protection system for preventing the illegal copy of digital media. For example, a copy device obtains a watermark from digital media before copying the digital media and determines whether to copy or not on the bases of the content of the watermark.
Another application of the watermarking is source tracking of digital media. A watermark is embedded in the digital media at each point of a distribution path. If such digital media is found later, a watermark may be extracted from the digital media and a distribution source may be recognized from the content of the watermark.
Another application of invisible watermarking is a description for digital media.
A file format for digital media may include additional information called metadata and a digital watermark is distinguished from metadata in that it is delivered as an AV signal itself of digital media.
The watermarking method may include spread spectrum, quantization, and amplitude modulation.
If a marked signal is obtained through additional editing, the watermarking method corresponds to the spread spectrum. Although it is known that the spread spectrum watermark is quite strong, not much information is contained because the watermark interferes with an embedded host signal.
If a marked signal is obtained through the quantization, the watermarking method corresponds to a quantization type. The quantization watermark is weak, much information may be contained.
If a marked signal is obtained through an additional editing method similar to the spread spectrum in a spatial domain, a watermarking method corresponds to the amplitude modulation.
FIG. 48 is a ladder diagram illustrating a data flow in a watermark based network topology according to an embodiment.
First, the content providing server 710 transmits a broadcast signal including a main AV content and an enhanced service in operation S701.
The watermark server 721 receives a broadcast signal that the content providing server 710 provides, inserts a visible watermark such as a logo or watermark information as an invisible watermark into the main AV content by editing the main AV content, and provides the watermarked main AV content and enhanced service to the MVPD 730 in operation S703.
The watermark information inserted through an invisible watermark may include at least one of a watermark purpose, content information, enhanced service information, and an available enhanced service. The watermark purpose represents one of illegal copy prevention, viewer ratings, and enhanced service acquisition.
The content information may include at least one of identification information of a content provider that provides main AV content, main AV content identification information, time information of a content interval used in content information acquisition, names of channels through which main AV content is broadcasted, logos of channels through which main AV content is broadcasted, descriptions of channels through which main AV content is broadcasted, a usage information reporting period, the minimum usage time for usage information acquisition, and available enhanced service information relating to main AV content.
According to an embodiment, content information inserted into the watermark may include channel information, an address (URL) of a server to be first connected to obtain content such as a TDO, or trigger information included in an enhanced service related to corresponding channel, and a timestamp which is viewing time information.
For example, if the video display device 800 uses a watermark to acquire content information, the time information of a content interval used for content information acquisition may be the time information of a content interval into which a watermark used is embedded.
If the video display device 800 uses a fingerprint to acquire content information, the Lime information of a content interval used for content information acquisition may be the time information of a content interval where feature information is extracted. The time information of a content interval used for content information acquisition may include at least one of the start time of a content interval used for content information acquisition, the duration of a content interval used for content information acquisition, and the end time of a content interval used for content information acquisition.
The usage information reporting address may include at least one of a main AV content watching information reporting address and an enhanced service usage information reporting address. The usage information reporting period may include at least one of a main AV content watching information reporting period and an enhanced service usage information reporting period. A minimum usage time for usage information acquisition may include at least one of a minimum watching time for a main AV content watching information acquisition and a minimum usage time for enhanced service usage information extraction.
On the basis that a main AV content is watched for more than the minimum watching time, the video display device 800 acquires watching information of the main AV content and reports the acquired watching information to the main AV content watching information reporting address in the main AV content watching information reporting period.
On the basis that an enhanced service is used for more than the minimum usage time, the video display device 100 acquires enhanced service usage information and reports the acquired usage information to the enhanced service usage information reporting address in the enhanced service usage information reporting period.
The enhanced service information may include at least one of information on whether an enhanced service exists, an enhanced service address providing server address, an acquisition path of each available enhanced service, an address for each available enhanced service, a start time of each available enhanced service, an end time of each available enhanced service, a lifetime of each available enhanced service, an acquisition mode of each available enhanced service, a request period of each available enhanced service, priority information each available enhanced service, description of each available enhanced service, a category of each available enhanced service, a usage information reporting address, a usage information reporting period, and the minimum usage time for usage information acquisition.
The acquisition path of available enhanced service may be represented with IP or Advanced Television Systems Committee—Mobile or Handheld (ATSC M or H). If the acquisition path of available enhanced service is ATSC M or H, enhanced service information may further include frequency information and channel information. An acquisition mode of each available enhanced service may represent Push or Pull.
Moreover, the watermark server 721 may insert watermark information as an invisible watermark into the logo of a main AV content.
Moreover, the watermark server 721 may insert a barcode at a predetermined position of a logo. At this point, the predetermined position of the logo may correspond to the first line at the bottom of an area where the logo is displayed. The video display device 800 may not display a barcode when receiving a main AV content including a logo with the barcode inserted.
Moreover, the watermark server 721 may insert watermark information in a metadata form of a logo. At this point, the log may maintain its form.
Moreover, the watermark server 721 may insert N-bit watermark information at each of the logos of M frames. That is, the watermark server 721 may insert M*N watermark information in M frames.
The MVPD 730 receives broadcast signals including watermarked main AV content and enhanced service and generates a multiplexed signal to provide it to the broadcast receiving device 760 in operation S705. At this point, the multiplexed signal may exclude the received enhanced service or may include new enhanced service.
The broadcast receiving device 760 tunes a channel that a user selects and receives signals of the tuned channel, demodulates the received signals, performs channel decoding and AV decoding on the demodulated signals to generate an uncompressed main AV content, and then, provides the generated uncompressed main AV content to the video display device 800 in operation S706.
Moreover, the content providing server 710 also broadcasts a broadcast signal including a main AV content through a wireless channel in operation S707. Additionally, the MVPD 730 may directly transmit a broadcast signal including a main AV content to the video display device 800 without going through the broadcast receiving device 760 in operation S708.
The video display device 800 may receive an uncompressed main AV content through the broadcast receiving device 760. Additionally, the video display device 800 may receive a broadcast signal through a wireless channel, and then, may demodulate and decode the received broadcast signal to obtain a main AV content. Additionally, the video display device 800 may receive a broadcast signal from the MVPD 730, and then, may demodulate and decode the received broadcast signal to obtain a main AV content.
The video display device 800 extracts watermark information from audio samples in some frames or intervals of the obtained main AV content. If watermark information corresponds to a logo, the video display device 800 confirms a watermark server address corresponding to a logo extracted from a corresponding relationship between a plurality of logos and a plurality of watermark server addresses.
When the watermark information corresponds to the logo, the video display device 800 cannot identify the main AV content only with the logo. Additionally, when the watermark information does not include content information, the video display device 800 cannot identify the main AV content but the watermark information may include content provider identifying information or a watermark server address. When the watermark information includes the content provider identifying information, the video display device 800 may confirm a watermark server address corresponding to the content provider identifying information extracted from a corresponding relationship between a plurality of content provider identifying information and a plurality of watermark server addresses.
In this manner, when the video display device 800 cannot identify a main AV content only with the watermark information, it accesses the watermark server 721 corresponding to the obtained watermark server address to transmit a first query in operation S709.
The watermark server 721 provides a first reply to the first query in operation S711. The first reply may include at least one of content information, enhanced service information, and an available enhanced service.
According to an embodiment, the video display device 800 may obtain information about currently viewed channel by using an ACR mechanism which uses watermarking according to the operations as described above. The obtained information may include information about the viewed channel, an address (URL) of the enhanced service information providing server 740 providing information necessary for obtaining an enhanced service related to the viewed channel, and a timestamp which is time information.
If the watermark information and the first reply do not include an enhanced service address, the video display device 800 cannot obtain enhanced service. However, the watermark information and the first reply may include an enhanced service address providing server address. In this manner, if the video display device 800 does not obtain a enhanced service address or enhanced service through the watermark information and the first reply and the video display device 100 obtains an enhanced service address providing server address, it accesses the enhanced service information providing server 740 corresponding to the obtained enhanced service address providing server address Lto transmit a second query including content information in operation S719.
The enhanced service information providing server 740 searches at least one available enhanced service relating to the content information of the second query. Later, the enhanced service information providing server 740 provides to the video display device 800 enhanced service information for at least one available enhanced service as a second reply to the second query in operation S721.
According to an embodiment, the enhanced service information may include metadata having information necessary for obtaining content such as a TDO forming a corresponding enhanced service or trigger information.
For example, the metadata may include one or more signaling tables, and the signaling tables an address (for example, a URL of the enhanced service providing server 50) of a server providing content such as the TDO and an address (for example, a URL of the enhanced service providing server 50) of a server providing the trigger information.
Moreover, the signaling tables may include at least one of NRT service signaling tables as described in relation to FIGS. 1 to 21, for example an NRT service map table (SMT), an NRT information table (NRT-IT), and a text fragment table (TFT).
In this case, the address (URL) of the server providing the content such as the TDO may be included in any one of the NRT service signaling tables. For example, a URL of the enhanced service providing server 750 providing the content may be included in the NRT-IT.
Moreover, the address (URL) of the server providing the trigger information may be included in any one of the NRT service signaling tables, and the table including the address (URL) of the server providing the trigger information may be the same as that including the address (URL) of the server providing the content such as the TDO, or may be separately defined as a table including the address (URL) of the server providing the trigger information.
If the video display device 800 obtains at least one available enhanced service address through the watermark information, the first reply, or the second reply, it accesses the enhanced service providing server 750 by using the at least one available enhanced service address to request enhanced service in operation S723, and then, obtains the enhanced service from the enhanced service providing servers 750 in operation S725.
According to an embodiment, an enhanced service obtained from the enhanced service providing servers 750 through the internet may include content such as a TDO, and trigger information. The enhanced service providing server 750 providing the content such as the TDO and the enhanced service providing server 750 providing the trigger information may have different URLs.
FIG. 49 is a view illustrating a watermark based content recognition timing according to an embodiment.
As shown in FIG. 49, when the broadcast receiving device 760 is turned on and tunes a channel, and also, the video display device 800 receives a main AV content of the turned channel from the broadcast receiving device 760 through an external input port 811, the video display device 100 may sense a content provider identifier (or a broadcasting station identifier) from the watermark of the main AV content. Then, the video display device 800 may sense content information from the watermark of the main AV content on the basis of the sensed content provider identifier.
At this point, as shown in FIG. 49, the detection available period of the content provider identifier may be different from that of the content information. Especially, the detection available period of the content provider identifier may be shorter than that of the content information. Through this, the video display device 100 may have an efficient configuration for detecting only necessary information.
FIG. 50 is a block diagram illustrating a fingerprint based network topology according to an embodiment.
As shown in FIG. 50, the network topology may further include a fingerprint server 722.
As shown in FIG. 50, the fingerprint server 722 does not edit a main AV content, but extracts feature information from audio samples in some frames or intervals of the main AV content and stores the extracted feature information. Then, when receiving the feature information from the video display device 800, the fingerprint server 722 provides an identifier and time information of an AV content corresponding to the received feature information.
According to an embodiment, information transferred from the fingerprint server 722 may include channel information, an address (URL) of a server to be first connected to obtain content such as a TDO, or trigger information included in an enhanced service related to a corresponding channel, and a timestamp which is time information.
FIG. 51 is a ladder diagram illustrating a data flow in a fingerprint based network topology according to an embodiment.
First, the content providing server 710 transmits a broadcast signal including a main AV content and an enhanced service in operation S801.
The fingerprint server 722 receives a broadcast signal that the content providing server 710, extracts a plurality of feature information from a plurality of frame intervals or audio intervals of the main AV content, and establishes a database for a plurality of query results corresponding to the plurality of feature information in operation S803. The query result may include at least one of content information, enhanced service information, and an available enhanced service.
The MVPD 730 receives broadcast signals including a main AV content and enhanced service and generates a multiplexed signal to provide it to the broadcast receiving device 760 in operation S805. At this point, the multiplexed signal may exclude the received enhanced service or may include new enhanced service.
The broadcast receiving device 760 tunes a channel that a user selects and receives signals of the tuned channel, demodulates the received signals, performs channel decoding and AV decoding on the demodulated signals to generate an uncompressed main AV content, and then, provides the generated uncompressed main AV content to the video display device 100 in operation S806.
Moreover, the content providing server 710 also broadcasts a broadcast signal including a main AV content through a wireless channel in operation S807.
Additionally, the MVPD 730 may directly transmit a broadcast signal including a main AV content to the video display device 800 without going through the broadcast receiving device 760 in operation S808.
The video display device 800 may receive an uncompressed main AV content through the broadcast receiving device 760. Additionally, the video display device 800 may receive a broadcast signal through a wireless channel, and then, may demodulate and decode the received broadcast signal to obtain a main AV content.
Additionally, the video display device 800 may receive a broadcast signal from the MVPD 730, and then, may demodulate and decode the received broadcast signal to obtain a main AV content. The video display device 800 extracts feature information from audio samples in some frames or intervals of the obtained main AV content in operation S813.
The video display device 800 accesses the fingerprint server 722 corresponding to the predetermined fingerprint server address to transmit a first query including the extracted feature information in operation S815, and receives a second response from the fingerprint server 722 in response to the first query in operation S816.
The fingerprint server 722 provides a query result as a first reply to the first query in operation S817. If the first reply corresponds to fail, the video display device 800 accesses the fingerprint server 722 corresponding to another fingerprint server address to transmit a first query including the extracted feature information.
According to an embodiment, the video display device 800 may obtain information about a currently viewed channel by using an ACR mechanism using fingerprint according to the operations as described above. The obtained information may include information about the viewed channel, an address (URL) of the enhanced service information providing server 740 providing information necessary for obtaining an enhanced service related to the viewed channel, and a timestamp which is time information.
For example, the fingerprint server 722 may provide Extensible Markup Language (XML) document as a query result. Examples of the XML document containing a query result will be described with reference to FIG. 52 and Table 4.
FIG. 52 is a view illustrating an XML schema diagram of ACR-Resulttype containing a query result according to an embodiment.
As shown in FIG. 52, ACR-Resulttype containing a query result includes ResultCode attributes and ContentID, NTPTimestamp, SignalingChannelInformation, and ServiceInformation elements.
For example, if the ResultCode attribute has 200, this may mean that the query result is successful. For example, if the ResultCode attribute has 404, this may mean that the query result is unsuccessful.
The ContentID is an identifier capable of identifying corresponding content, and may be an identifier for a currently viewed channel.
The NTPTimestamp provides time information about the start point (or including an end point) of a sample period used in query, and the NTP may ensure precision of 1 or 100 sec unit on the internet by using the UTC time.
Accordingly, the NTPTimestamp may be used for precise synchronization in a frame unit, and be a value synchronized with the same clock as an action timestamp for the trigger information as described in relation to FIGS. 25 to 32, according to an embodiment.
That is, content such as the TDO may be synchronized with time information of the trigger information on the basis of the NTPTimestamp to be executed or played according to a trigger action included in the trigger information.
The SignalingChanneInformation indicates a channel providing metadata which is signaling information for the enhanced service through the internet, and may provide connection information for the signaling channel on an IP network.
For example, the connection information for the signaling channel may be an address (URL) of a server providing signaling information for the enhanced service, and more specifically, may be a URL of the enhanced service information providing server 740 as described in relation to FIGS. 46 to 51.
For this, the SignalingChannelInformation element includes a SignalingChannelURL indicating a URL of a server providing signaling information of the enhanced information, and the SignalingChannelURL element includes an UpdateMode and PollingCycle attributes.
According to an embodiment, the video display device 800 connects to the enhanced service information providing server 740 by using a URL designated at the SignalingChannelURL element to receive signaling information for obtaining content such as a TDO, and trigger information.
Moreover, the UpdataMode indicates a scheme for obtaining information through the signaling channel, and may obtain signaling information by periodically polling according to a Pull scheme. In a case of Push scheme, the video display device 800 may transmit the signaling information in a Push scheme to the enhanced service information providing server 740, if necessary.
In addition, the PollingCycle may designate a basic period value for polling of the video display device 800. The video display device 800 may request for signaling information in a time period corresponding to the basic period value having a predetermined value added for preventing congestion of the requests to the enhanced service information providing server 740
Also, the ServiceInformation element provides a specific information about the corresponding channel, for example, a channel name, a logo, or text description, etc., and the channel information included in the ServiceInformation element may be immediately displayed through a banner of the video display device 800.
For example, the ServiceInformation element includes ServiceName indicating a currently viewed channel name, ServiceLogo providing a logo of the channel, and ServiceDescription providing text description for the channel, as sub-elements.
Table 4 illustrates an XML schema of ACR-ResultType containing the query result.







TABLE 4







<xs:complexType name=“ACR-ResultType”>


 <xs:sequence>


  <xs:element name=“Content ID” type=“xs:anyURI”/>


  <xs:element name=“NTPTimestamp” type=“xs:unsignedLong”/>


  <xs:element name=“SignalingChannel Information”>


  <xs:complexType>


   <xs:sequence>


   <xs:element name=“SignalingChannelURL”


maxOccurs=“unbounded”>


    <xs:complexType>


    <xs:simpleContent>


     <xs:extension base=“xs:anyURI”>


     <xs:attribute name=“UpdateMode”>


      <xs:simpleType>


      <xs:restriction base=“xs:string”>


       <xs:enumeration value=“Pull”/>


       <xs:enumeration value=“Push”/>


      </xs:restriction>


      </xs:simpleType>


     </xs:attribute>


     <xs:attribute name=“PollingCycle” type=“xs:unsignedInt”/>


     </xs:extension>


    </xs:simpleContent>


    </xs:complexType>


   </xs:element>


   </xs:sequence>


  </xs:complexType>


  </xs:element>


  <xs:element name=“ServiceInformation”>


  <xs:complexType>


   <xs:sequence>


   <xs:element name=“ServiceName” type=“xs:string”/>


   <xs:element name=“ServiceLogo” type=“xs:anyURI”


minOccurs=“0”/>


   <xs:element name=“ServiceDescription” type=“xs:string”


minOccurs=“0” maxOccurs=“unbounded”/>


   </xs:sequence>


  </xs:complexType>


  </xs:elment>


  <xs:any namespace=“##other” processContents=“skip”


minOccurs=“0” maxOccurs=“unbounded”/>


 </xs:sequence>


 <xs:attribute name=“ResultCode” type=“xs:string” use=“required”/>


 <xs:anyAttribute processContents=“skip”/>


 </xs:complexType>









As the ContentID element, an ATSC content identifier may be used as shown in Table 5.









TABLE 5





Syntax
The Number of bits
format















ATSC_content_identifier( ) {











TSID
16
uimsbf



reserved
2
bslbf



end_of_day
5
uimsbf



unique_for
9
uimsbf



content_id
var








}









As shown in Table 5, the ATSC content identifier has a structure including TSID and a house number.
The 16 bit unsigned integer TSID carries a transport stream identifier.
The 5 bit unsigned integer end_of_day is set with an hour in a day of when a content_id value can be reused after broadcasting is finished.
The 9 bit unsigned integer unique_for is set with the number of day of when the content_id value cannot be reused.
Content_id represents a content identifier. The video display device 100 reduces unique_for by 1 in a corresponding time to end_of_day daily and presumes that content_id is unique if unique_for is not 0.
Moreover, as the ContentID element, a global service identifier for ATSC-M or H service may be used as described below.
The global service identifier has the following form.
urn:oma:bcast:iauth:atsc:service:<region>:<xsid>:<serviceid>
Here, <region> is an international country code including two characters regulated by ISO 639-2. <xsid> for local service is a decimal number of TSID as defined in <region>, and <xsid> (regional service) (major>69) is “0”. <serviceid> is defined with <major> or <minor>. <major> represent a Major Channel number, and <minor> represents a Minor Channel Number.
Examples of the global service identifier are as follows.
urn:oma:bcast:iauth:atsc:service:us:1234:5.1
urn:oma:bcast:iauth:atsc:service:us:0:100.200
Moreover, as the ContentID element, an ATSC content identifier may be used as described below.
The ATSC content identifier has the following form.
urn:oma:bcast:iauth:atsc:content:<region>:<xsidz>:<contentid>:<unique_for>:<end_of_day>
Here, <region> is an international country code including two characters regulated by ISO 639-2. <xsid> for local service is a decimal number of TSID as defined in <region>, and may be followed by “.”<serviceid>. <xsid> for (regional service) (major>69) is <serviceid>. <content_id> is a base64 sign of a content_id field defined in Table 5, <unique_for> is a decimal number sign of an unique_for field defined in Table 5, and <end_of_day> is a decimal number sign of an end_of_day field defined in Table 5.
Moreover, as an exemplary configuration of information obtained by the ACR mechanism, a configuration of a first response transferred from the fingerprint server 722 as a first query result is described in relation to FIG. 52, and Tables 4 and 5, but the present invention is not limited thereto.
For example, information having the configuration as described in relation to FIG. 52, and Tables 4 and 5 is inserted into a watermark and received by the video display device 800, or transferred from the watermark server 721.
Hereinafter, FIG. 51 is described again.
If the query result does not include an enhanced service address or enhanced service but includes an enhanced service address providing server address, the video display device 800 accesses the enhanced service information providing server 740 corresponding to the obtained enhanced service address providing server address to transmit a second query including content information in operation S819.
The enhanced service information providing server 740 searches at least one available enhanced service relating to the content information of the second query. Later, the enhanced service information providing server 740 provides to the video display device 800 enhanced service information for at least one available enhanced service as a second reply to the second query in operation S821.
According to an embodiment, the enhanced service information may include metadata having information necessary for obtaining content such as a TDO, and trigger information forming the corresponding enhanced service.
For example, the metadata may include one or more signaling tables, and the signaling tables may include an address (for example, a URL of the enhanced service providing server 750) of a server providing content such as the TDO, and an address (for example, a URL of the enhanced service providing server 750) of a server providing the trigger information.
Moreover, the signaling tables may include at least one of NRT service signaling tables, for example, an NRT service map table (SMT), an NRT information table (NRT-IT), and a text fragment table (TFT), as described in relation to FIGS. 1 to 21.
In this case, the address (URL) of the server providing the content such as the TDO may be included in any one of the NRT service signaling tables. For example, the URL of the enhanced service providing server 50 providing the content may be included in the NRT-IT.
Moreover, the address (URL) of the server providing the trigger information may be included in any one table of the NRT service signaling tables, and the table including the address (URL) of the server providing the trigger information may be the same as a table including the address (URL) of the server providing the content such as the TDO, or may be separately defined to be a table including the address (URL) of the server providing the trigger information.
If the video display device 800 obtains at least one available enhanced service address through the first reply or the second reply, it accesses the at least one available enhanced service address to request enhanced service in operation S823, and then, obtains the enhanced service in operation S825.
When the UpdateMode attribute has a Pull value, the video display device 800 transmits an HTTP request to the enhanced service providing server 750 through SignalingChannelURL and receives an HTTP reply including a PSIP binary stream from the enhanced service providing server 750 in response to the request.
In this case, the video display device 800 may transmit the HTTP request according to a Polling period designated as the PollingCycle attribute. Additionally, the SignalingChannelURL element may have an update time attribute. In this case, the video display device 800 may transmit the HTTP request according to an update time designated as the update time attribute.
If the UpdateMode attribute has a Push value, the video display device 800 may receive update from a server asynchronously through XMLHTTPRequest API. After the video display device 800 transmits an asynchronous request to a server through XMLHTTPRequest object, if there is a change of signaling information, the server provides the signaling information as a reply through the channel. If there is limitation in session standby time, a server generates a session timeout reply and a receiver recognizes the generated timeout reply to transmit a request again, so that a signaling channel between the receiver and the server may be maintained for all time.
According to the present invention, the enhanced service obtained from the enhanced service providing server 750 may include content such as TDO, and trigger information, and the enhanced service providing server 750 providing the content such as the TDO and the enhanced service providing server 750 providing the trigger information may have different URLs.
FIG. 53 is a block diagram illustrating a watermark and fingerprint based network topology according to an embodiment.
As shown in FIG. 53, the watermark and fingerprint based network topology may further include a watermark server 721 and a fingerprint server 722.
As shown in FIG. 53, the watermark server 721 inserts content provider identifying information into a main AV content. The watermark server 721 may insert content provider identifying information as a visible watermark such as a logo or an invisible watermark into a main AV content.
The fingerprint server 722 does not edit a main AV content, but extracts feature information from audio samples in some frames or intervals of the main AV content and stores the extracted feature information. Then, when receiving the feature information from the video display device 800, the fingerprint server 722 provides an identifier and time information of an AV content corresponding to the received feature information.
FIG. 54 is a ladder diagram illustrating a data flow in a watermark and fingerprint based network topology according to an embodiment. In the illustrated data flow, description about the same portions as described in relation to FIGS. 46 to 53 will be omitted.
First, the content providing server 710 transmits a broadcast signal including a main AV content and an enhanced service in operation S901.
The watermark server 721 receives a broadcast signal that the content providing server 710 provides, inserts a visible watermark such as a logo or watermark information as an invisible watermark into the main AV content by editing the main AV content, and provides the watermarked main AV content and enhanced service to the MVPD 730 in operation S903.
The watermark information inserted through an invisible watermark may include at least one of content information, enhanced service information, and an available enhanced service. The content information and enhanced service information are described above.
The MVPD 730 receives broadcast signals including watermarked main AV content and enhanced service and generates a multiplexed signal to provide it to the broadcast receiving device 760 in operation S905. At this point, the multiplexed signal may exclude the received enhanced service or may include new enhanced service.
The broadcast receiving device 760 tunes a channel that a user selects and receives signals of the tuned channel, demodulates the received signals, performs channel decoding and AV decoding on the demodulated signals to generate an uncompressed main AV content, and then, provides the generated uncompressed main AV content to the video display device 800 in operation S906.
Moreover, the content providing server 710 also broadcasts a broadcast signal including a main AV content through a wireless channel in operation S907.
Additionally, the MVPD 730 may directly transmit a broadcast signal including a main AV content to the video display device 800 without going through the broadcast receiving device 760 in operation S908.
The video display device 800 may receive an uncompressed main AV content through the broadcast receiving device 760. Additionally, the video display device 800 may receive a broadcast signal through a wireless channel, and then, may demodulate and decode the received broadcast signal to obtain a main AV content. Additionally, the video display device 800 may receive a broadcast signal from the MVPD 730, and then, may demodulate and decode the received broadcast signal to obtain a main AV content. The video display device 800 extracts watermark information from audio samples in some frames or periods of the obtained main AV content.
If watermark information corresponds to a logo, the video display device 800 confirms a watermark server address corresponding to a logo extracted from a corresponding relationship between a plurality of logos and a plurality of watermark server addresses.
When the watermark information corresponds to the logo, the video display device 800 cannot identify the main AV content only with the logo. Additionally, when the watermark information does not include content information, the video display device 800 cannot identify the main AV content but the watermark information may include content provider identifying information or a watermark server address.
When the watermark information includes the content provider identifying information, the video display device 800 may confirm a watermark server address corresponding to the content provider identifying information extracted from a corresponding relationship between a plurality of content provider identifying information and a plurality of watermark server addresses. In this manner, when the video display device 800 cannot identify a main AV content the video display device 800 only with the watermark information, it accesses the watermark server 721 corresponding to the obtained watermark server address to transmit a first query in operation 8909.
The watermark server 721 provides a first reply to the first query in operation S911. The first reply may include at least one of a fingerprint server address, content information, enhanced service information, and an available enhanced service. The content information and enhanced service information are described above.
If the watermark information and the first reply include a fingerprint server address, the video display device 800 extracts feature information from audio samples in some frames or intervals of the obtained main AV content in operation S913.
The video display device 800 accesses the fingerprint server 722 corresponding to the fingerprint server address in the first reply to transmit a second query including the extracted feature information in operation S915.
The fingerprint server 722 provides a query result as a second reply to the second query in operation S917.
If the query result does not include an enhanced service address or enhanced service but includes an enhanced service address providing server address, the video display device 800 accesses the enhanced service information providing server 740 corresponding to the obtained enhanced service address providing server address to transmit a third query including content information in operation S919.
The enhanced service information providing server 740 searches at least one available enhanced service relating to the content information of the third query. Later, the enhanced service information providing server 740 provides to the video display device 800 enhanced service information for at least one available enhanced service as a third reply to the third query in operation S921.
If the video display device 800 obtains at least one available enhanced service address through the first reply, the second reply, or the third reply, it accesses the at least one available enhanced service address to request enhanced service in operation S923, and then, obtains the enhanced service in operation S925.
Hereinafter, a configuration of a receiver according to another embodiment will be described in relation to FIG. 55.
FIG. 55 is a block diagram illustrating the video display device 800 as an exemplary receiving apparatus. In the illustrated video display device 800, description about the same operations as described in relation to FIGS. 46 to 54 will be omitted.
As shown in FIG. 55, the video display device 800 includes a broadcast signal receiving unit 801, a demodulation unit 803, a channel decoding unit 805, a demultiplexing unit 807, an AV decoding unit 809, an external input port 811, a play controlling unit 813, a play device 820, an enhanced service management unit 830, a data transmitting or receiving unit 141, and a memory 850.
The broadcast signal receiving unit 801 receives a broadcast signal from the content providing server 710 or MVPD 730.
The demodulation unit 803 demodulates the received broadcast signal to generate a demodulated signal.
The channel decoding unit 805 performs channel decoding on the demodulated signal to generate channel-decoded data.
The demultiplexing unit 807 separates a main AV content and enhanced service from the channel-decoded data. The separated enhanced service is stored in an enhanced service storage unit 852.
The AV decoding unit 809 performs AV decoding on the separated main AV content to generate an uncompressed main AV content.
Moreover, the external input port 811 receives an uncompressed main AV content from the broadcast receiving device 760, a digital versatile disk (DVD) player, a Blu-ray disk player, and so on. The external input port 811 may include at least one of a DSUB port, a High Definition Multimedia Interface (HDMI) port, a Digital Visual Interface (DVI) port, a composite port, a component port, and an S-Video port.
The play controlling unit 813 controls the play device 820 to play at least one of an uncompressed main AV content that the AV decoding unit 809 generates and an uncompressed main AV content received from the external input port 811 according to a user's selection.
The play device 820 includes a display unit 821 and a speaker 823. The display unit 821 may include at least one of a liquid crystal display (LCD), a thin film transistor-liquid crystal display (TFT LCD), an organic light-emitting diode (OLED), a flexible display, and a 3D display.
The enhanced service management unit 830 obtains content information of the main AV content and obtains available enhanced service on the basis of the obtained content information. Especially, as described above, the enhanced service management unit 830 may obtain the identification information of the main AV content on the basis of audio samples in some frames or intervals of the uncompressed main AV content. This is called automatic contents recognition (ACR) in this specification.
According to an embodiment, the enhanced service management unit 830 may obtain information about a currently viewed channel by using an ACR mechanism, and the obtained information may include information about the viewed channel, an address (URL) of a server to be connected to receive an enhanced service related to the viewed channel through the internet, and a timestamp which is time information.
The data transmitting or receiving unit 841 may include an Advanced Television Systems Committee—Mobile or Handheld (ATSC-M or H) channel transmitting or receiving unit 841a and an IP transmitting or receiving unit 841b. 
The memory 850 may include at least one type of storage medium such as a flash memory type, a hard disk type, a multimedia card micro type, a card type memory such as SD or XD memory, Random Access Memory (RAM), Static Random Access Memory (SRAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Programmable Read-Only Memory (PROM), magnetic memory, magnetic disk, and optical disk. The video display device 800 may operate in linkage with a web storage performing a storage function of the memory 850 in the Internet.
The memory 850 may include a content information storage unit 851, an enhanced service storage unit 852, a logo storage unit 853, a setting information storage unit 854, a bookmark storage unit 855, a user information storage unit 856, and a usage information storage unit 857.
The content information storage unit 851 stores a plurality of content information corresponding to a plurality of feature information.
The enhanced service storage unit 852 may store a plurality of enhanced services corresponding to a plurality of feature information or a plurality of enhanced services corresponding to a plurality of content information.
According to an embodiment, the enhanced service storage unit 852 may store content such as a TDO, and trigger information received through the internet.
The logo storage unit 853 stores a plurality of logos. Additionally, the logo storage unit 853 may further store content provider identifiers corresponding to the plurality of logos or watermark server addresses corresponding to the plurality of logos.
The setting information storage unit 854 stores setting information for ACR. The bookmark storage unit 855 stores a plurality of bookmarks.
The user information storage unit 856 stores user information. The user information may include at least one of at least one account information for at least one service, regional information, family member information, preferred genre information, video display device information, and a usage information range. The at least one account information may include account information for a usage information measuring server and account information of social network service such as Twitter and Facebook. The regional information may include address information and zip codes.
For example, the family member information may include the number of family members, each member's age, each member's sex, each member's religion, and each member's job. The preferred genre information may be set with at least one of sports, movie, drama, education, news, entertainment, and other genres.
The video display device information may include information such as the type, manufacturer, firmware version, resolution, model, OS, browser, storage device availability, storage device capacity, and network speed of an video display device. Once the usage information range is set, the video display device 800 collects and reports main AV content watching information and enhanced service usage information within the set range. The usage information range may be set in each virtual channel. Additionally, the usage information measurement allowable range may be set over an entire physical channel.
The usage information providing unit 857 stores the main AV content watching information and the enhanced service usage information, which are collected by the video display device 800. Additionally, the video display device 800 analyzes a service usage pattern on the basis of the collected main AV content watching information and enhanced service usage information, and stores the analyzed service usage pattern in the usage information storage unit 857.
The enhanced service management unit 830 may obtain the content information of the main AV content from the fingerprint server 722 or the content information storage unit 851. If there is no content information or sufficient content information, which corresponds to the extracted feature information, in the content information storage unit 851, the enhanced service management unit 830 may receive additional content information through the data transmitting or receiving unit 841. Moreover, the enhanced service management unit 830 may update the content information continuously.
The enhanced service management unit 830 may obtain available enhanced service from the enhanced service providing server 750 or the enhanced service storage unit 853. If there is no enhanced service or sufficient enhanced service in the enhanced service storage unit 853, the enhanced service management unit 830 may update enhanced service through the data transmitting or receiving unit 841. Moreover, the enhanced service management unit 830 may update the enhanced service continuously.
The enhanced service management unit 830 may extracts a logo from the main AV content, and then, may make a query to the logo storage unit 855 to obtain a content provider identifier or watermark server address, which is corresponds to the extracted logo. If there is no logo or a sufficient logo, which corresponds to the extracted logo, in the logo storage unit 855, the enhanced service management unit 830 may receive an additional logo through the data transmitting or receiving unit 841. Moreover, the enhanced service management unit 830 may update the logo continuously.
The enhanced service management unit 830 may compare the logo extracted from the main AV content with the plurality of logos in the logo storage unit 855 through various methods. The various methods may reduce the load of the comparison operation.
For example, the enhanced service management unit 830 may perform the comparison on the basis of color characteristics. That is, the enhanced service management unit 830 may compare the color characteristic of the extracted logo with the color characteristics of the logos in the logo storage unit 855 to determine whether they are identical or not.
Moreover, the enhanced service management unit 830 may perform the comparison on the basis of character recognition. That is, the enhanced service management unit 130 may compare the character recognized from the extracted logo with the characters recognized from the logos in the logo storage unit 855 to determine whether they are identical or not.
Furthermore, the enhanced service management unit 830 may perform the comparison on the basis of the contour of the logo. That is, the enhanced service management unit 830 may compare the contour of the extracted logo with the contours of the logos in the logo storage unit 855 to determine whether they are identical or not.
Moreover, the above broadcast service transmitting and receiving methods of the present invention can also be embodied as computer readable codes on a computer readable recording medium. Examples of the computer readable recording medium include read-only memory (ROM), random-access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission through the Internet).
The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. Also, functional programs, codes, and code segments for accomplishing the present invention can be easily construed by programmers skilled in the art to which the present invention pertains.
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 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 or arrangements, alternative uses will also be apparent to those skilled in the art.

## Claims

1. A method of receiving a broadcast service in a receiving apparatus, the method comprising:
receiving uncompressed audio or video content;
extracting a signature from video frames or audio samples of the uncompressed audio or video content;
transmitting a query including the signature to a server;
obtaining a response based on the query, wherein the response includes period information for requesting trigger information; and
obtaining trigger information by using the obtained response,
wherein the trigger information includes at least one of trigger time, an identifier for a Triggered Declarative Object (TDO) and a trigger action,
wherein the obtaining trigger information comprises,
transmitting a request for trigger information according to the period information, and
receiving the trigger information, when the response indicates a first mode.

2. The method of claim 1,
wherein the obtaining trigger information comprises,
obtaining the trigger information, when signaling information changes, when the response indicates a second mode.

3. The method of claim 1, further comprising
executing the trigger action for an object corresponding to the identifier of the TDO at the trigger time.

4. The method of claim 1, wherein the trigger action comprises at least one of a preparation trigger action, an execution trigger action and a termination trigger action.

5. The method of claim 1, wherein the trigger time is synchronized with the uncompressed audio or video content.

6. The method of claim 1, wherein the obtaining trigger information comprises, when the response indicates a second mode, to receive the trigger information when signaling information changes.

7. A receiving apparatus comprising:
a receiving unit to receive uncompressed audio or video content; and
a service management unit to extract from video frames or audio samples of the uncompressed audio or video content, transmit a query including the signature to a server, obtain a response based on the query and obtain trigger information by using the obtained response,
wherein the response includes period information for requesting trigger information,
wherein the trigger information includes at least one of trigger time, an identifier for a Triggered Declarative Object (TDO) and a trigger action,
wherein the service management unit transmits a request for trigger information according to the period information, and receives the trigger information, when the response indicates a first mode.

8. The receiving apparatus of claim 7,
wherein the service management unit receives the trigger information when signaling information changes, when the response indicates a second mode.

9. The receiving apparatus of claim 8, wherein the service management unit obtains a trigger time related to the trigger information and
the receiving apparatus further comprises a control unit that executes the trigger action for an object corresponding to the identifier of the TDO at the trigger time.

10. The receiving apparatus of claim 9, wherein the trigger action comprises at least one of a preparation trigger action, an execution trigger action and a termination trigger action.

11. The receiving apparatus of claim 9, wherein the trigger time is synchronized with the uncompressed audio or video content.