KR20170000312A - Method and apparatus for digital broadcast services - Google Patents

Abstract

Disclosed are a method and apparatus for digital broadcasting services. The method includes the steps of: receiving an AIT message including an application information (AI) table through a multimedia transmission session; obtaining attribute information related to an application program service from the AI table; and executing the application program service based on the attribute information. Accordingly, the present invention can support an application program service which is independently operated or is connected with a broadcasting program.

Description

[0001] METHOD AND APPARATUS FOR DIGITAL BROADCAST SERVICES [

The present invention relates to a method and apparatus for transmitting application program service information and events in a digital broadcast service.

Multimedia service means a service such as an interactive service such as a video telephone, a streaming service such as a Video On Demand (VOD) service, or a multicast and broadcast service. The real-time multimedia service can be divided into an interactive service, an interactive service, and a streaming service depending on the service type, and can be divided into unicast, multicast, and broadcast according to the number of users participating.

2. Description of the Related Art MPEG-2 TS (Moving Picture Experts Group-2 Transport Stream) is a technology used for transmission of multimedia contents. In the transmission environment with an error, a plurality of broadcast programs (a plurality of coded video bit streams) Is used as a typical transmission technique. An MMT (MPEG MEDIA Transport) standard has been proposed as one of the multimedia transmission technologies for supporting multimedia services based on MPEG technology. MMT technology is a new standard technology of MPEG for smoothly providing various types of multimedia services through various user terminals such as TV (Television) and mobile devices in various kinds of network environments. For example, MMT standard is a heterogeneous network To transmit the composite content efficiently. Here, the complex contents means a set of contents having multimedia elements by video / audio / application. The heterogeneous network may be a network in which a broadcast network and a mobile communication network are mixed.

In order to support the application program service based on the hybrid transmission technology in which the broadcasting network and the communication network are linked with each other, in addition to receiving the data or the file necessary for executing the application program service using the broadcasting network or the communication network, Signaling information is needed to allow the service and associated data to be recognized and selected. Therefore, a need has arisen for a technology for transmitting effective signaling information for providing application program services in a communication system using MPEG media transmission technology.

The present invention provides a method and apparatus for supporting a digital broadcasting service.

The present invention provides a method and apparatus for supporting application program services that operate independently or in conjunction with broadcast programs transmitted using media transmission techniques.

The present invention provides a signaling information transmission method and apparatus for supporting an application program service for a digital broadcasting service.

It is an object of the present invention to provide a method and apparatus for transmitting application program service related information and event information for controlling operation of an application program service using MMT transmission technology.

A method according to an embodiment of the present invention comprises: A digital broadcasting service method comprising: receiving an AIT message including an application information (AI) table through a multimedia transmission session; acquiring attribute information related to an application program service from the AI table; And executing the application program service based on the application program.

An apparatus according to an embodiment of the present invention includes: An apparatus for receiving a digital broadcasting service, the apparatus comprising: a receiving unit for receiving an AIT message including an application information (AI) table through a multimedia transmission session; and an obtaining unit for obtaining attribute information related to the application program service from the AI table, And a control unit for executing the application program service based on the application program.

Further aspects, features and advantages of the present invention as set forth above will become more apparent from the following description, taken in conjunction with the accompanying drawings, in which certain preferred embodiments of the invention are described.
1 is a diagram illustrating a hierarchical structure of an MMT system according to an embodiment of the present invention.
FIG. 2 illustrates a configuration of an MMT payload according to an embodiment of the present invention.
3 shows a logical structure of an MMT package according to an embodiment of the present invention.
FIG. 4 illustrates a schematic operation process of a terminal for executing an application program service according to an embodiment of the present invention.
5 is a schematic representation of an apparatus for receiving information related to application program services in accordance with an embodiment of the present invention.
6 is a flowchart illustrating a process of processing event information using an MMT signaling message according to an embodiment of the present invention.
7 is a flowchart illustrating an event information processing procedure using an MPU according to an embodiment of the present invention.
Throughout the drawings, it should be noted that like reference numerals are used to illustrate the same or similar elements and features and structures.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In the following description of the embodiments of the present invention, descriptions of techniques which are well known in the technical field of the present invention and are not directly related to the present invention will be omitted. This is for the sake of clarity of the present invention without omitting the unnecessary explanation.

For the same reason, some of the components in the drawings are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In the drawings, the same or corresponding components are denoted by the same reference numerals.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

It will be appreciated that the combinations of blocks and flowchart illustrations in the process flow diagrams may be performed by computer program instructions. These computer program instructions may be loaded into a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, so that those instructions, which are executed through a processor of a computer or other programmable data processing apparatus, Thereby creating means for performing functions. These computer program instructions may also be stored in a computer usable or computer readable memory capable of directing a computer or other programmable data processing apparatus to implement the functionality in a particular manner so that the computer usable or computer readable memory The instructions stored in the block diagram (s) are also capable of producing manufacturing items containing instruction means for performing the functions described in the flowchart block (s). Computer program instructions may also be stored on a computer or other programmable data processing equipment so that a series of operating steps may be performed on a computer or other programmable data processing equipment to create a computer- It is also possible for the instructions to perform the processing equipment to provide steps for executing the functions described in the flowchart block (s).

In addition, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative implementations, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may actually be executed substantially concurrently, or the blocks may sometimes be performed in reverse order according to the corresponding function.

Herein, the term " part " used in the present embodiment means a hardware component such as software or an FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit) Lt; / RTI > However, 'part' is not meant to be limited to software or hardware. &Quot; to " may be configured to reside on an addressable storage medium and may be configured to play one or more processors. Thus, by way of example, 'parts' may refer to components such as software components, object-oriented software components, class components and task components, and processes, functions, , Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and components may be further combined with a smaller number of components and components or further components and components. In addition, the components and components may be implemented to play back one or more CPUs in a device or a secure multimedia card.

Although specific embodiments of the present disclosure will be described in the context of an OFDM-based wireless communication system, the subject matter of the present disclosure is not limited to the communication systems and services described herein, And the scope of the present invention is not limited to the above-described embodiments, but may be practiced by those skilled in the art.

The MMT protocol (MMT Protocol) defines an application layer protocol for delivering a delivery frame composed of an MMT payload format (PF) over an Internet Protocol (IP) network. The MMT payload is designed in a MMT payload format for efficient delivery. In order to efficiently deliver MPEG media data through heterogeneous IP networks, the MMT defines Encapsulation Formats, Delivery Protocols, and signaling message formats.

MMT technology defines data models such as package and asset. A package refers to one independent content such as a movie, and an asset is a logical entity that distinguishes elements such as video, audio, or data constituting the content, and one package can be composed of a plurality of assets.

1 is a diagram illustrating a hierarchical structure of an MMT system according to an embodiment of the present invention.

1, a media coding layer 110, an encapsulation function layer (Layer E) 120, and a delivery function layer A layer 130, a transport protocol layer 140, an Internet protocol (IP) layer 150, and a control function layer (Layer C) 100 are illustrated.

According to one embodiment, the media encoding layer 110 and the encapsulation function layer 120 operate as a multimedia data generation unit for generating multimedia data according to multimedia contents and / or multimedia services. Also, the transfer function layer 130 operates as a multimedia data constructing unit for constructing a multimedia data packet based on the multimedia data input from the data generating unit. The transfer function layer 130 corresponding to the multimedia data structure unit constructs header information by identifying at least one multimedia data provided from the multimedia data generation unit, combines the header information and at least one multimedia data to form a multimedia data packet do.

The multimedia data compressed in the media encoding layer 110 is packaged in a form similar to a file format via the encapsulation function layer 120 and output. The encapsulation function layer 120 receives coded media data or stored media data provided from the media encoding layer 110 to generate a data segment that is a small unit for the MMT service, And creates access units for the MMT service. The encapsulation layer 120 also creates a packet format for composing and storing and delivering composite content by combining and / or segmenting the access units.

The transfer function layer 130 converts the data unit (s) output from the encapsulation function layer 120 into an MMT payload format, and then forms an MMT transport packet by adding an MMT transport packet header Or an RTP (Real-time Protocol) which is an existing transmission protocol.

Packets configured in the delivery function layer 130 are finally IP packetized in the Internet protocol (IP) layer 150 through a transport protocol layer 140 such as UDP (User Datagram Protocol) or TCP (Transport Control Protocol) do. The transport protocol layer 140 and the IP layer 150 may operate as data transfer units. The control function unit 100, which may be selectively present, generates control information or signaling information necessary for data transmission, adds the control information or signaling information to the data, and transmits the control information or signaling information through separate signaling means.

The MMT payload format generated in the delivery function layer 130 defines the logical structure of the media unit (s) to be delivered by the MMT protocol or RTP. The MMT payload is specified by a payload format for conveying encapsulated data units and other information by MMT layer protocols or other existing Application Transport Protocols. The MMT payload provides information about streaming and information about file transfers. In streaming, the data unit may be an MMT Media Fragment Unit (MFU) or an MMT Processing Unit (MPU). For file delivery, the data unit may be an MMT Asset and an MMT Package.

FIG. 2 illustrates a configuration of an MMT payload according to an embodiment of the present invention.

2, an MMT payload 200 may comprise at least one of at least one MMT MFU 210, at least one MPU 230, at least one MMT asset 230, and an MMT package. have.

MFU 210 is a generic container format that includes coded media data that can be independently processed by a media decoder, independent of any particular media codec. The MFU 210 represents a part of fragmented data of the MPU 220, and is the minimum unit capable of decoding on its own. As an example, when encoding is performed using one frame as an access unit, the MFU 210 may be one video frame, and in other cases, it may be one slice included in one frame.

The MPU 220 is a container format containing one or more MFUs and additional delivery and processing related information, and may include various numbers of MFUs generated from a plurality of different access units. The MPU 220 is an encoded media data unit that can be completely and independently processed by an MMT compliant entity. The MPU 220 is a specific size according to an application environment, for example, 1 GOP (Group of Picture). As an example, the MPU 220 may be composed of a plurality of picture frames constituting one GOP (one-second video, for example), and the MFU 220 may include each picture frame.

The MMT asset 230 is a data entity composed of one or more MPUs and is the largest data unit to which the same composition information (CI) and transport characteristics are applied. to be. The MMT asset 230 includes only one type of data, including packaged or multiplexed data. For example, at least a portion of an audio elementary stream (ES), at least a portion of an ES of video, an MPEG-U (User Interface) widget package, an MPEG- At least a portion of a transport stream (TS), at least a portion of an MP4 (MPEG-4) file, and all or at least a portion of an MMT package may be each MMT asset 230.

Where the elementary stream (ES) is defined by a particular media codec, and may logically be one or more MMT assets. The MMT asset 230 supporting the layered codec and the multi-view codec may overlap with other MMT assets.

MMT Composition Information (MMT-CI) refers to information defining the spatial and temporal relationship of MMT assets. MMT Transport Characteristics (MMT-TC) (QoS) required for the delivery of the service. The MMT-TC can be expressed as Asset Delivery Characteristics (ADC) for a particular delivery environment.

The MMT package 240 is defined as a collection of encoded media data and related information, which is processed by an MMT compliant entity.

FIG. 3 illustrates a logical structure of an MMT package according to an embodiment of the present invention. As shown, the MMT package 300 includes one or more MMT assets 320, MMT composition information 310, And one or more ADCs 330 representing the port characteristics. MMT package 240 includes descriptive information such as an identifier and the location of MMT assets 320 and MMT assets 320 in MMT package 240 may be multiplexed or concatenated.

The processing of the MMT package 240 is applied in units of MPUs, where the MMT asset 320 is an aggregate of one or more MPUs having the same MMT asset ID, 330). The ADC 330 can be used by the entity that packetizes the MMT package to configure the parameters of the MMT payload and the header information of the MMT packet.

The configuration information of the package and information necessary for receiving and consuming it at the user terminal are transmitted through the MMT signaling message. The MMT signaling functional area defines the message format associated with media consumption and media delivery. Messages related to media consumption provide information necessary to consume transmitted media data and are defined as follows.

A Package Access (PA) message, which plays a role similar to the PMT (Program Map Table) of the MPEG-2 TS, contains all information necessary for the reproduction of the transmitted package. The PA message is the first message to be transmitted in order to receive and consume the package, and subsequently the individual information may be updated in a separate message. The MPI (Media Presentation Information) message that provides the presentation information is composed of the composite information (CI) defined in ISO / IEC 23008-11 or the media presentation defined in ISO / IEC 23009-1 And a media presentation description (MPD). The MPT (MMT Package Table) message is a message for providing information on the package to be transmitted, and provides the ID of the package and the asset information constituting the package. In addition, a CRI (Clock Relation Information) message is provided to provide mapping information between an NTP (Network Time Protocol) timestamp and an MPEG-2 STT (System Timing Clock) for synchronization between the asset and MPEG-2 ES, A DCI (Device Capability Information) message is provided that provides required terminal capability information.

(UHDTV), 3-dimen- sion TV (3DTV), and multi-view TV), as well as various types of fixed-type and fixed- Innovative technologies that enable next-generation broadcasting and multimedia services such as N-screen service technology to organically utilize portable multimedia devices are continuously on the market. In particular, an application program service that provides a variety of supplementary information linked to broadcast programs or independently based on a hybrid transmission technology that enables a convergent multimedia service by organically linking a broadcast network and a communication network, It is regarded as a key success factor of the next generation broadcasting service in addition to providing video contents. Typical application program service models include viewer participatory services (simple text messages, quizzes, polls, surveys, popularity polls), TV e-commerce (ticketing, auctions, electronic coupons, mobile downloads) An application program service and a portal service that can be provided independently of a broadcast program, a customized advertisement, and the like.

In order to support the application program service, signaling information for recognition and selection of the application program service and related data in the terminal is required along with reception of data or files necessary to execute the application program service using the broadcast network or the communication network. There are two types of signaling information related to application program services. That is, the signaling information may be subdivided into signaling information for providing overall attributes for individual services such as an available application program service list, an application program service name and transmission information, and event information for controlling the operation of the application program service. In particular, in the case of an application program service linked to a broadcast program, it is possible to provide a more diversified and rich broadcast service by transmitting event information together.

FIG. 4 illustrates a schematic operation process of a terminal for executing an application program service according to an embodiment of the present invention. Here, an example of an application program service for a tailored advertisement at a specific time in conjunction with a broadcast program is shown.

Referring to FIG. 4, in step 405, the terminal receives and plays audio and video streams of a broadcast program requested by the user (Show X in the illustrated example) from a service provider, Acquiring signaling information for an application program service associated with the broadcast program through an application information stream, which is a channel providing associated signaling, and, if necessary, executing the application program service using a broadcast network or a communications network As shown in Fig. The signaling information and data may be collectively referred to as application information.

In step 415, the terminal receives event information transmitted in an event stream, which is a channel for providing an event, while reproducing the broadcast program, and performs an operation according to the event information. In the example shown, the terminal receives event information regarding the execution of the application program service Y providing additional information of the product being advertised at the middle portion of Show X, i.e., at the beginning of the advertisement time. In step 420, the terminal executes the application program service Y (i.e., advertisement service) based on the event information. After a predetermined time, if the end event of the application program service Y is received in step 425, the terminal terminates the service Y. [

MMT technology defines various signaling messages related to media consumption and media delivery, but the main role of these signaling messages is to provide the configuration information of the package and the information needed to receive the individual assets that make up the package. In particular, the MP (MMT Package) table used in the MPT message defines configuration information for each asset constituting the package and position information necessary for receiving each asset. The additional information other than the basic information is provided using a descriptor, and the MPT message defines a container format capable of storing various descriptors.

The MPEG CI information that can be used in the MPI table may include location information on the logical screen of the terminal of the individual asset constituting the package together with time information related to playback of the asset. However, MPEG CI is mainly aimed at providing control information for an asset transmitted to an MMT, and thus there is a limit to apply to an application program service transmitted through a transmission protocol other than MMT.

In the following, a technique of transmitting information related to an application program service and event information for controlling the operation of an application program service using the MMT transmission technology will be described.

5 is a schematic representation of an apparatus for receiving information related to application program services in accordance with an embodiment of the present invention.

Referring to FIG. 5, a data receiver 505 receives packets transmitted to a communication network or a broadcasting network using at least one of transmission protocols such as MMT, ROUTE, and HTTP (Hyper Text Transfer Protocol) And may include at least one of an MMT data receiver 510, a ROUTE data receiver 515, an HTTP data receiver 520 and another data receiver 525. The control unit 500 may control the received packet according to its type, To a file data receiver 530, a media data receiver 540, or a signaling data receiver 550 within the network.

The file data receiver 530 processes the packet transmitted from the data receiver 505 and transfers the data included in the packet to the file processor 535. For example, the file data receiver 530 receives an MMTP (MMT Protocol) packet transmitted in a GFD (Generic File Delivery) mode defined by the MMT, reconfigures the MMTP payload to the file processor 535, And extracts the desired data and transmits the extracted data to the file processor 535. The file processor 535 extracts the desired data from the received packet. The file processor 535 reconstructs the individual files based on the data received from the file data receiver 530.

The media data receiver 540 and media processor 545 are components that process media data. For example, if the media data is an MPU (MMT Processing Unit) defined in the MMT, the media processor 545 may be a component that processes media data transmitted in the MPU mode of the MMTP. At this time, the media data receiver 540 reconstructs the MMTP payload based on the MMTP packet transmitted from the MMT data receiver 515 in the data receiver 505 to generate an MPU, and the media processor 545 transmits the MPU And plays it through the service indicator 570.

When the media data is transmitted through a file, the file processor 535 delivers the media file to the media processor 545 and the media processor 545 plays the media file to the service indicator 570. [ As another example, the media handler 545 may be a component that processes media data transmitted in the ROUTE protocol when the media data conforms to the DASH (Dynamic Adaptive Streaming over HTTP) format defined in ISO / IEC 23009-1. At this time, the media processor 545 processes the ROUTE packet received from the ROUTE data receiver 515 to generate a DASH segment, and the media processor 545 reproduces the received DASH segment to the service indicator 570 Role.

The media data receiver 540 may forward the media file to the media processor 545 after generating the entire media file that complies with the ISO Base Media File Format (ISOBMFF), such as an MPU or DASH segment, To the media processor 545, a portion of the media file generated before the entire media file is created.

When the packet received from the data receiver 505 includes signaling information, the packet is transmitted to the signaling data receiver 550 and used to reconstruct the signaling information. The reconstructed signaling information is delivered to the signaling processor 555 and additional operations are performed according to the content of the signaling information. For example, when the signaling information is transmitted through the MMTP, the signaling data receiver 550 receives the MMTP packet storing the signaling information from the MMT data receiver 510 and reconstructs it as an MMTP payload, and the signaling processor 555 transmits the MMTP And parses the signaling information in the payload to store necessary information in a signaling information DB (DataBase) 560. If the signaling information is included in the file and the signaling information is transmitted, the signaling processor 555 receives the file storing the signaling information from the file processor 535, parses the signaling information, and stores the required information in the DB 560.

The signaling processor 555 interacts with other components based on the parsed signaling information to perform additional operations. For example, when signaling information related to the application program service is received, the signaling processor 555 transfers the necessary information to the file data receiver 530 to receive the data necessary for executing the application program service, .

Event information associated with control of the application program service may be transmitted via a dedicated signaling channel or may be inherently transmitted in the media data. For example, in the case of an MMT, the event information may be transmitted via a signaling message or may be inherently transmitted to an MPU storing media data. Similarly, in the case of DASH, the signaling information may be included in the MPS (Media Presentation Description) or transmitted in the DASH segment containing the media data. Accordingly, the media data receiver 540 extracts event-related information from the media data if the event-related information is included in the media data, and transmits the extracted event-related information to the signaling processor 555 and ultimately to the application program manager 565, It is used to control the operation of program services.

The application program manager 565 stores and manages overall information about the application program service, manages the operation of the individual application program service, and displays information of each application program service through the service indicator 570. [ To this end, the application program manager 565 is interworked with the signaling processor 555 and the file processor 535 and receives data and signaling information necessary for providing the application program service.

Hereinafter, an operation of conveying signaling information and event information related to an application program service will be described.

1) transmission of signaling information related to the application program service

The information related to the application program service includes the main properties of the application program service such as the name of the application program service, the transmission method, and the life cycle.

In one embodiment, an Application Information Table (AIT) message may be used, which is a signaling message sent over an MMT signaling session to transmit information related to an application program service. Table 1 below shows an example of the format of the AI (Application Information) table included in the AIT message and the AIT message.

Syntax Number of bits format AIT_message {    message_id 16 uimsbf    version 8 uimsbf length 16 uimsbf    extension {    }    message_payload {       AI_table ()    } }

Herein, the message_id field indicates the ID of the AIT message, the version field indicates the version of the AIT message, the length field indicates the byte size of the AIT message, the length from the next position of the length field to the end of the AIT message, The field contains an AI table.

The AIT message may further include an identifier for identifying a service to which the AIT message is applied in the extension portion. In addition, a 1-bit flag for indicating the presence or absence of a URI (Uniform Resource Identifier) for identifying an AIT message may be further included. If the 1-bit flag is ON, a field indicating a URI is added to the AIT message .

Information about all application program services contained in the MMT package may be transmitted using a single AI table (ie, Complete AI Table) or divided into multiple AI tables (ie, Subset AI Table) . In the latter case, each Subset AI table is transmitted in an independent AIT message.

Table 2 below shows an example of the detailed format of the AI table.

Syntax value Number of bits format AI_table {    table_id 8 uimsbf    version 8 uimsbf length N1 16 uimsbf    reserved '1111' 4 bslbf    AI_table_mode 2 uimsbf    reserved '11' 2 bslbf    AI_table_descriptors {       AI_table_descriptor_length N2 16 uimsbf       for (i = 0; i <N2; ++ i)          AI_table_descriptor_bytes 8 uimsbf    }    AI_count N3 8 uimsbf    for (i = 0; i <N3; ++ i) {       application_attributes ()    } }

The table_id field indicates the ID of the AI table. Complete AI and Subset AI tables can have different table_id. The values of table_id are assigned sequentially, so the number of the Subset AI table can be calculated from the table_id field. That is, the number of the Subset AI table is calculated as "table_id - table_id of the Base Subset AI table". Here, the Base Subset AI table refers to the Subset AI table with the number 0. Numbers 1 through 14 refer to the other (not base) Subset AI cables, and 15 refers to the Complete AI table.

The version field indicates the version of the AI table, and the new version of the AI table replaces the previous version of the AI table upon receipt. The version field can be interpreted the same as the MPI table of the existing MMT signaling table. (If table_id indicates a complete AI table, if Subset-0 AI table has the same version value as this field (when AI_table_mode is '1'), or if all AI table subsets with lower- If the AI table has a new version, AI table subsets with higher subset number up to (AI_table_mode is' 0 '), or if processing of the AI table subsets are independent (when AI_table_mode is' 14 previously stored within an MMT receiving entity is treated as outdated except for the case when AI_table_mode is independent mode. When the AI table subset number is not 0 and AI_table_mode is '1', the contents of the AI table subset with version different from that subset-0 AI table stored in an MMT receiving entity shall be ignored. Also when the AI table subset number is not 0 and AI_table_mode is '0', the contents of the AI table subset with version different from that of the lower-subset AI table subsets stored in an MMT receiving entity shall be ignored. It will be modulo-256 incremented per version change.)

The length field is the byte size of the AI table, indicating the length from the next position in the length field to the end of the AI table.

The AI_table_mode field is used in a manner similar to the PI_mode of the MPI table among the existing MMT signaling tables to specify the processing method of the divided AI table when the AI table is divided and transmitted. (In "sequential_order_processing_mode" and a non-zero subset number of this AI table, an MMT receiving entity shall receive all AT tables with lower subset number, an "order_rerelevant_processing_mode" and the subset number of this AI table subset set to non-zero, an. MMT receiving entity should process a AI table right after it receives the AI table as long as the subset-0 AI table stored in an MMT receiving entity has the same version as this AI table. In "independent_processing_mode", versions of each subset of AI tables are managed individually. Fragmented AI table is adapted in this mode).

Examples of values and descriptions used in the AI_table_mode field are shown in Table 3 below.

AI_table_mode Description 00 "sequential_order_processing_mode" 01 "order_irrelevant_processing_mode" 10 "independent_processing_mode" 11 Reserved

The AI_table_descriptor_bytes field is a descriptor of the AI table. The AI_count field indicates the number of application program services included in the AI table. The application_attributes () field indicates an attribute of each application program service.

As described above, the AI table may include various attributes associated with the application program service, and the corresponding attributes are included in the application_attributes () field. These properties may include the name of the application program service, transmission information and priority of data related to the application program service, and the like. Table 4 below shows an example of application_attributes ().

Syntax Explanation application_attributes () { app_name Application program service name    app_id Application program service ID    related_MMT_assets_count The number of Assets in the MMT package associated with this application program service (N1). If set to 0, this is an application program service that can be executed independently and not linked to the package. for (i = 0; i <N1; ++ i)       asset_id Asset ID    application_transport_methods_count The number of data or file transfer methods required to run application program services (N2)    for (i = 0; i <N2; ++ i)       application_transport Detailed information about transferring data or files related to application program services using a broadcast network or a communications network.    application_priority Application program service priority    application_control_code Lifecycle of application program services (e.g., AutoStart / Present / Kill / Suspend / Prefetch / Destroy / Disabled). Meaning of life cycle according to ETSI TS 102 809    application_type Application program service type    AI_decoder_length    for (i = 0; i <N6; ++ i)       AI_descriptor_bytes Application program service descriptor } }

In the embodiments described below, the information related to the application program service can be transmitted via the MPT message, which is a signaling message related to the MMT package. Specifically, the MPT message includes a descriptor indicating whether or not an application program service exists in the MMT package. The terminal must receive the MPT message in order to reproduce the broadcast service transmitted to the MMT. Accordingly, the terminal can confirm the presence of the application program service more quickly by including the descriptor of the presence or absence of the application program service in the MPT message.

If it is determined through the MPT message that the application program service exists in the MMT package, the terminal can acquire detailed information related to the application program service by receiving the AIT message as described above. The MPT message may further include information to be preferentially provided to the terminal among the information transmitted and included in the AIT as needed, rather than merely indicating whether the application program service is present or absent. The information to be provided preferentially can be information that helps improve the performance of the terminal or improve the quality of experience (QoE).

Table 5 below shows an example of a detailed format of application_service_descriptor which is a descriptor that can be included in the MPT message.

Syntax value Number of bits format application_service_descriptor () {    descriptor_tag 16 uimsbf    descriptor_length 8 uimsbf    application_service_available One bslbf }

Here, the descriptor_tag field indicates a tag that can identify the inband_event_descriptor field, the descriptor_length field indicates the size of the inband_event_descriptor field, and the application_service_descriptor field indicates presence or absence of an application program service in the package. If the value of the application_service_descriptor field is 0, it means that there is no application program service. If 1, the application program service exists, and the detailed information related to the application program service is transmitted through the AIT message.

2) Transmission of event information

The event information can be largely transmitted in two ways depending on whether or not the time of occurrence of the event in the broadcast program can be known in advance. First, a static event transmission method is used when a specific event such as a recording broadcast can be known in advance. Second, when a specific event such as live broadcasting can not be known in advance, Is used. The event information is notified to the application program service.

In one embodiment, the event information may be delivered via an MMT signaling message, i.e., an AEI (Application Event Information) message, transmitted via the MMT signaling channel. AEI messages can be used for both static and dynamic event transmission. In the case of a dynamic event, the event information may be included in the media data in which the event is generated, that is, included in the MPU.

Table 6 and Table 7 below show an example of the detailed format of the MMT signaling message including the event information, that is, the AE table included in the AEI message and the AEI message.

Syntax Number of bits format AEI_message {    message_id 16 uimsbf    version 8 uimsbf    length 16 uimsbf    extension {    }    message_payload {       AE_table ()    } }

Here, the message_id field indicates the ID of the AEI message, the version field indicates the version of the AEI message, the length field indicates the byte size of the AEI message, and the length from the next position of the length field to the end of the AEI message. The AE_table () field contains an AE table.

In one embodiment, the AEI message may further include an identifier for identifying a service to which the AEI message is applied in the extension portion. In addition, a 1-bit flag for indicating whether a URI exists to identify the AEI message may be further included. If the 1-bit flag is ON, a field indicating a URI may be further included in the AEI message.

Syntax value Number of bits format AE_table {    table_id 16 uimsbf    version 8 uimsbf    length 16 uimsbf    reserved 111111 6 bslbf    number_of_app_events N1 8 uimsbf    for (i = 0; i <N1; ++ i) {       AE_descriptor ()    } }

The table_id field indicates the ID of the AE table. The version field indicates the version of the AE table, and the length field indicates the size of the AE table, from the next position in the length field to the end of the AE table. The number_of_app_events field indicates the number of events included in the AE table, and the AE_descriptor () field contains detailed information of each event.

The detailed information of the event is stored in the AE_descriptor () descriptor, and may include various information related to the event, such as the application program service ID associated with the event, the time and period when the event is applied, Table 8 shows an example of AE_descriptor ().

Syntax value Number of bits format AE_descriptor () {    descriptor_tag 16 uimsbf    descriptor_length 8 uimsbf    application_identifier ()    scheme_id_uri_length N1 8 uimsbf    for (i = 0; i <N1; ++ i)    scheme_id_uri_byte 8 uimsbf    event_value_length N2 8 Uimsbf    for (i = 0; i <N2; ++ i)    event_value_byte 8 uimsbf    event_id 32 uimsbf    event_presentation_time 64 uimsbf    event_duration 32 uimsbf    event_data }

Here, the descriptor_tag field indicates a tag that can identify the AE_descriptor (), the descriptor_length field indicates the size of the AE_descriptor (), and the application_identifier () field is a unique ID of the application to which the event is to be applied. Table 9 shows an example of the detailed format of the application_identifier () field.

Syntax Number of bits format application_identifier () {    organization_id 32 uimbsf    application_id 16 uimbsf }

The scheme_id_uri_length field indicates the byte size of the scheme_id_uri field. The scheme_id_uri field defines the meaning and syntax of the value transmitted in the event_data field. The event_value_length field indicates the byte size of the event_data field, and the event_value field indicates an event value. The range and semantics of event values are determined by scheme_id_uri. The event_id field indicates a unique ID of an event, the event_presentation_time field indicates a media play time to which the event is applied, the event_duration field indicates a media play time in which the event is valid, and the event_data field indicates an event content.

In one embodiment, the event information may be delivered via the media data.

In the MMT transmission protocol, media data is transmitted in the MPU, and the MPU follows the ISOBMFF structure. The event information may be included in the evti box in the MPU, and an example of the detailed format of the evti box is as follows.

Box Type: "evti"

Container: MPU

Mandatory: No

Quantity: Zero or more

Syntax:

aligned (8) class EventInformationBox extends FullBox ('evti', version = 0, flags = 0) {

string scheme_id_uri

string event_value

unsigned int (32) event_id

unsigned int (32) event_presentation_time_delta

unsigned int (32) event_duration

unsigned int (32) event_data

string application_identifier

}

Here, the scheme_id_uri field defines the meaning and syntax of values transmitted in the event_data field, and the event_value field includes an event value. The range and semantics of event values are determined by scheme_id_uri. The event_duration field indicates the playback time of the media for which the event is valid. The event_data field indicates the event content. The event_data field indicates a unique ID of the event. The event_presentation_time_delta field indicates a difference between the playback time of the MPU and the playback time of the media to which the event is applied. . The application_identifier field indicates the ID of the application program service to which the event is to be applied.

In one embodiment, event information is transmitted via the MPU of a particular asset, and MMT signaling information may be used to signal that the event information is embedded within the MPU of the asset. To this end, an MP (MMT Package) table for transmitting MMT package information includes an inband_event_descriptor which is a descriptor used at an asset level. When the terminal receives the inband_event_descriptor through the MP table and confirms that the event information is embedded in the MPU of the specific asset, the terminal receives the MPU of the asset and extracts the event information from the evti box in the MPU. Table 10 below shows an example of the detailed format of the inband_event_descriptor.

Syntax value Number of bits format inband_event__descriptor () {    descriptor_tag 16 Uimsbf    descriptor_length 8 Uimsbf    scheme_id_uri_length N1 8 Uimsbf    for (i = 0; i <N1; ++ i)    scheme_id_uri_byte 8 Uimsbf    event_value_length N2 8 Uimsbf    for (i = 0; i <N2; ++ i)    event_value_byte 8 Uimsbf }

Here, the descriptor_tag field is a tag for identifying the inband_event_descriptor, the descriptor_length field indicates the size of the inband_event_descriptor, the scheme_id_uri_length field indicates the byte size of the scheme_id_uri field, and the scheme_id_uri field defines the meaning and syntax of the value transmitted to the event_data field. The event_value_length field indicates the byte size of the event_data field, and the event_value field contains the event value. The range and semantics of event values are determined by scheme_id_uri.

6 is a flowchart illustrating a process of processing event information using an MMT signaling message according to an embodiment of the present invention.

Referring to FIG. 6, in step 605, the terminal receives a selection input of a service by a user, monitors reception of an MMT signaling message associated with the service in step 610, and parses the received MMT signaling message. In step 615, the terminal checks whether the AIT message is included in the MMT signaling message. If there is no AIT message, the terminal reproduces the video / audio stream of the selected service in step 620. On the other hand, if there is an AIT message, in step 625, the terminal receives data related to the application program service using the contents of the AI table included in the AIT message. The terminal can determine the reception start time of data related to the application program service, whether the application program service is immediately executed or the like, according to the attributes of the application program included in the AI table and the user's selection.

In step 630, the UE determines whether an AEI message, which is a signaling message storing event information, is received, and obtains information on an event application time from the AE table included in the AEI message to determine whether the event has reached the event application time. When the event application time is reached, in step 635, the application program service is controlled (e.g., started or ended) based on the corresponding event. The terminal can play the service in step 620 until the event application time is reached.

7 is a flowchart illustrating an event information processing procedure using an MPU according to an embodiment of the present invention.

Referring to FIG. 7, in step 705, the terminal receives a selection input of a service by a user, monitors reception of an MMT signaling message associated with the service in step 710, and parses the received MMT signaling message. In step 715, the terminal checks whether the AIT message is included in the MMT signaling message. If there is no AIT message, the terminal reproduces the video / audio stream of the selected service in step 730. On the other hand, if there is an AIT message, in step 735, the terminal receives data related to the application program service using the contents of the AI table included in the AIT message. The terminal can determine the reception start time of data related to the application program service, whether the application program service is immediately executed or the like, according to the attributes of the application program included in the AI table and the user's selection.

In step 715, the UE checks whether the event information is transmitted in the MPU based on the MMT signaling message. That is, the terminal analyzes the asset level descriptor included in the MP table in the MMT signaling message and checks whether the event information is included in the MPU that transmits the asset. If the asset level descriptor indicates that event information is included in the MPU, the terminal extracts event information from the MPU every time the terminal receives the MPU of the asset in step 720 and stores the extracted event information. In step 740, the UE periodically checks whether an event has been applied during the service replay. For example, information on the event application time can be obtained from the AE table in the AEI message. In step 745, if the event has reached the event application time, the terminal controls the application program service by applying the corresponding event.

In one embodiment, the signaling tables and descriptors may be encapsulated in mmt_atsc3_message (), which may be constructed as shown in Table 11, and transmitted in the Signaling Message mode of the MMTP.

Syntax No. of Bits Format mmt_atsc3_message () { message_id 16 uimsbf version 8 uimsbf length 32 uimsbf message payload { service_id 16 uimsbf atsc3_message_content_type 16 uimbsf atsc3_message_content_version 8 uimbsf atsc3_message_content_compression 8 uimbsf URI_length 8 uimbsf for (i = 0; i <URI_length; i ++) { URI_byte 8 uimsbf } atsc3_message_content_length 32 uimsbf for (i = 0; i <atsc3_message_content_length; i ++) { atsc3_message_content_byte 8 uimsbf } (i = 0; i <length-10-URI_length-atsc3_message_content_length) reserved 8 uimsbf } } }

The meaning of each field in Table 11 is as follows.

message_id - a 16-bit identifier to identify that it is mmt_atsc3_message ()

version - an 8-bit identifier to identify the version of mmt_atsc3_message ()

length - A 32-bit field representing the length in bytes of mmt_atsc3_message (). The length of mmt_atsc3_message () may be the number of bytes from the next byte of length field to the last byte of mmt_atsc3_message ().

service_id - A 16-bit identifier to identify the service to which the information sent to the payload of mmt_atsc3_message () applies. It sets the same value as the atsc: serviceId attribute of USD to be described later.

atsc3_message_content_type - A 16-bit identifier to identify the type of information sent to the payload of mmt_atsc3_message (). For example, the atsc3_message_content_type field can have the values shown in Table 12 below.

atsc3_message_content_type Meaning 0x0000 Reserved 0x0001 userServiceDescription 0x0002 MPD 0x0003 Application Information Table 0x0004 Application Event Information 0x0005 Video Stream Properties Descriptor 0x0006 ATSC Staggercast Descriptor () 0x007 to 0xFFFF Reserved for future use

atsc3_message_content_version - An 8-bit identifier to identify the version of information sent to the message payload of mmt_atsc3_message (). The message payload can be distinguished by a combination of the service_id and the atsc3_message_content_type.

atsc3_message_content_compression - An 8-bit field indicating the compression scheme applied to atsc3_message_content_byte contained in the message payload of mmt_atsc3_message ().

URI_length - An 8-bit field indicating the length of the URI used to identify the message payload. If the URI is not provided, it has a value of 0.

URI_byte - An 8-bit field representing each byte of the URI used to identify the message payload. It is expressed as a UTF-8 character, and does not include terminating null characters.

atsc3_message_content_byte - an 8-bit field indicating each byte of information sent to the message payload

The MMT_atsc3_message () shown in Table 10 can transmit signaling information of all types including XML and binary formats to the message payload, and the format of each signaling information can be determined using the atsc3_message_content_type.

If the inband_event_descriptor described above is transmitted to the payload of mmt_atsc3_message () in Table 11, the inband_event_descriptor may have the format shown in Table 13 below.

Syntax value Number of bits format inband_event__descriptor () { descriptor_tag 16 Uimsbf descriptor_length 8 Uimsbf number_of_assets N1 8 Uimsbf for (i = 0; i <N1; ++ i) { asset_id_length N2 8 Uimsbf for (j = 0; j <N2; ++ j) { asset_id_byte 8 Uimsbf } scheme_id_uri_length N3 8 Uimsbf for (j = 0; j <N3; ++ j) { scheme_id_uri_byte 8 Uimsbf } event_value_length N4 8 Uimsbf for (j = 0; i <N4; ++ j) { event_value_byte 8 Uimsbf } } }

Here, the descriptor_tag field is a tag for identifying the inband_event_descriptor, the descriptor_length field indicates the size of the inband_event_descriptor, and the number_of_assets field indicates the number of the attributes described in the inband_event_descriptor. The asset_id_length field indicates the byte size of the asset identifier, and the asset_id_byte indicates each byte of the asset identifier. The scheme_id_uri_length field indicates the byte size of scheme_id_uri, and the scheme_id_uri field defines the meaning and syntax of the value transmitted in the event_data field. The event_value_length field indicates the byte size of the event_data field, and the event_value field contains the event value. The range and semantics of event values are determined by scheme_id_uri.

In one embodiment, event information is transmitted via the MPU of a particular asset, and MMT signaling information may be used to signal that the event information is embedded within the MPU of the asset. To do this, mmt_atsc3_message () sends the inband_event_descriptor, which is the descriptor used at the asset level, in the payload. The terminal receives the inband_event_descriptor through the mmt_atsc3_message () and confirms that the event information is embedded in the MPU of the specific asset, the terminal receives the MPU of the asset and extracts the event information from the evti box in the MPU.

Various embodiments of the present invention may be embodied as computer readable code in a computer readable recording medium in particular aspects. The computer readable recording medium is any data storage device capable of storing data that can be read by a computer system. Examples of computer readable recording media include read only memory (ROM), random access memory (RAM), compact disk-read only memory (CD-ROMs), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission over the Internet) . The computer readable recording medium may also be distributed over networked computer systems, and thus the computer readable codes are stored and executed in a distributed manner. Also, functional programs, code, and code segments for accomplishing various embodiments of the present invention may be readily interpreted by programmers skilled in the art to which the invention applies.

It will also be appreciated that the apparatus and method according to various embodiments of the present invention may be implemented in hardware, software, or a combination of hardware and software. Such software may be, for example, a volatile or nonvolatile storage device such as a storage device such as ROM, whether removable or rewritable, or a memory such as, for example, a RAM, memory chip, For example, a storage medium readable by a machine (e.g., a computer), such as a compact disk (CD), a DVD, a magnetic disk, or a magnetic tape. A method according to various embodiments of the present invention may be implemented by a computer or a mobile terminal including a controller and a memory, which memory stores programs or programs including instructions embodying embodiments of the present invention It will be appreciated that this is an example of a suitable machine readable storage medium.

Accordingly, the present invention includes a program including code for implementing the apparatus or method described in the claims, and a storage medium readable by a machine (such as a computer) for storing such a program. In addition, such a program may be electronically transported through any medium such as a communication signal transmitted over a wired or wireless connection, and the present invention appropriately includes such equivalent

Also, an apparatus according to various embodiments of the present invention may receive and store a program from a program providing apparatus connected by wire or wirelessly. The program providing apparatus includes a memory for storing a program including instructions for causing the program processing apparatus to perform a predetermined content protection method, information necessary for the content protection method, and the like, and a program for executing a wired or wireless communication with the graphics processing apparatus A communication unit, and a control unit for requesting the graphic processing apparatus or automatically transmitting the program to the transmission / reception apparatus.

The embodiments of the present invention disclosed in the present specification and drawings are merely illustrative of the technical contents of the present invention and are intended to illustrate specific embodiments in order to facilitate understanding of the present invention and are not intended to limit the scope of the present invention. It should also be understood that the embodiments of the present invention described above are merely illustrative, and that those skilled in the art will be able to make various modifications and equivalent embodiments. Accordingly, the true scope of the present invention should be determined by the following claims.

Claims (9)

A digital broadcast service method comprising:
Receiving an AIT message including an application information (AI) table through a multimedia transmission session;
Obtaining attribute information related to an application program service from the AI table;
And executing the application program service based on the attribute information.
The method according to claim 1,
The name of the application program service, the ID of the application program service, the number of assets in the multimedia package associated with the application program service, the detailed information about the transmission of data or files related to the application program service, A lifetime of the application program service, and a type of the application program service.
The method according to claim 1,
Receiving a Multimedia Package Table (MPT) message related to a multimedia package before receiving the AIT message;
Detecting a descriptor indicating the presence of the application service from the MPT message;
Further comprising the step of determining to receive the AIT message if the descriptor indicates that the application program service is present in the multimedia package.
The method according to claim 1,
Receiving an application event information (AEI) message including an application event (AE) table over a multimedia signaling channel;
Acquiring event information associated with the application program service from the AE table;
And controlling the application program service based on the event information.
5. The apparatus of claim 4, wherein the AE table comprises:
An AE table ID, a version information of the AE table, a byte size of the AE table, information on the number of events included in the AE table, and an AE descriptor for each event,
Wherein the AE descriptor includes an ID of an application program service associated with the event, an event application time and duration, and information on an event operation.
The method according to claim 1,
Comprising: receiving a media data unit including media data;
Acquiring event information associated with the application program service from an event information box included in the media data unit;
And controlling the application program service based on the event information.
[7] The method of claim 6,
A unique ID of an event, information on an event application time, information on an event operation, and an ID of an application program service to which the event is to be applied.
The method according to claim 6,
Receiving an MPT message including a multimedia package (MP) table including information on a multimedia package;
Acquiring, from the MP table, a descriptor indicating that the event information is included in the media data unit related to a specific asset;
Further comprising the step of determining to acquire the event information from the event information box in the media data unit when the descriptor indicates that the event information is included in the media data unit.
An apparatus for receiving a digital broadcast service,
A receiver for receiving an AIT message including an application information (AI) table through a multimedia transmission session;
And a control unit for obtaining attribute information related to the application program service from the AI table and executing the application program service based on the attribute information.

Images